SATELLITE
tmnxSatelliteOperStateChange
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2001 |
Event name | tmnxSatelliteOperStateChange |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.1 |
Default severity | minor |
Message format string | Possible messages:
|
Cause |
The tmnxSatelliteOperStateChange notification is generated when there is a change in tmnxHwOperState for the satellite. |
Effect | The satellite has changed states. The tmnxSatNotifyFailureReason is only valid when tmnxHwOperState is 'failed (5)', and should otherwise be blank. |
Recovery | Contact Nokia customer support if tmnxSatNotifyFailureReason does not provide enough information to rectify the situation. |
tmnxSatLocalForwardSapStateChg
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2017 |
Event name | tmnxSatLocalForwardSapStateChg |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.17 |
Default severity | minor |
Message format string | Satellite Local Forward $tmnxSatLocalForwardId$ SAP $tmnxSatPortId$:$tmnxSatEncapValue$ changed to administrative state: $tmnxSatLocalForwardSapAdminState$, operational state: $tmnxSatLocalForwardSapOperState$ |
Cause | The tmnxSatLocalForwardSapStateChg notification is generated when the system detects a change in the administrative state, or operational state of the satellite local forward SAP. |
Effect | The administrative state or operational state of the satellite local forward SAP has changed. |
Recovery | If the administrative state is 'inService (2)', and the operational state is 'down (2)', check to ensure valid configuration of the satellite local forward SAP, and verify the connection of the satellite to the host. Contact Nokia customer support if the issue cannot be resolved. |
tmnxSatLocalForwardStateChg
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2016 |
Event name | tmnxSatLocalForwardStateChg |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.16 |
Default severity | minor |
Message format string | Satellite Local Forward $tmnxSatLocalForwardId$ changed to administrative state: $tmnxSatLocalForwardAdminState$, operational state: $tmnxSatLocalForwardOperState$ |
Cause |
The tmnxSatLocalForwardStateChg notification is generated when the system detects a change in the administrative state, or operational state of the satellite local forward. |
Effect | The administrative state or operational state of the satellite local forward has changed. |
Recovery | If the administrative state is 'inService (2)', and the operational state is 'down (2)', check to ensure valid configuration of the satellite local forward, and verify the connection of the satellite to the host. Contact Nokia\ customer support if the issue cannot be resolved. |
tmnxSatSyncIfTimHoldover
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2006 |
Event name | tmnxSatSyncIfTimHoldover |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.6 |
Default severity | critical |
Message format string | Synchronous timing interface on satellite $tmnxHwIndex$ is in holdover state |
Cause | The tmnxSatSyncIfTimHoldover notification is generated when the synchronous equipment timing subsystem of the satellite transitions into a holdover state. |
Effect | The transmit timing of all synchronous interfaces on the satellite are no longer synchronous with the host. This could result in traffic loss. |
Recovery | Investigate the state of the two input timing references on the satellite and the links between the host and the satellite (i.e. the uplinks) that drive them for failures. |
tmnxSatSyncIfTimHoldoverClear
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2007 |
Event name | tmnxSatSyncIfTimHoldoverClear |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.7 |
Default severity | cleared |
Message format string | Synchronous timing interface on satellite $tmnxHwIndex$, holdover state cleared |
Cause | The tmnxSatSyncIfTimHoldoverClear notification is generated when the synchronous equipment timing subsystem of the satellite transitions out of the holdover state. |
Effect | This notification is for informational purposes only. |
Recovery | No recovery required. |
tmnxSatSyncIfTimRef1Alarm
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2008 |
Event name | tmnxSatSyncIfTimRef1Alarm |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.8 |
Default severity | minor |
Message format string | Synchronous timing interface on satellite $tmnxHwIndex$, alarm $tmnxSatNotifySyncIfTimRefAlarm$ on reference 1 |
Cause | The tmnxSatSyncIfTimRef1Alarm notification is generated when an alarm condition on the first timing reference is detected. |
Effect | If the other timing reference is free of faults, the satellite no longer has a backup timing reference. If the other timing reference also has a fault, the satellite will likely no longer be synchronous with the host. |
Recovery | Investigate the state of the link between the host and the satellite (i.e. the uplink) that drives the first timing reference on the satellite for faults. |
tmnxSatSyncIfTimRef1AlarmClear
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2009 |
Event name | tmnxSatSyncIfTimRef1AlarmClear |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.9 |
Default severity | cleared |
Message format string | Synchronous timing interface on satellite $tmnxHwIndex$, alarm $tmnxSatNotifySyncIfTimRefAlarm$ on reference 1 cleared |
Cause | The tmnxSatSyncIfTimRef1AlarmClear notification is generated when the alarm condition on the first timing reference is cleared. |
Effect | This notification is for informational purposes only. |
Recovery | No recovery required. |
tmnxSatSyncIfTimRef1Quality
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2004 |
Event name | tmnxSatSyncIfTimRef1Quality |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.4 |
Default severity | minor |
Message format string | Synchronous timing interface on satellite $tmnxSatId$, reference 1 received quality level $tmnxSatSyncIfTimingRef1RxQltyLvl$ |
Cause | The tmnxSatSyncIfTimRef1Quality notification is generated when the received quality level changes on the first timing reference of the satellite. |
Effect | This notification is for informational purposes only. |
Recovery | No recovery required. |
tmnxSatSyncIfTimRef2Alarm
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2010 |
Event name | tmnxSatSyncIfTimRef2Alarm |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.10 |
Default severity | minor |
Message format string | Synchronous timing interface on satellite $tmnxHwIndex$, alarm $tmnxSatNotifySyncIfTimRefAlarm$ on reference 2 |
Cause | The tmnxSatSyncIfTimRef2Alarm notification is generated when an alarm condition on the second timing reference is detected. |
Effect | If the other timing reference is free of faults, the satellite no longer has a backup timing reference. If the other timing reference also has a fault, the satellite will likely no longer be synchronous with the host. |
Recovery | Investigate the state of the link between the host and the satellite (i.e. the uplink) that drives the second timing reference on the satellite for faults. |
tmnxSatSyncIfTimRef2AlarmClear
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2011 |
Event name | tmnxSatSyncIfTimRef2AlarmClear |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.11 |
Default severity | cleared |
Message format string | Synchronous timing interface on satellite $tmnxHwIndex$, alarm $tmnxSatNotifySyncIfTimRefAlarm$ on reference 2 cleared |
Cause | The tmnxSatSyncIfTimRef1AlarmClear notification is generated when the alarm condition on the second timing reference is cleared. |
Effect | This notification is for informational purposes only. |
Recovery | No recovery required. |
tmnxSatSyncIfTimRef2Quality
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2005 |
Event name | tmnxSatSyncIfTimRef2Quality |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.5 |
Default severity | minor |
Message format string | Synchronous timing interface on satellite $tmnxSatId$, reference 2 received quality level $tmnxSatSyncIfTimingRef2RxQltyLvl$ |
Cause | The tmnxSatSyncIfTimRef2Quality notification is generated when the received quality level changes on the second timing reference of the satellite. |
Effect | This notification is for informational purposes only. |
Recovery | No recovery required. |
tmnxSatSyncIfTimRefSwitch
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2002 |
Event name | tmnxSatSyncIfTimRefSwitch |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.2 |
Default severity | minor |
Message format string | Synchronous timing interface on satellite $tmnxSatId$, timing reference changed to $tmnxSatSyncIfTimingRef1InUse$ |
Cause | The tmnxSatSyncIfTimRefSwitch notification is generated when there is a change of which timing reference is providing timing for the satellite. |
Effect | This event is for notification only. |
Recovery | No recovery required. |
tmnxSatSyncIfTimSystemQuality
Property name | Value |
---|---|
Application name | SATELLITE |
Event ID | 2003 |
Event name | tmnxSatSyncIfTimSystemQuality |
SNMP notification prefix and OID | TIMETRA-SATELLITE-MIB.tmnxSatelliteNotifications.3 |
Default severity | minor |
Message format string | Synchronous timing interface on satellite $tmnxSatId$, system quality level changed to $tmnxSatSyncIfTimingSystemQltyLvl$ |
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. |