BAY-STACK-PETH-EXT-MIB

All MIBs › BAY-STACK-PETH-EXT-MIB

Organization: Avaya

Last Updated: 2012--0-1-

Category: Hardware and Environment, Vendor: Avaya

Description: Extends Power over Ethernet (PoE) port power allocation and priority configuration 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-PETH-EXT-MIB?

BAY-STACK-PETH-EXT-MIB is an Avaya/Nortel Ethernet Routing Switch extension to standard Power over Ethernet management, adding per-port power-limit configuration and detailed measured electrical values. It exposes a table with configured power limits alongside measured voltage, current, and power draw per powered port, plus detailed and current fault status objects. This is a direct hardware health monitor: it lets an operator see whether a PoE port is drawing power within its configured limit or exhibiting a fault condition, which is critical for detecting overloaded power-sourcing-equipment ports or failing powered devices. It extends the standard POWER-ETHERNET-MIB defined in RFC 3621. It is deployed on PoE-enabled access switches powering IP phones, wireless access points, or cameras in enterprise wiring closets. Engineers can download the BAY-STACK-PETH-EXT-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BAY-STACK-PETH-EXT-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 Ethernet Routing Switches with PoE

Monitoring Examples

An administrator polls bspePethPsePortExtTable/bspePethPsePortExtEntry indexed by bspePethPsePortExtGroupIndex and bspePethPsePortExtIndex, comparing bspePethPsePortExtMeasuredPower against bspePethPsePortExtPowerLimit. A port whose bspePethPsePortExtDetailedStatus or bspePethPsePortExtCurrentStatus reports a fault while bspePethPsePortExtMeasuredCurrent spikes indicates an overloaded or shorting powered device that needs to be disconnected.

What Can Be Monitored

per-port power limit
measured voltage
measured current
measured power draw
detailed/fault status

Imported Objects

From IF-MIB

ifIndex

OBJECT-TYPE

From SNMPv2-SMI

Gauge32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SYNOPTICS-ROOT-MIB

bayStackMibs

OBJECT-IDENTITY

How to Use in IPNetwork Monitor

Example using bspePethPsePortExtMeasuredVoltage OID:

