瞻博网络 vMX 路由器无法在 GNS3 中相互 ping 通

网络工程 杜松 瞻博网络 GNSS3 瞻博网络
2021-07-28 08:05:30

我在 GNS3 中设置了几个 VMX 路由器,它们直接连接在它们的接口 ge-0/0/2 上,并且它们无法相互 ping。PFB 配置。我好像找不到问题!

更新:在底部添加了所有 GNS3 拓扑详细信息

R1 配置

root@R1> show configuration             
## Last commit: 2020-09-11 14:29:18 UTC by root
version 14.1R1.10;
system {
    host-name R1;
    root-authentication {
    encrypted-password "$1$MJbVQp1z$J1HQasM0nRJXAbvMhUR/R."; ## SECRET-DATA
    }
    syslog {
    user * {
        any emergency;
    }
    file messages {
        any notice;
        authorization info;
    }
    file interactive-commands {
        interactive-commands any;
    }
    }
}
interfaces {
    ge-0/0/2 {
    unit 0 {
        family inet {               
            address 192.168.0.1/24;
        }
    }
    }
}

root@R1> 

R2 配置

root@R2> show configuration 
## Last commit: 2020-09-11 10:12:59 UTC by root
version 14.1R1.10;
system {
    host-name R2;
    root-authentication {
    encrypted-password "$1$5Aoo5B1X$SXlXzKs384GMYsTXnBDmH0"; ## SECRET-DATA
    }
    syslog {
    user * {
        any emergency;
    }
    file messages {
        any notice;
        authorization info;
    }
    file interactive-commands {
        interactive-commands any;
    }
    }
}
interfaces {
    ge-0/0/2 {
    unit 0 {
        family inet {               
            address 192.168.0.2/24;
        }
    }
    }
}

root@R2> 

如您所见,这是一个非常基本的配置——只是直连接口两端的一个 IP 地址。我什至尝试通过 GNS3 使用wireshark 进行数据包捕获,但在线路上看不到一个数据包!

但是,两端肯定存在路径。我也没有学习接口上的任何 ARP 条目。

root@R1> show interfaces terse | match ge-0/0/2 
ge-0/0/2                up    up
ge-0/0/2.0              up    up   inet     192.168.0.1/24  


root@R2> show interfaces terse | match ge-0/0/2 
ge-0/0/2                up    up
ge-0/0/2.0              up    up   inet     192.168.0.2/24  

root@R1> show arp interface ge-0/0/2 

root@R1> show arp interface ge-0/0/2.0  

root@R1> ping 192.168.0.1 
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=1.997 ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.116 ms
^C
--- 192.168.0.1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.116/1.056/1.997/0.941 ms

root@R1> ping 192.168.0.2    
PING 192.168.0.2 (192.168.0.2): 56 data bytes
^C
--- 192.168.0.2 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss

root@R1> show route                     

inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.0.0/24     *[Direct/0] 00:34:45
                > via ge-0/0/2.0
192.168.0.1/32     *[Local/0] 00:34:45
                  Local via ge-0/0/2.0

root@R2> show route 

inet.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

192.168.0.0/24     *[Direct/0] 04:51:35
                > via ge-0/0/2.0
192.168.0.2/32     *[Local/0] 04:51:35
                  Local via ge-0/0/2.0

版本信息——两个路由器

两个路由器都运行完全相同的镜像:

