No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-Next Hop incorrect due to mangement service affected but still can be pinged

Publication Date:  2014-06-21 Views:  46 Downloads:  0
Issue Description
【Problem Summary】  The issue that the third party eNodeB management network cannot be reached.
【Problem Details】 The management service failed but the ping result is successful.
【Topology】

Handling Process

1、  Check the ip routing-table of the management IP address, we can see we use a broadcast ip address by mistake.

<HAG-SIN.20ENERO-M1>display ip routing-table vpn-instance lte_OAM 10.66.128.2(Belong to NMS)

Route Flags: R - relay, D - download to fib

------------------------------------------------------------------------------

Routing Table : lte_OAM

Summary Count : 1

Destination/Mask    Proto   Pre  Cost      Flags     NextHop         Interface

0.0.0.0/0        Static  60   0          RD   10.64.189.127     InLoopBack0

 

<HAG-SIN.20ENERO-M1>display ip routing-table vpn-instance lte_OAM 10.64.189.127

Route Flags: R - relay, D - download to fib

------------------------------------------------------------------------------

Routing Table : lte_OAM

Summary Count : 1

Destination/Mask    Proto   Pre  Cost      Flags   NextHop         Interface

10.64.189.127/32   Direct  0    0           D   127.0.0.1       GigabitEthernet2/0/5

2、  When we ping from EnodeB(laptop) with the ip 10.228.160.1 to the NMS server 10.66.128.2, it’s successful.

Root Cause
 We made a mistake that set the broadcast ip address 10.64.189.127 as the default route next-hop. When we ping from EnodeB(laptop device) to NMS, the ping request packet will send to our inLoopBack . For us, we will think the packet is our host IP, so we feedback the icmp reply. Then, the ping is successful.
Solution
【Resolution Summary】Change the next-hop of the default route to the peer device host ip address.
【Resolution Details】[Cause analysis]//[ROOT CAUSE] We made a mistake that set the broadcast ip address 10.64.189.127 as the default route next- hop. When we ping from EnodeB(laptop device) to NMS, the ping request packet will send to our in LoopBack . For us, we will think the packet is our host IP, so we feedback the icmp reply. Then, the ping is successful. [Solution Description] Change the next-hop of the default route to the peer device host ip address.
Suggestions
【Resolution Summary】Change the next-hop of the default route to the peer device host ip address.
【Resolution Details】[Cause analysis]//[ROOT CAUSE] We made a mistake that set the broadcast ip address 10.64.189.127 as the default route next- hop. When we ping from EnodeB(laptop device) to NMS, the ping request packet will send to our inLoopBack . For us, we will think the packet is our host IP, so we feedback the icmp reply. Then, the ping is successful. [Solution Description] Change the next-hop of the default route to the peer device host ip address.

END