PEA_EQUIPMENT: View SNMP OID List / Download MIB

VENDOR: ERICSSON AB


 Home MIB: PEA_EQUIPMENT
Download as:   
PEM-STANDARD, SNMPv2-CONF, PEA-SMI, SNMPv2-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 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
             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 device software.
             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.
             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.
             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 device.
             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 device.
         mainProcessor 1.3.6.1.4.1.193.72.600.1.1.2
             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).
             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.
             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.
             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
             tempControlState 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 Enumeration: 'high': 2, 'tooHigh': 3, 'low': 0, 'normal': 1.
             tempValue 1.3.6.1.4.1.193.72.600.1.1.3.2 integer32 read-only
The temperature value in the device in grade Celsius.
         fansStatus 1.3.6.1.4.1.193.72.600.1.1.4
             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, green fan is the fan place to the front Enumeration: 'failed': 0, 'working': 1.
             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, red fan is the fan place to the back Enumeration: 'failed': 0, 'working': 1.
             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 (rotations per minute).
             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 (rotations per minute).
         alarmFilter 1.3.6.1.4.1.193.72.600.1.1.5
             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. E.g. Selecting minor (1) would filter out all alarms with warning (0) severity. Enumeration: 'major': 2, 'warning': 0, 'critical': 3, 'minor': 1.
             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. E.g. Selecting minor (1) would filter out all alarms with warning (0) severity. Enumeration: 'major': 2, 'warning': 0, 'critical': 3, 'minor': 1.
             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. E.g. Selecting minor (1) would filter out all alarms with warning (0) severity. Enumeration: 'major': 2, 'warning': 0, 'critical': 3, 'minor': 1.
             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. E.g. Selecting minor (1) would filter out all alarms with warning (0) severity. Enumeration: 'major': 2, 'warning': 0, 'critical': 3, 'minor': 1.
             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. E.g. Selecting minor (1) would filter out all alarms with warning (0) severity. Enumeration: 'major': 2, 'warning': 0, 'critical': 3, 'minor': 1.
             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 device in the time interval indicated by the alarmFilterInterval parameter before an alarm is sent. If set to 0, the functionality is disabled.
             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 device 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
             localMacAddr 1.3.6.1.4.1.193.72.600.1.1.6.1 macaddress read-only
Unique MAC address of the device.
             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
             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. Enumeration: 'on': 1, 'off': 0.
             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.
             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.
             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. Enumeration: 'on': 1, 'off': 0.
             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
             swFileName 1.3.6.1.4.1.193.72.600.1.1.7.1 displaystring read-write
The filename to upload to the device. The path to this file is in the root directory that is specified in the FTP server
             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. Enumeration: 'uploadSwWithoutRestart': 2, 'uploadSwWithRestart': 1.
             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.
             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. Enumeration: 'start': 1.
         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 (e.g. loopback and ATM interfaces). Enumeration: 'on': 1, 'off': 0.
         restart 1.3.6.1.4.1.193.72.600.1.1.9 integer read-write
When set to 'restart' the device 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. Enumeration: 'restart': 1.
         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. Enumeration: 'on': 1, 'off': 0.
         startCfgVerification 1.3.6.1.4.1.193.72.600.1.1.11 integer read-write
When startCfgVerification is set to verify(1) the device retrieves the configuration file from a server and overwrites its parameters with the parameters from the new file. Enumeration: 'verify': 1.
         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. Enumeration: 'start': 1.
         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.
         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 device: 1. Trap 2. Inform Enumeration: 'inform': 2, 'trap': 1.
         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
                   productNumber 1.3.6.1.4.1.193.72.600.1.1.15.1.1 displaystring read-only
Index number that identifies the device.
                   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. E.g. different types of components or new boot SW.
                   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.
                   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.
                   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.
                   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.
                   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.
                   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 device.
               microProcessorIdData 1.3.6.1.4.1.193.72.600.1.1.15.2
                   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.
                   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. E.g. different types of components or new boot SW.
                   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.
                   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.
                   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. he 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.
                   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.
                   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.
                   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
                   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.
                   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. E.g. different types of components or new boot SW.
                   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.
                   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.
                   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.
                   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.
                   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.
                   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
                   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.
                   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. E.g. different types of components or new boot SW.
                   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.
                   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.
                   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.
                   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.
                   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.
                   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.
         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.
     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
             tempTooHigh 1.3.6.1.4.1.193.72.600.1.2.0.1
