09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Communication Manager Maintenance Object Repair Procedures<br />

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

MO Name in Log Alarm<br />

Level<br />

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

Initial Command 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 and IP phones is being denied because the disable<br />

nr-registration network-region command was executed.<br />

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

phones will register with the LSP based on the primary search list for gateways and 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 command is entered from the SAT.<br />

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

network-region commands should only be used for situations where IP network problems<br />

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

that is too fast for the normal link bounce strategy to cause the gateways and 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 and 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 />

1060 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s

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

Saved successfully!

Ooh no, something went wrong!