[Troubleshooting Series] Case 23 Ping Failure Troubleshooting

560 0 0 0

Ping Failure Troubleshooting

Physical Network Topology

Figure 1-1 Network where a ping failure occurs

151701lqeqesu6ij8qsdwj.png

 

Networking Description

As shown in Figure 4-1, SwitchB is one VS of CE12800. It establishes a EBGP neighbor witch CE12800, and configures 128 VPN instances on the device and 200 static routes, then imports these routes to BGP protocol between different VPN instance, there will be 64K routes, lastly to ping the device from CE12800 to VS of the CE12800.

Fault Description

When the CE12800-Switch is used to carry the loopback address as the source IP address and attempt to ping the loopback address of the CE12800 device, packet loss occurs.

[~R4U13-CE12800-SWITCH-B] ping -a 5.5.5.5 7.7.7.7
PING 7.7.7.7: 56  data bytes, press CTRL_C to break 
    Reply from 7.7.7.7: bytes=56 Sequence=1 ttl=254 time=9 ms 
    Request time out
    Reply from 7.7.7.7: bytes=56 Sequence=3 ttl=254 time=3 ms
    Request time out
    Reply from 7.7.7.7: bytes=56 Sequence=5 ttl=254 time=4 ms
 
  --- 7.7.7.7 ping statistics ---
    5 packet(s) transmitted   
    3 packet(s) received                       
    40.00% packet loss                    
    round-trip min/avg/max = 3/5/9 ms

[~R4U13-CE12800-SWITCH-B] ping -a 5.5.5.5 7.7.7.7
PING 7.7.7.7: 56  data bytes, press CTRL_C to break 
    Reply from 7.7.7.7: bytes=56 Sequence=1 ttl=254 time=3 ms 
    Request time out
    Reply from 7.7.7.7: bytes=56 Sequence=3 ttl=254 time=5 ms
    Request time out
    Reply from 7.7.7.7: bytes=56 Sequence=5 ttl=254 time=3 ms
 
  --- 7.7.7.7 ping statistics ---
    5 packet(s) transmitted   
    3 packet(s) received                       
    40.00% packet loss                    
    round-trip min/avg/max = 3/3/5 ms

Configuration Files

!Software Version V100R005C10SPC200
dfs-group 1
 source ip 10.1.1.2 
#
mpls lsr-id 5.5.5.5
#
bridge-domain 10
 vxlan vni 5010
#
traffic classifier test type or
 if-match ipv6 acl 3000
#
traffic behavior test
 redirect interface 10GE3/0/9
#
traffic policy test
 classifier test behavior test precedence 5
#
interface Vlanif100
 ip address 10.1.1.2 255.255.255.0
 pim silent
 pim sm
 igmp enable
#
interface Vlanif1000
 ipv6 enable
 ip address 100.100.1.103 255.255.255.0
 ipv6 address 1000:1000::1/64
 vrrp vrid 1 virtual-ip 100.100.1.101
 vrrp6 vrid 2 virtual-ip FE80::5 link-local
 vrrp6 vrid 2 virtual-ip 1000:1000::1000
 traffic-policy test inbound 
#  
interface Eth-Trunk1
 peer-link 1
 port vlan exclude 1000 
#
interface Eth-Trunk10
 port default vlan 1000
 dfs-group 1 m-lag 500
#
interface Eth-Trunk10.1 mode l2
 encapsulation dot1q vid 4000
 bridge-domain 10
#
interface 10GE3/0/2
 undo portswitch
 mtu 1300
 ipv6 enable
 ip address 107.1.1.2 255.255.255.0
 ipv6 address 100::2/64
 ospfv3 100 area 0.0.0.0
 jumboframe enable 1536
 device transceiver 1000BASE-X
#
interface LoopBack1
 ip address 5.5.5.5 255.255.255.255
#
interface Nve1
 source 5.5.5.5
 vni 5010 head-end peer-list 1.1.1.1
#
interface Tunnel1
 ipv6 enable
 ip address 13.13.13.14 255.255.255.0
 ipv6 address 100:100::100/64
 tunnel-protocol gre
 source 107.1.1.2
 destination 107.1.1.1
 ospfv3 100 area 0.0.0.0
#
bgp 10089
 peer 107.1.1.1 as-number 10086
 #
 ipv4-family unicast
  import-route direct  
  peer 107.1.1.1 enable
