BN-IF-EXTENSIONS-MIB

All MIBs › BN-IF-EXTENSIONS-MIB

Organization: Avaya

Last Updated: 2013-07-26

Category: Network Interfaces

Description: Extends standard interface MIB objects for Bay Networks router interface management.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is BN-IF-EXTENSIONS-MIB?

BN-IF-EXTENSIONS-MIB is a Bay Networks (later Nortel/Avaya) vendor MIB that augments the standard interfaces MIB with hardware-specific details for physical ports on Bay Networks routing/switching platforms. It adds slot/port location identifiers, shared-port indication, active component selection, Power-over-Ethernet powered-device detection type, and extended auto-negotiation/hardware advertisement capabilities per interface. Its monitoring purpose is hardware status of the physical port layer: confirming a port's location (slot/port), whether it shares hardware with another port, its PoE powered-device detection state, and negotiated versus advertised link capabilities, which helps diagnose link speed/duplex mismatches or PoE detection failures. It explicitly extends IETF's standard IF-MIB, so it must be read together with ifTable/ifXTable entries via the shared ifIndex. Deployment context is Bay Networks/Avaya enterprise routers and switches where physical-layer port diagnostics beyond the generic interface MIB are needed, typically starting with a BN-IF-EXTENSIONS-MIB download to load into the management station.

IPNetwork Monitor allows you to monitor SNMP objects defined in BN-IF-EXTENSIONS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Bay Networks / Nortel / Avaya router or switch

Monitoring Examples

An operator would join bnIfExtnTable/bnIfExtnEntry to the standard ifTable via ifIndex, reading bnIfExtnSlot and bnIfExtnPort to locate a problem interface physically, then checking bnIfExtnPoweredDeviceDetectType to confirm PoE detection is working for an attached phone or AP. Comparing bnIfExtnAutoNegotiationExtAdv against bnIfExtnExtHwAdvCapability reveals whether the port is advertising less than its hardware supports, explaining an unexpectedly low negotiated link speed. A port flagged bnIfExtnIsPortShared unexpectedly true could explain unexplained contention between two logical ports.

What Can Be Monitored

port slot/port location
shared port hardware indication
active port component
PoE powered-device detection type
auto-negotiation advertised vs hardware capability

Imported Objects

From S5-ROOT-MIB

s5IfExt

OBJECT-IDENTITY

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
bnIfExtensions	1.3.6.1.4.1.45.1.6.15.1
bnIfExtnTable	1.3.6.1.4.1.45.1.6.15.1.1		not-accessible	A list of interface entries. The number of entries is given by the value of ifNumber.
bnIfExtnEntry	1.3.6.1.4.1.45.1.6.15.1.1.1		not-accessible	An interface entry containing objects at the subnetwork layer and below for a particular interface.
I32 bnIfExtnIndex	1.3.6.1.4.1.45.1.6.15.1.1.1.1	Integer32	read-only	A unique value for each interface corresponding to the ifIndex value for the same interface.
I32 bnIfExtnSlot	1.3.6.1.4.1.45.1.6.15.1.1.1.2	Integer32	read-only	The unit number associated with this particular interface.
I32 bnIfExtnPort	1.3.6.1.4.1.45.1.6.15.1.1.1.3	Integer32	read-only	The port number within a unit or slot.
INT bnIfExtnIsPortShared	1.3.6.1.4.1.45.1.6.15.1.1.1.4	INTEGER	read-only	Indicates whether the port is considered a 'shared' port or not. Multiple physical ports that are logically represented as a single port are considered shared. Only one of the physical ports is active at any given time.
INT bnIfExtnPortActiveComponent	1.3.6.1.4.1.45.1.6.15.1.1.1.5	INTEGER	read-write	Indicates which physical port component is currently active for ports that are 'shared'. The ability to set this object and thus specify the active physical component of a single logical port is implmentation dependent. This object will be read-only is this capability is not supported.
INT bnIfExtnPoweredDeviceDetectType	1.3.6.1.4.1.45.1.6.15.1.1.1.6	INTEGER	read-write	This object is used to specify the mechanism used to detect powered ethernet devices attached to a powered ethernet port. This object should only be instantiated for values of ifIndex that represent ports that support powered ethernet.
BIT bnIfExtnAutoNegotiationExtAdv	1.3.6.1.4.1.45.1.6.15.1.1.1.7	Bits	read-write	This object is used to specify the port speed and duplex abilities to be advertised during link negotiation. bit 0 - 10 half duplex advertised bit 1 - 10 full duplex advertised bit 2 - 100 half duplex advertised bit 3 - 100 full duplex advertised bit 4 - 1000 half duplex advertised bit 5 - 1000 full duplex advertised bit 6 - PAUSE frame support advertised bit 7 - Asymmetric PAUSE frame support advertised bit 8 - 10000 full duplex advertised bit 9 - 40000 full duplex advertised The abilities specified in this object are only used when auto-negotiation is enabled on the port. If all bits in this object are disabled, and auto-negotiation is enabled on the port, then the physical link process on the port will be disabled. Any change in the value of this bit map will force the PHY to restart the auto-negotiation process. This will have the same effect as physically unplugging and reattaching the cable plant attached to this port. Only capabilities present in the hardware as indicated by bnIfExtnExtHwAdvCapability can be advertised. The default value for this object will be the value of the associated instance of bnIfExtnExtHwAdvCapability.
BIT bnIfExtnExtHwAdvCapability	1.3.6.1.4.1.45.1.6.15.1.1.1.8	Bits	read-only	This object indicates the port speed and duplex capabilities that hardware can actually support on a port, and which may be advertised by the port using auto-negotiation. Bit 7 tells if a port supports pause frame capabilities (for full-duplex links) as a part of the advertisement. bit 0 - 10 half duplex advertisements bit 1 - 10 full duplex advertisements bit 2 - 100 half duplex advertisements bit 3 - 100 full duplex advertisements bit 4 - 1000 half duplex advertisements bit 5 - 1000 full duplex advertisements bit 6 - PAUSE frame support advertisements bit 7 - Asymmetric PAUSE frame support advertisements bit 8 - 10000 full duplex advertisements bit 9 - 40000 full duplex advertisements If auto negotiation is not supported by the port hardware, then all bits will reflect a value of zero.
bnIfExtensionsMib	1.3.6.1.4.1.45.1.6.15.2			Interface Extension MIB Copyright 1997 - 2013 Avaya, Inc. All rights reserved. This Bay Networks SNMP Management Information Base Specification (Specification) embodies Bay Networks' confidential and proprietary intellectual property. Bay Networks retains all title and ownership in the Specification, including any revisions. This Specification is supplied 'AS IS,' and Bay Networks makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.

RFC description

Avaya interface extension MIB providing additional attributes for network interfaces including auto-negotiation and power detection capabilities.

Start monitoring Bay Networks/Nortel/Avaya routers and switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download BN-IF-EXTENSIONS-MIB

What Is BN-IF-EXTENSIONS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description