Select an Avaya/Nortel BayStack Ethernet Routing Switch (ERS) (legacy) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type bspePethPsePortExtMeasuredVoltage into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports the measured Port Voltage. When the port is not supplying power, the value will be 0. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Gauge32-type OID, Value bounds is the most useful condition here — trigger an alert if the value drifts significantly from its normal baseline (in decivolts), since an unexpected change often points to a real underlying issue. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
bayStackPethExtMib	1.3.6.1.4.1.45.5.8			BayStack Power Over Ethernet Extension MIB Copyright 2004-2011 Avaya All rights reserved. This Avaya SNMP Management Information Base Specification embodies Avaya's confidential and proprietary intellectual property. Avaya retains all title and ownership in the Specification, including any revisions. This Specification is supplied 'AS IS,' and Avaya makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.
bspeNotifications	1.3.6.1.4.1.45.5.8.0
NTF bspePethPsePortCurrentStatusNotification	1.3.6.1.4.1.45.5.8.0.1			This notification indicate Port Change Status and it will be sent on every status change.
NTF bspeIpPhonePowerLimitNotification	1.3.6.1.4.1.45.5.8.0.2			This notification indicates the dynamic change of the power limit for a port, due to the discovering of an IP phone. This notification type is generating only if bspeIpPhonePowerLimit object is applicable.
NTF bspeIpPhonePowerPriorityNotification	1.3.6.1.4.1.45.5.8.0.3			This notification indicates the dynamic change of the power priority for a port, due to the discovering of an IP phone. This notification type is generating only if bspeIpPhonePowerPriority object is applicable.
bspeObjects	1.3.6.1.4.1.45.5.8.1
bspePethPsePortExtTable	1.3.6.1.4.1.45.5.8.1.1		not-accessible	This table extends the pethPsePortTable.
bspePethPsePortExtEntry	1.3.6.1.4.1.45.5.8.1.1.1		not-accessible	An entry that extends pethPsePortEntry.
I32 bspePethPsePortExtGroupIndex	1.3.6.1.4.1.45.5.8.1.1.1.1	Integer32	not-accessible	This object is equal to the value of pethPsePortGroupIndex of the entry in the pethPsePortTable extended by this entry.
I32 bspePethPsePortExtIndex	1.3.6.1.4.1.45.5.8.1.1.1.2	Integer32	not-accessible	This object is equal to the value of pethPsePortIndex of the entry in the pethPsePortTable extended by this entry.
I32 bspePethPsePortExtPowerLimit	1.3.6.1.4.1.45.5.8.1.1.1.3	Integer32	read-write	DTE Power limit per port.
INT bspePethPsePortExtDetailedStatus	1.3.6.1.4.1.45.5.8.1.1.1.4	INTEGER	read-only	Port Status. Valid values for Harrier: 4,8,9,16. Valid values for CondorPoE: 1-16. The object bspePsePortExtDetailedStatus details the status of the port when pethPsePortDetectionStatus is either deliveringPower(3), fault(4), or otherFault(6). - When the value of pethPsePortDetectionStatus is deliveringPower(3), the value of bspePethPsePortExtDetailedStatus should be a value in the range 1-3 (detailes the discovery scheme that was used to detect the PD that is currently powered). - When the value of pethPsePortDetectionStatus is fault(4) or otherFault(6), the value of bspePethPsePortExtDetailedStatus should be some fault value in the range: 4-15. - When the value of pethPsePortDetectionStatus is not deliveringPower(3), fault(4), nor otherFault(6), then the value of bspePethPsePortExtDetailedStatus should be detectionStatus(16). A value of poweredResistiveDiscovery(1) indicates that a PD device was detected on this port using the IEEE 802.3af standard compliant Resistor signature discovery scheme. A value of poweredCapacitiveDiscovery(2) indicates that a PD device was detected on this port using the Capacitive detection scheme. A value of poweredCiscoLegacyDiscovery(3) indicates that a PD device was detected on this port using the CiscoIP detection scheme. A value of invalidPd(4) indicates that a non-PoE device has been detected; no power will be supplied. A value of overloadFault(5) indicates that the port has exceeded its port power limit. A value of underloadFault(6) indicates that the connected PD device needs less power than the port lower power limit. A value of uvovFault(7) indicates that an under-voltage / over-voltage fault has occured. A value of powerManaged(8) indicates that the port is discovered and ready to power up, except that the power manager has not decided to power it up yet. This could be because of a power up delay, or it could be because there is no power available. Port does not supply power in order to keep active higher priority ports. A value of limitOverloadFault(9) indicates that the connected PD device needs more power than the port power limit; no power will be supplied. A value of discoveryDisabled(10) indicates that the port is enabled, but no discovery method has been enabled. A value of unableToResetTps(11) indicates that the TPS2384 (PoE Subsystem) could not be reset. A value of unableToInitializeTps(12) indicates that the TPS2384 (PoE Subsystem) could not be initialized. A value of unitialized(13) indicates that port PoE settings have not beed initialized. A value of nonexistent(14) indicates the port doesn't exist. This is used for the last 24 ports on 24 port systems. A value of otherFault(15) indicates that other fault has occured. A value of detectionStatus(16) indicates that the value of pethPsePortDetectionStatus should be disabled(1), searching(2), or test(5).
G32 bspePethPsePortExtMeasuredVoltageEx	1.3.6.1.4.1.45.5.8.1.1.1.5	Gauge32	read-only	Measured Port Voltage. When the port is not supplying power, the value will be 0.
G32 bspePethPsePortExtMeasuredCurrent	1.3.6.1.4.1.45.5.8.1.1.1.6	Gauge32	read-only	Measured Port Current.
G32 bspePethPsePortExtMeasuredPower	1.3.6.1.4.1.45.5.8.1.1.1.7	Gauge32	read-only	Measured Port Power. This value may not exceed 1000 times the current value of bspePethPsePortExtPowerLimit.
INT bspePethPsePortExtCurrentStatus	1.3.6.1.4.1.45.5.8.1.1.1.8	INTEGER	read-only	Describes a current port status related to the power generation. The value ok(1) indicates neither an undercurrent nor an overcurrent condition was detected since the attribute was last cleared. The value underCurrent(2) indicates that the port current is below the minimal value. The value overCurrent(3) indicates that the port current exceeds the maximal value. The value both(4) indicates both underCurrent and overCurrent. This attribute is cleared through the bspePethPsePortExtCurrentStatusClear action.
INT bspePethPsePortExtCurrentStatusClear	1.3.6.1.4.1.45.5.8.1.1.1.9	INTEGER	read-write	Setting the value of this object to clear(1) clears the value of bspePethPsePortExtCurrentStatus, and enables the agent to update it. Read operation this value will be off(2).
bspePethMainPseExtTable	1.3.6.1.4.1.45.5.8.1.2		not-accessible	This table extends the pethMainPseTable.
bspePethMainPseExtEntry	1.3.6.1.4.1.45.5.8.1.2.1		not-accessible	An entry that extends pethMainPseEntry.
I32 bspePethMainPseExtGroupIndex	1.3.6.1.4.1.45.5.8.1.2.1.1	Integer32	not-accessible	This object is equal to the value of pethMainPseGroupIndex of the entry in the pethMainPseTable extended by this entry.
INT bspePethMainPseExtPowerPresent	1.3.6.1.4.1.45.5.8.1.2.1.2	INTEGER	read-only	Current Power Source Present. Available power sources are AC and DC. A value of acOnly(1) indicates that the only power supply is AC. A value of dcOnly(2) indicates that the only power supply is DC. A value of acDc(3) indicates that there are two power supplies; both AC and DC are supplying power.
INT bspePethMainPseExtDisconnectScheme	1.3.6.1.4.1.45.5.8.1.2.1.3	INTEGER	read-write	When a low power draw is detected on a port, power will be turned off on that port. As a detection mechanism it can be used either AC Disconnect or DC Disconnect. A value of acDisconnect(1): AC impedance is monitored on each port; DC supply will be turned off on a port with a too high value of AC impedance. A value of dcDisconnect(2): DC current is monitored on each port; DC supply will be turned off on a port with a too low value of DC current.
bspeScalars	1.3.6.1.4.1.45.5.8.1.3
I32 bspeIpPhonePowerLimit	1.3.6.1.4.1.45.5.8.1.3.1	Integer32	read-write	Global power limit for IP phones. This value, if valid, applies for an IP phone discovered on a port. A value of 0 means not applicable; bspePethPsePortExtPowerLimit object should be used instead.
INT bspeIpPhonePowerPriority	1.3.6.1.4.1.45.5.8.1.3.2	INTEGER	read-write	Global power priority for IP phones. This object controls the priority of a port that connects an IP phone device. If the value is notApplicable(4), pethPsePortPowerPriority object should be used instead.
INT bspePoEPowerMode	1.3.6.1.4.1.45.5.8.1.3.3	INTEGER	read-write	Power over Ethernet Power Mode comfiguration: lowPowerBudget (1) Set PoE Low power budget and fanless mode. highPowerBudget (2) Set PoE High power budget and normal fans Mode.

RFC description

Extends Power over Ethernet (PoE) management on BayStack switches with power monitoring and port configuration.

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-PETH-EXT-MIB