Troubleshooting NR-CONN alarms in Avaya Aura CM
Errors/alarms of maintenance name “NR-CONN” indicate a network-region connectivity failure.
display errors Page 1
HARDWARE ERROR REPORT - ACTIVE ALARMS
Port Mtce Alt Err Aux First/Last Err Err Rt/ Al Ac
Name Name Type Data Occurrence Cnt Rt Hr St
NR-CONN 1 01/10/15:32 58 12 8 a y
01/10/20:17
display alarms Page 1
ALARM REPORT
Port Mtce On Alt Alarm Svc Ack? Date Date
Name Brd? Name Type State 1 2 Alarmed Resolved
NR-CONN n MINOR y 01/10/15:32 00/00/00:00
To list an index of the network regions having network connectivity issues, use this:
display failed-ip-network-region
WORST NETWORK REGIONS
Network Region:Number of Broken Paths
21 :5 : : : : : : :
27 :3 : : : : : : :
24 :2 : : : : : : :
14 :2 : : : : : : :
16 :1 : : : : : : :
18 :1 : : : : : : :
22 :1 : : : : : : :
23 :1 : : : : : : :
25 :1 : : : : : : :
15 :1 : : : : : : :
: : : : : : : :
: : : : : : : :
: : : :
If you aren’t sure which network-region is which, you can see a list of them here:
list ip-network-region monitor Page 1
IP NETWORK REGIONS MONITOR
Port No RTCP Monitor Report Codec UDP Port Range
Region Name IPv4/ IPv4 Address/ Period Set Min Max
IPv6 IPv6 Address
1 CRTH 5005 5 1 2048 65535
5005
[...]
14 wlsb 5005 5 1 2048 65535
5005
[...]
21 MJDC 5005 5 1 2048 65535
5005
[...]
27 engr 5005 5 1 2048 65535
5005
[...]
So, you can see that network-region 1’s name is “CRTH”, etc.
To see which ip-network-regions specifically are having communication issues amongst themselves, test them:
test failed-ip-network-region
TEST RESULTS
Region Dest. Region Maintenance Name Test No. Result Error Code
21 14 NR-CONN 1417 FAIL 1
27 14 NR-CONN 1417 FAIL 1
21 15 NR-CONN 1417 FAIL 1
24 16 NR-CONN 1417 FAIL 1
27 18 NR-CONN 1417 FAIL 1
22 21 NR-CONN 1417 FAIL 1
23 21 NR-CONN 1417 FAIL 1
25 21 NR-CONN 1417 FAIL 1
27 24 NR-CONN 1417 FAIL 1
You’ll see that regions 21 (MJDC) and 27 (engr) are unable to reach region 14 (wlsb), etc. It’s up to you to determine the cause of the failed inter-region network connectivity, and to resolve it. Once you believe you’ve identified and resolved the issue, re-run the above test; if communication is back up, the result will change from “FAIL” to “PASS” for that specific origin-destination region combination - only for the first test. Each combination that passes will be removed from the list of failed regions, and will not be tested on subsequent tests (unless routine maintenance detects another failure).
To confirm that you have resolved all of your issues, ask CM to give you a list of failed-ip-network-regions:
display failed-ip-network-region
WORST NETWORK REGIONS
Network Region:Number of Broken Paths
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : : : : : :
: : : :
In this specific example (which was real), the errors were expected as a result of extended-duration power outages.
