Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

G430 FW 30.12.1 HW 1 NR-CONN issues

Status
Not open for further replies.

TwistedWire

Technical User
May 4, 2001
38
I have a S8800 CM 6.0.1 around 70 remote G430 FW 30.12.1 HW 1. The G430's intermittently experience NR-CONN alarms that resolve within 5 secs, although, the alarm remains present until I do a test failed ip-net-rgns command. I have called Avaya Spt and they are at a loss as to what it is. Can anyone explaing the NR-CONN and what can be the root cause for something like this. I appreciate any input provided. Thanks.
 
This is from the 5.2.1 version of Maintenance Alarms for Avaya Aura™ Communication Manager, Media Gateways and Servers, but it may shed some light on what you are looking at.

NR-CONN (Network-Region Connect)
A network region is a logical grouping of IP endpoints (including IP stations, IP trunks, and
media gateways) sharing the same transmission characteristics and/or VoIP and signaling
resources, such as a Media Processor board or a C-LAN. The Network-Region Connect
(NR-CONN) MO monitors VoIP connectivity between network regions and raises a:
● Warning alarm for a single failure.
This alarm is in response to one failed background ping test between IP endpoints in
separate network regions. This test is part of the background Network Region
Interconnectivity Test (#1417).
● Minor alarm for multiple failures.
Once a single failure is detected, Test #1417 is re-executed between different IP endpoints
in the same pair of network regions. If the test still fails between these network regions:
- Maintenance software marks the connectivity between them as “failed.”
- Communication Manager denies every attempted call between them.
As a background operation during each 2-minute interval, Test #1417 checks the translated
connections between 50 pairs of network regions until every translated connection has been
tested, and then repeats. (The Communication Manager translation table’s maximum capacity
for network-region connections is 31,250. Testing every possible connection would require 625
2-minute test intervals during about 21 hours.)
Repair strategies
● Use display failed-ip-network-region to display pairs of network regions with
failed connectivity. In descending order of severity, this command lists up to 100 network
regions with the most severely broken connectivity.
● Use status ip-network-region to see the status of connections from a particular
network region.
● As an on-demand operation, test failed-ip-network-region retests every
network-region connection marked as “failed.” Those connections that:
- Pass are returned to service.
- Fail are remarked as “failed” and remain on the list of bad connections.
MO Name
in Log
Alarm
Level
Initial Command to Run Full Name of MO
NR-CONN MIN
WRN
test failed-ip-network-region Network-Region Connect
692 Maintenance Alarms for Communication Manager, Media Gateways and Servers
Error log entries and recommended actions
Note:
a. Error Type 1: one or more network-region connections have failed.
1. Enter display failed-ip-network-region to verify that connections between
pairs of network regions are failing.
2. If so, enter test failed-ip-network-region to retest these paths.
3. For each affected network region, check the error log for failures to related MOs, such
as:
- IPMEDPRO (IP Media Processor Circuit Pack)
- MEDPRO (Media Processor MAPD Circuit Pack)
- CLAN-BD (Control LAN Circuit Pack)
- DIG-IP-S (Digital IP Station)
- RDIG-STA (Remote Digital Station)
and resolve any problems.
4. Enter test failed-ip-network-region to retest these paths.
5. If errors persist, escalate.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top