nnbundleDownCause – BUNDLE-MIB – Observium MIB Browser

Object

scalar Enumeration

Reason for the bundle going down
admin_delete - bundle has been deleted by administrator,
admin_down - bundle has been disabled administratively,
l1-failure - Layer 1 failures (physical links), 
		including physical alarms, errors,etc. If a bundle
		is a multilink bundle, then the bundle will go down
		if all the inks go down. In case of MFR 
		bundles, bundles behave according to the 
		bandwidth class settings.
l2-failure - Layer 2 related failures: LCP for PPP and  
		LMI for FR bundles.
bcp-negotiation-fail - BCP negotiation failures on PPP bundles.
l3-failure - Layer 3 related failures. NCP for PPP. Incase of 
		FR bundles, the layer 3 negotiation failures 
		will not bring the bundle down.
bundle-track-down - Bundle is disabled by bundle tracking,

Context

MIB: BUNDLE-MIB
OID: .1.3.6.1.4.1.562.73.1.1.1.13.5.1.2
Type: scalar
Access: notifyonly
Status: current
Parent: nnbundleTrapVariables

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 'BUNDLE-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'BUNDLE-MIB::nnbundleDownCause.0'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'BUNDLE-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'BUNDLE-MIB::nnbundleDownCause'

Syntax

Enumeration

Values & Constraints

Enumerated Values

`1`	admin-delete
`2`	admin-down
`3`	l1-failures
`4`	l2-negotiation-fail
`5`	bcp-negotiation-fail
`6`	l3-negotiation-fail
`7`	bundle-track-down