BAY-STACK-LLDP-EXT-DOT3-MIB

All MIBs › BAY-STACK-LLDP-EXT-DOT3-MIB

Organization: Avaya Inc.

Last Updated: 2014-10-22

Category: Vendor: Avaya

Description: Extends LLDP with IEEE 802.3 TLVs for link speed, duplex, and power-via-MDI on Avaya/Nortel ERS.

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 BAY-STACK-LLDP-EXT-DOT3-MIB?

BAY-STACK-LLDP-EXT-DOT3-MIB is a Nortel/Avaya extension to the standard IEEE 802.3 LLDP extension MIB, adding vendor-specific handling of local and remote power-via-MDI (PoE) TLVs on BayStack ERS switches. It exposes local and remote power tables recording power type, source, priority, and requested/allocated power values for both the local switch port and the connected remote device. Its monitoring value is directly hardware-related: by tracking PSE allocated power versus PD requested power, an administrator can detect PoE power budget exhaustion or a connected device not receiving its requested power, which is a common cause of powered-device (e.g., phone or camera) failures. It explicitly depends on and extends the standard LLDP-EXT-DOT3 MIB. It is deployed on PoE-capable Avaya/Nortel ERS switches supporting phones, APs, and cameras over Ethernet. Engineers can download the BAY-STACK-LLDP-EXT-DOT3-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BAY-STACK-LLDP-EXT-DOT3-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

Avaya/Nortel BayStack Ethernet Routing Switch (ERS)
PoE-powered endpoint devices (phones, APs, cameras)

Monitoring Examples

An administrator would compare bsLldpXdot3LocPowerTable's bsLldpXdot3LocPSEAllocatedPowerValue against the remote device's requested value in bsLldpXdot3RemPowerTable's bsLldpXdot3RemPowerType/bsLldpXdot3RemPowerPriority entries to see if a connected PoE phone or camera is being under-powered. A mismatch between bsLldpXdot3LocPDRequestedPowerValue and the allocated power, flagged via bsLldpXDot3Notifications, would point to a power-budget shortfall on that switch.

What Can Be Monitored

PSE allocated power
PD requested power
local/remote power source
power priority
PoE power type

Imported Objects

From LLDP-EXT-DOT3-MIB

lldpXdot3LocPowerEntry	OBJECT-TYPE
lldpXdot3RemPowerEntry	OBJECT-TYPE

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SYNOPTICS-ROOT-MIB

bayStackMibs

OBJECT-IDENTITY

OIDs

