PEA-EQUIPMENT-IPDSLAM: View SNMP OID List / Download MIB

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.

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.

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. Enumeration: 'restart': 1.

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.

The temperature value in the IP DSLAM in grade Celsius.

The status of the fan which is placed closest to the green LED. Enumeration: 'failed': 0, 'working': 1.

The status of the fan which is placed closest to the red LED. Enumeration: 'failed': 0, 'working': 1.

The speed of the fan which is placed closest to the green LED measured in rpm (rotations per minute).

The speed of the fan which is placed closest to the red LED measured in rpm (rotations per minute).

When the ledsAlternativeBlink is set to ON(1) the LEDs will start to blink alternatively. Enumeration: 'on': 1, 'off': 0.

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. Enumeration: 'on': 1, 'off': 0.

The percentage of time that the main processor was not idle. Average over 10 seconds. (almost like hrProcessorLoad in RFC1514).

The amount of free memory on main processor in percent.

The amount of free memory on main processor in bytes.

The total number of memory buffers currently used (Ethernet, ATM & local IP-stack).

This value includes the full name and version identification of the IP DSLAM software.

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.

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.

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.

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.

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.

Index number that identifies the IP DSLAM hardware unit.

Revision State or 'R-state' declaring minor versions. E.g. different types of components or new boot SW.

Number with reference to the handling and use of the product.

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.

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.

Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.

The data layout version that allows the possibility to interpret stored data differently.

CRC32 Checksum of identification data structure of the IP DSLAM.

Index number that identifies the DUP board.

Revision State or 'R-state' declaring minor versions. E.g. different types of components or new boot SW.

Number with reference to the handling and use of the product.

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.

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.

Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.

The data layout version that allows the possibility to interpret stored data differently.

CRC32 Checksum of identification data structure for the DUP board.

Index number that identifies the DAFE board.

Revision State or 'R-state' declaring minor versions. E.g. different types of components or new boot SW.

Number with reference to the handling and use of the product.

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.

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.

Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.

The data layout version that allows the possibility to interpret stored data differently.

CRC32 Checksum of identification data structure for the DAFE board.

Index number that identifies the DDC board.

Revision State or 'R-state' declaring minor versions. E.g. different types of components or new boot SW.

Number with reference to the handling and use of the product.

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.

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.

Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.

The data layout version that allows the possibility to interpret stored data differently.

CRC32 Checksum of identification data for the DDC board.

Index number that identifies the DIF board.

Revision State or 'R-state' declaring minor versions. E.g. different types of components or new boot SW.

Number with reference to the handling and use of the product.

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.

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.

Unique serial number, describing the product in terms of a manufacturing site code and a sequence number.

The data layout version that allows the possibility to interpret stored data differently.

CRC32 Checksum of identification data for the DIF board.

Unique MAC address of the IP DSLAM.

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

Enabling of the HW Watchdog. If 0 (zero), the watchdog is OFF, else the watchdog is ON. Enumeration: 'on': 1, 'off': 0.

The VLAN ID setting for the management VLAN.

Specifies the IEEE 802.1Q priority used for the management VLAN.

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.

Text commands for the bootloader.

This value includes the full name and version identification of the BOOT software.

Number of subscriber lines supported by this IP DSLAM.

The IP Address of FTP server to be used with the remote storage area. The value can be any IP address

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.

The user name which should be used by the IP DSLAM to access the remote storage ftp server.

The password which should be used by the IP DSLAM to access the remote storage ftp server.

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

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

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.

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.

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).

This is an entry of the multilinkInterfaceTable

This is the index to the multilinkInterfaceTable. The values are the same as used in the IF-MIB (1-based).

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).

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.).

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.

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

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]

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]

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]

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]

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

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]

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

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

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

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

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]

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]

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]

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

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]

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

Indicates that the fan located near the green LED has a low performance. 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 next time you get near the device, since it will soon break. 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, Working] 9: Fan green speed [The speed of the fan measured in rotations per minute] Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.20 # fanGreenLowPerformanceCeasing Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.8 # IP DSLAM RestartAlarm

Indicates that the low performance of the green fan, which is the one located near the green LED, has ceased. If this ceasing alarm is seen frequently on a device in your system, then you should find a way to replace the fan, which causes problems. 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 Working 9: Fan green speed [The speed of the fan measured in rotations per minute]

Indicates that the fan located near the red LED has a low performance. 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 next time you get near the device, since it will soon break. 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, Working] 9: Fan red speed [The speed of the fan measured in rotations per minute] Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.22 # fanRedLowPerformanceCeasing Ceasing OID: 1.3.6.1.4.1.193.72.300.1.2.0.8 # IP DSLAM RestartAlarm

Indicates that the low performance of the red fan, which is the one located near the red LED, has ceased. If this ceasing alarm is seen frequently on a device in your system, then you should find a way to replace the fan, which causes problems. 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 Working 9: Fan red speed [The speed of the fan measured in rotations per minute]

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

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]

The name of the process which sent the alarm.

The state of the process which sent the alarm.

The file name from where the alarm was sent

The line number in the file indicated by fileName, from where the alarm was sent

Indicates the name of the task which sent the message causing a stateEventErrror.

Additional error information.

Indicates the reason of the restart.

Additional data related to the error.

Message ID of the last received message. E.g. the ID of the message causing a state event error.

Message content of the last received message. E.g. the content of the message causing a state event error.

Identifies the HW unit which has the identification data corrupted into FLASH. Enumeration: 'modemPool': 1, 'dafeBoard': 3, 'dupBoard': 2, 'ddcBoard': 4.

Identifies the corrupted configuration data read from FLASH for the IP DSLAM. Enumeration: 'bootString': 5, 'watchdogEnable': 3, 'localMacAddr': 1, 'phyMode': 2, 'vlanInfo': 4.

Identifies during which data writing occured an error. Enumeration: 'bootString': 9, 'localMacAddr': 5, 'vlanInfo': 8, 'watchdogEnable': 7, 'ipdslamIdData': 1, 'dupBoardIdData': 2, 'dafeBoardIdData': 3, 'phyMode': 6, 'ddcBoardIdData': 4.

Objects for the peaEquipmentIpDslamObjects Group

Objects for the peaEquipmentIpDslamObjects Group

Deprecated Notifications Group