BAY-STACK-PETH-EXT-MIB
AI MIB Summary
The BAY-STACK-PETH-EXT-MIB extends standard Power over Ethernet (PoE) management capabilities for Avaya BayStack switches, enabling SNMP-based monitoring of per-port power consumption, available power budgets, and PoE status states. This module facilitates granular control and fault isolation for powered devices by exposing vendor-specific extensions to the IEEE 802.3af/at power delivery metrics.
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.
Main OID:
bayStackPethExtMib.bayStackMibs.8
27
Objects
Active
Status
3
Dependencies
Imported Objects
Objects
27 total| Object Name |
|---|
bayStackPethExtMibBayStack 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. MODULE-IDENTITY .bayStackMibs.8 |
IMPORTSBayStack 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. Unknown .bayStackMibs.8 |
bspeNotifications OBJECT IDENTIFIER .bayStackMibs.8.0 |
bspePethPsePortCurrentStatusNotificationThis notification indicate Port Change Status and
it will be sent on every status change. NOTIFICATION-TYPE .bayStackMibs.8.0.1 |
bspeIpPhonePowerLimitNotificationThis 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. NOTIFICATION-TYPE .bayStackMibs.8.0.2 |
bspeIpPhonePowerPriorityNotificationThis 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. NOTIFICATION-TYPE .bayStackMibs.8.0.3 |
bspeObjects OBJECT IDENTIFIER .bayStackMibs.8.1 |
bspePethPsePortExtTableThis table extends the pethPsePortTable. SEQUENCE OF BspePethPsePortExtEntry .bayStackMibs.8.1.1 |
bspePethPsePortExtEntryAn entry that extends pethPsePortEntry. BspePethPsePortExtEntry .bayStackMibs.8.1.1.1 |
bspePethPsePortExtGroupIndexThis object is equal to the value of pethPsePortGroupIndex
of the entry in the pethPsePortTable extended by this entry. Integer32 .bayStackMibs.8.1.1.1.1 |
bspePethPsePortExtIndexThis object is equal to the value of pethPsePortIndex of the
entry in the pethPsePortTable extended by this entry. Integer32 .bayStackMibs.8.1.1.1.2 |
bspePethPsePortExtPowerLimitDTE Power limit per port.rw Integer32 .bayStackMibs.8.1.1.1.3 |
bspePethPsePortExtDetailedStatusPort 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).ro Enumeration .bayStackMibs.8.1.1.1.4 |
bspePethPsePortExtMeasuredVoltageMeasured Port Voltage. When the port is not supplying
power, the value will be 0.ro Gauge32 (0|400..580) UNITS "decivolts" .bayStackMibs.8.1.1.1.5 |
bspePethPsePortExtMeasuredCurrentMeasured Port Current.ro Gauge32 .bayStackMibs.8.1.1.1.6 |
bspePethPsePortExtMeasuredPowerMeasured Port Power. This value may not exceed 1000 times the
current value of bspePethPsePortExtPowerLimit.ro Gauge32 .bayStackMibs.8.1.1.1.7 |
bspePethPsePortExtCurrentStatusDescribes 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.ro Enumeration .bayStackMibs.8.1.1.1.8 |
bspePethPsePortExtCurrentStatusClearSetting 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).rw Enumeration .bayStackMibs.8.1.1.1.9 |
bspePethMainPseExtTableThis table extends the pethMainPseTable. SEQUENCE OF BspePethMainPseExtEntry .bayStackMibs.8.1.2 |
bspePethMainPseExtEntryAn entry that extends pethMainPseEntry. BspePethMainPseExtEntry .bayStackMibs.8.1.2.1 |
bspePethMainPseExtGroupIndexThis object is equal to the value of pethMainPseGroupIndex
of the entry in the pethMainPseTable extended by this entry. Integer32 .bayStackMibs.8.1.2.1.1 |
bspePethMainPseExtPowerPresentCurrent 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.ro Enumeration .bayStackMibs.8.1.2.1.2 |
bspePethMainPseExtDisconnectSchemeWhen 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.rw Enumeration .bayStackMibs.8.1.2.1.3 |
bspeScalars OBJECT IDENTIFIER .bayStackMibs.8.1.3 |
bspeIpPhonePowerLimitGlobal 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.rw Integer32 (0|3..32) UNITS "watts" .bayStackMibs.8.1.3.1 |
bspeIpPhonePowerPriorityGlobal 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.rw Enumeration .bayStackMibs.8.1.3.2 |
bspePoEPowerModePower 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.rw Enumeration .bayStackMibs.8.1.3.3 |