root@R1> show version brief 
Hostname: R1
Model: vmx
Junos: 14.1R1.10
JUNOS Base OS Software Suite [14.1R1.10]
JUNOS Base OS boot [14.1R1.10]
JUNOS Crypto Software Suite [14.1R1.10]
JUNOS Online Documentation [14.1R1.10]
JUNOS Kernel Software Suite [14.1R1.10]
JUNOS Packet Forwarding Engine Support (M320) [14.1R1.10]
JUNOS Packet Forwarding Engine Support (M/T/EX Common) [14.1R1.10]
JUNOS Routing Software Suite [14.1R1.10]
JUNOS Runtime Software Suite [14.1R1.10]
JUNOS Services AACL PIC package [14.1R1.10]
JUNOS Services Application Level Gateway [14.1R1.10]
JUNOS Services Application Level Gateway (xlp64) [14.1R1.10]
JUNOS Services Application Level Gateway (xlr64) [14.1R1.10]
JUNOS AppId Services PIC Package [14.1R1.10]
JUNOS Services AppId PIC package (xlr64) [14.1R1.10]
JUNOS Border Gateway Function PIC package [14.1R1.10]
JUNOS Services Captive Portal and Content Delivery PIC package [14.1R1.10]
JUNOS Services HTTP Content Management PIC package [14.1R1.10]
JUNOS Services HTTP Content Management PIC package (xlr64) [14.1R1.10]
JUNOS IDP Services PIC Package [14.1R1.10]
JUNOS Packet Forwarding Engine Trio Simulation Package [14.1R1.10]
JUNOS Services JFLOW PIC package [14.1R1.10]
JUNOS Services JFLOW PIC package (xlp64) [14.1R1.10]
JUNOS Services LL-PDF PIC package [14.1R1.10]
JUNOS MobileNext PIC package [14.1R1.10]
JUNOS MobileNext PIC package (xlr64) [14.1R1.10]
JUNOS Services Mobile Subscriber Service Container package [14.1R1.10]
JUNOS Services Mobile Subscriber Service PIC package (xlr64) [14.1R1.10]
JUNOS Services NAT PIC package [14.1R1.10]
JUNOS Services NAT PIC package (xlp64) [14.1R1.10]
JUNOS Services NAT PIC package (xlr64) [14.1R1.10]
JUNOS Services PTSP PIC package [14.1R1.10]
JUNOS Services RPM PIC package [14.1R1.10]
JUNOS Services RPM PIC package (xlp64) [14.1R1.10]
JUNOS Services Stateful Firewall PIC package [14.1R1.10]
JUNOS Services Stateful Firewall PIC package (xlp64) [14.1R1.10]
JUNOS Services Stateful Firewall PIC package (xlr64) [14.1R1.10]
JUNOS BSG PIC package [14.1R1.10]
JUNOS Services Crypto Base PIC package [14.1R1.10]
JUNOS Services Crypto Base PIC package [14.1R1.10]
JUNOS Services Crypto Base PIC package(xlr64) [14.1R1.10]
JUNOS Services IPSec PIC package [14.1R1.10]
JUNOS Services IPSec PIC package [14.1R1.10]
JUNOS Services IPSec PIC(xlr64) package [14.1R1.10]
JUNOS Services SSL PIC package [14.1R1.10]

我究竟做错了什么?

故障排除:

尝试了此链接的建议:我的两个瞻博网络 J2320 路由器无法相互 ping

甚至没有选择:

root@R2# set security forwarding-options
                  ^
syntax error.
root@R2# set security forwarding-optionsfamily            
                  ^
syntax error.
root@R2# set security forwarding-optionsfamilympls
                  ^
syntax error.
root@R2# set security forwarding-optionsfamilymplsmode
                  ^
syntax error.
root@R2# set security forwarding-optionsfamilymplsmodepacket-based
                  ^
syntax error.
root@R2# set security forwarding-optionsfamilymplsmodepacket-based   
                  ^
syntax error.
root@R2# set security forwarding                                     
                  ^
syntax error.
root@R2# set security forwarding                                    
                  ^
syntax error.
root@R2# set security ?            
Possible completions:
> alarms               Configure security alarms
+ apply-groups         Groups from which to inherit configuration data
+ apply-groups-except  Don't inherit configuration data from these groups
> authentication-key-chains  Authentication key chain configuration
> group-vpn            Group VPN configuration
> idp                  IDP configuration
> ike                  IKE configuration
> ipsec                IPSec configuration
> log                  Configure auditable security logs
> pki                  PKI service configuration
> ssh-known-hosts      SSH known host list
> traceoptions         Trace options for IPSec key management
[edit]
root@R2# delete security          
warning: statement not found

[edit]
root@R2# 

更新:添加 GNS3 拓扑和配置

这是拓扑:

拓扑 1 拓扑 2

这是 GNS3 中的模板设置:

配置1 配置2 配置3 配置4 配置5

1个回答

我认为您在 GNS3 中连接的接口em2 ---- em2实际上是ge-0/0/0由 vMX 节点命名的。尝试edit interfaces rename ge-0/0/2 to ge-0/0/0vMX,提交并检查连接性;或者在 GNS3 中将em4接口相互连接并检查当前的 vMX 配置是否有效。

关于 GNS3/vMX 接口命名的文档非常混乱。它告诉您前两个接口用于内部连接,这实际上意味着 JunOS 将 eth0/em0 和 eth1/em1 用于 fxp0 和 fxp1(或您正在运行的 JunOS 映像所命名的任何名称)。您可以使用的第一个接口是ge-0/0/0GNS3 将其称为 eth2 或 em2。

摘自 GNS3 vMX & vQFX参考

    Eth0 = the management interface (fxp0)
    Eth1 = internal interface (unusable to us)
    Eth2 = ge-0/0/0
    Eth3 = ge-0/0/1
    Eth4 = ge-0/0/2
    …
    Eth11 = ge-0/0/9

Thus, if you wanted to connect ge-0/0/0 on two vMX instances to each other, you’d connect Eth2 on both VMs to each other.