OID symbolic	OID numeric	Type	Access	Description
bayStackLldpXDot3Mib	1.3.6.1.4.1.45.5.47			This MIB module is an extension to the standard LLDP-EXT-DOT3 MIB.
bsLldpXDot3Notifications	1.3.6.1.4.1.45.5.47.0
bsLldpXDot3Objects	1.3.6.1.4.1.45.5.47.1
bsLldpXdot3Config	1.3.6.1.4.1.45.5.47.1.1
bsLldpXdot3LocalData	1.3.6.1.4.1.45.5.47.1.2
bsLldpXdot3LocPowerTable	1.3.6.1.4.1.45.5.47.1.2.1		not-accessible	This table contains one row per port of PSE PoE information on the local system known to this agent.
bsLldpXdot3LocPowerEntry	1.3.6.1.4.1.45.5.47.1.2.1.1		not-accessible	Information about a particular port PoE information.
INT bsLldpXdot3LocPowerType	1.3.6.1.4.1.45.5.47.1.2.1.1.1	INTEGER	read-only	A GET attribute that returns whether the local system is a PSE or a PD and whether it is Type 1 or Type 2.
INT bsLldpXdot3LocPowerSource	1.3.6.1.4.1.45.5.47.1.2.1.1.2	INTEGER	read-only	A GET attribute indicating the PSE Power Sources of the local system. A PSE indicates whether it is being powered by a primary power source; a backup power source; or unknown. A value primaryPs(2) indicates that the device advertises its power source as primary. A value backupPs(3) indicates that the device advertises its power source as backup.
INT bsLldpXdot3LocPowerPriority	1.3.6.1.4.1.45.5.47.1.2.1.1.3	INTEGER	read-only	Reflects the PD power priority that is being advertised on this PSE port. If both locally configure priority and ldpXMedRemXPoEPDPowerPriority are available on this port, it is a matter of local policy which one takes precedence. This object reflects the active value on this port. If the priority is not configured or known by the PD, the value unknown(1) will be returned. A value critical(2) indicates that the device advertises its power Priority as critical, as per RFC 3621. A value high(3) indicates that the device advertises its power Priority as high, as per RFC 3621. A value low(4) indicates that the device advertises its power Priority as low, as per RFC 3621.
I32 bsLldpXdot3LocPDRequestedPowerValue	1.3.6.1.4.1.45.5.47.1.2.1.1.4	Integer32	read-only	A GET attribute that returns the PD requested power value. For a PSE, it is the power value that the PSE mirrors back to the remote system. This is the PD requested power value that was used by the PSE to compute the power it has currently allocated to the remote system. It is expressed in units of 0.1 watts.
I32 bsLldpXdot3LocPSEAllocatedPowerValue	1.3.6.1.4.1.45.5.47.1.2.1.1.5	Integer32	read-only	A GET attribute that returns the PSE allocated power value. For a PSE, it is the power value that the PSE has currently allocated to the remote system. The PSE allocated power value is the maximum input average power that the PSE wants the PD to ever draw under this allocation if it is accepted. It is expressed in units of 0.1 watts.
bsLldpXdot3RemoteData	1.3.6.1.4.1.45.5.47.1.3
bsLldpXdot3RemPowerTable	1.3.6.1.4.1.45.5.47.1.3.1		not-accessible	This table contains information about the PoE device type as advertised by the remote system.
bsLldpXdot3RemPowerEntry	1.3.6.1.4.1.45.5.47.1.3.1.1		not-accessible	Information about a particular port component.
INT bsLldpXdot3RemPowerType	1.3.6.1.4.1.45.5.47.1.3.1.1.1	INTEGER	read-only	A GET attribute that returns whether the remote system is a PSE or a PD and whether it is Type 1 or Type 2.
INT bsLldpXdot3RemPowerSource	1.3.6.1.4.1.45.5.47.1.3.1.1.2	INTEGER	read-only	A GET attribute that returns the power sources of the remote system. When the remote system is a PD, it indicates whether it is being powered by: a PSE and locall; locally only; by a PSE only; or unknown.
INT bsLldpXdot3RemPowerPriority	1.3.6.1.4.1.45.5.47.1.3.1.1.3	INTEGER	read-only	A GET operation returns the priority of the PD system received from the remote system. For a PD, this is the priority that the remote system has assigned to the PD.
I32 bsLldpXdot3RemPDRequestedPowerValue	1.3.6.1.4.1.45.5.47.1.3.1.1.4	Integer32	read-only	A GET attribute that for a PSE returs the the PD requested power value received from the remote system. It is expressed in units of 0.1 watts.
I32 bsLldpXdot3RemPSEAllocatedPowerValue	1.3.6.1.4.1.45.5.47.1.3.1.1.5	Integer32	read-only	A GET attribute that for a PSE returns the PSE allocated power value that was used by the remote system to compute the power value that it has currently requested from the PSE. It is expressed in units of 0.1 watts.

RFC description

Extends LLDP protocol with Power over Ethernet (PoE) information for Avaya network switches.

Start monitoring Avaya/Nortel BayStack Ethernet Routing Switch (ERS) (legacy) 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 BAY-STACK-LLDP-EXT-DOT3-MIB

What Is BAY-STACK-LLDP-EXT-DOT3-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description