CHASSIS
CpmIcPortSFFStatusDDMCorrupt
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4012 |
Event name | CpmIcPortSFFStatusDDMCorrupt |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.7 |
Default severity | minor |
Message format string | CPM interconnect port SFF DDM checksums do not match |
Cause | The tmnxCpmIcPortSFFStatusFailure notification is generated when the value of tmnxCpmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. |
Effect | The SFF device is not operational and the associated CPM interconnect port can not be used. The SFF and port will not recover without operator intervention. |
Recovery | Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
CpmIcPortSFFStatusFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4011 |
Event name | CpmIcPortSFFStatusFailure |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.7 |
Default severity | minor |
Message format string | CPM interconnect port SFF checksums do not match |
Cause | The tmnxCpmIcPortSFFStatusFailure notification is generated when the value of tmnxCpmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. |
Effect | The SFF device is not operational and the associated CPM interconnect port can not be used. The SFF and port will not recover without operator intervention. |
Recovery | Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
CpmIcPortSFFStatusReadError
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4013 |
Event name | CpmIcPortSFFStatusReadError |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.7 |
Default severity | minor |
Message format string | CPM interconnect port SFF read failure |
Cause | The tmnxCpmIcPortSFFStatusFailure notification is generated when the value of tmnxCpmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. |
Effect | The SFF device is not operational and the associated CPM interconnect port can not be used. The SFF and port will not recover without operator intervention. |
Recovery | Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
CpmIcPortSFFStatusUnsupported
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4014 |
Event name | CpmIcPortSFFStatusUnsupported |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.7 |
Default severity | minor |
Message format string | CPM interconnect port SFF unsupported type |
Cause | The tmnxCpmIcPortSFFStatusFailure notification is generated when the value of tmnxCpmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. |
Effect | The SFF device is not operational and the associated CPM interconnect port can not be used. The SFF and port will not recover without operator intervention. |
Recovery | Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
SfmIcPortSFFStatusDDMCorrupt
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4022 |
Event name | SfmIcPortSFFStatusDDMCorrupt |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.5 |
Default severity | minor |
Message format string | SFM interconnect port SFF DDM checksums do not match |
Cause | The tmnxSfmIcPortSFFStatusFailure notification is generated when the value of tmnxSfmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. |
Effect | The SFF device is not operational and the associated SFM interconnect port can not be used. The SFF and port will not recover without operator intervention. |
Recovery | Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
SfmIcPortSFFStatusFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4021 |
Event name | SfmIcPortSFFStatusFailure |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.5 |
Default severity | minor |
Message format string | SFM interconnect port SFF checksums do not match |
Cause | The tmnxSfmIcPortSFFStatusFailure notification is generated when the value of tmnxSfmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. |
Effect | The SFF device is not operational and the associated SFM interconnect port can not be used. The SFF and port will not recover without operator intervention. |
Recovery | Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
SfmIcPortSFFStatusReadError
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4023 |
Event name | SfmIcPortSFFStatusReadError |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.5 |
Default severity | minor |
Message format string | SFM interconnect port SFF read failure |
Cause | The tmnxSfmIcPortSFFStatusFailure notification is generated when the value of tmnxSfmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. |
Effect | The SFF device is not operational and the associated SFM interconnect port can not be used. The SFF and port will not recover without operator intervention. |
Recovery | Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
SfmIcPortSFFStatusUnsupported
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4024 |
Event name | SfmIcPortSFFStatusUnsupported |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.5 |
Default severity | minor |
Message format string | SFM interconnect port SFF unsupported type |
Cause | The tmnxSfmIcPortSFFStatusFailure notification is generated when the value of tmnxSfmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. |
Effect | The SFF device is not operational and the associated SFM interconnect port can not be used. The SFF and port will not recover without operator intervention. |
Recovery | Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
tIPsecIsaMemHighWatermark
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2151 |
Event name | tIPsecIsaMemHighWatermark |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.138 |
Default severity | minor |
Message format string | The memory usage ratio for ISA $tmnxCardSlotNum$/$tmnxMDASlotNum$ has almost reached the maximum value. |
Cause | A tIPsecIsaMemHighWatermark notification is generated when the ISA card memory usage ratio has almost reached the maximum value. |
Effect | The system may stop accepting new IKE states shortly. |
Recovery | Use fewer SAs for each IKE tunnel. |
tIPsecIsaMemLowWatermark
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2150 |
Event name | tIPsecIsaMemLowWatermark |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.137 |
Default severity | minor |
Message format string | The memory usage ratio for ISA $tmnxCardSlotNum$/$tmnxMDASlotNum$ has dropped back to the normal level. |
Cause | A tIPsecIsaMemLowWatermark notification is generated when the ISA card memory usage ratio has dropped back to the normal level. |
Effect | The system accepts new IKE states. |
Recovery | There is no recovery required for this notification. |
tIPsecIsaMemMax
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2152 |
Event name | tIPsecIsaMemMax |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.139 |
Default severity | minor |
Message format string | The memory usage for ISA $tmnxCardSlotNum$/$tmnxMDASlotNum$ has reached the maximum value. |
Cause | A tIPsecIsaMemMax notification is generated when the ISA card memory usage ratio has reached the maximum value. |
Effect | The system stops accepting new IKE states. |
Recovery | Use fewer SAs for each IKE tunnel. |
tmnxAlarmInputVoltageFailure
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 3014 |
Event name | tmnxAlarmInputVoltageFailure |
SNMP notification prefix and OID | TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSASChassisNotification.10 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : alarm input voltage failure |
Cause | A tmnxAlarmInputVoltageFailure notification is sent when the internal power supply for alarm inputs fails. The value of tmnxSasAlarmInputPowerStatus indicates whether the power to external alarm inputs is on or off. |
Effect | If the alarm inputs use the internal power supply, then a failure in the power supply will cause state change event alarms to not be raised. |
Recovery | Check the internal power source for alarm inputs and rectify the problem. |
tmnxChassisHiBwMcastAlarm
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2052 |
Event name | tmnxChassisHiBwMcastAlarm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.43 |
Default severity | minor |
Message format string | Class $tmnxHwClass$ : Plane shared by multiple multicast high bandwidth taps |
Cause | The tmnxChassisHiBwMcastAlarm notification is generated when a plane is shared by more than one high bandwidth multicast tap. |
Effect | N/A |
|
Recovery | N/A |
tmnxChassisNotificationClear
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2016 |
Event name | tmnxChassisNotificationClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.25 |
Default severity | major |
Message format string | Clear $tmnxHwClass$ $tmnxHwIndex$ $tmnxChassisNotifyOID$ |
Cause | A trap indicating the clear of a chassis notification identified by tmnxChassisNotifyOID. |
Effect | N/A |
|
Recovery | N/A |
tmnxChassisUpgradeComplete
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2034 |
Event name | tmnxChassisUpgradeComplete |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.42 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : software upgrade complete |
Cause | The tmnxChassisUpgradeComplete notification is generated to indicate that all the IOMs are running matching software versions in reference to the active CPM software version changed as part of the upgrade process. |
Effect | N/A |
|
Recovery | N/A |
tmnxChassisUpgradeInProgress
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2033 |
Event name | tmnxChassisUpgradeInProgress |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.41 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : software upgrade in progress |
Cause | The tmnxChassisUpgradeInProgress notification is generated only after a CPM switchover occurs and the new active CPM is running new software, while the IOMs are still running old software. This is the start of the upgrade process. The tmnxChassisUpgradeInProgress notification will continue to be generated every 30 minutes while at least one IOM is still running older software. |
Effect | N/A |
|
Recovery | N/A |
tmnxCpmALocalIcPortAvail
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4009 |
Event name | tmnxCpmALocalIcPortAvail |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.6 |
Default severity | major |
Message format string | CPM $tmnxChassisNotifyCpmCardSlotNum$ can reach the chassis using its local CPM interconnect ports |
Cause | The tmnxCpmLocalIcPortAvail notification is generated when the CPM re-establishes communication with the other chassis using its local CPM interconnect ports. |
Effect | A new control communications path is now available between the CPM and the other chassis. |
Recovery | N/A |
tmnxCpmANoLocalIcPort
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4007 |
Event name | tmnxCpmANoLocalIcPort |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.5 |
Default severity | major |
Message format string | CPM $tmnxChassisNotifyCpmCardSlotNum$ can not reach the chassis using its local CPM interconnect ports |
Cause | The tmnxCpmNoLocalIcPort alarm is generated when the CPM cannot reach the other chassis using its local CPM interconnect ports. |
Effect | Another control communications path may still be available between the CPM and the other chassis via the mate CPM in the same chassis. If that alternative path is not available then complete disruption of control communications to the other chassis will occur and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the active CPM indicates that a further failure of the local CPM interconnect ports on the standby CPM will cause complete disruption of control communications to the other chassis and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the standby CPM indicates that a CPM switchover may cause temporary disruption of control communications to the other chassis while the rebooting CPM comes back into service. |
Recovery | Ensure that all CPM interconnect ports in the system are properly cabled together with working cables. |
tmnxCpmBLocalIcPortAvail
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4010 |
Event name | tmnxCpmBLocalIcPortAvail |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.6 |
Default severity | major |
Message format string | CPM $tmnxChassisNotifyCpmCardSlotNum$ can reach the chassis using its local CPM interconnect ports |
Cause | The tmnxCpmLocalIcPortAvail notification is generated when the CPM re-establishes communication with the other chassis using its local CPM interconnect ports. |
Effect | A new control communications path is now available between the CPM and the other chassis. |
Recovery | N/A |
tmnxCpmBNoLocalIcPort
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4008 |
Event name | tmnxCpmBNoLocalIcPort |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.5 |
Default severity | major |
Message format string | CPM $tmnxChassisNotifyCpmCardSlotNum$ can not reach the chassis using its local CPM interconnect ports |
Cause | The tmnxCpmNoLocalIcPort alarm is generated when the CPM cannot reach the other chassis using its local CPM interconnect ports. |
Effect | Another control communications path may still be available between the CPM and the other chassis via the mate CPM in the same chassis. If that alternative path is not available then complete disruption of control communications to the other chassis will occur and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the active CPM indicates that a further failure of the local CPM interconnect ports on the standby CPM will cause complete disruption of control communications to the other chassis and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the standby CPM indicates that a CPM switchover may cause temporary disruption of control communications to the other chassis while the rebooting CPM comes back into service. |
Recovery | Ensure that all CPM interconnect ports in the system are properly cabled together with working cables. |
tmnxCpmCardSyncFileNotPresent
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2057 |
Event name | tmnxCpmCardSyncFileNotPresent |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.45 |
Default severity | minor |
Message format string | Class $tmnxHwClass$ : Optional file $tmnxChassisNotifyCardSyncFile$ is not present during sync operation |
Cause | The tmnxCpmCardSyncFileNotPresent notification is generated when the redundancy file synchronization failed to locate an optional file. |
Effect | N/A |
|
Recovery | N/A |
tmnxCpmIcPortDDMClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4016 |
Event name | tmnxCpmIcPortDDMClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.9 |
Default severity | minor |
Message format string | CPM interconnect port SFF DDM $tmnxDDMLaneIdOrModule$ ($tmnxDDMFailedObject$) cleared |
Cause | The tmnxCpmIcPortDDMFailure notification is generated when an SFF in a CPM interconnect port that supports Digital Diagnostic Monitoring (DDM) clears a failed state. |
Effect | N/A |
|
Recovery | N/A |
tmnxCpmIcPortDDMFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4015 |
Event name | tmnxCpmIcPortDDMFailure |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.8 |
Default severity | minor |
Message format string | CPM interconnect port SFF DDM $tmnxDDMLaneIdOrModule$ ($tmnxDDMFailedObject$) raised |
Cause | The tmnxCpmIcPortDDMFailure notification is generated when an SFF in a CPM interconnect port that supports Digital Diagnostic Monitoring (DDM) enters a failed state. |
Effect | N/A |
|
Recovery | N/A |
tmnxCpmIcPortDown
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4003 |
Event name | tmnxCpmIcPortDown |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.1 |
Default severity | minor |
Message format string | CPM interconnect port is not operational. Error code = $tmnxCpmIcPortOperState$ |
Cause |
The tmnxCpmIcPortDown alarm is generated when the CPM interconnect port is not operational. The reason may be a cable connected incorrectly, a disconnected cable, a faulty cable, or a misbehaving CPM interconnect port or card. |
Effect | At least one of the control plane paths used for inter-chassis CPM communication is not operational. Other paths may be available. |
Recovery | A manual verification and testing of each CPM interconnect port is required to ensure fully functional operation. Physical replacement of cabling may be required. |
tmnxCpmIcPortSFFInserted
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4005 |
Event name | tmnxCpmIcPortSFFInserted |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.3 |
Default severity | minor |
Message format string | CPM interconnect port SFF inserted |
Cause | The tmnxCpmIcPortSFFInserted notification is generated when the small form factor (SFF) pluggable optical module (eg. QSFP) is inserted into a CPM interconnect port. |
Effect | This event is for notification only. |
Recovery | N/A |
tmnxCpmIcPortSFFRemoved
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4006 |
Event name | tmnxCpmIcPortSFFRemoved |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.4 |
Default severity | minor |
Message format string | CPM interconnect port SFF removed |
Cause | The tmnxCpmIcPortSFFRemoved notification is generated when the SFF (eg. QSFP) is removed from the CPM interconnect port. Removing an SFF causes both this trap, and also a tmnxCpmIcPortDown event. |
Effect | Removing the SFF will cause the CPM interconnect port to go down. This port will no longer be able to be used as part of the control plane between chassis but other paths may be available. |
Recovery | Insert a working SFF into the port. |
tmnxCpmIcPortUp
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4004 |
Event name | tmnxCpmIcPortUp |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxCpmIcPortNotifications.2 |
Default severity | minor |
Message format string | CPM interconnect port is operational |
Cause | The tmnxCpmIcPortUp notification is generated when the CPM interconnect port is operational again. |
Effect | A control plane communication path between CPM cards in the different chassis have been established. |
Recovery | N/A |
tmnxCpmMemSizeMismatch
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2153 |
Event name | tmnxCpmMemSizeMismatch |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.140 |
Default severity | major |
Message format string | The standby CPM $tmnxChassisNotifyCpmCardSlotNum$ has a different memory size than the active $tmnxChassisNotifyHwIndex$ |
Cause |
A tmnxCpmMemSizeMismatch notification is generated when the RAM memory size of the standby CPM (i.e., tmnxChassisNotifyCpmCardSlotNum) is different than the active CPM (i.e., tmnxChassisNotifyHwIndex). |
Effect | There is an increased risk of the memory overflow on the standby CPM during the CPM switchover. |
Recovery | Use CPMs with the same memory size. |
tmnxCpmMemSizeMismatchClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2154 |
Event name | tmnxCpmMemSizeMismatchClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.141 |
Default severity | cleared |
Message format string | The standby CPM $tmnxChassisNotifyCpmCardSlotNum$ has the same memory size as the active $tmnxChassisNotifyHwIndex$ |
Cause |
A tmnxCpmMemSizeMismatchClear notification is generated when the RAM memory sizes of the standby (i.e., tmnxChassisNotifyCpmCardSlotNum) and active (i.e., tmnxChassisNotifyHwIndex) CPMs become matched. |
Effect | The tmnxCpmMemSizeMismatch notification is cleared. |
Recovery | There is no recovery required for this notification. |
tmnxDcpCardFpEventOvrflw
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2084 |
Event name | tmnxDcpCardFpEventOvrflw |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.72 |
Default severity | minor |
Message format string | TODO |
Cause | The tmnxDcpCardFpEventOvrflw notification is generated when a flood of distibuted CPU FP protection events occur on a particular card and some of the events are lost due to event throttling mechanism. |
Effect | Some FP notifications configured on the card may not be received. |
Recovery | Notifications will resume once the event throttling ends. |
tmnxDcpCardFpEventOvrflwClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2089 |
Event name | tmnxDcpCardFpEventOvrflwClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.77 |
Default severity | minor |
Message format string | TODO |
Cause | The tmnxDcpCardFpEventOvrflwClr notification is generated when the event throttling has ended for distibuted CPU protection FP events on a particular card. |
Effect | Notifications are received again since the event throttling has ended. |
Recovery | There is no recovery for this notification. |
tmnxDcpCardSapEventOvrflw
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2085 |
Event name | tmnxDcpCardSapEventOvrflw |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.73 |
Default severity | minor |
Message format string | TODO |
Cause | The tmnxDcpCardSapEventOvrflw notification is generated when a flood of distibuted CPU protection SAP events occur on a particular card and some of the events are lost due to event throttling mechanism. |
Effect | Some SAP notifications configured on the card may not be received. |
Recovery | Notifications will resume once the event throttling ends. |
tmnxDcpCardSapEventOvrflwClr
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2090 |
Event name | tmnxDcpCardSapEventOvrflwClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.78 |
Default severity | minor |
Message format string | TODO |
Cause | The tmnxDcpCardSapEventOvrflwClr notification is generated when the event throttling has ended for distibuted CPU protection SAP events on a particular card. |
Effect | Notifications are received again since the event throttling has ended. |
Recovery | There is no recovery for this notification. |
tmnxDcpCardVrtrIfEventOvrflw
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2086 |
Event name | tmnxDcpCardVrtrIfEventOvrflw |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.74 |
Default severity | minor |
Message format string | TODO |
Cause | The tmnxDcpCardVrtrIfEventOvrflw notification is generated when a flood of distibuted CPU protection network-interface events occur on a particular card and some of the events are lost due to event throttling mechanism. |
Effect | Some network-interface notifications configured on the card may not be received. |
Recovery | Notifications will resume once the event throttling ends. |
tmnxDcpCardVrtrIfEventOvrflwClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2091 |
Event name | tmnxDcpCardVrtrIfEventOvrflwClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.79 |
Default severity | minor |
Message format string | TODO |
Cause | The tmnxDcpCardVrtrIfEventOvrflwClr notification is generated when the event throttling has ended for distibuted CPU protection networrk-interface events on a particular card. |
Effect | Notifications are received again since the event throttling has ended. |
Recovery | There is no recovery for this notification. |
tmnxDcpFpDynPoolUsageHiAlmClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2088 |
Event name | tmnxDcpFpDynPoolUsageHiAlmClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.76 |
Default severity | minor |
Message format string | TODO |
Cause | The tmnxDcpFpDynPoolUsageHiAlmClear notification is generated when the dynamic enforcement policer pool usage on the forwarding plane is no longer exhausted. |
Effect | Dynamic enforcement policers are available in the free pool to be allocated when needed. |
Recovery | There is no recovery required for this notification. |
tmnxDcpFpDynPoolUsageHiAlmRaise
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2087 |
Event name | tmnxDcpFpDynPoolUsageHiAlmRaise |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.75 |
Default severity | minor |
Message format string | TODO |
Cause | The tmnxDcpFpDynPoolUsageHiAlmRaise notification is generated when the dynamic enforcement policer pool usage on the forwarding plane is nearly exhausted. |
Effect | Dynamic enforcement policers may not get allocated on the forwarding plane. |
Recovery | This notification will be cleared when either the dynamic enforcement policer pool is increased or the usage drops. |
tmnxEnvTempTooHigh
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2005 |
Event name | tmnxEnvTempTooHigh |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.2 |
Default severity | major |
Message format string | $tmnxHwClass$ $tmnxChassisNotifyHwIndex$: temperature too high |
Cause | N/A |
|
Effect | N/A |
Recovery |
N/A |
tmnxEqCardChipIfCellEvent
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2103 |
Event name | tmnxEqCardChipIfCellEvent |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.90 |
Default severity | minor |
Message format string | Possible messages:
|
Cause |
The tmnxEqCardChipIfCellEvent notification is generated when an inter-chip interface (XPL2 bundle) experiences internal datapath cell errors. |
Effect | Contact Nokia customer support. |
Recovery | Contact Nokia customer support. |
tmnxEqCardChipIfDownEvent
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2102 |
Event name | tmnxEqCardChipIfDownEvent |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.89 |
Default severity | minor |
Message format string | Possible messages:
|
Cause |
The tmnxEqCardChipIfDownEvent notification is generated when an inter-chip interface (XPL2 bundle) experiences an internal datapath problem. |
Effect | Contact Nokia customer support. |
Recovery | Contact Nokia customer support. |
tmnxEqCardFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2001 |
Event name | tmnxEqCardFailure |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.7 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : failed, reason: $tmnxChassisNotifyCardFailureReason$ |
|
Cause | Generated when one of the cards in a chassis has failed. The card type may be IOM, Fabric, MDA, MCM, CCM, CPM module, compact flash module, etc. tmnxChassisNotifyCardFailureReason contains the reason for card failure. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqCardFirmwareUpgraded
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2032 |
Event name | tmnxEqCardFirmwareUpgraded |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.40 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : firmware upgraded |
Cause | Generated when a card is hot-inserted into the chassis and its firmware is automatically upgraded. The card type may be IOM or CPM module. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqCardInserted
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2002 |
Event name | tmnxEqCardInserted |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.8 |
Default severity | minor |
Message format string | Class $tmnxHwClass$ : inserted |
Cause | Generated when a card is inserted into the chassis. The card type may be IOM, Fabric, MDA, MCM, CCM CPM module, compact flash module, etc. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqCardPChipCamEvent
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2076 |
Event name | tmnxEqCardPChipCamEvent |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.64 |
Default severity | critical |
Message format string | A fault has been detected in the hardware on IOM $tmnxSlotNum$-forwarding engine $tmnxCardComplexNumber$: Please contact Nokia support |
Cause | The tmnxEqCardPChipCamEvent notification is generated when either an IOM or a CPM experiences a persistent occurrence of a PChip CAM error. On a CPM card, the tmnxCardComplexNumber will be fixed to the value zero (0). |
Effect | N/A |
|
Recovery | N/A |
tmnxEqCardPChipError
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2059 |
Event name | tmnxEqCardPChipError |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.47 |
Default severity | minor |
Message format string | Slot $tmnxCardSlotNum$ detected $tmnxCardFwdDirection$ FCS errors on complex $tmnxCardComplexNumber$. Source card(s) of detected errors: $tmnxCardSrcSlotBitmap$ |
Cause |
The tmnxEqCardPChipError notification is generated when persistent FCS errors are detected by the P chip in either the ingress or egress datapath/complex. The value tmnxCardSrcSlotBitmap is only used for the egress datapath/complex direction. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqCardPChipMemoryEvent
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2063 |
Event name | tmnxEqCardPChipMemoryEvent |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.51 |
Default severity | minor |
Message format string | Possible messages:
|
Cause |
The tmnxEqCardPChipMemoryEvent notification is generated when a P-chip experiences an occurrence of a memory error. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqCardQChipBufMemoryEvent
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2098 |
Event name | tmnxEqCardQChipBufMemoryEvent |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.86 |
Default severity | minor |
Message format string | Possible messages:
|
Cause |
The tmnxEqCardQChipBufMemoryEvent notification is generated when a Q-chip experiences an occurrence of a buffer memory error. |
Effect | Contact Nokia customer support. |
Recovery | Contact Nokia customer support. |
tmnxEqCardQChipIntMemoryEvent
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2101 |
Event name | tmnxEqCardQChipIntMemoryEvent |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.88 |
Default severity | minor |
Message format string | Possible messages:
|
Cause |
The tmnxEqCardQChipIntMemoryEvent notification is generated when a Q-chip experiences an occurrence of an internal memory error. |
Effect | Contact Nokia customer support. |
Recovery | Contact Nokia customer support. |
tmnxEqCardQChipStatsMemoryEvent
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2099 |
Event name | tmnxEqCardQChipStatsMemoryEvent |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.87 |
Default severity | minor |
Message format string | Possible messages:
|
Cause |
The tmnxEqCardQChipStatsMemoryEvent notification is generated when a Q-chip experiences an occurrence of a statistics memory error. |
Effect | Contact Nokia customer support. |
Recovery | Contact Nokia customer support. |
tmnxEqCardRemoved
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2003 |
Event name | tmnxEqCardRemoved |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.9 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : removed |
Cause | Generated when a card is removed from the chassis. The card type may be IOM, Fabric, MDA, MCM, CCM, CPM module, compact flash module, etc. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqCardSoftResetAlarm
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2060 |
Event name | tmnxEqCardSoftResetAlarm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.48 |
Default severity | minor |
Message format string | Slot $tmnxHwIndex$ entered soft-reset state $tmnxCardSoftResetState$ |
Cause |
The tmnxEqCardSoftResetAlarm notification is generated when an IOM card enters and exits the 'soft-reset' state. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqCardTChipParityEvent
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2110 |
Event name | tmnxEqCardTChipParityEvent |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.97 |
Default severity | minor |
Message format string | Slot $tmnxHwIndex$ experienced a T-chip memory error occurrence on complex $tmnxCardComplexNumber$ |
Cause |
The tmnxEqCardTChipParityEvent notification is generated when a T-chip experiences an occurrence of an internal memory error. |
Effect | Contact Nokia customer support. |
Recovery | Contact Nokia customer support. |
tmnxEqDataPathFailureProtImpact
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2126 |
Event name | tmnxEqDataPathFailureProtImpact |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.113 |
Default severity | minor |
Message format string | $tmnxHwClass$ $tmnxHwIndex$ experienced a datapath failure which impacted a protocol. |
Cause | The tmnxEqDataPathFailureProtImpact notification is generated when a slot experienced a data path failure which impacted a protocol. |
Effect | Services-related data associated with the impacted protocol may be lost. |
Recovery | N/A |
tmnxEqFanFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2006 |
Event name | tmnxEqFanFailure |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.6 |
Default severity | critical |
Message format string | Fan $tmnxChassisNotifyHwIndex$ failed |
Cause | Generated when one of the fans in a fan tray has failed. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqFlashDataLoss
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2023 |
Event name | tmnxEqFlashDataLoss |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.32 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : probable data loss |
Cause | tmnxEqFlashDataLoss is generated when an error occurs while data was being written to the compact flash. This notification indicates a probable data loss. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqFlashDiskFull
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2024 |
Event name | tmnxEqFlashDiskFull |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.33 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : disk full |
Cause | tmnxEqFlashDiskFull is generated when there is no space left on the compact flash. No more data can be written to it. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqHwEnhancedCapability
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2078 |
Event name | tmnxEqHwEnhancedCapability |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.66 |
Default severity | major |
Message format string | CPM Upgrade In Progress. Card in slot $tmnxCardSlotNum$ has enhanced capabilities. |
Cause | The tmnxEqHwEnhancedCapability notification is generated when the hardware, specified by the supplied objects, consists of enhanced capabilities as compared to the active hardware. |
Effect | The system behaves normally under this situation, however, switching to the newer hardware will put the system in an incompatible state with the currently active hardware. That is, once this device takes activity, the lesser capable hardware will fail to communicate with it. In this mode, the system is deemed in a 'one-way upgrade' scenario. |
Recovery | Two modes of recovery exist for this notification: 1) Remove the enhanced hardware, and supply a more compatible device (status quo) with the active hardware. 2) Switch to the enhanced device, and replace the older hardware with a similarly enhanced device (upgrade). |
tmnxEqLowSwitchFabricCap
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2104 |
Event name | tmnxEqLowSwitchFabricCap |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.91 |
Default severity | major |
Message format string | The switch fabric capacity is less than the forwarding capacity of $tmnxHwClass$ $tmnxHwIndex$ due to errors in fabric links. |
Cause | The tmnxEqLowSwitchFabricCap alarm is generated when the total switch fabric capacity becomes less than the IOM capacity due to link failures. At least one of the taps on the IOM is below 100% capacity. |
Effect | There is diminished switch fabric capacity to forward service-impacting information. |
Recovery | If the system does not self-recover, the IOM must be rebooted. |
tmnxEqLowSwitchFabricCapClear
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2105 |
Event name | tmnxEqLowSwitchFabricCapClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.92 |
Default severity | major |
Message format string | The switch fabric capacity alarm for $tmnxHwClass$ $tmnxHwIndex$ was cleared. |
Cause | The tmnxEqLowSwitchFabricCapClear notification is generated when the link failures that resulted in the tmnxEqLowSwitchFabricCap alarm to be raised have been resolved. |
Effect | There is sufficient switch fabric capacity to forward service-impacting information. |
Recovery | N/A |
tmnxEqMdaCfgNotCompatible
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2056 |
Event name | tmnxEqMdaCfgNotCompatible |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.44 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : configuration not compatible with equipped MDA |
Cause | Generated when a supported MDA is inserted into a slot of an IOM, the MDA is compatible with the currently provisioned MDA, but the current configuration on the MDA's ports is not compatible with the inserted MDA. |
Effect | Though services can still be created, if the tmnxMdaNotifyType is the same as the tmnxMDAEquippedType then the MDA will fail to operate as configured and will be in a failed state. |
Recovery | Change the configuration to reflect the capabilities of the MDA port, or switch out/re-provision the MDA for one that is compatible. |
tmnxEqMdaIngrXplError
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2129 |
Event name | tmnxEqMdaIngrXplError |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.116 |
Default severity | minor |
Message format string | MDA $tmnxCardSlotNum$/ $tmnxEqMdaSlotNum$ experienced an ingress XPL error occurrence. |
Cause | The tmnxEqMdaIngrXplError notification is generated when an MDA exhibits persistent ingress XPL errors. |
Effect | Contact Nokia customer support. |
Recovery | Contact Nokia customer support. |
tmnxEqMdaSyncENotCompatible
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2061 |
Event name | tmnxEqMdaSyncENotCompatible |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.49 |
Default severity | major |
Message format string | Provisioned synchronous ethernet not compatible with equipped MDA |
Cause | The tmnxEqMdaSyncENotCompatible notification is generated when an MDA card is inserted into a slot of an IOM. The MDA is compatible with the currently provisioned MDA, but the currently configured synchronous ethernet, tmnxMDASynchronousEthernet, is not compatible with the inserted MDA. |
Effect | Though services can still be created, if the tmnxMdaNotifyType is the same as the tmnxMDAEquippedType then the MDA will fail to operate as configured and will be in a failed state. |
Recovery | Change the configuration to reflect the capabilities of the MDA port, or switch out/re-provision the MDA for one that is compatible. |
tmnxEqMdaXplError
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2058 |
Event name | tmnxEqMdaXplError |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.46 |
Default severity | minor |
Message format string | MDA $tmnxCardSlotNum$/ $tmnxMDASlotNum$ experienced an egress XPL error occurrence. |
Cause | The tmnxEqMdaXplError notification is generated when an MDA exhibits persistent egress XPL Errors. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqMgmtEthRedStandbyClear
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2137 |
Event name | tmnxEqMgmtEthRedStandbyClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.122 |
Default severity | minor |
Message format string | The active CPM's management Ethernet port $tmnxChassisNotifyMgmtEthRedPort$ is serving as the system's management Ethernet port. |
Cause | The tmnxEqMgmtEthRedStandbyClear notification is generated when the active CPM's management Ethernet port goes operationally up and the management Ethernet port reverts from the standby CPM to the active CPM. |
Effect | The management of the node is operating from the active CPM's management Ethernet port and is redundant. |
Recovery | No recovery required. |
tmnxEqMgmtEthRedStandbyRaise
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2136 |
Event name | tmnxEqMgmtEthRedStandbyRaise |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.121 |
Default severity | minor |
Message format string | The standby CPM's management Ethernet port $tmnxChassisNotifyMgmtEthRedPort$ is serving as the system's management Ethernet port. |
Cause | The tmnxEqMgmtEthRedStandbyRaise notification is generated when the active CPM's management Ethernet port goes operationally down and the standby CPM's management Ethernet port is operationally up and now serving as the system's management Ethernet port. |
Effect | The management Ethernet port is no longer redundant. The node can be managed via the standby CPM's management Ethernet port only. |
Recovery | Bring the active CPM's management Ethernet port operationally up. |
tmnxEqPhysChassisFanFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2148 |
Event name | tmnxEqPhysChassisFanFailure |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.135 |
Default severity | critical |
Message format string | Chassis $tmnxPhysChassisNum$ fan $tmnxPhysChassisFanIndex$ failure |
Cause |
The tmnxEqPhysChassisFanFailure notification is generated when one of the fans in a fan tray fails on a particular physical chassis. |
Effect | The fan is no longer operational. |
Recovery | Insert a new fan. |
tmnxEqPhysChassisFanFailureClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2149 |
Event name | tmnxEqPhysChassisFanFailureClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.136 |
Default severity | cleared |
Message format string | Chassis $tmnxPhysChassisNum$ fan $tmnxPhysChassisFanIndex$ failure cleared |
Cause | The tmnxEqPhysChassisFanFailureClear notification is generated when the fan failure is cleared on the particular physical chassis. |
Effect | The fan is operational again. |
Recovery | There is no recovery for this notification. |
tmnxEqPhysChassPowerSupAcFail
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2140 |
Event name | tmnxEqPhysChassPowerSupAcFail |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.127 |
Default severity | critical |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ AC failure |
|
Cause | The tmnxEqPhysChassPowerSupAcFail notification is generated when an AC failure occurs on the power supply. |
Effect | The power supply is no longer operational. |
Recovery | Insert a new power supply. |
tmnxEqPhysChassPowerSupAcFailClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2141 |
Event name | tmnxEqPhysChassPowerSupAcFailClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.128 |
Default severity | cleared |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ AC failure cleared |
Cause | The tmnxEqPhysChassPowerSupAcFailClr notification is generated when the AC failure is cleared on the power supply. |
Effect | The power supply is operational again. |
Recovery | There is no recovery for this notification. |
tmnxEqPhysChassPowerSupDcFail
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2142 |
Event name | tmnxEqPhysChassPowerSupDcFail |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.129 |
Default severity | critical |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ DC failure |
|
Cause | The tmnxEqPhysChassPowerSupDcFail notification is generated when a DC failure occurs on the power supply. |
Effect | The power supply is no longer operational. |
Recovery | Insert a new power supply. |
tmnxEqPhysChassPowerSupDcFailClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2143 |
Event name | tmnxEqPhysChassPowerSupDcFailClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.130 |
Default severity | cleared |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ DC failure cleared |
Cause | The tmnxEqPhysChassPowerSupDcFailClr notification is generated when the DC failure is cleared on the power supply. |
Effect | The power supply is operational again. |
Recovery | There is no recovery for this notification. |
tmnxEqPhysChassPowerSupInFail
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2144 |
Event name | tmnxEqPhysChassPowerSupInFail |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.131 |
Default severity | critical |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ input failure |
|
Cause | The tmnxEqPhysChassPowerSupInFail notification is generated when an input failure occurs on the power supply. |
Effect | The power supply is no longer operational. |
Recovery | Check input feed and/or insert a new power supply. |
tmnxEqPhysChassPowerSupInFailClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2145 |
Event name | tmnxEqPhysChassPowerSupInFailClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.132 |
Default severity | cleared |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ input failure cleared |
Cause | The tmnxEqPhysChassPowerSupInFailClr notification is generated when the input failure is cleared on the power supply. |
Effect | The power supply is operational again. |
Recovery | There is no recovery for this notification. |
tmnxEqPhysChassPowerSupOutFail
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2146 |
Event name | tmnxEqPhysChassPowerSupOutFail |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.133 |
Default severity | critical |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ output failure |
|
Cause | The tmnxEqPhysChassPowerSupOutFail notification is generated when an output failure occurs on the power supply. |
Effect | The power supply is no longer operational. |
Recovery | Insert a new power supply. |
tmnxEqPhysChassPowerSupOutFailCl
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2147 |
Event name | tmnxEqPhysChassPowerSupOutFailCl |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.134 |
Default severity | cleared |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ output failure cleared |
Cause | The tmnxEqPhysChassPowerSupOutFailCl notification is generated when an output failure is cleared on the power supply. |
Effect | The power supply is operational again. |
Recovery | There is no recovery for this notification. |
tmnxEqPhysChassPowerSupOvrTmp
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2138 |
Event name | tmnxEqPhysChassPowerSupOvrTmp |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.125 |
Default severity | critical |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ over temperature |
Cause | The tmnxEqPhysChassPowerSupOvrTmp notification is generated when a power supply's temperature surpasses the threshold of the particular physical chassis. |
Effect | The power supply is no longer operational. |
Recovery | Check input feed and/or insert a new power supply. |
tmnxEqPhysChassPowerSupOvrTmpClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2139 |
Event name | tmnxEqPhysChassPowerSupOvrTmpClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.126 |
Default severity | cleared |
Message format string | Chassis $tmnxPhysChassisNum$ power supply $tmnxPhysChassPowerSupId$ over temperature cleared |
Cause | The tmnxEqPhysChassPowerSupOvrTmpClr notification is generated when a power supply's temperature is reduced below the threshold of the particular physical chassis. |
Effect | The power supply is operational again. |
Recovery | There is no recovery for this notification. |
tmnxEqPowerCapacityExceeded
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2092 |
Event name | tmnxEqPowerCapacityExceeded |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.80 |
Default severity | minor |
Message format string | The system has reached maximum power capacity $tmnxChassisNotifyPowerCapacity$ watts |
|
Cause | The tmnxEqPowerCapacityExceeded alarm is generated when a device needs power to boot, but there is not enough power capacity to support the device. |
Effect | A non-powered device will not boot until the power capacity is increased to support the device. |
Recovery | Add a new power supply to the system or change the faulty power supply for a working one. |
tmnxEqPowerCapacityExceededClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2093 |
Event name | tmnxEqPowerCapacityExceededClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.81 |
Default severity | minor |
Message format string | The system power capacity is sufficient to support installed devices |
Cause | The tmnxEqPowerCapacityExceededClear notification is generated when the available power capacity exceeds the required power to boot all inserted devices. |
Effect | Devices that failed to boot due to power constrains, power up. |
Recovery | N/A |
tmnxEqPowerLostCapacity
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2094 |
Event name | tmnxEqPowerLostCapacity |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.82 |
Default severity | major |
Message format string | The system can no longer support configured devices. Power capacity dropped to $tmnxChassisNotifyPowerCapacity$ watts |
|
Cause | The tmnxEqPowerLostCapacity alarm is generated when a power supply fails or is removed which puts the system in an overloaded situation. |
Effect | Devices are powered off in order of lowest power priority (tmnxMDAHwPowerPriority) until the available power capacity can support the powered devices. |
Recovery | Add a new power supply to the system or change the faulty power supply for a working one. |
tmnxEqPowerLostCapacityClear
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2095 |
Event name | tmnxEqPowerLostCapacityClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.83 |
Default severity | major |
Message format string | The system has reached a sustainable power capacity. |
Cause | The tmnxEqPowerLostCapacityClear notification is generated when the available power capacity exceeds the required power to boot all inserted devices. |
Effect | Devices that powered off due to power constrains, power up. |
Recovery | N/A |
tmnxEqPowerOverloadState
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2096 |
Event name | tmnxEqPowerOverloadState |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.84 |
Default severity | critical |
Message format string | The system has reached critical power capacity. Increase available power now. |
Cause | The tmnxEqPowerOverloadState alarm is generated when the overloaded power capacity can not support the power requirements and there are no further devices that can be powered off. |
Effect | The system runs a risk of experiencing brownouts while the available power capacity does not meet the required power consumption. |
Recovery | Add power capacity or manually shut down devices until the power capacity meets the power needs. |
tmnxEqPowerOverloadStateClear
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2097 |
Event name | tmnxEqPowerOverloadStateClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.85 |
Default severity | critical |
Message format string | The system has reached a sustainable power capacity for critical equipment. |
Cause | The tmnxEqPowerOverloadStateClear notification is generated when the available power capacity meets or exceeds the power needs of the powered on devices. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqPowerSafetyAlertClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2107 |
Event name | tmnxEqPowerSafetyAlertClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.94 |
Default severity | minor |
Message format string | Possible messages:
|
Cause | The tmnxEqPowerSafetyAlertClear notification is generated when the system power capacity raises above the configured safety alert threshold. |
Effect | This event is for notification only. |
Recovery | N/A |
tmnxEqPowerSafetyAlertThreshold
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2106 |
Event name | tmnxEqPowerSafetyAlertThreshold |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.93 |
Default severity | minor |
Message format string | The system power capacity for zone $tmnxChassisPwrMgmtZone$ dropped below the configured safety alert threshold of $tmnxChassisPwrMgmtSafetyAlert$ watts. |
|
Cause | The tmnxEqPowerSafetyAlertThreshold notification is generated when the system power capacity drops below the configured safety alert threshold. |
Effect | This event is for notification only. |
Recovery | N/A |
tmnxEqPowerSafetyLevelClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2109 |
Event name | tmnxEqPowerSafetyLevelClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.96 |
Default severity | minor |
Message format string | The peak nodal power for zone $tmnxChassisPwrMgmtZone$ consumption dropped below the configured safety level threshold of $tmnxChassisPwrMgmtSafetyLevel$ percent |
|
Cause | The tmnxEqPowerSafetyLevelClear notification is generated when the peak nodal power consumption drops below the configured safety level threshold. |
Effect | This event is for notification only. |
Recovery | N/A |
tmnxEqPowerSafetyLevelThreshold
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2108 |
Event name | tmnxEqPowerSafetyLevelThreshold |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.95 |
Default severity | minor |
Message format string | The peak nodal power for zone $tmnxChassisPwrMgmtZone$ consumption exceeded the configured safety level threshold of $tmnxChassisPwrMgmtSafetyLevel$ percent |
|
Cause | The tmnxEqPowerSafetyLevelThreshold notification is generated when the peak nodal power consumption exceeds the configured safety level threshold. |
Effect | This event is for notification only. |
Recovery | N/A |
tmnxEqPowerSupplyFailureAc
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2008 |
Event name | tmnxEqPowerSupplyFailureAc |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.3 |
Default severity | critical |
Message format string | Power supply $tmnxChassisNotifyHwIndex$ AC failure |
|
Cause | Generated when the temperature sensor reading on an equipment object is greater than its configured threshold. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqPowerSupplyFailureDc
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2009 |
Event name | tmnxEqPowerSupplyFailureDc |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.3 |
Default severity | critical |
Message format string | Power supply $tmnxChassisNotifyHwIndex$ DC failure |
|
Cause | Generated when one of the chassis's power supplies fails. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqPowerSupplyFailureInput
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2050 |
Event name | tmnxEqPowerSupplyFailureInput |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.3 |
Default severity | critical |
Message format string | Power supply $tmnxChassisNotifyHwIndex$ input failure |
|
Cause | Generated when one of the chassis's power supplies fails. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqPowerSupplyFailureOutput
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2051 |
Event name | tmnxEqPowerSupplyFailureOutput |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.3 |
Default severity | critical |
Message format string | Power supply $tmnxChassisNotifyHwIndex$ output failure |
Cause | Generated when one of the chassis's power supplies fails. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqPowerSupplyFailureOvt
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2007 |
Event name | tmnxEqPowerSupplyFailureOvt |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.3 |
Default severity | critical |
Message format string | Power supply $tmnxChassisNotifyHwIndex$ over temperature |
Cause | N/A |
Effect |
N/A |
Recovery |
N/A |
tmnxEqPowerSupplyInputFeedAlm
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2113 |
Event name | tmnxEqPowerSupplyInputFeedAlm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.100 |
Default severity | minor |
Message format string | Power supply $tmnxHwIndex$ $tmnxChassisPowerSupplyInFeedDown$not supplying power. |
Cause | The tmnxEqPowerSupplyInputFeedAlm alarm is generated if any one of the input feeds for a given power supply is not supplying power. |
Effect | There is an increased risk of system power brown-outs or black-outs. |
Recovery | Restore all of the input feeds that are not supplying power. |
tmnxEqPowerSupplyInputFeedAlmClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2114 |
Event name | tmnxEqPowerSupplyInputFeedAlmClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.101 |
Default severity | minor |
Message format string | The input feeds for power supply $tmnxHwIndex$ are supplying power. |
|
Cause | The tmnxEqPowerSupplyInputFeedAlmClr notification is generated when the last of the missing input feeds has been brought back online. |
Effect | All power supply input feeds are supplying power. |
Recovery | N/A |
tmnxEqPowerSupplyInserted
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2010 |
Event name | tmnxEqPowerSupplyInserted |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.4 |
Default severity | major |
Message format string | Power supply $tmnxChassisNotifyHwIndex$ inserted |
|
Cause | Generated when one of the chassis's power supplies is inserted. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqPowerSupplyPemACRectAlm
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2111 |
Event name | tmnxEqPowerSupplyPemACRectAlm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.98 |
Default severity | minor |
Message format string | Power supply $tmnxHwIndex$ $tmnxChassisPowerSupplyPemACRect$failed or missing. |
Cause | The tmnxEqPowerSupplyPemACRectAlm alarm is generated if any one of the AC rectifiers for a given power supply is in a failed state or is missing. |
Effect | There is an increased risk of the power supply failing, causing insufficient power to the system. |
Recovery | Bring the AC rectifiers back online. |
tmnxEqPowerSupplyPemACRectAlmClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2112 |
Event name | tmnxEqPowerSupplyPemACRectAlmClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.99 |
Default severity | minor |
Message format string | The power supply $tmnxHwIndex$ AC rectifiers are fully operational. |
Cause | The tmnxEqPowerSupplyPemACRectAlmClr notification is generated when the last of the failed or missing AC rectifiers has been brought back online. |
Effect | The power supply AC rectifiers are fully operational. |
Recovery | N/A |
tmnxEqPowerSupplyRemoved
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2011 |
Event name | tmnxEqPowerSupplyRemoved |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.5 |
Default severity | major |
Message format string | Power supply $tmnxChassisNotifyHwIndex$, power lost |
|
Cause | Generated when one of the chassis's power supplies is removed. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqProvPowerCapacityAlm
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2115 |
Event name | tmnxEqProvPowerCapacityAlm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.102 |
Default severity | minor |
Message format string | The provisioned power capacity can no longer support configured devices. |
Cause | The tmnxEqProvPowerCapacityAlm notification is generated if a power zone's provisioned power capacity can no longer support configured devices. |
Effect | There is an increased risk of device power outages that may be service affecting. |
Recovery | Increase the provisioned power capacity. |
tmnxEqProvPowerCapacityAlmClr
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2116 |
Event name | tmnxEqProvPowerCapacityAlmClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.103 |
Default severity | minor |
Message format string | The provisioned power capacity now supports configured devices. |
Cause | The tmnxEqProvPowerCapacityAlmClr notification is generated when the power zone's provisioned power capacity can support configured devices. |
Effect | All configured devices in the power zone have enough provisioned power capacity. |
Recovery | N/A |
tmnxEqSyncIfTimingBITS2Alarm
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2073 |
Event name | tmnxEqSyncIfTimingBITS2Alarm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.61 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on BITS 2 reference |
Cause | Generated when an alarm condition on the BITS 2 timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingBITS2AlarmClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2074 |
Event name | tmnxEqSyncIfTimingBITS2AlarmClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.62 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on BITS 2 reference cleared |
Cause | Generated when an alarm condition on the BITS 2 timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingBITS2Quality
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2071 |
Event name | tmnxEqSyncIfTimingBITS2Quality |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.59 |
Default severity | minor |
Message format string | Synchronous Timing interface, reference BITS2 received quality level $tmnxSyncIfTimingBITS2RxQltyLevel$ |
|
Cause | Generated when there is a change of the received quality level on the second bits interface. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingBITSAlarm
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2030 |
Event name | tmnxEqSyncIfTimingBITSAlarm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.38 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on BITS$bits-two-supported$ reference |
Cause | Generated when an alarm condition on the BITS timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingBITSAlarmClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2031 |
Event name | tmnxEqSyncIfTimingBITSAlarmClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.39 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on BITS$bits-two-supported$ reference cleared |
Cause | Generated when an alarm condition on the BITS timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingBITSOutRefChg
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2075 |
Event name | tmnxEqSyncIfTimingBITSOutRefChg |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.63 |
Default severity | minor |
Message format string | Synchronous Timing interface, BITS output timing reference changed to $tmnxSyncIfTimingBITSOutRefSel$ |
Cause |
Generated when the BITS Out timing reference selection changes. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingBITSQuality
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2070 |
Event name | tmnxEqSyncIfTimingBITSQuality |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.58 |
Default severity | minor |
Message format string | Synchronous Timing interface, reference BITS $bits-two-supported$ received quality level $tmnxSyncIfTimingBITSRxQltyLevel$ |
Cause | Generated when there is a change of the received quality level on the bits interface. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingHoldover
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2017 |
Event name | tmnxEqSyncIfTimingHoldover |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.26 |
Default severity | critical |
Message format string | Synchronous Timing interface in holdover state |
Cause | Generated when the synchronous equipment timing subsystem transitions into a holdover state. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingHoldoverClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2018 |
Event name | tmnxEqSyncIfTimingHoldoverClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.27 |
Default severity | critical |
Message format string | Synchronous Timing interface holdover state cleared |
Cause | Generated when the synchronous equipment timing subsystem transitions out of the holdover state. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingPTPAlarm
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2080 |
Event name | tmnxEqSyncIfTimingPTPAlarm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.68 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on PTP reference |
Cause | Generated when an alarm condition on the Precision Timing Protocol (PTP) timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingPTPAlarmClr
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2081 |
Event name | tmnxEqSyncIfTimingPTPAlarmClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.69 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on PTP reference cleared |
Cause | Generated when an alarm condition on the Precision Timing Protocol (PTP) timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingPTPQuality
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2079 |
Event name | tmnxEqSyncIfTimingPTPQuality |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.67 |
Default severity | minor |
Message format string | Synchronous Timing interface, reference PTP received quality level $tmnxSyncIfTimingPTPRxQltyLevel$ |
Cause |
Generated when there is a change of the received quality level on the Precision Timing Protocol (PTP). |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingRef1Alarm
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2019 |
Event name | tmnxEqSyncIfTimingRef1Alarm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.28 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on reference 1 |
Cause | Generated when an alarm condition on the first timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingRef1AlarmClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2020 |
Event name | tmnxEqSyncIfTimingRef1AlarmClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.29 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on reference 1 cleared |
Cause | Generated when an alarm condition on the first timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingRef1Quality
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2068 |
Event name | tmnxEqSyncIfTimingRef1Quality |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.56 |
Default severity | minor |
Message format string | Synchronous Timing interface, reference 1 received quality level $tmnxSyncIfTimingRef1RxQltyLevel$ |
Cause |
Generated when there is a change of the received quality level on timing reference 1. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingRef2Alarm
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2021 |
Event name | tmnxEqSyncIfTimingRef2Alarm |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.30 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on reference 2 |
Cause | Generated when an alarm condition on the second timing reference is detected. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingRef2AlarmClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2022 |
Event name | tmnxEqSyncIfTimingRef2AlarmClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.31 |
Default severity | minor |
Message format string | Synchronous Timing interface, alarm $tmnxSyncIfTimingNotifyAlarm$ on reference 2 cleared |
Cause | Generated when an alarm condition on the second timing reference is cleared. This notification will have the same indices as those of the tmnxCpmCardTable. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingRef2Quality
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2069 |
Event name | tmnxEqSyncIfTimingRef2Quality |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.57 |
Default severity | minor |
Message format string | Synchronous Timing interface, reference 2 received quality level $tmnxSyncIfTimingRef2RxQltyLevel$ |
Cause |
Generated when there is a change of the received quality level on timing reference 2. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingRefSwitch
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2072 |
Event name | tmnxEqSyncIfTimingRefSwitch |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.60 |
Default severity | minor |
Message format string | Synchronous Timing interface, timing reference changed to $tmnxSyncIfTimingRef1InUse$ |
Cause |
Generated when there is a change of which timing reference is providing timing for the system. |
Effect | N/A |
|
Recovery | N/A |
tmnxEqSyncIfTimingSystemQuality
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2077 |
Event name | tmnxEqSyncIfTimingSystemQuality |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.65 |
Default severity | minor |
Message format string | Synchronous Timing interface, System Quality Level changed to $tmnxSyncIfTimingSystemQltyLevel$ |
Cause |
This notification may be triggered for the following reasons: 1) There has been a switch in the timing reference in use by the network element, either because the previously active timing reference was disqualified, or to ensure that the network element is using the timing reference with the best timing quality. 2) There has been a change in the active timing reference's quality and the change does not result in a timing reference switch. 3) The network element has transitioned into or out of the holdover state. |
Effect | The system quality level is used to determine the SSM code transmitted on synchronous interfaces. This may affect the SSM code transmitted on some or all interfaces, which may affect the distribution of timing throughout the network. |
Recovery | If the customer is expecting the system to be locked to a reference of a particular quality and the system quality has decreased, the customer will need to determine the root cause (for example, loss of communication with a satellite) and resolve the issue. |
tmnxEqWrongCard
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2004 |
Event name | tmnxEqWrongCard |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.10 |
Default severity | minor |
Message format string | Class $tmnxHwClass$ : wrong type inserted |
Cause | Generated when the wrong type of card is inserted into a slot of the chassis. Even though a card may be physically supported by the slot, it may have been administratively configured to allow only certain card types in a particular slot location. The card type may be IOM, Fabric, MDA, MCM, CPM module, etc. |
Effect | N/A |
|
Recovery | N/A |
tmnxExtStandbyCpmReboot
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2127 |
Event name | tmnxExtStandbyCpmReboot |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.114 |
Default severity | warning |
Message format string | Rebooting extension standby CPM due to master standby CPM reboot and transition into or out of an ISSU state. |
Cause | The tmnxExtStandbyCpmReboot notification is generated after a master standby CPM reboots and it is determined that the master standby CPM has transitioned into or out of an ISSU state. This detected transition will cause a reboot of the extension standby CPM (this reboot is necessary and expected for ISSU operation). This notification helps an operator understand why an extension standby CPM may have rebooted. |
Effect | The extension standby CPM will reboot. |
Recovery | There is no recovery for this notification. |
tmnxExtStandbyCpmRebootFail
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2128 |
Event name | tmnxExtStandbyCpmRebootFail |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.115 |
Default severity | minor |
Message format string | Unable to automatically reboot extension standby CPM during ISSU. |
Cause | The tmnxExtStandbyCpmRebootFail notification is generated after a master standby CPM reboots and it is determined that the master standby CPM has transitioned into or out of an ISSU state. The system will attempt to reboot the extension standby CPM as part of the normal ISSU process. If the system determines that it cannot reboot the extension standby CPM (i.e. it is not reachable) then this log event is raised. |
Effect | The extension standby CPM may not transition to the ISSU state in which case the ISSU cannot proceed normally. |
Recovery | Resetting the extension standby CPM can be attempted to try and get the CPM into an ISSU state. If that is not successful, then the ISSU should be aborted. |
tmnxInterChassisCommsDown
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4001 |
Event name | tmnxInterChassisCommsDown |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxInterChassisNotifications.1 |
Default severity | critical |
Message format string | Control communications disrupted between the active CPM and the chassis |
Cause | The tmnxInterChassisCommsDown alarm is generated when the active CPM cannot reach the far-end chassis. |
Effect | The resources on the far-end chassis are not available. This event for the far-end chassis means that the CPM, SFM, and XCM cards in the far-end chassis will reboot and remain operationally down until communications are re-established. |
Recovery | Ensure that all CPM interconnect ports in the system are properly cabled together with working cables. |
tmnxInterChassisCommsUp
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4002 |
Event name | tmnxInterChassisCommsUp |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxInterChassisNotifications.2 |
Default severity | critical |
Message format string | Control communications established between the active CPM and the chassis |
Cause | The tmnxInterChassisCommsUp notification is generated when the control communications are re-established between the active CPM and the far-end chassis. |
Effect | The resources on the far-end chassis are now available. This event for the far-end chassis means that the CPM, SFM and XCM cards in the far-end chassis will start the process of coming back into service. |
Recovery | N/A |
tmnxIomEventOverflow
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2124 |
Event name | tmnxIomEventOverflow |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.111 |
Default severity | minor |
Message format string | Iom $tmnxIomResourceType$ Resource event overflow occurred on card $tmnxChassisNotifyCardSlotNum$ at $tmnxIomResLimitTimeEventOccured$. |
Cause | The tmnxIomEventOverflow notification is generated when tmnxIomResStateClr, tmnxIomResExhausted and tmnxIomResHighLimitReached occur more than 200 times because of resource usage fluctuation. The Iom Raises the final trap to indicate overflow and stops logging traps. |
Effect | Some FP notifications configured on the card may not be received. |
Recovery | Notifications will resume once the Overflow clear is set. |
tmnxIomEventOverflowClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2125 |
Event name | tmnxIomEventOverflowClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.112 |
Default severity | minor |
Message format string | $tmnxIomResLimMissingNotifCount$ Iom $tmnxIomResourceType$ Resources events were dropped in the last event throttling interval on card $tmnxChassisNotifyCardSlotNum$ at $tmnxIomResLimitTimeEventOccured$. |
Cause | The tmnxIomEventOverflowClr notification is generated when the CPM polls the IOM for traps and the overflow is cleared by logging an overflow-clear on a particular card. |
Effect | Notifications are received again since the event throttling has ended. |
Recovery | There is no recovery for this notification. |
tmnxIomResExhausted
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2122 |
Event name | tmnxIomResExhausted |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.109 |
Default severity | critical |
Message format string | The $tmnxIomResourceType$ resources on IOM $tmnxChassisNotifyCardSlotNum$ and Forwarding Plane $tmnxChassisNotifyFpNum$ has been exhausted at $tmnxIomResLimitTimeEventOccured$. |
|
Cause | The tmnxIomResExhausted notification is generated when the type of resources on IOM as specified by tmnxIomResourceType has reached the 100% of its utilization threshold. |
Effect | The specified resource has reached the stats pool limit. |
Recovery | Intervention may be required to recover resources. |
tmnxIomResHighLimitReached
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2121 |
Event name | tmnxIomResHighLimitReached |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.108 |
Default severity | major |
Message format string | The $tmnxIomResourceType$ resources on IOM $tmnxChassisNotifyCardSlotNum$ and Forwarding Plane $tmnxChassisNotifyFpNum$ has reached the $tmnxIomResourceLimitPct$% utilization threshold at $tmnxIomResLimitTimeEventOccured$. |
Cause | The tmnxIomResHighLimitReached notification is generated when the resource (of type tmnxIomResourceType) utilization on IOM has reached the value of tmnxIomResourceLimitPct. |
Effect | The specified resource limit is cleared when the number of in-use stats resources falls below the clear threshold of the stats pool limit. |
Recovery | There is no recovery required for this notification. |
tmnxIomResStateClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2123 |
Event name | tmnxIomResStateClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.110 |
Default severity | minor |
Message format string | The $tmnxIomResourceType$ resources on IOM $tmnxChassisNotifyCardSlotNum$ and Forwarding Plane $tmnxChassisNotifyFpNum$ has dropped below the $tmnxIomResourceLimitPct$% utilization threshold at $tmnxIomResLimitTimeEventOccured$. |
Cause | The tmnxIomResStateClr notification is generated when the type of resources on IOM as specified by tmnxIomResourceType has dropped back down below the value of tmnxIomResourceLimitPct. |
Effect | The specified resource limit is cleared when the number of in-use stats resources falls below tmnxIomResourceLimitPct of the stats pool limit. |
Recovery | There is no recovery required for this notification. |
tmnxIPsecIsaGrpActiveIsaChgd
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2062 |
Event name | tmnxIPsecIsaGrpActiveIsaChgd |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.50 |
Default severity | minor |
Message format string | Active ISA changed to $tmnxIPsecIsaGrpActiveIsa$ for IPSec ISA group $tmnxIPsecIsaGrpId$ where primary ISA is $tmnxIPsecIsaGrpPrimaryIsa$ and Backup ISA is $tmnxIPsecIsaGrpBackupIsa$ |
Cause | The tmnxIPsecIsaGrpActiveIsaChgd notification is generated when a change in the active ISA (Integrated Service Adaptor) occurs in an IPsec ISA module group. |
Effect | N/A |
|
Recovery | N/A |
tmnxIPsecIsaGrpTnlHighWMark
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2066 |
Event name | tmnxIPsecIsaGrpTnlHighWMark |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.54 |
Default severity | minor |
Message format string | Number of tunnels for an IPsec ISA module for the group $tmnxIPsecIsaGrpId$ has reached to the high watermark which is 95% of the maximum limit $tmnxIPsecIsaGrpMaxTunnels$. |
Cause |
The number of tunnels for an IPsec ISA (Integrated Service Adaptor) module has reached to the high watermark which is 95% of the maximum limit. |
Effect | N/A |
|
Recovery | N/A |
tmnxIPsecIsaGrpTnlLowWMark
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2065 |
Event name | tmnxIPsecIsaGrpTnlLowWMark |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.53 |
Default severity | minor |
Message format string | Number of tunnels for an IPsec ISA module for the group $tmnxIPsecIsaGrpId$ has dropped to the low watermark which is 90% of the maximum limit $tmnxIPsecIsaGrpMaxTunnels$. |
Cause |
The number of tunnels for an IPsec ISA (Integrated Service Adaptor) module has dropped to the low watermark which is 90% of the maximum limit. |
Effect | N/A |
|
Recovery | N/A |
tmnxIPsecIsaGrpTnlMax
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2067 |
Event name | tmnxIPsecIsaGrpTnlMax |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.55 |
Default severity | minor |
Message format string | Number of tunnels for an IPsec ISA module the for group $tmnxIPsecIsaGrpId$ has reached the maximum limit $tmnxIPsecIsaGrpMaxTunnels$. |
Cause | The number of tunnels for an IPsec ISA (Integrated Service Adaptor) module has reached the maximum limit. |
Effect | N/A |
|
Recovery | N/A |
tmnxIPsecIsaGrpUnableToSwitch
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2064 |
Event name | tmnxIPsecIsaGrpUnableToSwitch |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.52 |
Default severity | minor |
Message format string | IPsec ISA $tmnxIPsecIsaGrpActiveIsa$ for group $tmnxIPsecIsaGrpId$ is unable to switch due to lack of resources on the destination MDA |
Cause | IPsec ISA group is unable to switch due to lack of resources on the destination MDA. |
Effect | In such an event the IPsec ISA group is left without an active MDA and the tmnxIPsecIsaGrpOperState is set to 'outOfService'. |
Recovery | Recovery is possible by releasing resources and performing a shutdown/no shutdown operation to bring up the ISA group. |
tmnxMDAIsaTunnelGroupChange
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2083 |
Event name | tmnxMDAIsaTunnelGroupChange |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.71 |
Default severity | minor |
Message format string | MDA $tmnxCardSlotNum$/ $tmnxMDASlotNum$ is $tmnxMDAIsaTunnelGroupInUse$ active in the ISA tunnel-group $tmnxMDAIsaTunnelGroup$ |
Cause |
The tmnxMDAIsaTunnelGroupChange notification is generated when IPsec ISA (Integrated Service Adaptor) tunnel-group in-use for the MDA changes value. |
Effect | There is no operational impact due to this event. |
Recovery | N/A |
tmnxOesCardDegraded
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5123 |
Event name | tmnxOesCardDegraded |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.23 |
Default severity | minor |
Message format string | Class $tmnxHwClass$: Card degraded |
Cause | The tmnxOesCardDegraded notification is generated when a fault on the card has caused the system to declare a hardware failure. This condition may be declared due to a failure in the SEEP or another hardware failure, depending on the card type the alarm is raised against. |
Effect | The tmnxOesCardDegraded alarm indicates a lower priority fault on the card that does not directly affect the traffic currently flowing through the device. |
Recovery | First attempt a soft reset of the card. If the card has rebooted and the condition did not clear, then try a hard reset of the card. If the card has rebooted and the condition did not clear, then remove the card and re-insert it to see if the condition clears. If the condition remains, then replace the card and follow the return and repair process for the problem card. |
tmnxOesCardFirmwareErr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5132 |
Event name | tmnxOesCardFirmwareErr |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.33 |
Default severity | minor |
Message format string | Class $tmnxHwClass$: Inventory error |
Cause | The tmnxOesCardFirmwareErr is raised when the device installed in the shelf has an EEPROM that does not contain the correct or recognizable information. |
Effect | The card may demonstrate other alarms due to this condition. |
Recovery | Replace the card. |
tmnxOesCfgBlocked
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5139 |
Event name | tmnxOesCfgBlocked |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.15 |
Default severity | minor |
Message format string | OES Configuration blocked |
Cause | This event tmnxOesCfgBlocked notification is generated when a configuration being made in the OES is blocked. |
Effect | The configuration is not active in the OES. |
Recovery | One possible reason for this configuration failure is if there is a card present in the OES that is a supported card type but the router was not yet aware of its presence. This condition should clear as soon as the router becomes aware of the card. A second reason is when the supported card is present and is misaligned with the configuration (e.g. card present in slot 3 and 4, yet configuration is oes-1/2 where the width of card is two slots). This condition cannot be cleared automatically as the card has to be moved to the correct slot (or the configuration has to be removed for card oes-1/3 via cli command ). A third reason is when there is an unsupported card type in the OES that the router cannot manage. This condition cannot be cleared automatically and the OES will need to be recommissioned to clear the condition. Note: services on cards not impacted by the unknown card type are not affected. |
tmnxOesCfgFailNoMemory
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5138 |
Event name | tmnxOesCfgFailNoMemory |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.14 |
Default severity | minor |
Message format string | OES Configuration failed due to insufficient dynamic memory |
Cause | The tmnxOesCfgFailNoMemory notification is generated when a request to obtain dynamic memory to download a configuration to the OES has failed. |
Effect | The configuration is not active in the OES. |
Recovery | This may be a temporary issue and the condition may clear on its own. If the event is raised periodically, then there is a permanent memory issue and the support organization should be informed. |
tmnxOesCtlCardActivityChange
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5117 |
Event name | tmnxOesCtlCardActivityChange |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.17 |
Default severity | minor |
Message format string | OES active control card changed to $tmnxHwIndex$ |
Cause |
The tmnxOesCtlCardActivityChange notification is generated when the active Equipment Controller has changed to the card specified by the tmnxHwIndex. |
Effect | The active Equipment Controller has moved to the previously standby card. |
Recovery | No recovery is required. |
tmnxOesCtlCardPortDown
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5101 |
Event name | tmnxOesCtlCardPortDown |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.1 |
Default severity | minor |
Message format string | OES Ctl Card Port is not operational |
Cause | The tmnxOesCtlCardPortDown notification is generated when a port (e.g. ES 1 or AUX) on an OES Control Card (e.g. EC card) is not operational. The reason may be a misconnected, disconnected or faulty cable, a faulty port or Control Card. |
Effect | If an ES (Extension Shelf) port is down then one of the control plane communication paths between EC (Equipment Controller) cards in different OES Chassis is not available. The control communications with one or more OES subtending chassis may be affected rendering the Chassis unmanageable. Other control paths may be available. If an AUX port is down then one of the control plane communication paths between the router and the OES Master Chassis is not available and control communications with the OES may be affected rendering the OES unmanageable. Other control paths may be available. |
Recovery | Check that the cable is correctly connected and test the cable. |
tmnxOesCtlCardPortUp
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5102 |
Event name | tmnxOesCtlCardPortUp |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.2 |
Default severity | minor |
Message format string | OES Ctl Card Port is operational |
Cause | The tmnxOesCtlCardPortUp notification is generated when the port on the OES Control Card (e.g. EC card) is operational. |
Effect | If an ES port is up then a control plane communication path between EC cards in different OES Chassis has been established. If an AUX port is up then a control plane communication path between the router and the OES Master Chassis has been established and the OES can be managed by the router. |
Recovery | No recovery required |
tmnxOesCtlCommsDown
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5001 |
Event name | tmnxOesCtlCommsDown |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.1 |
Default severity | critical |
Message format string | Control communications disrupted between the Active CPM and the OES Master chassis, reason: $tmnxOesCtlCommsDownReason$ |
Cause |
The tmnxOesCtlCommsDown notification is generated when the active CPM can't reach the OES master chassis. |
Effect | The OES can't be managed by the router. |
Recovery | Ensure that all control communications ports between the router and the OES master chassis are correctly connected and test the cables. |
tmnxOesCtlCommsUp
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5002 |
Event name | tmnxOesCtlCommsUp |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.2 |
Default severity | critical |
Message format string | Control communications established between the Active CPM and the OES Master chassis |
Cause | The tmnxOesCtlCommsUp notification is generated when the active CPM can reach the OES master chassis. |
Effect | The OES can be managed by the router. |
Recovery | No recovery required. |
tmnxOesDbInvalid
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5005 |
Event name | tmnxOesDbInvalid |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.5 |
Default severity | major |
Message format string | OES database invalid |
Cause | The tmnxOesDbInvalid notification may be raised under the following conditions: 1) During initial installation, if the OES is not properly commissioned. 2) The serial number in the database does not match that of the OES either because the controller was replaced or the alarm card was replaced. 3) A downgrade of OES software has occurred. 4) Equipment Controller is removed/reseated during a system process, causing file corruption. 5) The database audit failed indicating some type of corruption of the database. |
Effect | The OES is not in a normal operating mode. It does not have the correct configuration and the state of its cards is unpredictable. As a result, the OES will not boot normally and not all commands are allowed. |
Recovery | A database corruption on the OES requires that the OES be re-commissioned. The correct database is held in the host system so it will be restored to the shelf once the existing database is cleared and the host re-establishes communication with the OES. |
tmnxOesDbInvalidClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5006 |
Event name | tmnxOesDbInvalidClear |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.6 |
Default severity | major |
Message format string | OES database invalid cleared |
Cause | The tmnxOesDbInvalidClear notification is generated when the active Equipment Controller previously under tmnxOesDbInvalid condition now contains a valid database. |
Effect | The OES active Equipment Controller's database is now valid. |
Recovery | No recovery is required. |
tmnxOesDbSyncFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5003 |
Event name | tmnxOesDbSyncFailure |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.3 |
Default severity | minor |
Message format string | OES database synchronization failure |
Cause | The tmnxOesDbSyncFailure notification may be raised under the following conditions: 1) An incorrectly seated Equipment Controller. 2) The software versions on the active and inactive Equipment Controllers are not compatible. 3) A hardware problem with one or both controllers. |
Effect | The OES does not have redundancy protection between the two Equipment Controller cards. |
Recovery | Proceed as follows to clear the Database Synchronization Failed alarm: 1) Remove the Equipment Controller with the condition and examine the connector on the back of the card for damage, including bent or broken pins. 2) Examine the connector on the backplane for damage. If there is damage to the backplane of the shelf, contact your service representative. 3) Re-insert the Equipment Controller into its original slot and allow the card to initialize. 4) Repeat Step 2) through Step 4) for the second Equipment Controller. 5) Replace the Equipment Controller with the alarm condition with a new unit. If the condition is not cleared, replace the second Equipment Controller with a new unit. Follow the return and repair process to return the faulty card to an authorized repair center for replacement. |
tmnxOesDbSyncFailureClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5004 |
Event name | tmnxOesDbSyncFailureClear |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.4 |
Default severity | minor |
Message format string | OES database synchronization failure cleared |
Cause | The tmnxOesDbSyncFailureClear notification is generated when the active Equipment Controller is able to synchronize its database with the inactive Equipment Controller. |
Effect | The active and inactive Equipment Controller's databases are now synchronized. |
Recovery | No recovery required. |
tmnxOesDbUnsync
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5007 |
Event name | tmnxOesDbUnsync |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.7 |
Default severity | minor |
Message format string | OES active and standby EC databases out of sync |
Cause | The tmnxOesDbUnsync notification is generated when the active and standby Equipment Controllers are not in sync. |
Effect | The OES does not have redundancy protection between the two Equipment Controller cards. If a switchover were to occur, then the database of the newly active controller might not reflect the latest configuration. |
Recovery | Proceed as follows to clear the Database Unsynchronization alarm: 1) Perform a warm reset of the standby controller; 2) If step 1 does not clear the alarm condition, then contact the next level of technical support for help. |
tmnxOesDbUnsyncClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5008 |
Event name | tmnxOesDbUnsyncClear |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.8 |
Default severity | minor |
Message format string | OES active and standby EC databases synchronized |
Cause | The tmnxOesDbUnsyncClear notification is generated when the previously out of sync database is now synchronized between the active and standby Equipment Controller cards. |
Effect | The database is synchronized between the active and standby Equipment Controller cards. |
Recovery | No recovery is required. |
tmnxOesFan32HReqd
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5107 |
Event name | tmnxOesFan32HReqd |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.7 |
Default severity | critical |
Message format string | OES high speed fan required (FAN32H) |
Cause | The tmnxOesFan32HReqd notification is generated when the OES chassis requires high speed fan (FAN32H), but the fan inserted is not FAN32H type. |
Effect | The OES chassis is not operating with required fan type. |
Recovery | Replace the OES fan unit with FAN32H. |
tmnxOesFan32HReqdClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5108 |
Event name | tmnxOesFan32HReqdClear |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.8 |
Default severity | critical |
Message format string | Cleared: OES high speed fan required (FAN32H) |
Cause | The tmnxOesFan32HReqdClear notification is generated when the OES chassis is equipped with FAN32H or when the alarmed fan unit with tmnxOesFan32HReqd condition is removed from the slot. |
Effect | The OES chassis is operating with required FAN32H type, or the incorrect fan unit has been removed. |
Recovery | No recovery required. |
tmnxOesFanFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5109 |
Event name | tmnxOesFanFailure |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.9 |
Default severity | critical |
Message format string | OES Fan Failure: $tmnxOesNotifyFailureReason$ |
Cause |
The tmnxOesFanFailure notification is generated when the fan unit in an OES chassis has failed. tmnxOesNotifyFailureReason contains the reason for fan failure. |
Effect | The fan unit in the OES chassis is out of service. |
Recovery | If the condition causing fan failure can not be removed, replace the faulty fan unit. |
tmnxOesFanFailureClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5110 |
Event name | tmnxOesFanFailureClear |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.10 |
Default severity | critical |
Message format string | Clear OES Fan Failure: $tmnxOesNotifyFailureReason$ |
Cause |
The tmnxOesFanFailureClear notification is generated when fan failure in an OES chassis is cleared. tmnxOesNotifyFailureReason contains the reason for fan failure being cleared. |
Effect | The fan unit in the OES chassis is in service. |
Recovery | No recovery required. |
tmnxOesFanInserted
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5106 |
Event name | tmnxOesFanInserted |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.6 |
Default severity | critical |
Message format string | OES Fan Inserted |
Cause | The tmnxOesFanInserted notification is generated when the OES fan unit is inserted into its slot in the OES chassis. |
Effect | The OES chassis is now equipped with a fan unit. |
Recovery | No recovery required. |
tmnxOesFanRemoved
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5105 |
Event name | tmnxOesFanRemoved |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.5 |
Default severity | critical |
Message format string | OES Fan Removed |
Cause | The tmnxOesFanRemoved notification is generated when the OES fan unit is removed from its slot in the OES chassis. |
Effect | The function of OES fan unit is not available. |
Recovery | Insert OES fan unit into its slot. |
tmnxOesFanSpeedHigh
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5124 |
Event name | tmnxOesFanSpeedHigh |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.24 |
Default severity | minor |
Message format string | OES Fan speed is too high |
Cause | The tmnxOesFanSpeedHigh notification is generated when the fan speed is too high, based upon the current shelf cooling requirements. |
Effect | The fans run faster than required. |
Recovery | Remove and re-insert the fan tray into the chassis. If the alarm does not clear then replace the fan tray. |
tmnxOesFanSpeedHighClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5125 |
Event name | tmnxOesFanSpeedHighClear |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.25 |
Default severity | minor |
Message format string | OES Fan speed is too high cleared |
Cause | The tmnxOesFanSpeedHighClear notification is generated when the conditions causing a tmnxOesFanSpeedHigh notification have been cleared. Fan speed has returned to acceptable conditions. |
Effect | The fan speed is normal. |
Recovery | No recovery is required. |
tmnxOesFanSpeedLow
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5126 |
Event name | tmnxOesFanSpeedLow |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.26 |
Default severity | minor |
Message format string | OES Fan speed is too low |
Cause | The tmnxOesFanSpeedLow notification is generated when the fan speed is too low, based upon the current shelf cooling requirements. |
Effect | The fans run slower than required. |
Recovery | Check for airflow blockage or a dirty filter, and clear. If no problems are found, replace the fan tray. |
tmnxOesFanSpeedLowClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5127 |
Event name | tmnxOesFanSpeedLowClear |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.27 |
Default severity | minor |
Message format string | OES Fan speed is too low cleared |
Cause | The tmnxOesFanSpeedLowClear notification is generated when the conditions causing a tmnxOesFanSpeedLow notification have been cleared. Fan speed has returned to acceptable conditions. |
Effect | The fan speed is normal. |
Recovery | No recovery is required. |
tmnxOesFirmwareCondition
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5137 |
Event name | tmnxOesFirmwareCondition |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.13 |
Default severity | minor |
Message format string | Class $tmnxHwClass$: $tmnxOesEventReason$ |
Cause |
The tmnxOesFirmwareCondition notification is generated when the firmware on the card has a condition that needs to be notified to network administrator. The value of tmnxOesEventReason object specifies the specific reason for the condition. |
Effect | Not all the features may be available. |
Recovery | Perform a hard reset of the card. If the condition persists, then contact Nokia customer support. |
tmnxOesFpgaFail
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5118 |
Event name | tmnxOesFpgaFail |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.18 |
Default severity | critical |
Message format string | OES FPGA download failure |
Cause | The tmnxOesFpgaFail notification is generated during an out-of-service upgrade when the FPGA file downloaded to the card was corrupt or the FPGA failed to program correctly. |
Effect | The OES card shall automatically cold reboot and the card shall attempt to recover. While the condition exists the card remains out-of-service. |
Recovery | If the card has rebooted and the condition did not clear, then first reseat the card and see if the condition clears. If the condition remains, then replace the card and follow the return and repair process for the problem card. |
tmnxOesFpgaFailClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5119 |
Event name | tmnxOesFpgaFailClear |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.19 |
Default severity | critical |
Message format string | OES FPGA download failure cleared |
Cause | The tmnxOesFpgaFailClear notification is generated when the FPGA is successfully programmed. |
Effect | The FPGA is successfully programmed. |
Recovery | No recovery is required. |
tmnxOesFpgaTimeout
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5120 |
Event name | tmnxOesFpgaTimeout |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.20 |
Default severity | critical |
Message format string | OES FPGA timeout |
Cause | The tmnxOesFpgaTimeout notification is generated when the FPGA file download and reprogramming took longer than expected (about 45 minutes). |
Effect | The FPGA on the indicated card was not reprogrammed in the time window. |
Recovery | If the OES card is operational, wait for a maintenance window and reset the OES card. |
tmnxOesFpgaTimeoutClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5121 |
Event name | tmnxOesFpgaTimeoutClear |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.21 |
Default severity | critical |
Message format string | OES FPGA timeout cleared |
Cause | The tmnxOesFpgaTimeoutClear notification is generated when the OES FPGA timeout condition is cleared. |
Effect | The FPGA is successfully programmed. |
Recovery | No recovery is required. |
tmnxOesNtpOutOfSync
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5134 |
Event name | tmnxOesNtpOutOfSync |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.10 |
Default severity | minor |
Message format string | NTP is enabled but not in sync with NTP server |
Cause | The tmnxOesNtpOutOfSync notification is generated when NTP time on the OES is not synchronized to the host router. The host router must have NTP enabled and have recovered time from external time sources (NTP to PTP). If there is no NTP time source for the router, it will not serve time to the OES. In addition, once the NE is power cycled, it takes approximately 20-30 minutes to initialize. Thereafter, time synchronization will be completed, with a maximum delay time of 2-3 minutes. |
Effect | Timestamp of event occurring on the OES may not be exactly aligned with the host router. |
Recovery | Ensure the host router has NTP configured and a reachable time source. Allow 40 minutes for the condition to clear. |
tmnxOesNtpSync
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5135 |
Event name | tmnxOesNtpSync |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.11 |
Default severity | minor |
Message format string | NTP is enabled but not in sync with NTP server cleared |
Cause | The tmnxOesNtpSync notification is generated when NTP on the OES is synchronized to the host router. The host router is serving acceptable time toward the OES and the OES has completed initial acquisition of time from the host. |
Effect | None. |
Recovery | No recovery is required. |
tmnxOesOptTrnspndrMiscFail
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5122 |
Event name | tmnxOesOptTrnspndrMiscFail |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.22 |
Default severity | minor |
Message format string | Class $tmnxHwClass$: miscellaneous failure |
Cause | The tmnxOesOptTrnspndrMiscFail notification is generated when a non-service affecting hardware defect is detected on the card. This condition may be declared on the card due to one of the following causes: 1) Detection of line side transmitter laser bias or optical output power nearing end-of-life. 2) Detection of line receiver ITLA (Integrated Tunable Laser Assembly) laser bias or output power nearing end-of-life. 3) Detection of board-level Analog-to-Digital Conversion Digital Signal Processor (ADC DSP) device defect. 4) A device-to-device interface communication problem. |
Effect | The tmnxOesOptTrnspndrMiscFail alarm indicates a lower priority fault on the card that does not directly affect the traffic currently flowing through the card. However, the card should be replaced at the next available maintenance opportunity. |
Recovery | Replace the card. |
tmnxOesPowerSupplyFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5113 |
Event name | tmnxOesPowerSupplyFailure |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.13 |
Default severity | critical |
Message format string | OES Power Supply Failure: $tmnxOesNotifyFailureReason$ |
Cause |
The tmnxOesPowerSupplyFailure notification is generated when the power supply unit in the indicated slot of the OES chassis has failed. tmnxOesNotifyFailureReason contains the reason for the failure. |
Effect | The indicated OES power supply unit is out of service. |
Recovery | If the condition causing the power supply failure can not be removed, replace the faulty power supply unit. |
tmnxOesPowerSupplyFailureClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5114 |
Event name | tmnxOesPowerSupplyFailureClear |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.14 |
Default severity | critical |
Message format string | Clear OES Power Supply Failure: $tmnxOesNotifyFailureReason$ |
Cause |
The tmnxOesPowerSupplyFailureClear notification is generated when the power supply failure in the indicated slot of the OES chassis is cleared. tmnxOesNotifyFailureReason contains the reason for the power supply failure being cleared. |
Effect | The indicated power supply unit in the OES chassis is in service. |
Recovery | No recovery required. |
tmnxOesPowerSupplyInserted
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5112 |
Event name | tmnxOesPowerSupplyInserted |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.12 |
Default severity | major |
Message format string | OES Power Supply Inserted |
Cause | The tmnxOesPowerSupplyInserted notification is generated when the OES power supply unit is inserted into its slot in the OES chassis. |
Effect | The indicated slot of the OES chassis is now equipped with the power supply unit. |
Recovery | No recovery required. |
tmnxOesPowerSupplyRemoved
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5111 |
Event name | tmnxOesPowerSupplyRemoved |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.11 |
Default severity | major |
Message format string | OES Power Supply Removed |
Cause | The tmnxOesPowerSupplyRemoved notification is generated when an OES power supply unit is removed from its slot in the OES chassis. |
Effect | The power supply unit is not present in the indicated OES chassis slot. |
Recovery | Insert OES power supply unit into its slot. |
tmnxOesRedundancyFail
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5130 |
Event name | tmnxOesRedundancyFail |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.30 |
Default severity | minor |
Message format string | Class $tmnxHwClass$: Equipment controller redundancy failure |
Cause | The tmnxOesRedundancyFail notification is generated when the inactive equipment controller card in the OES is not providing redundancy protection. In some cases this is a transitory alarm that occurs as redundant Equipment Controllers discover one another and synchronize. Typical causes for the persistence of this alarm are: 1) Irreconcilable database schemas. 2) Inability to support system timing. 3) System timing is compromised. The inactive controller system timing module is not reporting the same status as the active controller or is reporting an error that the active controller does not have. 4) Subshelf link missing. Reasons that are generally transitory are: 1) Database not yet fully synchronized. 2) Software loads are not yet synchronized. Some or all of these may apply when the alarm is raised. |
Effect | The OES is not protected against failure of the active Equipment Controller. |
Recovery | Check for the Redundancy demerit in the detailed information of the chassis indicated. |
tmnxOesRedundancyReady
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5131 |
Event name | tmnxOesRedundancyReady |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.31 |
Default severity | minor |
Message format string | Class $tmnxHwClass$: Redundancy ready |
Cause | The tmnxOesRedundancyReady notification is generated when the equipment controller cards in the indicated OES chassis are providing redundant protection. The equipment controller cards are synchronized. |
Effect | The equipment controller cards are synchronized. |
Recovery | No recovery is required. |
tmnxOesSwBelowMinRev
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5136 |
Event name | tmnxOesSwBelowMinRev |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.12 |
Default severity | minor |
Message format string | OES running software version $tmnxOesRunningSwImage$ is below the minimum expected version $tmnxOesExpectedSwImage$ |
Cause | The tmnxOesSwBelowMinRev notification is generated when the version of the running OES software image is below the minimum expected version. |
Effect | The OES may not be operating as expected. |
Recovery | Upgrade the OES to a software image that is equal to or greater than the minimum expected version. |
tmnxOesSwUpgdCleanupFailed
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5140 |
Event name | tmnxOesSwUpgdCleanupFailed |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.16 |
Default severity | minor |
Message format string | $tmnxHwClass$ : Software upgrade cleanup failed: $tmnxOesEventReason$ |
Cause |
This event tmnxOesSwUpgdCleanupFailed notification is generated when the operation to clean-up a failed software upgrade fails. The reason for the failure is specified in the object tmnxOesEventReason. |
Effect | The OES software revision cannot be determined and so the operational state of the respective OES or OES card is indeterminate. |
Recovery | 1) Determine the reason for the upgrade failure from tmnxOesSwUpgradeCancelFlrReason in the notification. First clear the condition indicated by the reason. 2) Re-try the upgrade procedure. 3) Contact the Nokia technical support team if the re-try does not fix the problem. |
tmnxOesSwUpgdFailed
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5133 |
Event name | tmnxOesSwUpgdFailed |
SNMP notification prefix and OID | TIMETRA-OES-MIB.tmnxOesNotifications.9 |
Default severity | minor |
Message format string | OES software upgrade failed: $tmnxOesEventReason$ |
Cause |
The tmnxOesSwUpgdFailed notification is generated when a failure occurs in upgrading a component in the OES. This notification is applicable at the NE (Network Element) level and/or the card level. |
Effect | The component is not upgraded. |
Recovery | 1) Determine the reason the upgrade failed by checking the tmnxOesEventReason. First clear the condition indicated by the reason in the object tmnxOesEventReason. 2) Perform a soft reset on the card that failed to upgrade and try the upgrade procedure again. 3) Perform a hard reset on the card that failed to upgrade and try the upgrade procedure again. 4) Remove and re-insert the card that failed to upgrade and try the upgrade procedure again. 5) Replace the card that failed to upgrade and try the upgrade procedure again. 6) Inform the Nokia technical support team. |
tmnxOesTempLow
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5128 |
Event name | tmnxOesTempLow |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.28 |
Default severity | major |
Message format string | Class $tmnxHwClass$: Operational temperature too low |
Cause | The tmnxOesTempLow notification is generated when the card has detected its temperature is below operational limits. |
Effect | The card performance may degrade or may not work as expected. |
Recovery | Ensure that no environmental issues exist where the network element resides. Resolve any existing issues. |
tmnxOesTempLowClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5129 |
Event name | tmnxOesTempLowClear |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.29 |
Default severity | cleared |
Message format string | Class $tmnxHwClass$: Operational temperature too low cleared |
Cause | The tmnxOesFanSpeedLowClear notification is generated when the card has indicated its temperature is within operational limits. |
Effect | The card resumes normal operation state. |
Recovery | No recovery is required. |
tmnxOesUsrpnlPortDown
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5103 |
Event name | tmnxOesUsrpnlPortDown |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.3 |
Default severity | minor |
Message format string | OES USRPNL Port is not operational |
Cause | The tmnxOesUsrpnlPortDown notification is generated when a port (E1 or E2) on an OES USRPNL card is not operational. The reason may be a misconnected, disconnected or faulty cable, or a faulty port or USRPNL. |
Effect | If an E1 or E2 port is down then one of the control plane communication paths between the router and the OES Master Chassis is not available. The control communications with the OES may be affected rendering the OES chassis unmanageable. Other control communications paths may be available. |
Recovery | Check that the cable is correctly connected and test the cable. |
tmnxOesUsrpnlPortUp
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 5104 |
Event name | tmnxOesUsrpnlPortUp |
SNMP notification prefix and OID | TIMETRA-OES-HARDWARE-MIB.tmnxOesHwNotifications.4 |
Default severity | minor |
Message format string | OES USRPNL Port is operational |
Cause | The tmnxOesUsrpnlPortUp notification is generated when the OES USRPNL port is now operational. |
Effect | If an E1 or E2 port is up then a control plane communication path between the router and the OES Master Chassis has been established and the OES can be managed by the router. |
Recovery | No recovery required. |
tmnxPeBootloaderVersionMismatch
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2027 |
Event name | tmnxPeBootloaderVersionMismatch |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.35 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : Bootloader version mismatch - expected software version $tmnxHwSoftwareCodeVersion$, equipped version $tmnxChassisNotifyMismatchedVer$ |
Cause | Generated when there is a mismatch between the CPM and boot loader versions. tmnxChassisNotifyHwIndex identifies the CPM card. tmnxChassisNotifyMismatchedVer contains the mismatched version of bootloader and tmnxHwSoftwareCodeVersion contains the expected version of the bootloader. |
Effect | N/A |
|
Recovery | N/A |
tmnxPeBootromVersionMismatch
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2028 |
Event name | tmnxPeBootromVersionMismatch |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.36 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : Bootrom version mismatch - expected version $tmnxHwSoftwareCodeVersion$, equipped version $tmnxChassisNotifyMismatchedVer$ |
Cause | Generated when there is a mismatch between the boot rom versions. tmnxChassisNotifyHwIndex identifies the IOM card. tmnxChassisNotifyMismatchedVer contains the mismatched version of bootrom and tmnxHwSoftwareCodeVersion contains the expected version of the bootrom. |
Effect | N/A |
|
Recovery | N/A |
tmnxPeFirmwareVersionWarning
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2082 |
Event name | tmnxPeFirmwareVersionWarning |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.70 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : Firmware version $tmnxHwFirmwareCodeVersion$ is compatible but not the latest. Hard reset the MDA/IMM to upgrade to the most recent firmware if desired. |
Cause | Generated when a card is running compatible yet older firmware than the firmware associated with the current software release. tmnxChassisNotifyHwIndex identifies the card. The tmnxHwFirmwareCodeVersion object will contain the programmed the firmware version. |
Effect | N/A |
|
Recovery | N/A |
tmnxPeFPGAVersionMismatch
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2029 |
Event name | tmnxPeFPGAVersionMismatch |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.37 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : FPGA version mismatch - expected version $tmnxHwSoftwareCodeVersion$, equipped version $tmnxChassisNotifyMismatchedVer$ |
Cause | Generated when there is a mismatch between the FPGA versions. tmnxChassisNotifyHwIndex identifies the IOM card. tmnxChassisNotifyMismatchedVer contains the mismatched version of FPGA and tmnxHwSoftwareCodeVersion contains the expected version of the FPGA. |
Effect | N/A |
|
Recovery | N/A |
tmnxPeSoftwareLoadFailed
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2026 |
Event name | tmnxPeSoftwareLoadFailed |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.34 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : Failed to load software from $tmnxChassisNotifySoftwareLocation$ |
|
Cause | Generated when the CPM fails to load the software from a specified location. tmnxChassisNotifyHwIndex identifies the card for which the software load failed and tmnxChassisNotifySoftwareLocation contains the location from where the software load was attempted. |
Effect | N/A |
|
Recovery | N/A |
tmnxPeSoftwareVersionMismatch
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2025 |
Event name | tmnxPeSoftwareVersionMismatch |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.16 |
Default severity | major |
Message format string | Class $tmnxHwClass$ : Software version mismatch - expected software version $tmnxHwSoftwareCodeVersion$, equipped version $tmnxChassisNotifyMismatchedVer$ |
Cause | Generated when there is a mismatch between software versions of the active CPM and standby CPM or the CPM and IOM. tmnxChassisNotifyHwIndex identifies the mismatched CPM/IOM card and tmnxChassisNotifyMismatchedVer will contain the version of the mismatched card. The tmnxHwSoftwareCodeVersion object will contain the expected version. |
Effect | N/A |
|
Recovery | N/A |
tmnxPlcyAcctStatsEventOvrflw
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2120 |
Event name | tmnxPlcyAcctStatsEventOvrflw |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.107 |
Default severity | minor |
Message format string | Policy Accounting FP log event overflow occurred on card $tmnxChassisNotifyCardSlotNum$ at $tmnxPlcyAcctTimeEventOccured$. |
Cause | The tmnxPlcyAcctStatsEventOvrflw notification is generated when tmnxPlcyAcctStatsPoolExcResource and tmnxPlcyAcctStatsPoolLowResource occur more than 200 times because of resource usage fluctuation. The IOM raises the final trap to indicate overflow and stops logging traps. |
Effect | Some FP notifications configured on the card may not be received. |
Recovery | Notifications will resume once the Overflow clear is set. |
tmnxPlcyAcctStatsEventOvrflwClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2119 |
Event name | tmnxPlcyAcctStatsEventOvrflwClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.106 |
Default severity | minor |
Message format string | $tmnxPlcyAcctMissingNotifCount$ Policy Accounting FP log events were dropped in the last event throttling interval on card $tmnxChassisNotifyCardSlotNum$ at $tmnxPlcyAcctTimeEventOccured$. |
Cause | The tmnxPlcyAcctStatsEventOvrflwClr notification is generated when the CPM polls the IOM for traps and the overflow is cleared by logging an overflow-clear on a particular card. |
Effect | Notifications are received again since the event throttling has ended. |
Recovery | There is no recovery for this notification. |
tmnxPlcyAcctStatsPoolExcResource
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2117 |
Event name | tmnxPlcyAcctStatsPoolExcResource |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.104 |
Default severity | minor |
Message format string | Stats Resource usage on card $tmnxCardSlotNum$ and forwarding plane $tmnxFPNum$ exceeds 95 percent of the stats pool limit. Total stats resource used is ' $tmnxFPPlcyAcctStatsInUse$' and the limit is '$tmnxFPPlcyAcctStatsPool$' |
Cause | The tmnxPlcyAcctStatsPoolExcResource notification is generated when the number of in-use stats resource usage as specified by tmnxFPPlcyAcctStatsInUse exceeds 95 percent of the stats pool limit as specified by tmnxFPPlcyAcctStatsPool. |
Effect | The affected device may not provide accurate and complete statistics. |
Recovery | There is no recovery required for this notification. |
tmnxPlcyAcctStatsPoolLowResource
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2118 |
Event name | tmnxPlcyAcctStatsPoolLowResource |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.105 |
Default severity | minor |
Message format string | Stats Resource usage on card $tmnxCardSlotNum$ and forwarding plane $tmnxFPNum$ is below 85 percent of the stats pool limit. Total stats resource used is ' $tmnxFPPlcyAcctStatsInUse$' and the limit is '$tmnxFPPlcyAcctStatsPool$' |
Cause | The tmnxPlcyAcctStatsPoolLowResource notification is generated when the number of in-use stats resource as specified by tmnxFPPlcyAcctStatsInUse is below 85 percent of the stats pool limit as specified by tmnxFPPlcyAcctStatsPool. |
Effect | The configured stats pool limit is cleared when the number of in-use stats resources falls below 85 percent of the stats pool limit. |
Recovery | There is no recovery required for this notification. |
tmnxPowerSupplyWrongFanDir
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2132 |
Event name | tmnxPowerSupplyWrongFanDir |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.119 |
Default severity | major |
Message format string | The $tmnxChassisPowerSupplyFanDir$ fan direction for power supply $tmnxHwIndex$ is not supported. |
Cause |
The tmnxPowerSupplyWrongFanDir notification is generated when the airflow direction of the power supply's fan is incorrect. |
Effect | The power supply is not cooling properly and may overheat. |
Recovery | Replace the power supply with one that has the proper fan direction. |
tmnxPowerSupplyWrongFanDirClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2133 |
Event name | tmnxPowerSupplyWrongFanDirClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.120 |
Default severity | major |
Message format string | The fan direction for power supply $tmnxHwIndex$ has been corrected. |
Cause |
The tmnxPowerSupplyWrongFanDirClear notification is generated when the airflow direction of the power supply's fan is corrected. |
Effect | The fan is cooling the power supply in the proper direction. |
Recovery | No recovery required. |
tmnxRedPrimaryCPMFail
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2012 |
Event name | tmnxRedPrimaryCPMFail |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.21 |
Default severity | critical |
Message format string | Active CPM failed |
Cause | Generated when the primary CPM fails. |
Effect | N/A |
|
Recovery | N/A |
tmnxSasAlarminput1StateChanged
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 3001 |
Event name | tmnxSasAlarminput1StateChanged |
SNMP notification prefix and OID | TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSasAlarmInputNotifications.1 |
Default severity | major |
Message format string | Alarm Input " $tmnxSasAlarmInputDescription$" ("$tmnxSasAlarmInputNotifyId$") has changed status to " $tmnxSasAlarmOutputSeverity$" "$tmnxSasAlarmInputNotifyMessage$" |
Cause | A tmnxSasAlarminput1StateChanged notification is sent when status of the alarm input on pin one(1) changes. When this notification is sent, the field tmnxSasAlarmInputNotifyMessage is populated with either the tmnxSasAlarmInputTriggerMessage when the alarm is raised, or the tmnxSasAlarmInputClearMessage when the alarm is cleared. The trigger or clear actions depend on the polarity of the input as defined in tmnxSasAlarmInputPolarity. |
Effect | A desirable or undesirable event has occurred in the external equipment connected to the alarm input. Hence the characteristics of effect and the associated risks vary depending on the nature of the external equipment being monitored over the alarm input. |
Recovery | Check the external equipment, connected to the alarm input pin one(1), that resulted in this alarm and rectify the problem. |
tmnxSasAlarminput2StateChanged
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 3002 |
Event name | tmnxSasAlarminput2StateChanged |
SNMP notification prefix and OID | TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSasAlarmInputNotifications.2 |
Default severity | major |
Message format string | Alarm Input " $tmnxSasAlarmInputDescription$" ("$tmnxSasAlarmInputNotifyId$") has changed status to " $tmnxSasAlarmOutputSeverity$" "$tmnxSasAlarmInputNotifyMessage$" |
Cause | A tmnxSasAlarminput2StateChanged notification is sent when status of the alarm input on pin two(2) changes. When this notification is sent, the field tmnxSasAlarmInputNotifyMessage is populated with either the tmnxSasAlarmInputTriggerMessage when the alarm is raised, or the tmnxSasAlarmInputClearMessage when the alarm is cleared. The trigger or clear actions depend on the polarity of the input as defined in tmnxSasAlarmInputPolarity. |
Effect | A desirable or undesirable event has occurred in the external equipment connected to the alarm input. Hence the characteristics of effect and the associated risks vary depending on the nature of the external equipment being monitored over the alarm input. |
Recovery | Check the external equipment, connected to the alarm input pin two(2), that resulted in this alarm and rectify the problem. |
tmnxSasAlarminput3StateChanged
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 3003 |
Event name | tmnxSasAlarminput3StateChanged |
SNMP notification prefix and OID | TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSasAlarmInputNotifications.3 |
Default severity | major |
Message format string | Alarm Input " $tmnxSasAlarmInputDescription$" ("$tmnxSasAlarmInputNotifyId$") has changed status to " $tmnxSasAlarmOutputSeverity$" "$tmnxSasAlarmInputNotifyMessage$" |
Cause | A tmnxSasAlarminput3StateChanged notification is sent when status of the alarm input on pin three(3) changes. When this notification is sent, the field tmnxSasAlarmInputNotifyMessage is populated with either the tmnxSasAlarmInputTriggerMessage when the alarm is raised, or the tmnxSasAlarmInputClearMessage when the alarm is cleared. The trigger or clear actions depend on the polarity of the input as defined in tmnxSasAlarmInputPolarity. |
Effect | A desirable or undesirable event has occurred in the external equipment connected to the alarm input. Hence the characteristics of effect and the associated risks vary depending on the nature of the external equipment being monitored over the alarm input. |
Recovery | Check the external equipment, connected to the alarm input pin three(3), that resulted in this alarm and rectify the problem. |
tmnxSasAlarminput4StateChanged
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 3004 |
Event name | tmnxSasAlarminput4StateChanged |
SNMP notification prefix and OID | TIMETRA-SAS-ALARM-INPUT-MIB.tmnxSasAlarmInputNotifications.4 |
Default severity | major |
Message format string | Alarm Input " $tmnxSasAlarmInputDescription$" ("$tmnxSasAlarmInputNotifyId$") has changed status to " $tmnxSasAlarmOutputSeverity$" "$tmnxSasAlarmInputNotifyMessage$" |
Cause | A tmnxSasAlarminput4StateChanged notification is sent when status of the alarm input on pin four(4) changes. When this notification is sent, the field tmnxSasAlarmInputNotifyMessage is populated with either the tmnxSasAlarmInputTriggerMessage when the alarm is raised, or the tmnxSasAlarmInputClearMessage when the alarm is cleared. The trigger or clear actions depend on the polarity of the input as defined in tmnxSasAlarmInputPolarity. |
Effect | A desirable or undesirable event has occurred in the external equipment connected to the alarm input. Hence the characteristics of effect and the associated risks vary depending on the nature of the external equipment being monitored over the alarm input. |
Recovery | Check the external equipment, connected to the alarm input pin four(4), that resulted in this alarm and rectify the problem. |
tmnxSfmIcPortDDMClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4026 |
Event name | tmnxSfmIcPortDDMClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.7 |
Default severity | minor |
Message format string | SFM interconnect port SFF DDM $tmnxDDMLaneIdOrModule$ ($tmnxDDMFailedObject$) cleared |
Cause | The tmnxSfmIcPortDDMFailure notification is generated when an SFF in an SFM interconnect port that supports Digital Diagnostic Monitoring (DDM) clears a failed state. |
Effect | N/A |
|
Recovery | N/A |
tmnxSfmIcPortDDMFailure
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4025 |
Event name | tmnxSfmIcPortDDMFailure |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.6 |
Default severity | minor |
Message format string | SFM interconnect port SFF DDM $tmnxDDMLaneIdOrModule$ ($tmnxDDMFailedObject$) raised |
Cause | The tmnxSfmIcPortDDMFailure notification is generated when an SFF in an SFM interconnect port that supports Digital Diagnostic Monitoring (DDM) enters a failed state. |
Effect | N/A |
|
Recovery | N/A |
tmnxSfmIcPortDegraded
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4027 |
Event name | tmnxSfmIcPortDegraded |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.8 |
Default severity | minor |
Message format string | Switch fabric capacity associated with the SFM interconnect port is in a $tmnxSfmIcPortDegradeState$ state |
Cause |
The tmnxSfmIcPortDegraded notification is generated when the system has detected a degradation of the switch fabric that is associated with a particular SFM interconnect port. The value of tmnxSfmIcPortDegradeState will reflect this condition by having a value that is NOT 'none (1)'. If the value of tmnxSfmIcPortDegradeState is 'degraded (2)' the SFM interconnect port can still carry some traffic but not at the full capacity of the port. The port and attached cable are not necessarily the cause of the degradation but are a likely cause. |
Effect | Switch fabric capacity on this port is reduced when tmnxSfmIcPortDegradeState is degraded. This may not be causing any impact to service because of redundancy in the fabric. |
Recovery | Although it may not be necessary to maintain full service, replacing the affected components may restore some fabric capacity." |
tmnxSfmIcPortDegradedClear
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4028 |
Event name | tmnxSfmIcPortDegradedClear |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.9 |
Default severity | minor |
Message format string | Switch fabric capacity associated with the SFM interconnect port is not in a degraded state |
Cause | The tmnxSfmIcPortDegradedClear notification is generated when the switch fabric associated with the SFM interconnect port is not degraded. This occurs when the value of tmnxSfmIcPortDegradeState is 'none (1)'." |
Effect | N/A |
|
Recovery | N/A |
tmnxSfmIcPortDown
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4017 |
Event name | tmnxSfmIcPortDown |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.1 |
Default severity | minor |
Message format string | Possible messages:
|
Cause | The tmnxSfmIcPortDown alarm is generated when the SFM interconnect port is not operational. The reason may be a cable connected incorrectly, a disconnected cable, a faulty cable, or a misbehaving SFM interconnect port or SFM card. |
Effect | This port can no longer be used as part of the user plane fabric between chassis. Other fabric paths may be available resulting in no loss of capacity. |
Recovery | A manual verification and testing of each SFM interconnect port is required to ensure fully functional operation. Physical replacement of cabling may be required. |
tmnxSfmIcPortSFFInserted
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4019 |
Event name | tmnxSfmIcPortSFFInserted |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.3 |
Default severity | minor |
Message format string | SFM interconnect port SFF inserted |
Cause | The tmnxSfmIcPortSFFInserted notification is generated when the Small Form Factor (SFF) pluggable optical module (eg. CXP) is inserted into an SFM interconnect port. |
Effect | This event is for notification only. |
Recovery | N/A |
tmnxSfmIcPortSFFRemoved
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4020 |
Event name | tmnxSfmIcPortSFFRemoved |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.4 |
Default severity | minor |
Message format string | SFM interconnect port SFF removed |
Cause | The tmnxSfmIcPortSFFRemoved notification is generated when the SFF (eg. CXP) is removed from the SFM interconnect port. |
Effect | Removing the module will cause the port to go down. This port can no longer be used as part of the user plane fabric between chassis. Other fabric paths may be available resulting in no loss of capacity. |
Recovery | Insert a working SFF into the SFM interconnect port. |
tmnxSfmIcPortUp
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 4018 |
Event name | tmnxSfmIcPortUp |
SNMP notification prefix and OID | TIMETRA-CHASSIS-INTERCONNECT-MIB.tmnxSfmIcPortNotifications.2 |
Default severity | minor |
Message format string | SFM interconnect port is operational |
Cause | The tmnxSfmIcPortUp notification is generated when the SFM interconnect port is operational again. |
Effect | This port can now be used as part of the user plane fabric between chassis. |
Recovery | N/A |
tmnxSyncIfTimBITS2048khzUnsup
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2134 |
Event name | tmnxSyncIfTimBITS2048khzUnsup |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.123 |
Default severity | major |
Message format string | The revision of $tmnxHwIndex$ does not meet the specifications to support the 2048kHz BITS interface type. |
Cause | The tmnxSyncIfTimBITS2048khzUnsup notification is generated when the value of tSyncIfTimingAdmBITSIfType is set to 'g703-2048khz (5)' and the CPM does not meet the specifications for the 2048kHz BITS output signal under G.703. |
Effect | The BITS input will not be used as the Sync reference and the 2048kHz BITS output signal generated by the CPM is squelched. |
Recovery | Replace the CPM with one that is capable of generating the 2048kHz BITS output signal, or set tSyncIfTimingAdmBITSIfType to a value other than 'g703-2048khz (5)'. |
tmnxSyncIfTimBITS2048khzUnsupClr
|
Property name | Value |
|---|---|
Application name | CHASSIS |
Event ID | 2135 |
Event name | tmnxSyncIfTimBITS2048khzUnsupClr |
SNMP notification prefix and OID | TIMETRA-CHASSIS-MIB.tmnxChassisNotification.124 |
Default severity | major |
Message format string | $tmnxHwIndex$ has been replaced with a CPM that meets the specification for 2048kHz or the BITS interface type is no longer 2048kHz. |
Cause | The tmnxSyncIfTimBITS2048khzUnsupClr notification is generated when a tmnxSyncIfTimBITS2048khzUnsup notification is outstanding and the CPM was replaced with one that meets the specifications for the 2048kHz BITS output signal under G.703 or tSyncIfTimingAdmBITSIfType is set to a value other than 'g703-2048khz (5)'. |
Effect | The CPM can now support the configuration of tSyncIfTimingAdmBITSIfType. |
Recovery | No recovery required. |