BROADCOM-POWER-ETHERNET-MIB

All MIBs › BROADCOM-POWER-ETHERNET-MIB

Organization: Netgear

Last Updated: 2007-05-23

Description: Broadcom/Netgear augmentation of the standard POWER-ETHERNET-MIB exposing additional PoE PSE hardware details not covered by the base MIB on Netgear managed switches

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 BROADCOM-POWER-ETHERNET-MIB?

BROADCOM-POWER-ETHERNET-MIB is a Broadcom/Netgear vendor augmentation of the standard IETF POWER-ETHERNET-MIB, adding hardware-specific Power-over-Ethernet (PoE) Power Source Equipment (PSE) details available on Netgear managed switches that the base standard MIB does not represent. Although no explicit object list is available here, by definition such an augmentation table exposes additional per-port PSE hardware attributes, such as detected power class, actual power draw, or chip-level PSE fault/status, alongside the standard PoE objects. Its monitoring value is hardware status: identifying per-port PoE power delivery faults, over-current or over-temperature conditions on the PSE hardware, and confirming powered devices (IP phones, APs, cameras) are receiving expected power. It explicitly augments POWER-ETHERNET-MIB (RFC 3621) and must be read jointly with that standard MIB's port table via the shared index. Deployment context is Netgear/Broadcom-based managed PoE switches in enterprise wiring closets powering IP phones, wireless APs, and IP cameras, where BROADCOM-POWER-ETHERNET-MIB SNMP monitoring catches per-port PSE faults the base standard MIB alone would miss.

IPNetwork Monitor allows you to monitor SNMP objects defined in BROADCOM-POWER-ETHERNET-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

Netgear managed PoE switch (Broadcom PSE hardware)

Monitoring Examples

An admin would join the augmentation entries to the standard pethPsePortTable by port index to read additional Broadcom-specific PSE status fields alongside pethPsePortDetectionStatus, catching PoE faults not visible in the base MIB alone. A port reporting an over-current or hardware fault flag in this extension while the standard MIB still shows 'delivering power' would reveal an imminent PoE failure before a device drops offline. Monitoring extended power draw per port helps plan PoE budget allocation across a switch stack.

What Can Be Monitored

per-port PoE hardware fault status
extended PSE power draw
PoE detection/classification detail
PSE chip-level status not in the base standard MIB

Imported Objects

From Netgear-MIB

ng7000managedswitch

OBJECT-IDENTITY

From POWER-ETHERNET-MIB

pethMainPseEntry	OBJECT-TYPE
pethPsePortEntry	OBJECT-TYPE

From SNMPv2-SMI

