extremeNetsightAlarmMessage
1.3.6.1.4.1.5624.1.2.105.1.1.1
OCTET STRING SIZE (0..256)
The message describing the specific alarm triggered.
2016-08-29
This MIB module defines a portion of the SNMP MIB under the Enterasys Networks enterprise OID pertaining to definitions and notifications for the Extreme Netsight network management software. This MIB defines a set of notifications that the Netsight Alarm Manager can send to another SNMP trap receiver.
Download EXTREME-NETSIGHT-ALARM-MIB.txt Open EXTREME-NETSIGHT-ALARM-MIB.txt in a new tab
END OF TOC
1.3.6.1.4.1.5624.1.2.105.1.1.1
OCTET STRING SIZE (0..256)
The message describing the specific alarm triggered.
1.3.6.1.4.1.5624.1.2.105.1.1.2
INTEGER0 = emergency1 = alert2 = critical3 = error4 = warning5 = notice6 = info7 = debug · Integer32
The severity of an alarm. Lower values signify more serious conditions, whereas higher values are less critical.
1.3.6.1.4.1.5624.1.2.105.1.1.3
DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The date and time, in device local time, when the alarm occurred.
1.3.6.1.4.1.5624.1.2.105.1.1.4
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
The address type of extremeNetsightAlarmSourceDeviceAddress.
1.3.6.1.4.1.5624.1.2.105.1.1.5
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The address of the device that triggered this alarm. This may be the address of the Netsight server itself or a remote device managed by Netsight.
1.3.6.1.4.1.5624.1.2.105.1.1.6
OCTET STRING SIZE (0..256)
Additional event specific data for this alarm (e.g. interface number). Note that in most cases there is no such data, and this object will be an empty string.
1.3.6.1.4.1.5624.1.2.105.1.0.1
This notification indicates that an alarm was triggered and contains information related to that alarm. Note that this notification is generic and MAY not be used when a more specific notification is defined for a given alarm. NOTE: The list of OBJECTS defined for this alarm will act as a template for all other notifications defined in this group and they should include the same list.
1.3.6.1.4.1.5624.1.2.105.1.1.1
OCTET STRING SIZE (0..256)
The message describing the specific alarm triggered.
1.3.6.1.4.1.5624.1.2.105.1.1.2
INTEGER0 = emergency1 = alert2 = critical3 = error4 = warning5 = notice6 = info7 = debug · Integer32
The severity of an alarm. Lower values signify more serious conditions, whereas higher values are less critical.
1.3.6.1.4.1.5624.1.2.105.1.1.3
DateAndTimeA date-time specification. field octets contents range ----- ------ -------- ----- 1 1-2 year* 0..65536 2 3 month 1..12 3 4 day 1..31 4 5 hour 0..23 5 6 minutes 0..59 6 7 seconds 0..60 (use 60 for leap-second) 7 8 deci-seconds 0..9 8 9 direction from UTC '+' / '-' 9 10 hours from UTC* 0..13 10 11 minutes from UTC 0..59 * Notes: - the value of year is in network-byte order - daylight saving time in New Zealand is +13 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be displayed as: 1992-5-26,13:30:15.0,-4:0 Note that if only local time is known, then timezone information (fields 8-10) is not present. SIZE (8 | 11) · OCTET STRING · hint 2d-1d-1d,1d:1d:1d.1d,1a1d:1d
The date and time, in device local time, when the alarm occurred.
1.3.6.1.4.1.5624.1.2.105.1.1.4
InetAddressType0 = unknown1 = ipv42 = ipv63 = ipv4z4 = ipv6z16 = dnsA value that represents a type of Internet address. unknown(0) An unknown address type. This value MUST be used if the value of the corresponding InetAddress object is a zero-length string. It may also be used to indicate an IP address that is not in one of the formats defined below. ipv4(1) An IPv4 address as defined by the InetAddressIPv4 textual convention. ipv6(2) An IPv6 address as defined by the InetAddressIPv6 textual convention. ipv4z(3) A non-global IPv4 address including a zone index as defined by the InetAddressIPv4z textual convention. ipv6z(4) A non-global IPv6 address including a zone index as defined by the InetAddressIPv6z textual convention. dns(16) A DNS domain name as defined by the InetAddressDNS textual convention. Each definition of a concrete InetAddressType value must be accompanied by a definition of a textual convention for use with that InetAddressType. To support future extensions, the InetAddressType textual convention SHOULD NOT be sub-typed in object type definitions. It MAY be sub-typed in compliance statements in order to require only a subset of these address types for a compliant implementation. Implementations must ensure that InetAddressType objects and any dependent objects (e.g., InetAddress objects) are consistent. An inconsistentValue error must be generated if an attempt to change an InetAddressType object would, for example, lead to an undefined InetAddress value. In particular, InetAddressType/InetAddress pairs must be changed together if the address type changes (e.g., from ipv6(2) to ipv4(1)). · Integer32
The address type of extremeNetsightAlarmSourceDeviceAddress.
1.3.6.1.4.1.5624.1.2.105.1.1.5
InetAddressDenotes a generic Internet address. An InetAddress value is always interpreted within the context of an InetAddressType value. Every usage of the InetAddress textual convention is required to specify the InetAddressType object that provides the context. It is suggested that the InetAddressType object be logically registered before the object(s) that use the InetAddress textual convention, if they appear in the same logical row. The value of an InetAddress object must always be consistent with the value of the associated InetAddressType object. Attempts to set an InetAddress object to a value inconsistent with the associated InetAddressType must fail with an inconsistentValue error. When this textual convention is used as the syntax of an index object, there may be issues with the limit of 128 sub-identifiers specified in SMIv2, STD 58. In this case, the object definition MUST include a 'SIZE' clause to limit the number of potential instance sub-identifiers; otherwise the applicable constraints MUST be stated in the appropriate conceptual row DESCRIPTION clauses, or in the surrounding documentation if there is no single DESCRIPTION clause that is appropriate. SIZE (0..255) · OCTET STRING
The address of the device that triggered this alarm. This may be the address of the Netsight server itself or a remote device managed by Netsight.
1.3.6.1.4.1.5624.1.2.105.1.1.6
OCTET STRING SIZE (0..256)
Additional event specific data for this alarm (e.g. interface number). Note that in most cases there is no such data, and this object will be an empty string.
1.3.6.1.4.1.5624.1.2.105.1.0.2
Device Up
1.3.6.1.4.1.5624.1.2.105.1.0.3
Device Down
1.3.6.1.4.1.5624.1.2.105.1.0.4
Link Up
1.3.6.1.4.1.5624.1.2.105.1.0.5
Link Down
1.3.6.1.4.1.5624.1.2.105.1.0.6
Fan OK
1.3.6.1.4.1.5624.1.2.105.1.0.7
Fan Failure
1.3.6.1.4.1.5624.1.2.105.1.0.8
Power supply normal
1.3.6.1.4.1.5624.1.2.105.1.0.9
Power supply failed
1.3.6.1.4.1.5624.1.2.105.1.0.10
MultiAuth max users reached
1.3.6.1.4.1.5624.1.2.105.1.0.11
MultiAuth module max users reached
1.3.6.1.4.1.5624.1.2.105.1.0.12
MultiAuth system max users reached
1.3.6.1.4.1.5624.1.2.105.1.0.13
OSPF Conflicting packet
1.3.6.1.4.1.5624.1.2.105.1.0.14
Spanguard
1.3.6.1.4.1.5624.1.2.105.1.0.15
MSTP Loop Protect Event
1.3.6.1.4.1.5624.1.2.105.1.0.16
STP Diagnostic MSTI
1.3.6.1.4.1.5624.1.2.105.1.0.17
STP Diagnostic CIST
1.3.6.1.4.1.5624.1.2.105.1.0.18
Cold start
1.3.6.1.4.1.5624.1.2.105.1.0.19
Warm start
1.3.6.1.4.1.5624.1.2.105.1.0.20
MultiAuth Success
1.3.6.1.4.1.5624.1.2.105.1.0.21
MultiAuth Failed
1.3.6.1.4.1.5624.1.2.105.1.0.22
MultiAuth terminated
1.3.6.1.4.1.5624.1.2.105.1.0.23
Configuration Changed
1.3.6.1.4.1.5624.1.2.105.1.0.24
AP In Service
1.3.6.1.4.1.5624.1.2.105.1.0.25
AP Out of Service
1.3.6.1.4.1.5624.1.2.105.1.0.26
AP Radio Change
1.3.6.1.4.1.5624.1.2.105.1.0.27
AP Radio OnOff
1.3.6.1.4.1.5624.1.2.105.1.0.28
Interference Stopped
1.3.6.1.4.1.5624.1.2.105.1.0.29
Interference Started
1.3.6.1.4.1.5624.1.2.105.1.0.30
Threat Inactive
1.3.6.1.4.1.5624.1.2.105.1.0.31
Threat Active
1.3.6.1.4.1.5624.1.2.105.1.0.32
Appliance Disk Usage
1.3.6.1.4.1.5624.1.2.105.1.0.33
Database Backup Disk Usage
1.3.6.1.4.1.5624.1.2.105.1.0.34
Rogue Inactive
1.3.6.1.4.1.5624.1.2.105.1.0.35
Rogue Active
1.3.6.1.4.1.5624.1.2.105.1.0.36
IPMI Event
1.3.6.1.4.1.5624.1.2.105.1.0.37
AC Power Recovered
1.3.6.1.4.1.5624.1.2.105.1.0.38
AC Power Lost
1.3.6.1.4.1.5624.1.2.105.1.0.39
Drive Fault Recovered
1.3.6.1.4.1.5624.1.2.105.1.0.40
Drive Fault
1.3.6.1.4.1.5624.1.2.105.1.0.41
Application Analytics License Violation Clear
1.3.6.1.4.1.5624.1.2.105.1.0.42
Application Analytics License Violation
1.3.6.1.4.1.5624.1.2.105.1.0.43
Application Analytics Appliance Up
1.3.6.1.4.1.5624.1.2.105.1.0.44
Application Analytics Appliance Down
1.3.6.1.4.1.5624.1.2.105.1.0.45
NAC Appliance Up
1.3.6.1.4.1.5624.1.2.105.1.0.46
NAC Appliance Down
1.3.6.1.4.1.5624.1.2.105.1.0.47
NAC License Violation Clear
1.3.6.1.4.1.5624.1.2.105.1.0.48
NAC License Violation
1.3.6.1.4.1.5624.1.2.105.1.0.49
NAC Assessment License Violation Clear
1.3.6.1.4.1.5624.1.2.105.1.0.50
NAC Assessment License Violation
1.3.6.1.4.1.5624.1.2.105.1.0.51
NAC Lost Contact with Switch Clear
1.3.6.1.4.1.5624.1.2.105.1.0.52
NAC Lost Contact with Switch
1.3.6.1.4.1.5624.1.2.105.1.0.53
NAC Lost Partial Contact with Switch Clear
1.3.6.1.4.1.5624.1.2.105.1.0.54
NAC Lost Partial Contact with Switch
1.3.6.1.4.1.5624.1.2.105.1.0.55
NAC Lost Contact with RADIUS Server Clear
1.3.6.1.4.1.5624.1.2.105.1.0.56
NAC Lost Contact with RADIUS Server
1.3.6.1.4.1.5624.1.2.105.1.0.57
NAC Lost Contact with LDAP Service Clear
1.3.6.1.4.1.5624.1.2.105.1.0.58
NAC Lost Contact with LDAP Service
1.3.6.1.4.1.5624.1.2.105.1.0.59
NAC Lost Partial Contact with LDAP Service Clear
1.3.6.1.4.1.5624.1.2.105.1.0.60
NAC Lost Partial Contact with LDAP Service
1.3.6.1.4.1.5624.1.2.105.1.0.61
NAC RFC 3576 Error Clear
1.3.6.1.4.1.5624.1.2.105.1.0.62
NAC RFC 3576 Error
1.3.6.1.4.1.5624.1.2.105.1.0.63
NAC Database Table Service is up
1.3.6.1.4.1.5624.1.2.105.1.0.64
NAC Database Table Service down
1.3.6.1.4.1.5624.1.2.105.1.0.65
NAC RADIUS Requests Warning Threshold Rectified
1.3.6.1.4.1.5624.1.2.105.1.0.66
NAC RADIUS Requests Warning Threshold Exceeded
1.3.6.1.4.1.5624.1.2.105.1.0.67
NAC RADIUS Requests Critical Threshold Rectified
1.3.6.1.4.1.5624.1.2.105.1.0.68
NAC RADIUS Requests Critical Threshold Exceeded
1.3.6.1.4.1.5624.1.2.105.1.0.69
NAC Certificate Updated
1.3.6.1.4.1.5624.1.2.105.1.0.70
NAC Certificate has Invalid Date
1.3.6.1.4.1.5624.1.2.105.1.0.71
NAC Certificate Warning Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.72
NAC Certificate Expiring Warning
1.3.6.1.4.1.5624.1.2.105.1.0.73
NAC Certificate Notice Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.74
NAC Certificate Expiring Notice
1.3.6.1.4.1.5624.1.2.105.1.0.75
NAC Duplicate SNMP Engine ID Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.76
NAC Duplicate SNMP Engine ID Found
1.3.6.1.4.1.5624.1.2.105.1.0.77
Device Topology Change
1.3.6.1.4.1.5624.1.2.105.1.0.78
Device % CPU
1.3.6.1.4.1.5624.1.2.105.1.0.79
Device Memory % Usage
1.3.6.1.4.1.5624.1.2.105.1.0.80
Host % CPU
1.3.6.1.4.1.5624.1.2.105.1.0.81
Host Disk % Usage
1.3.6.1.4.1.5624.1.2.105.1.0.82
Host Memory % Usage
1.3.6.1.4.1.5624.1.2.105.1.0.83
Interface % Usage
1.3.6.1.4.1.5624.1.2.105.1.0.84
Interface % Valid Packets
1.3.6.1.4.1.5624.1.2.105.1.0.85
Historical Persistence Resumed
1.3.6.1.4.1.5624.1.2.105.1.0.86
Historical Persistence Suspended
1.3.6.1.4.1.5624.1.2.105.1.0.87
Analytics Persistence Resumed
1.3.6.1.4.1.5624.1.2.105.1.0.88
Analytics Persistence Suspended
1.3.6.1.4.1.5624.1.2.105.1.0.89
Controller Established SSH Connection
1.3.6.1.4.1.5624.1.2.105.1.0.90
Controller Failed SSH Connection
1.3.6.1.4.1.5624.1.2.105.1.0.91
Server Heap Memory OK
1.3.6.1.4.1.5624.1.2.105.1.0.92
Server Heap Memory Low
1.3.6.1.4.1.5624.1.2.105.1.0.93
Client MAC Availability Low
1.3.6.1.4.1.5624.1.2.105.1.0.94
Client MAC IP Changes High
1.3.6.1.4.1.5624.1.2.105.1.0.95
NAC Entries Per Group Performance Threshold Rectified
1.3.6.1.4.1.5624.1.2.105.1.0.96
NAC Entries Per Group Performance Threshold Exceeded
1.3.6.1.4.1.5624.1.2.105.1.0.97
NAC Certificate Uses MD5 Signature Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.98
NAC Certificate Uses MD5 Signature Notice
1.3.6.1.4.1.5624.1.2.105.1.0.99
NAC winbindd Process Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.100
NAC winbindd Process Down
1.3.6.1.4.1.5624.1.2.105.1.0.101
NAC squid Process Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.102
NAC squid Process Down
1.3.6.1.4.1.5624.1.2.105.1.0.103
NAC radiusd Process Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.104
NAC radiusd Process Down
1.3.6.1.4.1.5624.1.2.105.1.0.105
NAC dnsproxy Process Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.106
NAC dnsproxy Process Down
1.3.6.1.4.1.5624.1.2.105.1.0.107
NAC IPMI Critical Event Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.108
NAC IPMI Critical Event
1.3.6.1.4.1.5624.1.2.105.1.0.109
NAC DNS Servers Unreachable Cleared
1.3.6.1.4.1.5624.1.2.105.1.0.110
NAC DNS Servers Unreachable