#
ospf 100
 import-route direct
 import-route static
 area 0.0.0.0
  network 5.5.5.5 0.0.0.0
  network 13.13.13.0 0.0.0.255
  network 107.1.1.0 0.0.0.255 

Troubleshooting Procedure

                               Step 1      Check the information about router neighbours and the information about the IP routing table.

# Run the display bgp peer command in the user view to check the status about BGP peers.

[~R4U13-CE12800-SWITCH-B] display bgp peer
 BGP Local router ID : 10.1.1.2
 local AS number : 10089
 Total number of peers : 1                 
 Peers in established state : 1
 
  Peer        V    AS  MsgRcvd  MsgSent  OutQ  Up/Down       State PrefRcv
  107.1.1.1   4 10086      316      290     0 04:00:39 Established      10

# Run the display ip routing-tableip-address command in the user view to check the information about the Ip routing table.

[~R4U13-CE12800-SWITCH-B] display ip routing-table 7.7.7.7
Proto: Protocol        Pre: Preference
Route Flags: R - relay, D - download to fib, T - to vpn-instance
------------------------------------------------------------------------------
Routing Table: _public_
Summary Count:1
 
   Destination/Mask  Proto  Pre  Cost  Flags   NextHop   Interface
 
        7.7.7.7/32   EBGP_  255  0     RD      107.1.1.1 10GE3/0/2

Exclude the cause that the configuration of the routing protocol is incorrect, the network created by the unsuccessful establishment of the neighbor cannot be reached after the confirmation.

                               Step 2      Check the ping test on per segment.

# Ping the BGP peer of the CE12800 to test the connectivity of the direct port on the CE12800-SwitchB.

[~R4U13-CE12800-SWITCH-B] ping 107.1.1.1
  PING 107.1.1.1: 56  data bytes, press CTRL_C to break
    Reply from 107.1.1.1: bytes=56 Sequence=1 ttl=254 time=2 ms
    Reply from 107.1.1.1: bytes=56 Sequence=2 ttl=254 time=2 ms
    Reply from 107.1.1.1: bytes=56 Sequence=3 ttl=254 time=2 ms
    Reply from 107.1.1.1: bytes=56 Sequence=4 ttl=254 time=2 ms
    Reply from 107.1.1.1: bytes=56 Sequence=5 ttl=254 time=2 ms
  --- 107.1.1.1 ping statistics ---
    5 packet(s) transmitted
    5 packet(s) received
    0.00% packet loss
    round-trip min/avg/max = 2/2/2 ms

# Ping the loopback address of the CE12800 device with the loopback address as the source IP address on the CE12800-SwitchB.

[~R4U13-CE12800-SWITCH-B] ping -a 5.5.5.5 7.7.7.7
PING 7.7.7.7: 56  data bytes, press CTRL_C to break  
    Reply from 7.7.7.7: bytes=56 Sequence=1 ttl=254 time=9 ms 
    Request time out
    Reply from 7.7.7.7: bytes=56 Sequence=3 ttl=254 time=3 ms
    Request time out
    Reply from 7.7.7.7: bytes=56 Sequence=5 ttl=254 time=4 ms
 
  --- 7.7.7.7 ping statistics ---
    5 packet(s) transmitted   
    3 packet(s) received                       
    40.00% packet loss                    
    round-trip min/avg/max = 3/5/9 ms

From the above tests, it can be found that the link between the direct interfaces can be reached, but there is a packet loss situation between the loopback interfaces.

                               Step 3      Check the statistics of the ICMP packets sent to the CPU.

 


  • x
  • convention:

Reply

Reply
You need to log in to reply to the post Login | Register

Notice: To protect the legitimate rights and interests of you, the community, and third parties, do not release content that may bring legal risks to all parties, including but are not limited to the following:
  • Politically sensitive content
  • Content concerning pornography, gambling, and drug abuse
  • Content that may disclose or infringe upon others ' commercial secrets, intellectual properties, including trade marks, copyrights, and patents, and personal privacy
Do not share your account and password with others. All operations performed using your account will be regarded as your own actions and all consequences arising therefrom will be borne by you. For details, see " Privacy."
If the attachment button is not available, update the Adobe Flash Player to the latest version!

Login and enjoy all the member benefits

Login
Fast reply Scroll to top