Gauge32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
fastPathpowerEthernetMIB	1.3.6.1.4.1.4526.10.15			This MIB Augments the POWER-ETHERNET-MIB created by the IETF Ethernet Interfaces and Hub MIB Working Group for managing Power Source Equipment (PSE). The objects in this MIB are intended to provide additional objects for reporting information available to the hardware on this platform which are not represented in the draft MIB.
agentPethObjects	1.3.6.1.4.1.4526.10.15.1
agentPethPsePortTable	1.3.6.1.4.1.4526.10.15.1.1		not-accessible	A table of per-port information and configuration objects relating to the power status of each port.
agentPethPsePortEntry	1.3.6.1.4.1.4526.10.15.1.1.1		not-accessible	A collection of objects providing additional power information and control parameters for the specified port.
G32 agentPethPowerLimit	1.3.6.1.4.1.4526.10.15.1.1.1.1	Gauge32	read-write	The configured maximum power this port can provide to an attached device measured in Milliwatts.
G32 agentPethOutputPower	1.3.6.1.4.1.4526.10.15.1.1.1.2	Gauge32	read-only	The power this port is supplying to an attached device measured in Milliwatts.
G32 agentPethOutputCurrent	1.3.6.1.4.1.4526.10.15.1.1.1.3	Gauge32	read-only	The current this port is supplying to an attached device measured in Milliamps.
G32 agentPethOutputVolts	1.3.6.1.4.1.4526.10.15.1.1.1.4	Gauge32	read-only	The voltage this port is supplying to an attached device measured in millivolts.
G32 agentPethTemperature	1.3.6.1.4.1.4526.10.15.1.1.1.5	Gauge32	read-only	The temperature measured at this port of the PoE Controller. It is measured in degree celcius.
INT agentPethPowerLimitType	1.3.6.1.4.1.4526.10.15.1.1.1.6	INTEGER	read-write	Describes or controls the maximum power that a port can deliver A value of dot3af(1) means that the port power limit is as per the dot3af class of the PD attached. A value of user(2) means that the port power limit is equal to the value specified by agentPethPowerLimit
T/F agentPethHighPowerEnable	1.3.6.1.4.1.4526.10.15.1.1.1.7	TruthValue	read-write	true (1) The PSE port can deliver power up to 32Watts. false(2) The PSE port can deliver power up to 18Watts
INT agentPethPowerDetectionType	1.3.6.1.4.1.4526.10.15.1.1.1.8	INTEGER	read-write	Describes PD detection mechanism performed by the PSE port. A value of none(0) means no detection is done. A value of legacy(1) means only legacy capacitive detection scheme is used. A value of 4ptdot3afonly(2) means that IEEE 802.3af 4point detection scheme is used. A value of 4ptdot3afandlegacy(3)means that IEEE 802.3af 4point detection scheme is used and when that fails to detect a connected PD, legacity capacitive detection is used. A value of 2ptdot3afonly(4) means that IEEE 802.3af 2point detection scheme is used. A value of 2ptdot3afandlegacy(5)means that IEEE 802.3af 2point detection scheme is used and when that fails to detect a connected PD, legacity capacitive detection is used. The value 'none' can not be forcibly set by the administrator.
INT agentPethFaultStatus	1.3.6.1.4.1.4526.10.15.1.1.1.9	INTEGER	read-only	Describes the error description when the pse port is in fault status. A value of none(0) specifies that the pse port is not in any error state. A value of mpsAbsent(1) specifies that the pse port has detected and absence of main power supply. A value of short(2) specifies that the pse port has detected a short circuit condition. A value of overload(3) specifies that the pd connected to the pse port had tried to draw more power than permissible by the hardware. A value of powerDenied(4) specifies that the pse port has been denied power because of shortage of power or due to administrative action.
INT agentPethPortReset	1.3.6.1.4.1.4526.10.15.1.1.1.10	INTEGER	read-write	A value of reset(1) is used to move the pse port dot3af state to idle. A read on this object will always return the value none(0). The value none(0) can not be forcibly set by the administrtor.
INT agentPethPowerUpMode	1.3.6.1.4.1.4526.10.15.1.1.1.11	INTEGER	read-write	Describes the power up mode used by the PSE Port. A value of 802dot3af(0) means port is powered in IEEE 802.3af mode. A value of high-inrush(1) means port is powered used high-inrush current, used by legacy PD's A value of pre-802dot3at(2) means port is powered in IEEE 802.3af mode initially, switched to high-power IEEE 802.3at mode before 75msec. This mode needs to be used if PSE is NOT performing Layer 2 Classification Or PSE is performing 2-Event Layer 1 Classification. A value of 802dot3at(3) means is port is powered in IEEE 802.3at mode. i.e. if class detected by PSE is not class4 then PSE port will not power up the PD.
INT agentPethClassificationMode	1.3.6.1.4.1.4526.10.15.1.1.1.12	INTEGER	read-write	Describes the classification mode used by the PSE Port. A value of bypass(0) means port is not performing classification. A value of standard(1) means port is performing classification as per IEEE 802.3af/802.3at .
agentPethMainPseObjects	1.3.6.1.4.1.4526.10.15.1.2
agentPethMainPseTable	1.3.6.1.4.1.4526.10.15.1.2.1		not-accessible	A table of objects that display and control attributes of the main power source in a PSE device. Ethernet switches are one example of boxes that would support these objects. Values of all read-write objects in this table are persistent at restart/reboot.
agentPethMainPseEntry	1.3.6.1.4.1.4526.10.15.1.2.1.1		not-accessible	A set of objects that display and control the Main power of a PSE.
T/F agentPethMainPseLegacy	1.3.6.1.4.1.4526.10.15.1.2.1.1.1	TruthValue	read-write	Enable/Disable Legacy device detection. The value true(1) means legacy devices are detected; the value false(2) means legacy devices are not detected.
agentPethPseTable	1.3.6.1.4.1.4526.10.15.1.3		not-accessible	A table of per-unit information and configuration objects relating to the power configurtion for the entire pse unit.
agentPethPseEntry	1.3.6.1.4.1.4526.10.15.1.3.1		not-accessible	A collection of objects providing additional power information and control parameters for the specified pse unit.
INT agentPethPsePowerManagementMode	1.3.6.1.4.1.4526.10.15.1.3.1.1	INTEGER	read-write	Describes or controls the power management algorithm used by the pse to deliver power to the requesting PDsthat a pds.
T/F agentPethPseAutoResetEnable	1.3.6.1.4.1.4526.10.15.1.3.1.2	TruthValue	read-write	true (1) The PSE port is reset with out administrator intervention whenver a fault condition occurs. false(2) Administrator has to reset the pse port whenver a fault condition is detected.

RFC description

Augments Power Ethernet MIB with additional PSE power management and port monitoring for PoE devices.

Start monitoring Netgear PoE 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 BROADCOM-POWER-ETHERNET-MIB

What Is BROADCOM-POWER-ETHERNET-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description