All MIBs › JUNIPER-MIMSTP-MIB › jnxMIMstDebug
jnxMIMstDebug
Module: JUNIPER-MIMSTP-MIB
OID (symbolic): JUNIPER-MIMSTP-MIB::jnxMIMstDebug
OID (numeric): 1.3.6.1.4.1.2636.3.46.1.1.3.1.23
Node type: OBJECT-TYPE
Type: Integer32
Access: read-only
Description: This object is used to enable Debug Statements in the MSTP Module.
A FOUR BYTE integer is used for enabling the level of debugging. Each BIT in the four byte integer, represents a particular level of Debug.
The mapping between the bit positions & the level of debug is as follows: 0 - Init and Shutdown Debug statements 1 - Management Debug statements 2 - Memory related Debug statements 3 - BPDU related Debug statements 4 - Event Handling Debug statements 5 - Timer Module Debug statements 6 - Port Information SEM Debug statements 7 - Port Receive SEM Debug statements (valid in the case of MSTP alone) 8 - Role Selection SEM Debug statements 9 - Role Transition SEM Debug statements 10 - State Transition SEM Debug statements 11 - Protocol Migration SEM Debug statements 12 - Topology Change SEM Debug statements 13 - Port Transmit SEM Debug statements 14 - Bridge Detection SEM Debug statements 15 - All Failure Debug statements 16 - Redundancy code flow Debug statements
The remaining bits are unused. Combination of debug levels are also allowed.
For example if the bits 0 and 1 are set, then the Debug statements related to Init-Shutdown and management will be printed.
The user has to enter the corresponding INTEGER VALUE for the bits set. For example if bits 0 and 1 are to be set then user has to give the value for this object as 3.
Setting the Debug Option to any value will cause the Trace Option to be set to 0 (i.e.) the Trace Option and Debug Option are mutually exclusive.
What is jnxMIMstDebug?
A wider bitmask (0-131071) selecting which categories of MSTP debug statements to print, covering things like memory, BPDU, timer, and per-state-machine debug output; setting any nonzero value here zeroes out jnxMIMstTrace because debug and trace logging are mutually exclusive. Like jnxMIMstTrace, this is a temporary diagnostic aid an engineer enables only while investigating a specific spanning-tree fault.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2636.3.46.1.1.3.1.23 snmpwalk -v2c -c public <target> JUNIPER-MIMSTP-MIB::jnxMIMstDebug
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2636.3.46.1.1.3.1.23.1 snmpget -v2c -c public <target> JUNIPER-MIMSTP-MIB::jnxMIMstDebug.1
Start monitoring Juniper EX-series Ethernet switch (MIMSTP, any generation) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JUNIPER-MIMSTP-MIB::jnxMIMstDebug OID value, configure state conditions and alerts, and monitor any Juniper EX-series Ethernet switch (MIMSTP, any generation) from a single console.
OID Breakdown
Upper-level ancestors (9 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.2636 | juniperMIB | JUNIPER-SMI |
| 1.3.6.1.4.1.2636.3 | jnxMibs | JUNIPER-SMI |
| 1.3.6.1.4.1.2636.3.46 | jnxXstpMibs | JUNIPER-SMI |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2636.3.46.1 | jnxMIMstMIB | JUNIPER-MIMSTP-MIB |
| 1.3.6.1.4.1.2636.3.46.1.1 | jnxMIDot1sJuniperMst | JUNIPER-MIMSTP-MIB |
| 1.3.6.1.4.1.2636.3.46.1.1.3 | jnxMIDot1sJuniperMstTable | JUNIPER-MIMSTP-MIB |
| 1.3.6.1.4.1.2636.3.46.1.1.3.1 | jnxMIDot1sJuniperMstEntry | JUNIPER-MIMSTP-MIB |
| 1.3.6.1.4.1.2636.3.46.1.1.3.1.23 | jnxMIMstDebug | JUNIPER-MIMSTP-MIB |