Temperature is too high. The temperature has increased above a fixed threshold value. The high temperature value is probably caused by fan failure or high environment temperature. For the IP DSLAM the lines are stopped in order to reduce the power consumption and avoid damage to the device.
             tempTooHighCeasing 1.3.6.1.4.1.193.72.600.1.2.0.2
Temperature too high ceasing. The temperature has decreased below a fixed threshold value in the normal working area. For the IP DSLAM the lines are brought into service again, which will lead to increasing power consumption and possibly increased temperature.
             greenFanFailure 1.3.6.1.4.1.193.72.600.1.2.0.3
Indicates a fan failure on the fan closest to the green LED. For ESN310, green fan is the fan place to the front
             greenFanCeasing 1.3.6.1.4.1.193.72.600.1.2.0.4
Indicates the ceasing of the fan which is closest to the green LED. For ESN310, green fan is the fan place to the front
             redFanFailure 1.3.6.1.4.1.193.72.600.1.2.0.5
Indicates a fan failure on the fan closest to the red LED. For ESN310, red fan is the fan place to the back
             redFanCeasing 1.3.6.1.4.1.193.72.600.1.2.0.6
Indicates the ceasing of the fan which is closest to the red LED. For ESN310, red fan is the fan place to the back
             restartAlarm 1.3.6.1.4.1.193.72.600.1.2.0.7
Device restart alarm. The post mortem information will indicate the reason for the restart.
             stateEventErr 1.3.6.1.4.1.193.72.600.1.2.0.8
State/Event SW error detected. Called by the Default Error Handler in DMAPI when a message is discarded.
             nonFatalSoftwareErr 1.3.6.1.4.1.193.72.600.1.2.0.9
Non-fatal SW error detected.
             fatalSoftwareErr 1.3.6.1.4.1.193.72.600.1.2.0.10
Fatal SW error detected - The device SW will restart.
             configurationFileErr 1.3.6.1.4.1.193.72.600.1.2.0.11
Configuration file load or pass error.
             idDataReadErr 1.3.6.1.4.1.193.72.600.1.2.0.12
Indicates that the identification data read from FLASH for the HW unit indicated by 'hwUnitId' parameter is corrupted.
             cfgDataReadErr 1.3.6.1.4.1.193.72.600.1.2.0.13
Indicates that the configuration data read from FLASH for the device is corrupted. The 'configData' parameter indicates the data corrupted.
             writeFlashErr 1.3.6.1.4.1.193.72.600.1.2.0.14
Indicates that an error occured during FLASH writing.
             bothFansFailed 1.3.6.1.4.1.193.72.600.1.2.0.15
Indicates that both fans failed.
             bothFansFailCeasing 1.3.6.1.4.1.193.72.600.1.2.0.16
Indicates the ceasing of both fans failure. At least one of the fans is working.
             deviceTypeUnknown 1.3.6.1.4.1.193.72.600.1.2.0.17
Indicates that the device type can not be identified. The product number and revision state are unkonwn or corrupted. The application software can not handle hardware correctly.
             greenFanLowPerformance 1.3.6.1.4.1.193.72.600.1.2.0.18
Indicates that the fan, which is close to the green LED, has a low performance.
             greenFanLowPerformanceCeasing 1.3.6.1.4.1.193.72.600.1.2.0.19
Indicates the ceasing of the low performance of the fan, which is close to the green LED.
             redFanLowPerformance 1.3.6.1.4.1.193.72.600.1.2.0.20
Indicates that the fan, which is close to the red LED, has a low performance.
             redFanLowPerformanceCeasing 1.3.6.1.4.1.193.72.600.1.2.0.21
Indicates the ceasing of the low performace of the fan, which is close to the red LED.
             tempCloseToTooHigh 1.3.6.1.4.1.193.72.600.1.2.0.22
Indicates the temperature is close to the too high value, when the subscriber lines are shut down.
             tempCloseToTooHighCeasing 1.3.6.1.4.1.193.72.600.1.2.0.23
