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

A classic troubleshooting case that PDSN configuration errors lead to less ping loss

Publication Date:  2014-12-16 Views:  54 Downloads:  0
Issue Description

Network description:

NE40E-1 connects NE40E-2 through Eth-Trunk1.There are two members port G3/0/1 and G2/0/10 on Eth-Trunk1, port G2/0/0 are conncected to S8505-1. Eth-Trunk1 and G2/0/0 are layer 2 ports, which belong to VLAN 903. Port G4/0/16 are connected to the left network. Both VLANIF 903 and G4/0/16 is binding VPN instance CDMA-RP. VRRP is enabled between two NE40E and the heartbeat runs through the connected Eth-Trunk. The VRRP state of NE40E-1 is master.

 

interface GigabitEthernet4/0/16

description to_BSC11_PCF0

undo shutdown

ip binding vpn-instance CDMA-RP

ip address 172.16.96.1 255.255.255.252

interface Vlanif903

description TO_liantong_RP

ip binding vpn-instance CDMA-RP

ip address 172.16.126.46 255.255.255.128

vrrp vrid 93 virtual-ip 172.16.126.45

vrrp vrid 93 priority 105


 

Topology:

Fault description:

Customers feedback that the service was affected, Through telnet to the NE and ping test, we found there are less ping loss between OSS equipment (172.16.97.1) to PDSN (172.16.126.42) when the service throughput is around peak value everyday.

Handling Process

Please refer the detail handling process to the attachment 《A classic troubleshooting case that PDSN configuration errors lead to less ping loss》

Root Cause

It is due to static configuration errors of PDSN.

Solution

Need to Modify the PDSN static route configuration, which corrected the route to NE40E VRRP Group virtual IP.

Suggestions

Please refer the suggestions as in the attachment.

END