09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - 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.

<strong>Server</strong> <strong>Alarms</strong><br />

STD (Standard SNMP Traps)<br />

Table 29: STD <strong>Alarms</strong> describes STD traps and their troubleshooting procedures.<br />

Table 29: STD <strong>Alarms</strong><br />

Event<br />

ID<br />

Alarm<br />

Level<br />

Type Cause/Description<br />

1 MIN ACT "coldStart" - Agent Up with Possible Changes. A coldStart trap indicates<br />

that the entity sending the protocol (SNMPv2) is re initializing itself in<br />

such a way as to potentially cause the alteration of either the agent’s<br />

configuration or the entity’s implementation.<br />

2 MIN ACT “warmStart" - Agent Up with No Changes. A warmStart trap indicates that<br />

the entity sending the protocol (SNMPv2) is re initializing itself in such a<br />

way as to keep both the agent configuration and the entity’s<br />

implementation intact.<br />

3 MIN ACT "linkDown" - Agent Interface Down. A linkDown trap indicates that the<br />

entity sending the protocol (SNMPv2) recognizes a failure in one of the<br />

communication links represented in the agent’s configuration. The data<br />

passed within the event is 1) The name and value of the ifIndex instance<br />

for the affected interface. 2) The name of the interface can be retrieved<br />

via an snmpget of .1.3.6.1.2.1.2.2.1.2.INST, where INST is the instance<br />

returned with the trap. The state is indicated by the included value of<br />

ifOperStatus.<br />

3 MIN RES "linkUP" - Agent Interface Up. A linkUp trap indicates that the entity<br />

sending the protocol (SNMPv2) recognizes that one of the<br />

communication links represented in the agent’s configuration has come<br />

up. The data passed within the event is 1) The name and value of the<br />

ifIndex instance for the affected interface. 2) The name of the interface<br />

can be retrieved via an snmpget of .1.3.6.1.2.1.2.2.1.2.INST, where INST<br />

is the instance returned with the trap. The state is indicated by the<br />

included value of ifOperStatus.<br />

Back to: Linux <strong>Server</strong> <strong>Alarms</strong><br />

102 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!