BAY-STACK-DHCP-SNOOPING-MIB
This MIB module is used for DHCP snooping configuration
settings in Nortel's software and products.
- Source file
BAY-STACK-DHCP-SNOOPING-MIB- Last revised
- Identity
bayStackDhcpSnoopingMib- Base OID
1.3.6.1.4.1.45.5.17
Imported Objects
| IF-MIB | InterfaceIndex |
| INET-ADDRESS-MIB | InetAddress InetAddressType InetPortNumber |
| Q-BRIDGE-MIB | VlanIndex |
| SNMPv2-SMI | Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | DateAndTime DisplayString MacAddress RowStatus TruthValue |
| SYNOPTICS-ROOT-MIB | bayStackMibs |
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 'BAY-STACK-DHCP-SNOOPING-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'BAY-STACK-DHCP-SNOOPING-MIB::bayStackDhcpSnoopingMib'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'BAY-STACK-DHCP-SNOOPING-MIB' -M '/opt/observium/mibs/nortel:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'BAY-STACK-DHCP-SNOOPING-MIB::bayStackDhcpSnoopingMib'
Objects (45)
Showing 45 of 45 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.45.5.17 |
||
.1.3.6.1.4.1.45.5.17.0 |
||
.1.3.6.1.4.1.45.5.17.1 |
||
.1.3.6.1.4.1.45.5.17.1.1 |
||
.1.3.6.1.4.1.45.5.17.1.1.1 |
||
.1.3.6.1.4.1.45.5.17.1.1.2 |
||
.1.3.6.1.4.1.45.5.17.1.2 |
||
.1.3.6.1.4.1.45.5.17.1.2.1 |
||
.1.3.6.1.4.1.45.5.17.1.2.1.1 |
||
.1.3.6.1.4.1.45.5.17.1.2.1.2 |
||
.1.3.6.1.4.1.45.5.17.1.2.1.3 |
||
|
Bits
|
.1.3.6.1.4.1.45.5.17.1.2.1.4 |
|
.1.3.6.1.4.1.45.5.17.1.3 |
||
.1.3.6.1.4.1.45.5.17.1.3.1 |
||
.1.3.6.1.4.1.45.5.17.1.3.1.1 |
||
.1.3.6.1.4.1.45.5.17.1.3.1.2 |
||
.1.3.6.1.4.1.45.5.17.1.3.1.3 |
||
.1.3.6.1.4.1.45.5.17.1.4 |
||
.1.3.6.1.4.1.45.5.17.1.4.1 |
||
.1.3.6.1.4.1.45.5.17.1.4.1.1 |
||
.1.3.6.1.4.1.45.5.17.1.4.1.2 |
||
.1.3.6.1.4.1.45.5.17.1.4.1.3 |
||
.1.3.6.1.4.1.45.5.17.1.4.1.4 |
||
.1.3.6.1.4.1.45.5.17.1.4.1.5 |
||
|
secondsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.45.5.17.1.4.1.6 |
|
.1.3.6.1.4.1.45.5.17.1.4.1.7 |
||
|
secondsSNMPv2-SMIUnsigned32
|
.1.3.6.1.4.1.45.5.17.1.4.1.8 |
|
|
Enumeration
|
.1.3.6.1.4.1.45.5.17.1.4.1.9 |
|
.1.3.6.1.4.1.45.5.17.1.5 |
||
|
Unsigned32
|
.1.3.6.1.4.1.45.5.17.1.5.1 |
|
|
Enumeration
|
.1.3.6.1.4.1.45.5.17.1.5.2 |
|
.1.3.6.1.4.1.45.5.17.1.5.3 |
||
.1.3.6.1.4.1.45.5.17.1.5.4 |
||
.1.3.6.1.4.1.45.5.17.1.5.5 |
||
.1.3.6.1.4.1.45.5.17.1.6 |
||
.1.3.6.1.4.1.45.5.17.1.6.1 |
||
.1.3.6.1.4.1.45.5.17.1.6.10 |
||
.1.3.6.1.4.1.45.5.17.1.6.2 |
||
.1.3.6.1.4.1.45.5.17.1.6.3 |
||
|
OctetString
|
.1.3.6.1.4.1.45.5.17.1.6.4 |
|
.1.3.6.1.4.1.45.5.17.1.6.5 |
||
.1.3.6.1.4.1.45.5.17.1.6.6 |
||
|
Integer32
|
.1.3.6.1.4.1.45.5.17.1.6.7 |
|
.1.3.6.1.4.1.45.5.17.1.6.8 |
||
.1.3.6.1.4.1.45.5.17.1.6.9 |
Dependencies (19) 6 direct · 13 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
Dependency-first compile order
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- INET-ADDRESS-MIBrfc
- BRIDGE-MIBrfc
- P-BRIDGE-MIBrfc
- RMON-MIBrfc
- RFC-1212rfc
- RFC1155-SMIrfc
- RFC1213-MIBrfc
- RFC1271-MIBrfc
- TOKEN-RING-RMON-MIBrfc
- RMON2-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- Q-BRIDGE-MIBrfc
- SYNOPTICS-ROOT-MIBnortel
- BAY-STACK-DHCP-SNOOPING-MIBnortelselected
Notifications / Traps (23)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.45.5.17.0.1 |
This notification is generated when an attempt is made to add a new
DHCP binding entry when the binding table is full. The value of bsDhcpSnoopingNotificationClientMACAddr gives the MAC address that could not be added to the binding table. This notification also indicates that additional untrusted DHCP packets will not be added to the binding table and will be dropped. |
|
.1.3.6.1.4.1.45.5.17.0.10 |
This notification is generated after successfully saving the DHCP
snooping binding table to a TFTP server external file. |
|
.1.3.6.1.4.1.45.5.17.0.11 |
This notification is generated after unsuccessfully saving the DHCP
snooping binding table to a USB drive external file. |
|
.1.3.6.1.4.1.45.5.17.0.12 |
This notification is generated after unsuccessfully saving the DHCP
snooping binding table to a TFTP server external file. |
|
.1.3.6.1.4.1.45.5.17.0.13 |
This notification is generated after successfully restoring the DHCP
snooping binding table from a USB drive external file. |
|
.1.3.6.1.4.1.45.5.17.0.14 |
This notification is generated after successfully restoring the DHCP
snooping binding table from a TFTP server external file. |
|
.1.3.6.1.4.1.45.5.17.0.15 |
This notification is generated after unsuccessfully restoring the DHCP
snooping binding table from a USB drive external file. |
|
.1.3.6.1.4.1.45.5.17.0.16 |
This notification is generated after unsuccessfully restoring the DHCP
snooping binding table from a TFTP server external file. |
|
.1.3.6.1.4.1.45.5.17.0.17 |
This notification is generated when a DHCP snooping binding entry is
not restored from an external file because VLAN requirements are not met: VLAN must exist, VLAN must be DHCP snooping enabled, binding entry unit/port must be a part of the VLAN. |
|
.1.3.6.1.4.1.45.5.17.0.18 |
This notification is generated after successfully saving the DHCP
snooping binding table to a SFTP server external file. |
|
.1.3.6.1.4.1.45.5.17.0.19 |
This notification is generated after unsuccessfully saving the DHCP
snooping binding table to a SFTP server external file. |
|
.1.3.6.1.4.1.45.5.17.0.2 |
This notification is generated when a DHCP packet is dropped.
|
|
.1.3.6.1.4.1.45.5.17.0.20 |
This notification is generated after successfully restoring the DHCP
snooping binding table from a SFTP server external file. |
|
.1.3.6.1.4.1.45.5.17.0.21 |
This notification is generated after unsuccessfully restoring the DHCP
snooping binding table from a SFTP server external file. |
|
.1.3.6.1.4.1.45.5.17.0.22 |
This notification is generated when a DHCP snooping binding entry is
not restored from an external file on a trusted interface. |
|
.1.3.6.1.4.1.45.5.17.0.23 |
This notification is generated when a DHCP packet is dropped because
a static entry with the same MAC address was found in the binding table. |
|
.1.3.6.1.4.1.45.5.17.0.3 |
This notification is generated when the DHCP Option 82 information
could not be added to a DHCP packet because the resulting packet would be too long. |
|
.1.3.6.1.4.1.45.5.17.0.4 |
This notification is generated when a DHCP snooping binding entry is
not restored from an external file due to a MAC conflict. |
|
.1.3.6.1.4.1.45.5.17.0.5 |
This notification is generated when a DHCP snooping binding entry is
not restored from an external file due to an unexisting interface. |
|
.1.3.6.1.4.1.45.5.17.0.6 |
This notification is generated when a DHCP snooping binding entry is
not restored from an external file because the client lease expired. |
|
.1.3.6.1.4.1.45.5.17.0.7 |
This notification is generated when a DHCP snooping binding entry is
not restored from an external file due to a parsing failure. |
|
.1.3.6.1.4.1.45.5.17.0.8 |
This notification is generated when enabling the DHCP snooping external
saves feature without synchronizing the switch to a NTP server. |
|
.1.3.6.1.4.1.45.5.17.0.9 |
This notification is generated after successfully saving the DHCP
snooping binding table to a USB drive external file. |