Data Center (VDX)

 Requesting help :VDX 8770 unable to ping a directly connected MLX router

Jump to Best Answer
thaizoun's profile image
thaizoun posted 09-01-2021 18:56

Hello All,

I am new to the VDX platform. We have a VDX fabric in our lab .We have two VDXs directly connected to  two MLXes.We configured OSPF on both the MLXes and the VDXs. The ports are routed ports with OSPF set on them .OSPF neighborships gets established and we see ospf  routes on the MLXes and we can ping VDXs from the MLXs  but not from the VDXs even though we see the ip of the MLXs in the arp table within the VDX.

we configured rb 4 from within the principal rb (rb1)

 

I am not sure why we cannot ping the MLX from within rb1 .We can ping the MLX from the rb4 itself , but not from within the principal rb ( fabric )

 

rb1# sh lldp nei rbridge-id 4
Local Intf    Dead Interval  Remaining Life  Remote Intf                       Chassis ID        Tx           Rx                  System Name
Te 4/2/14     120            115             0024.388f.803d                    0024.388f.8000    10           6                   MLXe4-3

Total no. of Records: 1
rb1# conf t
Entering configuration mode terminal
rb1(config)# rbridge-id 4
rb1(config-rbridge-id-4)# do show ip ospf nei rbridge-id 4
Number of Neighbors is 1, in FULL state 1

Port           Address         Pri State      Neigh Address   Neigh ID        Ev      Opt Cnt
Te 4/2/14      38.0.0.2        1   FULL/OTHER 38.0.0.1        3.3.3.3         5       2   0
rb1(config-rbridge-id-4)# do show arp  rbridge-id 4
Entries in VRF default-vrf : 1
Address          Mac-address     L3 Interface  L2 Interface  Age         Type
--------------------------------------------------------------------------------
38.0.0.1         0024.388f.803d  Te 4/2/14     Te 4/2/14     00:01:35    Dynamic
rb1(config-rbridge-id-4)# do ping 38.0.0.1
Type Control-c to abort
PING 38.0.0.1 (38.0.0.1): 56 data bytes
ping: sendto: Network is unreachable
ping: sendto: Network is unreachable
ping: sendto: Network is unreachable
^C^C--- 38.0.0.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
rb1(config-rbridge-id-4)#

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

MLXe4-3#sh lldp nei
Total number of LLDP neighbors on all ports: 1
Lcl Port Chassis ID      Port ID         Port Description        System Name
2/14     0027.f810.c59c  TenGigabitEthe~                         rb4
MLXe4-3#
MLXe4-3#
MLXe4-3#sh ip ospf nei
Number of Neighbors is 1, in FULL state 1

Port   Address         Pri State      Neigh Address   Neigh ID        Ev        Opt Cnt
2/14   38.0.0.1        1   FULL/OTHER 38.0.0.2        8.8.8.8         5         2   0
MLXe4-3#
MLXe4-3#
MLXe4-3#
MLXe4-3#ping 38.0.0.2
Sending 1, 16-byte ICMP Echo to 38.0.0.2, timeout 5000 msec, TTL 64
Type Control-c to abort
Reply from 38.0.0.2        : bytes=16 time=1ms TTL=64
Success rate is 100 percent (1/1), round-trip min/avg/max=1/1/1 ms.
MLXe4-3#

 

 

Any help /tips would be highly appreciated.

 

THX

Talal

 

Deep Bakul Bhojani's profile image
Deep Bakul Bhojani

Hello Talal,

On the vdx fabric the Layer2 works together however for the layer3 each VDX will need to have route and path to the MLX. So for this particular case you should be able to ping from the actual rb 4 VDX (ssh into the rb 4) to the MLX IP.

 

Regards,

Deep

thaizoun's profile image
thaizoun

Hi Deep,

Thank you for responding to my question and for the explanation.I thought so too as i am able to ping the MLXes from rb4 & rb5

 

Regards,

Talal