RNRP showing Primary path Missing for CN1 of AC800M Controller but able to ping with TTL 64
system version: 800xA126.96.36.199
In one of our AC800M Controller (PM866 -red) not showing the primary path CN1 in the RNRP of all nodes, showing as primary path missing but able to ping as TTL 64.
1.Checked the IP and subnet of primary path (CN1) found Ok
2. Restarted the RNRP service still same problem.
3.Re-downloaded the controller but still same problem.
4.Checked the hardware CN1 of both red-controller status and found blinking.
5.Checked the port status in the switch and found showing data traffic healthy.
While other 7 sets (redundant) of AC800M Controllers are showing (up,up) in RNRP without any issues.
Could you please suggest us how to correct the issues
- Check the RNRP settings in the controller, if they were accidentally changed.
- Ultimate solution will probably be to perform a reset (long init) of the controller to flush the network stack, or to restore factory defaults network settings using IPConfig. Both actions will of course cause a noticeable disruption.
Remark: Do not use ping for analyzing CN1/CN2 issues, because your ping request will probably be routed to CN2 in your case (this fooled me more than once).
A path down means RNRP in the observing node does not receive any periodic hello messages from that interface on the controller.
When this happen, RNRP reroute the traffic via the other path.
ping cannot differentiate this situation from a normal situation.
Stop RNRP (disable to prevent auto start) in the pinging computer to see "true" ping results.
Port Statistics should be quite different if path0 is down. Did you reset the counters before taking your sample?
1. Pull controller log via Control Builder M > Tools > Remote System
2. Pull Network Statistics via above, but followed by > Controller Diagnosis > Network Info > Get
Study these logs. There should be indications that traffic isn't flowing normally via path0.
Remember to check the IP address in use from the log - a recent change may be pending a controller reset.
Engage your regional support team.