19.12.2012 Views

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

Demand test descriptions and error codes - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

NR-REG (Network Region Registrations)<br />

MO Name in Log Alarm<br />

Level<br />

The NR-REG maintenance object generates alarms when:<br />

NR-REG (Network Region Registrations)<br />

Initial Comm<strong>and</strong> to Run Full Name of MO<br />

NR-REG MIN none Network Region<br />

Registrations<br />

WRN enable nr-registration<br />

network-region<br />

● there has been hyperactive registration of gateways within a network region<br />

● registration from media gateways <strong>and</strong> IP phones is being denied because the disable<br />

nr-registration network-region comm<strong>and</strong> was executed.<br />

It is assumed that an LSP is provided for the network region <strong>and</strong> that the gateways <strong>and</strong> IP<br />

phones will register with the LSP based on the primary search list for gateways <strong>and</strong> the<br />

alternate gatekeeper list for IP phones.<br />

NR-REG alarms will only be generated if hyperactive link bounce detection is enabled on the<br />

system-parameters ip-options screen. Registration will be denied only if the disable<br />

nr-registration network-region comm<strong>and</strong> is entered from the SAT.<br />

The hyperactive NR-REG alarms <strong>and</strong> the associated disable/enable nr-registration<br />

network-region comm<strong>and</strong>s should only be used for situations where IP network problems<br />

cause media gateways <strong>and</strong> IP phones to repeatedly register <strong>and</strong> unregister to a server at a rate<br />

that is too fast for the normal link bounce strategy to cause the gateways <strong>and</strong> phones to fail over<br />

to an LSP.<br />

The system detects hyperactivity by monitoring the number of link down failures reported to the<br />

MED-GTWY maintenance object. When enough link down failures are detected within the<br />

administered time frame, an alarm is raised against the offending media gateway. Using this<br />

data, a percentage of hyperactive media gateways is calculated <strong>and</strong> checked against the<br />

administered system-wide limit. If the limit is exceeded, a minor alarm is generated for the<br />

network region. The system does not try to recover from hyperactivity. It only generates an<br />

alarm.<br />

If a certain period of time passes without any additional link down events, the hyperactivity<br />

alarm is cleared. The alarm is resolved if less than 50% of the media gateways required to raise<br />

an alarm are out of hyperactive mode.<br />

Issue 5 May 2009 693

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!