BASIS-GENERIC-MIB - moduleTrapAlarmSeverity

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

moduleTrapAlarmSeverity

module Trap Alarm Severity
1.3.6.1.4.1.351.110.2.1.15

This object is sent to managers as part of all Trap PDUs, to determine the module alarm severity. An implementation may not support all the possible values. The Possible values are : major (1) : Major Service has been impacted minor (2) : Minor Service has been lost dontCare (3) : severity is not applicable critical (4) : affects existing data traffic error (5) : error has occurred warning (6) : a threshold has been reached notice (7) : a normal but significant event has occurred info (8) : informational ::= { cardInformation 15 } SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION MIB version number. Updated when any part of the MIB changes. DEFVAL { 2 } ::= { cardInformation 16 } SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION Configuration change Type BitMap bit 0 set = Card Configuration Change bit 1 set = Line Configuration Change bit 2 set = Port Configuration Change bit 3 set = Chan Configuration Change bit 4 set = STUN protocol group configuration Change bit 5 set = STUN port configuration Change bit 6 set = STUN route configuration Change bit 7 set = BSTUN protocol configuration Change bit 8 set = BSTUN port configuration Change bit 9 set = BSTUN route configuration Change bit 10 set = FRASBNN route configuration Change bit 11 set = FRASBAN route configuration Change bit 12 set = SDLC port configuration Change bit 13 set = SDLC LS configuration Change bit 14 set = BSC port configuration Change bit 15 set = LLC port configuration Change bit 16 set = card LCN partition change (controller based only) bit 17 set = port resource partition change (under any partition type) bit 18 set = VISM Endpoint Configuration Change bit 19 set = Egress Q configuration change default value is 0, no change This object makes sense only in traps. A GET on this may not return a Useful result. Bit 19 is not applicable for MGX 8850 Release 1.x.x and MGX 8220 DEFVAL { 0 } ::= { cardInformation 17 } SYNTAX INTEGER (1..1024) ACCESS read-only STATUS mandatory DESCRIPTION Configuration change object index, could be line number or port number or channel number depends on the type bitmap, for port resouce partition change (bit 17), this index is actually constructed by (portNum << 16 | controller) because the table has two indices. When the 'Line Configuration Change' bit is set, the configChangeObjectIndex has the following special meanings in IMATM and FRSM-2CT3 cards: IMATM - configChangeObjectIndex range between 1..8 indicates that the configuration change refers to the DS1 line index. A value of 9 indicates that the configuration change refers to the DS3 line index. FRSM-2CT3 - configChangeObjectIndex range between 1..56 indicates that the configuration change refers to the DS1 line index. A value of (128 + n) refers to DS3 line index numbered 'n'. This object makes sense only in traps. A GET on this may not return a Useful result. ::= { cardInformation 18 } SYNTAX INTEGER (0..3) ACCESS read-only STATUS mandatory DESCRIPTION This object is applicable only for traps. The SNMP operation may not be meaningful. The value contained in this object is same as the value of the other objects which are used for adding/deleting/modifying the row. The possible values are 0 - No meaning and is not applicable. 1 - add [ Row added ] 2 - delete [ Row deleted ] 3 - mod [ Row modified ] This value and value contained in configChangeTypeBitMap represent the configuration change operation. The default value is 0 and it does not represent any status.

Back to BASIS-GENERIC-MIB MIB page.

IPHost Network monitor allows you to monitor moduleTrapAlarmSeverity on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco optical switches right now.

How to get moduleTrapAlarmSeverity value right now?

MIBs list