stpxNotificationEnable

CISCO-STP-EXTENSIONS-MIB · .1.3.6.1.4.1.9.9.82.1.6.6

Object

scalar r/w Bits

Indicates whether a specified notification is enabled or not.
If a bit corresponding to a notification is set to 1, then 
the specified notification can be generated.
          
newRoot -- the newRoot notification as defined in BRIDGE-MIB.
          
topologyChange -- the topologyChange notification as
                  defined in BRIDGE-MIB.
          
inconsistency -- the stpxInconsistencyUpdate notification.
          
rootInconsistency -- the stpxRootInconsistencyUpdate 
                     notification.
          
loopInconsistency -- the stpxLoopInconsistencyUpdate 
                     notification.

Context

MIB: CISCO-STP-EXTENSIONS-MIB
OID: .1.3.6.1.4.1.9.9.82.1.6.6
Type: scalar
Access: readwrite
Status: current
Parent: stpxSpanningTreeObjects
Groups: 1

Net-SNMP examples

How SNMP and these commands work

Scalars have one instance, identified by the .0 suffix.

Read the scalar instance

/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'CISCO-STP-EXTENSIONS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-STP-EXTENSIONS-MIB::stpxNotificationEnable.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-STP-EXTENSIONS-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-STP-EXTENSIONS-MIB::stpxNotificationEnable'

Syntax

Bits

Values & Constraints

Enumerated Values

`0`	newRoot
`1`	topologyChange
`2`	inconsistency
`3`	rootInconsistency
`4`	loopInconsistency