PEA-EQUIPMENT: View SNMP OID List / Download MIB
VENDOR: ERICSSON AB
| Home | MIB: PEA-EQUIPMENT | |||
|---|---|---|---|---|
| Download as: |
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).
|
|||
| 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 node 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 node. |
| 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 | |||
| 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 node in deg. 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/ECN320/ECN330, green fan is the fan placed near the front. Made deprecated. Use the greenFanPerfStatus parameter instead. 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/ECN320/ECN330, red fan is the fan placed near the rear. Made deprecated. Use the redFanPerfStatus parameter instead. 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 (revolutions per minute). For ESN310/ECN320/ECN330, green fan is the fan placed near the front. |
| 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. |
| 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. Enumeration: 'poor': 2, 'failed': 1, 'good': 3. |
| 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. Enumeration: 'poor': 2, 'failed': 1, 'good': 3. |
| 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. For example: 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. For example: 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. For example: 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. For example: 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. For example: 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 node 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 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 | |||
| localMacAddr | 1.3.6.1.4.1.193.72.600.1.1.6.1 | macaddress | read-only |
Unique MAC address of the node. |
| 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 node. 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. Using GET command the current (inProgress) or last known state (success or failure) are displayed. Enumeration: 'failure': 4, 'uploadSwWithoutRestart': 2, 'uploadSwWithRestart': 1, 'success': 0, 'uploadInProgress': 3. |
| 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. Using GET command the current (inProgress) or last known state (success or failure) are displayed. Enumeration: 'failure': 3, 'uploadInProgress': 2, 'success': 0, '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 (for example 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 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. 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 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. Enumeration: 'verify': 1, 'noAnswerFromDHCP': 3, 'noAnswerFromTFTP': 4, 'success': 0, 'verificationInProgress': 2. |
| 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. Enumeration: 'start': 1, 'saveInProgress': 2, 'success': 0, 'failure': 3. |
| 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 node: 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 node. |
| 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. |
| 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 node. |
| 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. For example: 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. 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. |
| 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. For example: 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. For example: 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. |
| snmpKeepAliveTimerTime | 1.3.6.1.4.1.193.72.600.1.1.17 | unsigned32 | read-write |
The interval between SNMP KeepAlive checks. |
| 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. Enumeration: 'false': 0, 'true': 1. |
| peaMultilink | 1.3.6.1.4.1.193.72.600.1.1.20 | |||
| 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. Enumeration: 'linkAggregation': 2, 'redundantConfiguration': 3, 'singleLink': 1. |
| 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 | no-access |
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). |
|
| 1.3.6.1.4.1.193.72.600.1.1.20.3.1 | no-access |
This is an entry of the multilinkInterfaceTable |
||
| peaMultilinkInterfaceIndex | 1.3.6.1.4.1.193.72.600.1.1.20.3.1.1 | interfaceindex | no-access |
This is the index to the multilinkInterfaceTable. The values are the same as used in the IF-MIB (1-based). |
| 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). |
| 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.). |
| 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. Enumeration: 'disabled': 2, 'enabled': 1. |
| 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. Enumeration: 'mounted': 1, 'notMounted': 2. |
| 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. Enumeration: 'unblock': 2, 'block': 1. |
| 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 | |||