NR-CONN alarm

[lever]

Hi all,

we currently have this minor alarm after our maintainer made some changes between sites.

When i run the failed-ip-network-region I can see clearly we have problems on a few NR's between the sites, BUT our maintainer says because we don't have ping turned on with have to live with it.

Surly this can't be right...can it?

both sites are 5.2, one is a 8800 with G650's and the other "hangs off" it with G450's and a 8300 LSP.

 

[redphone]

No, it is not right.

NR-CONN alarm means that there are devices in a region that needs codecs assigned to them to talk to another region, but no codec has been assigned.

Run the 'test failed-ip-network-region' command to see what two regions do not have codecs set between them.

Then run 'ch ip-network-region n' (where n is one of the numbers listed in the previous test). Start on page 4 and find the destination region (dst rgn) it failed against and assign it a codec set.