Indicates that the temperatureCloseToTooHigh alarm is ceased.
             configurationMismatch 1.3.6.1.4.1.193.72.600.1.2.0.24
This alarm has a higher severity than configurationItemMismatch and is only sent once no matter how many parameter mismatches that is detected. This can be considered as one generel alarm instead of using several configurationItemMismatch alarms. From this trap it is possible to see how many items that had a mismatch The trap is sent if e.g. the trap notification is set to 'inform' and that it was expected to be 'trap' then a configurationMismatch will be sent to the management system
             configurationItemMismatch 1.3.6.1.4.1.193.72.600.1.2.0.25
This alarm is sent for each parameter where a mismatch is detected. If e.g. the trap notification is set to 'inform' and that it was expected to be 'trap' then a configurationItemMismatch will be sent to the management system
             swUploadErr 1.3.6.1.4.1.193.72.600.1.2.0.26
An error occured during software upload.
             programStartFailure 1.3.6.1.4.1.193.72.600.1.2.0.27
When no valid flash part can be found on the device this trap is sent.
         trapsParameters 1.3.6.1.4.1.193.72.600.1.2.1
             taskId 1.3.6.1.4.1.193.72.600.1.2.1.1 displaystring no-access
The name of the task, which sent the alarm.
             taskState 1.3.6.1.4.1.193.72.600.1.2.1.2 unsigned32 no-access
The state of the task, which sent the alarm.
             taskFileName 1.3.6.1.4.1.193.72.600.1.2.1.3 displaystring no-access
The file name from where the alarm was sent
             lineNumber 1.3.6.1.4.1.193.72.600.1.2.1.4 unsigned32 no-access
The line number in the file indicated by taskFileName, from where the alarm was sent
             msgSenderTask 1.3.6.1.4.1.193.72.600.1.2.1.5 displaystring no-access
Indicates the name of the task which sent the message causing a stateEventError.
             errCode 1.3.6.1.4.1.193.72.600.1.2.1.6 displaystring no-access
Additional error information.
             postMortemInfo 1.3.6.1.4.1.193.72.600.1.2.1.7 displaystring no-access
Indicates the reason of the restart.
             errData 1.3.6.1.4.1.193.72.600.1.2.1.8 octet string no-access
Additional data related to the error.
             msgId 1.3.6.1.4.1.193.72.600.1.2.1.9 unsigned32 no-access
Message ID of the last received message. E.g. the ID of the message causing a state event error.
             msgData 1.3.6.1.4.1.193.72.600.1.2.1.10 octet string no-access
Message content of the last received message. E.g. the content of the message causing a state event error.
             hwUnitId 1.3.6.1.4.1.193.72.600.1.2.1.11 integer no-access
Identifies the HW unit which has the identification data corrupted into FLASH. Enumeration: 'device': 1, 'dcDcConverter': 4, 'analogueFrontEnd': 3, 'microProcessor': 2.
             configData 1.3.6.1.4.1.193.72.600.1.2.1.12 integer no-access
Identifies the corrupted configuration data read from FLASH . Enumeration: 'bootString': 5, 'watchdogEnable': 3, 'localMacAddr': 1, 'phyMode': 2, 'vlanInfo': 4.
             idOrConfigData 1.3.6.1.4.1.193.72.600.1.2.1.13 integer no-access
Identifies during which data writing occured an error. Enumeration: 'bootString': 9, 'localMacAddr': 5, 'vlanInfo': 8, 'watchdogEnable': 7, 'phyMode': 6, 'microProcessorIdData': 2, 'analogueFrontEndIdData': 3, 'dcDcConverterIdData': 4, 'deviceIdData': 1.
     pethObjects 1.3.6.1.4.1.193.72.600.1.3
     pethNotifications 1.3.6.1.4.1.193.72.600.1.4
         pethNotificationTypes 1.3.6.1.4.1.193.72.600.1.4.0
             pethPsePortFailureNotification 1.3.6.1.4.1.193.72.600.1.4.0.1
This notification is sent when the port detects a permanent power failure. It is not specified if the notification is triggered by a malfunction on the PSE, PD or the MAIN PSE HW.
             pethPsePortFailureCeasingNotification 1.3.6.1.4.1.193.72.600.1.4.0.2
The CEASING counterpart of pethPsePortFailureNotification.