Chronic NR-CONN Alarms

If you are getting NR-CONN alerts and reports of no talk path check out this article

Details
Users are unable to place and receive calls and Communication Manager has a NR-CONN alarm. Use the command display failed-ip-network-region to show which regions currently have an issue communicating with each other.

NR-Conn-Alarm

Here we see regions 2 and 5 cannot communicate (PING) region 1

Let's investigate further...
Get logged into the Active Communication Server using Linux, you can also view this data from the web interface but that will be outside the scope of this article.

Next, we run the command grep -A4 ps_mapa /var/log/ecs/2020-0814* using your year and date as an argument.

2020-0814-124902.log:20200814:125521962:2146058:ps_mapa(2609):HIGH:[net_region:
2020-0814-124902.log- Internetwork region connectivity test failures:
2020-0814-124902.log- Testing between regions 2 and 5
2020-0814-124902.log- MG 3 pinged MG 6
2020-0814-124902.log- MG 6 pinged MG 3 ]
--
2020-0814-125932.log:20200814:130021335:2148047:ps_mapa(2609):HIGH:[net_region:
2020-0814-125932.log- Internetwork region connectivity test failures:
2020-0814-125932.log- Testing between regions 2 and 5
2020-0814-125932.log- MG 3 pinged MG 6
2020-0814-125932.log- MG 6 pinged MG 3 ]
--
2020-0814-125932.log:20200814:131021327:2150851:ps_mapa(2609):HIGH:[net_region:
2020-0814-125932.log- Internetwork region connectivity test failures:
2020-0814-125932.log- Testing between regions 2 and 5
2020-0814-125932.log- MG 3 pinged MG 6
2020-0814-125932.log- MG 6 pinged MG 3 ]
--
2020-0814-131117.log:20200814:131521426:2152265:ps_mapa(2609):HIGH:[net_region:
2020-0814-131117.log- Internetwork region connectivity test failures:
2020-0814-131117.log- Testing between regions 2 and 5
2020-0814-131117.log- MG 3 pinged MG 6
2020-0814-131117.log- MG 6 pinged MG 3 ]


Solution
We will need to login to media gateway 6 using SSH and try to use the traceroute command to see if we can reach media gateway 3.

mun-mgp1-006(super)# traceroute 132.147.20.186
Tracing route to 132.147.20.186 over a maximum of 30 hops, 32 bytes packets.
Press any key to abort.
1 1 ms 1 ms 1 ms 10.10.10.1
2 16 ms 16 ms 16 ms 192.168.1.99


Gateway 6 is unable to ping or traceroute to gateway 3's IP address. This ticket needs to go to the customer to figure out any routing and or firewall issues that may be taking place.
Was this article helpful?
Cancel
Thank you!