PEA-EQUIPMENT

All MIBs › PEA-EQUIPMENT

Organization: Ericsson Danmark A/S

Last Updated: 2005-08-16

Category: DSL and Broadband

Description: Provides physical equipment inventory, slot, and module status management for Ericsson IP DSLAM chassis.

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 PEA-EQUIPMENT?

PEA-EQUIPMENT is a vendor-specific MIB from Ericsson covering the physical equipment inventory and hardware health of its IP DSLAM chassis. It exposes objects for system identity, software versions (boot and active/passive images), configuration version, and detailed hardware health metrics. This MIB is explicitly geared toward monitoring device hardware and software status: it reports CPU/processor load, free memory (both as a percentage and in bytes), memory buffer usage, temperature control state and readings, and fan status, alongside active/passive software image tracking for firmware management. As a proprietary equipment MIB it is largely self-contained but is used together with sibling Ericsson PEA-series MIBs on the same platform for a complete device picture. It is typically deployed in DSL access network monitoring systems to track the physical health and software state of DSLAM chassis in the field. Engineers can download the PEA-EQUIPMENT file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in PEA-EQUIPMENT. 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

Ericsson IP DSLAM chassis

Monitoring Examples

An NMS would poll processorLoad and memFree/memFreeBytes periodically to detect CPU or memory exhaustion on the DSLAM control processor, and check tempValue against tempControlState to catch overheating before it triggers thermal shutdown. Monitoring greenFanStatus reveals cooling fan failures that could lead to equipment damage, while comparing activeSwInfo and passiveSwInfo confirms which firmware image is running versus staged for failover. A sudden rise in memBuffersUsed alongside falling memFree would signal a memory leak requiring a reboot or software fix.

What Can Be Monitored

CPU/processor load
free memory (percent and bytes)
memory buffer usage
temperature reading and control state
fan status
active/passive software version

Imported Objects

From IF-MIB

InterfaceIndex
ifIndex	OBJECT-TYPE

From PEA-SMI

pea	OBJECT-IDENTITY

From PEM-STANDARD

eventTime	OBJECT-TYPE
eventTypePem	OBJECT-TYPE
managedObjectClass	OBJECT-TYPE
managedObjectInstance	OBJECT-TYPE
perceivedSeverity	OBJECT-TYPE
probableCause	OBJECT-TYPE
sequenceNumber	OBJECT-TYPE

From SNMPv2-CONF

NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
MacAddress
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using tempControlState OID:

