RAPID-CITY-BAY-STACK

        BayStack specific portion of RAPID-CITY-MIB.
    
Source file
RAPID-CITY-BAY-STACK
Last revised
Identity
rcBayStackMIB
Base OID
1.3.6.1.4.1.2272.40.1
Imported Objects
INET-ADDRESS-MIB InetAddress InetAddressType
RAPID-CITY rcBayStack
RC-MLT-MIB rcMltId
SNMP-FRAMEWORK-MIB SnmpEngineID
SNMPv2-SMI Integer32 IpAddress MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
Net-SNMP examples using the nortel MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'RAPID-CITY-BAY-STACK' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RAPID-CITY-BAY-STACK::rcBayStackMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'RAPID-CITY-BAY-STACK' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RAPID-CITY-BAY-STACK::rcBayStackMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (17)
.1.3.6.1.4.1.2272.40.1
.1.3.6.1.4.1.2272.40.1.1
.1.3.6.1.4.1.2272.40.1.1.1
Enumeration
.1.3.6.1.4.1.2272.40.1.1.1.1
.1.3.6.1.4.1.2272.40.1.1.2
.1.3.6.1.4.1.2272.40.1.1.2.1
Integer32
.1.3.6.1.4.1.2272.40.1.1.2.1.1
.1.3.6.1.4.1.2272.40.1.1.2.1.2
.1.3.6.1.4.1.2272.40.1.1.2.1.3
.1.3.6.1.4.1.2272.40.1.1.2.1.4
.1.3.6.1.4.1.2272.40.1.1.3
Enumeration
.1.3.6.1.4.1.2272.40.1.1.3.1
Enumeration
.1.3.6.1.4.1.2272.40.1.1.3.2
.1.3.6.1.4.1.2272.40.1.1.4
.1.3.6.1.4.1.2272.40.1.1.4.1
.1.3.6.1.4.1.2272.40.1.21
.1.3.6.1.4.1.2272.40.1.21.0
Dependencies (40) 5 direct · 35 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.2272.40.1.21.0.1
An rcMltConfigError trap indicates that one of the
ports in a multi-link trunk was connected to a remote
port that was not also configured as a trunk. The
trap indicates that the specified trunk has also been
automatically disabled.