SNIA-SML-MIB :: trapPerceivedSeverity

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › SNIA-SML-MIB › trapPerceivedSeverity

trapPerceivedSeverity

Module: SNIA-SML-MIB

OID (symbolic): SNIA-SML-MIB::trapPerceivedSeverity

OID (numeric): 1.3.6.1.4.1.14851.3.1.16.6

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: An enumerated value that describes the severity of the Alert Indication from the notifier's point of view: 1 - Other, by CIM convention, is used to indicate that the Severity's value can be found in the OtherSeverity property. 3 - Degraded/Warning should be used when its appropriate to let the user decide if action is needed. 4 - Minor should be used to indicate action is needed, but the situation is not serious at this time. 5 - Major should be used to indicate action is needed NOW. 6 - Critical should be used to indicate action is needed NOW and the scope is broad (perhaps an imminent outage to a critical resource will result). 7 - Fatal/NonRecoverable should be used to indicate an error occurred, but it's too late to take remedial action. 2 and 0 - Information and Unknown (respectively) follow common usage. Literally, the AlertIndication is purely informational or its severity is simply unknown. This would have values described in SMI-S 1.1 section 8.1.8.25 LibraryAlert Events/Indications for Library Devices, the PerceivedSeverity column. These values are a superset of the Info/Warning/Critical values in the T10 TapeAlert Specification v3 (w/SSC-3 Enhancements) , and an SNMP agent may choose to only specify those if that's all that's available. (This corresponds to the CIM_AlertIndication.PerceivedSeverity property.)

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.14851.3.1.16.6
snmpwalk -v2c -c public <target> SNIA-SML-MIB::trapPerceivedSeverity

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.14851.3.1.16.6.1
snmpget -v2c -c public <target> SNIA-SML-MIB::trapPerceivedSeverity.1

Start monitoring vendor-neutral, standards-based MIB (SNIA SMI-S), SAN storage subsystems/enclosures (chassis identity/security-breach status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the SNIA-SML-MIB::trapPerceivedSeverity OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB (SNIA SMI-S), SAN storage subsystems/enclosures (chassis identity/security-breach status) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
Numeric OIDNameModule
1.3.6.1.4.1.14851sniaSNIA-SML-MIB
1.3.6.1.4.1.14851.3librariesSNIA-SML-MIB
1.3.6.1.4.1.14851.3.1smlRootSNIA-SML-MIB
1.3.6.1.4.1.14851.3.1.16trapGroupSNIA-SML-MIB
1.3.6.1.4.1.14851.3.1.16.6trapPerceivedSeveritySNIA-SML-MIB