Select an Ericsson IP DSLAM chassis (system identity/hardware health) 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 tempControlState into the Find box to locate it in the OID tree, then select it and click OK. The state of the temperature control can be: 0 - Low 1 - Normal 2 - High 3 - TooHigh. 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 an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value is anything other than 'normal', since that indicates the condition this object reports has changed to one worth investigating. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
peaEquipment	1.3.6.1.4.1.193.72.600.1			The public ethernet access software supports a number of standard and proprietary MIBs. This MIB module defines objects for reading/writing common equipment information.
commonObjects	1.3.6.1.4.1.193.72.600.1.1
versions	1.3.6.1.4.1.193.72.600.1.1.1
STR sysId	1.3.6.1.4.1.193.72.600.1.1.1.1	DisplayString	read-only	This value includes the full name and version identification of the node software.
STR bootSwId	1.3.6.1.4.1.193.72.600.1.1.1.2	DisplayString	read-only	This value includes the full name and version identification of the BOOT software.
U32 cfgVer	1.3.6.1.4.1.193.72.600.1.1.1.3	Unsigned32	read-write	The CfgVer will initially be zero, but is set to the version number defined in the configuration file received from the tftp server at system start-up. The management system may use this version number to verify that the unit contains the correct configuration parameter values. The management system may update the version number when configuration parameters are modified.
STR activeSwInfo	1.3.6.1.4.1.193.72.600.1.1.1.4	DisplayString	read-only	This value represents the software version of the active software part of the node.
STR passiveSwInfo	1.3.6.1.4.1.193.72.600.1.1.1.5	DisplayString	read-only	This value represents the software version of the passive software part of the node.
mainProcessor	1.3.6.1.4.1.193.72.600.1.1.2
U32 processorLoad	1.3.6.1.4.1.193.72.600.1.1.2.1	Unsigned32	read-only	The percentage of time that the main processor was not idle. Average over 10 seconds. (almost like hrProcessorLoad in RFC1514).
U32 memFree	1.3.6.1.4.1.193.72.600.1.1.2.2	Unsigned32	read-only	The amount of free memory on main processor in percent.
U32 memFreeBytes	1.3.6.1.4.1.193.72.600.1.1.2.3	Unsigned32	read-only	The amount of free memory on main processor in bytes.
U32 memBuffersUsed	1.3.6.1.4.1.193.72.600.1.1.2.4	Unsigned32	read-only	The total number of memory buffers currently used (Ethernet, ATM & local IP-stack).
temperature	1.3.6.1.4.1.193.72.600.1.1.3
INT tempControlStateEx	1.3.6.1.4.1.193.72.600.1.1.3.1	INTEGER	read-only	The state of the temperature control can be: 0 - Low 1 - Normal 2 - High 3 - TooHigh
I32 tempValue	1.3.6.1.4.1.193.72.600.1.1.3.2	Integer32	read-only	The temperature value in the node in deg. Celsius.
fansStatus	1.3.6.1.4.1.193.72.600.1.1.4
INT greenFanStatus	1.3.6.1.4.1.193.72.600.1.1.4.1	INTEGER	read-only	The status of the fan which is placed closest to the green LED. For ESN310/ECN320/ECN330, green fan is the fan placed near the front. Made deprecated. Use the greenFanPerfStatus parameter instead.
INT redFanStatus	1.3.6.1.4.1.193.72.600.1.1.4.2	INTEGER	read-only	The status of the fan which is placed closest to the red LED. For ESN310/ECN320/ECN330, red fan is the fan placed near the rear. Made deprecated. Use the redFanPerfStatus parameter instead.
U32 greenFanSpeed	1.3.6.1.4.1.193.72.600.1.1.4.3	Unsigned32	read-only	The speed of the fan, which is placed closest to the green LED, measured in rpm (revolutions per minute). For ESN310/ECN320/ECN330, green fan is the fan placed near the front.
U32 redFanSpeed	1.3.6.1.4.1.193.72.600.1.1.4.4	Unsigned32	read-only	The speed of the fan, which is placed closest to the red LED, measured in rpm (revolutions per minute). For ESN310/ECN320/ECN330, red fan is the fan placed near the rear.
INT greenFanPerfStatus	1.3.6.1.4.1.193.72.600.1.1.4.5	INTEGER	read-only	The performance status of the fan which is placed closest to the green LED. For ESN310/ECN320/ECN330, green fan is the fan placed near the front.
INT redFanPerfStatus	1.3.6.1.4.1.193.72.600.1.1.4.6	INTEGER	read-only	The performance status of the fan which is placed closest to the red LED. For ESN310/ECN320/ECN330, red fan is the fan placed near the rear.
alarmFilter	1.3.6.1.4.1.193.72.600.1.1.5
INT comAlarmFilter	1.3.6.1.4.1.193.72.600.1.1.5.1	INTEGER	read-write	This alarm filter will filter out all communication alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
INT envAlarmFilter	1.3.6.1.4.1.193.72.600.1.1.5.2	INTEGER	read-write	This alarm filter will filter out all environment alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
INT equipAlarmFilter	1.3.6.1.4.1.193.72.600.1.1.5.3	INTEGER	read-write	This alarm filter will filter out all equipment alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
INT processAlarmFilter	1.3.6.1.4.1.193.72.600.1.1.5.4	INTEGER	read-write	This alarm filter will filter out all processing alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
INT qosAlarmFilter	1.3.6.1.4.1.193.72.600.1.1.5.5	INTEGER	read-write	This alarm filter will filter out all quality alarms with lower severity than the selected. For example: Selecting minor (1) would filter out all alarms with warning (0) severity.
U32 alarmFilterThres	1.3.6.1.4.1.193.72.600.1.1.5.6	Unsigned32	read-write	The threshold value indicates how many alarms that can be filtered by the node in the time interval indicated by the alarmFilterInterval parameter before an alarm is sent. If set to 0, the functionality is disabled.
U32 alarmFilterInterval	1.3.6.1.4.1.193.72.600.1.1.5.7	Unsigned32	read-write	The value of this parameter indicates the time interval in which the node can filter a number of alarms indicated by the alarmFilterThres parameter before an alarm is sent. If set to 0, the functionality is disabled.
configurationData	1.3.6.1.4.1.193.72.600.1.1.6
MAC localMacAddr	1.3.6.1.4.1.193.72.600.1.1.6.1	MacAddress	read-only	Unique MAC address of the node.
PHY phyMode	1.3.6.1.4.1.193.72.600.1.1.6.2	PhyModeType	read-write	Ethernet PHY Mode setting. The Phy Mode is coded as a bitfield: * Bit 0: Auto-negotiation. If set, auto-negotiation is OFF else ON. * Bit 2: Full Duplex control. If set, full duplex operation is NOT allowed. * Bit 3: 100 Mbit/s control. If set, 100 Mbit/s operation is NOT allowed. * Bit 4: Half Duplex control. If set, half duplex operation is NOT allowed * Bit 5: 10 Mbit/s control. If set, 10 Mbit/s operation is NOT allowed. Examples of PHY Mode values: * 0x00: Full auto-negotiation. * 0x20: 100 Mbit/s only. Auto-negotiation between half & full duplex. * 0x31: Fixed 100 Mbit/s, full duplex only operation. * 0x25: Fixed 100 Mbit/s, half duplex only operation
INT watchDogEnable	1.3.6.1.4.1.193.72.600.1.1.6.3	INTEGER	read-only	Enabling of the HW Watchdog. If 0 (zero), the watchdog is OFF, else the watchdog is ON.
U32 vlanId	1.3.6.1.4.1.193.72.600.1.1.6.5	Unsigned32	read-write	The VLAN ID setting for the management VLAN.
U32 vlanPrio	1.3.6.1.4.1.193.72.600.1.1.6.6	Unsigned32	read-write	Specifies the IEEE 802.1Q priority used for the management VLAN.
INT vlanTagging	1.3.6.1.4.1.193.72.600.1.1.6.7	INTEGER	read-write	If 0, VLAN tagging is off, meaning that VLAN is not used. If 1, VLAN tagging is used, with the given ID and Prio.
OCT bootString	1.3.6.1.4.1.193.72.600.1.1.6.8	OCTET STRING	read-only	Text commands for the bootloader.
upgradeSW	1.3.6.1.4.1.193.72.600.1.1.7
STR swFileName	1.3.6.1.4.1.193.72.600.1.1.7.1	DisplayString	read-write	The filename to upload to the node. The path to this file is in the root directory that is specified in the FTP server
INT uploadSW	1.3.6.1.4.1.193.72.600.1.1.7.2	INTEGER	read-write	Upload new application software to device. The file which is loaded is indicated by the swFileName parameter. 1 - upload SW to the device and restart afterwards. 2 - upload SW to the device without restarting. Using GET command the current (inProgress) or last known state (success or failure) are displayed.
STR bootSwFileName	1.3.6.1.4.1.193.72.600.1.1.7.3	DisplayString	read-write	The filename of a boot sw image located on the domain file server. This file name is used by the uploadBootSw.
INT uploadBootSw	1.3.6.1.4.1.193.72.600.1.1.7.4	INTEGER	read-write	Upload new boot software to this device. The boot sw image must be named by the bootSwFileName parameter and located on the domain file server, which is the next-server in the DHCP offer. Using GET command the current (inProgress) or last known state (success or failure) are displayed.
INT hideInternalInterfaces	1.3.6.1.4.1.193.72.600.1.1.8	INTEGER	read-write	The management system can chose to hide all interfaces (RFC1233/RFC2233) that are irrelevant in the PEM network view (HP OpenView issue). If 0, Don't hide any interfaces. If 1, Hide internal interfaces (for example loopback and ATM interfaces).
INT restart	1.3.6.1.4.1.193.72.600.1.1.9	INTEGER	read-write	When set to 'restart' the node restarts, which includes loading the SW image and configuration data from the server. In this way a new SW version can be loaded and/or the configu- ration data can be updated.
INT ledsAltBlink	1.3.6.1.4.1.193.72.600.1.1.10	INTEGER	read-write	When the ledsAltBlink is set to ON(1) the LEDs will start to blink alternatively.
INT startCfgVerification	1.3.6.1.4.1.193.72.600.1.1.11	INTEGER	read-write	When startCfgVerification is set to verify(1) the node makes a DHCP renew and retrieves the configuration file from the address of the server just received from DHCP. The parameters contained in the configuration file overwrites the current settings. The status of the last issued verification can be read out by reading this MIB variable.
INT saveCfgToNvm	1.3.6.1.4.1.193.72.600.1.1.12	INTEGER	read-write	When saveCfgToNvm is set to start(1) the device saves the configuration data parameters to NVM. Using GET command the current (inProgress) or last known state (success or failure) are displayed.
U32 cfgVerificationInterval	1.3.6.1.4.1.193.72.600.1.1.13	Unsigned32	read-write	This is the time in minutes between configuration file verification. If the value is zero the configuration verification is disabled.
INT notifyType	1.3.6.1.4.1.193.72.600.1.1.14	INTEGER	read-write	Set the type of the notify sent by the node: 1. Trap 2. Inform
identificationData	1.3.6.1.4.1.193.72.600.1.1.15
deviceIdData	1.3.6.1.4.1.193.72.600.1.1.15.1
STR productNumber	1.3.6.1.4.1.193.72.600.1.1.15.1.1	DisplayString	read-only	Index number that identifies the node.
STR revisionState	1.3.6.1.4.1.193.72.600.1.1.15.1.2	DisplayString	read-only	Revision State or 'R-state' declaring minor versions. For example: different types of components or new boot SW.
STR functionDesignation	1.3.6.1.4.1.193.72.600.1.1.15.1.3	DisplayString	read-only	Number with reference to the handling and use of the product.
OCT dateOfProduction	1.3.6.1.4.1.193.72.600.1.1.15.1.4	OCTET STRING	read-only	Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
OCT dateOfRepair	1.3.6.1.4.1.193.72.600.1.1.15.1.5	OCTET STRING	read-only	Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
STR productionSerialNumber	1.3.6.1.4.1.193.72.600.1.1.15.1.6	DisplayString	read-only	Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.
OCT layoutVersionCode	1.3.6.1.4.1.193.72.600.1.1.15.1.7	OCTET STRING	read-only	The data layout version that allows the possibility to interpret stored data differently.
OCT idCheckSum	1.3.6.1.4.1.193.72.600.1.1.15.1.8	OCTET STRING	read-only	CRC32 Checksum of identification data structure of the node.
microProcessorIdData	1.3.6.1.4.1.193.72.600.1.1.15.2
STR productNumberMicroProcessor	1.3.6.1.4.1.193.72.600.1.1.15.2.1	DisplayString	read-only	Index number that identifies the MicroProcessor board.
STR revisionStateMicroProcessor	1.3.6.1.4.1.193.72.600.1.1.15.2.2	DisplayString	read-only	Revision State or 'R-state' declaring minor versions. For example: different types of components or new boot SW.
STR functionDesignationMicroProcessor	1.3.6.1.4.1.193.72.600.1.1.15.2.3	DisplayString	read-only	Number with reference to the handling and use of the product.
OCT dateOfProductionMicroProcessor	1.3.6.1.4.1.193.72.600.1.1.15.2.4	OCTET STRING	read-only	Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
OCT dateOfRepairMicroProcessor	1.3.6.1.4.1.193.72.600.1.1.15.2.5	OCTET STRING	read-only	Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
STR productionSerialNumberMicroProcessor	1.3.6.1.4.1.193.72.600.1.1.15.2.6	DisplayString	read-only	Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.
OCT layoutVersionCodeMicroProcessor	1.3.6.1.4.1.193.72.600.1.1.15.2.7	OCTET STRING	read-only	The data layout version that allows the possibility to interpret stored data differently.
OCT idCheckSumMicroProcessor	1.3.6.1.4.1.193.72.600.1.1.15.2.8	OCTET STRING	read-only	CRC32 Checksum of identification data structure for the MicroProcessor board.
analogueFrontEndIdData	1.3.6.1.4.1.193.72.600.1.1.15.3
STR productNumberAnalogueFrontEnd	1.3.6.1.4.1.193.72.600.1.1.15.3.1	DisplayString	read-only	Index number that identifies the AFE board.
STR revisionStateAnalogueFrontEnd	1.3.6.1.4.1.193.72.600.1.1.15.3.2	DisplayString	read-only	Revision State or 'R-state' declaring minor versions. For example: different types of components or new boot SW.
STR functionDesignationAnalogueFrontEnd	1.3.6.1.4.1.193.72.600.1.1.15.3.3	DisplayString	read-only	Number with reference to the handling and use of the product.
OCT dateOfProductionAnalogueFrontEnd	1.3.6.1.4.1.193.72.600.1.1.15.3.4	OCTET STRING	read-only	Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
OCT dateOfRepairAnalogueFrontEnd	1.3.6.1.4.1.193.72.600.1.1.15.3.5	OCTET STRING	read-only	Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
STR productionSerialNumberAnalogueFrontEnd	1.3.6.1.4.1.193.72.600.1.1.15.3.6	DisplayString	read-only	Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.
OCT layoutVersionCodeAnalogueFrontEnd	1.3.6.1.4.1.193.72.600.1.1.15.3.7	OCTET STRING	read-only	The data layout version that allows the possibility to interpret stored data differently.
OCT idCheckSumAnalogueFrontEnd	1.3.6.1.4.1.193.72.600.1.1.15.3.8	OCTET STRING	read-only	CRC32 Checksum of identification data structure for the Analogue Front End board.
dcDcConverterIdData	1.3.6.1.4.1.193.72.600.1.1.15.4
STR productNumberDcDcConverter	1.3.6.1.4.1.193.72.600.1.1.15.4.1	DisplayString	read-only	Index number that identifies the DC-DC Converter board.
STR revisionStateDcDcConverter	1.3.6.1.4.1.193.72.600.1.1.15.4.2	DisplayString	read-only	Revision State or 'R-state' declaring minor versions. For example: different types of components or new boot SW.
STR functionDesignationDcDcConverter	1.3.6.1.4.1.193.72.600.1.1.15.4.3	DisplayString	read-only	Number with reference to the handling and use of the product.
OCT dateOfProductionDcDcConverter	1.3.6.1.4.1.193.72.600.1.1.15.4.4	OCTET STRING	read-only	Manufacturing date, describing when the unit has been manufactured, in terms of a year, month and a day, as described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
OCT dateOfRepairDcDcConverter	1.3.6.1.4.1.193.72.600.1.1.15.4.5	OCTET STRING	read-only	Repair date, declaring the year, month and day of the latest repair. The format is described below: Year code(0000 ..9999) - 2 bytes (LSB,MSB) Month (1..12)- 1 byte Day (1 ..31)- 1 byte. For example, Wednesday June 12, 2002 would be displayed as: h'02, h'14, h'06, h'0C.
STR productionSerialNumberDcDcConverter	1.3.6.1.4.1.193.72.600.1.1.15.4.6	DisplayString	read-only	Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.
OCT layoutVersionCodeDcDcConverter	1.3.6.1.4.1.193.72.600.1.1.15.4.7	OCTET STRING	read-only	The data layout version that allows the possibility to interpret stored data differently.
OCT idCheckSumDcDcConverter	1.3.6.1.4.1.193.72.600.1.1.15.4.8	OCTET STRING	read-only	CRC32 Checksum of identification data for the DC-DC Converter board.
IP sntpServerIP	1.3.6.1.4.1.193.72.600.1.1.16	IpAddress	read-write	The IP address of SNTP server used for time synchronization.
U32 snmpKeepAliveTimerTime	1.3.6.1.4.1.193.72.600.1.1.17	Unsigned32	read-write	The interval between SNMP KeepAlive checks.
INT allowBroadcastToDux	1.3.6.1.4.1.193.72.600.1.1.18	INTEGER	read-write	Enables/disables broadcast to DUX (broadcast beacons). When the IP DSLAM is restarted one broadcast to DUX is always sent, hereafter allowBroadcastToDux determines whether broadcast to DUX are sent on a regular basis. In default settings the broadcast to DUX is enabled. Note: It is not recommended to disable broadcast to DUX because it might result in reboot of EDA nodes due to expire of the 'Keep-alive Timer'. For more details consult the Users Guide.
peaMultilink	1.3.6.1.4.1.193.72.600.1.1.20
INT peaMultilinkMode	1.3.6.1.4.1.193.72.600.1.1.20.1	INTEGER	read-write	This defines the mode the multiple network-side links operate in. singleLink(1) - only one link is used for active data transfer. This is the only possible value for devices with a single network-side link. linkAggregation(2) - the multiple links are used as one trunk aggregating the traffic. redundantConfiguration(3) - only one of the the multiple links is used for active data transfer, but the other are kept stand by for resilience (uses RSTP protocol). Note: the read value may not match the actual mode during switch over.
I32 peaMultilinkPreferredInterface	1.3.6.1.4.1.193.72.600.1.1.20.2	Integer32	read-only	Shows the index of the interface (link) selected for traffic forwarding whenever there is no other explicit indication on which one to choose. The interface is selected during boot - it is the interface the device was booted from. The value is the same as used for interfaces in the IF-MIB (1-based).
peaMultilinkInterfaceTable	1.3.6.1.4.1.193.72.600.1.1.20.3		not-accessible	This is a table of interfaces (links) on the network-side. The table is indexed by the same interface numbers as used in the IF-MIB (1-based).
peaMultilinkInterfaceEntry	1.3.6.1.4.1.193.72.600.1.1.20.3.1		not-accessible	This is an entry of the multilinkInterfaceTable
NUM peaMultilinkInterfaceIndex	1.3.6.1.4.1.193.72.600.1.1.20.3.1.1	InterfaceIndex	not-accessible	This is the index to the multilinkInterfaceTable. The values are the same as used in the IF-MIB (1-based).
T/F peaMultilinkIsForwarding	1.3.6.1.4.1.193.72.600.1.1.20.3.1.2	TruthValue	read-only	This shows if the corresponding interface (link) is forwarding traffic - true(1) or not - false(2). An interface that is not forwarding may still carry some service data (e.g. PDUs).
T/F peaMultilinkIsUp	1.3.6.1.4.1.193.72.600.1.1.20.3.1.3	TruthValue	read-only	This shows if the corresponding interface (link) is up true(1) or down - false(2). The true(1) value is returned if the ifOperState of the corresponding port is up. The false(1) value is returned if the ifOperState of the corresponding port is NOT up (e.g. down, testing, etc.).
INT peaMultilinkForceManagementToUsePreferredInterface	1.3.6.1.4.1.193.72.600.1.1.20.4	INTEGER	read-write	Setting this value to 'enabled (1)' forces the management traffic to be sent on the interface towards the Active ECN thereby overruling the RSTP protocol for management traffic towards this node. This enables the node controller to stay in contact with the DSLAM, even if the link is switched to the other interface by RSTP.
INT comboConnector	1.3.6.1.4.1.193.72.600.1.1.21	INTEGER	read-only	Tell if a combo connector is mounted for this board.
INT blockUnit	1.3.6.1.4.1.193.72.600.1.1.22	INTEGER	read-write	Block this unit. When blocked: - no user traffic is carried out - no alarms are issued - it does not allow any configuration Getting a card out of blocked state can be done by either sending a restart request to it (MIB or Reset-On-Lan) or by dismouting and mounting it again. Setting state to unblock will be ignored.
commonTraps	1.3.6.1.4.1.193.72.600.1.2
traps	1.3.6.1.4.1.193.72.600.1.2.0
trapsParameters	1.3.6.1.4.1.193.72.600.1.2.1
ifObjects	1.3.6.1.4.1.193.72.600.1.5
ifNotifications	1.3.6.1.4.1.193.72.600.1.6
ifNotificationTypes	1.3.6.1.4.1.193.72.600.1.6.0
peaEquipmentMibGroups	1.3.6.1.4.1.193.72.600.1.7
snmpv2Notifications	1.3.6.1.4.1.193.72.600.1.8
snmpv2NotificationsTypes	1.3.6.1.4.1.193.72.600.1.8.0
bridgeNotifications	1.3.6.1.4.1.193.72.600.1.9
bridgeNotificationsTypes	1.3.6.1.4.1.193.72.600.1.9.0
rmonNotifications	1.3.6.1.4.1.193.72.600.1.10
rmonNotificationsTypes	1.3.6.1.4.1.193.72.600.1.10.0

RFC description

Ericsson public ethernet access equipment management MIB for reading and writing common equipment information and alarms.

Start monitoring Ericsson IP DSLAM chassis (system identity/hardware health) 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 PEA-EQUIPMENT