PEA-EQUIPMENT-IPDSLAM
File:
PEA-EQUIPMENT-IPDSLAM.mib (80158 bytes)
Imported modules
Imported symbols
Defined Types
| PhyModeType |
|
| Represent the Ethernet PHY Mode. |
| TEXTUAL-CONVENTION |
|
|
|
| |
OCTET STRING |
Size(1) |
|
| MultilinkInterfaceEntry |
|
| SEQUENCE |
|
|
|
| |
multilinkInterfaceIndex |
InterfaceIndex |
|
| |
multilinkIsForwarding |
TruthValue |
|
| |
multilinkIsUp |
TruthValue |
|
Defined Values
| peaEquipmentIpDslam |
1.3.6.1.4.1.193.72.300.1 |
|
The IP DSLAM software supports a number of standard
and proprietary MIBs.
This MIB module defines objects for reading out system
specific information about the IP DSLAM and the control
entries for restarting the IP DSLAM, for setting the
alarm filter and for controlling the LEDs.
|
| MODULE-IDENTITY |
|
|
|
| ledControl |
1.3.6.1.4.1.193.72.300.1.1.4 |
| OBJECT IDENTIFIER |
|
|
|
| mainProcessor |
1.3.6.1.4.1.193.72.300.1.1.7 |
| OBJECT IDENTIFIER |
|
|
|
| alarmFilter |
1.3.6.1.4.1.193.72.300.1.1.9 |
| OBJECT IDENTIFIER |
|
|
|
| multilink |
1.3.6.1.4.1.193.72.300.1.1.15 |
| OBJECT IDENTIFIER |
|
|
|
| cfgVersion |
1.3.6.1.4.1.193.72.300.1.1.1 |
| The CfgVersion 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. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| restartModemPool |
1.3.6.1.4.1.193.72.300.1.1.2 |
| When set to 'restart' the IP DSLAM 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. All the ADSL lines will be out of
service while the IP DSLAM restarts. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
restart(1) |
|
| systemIdentification |
1.3.6.1.4.1.193.72.300.1.1.8 |
| This value includes the full name and version
identification of the IP DSLAM software. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..255) |
|
| bootSwIdentification |
1.3.6.1.4.1.193.72.300.1.1.12 |
| This value includes the full name and version
identification of the BOOT software. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..255) |
|
| temperatureControlState |
1.3.6.1.4.1.193.72.300.1.1.3.1 |
| The state of the temperature control can be:
0 - Low
1 - Normal
2 - High
3 - TooHigh |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
low(0), normal(1), high(2), tooHigh(3) |
|
| temperatureValue |
1.3.6.1.4.1.193.72.300.1.1.3.2 |
| The temperature value in the IP DSLAM in grade Celsius. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
1..150 |
|
| fansStatus |
1.3.6.1.4.1.193.72.300.1.1.3.3 |
| OBJECT IDENTIFIER |
|
|
|
| fanGreenStatus |
1.3.6.1.4.1.193.72.300.1.1.3.3.1 |
| The status of the fan which is placed closest to the green LED. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
failed(0), working(1) |
|
| fanRedStatus |
1.3.6.1.4.1.193.72.300.1.1.3.3.2 |
| The status of the fan which is placed closest to the red LED. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
failed(0), working(1) |
|
| fanGreenSpeed |
1.3.6.1.4.1.193.72.300.1.1.3.3.3 |
| The speed of the fan which is placed closest to the
green LED measured in rpm (rotations per minute). |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| fanRedSpeed |
1.3.6.1.4.1.193.72.300.1.1.3.3.4 |
| The speed of the fan which is placed closest to the
red LED measured in rpm (rotations per minute). |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| ledsAlternativeBlink |
1.3.6.1.4.1.193.72.300.1.1.4.1 |
| When the ledsAlternativeBlink is set to ON(1) the
LEDs will start to blink alternatively. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
on(1), off(0) |
|
| onlyShowEthernetInterface |
1.3.6.1.4.1.193.72.300.1.1.5 |
| When set to ON(1) only the Ethernet interface
is visible (RFC1233/RFC2233).
When is set to OFF(0) the ATM and software loop
back interfaces are also visible. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
on(1), off(0) |
|
| mpProcessorLoad |
1.3.6.1.4.1.193.72.300.1.1.7.1 |
| The percentage of time that the main processor was not idle.
Average over 10 seconds. (almost like hrProcessorLoad in RFC1514). |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..100 |
|
| mpMemFree |
1.3.6.1.4.1.193.72.300.1.1.7.2 |
| The amount of free memory on main processor in percent. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..100 |
|
| mpMemFreeBytes |
1.3.6.1.4.1.193.72.300.1.1.7.3 |
| The amount of free memory on main processor in bytes. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| mpMemBuffersUsed |
1.3.6.1.4.1.193.72.300.1.1.7.4 |
| The total number of memory buffers currently used (Ethernet, ATM & local IP-stack). |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| communicationsAlarmFilter |
1.3.6.1.4.1.193.72.300.1.1.9.1 |
| 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. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
warning(0), minor(1), major(2), critical(3) |
|
| environmentAlarmFilter |
1.3.6.1.4.1.193.72.300.1.1.9.2 |
| 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. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
warning(0), minor(1), major(2), critical(3) |
|
| equipmentAlarmFilter |
1.3.6.1.4.1.193.72.300.1.1.9.3 |
| 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. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
warning(0), minor(1), major(2), critical(3) |
|
| processingAlarmFilter |
1.3.6.1.4.1.193.72.300.1.1.9.4 |
| 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. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
warning(0), minor(1), major(2), critical(3) |
|
| qualityOfServiceAlarmFilter |
1.3.6.1.4.1.193.72.300.1.1.9.5 |
| 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. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
warning(0), minor(1), major(2), critical(3) |
|
| productNumberMP |
1.3.6.1.4.1.193.72.300.1.1.10.1.1 |
| Index number that identifies the IP DSLAM hardware unit. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..24) |
|
| revisionStateMP |
1.3.6.1.4.1.193.72.300.1.1.10.1.2 |
| Revision State or 'R-state' declaring minor versions.
E.g. different types of components or new boot SW. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..7) |
|
| functionDesignationMP |
1.3.6.1.4.1.193.72.300.1.1.10.1.3 |
| Number with reference to the handling and use of the product. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..12) |
|
| dateOfProductionMP |
1.3.6.1.4.1.193.72.300.1.1.10.1.4 |
| 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. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| dateOfRepairMP |
1.3.6.1.4.1.193.72.300.1.1.10.1.5 |
| 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. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productionSerialNumberMP |
1.3.6.1.4.1.193.72.300.1.1.10.1.6 |
| Unique serial number, describing the product in terms of a manufacturing
site code and a sequence number. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(13) |
|
| layoutVersionCodeMP |
1.3.6.1.4.1.193.72.300.1.1.10.1.7 |
| The data layout version that allows the possibility
to interpret stored data differently. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| idCheckSumMP |
1.3.6.1.4.1.193.72.300.1.1.10.1.8 |
| CRC32 Checksum of identification data structure
of the IP DSLAM. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productNumberDUP |
1.3.6.1.4.1.193.72.300.1.1.10.2.1 |
| Index number that identifies the DUP board. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..24) |
|
| revisionStateDUP |
1.3.6.1.4.1.193.72.300.1.1.10.2.2 |
| Revision State or 'R-state' declaring minor versions.
E.g. different types of components or new boot SW. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..7) |
|
| functionDesignationDUP |
1.3.6.1.4.1.193.72.300.1.1.10.2.3 |
| Number with reference to the handling and use of the product. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..12) |
|
| dateOfProductionDUP |
1.3.6.1.4.1.193.72.300.1.1.10.2.4 |
| 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. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| dateOfRepairDUP |
1.3.6.1.4.1.193.72.300.1.1.10.2.5 |
| 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. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productionSerialNumberDUP |
1.3.6.1.4.1.193.72.300.1.1.10.2.6 |
| Unique serial number, describing the product in terms of a manufacturing
site code and a sequence number. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(13) |
|
| layoutVersionCodeDUP |
1.3.6.1.4.1.193.72.300.1.1.10.2.7 |
| The data layout version that allows the possibility
to interpret stored data differently. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| idCheckSumDUP |
1.3.6.1.4.1.193.72.300.1.1.10.2.8 |
| CRC32 Checksum of identification data structure
for the DUP board. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productNumberDAFE |
1.3.6.1.4.1.193.72.300.1.1.10.3.1 |
| Index number that identifies the DAFE board. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..24) |
|
| revisionStateDAFE |
1.3.6.1.4.1.193.72.300.1.1.10.3.2 |
| Revision State or 'R-state' declaring minor versions.
E.g. different types of components or new boot SW. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..7) |
|
| functionDesignationDAFE |
1.3.6.1.4.1.193.72.300.1.1.10.3.3 |
| Number with reference to the handling and use of the product. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..12) |
|
| dateOfProductionDAFE |
1.3.6.1.4.1.193.72.300.1.1.10.3.4 |
| 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. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| dateOfRepairDAFE |
1.3.6.1.4.1.193.72.300.1.1.10.3.5 |
| 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. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productionSerialNumberDAFE |
1.3.6.1.4.1.193.72.300.1.1.10.3.6 |
| Unique serial number, describing the product in terms of a manufacturing
site code and a sequence number. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(13) |
|
| layoutVersionCodeDAFE |
1.3.6.1.4.1.193.72.300.1.1.10.3.7 |
| The data layout version that allows the possibility
to interpret stored data differently. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| idCheckSumDAFE |
1.3.6.1.4.1.193.72.300.1.1.10.3.8 |
| CRC32 Checksum of identification data structure
for the DAFE board. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productNumberDDC |
1.3.6.1.4.1.193.72.300.1.1.10.4.1 |
| Index number that identifies the DDC board. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..24) |
|
| revisionStateDDC |
1.3.6.1.4.1.193.72.300.1.1.10.4.2 |
| Revision State or 'R-state' declaring minor versions.
E.g. different types of components or new boot SW. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..7) |
|
| functionDesignationDDC |
1.3.6.1.4.1.193.72.300.1.1.10.4.3 |
| Number with reference to the handling and use of the product. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..12) |
|
| dateOfProductionDDC |
1.3.6.1.4.1.193.72.300.1.1.10.4.4 |
| 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. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| dateOfRepairDDC |
1.3.6.1.4.1.193.72.300.1.1.10.4.5 |
| 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. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productionSerialNumberDDC |
1.3.6.1.4.1.193.72.300.1.1.10.4.6 |
| Unique serial number, describing the product in terms of a manufacturing
site code and a sequence number. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(13) |
|
| layoutVersionCodeDDC |
1.3.6.1.4.1.193.72.300.1.1.10.4.7 |
| The data layout version that allows the possibility
to interpret stored data differently. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| idCheckSumDDC |
1.3.6.1.4.1.193.72.300.1.1.10.4.8 |
| CRC32 Checksum of identification data for the DDC board. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productNumberDIF |
1.3.6.1.4.1.193.72.300.1.1.10.5.1 |
| Index number that identifies the DIF board. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..24) |
|
| revisionStateDIF |
1.3.6.1.4.1.193.72.300.1.1.10.5.2 |
| Revision State or 'R-state' declaring minor versions.
E.g. different types of components or new boot SW. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..7) |
|
| functionDesignationDIF |
1.3.6.1.4.1.193.72.300.1.1.10.5.3 |
| Number with reference to the handling and use of the product. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(0..12) |
|
| dateOfProductionDIF |
1.3.6.1.4.1.193.72.300.1.1.10.5.4 |
| 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. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| dateOfRepairDIF |
1.3.6.1.4.1.193.72.300.1.1.10.5.5 |
| 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. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| productionSerialNumberDIF |
1.3.6.1.4.1.193.72.300.1.1.10.5.6 |
| Unique serial number, describing the product in terms of a manufacturing
site code and a sequence number. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(13) |
|
| layoutVersionCodeDIF |
1.3.6.1.4.1.193.72.300.1.1.10.5.7 |
| The data layout version that allows the possibility
to interpret stored data differently. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| idCheckSumDIF |
1.3.6.1.4.1.193.72.300.1.1.10.5.8 |
| CRC32 Checksum of identification data for the DIF board. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(4) |
|
| localMacAddrMP |
1.3.6.1.4.1.193.72.300.1.1.11.1 |
| Unique MAC address of the IP DSLAM. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
MacAddress |
|
|
| phyModeMP |
1.3.6.1.4.1.193.72.300.1.1.11.2 |
| 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
|
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
PhyModeType |
|
|
| watchDogEnableMP |
1.3.6.1.4.1.193.72.300.1.1.11.3 |
| Enabling of the HW Watchdog.
If 0 (zero), the watchdog is OFF,
else the watchdog is ON. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
off(0), on(1) |
|
| vlanIdMP |
1.3.6.1.4.1.193.72.300.1.1.11.5 |
| The VLAN ID setting for the management VLAN. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..4095 |
|
| vlanPrioMP |
1.3.6.1.4.1.193.72.300.1.1.11.6 |
| Specifies the IEEE 802.1Q priority used for the management VLAN. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..7 |
|
| vlanTaggingMP |
1.3.6.1.4.1.193.72.300.1.1.11.7 |
| If 0, VLAN tagging is off, meaning that VLAN is not used.
If 1, VLAN tagging is used, with the given ID and Prio. |
| Status: deprecated |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
off(0), on(1) |
|
| bootStringMP |
1.3.6.1.4.1.193.72.300.1.1.11.8 |
| Text commands for the bootloader. |
| Status: deprecated |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
Size(0..255) |
|
| numberOfLines |
1.3.6.1.4.1.193.72.300.1.1.13.1 |
| Number of subscriber lines supported by this IP DSLAM. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..10 |
|
| remoteStorageFTPServerIPMP |
1.3.6.1.4.1.193.72.300.1.1.14.1 |
| The IP Address of FTP server to be used with the remote storage area.
The value can be any IP address |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
IpAddress |
|
|
| remoteStorageFilePathMP |
1.3.6.1.4.1.193.72.300.1.1.14.2 |
| The path to the remote storage file. The path should be relatetive to home of the
FTP server. (I.e. Files/MPRemoteStorageFiles where the 'Files' directory is can be
reached from home through the FTP server. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(1..255) |
|
| remoteStorageFTPUserMP |
1.3.6.1.4.1.193.72.300.1.1.14.3 |
| The user name which should be used by the IP DSLAM to access
the remote storage ftp server. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(1..255) |
|
| remoteStorageFTPPasswordMP |
1.3.6.1.4.1.193.72.300.1.1.14.4 |
| The password which should be used by the IP DSLAM to access
the remote storage ftp server. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
Size(1..255) |
|
| remoteStorageTrafficInfoTimeMP |
1.3.6.1.4.1.193.72.300.1.1.14.5 |
| The time interval for periodically triggering a backup of the
remote storage file. All traffic counters will be backed up with
remote storage. This includes total number of send bytes, total
number of send frames, total number of received bytes and total
number of received frames for each PVC.
Valid range is 0 - 24 hours. 0 means disabled |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..24 |
|
| remoteStorageTrafficInfoSizeMP |
1.3.6.1.4.1.193.72.300.1.1.14.6 |
| The size interval for triggering a backup of the remote
storage file. Whenever x MBytes has been transfered on any PVC since
last backup all traffic counters will be backed up with remote
storage. This includes total number of send bytes, total
number of send frames, total number of received bytes and total
number of received frames for each PVC.
Valid range is 50 - 1000 MBytes. 0 means disabled
Note: Backup is limited to maximum once every minute |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0 | 50..1000 |
|
| multilinkMode |
1.3.6.1.4.1.193.72.300.1.1.15.1 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
singleLink(1), linkAggregation(2), redundantConfiguration(3) |
|
| multilinkPreferredInterface |
1.3.6.1.4.1.193.72.300.1.1.15.2 |
|
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).
This interface will be used in case of multilinkMode is set to
redundantConfiguration and the rootID is equal for the links. If
the rootIDs are different this value is ignored and the one with
highest priority (lowest cost) will be selected.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
0..2147483646 |
|
| multilinkInterfaceTable |
1.3.6.1.4.1.193.72.300.1.1.15.3 |
|
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).
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
MultilinkInterfaceEntry |
|
| multilinkForceManagementToUsePreferredInterface |
1.3.6.1.4.1.193.72.300.1.1.15.4 |
|
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.
|
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
enabled(1), disabled(2) |
|
| multilinkInterfaceEntry |
1.3.6.1.4.1.193.72.300.1.1.15.3.1 |
|
This is an entry of the multilinkInterfaceTable
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
MultilinkInterfaceEntry |
|
|
| multilinkInterfaceIndex |
1.3.6.1.4.1.193.72.300.1.1.15.3.1.1 |
|
This is the index to the multilinkInterfaceTable. The values
are the same as used in the IF-MIB (1-based).
|
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
InterfaceIndex |
1..2147483647 |
|
| multilinkIsForwarding |
1.3.6.1.4.1.193.72.300.1.1.15.3.1.2 |
|
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).
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| multilinkIsUp |
1.3.6.1.4.1.193.72.300.1.1.15.3.1.3 |
|
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.).
|
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| traps |
1.3.6.1.4.1.193.72.300.1.2.0 |
| OBJECT IDENTIFIER |
|
|
|
| temperatureTooHigh |
1.3.6.1.4.1.193.72.300.1.2.0.1 |
| The temperature is too high and 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.
Corrective Actions:
- Check that the fans for the device is working properly.
- Check that the environment temperature is acceptable.
- For the IPDSLAM it might help to remove some subscibers from the lines.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Critical
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause temperatureUnacceptable
8: Temp control state [Low, Normal, High or TooHigh]
9: Temperature value [Value in degree Celsius]
Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.2 # temperatureTooHighCeasing
Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.8 # IP DLSAM RestartAlarm
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| temperatureTooHighCeasing |
1.3.6.1.4.1.193.72.300.1.2.0.2 |
| The too high temperature has ceased and 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 an increased temperature.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Ceasing
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause ThresholdCrossed
8: Temp control state [Low, Normal, High or TooHigh]
9: Temperature value [Value in degree Celsius]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| stateEventError |
1.3.6.1.4.1.193.72.300.1.2.0.4 |
| A state/event SW error has been detected on the device. This trap is seen
if the IPDSLAM is discarding a message that it did not know how to handle.
This kind of problem is sometimes related to an unforeseen state in the IP DSLAM.
Corrective Actions:
- Save the alarm information to a file, e.g. using a screenshot. It has to show
all the trap parameters.
- Give a brief explanation to how the error was provoked. If it can be provoked
again, then it is important for the Ericsson support team to know how this is done.
- Create a trouble report, which includes the log files, and send it to Ericsson support.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Major
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type ProcessingErrorAlarm
7: Probable cause SoftwareError
8: Process name [Name of DMAPI task]
9: Process state [DMAPI task state]
10: File name [The file name from where the alarm was sent]
11: Line no [The line number in the specified file]
12: Sender task [The task name of the task sending the message]
13: Message id [Internal message number]
14: Message data [Message content - hex bytes]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| nonFatalSoftwareError |
1.3.6.1.4.1.193.72.300.1.2.0.5 |
| A non-fatal SW error has been detected on the device. This type of software
error is normally not fatal for your system, It could be a configuration error
or a minor problem in the software, so do not panic if this alarm is seen.
Corrective Actions:
- Save the alarm information to a file, e.g. using a screenshot. It has to show
all the trap parameters.
- Give a brief explanation to how the error was provoked. If it can be provoked
again, then it is important for the Ericsson support team to know how this is done.
- Create a trouble report, which includes the log files, and send it to Ericsson support.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Major
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type ProcessingErrorAlarm
7: Probable cause SoftwareError
8: Process name [Name of DMAPI task]
9: Process state [DMAPI task state]
10: File name [The file name from where the alarm was sent]
11: Line no [The line number in the specified file]
12: Error code [Additional error information]
13: Error data [Additional data related to the error - hex bytes]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| fatalSoftwareError |
1.3.6.1.4.1.193.72.300.1.2.0.6 |
| A fatal SW error has been detected on your device. The device will now restart
in order to recover. This type of error is very serious and if it is seen in your
system, then it is important that it is handled right away.
Corrective Actions:
- Save the alarm information to a file, e.g. using a screenshot. It has to show
all the trap parameters.
- Give a brief explanation to how the error was provoked. If it can be provoked
again, then it is important for the Ericsson support team to know how this is done.
- Create a trouble report which includes the log files and send it to Ericsson support.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Critical
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type ProcessingErrorAlarm
7: Probable cause SoftwareError
8: Process name [Name of DMAPI task]
9: Process state [DMAPI task state]
10: File name [The file name from where the alarm was sent]
11: Line no [The line number in the specified file]
12: Error code [Additional error information]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| configurationFileError |
1.3.6.1.4.1.193.72.300.1.2.0.7 |
| The configuration file which the device is using failed to pass or load.
Corrective Actions:
- Check that the device can reach the server where the configuration file is located.
- Check that the configuration is physically located on the server.
- Check that the configuration file does not contain any syntax errors.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Critical
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type ProcessingErrorAlarm
7: Probable cause FileError
8: Error code [Additional error information]
Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.8 # restartAlarm
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| modemPoolRestartAlarm |
1.3.6.1.4.1.193.72.300.1.2.0.8 |
| The IP DSLAM has restarted. The post mortem information will indicate the
reason for the restart.
If the device has restarted from an unknown reason, then it is strongly
advised that you contact Ericsson support, which will help you do make
the necessary logs. A trace is very valuable for the Ericsson support team
in case an error correction has to be made. The trace should afterwards be
sent for further investigations.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Major
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause Other
8: Post mortem info [reason for the restart]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| fanGreenFailure |
1.3.6.1.4.1.193.72.300.1.2.0.9 |
| Indicates that the fan located near to the green LED has failed. This means that the
fan control cannot secure that the temperature is kept in the normal state in the
worst-case scenario (e.g. high environmental temperature, high traffic).
Corrective Actions:
- Replace the fan.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Major
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause CoolingFanFailure
8: Fan green status Failed
Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.10 # fanGreenCeasing
Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.8 # IP DLSAM RestartAlarm
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| fanGreenCeasing |
1.3.6.1.4.1.193.72.300.1.2.0.10 |
| Indicates the ceasing of the fan, which is located near to the green LED.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Ceasing
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause CoolingFanFailure
8: Fan green status Failed
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| fanRedFailure |
1.3.6.1.4.1.193.72.300.1.2.0.11 |
| Indicates that the fan located near to the red LED has failed, This means that the fan
control cannot secure that the temperature is kept in the normal state in the worst-case
scenario (e.g. high environmental temperature, high traffic).
Corrective Actions:
- Replace the fan.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Major
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause CoolingFanFailure
8: Fan red status Failed
Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.12 # redFanCeasing
Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.8 # IP DSLAM RestartAlarm
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| fanRedCeasing |
1.3.6.1.4.1.193.72.300.1.2.0.12 |
| Indicates the ceasing of the fan which is located near to the red LED.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Ceasing
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause CoolingFanFailure
8: Fan red status Failed
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| idDataReadError |
1.3.6.1.4.1.193.72.300.1.2.0.13 |
| This alarm indicates that the identification data the device has in flash memory
is corrupted. Identification data could be parameters like 'product number',
'revision state', 'date of repair' in other words data that is loaded to
the device when it is manufactured.
The 'hwUnitId' parameter in the alarm shows which type of unit that is corrupted
in the flash memory.
Corrective Actions:
- Save the alarm information to a file, e.g. using a screenshot. It has to show
all the trap parameters.
- Give a brief explanation to how the error was provoked. If it can be provoked
again, then it is important for the Ericsson support team to know how this is done.
- Send the trouble report and the physical device to Ericsson support for further
investigations.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Major
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause InformationMissing
8: HwUnit [device, MicroProcessorBoard, FrontAnalogueBoard or ddcBoard]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| cfgDataReadError |
1.3.6.1.4.1.193.72.300.1.2.0.14 |
| This alarm indicates that the configuration data it has in flash is corrupted.
Configuration data could be parameters like 'local mac address', 'phy mode', 'vlan id',
'vlan tagging' etc.
The 'configData' parameter in the alarm shows which data that is corrupted.
Corrective Actions:
- Give it a valid configuration data and reboot the device.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Major
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause InformationMissing
8: CfgData [localMacAddr, phyMode, watchdogEnable, vlanInfo or bootString]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| writeFlashError |
1.3.6.1.4.1.193.72.300.1.2.0.15 |
| Indicates that an error occurred during the writing to the flash memory.
Corrective Actions:
- Try to restart the device and if the error keeps appearing then replace the
device with a new unit.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Major
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause CorruptData
8: idOrCfgData [The configuration item, which failed writing to FLASH]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| bothFansFailure |
1.3.6.1.4.1.193.72.300.1.2.0.16 |
| Indicates that both fans on the device have failed. This means that the fan control
cannot secure that the temperature is kept in the normal state in the worst-case
scenario (e.g. high environmental temperature, high traffic).
Corrective Actions:
- Replace the fans of the device.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Critical
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause CoolingFanFailure
8: Fan green status Failed
9: Fan red status Failed
Ceasing OID: 1.3.6.1.4.1.193.72.600.1.2.0.16 # bothFansFailed
Ceasing OID: 1.3.6.1.4.1.193.72.600.1.2.0.7 # restartAlarm
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| bothFansCeasing |
1.3.6.1.4.1.193.72.300.1.2.0.17 |
| Indicates that at least one of the fans is working again. This means that the
fan control cannot secure that the temperature is kept in the normal state in
the worst-case scenario (e.g. high environmental temperature, high traffic).
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Ceasing
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause CoolingFanFailure
8: Fan green status [Failed, Working]
9: Fan red status [Failed, Working]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| modemPoolTypeUnknown |
1.3.6.1.4.1.193.72.300.1.2.0.18 |
| Indicates that the device type can not be identified. The product number and
revision state are either unkonwn or corrupted. The application software cannot handle
its hardware correctly.
Corrective Actions:
- Reinstall the device in the management system.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Critical
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause Other
8: Product number MP Product number of the device
9: Revision state MP Revision state of the device
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| temperatureCloseToTooHigh |
1.3.6.1.4.1.193.72.300.1.2.0.23 |
| Indicates the temperature is close to the too high value. This alarm should be
considered as a warning alarm that is received a while before the high temperature
is reached.
Corrective Actions:
- Check that the fans for the device are working properly.
- Check that the environment temperature is acceptable.
- For the IPDSLAM it might help to remove some subscribers from the line.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Major
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause TemperatureUnacceptable
8: Temperature value [Value in degree Celsius]
Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.24 # tempCloseToTooHighCeasing
Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.8 # IP DSLAM RestartAlarm
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| temperatureCloseToTooHighCeasing |
1.3.6.1.4.1.193.72.300.1.2.0.24 |
| Indicates that the temperatureCloseToTooHigh alarm is no longer active. The
temperature has been successfully reduced to level where the device can work normal.
Deprecated from: EDA 1.1 R2A
Parameters
1: Managed object class IPDSLAM
2: Managed object ID [MAC]
3: Sequence number [Alarm sequence number]
4: Perceived severity Ceasing
5: Event time [Timestamp is retrieved from a SNTP server]
6: Event type Equipment
7: Probable cause TemperatureUnacceptable
8: Temperature value [Value in degree Celsius]
|
| Status: deprecated |
Access: read-only |
| NOTIFICATION-TYPE |
|
|
|
| processName |
1.3.6.1.4.1.193.72.300.1.2.1.1 |
| The name of the process which sent the alarm. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| processState |
1.3.6.1.4.1.193.72.300.1.2.1.2 |
| The state of the process which sent the alarm. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| fileName |
1.3.6.1.4.1.193.72.300.1.2.1.3 |
| The file name from where the alarm was sent |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| lineNo |
1.3.6.1.4.1.193.72.300.1.2.1.4 |
| The line number in the file indicated by fileName,
from where the alarm was sent |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| senderTask |
1.3.6.1.4.1.193.72.300.1.2.1.5 |
| Indicates the name of the task which sent the message
causing a stateEventErrror. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| errorCode |
1.3.6.1.4.1.193.72.300.1.2.1.6 |
| Additional error information. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| errorData |
1.3.6.1.4.1.193.72.300.1.2.1.8 |
| Additional data related to the error. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
|
|
| messageId |
1.3.6.1.4.1.193.72.300.1.2.1.9 |
| Message ID of the last received message.
E.g. the ID of the message causing a state event error. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| messageData |
1.3.6.1.4.1.193.72.300.1.2.1.10 |
| Message content of the last received message. E.g.
the content of the message causing a state event error. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
OCTET STRING |
|
|
| hwUnit |
1.3.6.1.4.1.193.72.300.1.2.1.11 |
| Identifies the HW unit which has the identification
data corrupted into FLASH. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
modemPool(1), dupBoard(2), dafeBoard(3), ddcBoard(4) |
|
| cfgData |
1.3.6.1.4.1.193.72.300.1.2.1.12 |
| Identifies the corrupted configuration data read from FLASH for
the IP DSLAM. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
localMacAddr(1), phyMode(2), watchdogEnable(3), vlanInfo(4), bootString(5) |
|
| idOrCfgData |
1.3.6.1.4.1.193.72.300.1.2.1.13 |
| Identifies during which data writing occured an error. |
| Status: deprecated |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
INTEGER |
ipdslamIdData(1), dupBoardIdData(2), dafeBoardIdData(3), ddcBoardIdData(4), localMacAddr(5), phyMode(6), watchdogEnable(7), vlanInfo(8), bootString(9) |
|