MC_REDUNDANCY
srrpPacketDiscarded
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2025 |
Event name | srrpPacketDiscarded |
SNMP notification prefix and OID | N/A |
Default severity | minor |
Message format string | Discarded SRRP packet from $tmnxMcPeerSrcIpAddr$ because $srrpPacketDiscardReason$ |
Cause | The following checks are performed on an incoming SRRP packet 1. verify that the IP TTL is 255. 2. verify the SRRP version. 3. verify that the received packet length is greater than or equal to the SRRP header. 4. verify the SRRP checksum. 5. perform authentication specified by Auth Type. If any one of the above checks fail, the receiver must discard the packet and log the event. |
Effect | N/A |
|
Recovery | N/A |
tMcIPsecDomainActivityStateChg
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2046 |
Event name | tMcIPsecDomainActivityStateChg |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.42 |
Default severity | warning |
Message format string | Multi-chassis ipsec domain $tMcIPsecDomainId$ local activity state changed from $tMcIPsecDomainActyStateOld$ to $tMcIPsecDomainActivityState$ because $tMcIPsecDomainActyStateChR$, and the active router in the domain is $tMcIPsecDmCurActiveRouterId$ |
Cause |
The notification tMcIPsecDomainActivityStateChg is generated whenever activity election state of a domain changes. |
Effect | This notification is informational. The effects associated with this notification depend upon the new state of the domain. For example, when a domain becomes active it will begin attracting traffic towards its chassis and will begin to manage IKE sessions for all IPsec tunnels in that domain. |
Recovery | No recovery actions are required, although unexpected state transitions often indicate causal fault conditions which may require investigation. |
tMcIpsecDomainProtStatusChg
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2047 |
Event name | tMcIpsecDomainProtStatusChg |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.43 |
Default severity | warning |
Message format string | Protection status for the multi-chassis ipsec domain $tMcIPsecDomainId$ changed to $tMcIPsecDomainProtectStatus$ |
Cause | The notification tMcIpsecDomainProtStatusChg is generated whenever protection status of a ipsec-domain changes. |
Effect | This notification is informational. A change in tMcIPsecDomainProtectStatus to 'nominal' indicates protection status readiness for switchover. |
Recovery | No recovery actions are required. |
tMcPeerIPsecTnlGrpMasterStateChg
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2035 |
Event name | tMcPeerIPsecTnlGrpMasterStateChg |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.34 |
Default severity | warning |
Message format string | Master state for the multi-chassis ipsec peer $tmnxMcPeerIpAddr$ tunnel-group $tMcPeerIPsecTnlGrpId$ changed from $tMcPeerIPsecTnlGrpMasterStateOld$ to $tMcPeerIPsecTnlGrpMasterState$ because $tMcPeerIPsecTnlGrpMasterStateChR$ |
|
Cause | The notification tMcPeerIPsecTnlGrpMasterStateChg is generated whenever mastership election state of a tunnel-group changes. |
Effect | This trap is informational. The effects associated with this notification depend upon the new state of the tunnel-group. For example, when a tunnel-group becomes master it will begin attracting traffic towards its chassis and will begin to manage IKE sessions for all IPsec tunnels in that tunnel-group. |
Recovery | No recovery actions are required, although unexpected state transitions often indicate causal fault conditions which may require investigation. |
tMcPeerIPsecTnlGrpProtStatusChg
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2036 |
Event name | tMcPeerIPsecTnlGrpProtStatusChg |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.35 |
Default severity | warning |
Message format string | Protection status for the multi-chassis ipsec peer $tmnxMcPeerIpAddr$ tunnel-group $tMcPeerIPsecTnlGrpId$ changed to $tMcPeerIPsecTnlGrpProtectStatus$ |
Cause |
The notification tMcPeerIPsecTnlGrpProtStatusChg is generated whenever protection status of a tunnel-group changes. |
Effect | This notification is informational. A change in tMcPeerIPsecTnlGrpProtectStatus to 'nominal' indicates protection status readiness for switchover. |
Recovery | No recovery actions are required. |
tmnxMCEPSessionPsvModeDisabled
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2034 |
Event name | tmnxMCEPSessionPsvModeDisabled |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.33 |
Default severity | warning |
Message format string | Passive-mode for the multi-chassis endpoint peer $tmnxMcPeerIpAddr$ with source $tmnxMcPeerSrcIpAddr$ is disabled |
Cause | Passive-mode for the session between a multi-chassis endpoint and its peer has been 'disabled' from either local or peer. |
Effect | N/A |
|
Recovery | Configure passive-mode enabled on local or peer multi-chassis endpoint. |
tmnxMCEPSessionPsvModeEnabled
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2033 |
Event name | tmnxMCEPSessionPsvModeEnabled |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.32 |
Default severity | warning |
Message format string | Passive-mode for the multi-chassis endpoint peer $tmnxMcPeerIpAddr$ with source $tmnxMcPeerSrcIpAddr$ is enabled. Passive-mode with peer has $tmnxMcPeerEPPsvModeConfigState$ |
Cause |
Passive-mode for the session between a multi-chassis endpoint and its peer has been 'enabled' from either local or peer. |
Effect | N/A |
|
Recovery | N/A |
tmnxMcLagInfoLagChanged
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2014 |
Event name | tmnxMcLagInfoLagChanged |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.14 |
Default severity | warning |
Message format string | tmnxMcLagInfoLagTable: Peer $tmnxMcPeerIpAddrForNotify$ configuration changed. |
Cause | Entries in tmnxMcLagInfoLagTable were changed. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxMcOmcrClientNumEntriesHigh
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2038 |
Event name | tmnxMcOmcrClientNumEntriesHigh |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.38 |
Default severity | minor |
Message format string | The number of warm standby MCS entries for application $tmnxMcsClientApplication$ is becoming too high: $tmnxMcNotifyNumber$% (peer $tmnxMcPeerIpAddr$) |
Cause |
The notification tmnxMcOmcrClientNumEntriesHigh is generated when this system is configured as an OMCR warm standby system, and the total number of entries in the MCS database for a particular application becomes high. This system is configured as a warm standby system as soon as the value of the object tmnxMcPeerWarmStandby is equal to 'true' for any multi-chassis peer in this system. The total number of entries is the sum of the values of the object tmnxMcsClientNumEntries for the client application specified by tmnxMcsClientApplication. The maximum number of entries for a client application is equal to one million. The value of tmnxMcNotifyNumber indicates the ratio in percent of the total number of entries and the maximum number of entries. The threshold ratios are at 80%, 90% and 100%. The values of tmnxMcPeerIpType and tmnxMcPeerIpAddr indicate the peer that reached the threshold. |
Effect | When the 80% and 90% threshold is crossed, there is no effect. When the 100% threshold is exceeded, the peer indicated by the values of tmnxMcPeerIpType and tmnxMcPeerIpAddr is shut down automatically by this system (the value of tmnxMcPeerSyncAdminState is set to 'outOfService' and the value of tmnxMcPeerSyncOperFlags is set to 'omcrNumEntriesHigh'). |
Recovery | Reconfigure the oversubscribed multi-chassis redundancy set-up to reduce the number of entries protected by this system. When the total number of entries in the MCS database for this client application becomes lower than the 80% threshold again, there is no further notification. |
tmnxMcOmcrStatFailedChanged
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2037 |
Event name | tmnxMcOmcrStatFailedChanged |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.37 |
Default severity | minor |
Message format string | $tmnxMcOmcrStatClientApplication$ OMCR protection with $tmnxMcOmcrStatAccessProtection$ instance $tmnxMcOmcrStatIndex$ $tmnxMcOmcrStatFailed$ - $tmnxMcOmcrStatFailure$ |
Cause | The notification tmnxMcOmcrStatFailedChanged is generated when the value of the object tmnxMcOmcrStatFailed changes. The most interesting change is from 'notAct' to any of the other values; when an OMCR client application access protection instance (for example an SRRP instance) becomes active, the system will attempt to allocate resources for all associated client application entries (for example IPOE subscriber hosts); if this succeeds, the value of tmnxMcOmcrStatFailed becomes 'no', if it fails, it becomes 'yes'. |
Effect | A transition from 'notAct' or 'no' to 'yes' means that the traffic of some or all associated client application entries' is being dropped. For example, all traffic from some or all of the IPOE subscriber hosts protected by a failed SRRP instance is dropped by this system. A transition to 'no' means that the system has successfully allocated resources for the traffic of all associated client application entries. A transition to 'notAct' means that this system is not performing the active role anymore for this access protection instance. For example, the value of the object tmnxSrrpOperState has become different from 'master' for the corresponding instance. |
Recovery | There are three recovery actions possible, depending on the reason of the transition of the access protection instance. If it is caused by a problem in the access network, fix that problem, or make additional resources available for this access protection instance. If it is caused by a misconfiguration of this system, correct that, or make additional resources available for this access protection instance. |
tmnxMcPeerEPBfdSessionClose
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2028 |
Event name | tmnxMcPeerEPBfdSessionClose |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.27 |
Default severity | warning |
Message format string | Multi-Chassis endpoint closed BFD session for peer $tmnxMcPeerIpAddr$ with source $tmnxMcPeerSrcIpAddr$ |
Cause | A multi-chassis endpoint is closing a BFD session to the multi-chassis endpoint peer. |
Effect | N/A |
|
Recovery | N/A |
tmnxMcPeerEPBfdSessionDown
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2030 |
Event name | tmnxMcPeerEPBfdSessionDown |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.29 |
Default severity | warning |
Message format string | Operational state of the BFD session for multi-chassis endpoint peer $tmnxMcPeerIpAddr$ and source $tmnxMcPeerSrcIpAddr$ is changed to down |
Cause | The operational state of a BFD session between a multi-chassis endpoint and its peer has changed to 'down'. |
Effect | N/A |
|
Recovery | N/A |
tmnxMcPeerEPBfdSessionOpen
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2027 |
Event name | tmnxMcPeerEPBfdSessionOpen |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.26 |
Default severity | warning |
Message format string | Multi-Chassis endpoint attempted to open BFD session for peer $tmnxMcPeerIpAddr$ and source $tmnxMcPeerSrcIpAddr$ with status= $tmnxMcPeerEPBfdSessionOpenStatus$ |
|
Cause | A multi-chassis endpoint is attempting to open a BFD session to the multi-chassis endpoint peer. |
Effect | N/A |
|
Recovery | N/A |
tmnxMcPeerEPBfdSessionUp
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2029 |
Event name | tmnxMcPeerEPBfdSessionUp |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.28 |
Default severity | warning |
Message format string | Operational state of the BFD session for multi-chassis endpoint peer $tmnxMcPeerIpAddr$ and source $tmnxMcPeerSrcIpAddr$ is changed to up |
Cause | The operational state of a BFD session between a multi-chassis endpoint and its peer is changed to 'up'. |
Effect | N/A |
|
Recovery | N/A |
tmnxMcPeerEPOperDown
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2031 |
Event name | tmnxMcPeerEPOperDown |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.30 |
Default severity | warning |
Message format string | Multi-Chassis endpoint peer $tmnxMcPeerIpAddr$ with source $tmnxMcPeerSrcIpAddr$ oper state changed to Down |
Cause | A multi-chassis endpoint detected a time-out while communicating with the multi-chassis endpoint peer. |
Effect | N/A |
|
Recovery | N/A |
tmnxMcPeerEPOperUp
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2032 |
Event name | tmnxMcPeerEPOperUp |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.31 |
Default severity | warning |
Message format string | Multi-Chassis endpoint peer $tmnxMcPeerSrcIpAddr$ with source $tmnxMcPeerIpAddr$ oper state changed to Up |
Cause | A multi-chassis endpoint has cleared the time-out condition in communicating with the multi-chassis endpoint peer. |
Effect | N/A |
|
Recovery | N/A |
tmnxMcPeerRingsOperStateChanged
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2022 |
Event name | tmnxMcPeerRingsOperStateChanged |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.22 |
Default severity | warning |
Message format string | The MC-Ring operational state of peer $tmnxMcPeerIpAddr$ changed to $tmnxMcPeerRingsOperState$. |
Cause | The notification tmnxMcPeerRingsOperStateChanged is sent when the operational state, with respect to multi-chassis ring operation, of a peer changed. unknown | No rings are configured for this peer. inService | The signaling connection for mc-ring operation | is operational. outOfService | The signaling connection for mc-ring operation | has timed out. transition | Not implemented. |
Effect | unknown | None. inService | The signaling connection for mc-ring operation | is operational. outOfService | None, as long as no rings are in state 'broken'.The MCS connection is likely to be out of service. If some rings are in state 'broken', those rings will suffer degraded functionality. transition | Not implemented. |
Recovery | The recovery depends on the operational state of the ring: unknown | None. inService | None. outOfService | Restore the IP connectivity between the local peer and the remote peer. transition | Not implemented. |
tmnxMcPeerSyncStatusChanged
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2004 |
Event name | tmnxMcPeerSyncStatusChanged |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.4 |
Default severity | warning |
Message format string | The Sync status of peer $tmnxMcPeerIpAddr$ changed to $tmnxMcPeerSyncStatus$ |
Cause | The event is generated when the sync state changes. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxMcRedundancyMismatchDetected
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2002 |
Event name | tmnxMcRedundancyMismatchDetected |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.2 |
Default severity | warning |
Message format string | $tmnxMcLagConfigMismatchString$ |
Cause | The event is generated when a configuration mismatch is detected. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxMcRedundancyMismatchResolved
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2003 |
Event name | tmnxMcRedundancyMismatchResolved |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.3 |
Default severity | warning |
Message format string | $tmnxMcLagConfigMismatchString$ |
Cause | The event is generated when a configuration mismatch is resolved. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxMcRedundancyPeerStateChanged
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2001 |
Event name | tmnxMcRedundancyPeerStateChanged |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.1 |
Default severity | warning |
Message format string | The MC-LAG operational status of peer $tmnxMcPeerIpAddr$ changed to $tmnxMcLagConfigOperState$ |
Cause | The event is generated when the MC lag has changed its operational state. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxMcRingInbCtrlOperStateChgd
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2017 |
Event name | tmnxMcRingInbCtrlOperStateChgd |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.17 |
Default severity | warning |
Message format string | The MC-Ring operational state of the inband control connection of ring $tmnxMcPeerIpAddr$::$tmnxMcPeerSyncPortSyncTag$ changed to $tmnxMcRingInfoOperState$. |
Cause |
The notification tmnxMcRingInbCtrlOperStateChgd is generated when the operational state of a multi-chassis ring's inband control connection changes. unknown : none connected : the inband control connection with the peer is operational broken : the inband control connection with the peer has timed out testing : the inband control connection with the peer is being set up. Waiting for result notConfigured : the inband control connection with the peer is not configured |
Effect | The operational state of the inband control connection affects the operational state of the ring. |
Recovery | The recovery depends on the operational state of the ring. |
tmnxMcRingNodeLocOperStateChgd
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2018 |
Event name | tmnxMcRingNodeLocOperStateChgd |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.18 |
Default severity | warning |
Message format string | The MC-Ring Node operational state of ring node $tmnxMcPeerIpAddr$::$tmnxMcPeerSyncPortSyncTag$::$tmnxMcRingNodeName$ changed to $tmnxMcRingNodeInfoLocOperState$ while in-use is $tmnxMcRingNodeInfoInUse$. |
Cause | The notification tmnxMcRingNodeLocOperStateChgd is generated upon a change of the operational state of a provisioned ring node as monitored by the local chassis, or when an unprovisioned ring node appears or disappears. unknown : none notProvisioned : the node is configured on the peer but not on this system configErr : the local configuration of the node is incorrect notTested : the ring node connectivity verification is shut down testing : temporary state connected : none disconnected : none |
Effect | unknown : none notProvisioned : no effect configErr : no effect notTested : no effect testing : no effect the effect of the operational state of the ring node depends on the operational state of the ring; when the operational state of the ring is 'broken' connected : all MAC addresses associated with this ring node are put on the SAP disconnected : all MAC addresses associated with this ring node are put on the shunt |
Recovery | Recovery is only required if the operational state of the ring is 'broken'. Repair the ring connection with the peer. |
tmnxMcRingOperStateChanged
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2016 |
Event name | tmnxMcRingOperStateChanged |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.16 |
Default severity | warning |
Message format string | The MC-Ring operational state of ring $tmnxMcPeerIpAddr$::$tmnxMcPeerSyncPortSyncTag$ changed to $tmnxMcRingInfoOperState$. |
Cause |
The notification tmnxMcRingOperStateChanged is generated when the operational state of a multi-chassis ring changes. unknown : none shutdown : none configErr : none noPeer : the peer has no corresponding ring configured connected : the inband control connection with the peer is operational broken : the inband control connection with the peer has timed out localBroken : the inband control connection with the peer is known to be broken because of a local failure or local administrative action conflict : the inband control connection with the peer has timed out but the physical connection is still OK; the failure of the inband signaling connection is caused by some misconfiguration a conflict between the configuration of this system and its peer or a misconfiguration on one of the ring access node systems testingRing : the inband control connection with the peer is being set up. Waiting for result waitingForPeer : verifying if this ring is configured on the peer |
Effect | unknown : none shutdown : the ring brings all SAPs of path-a and path-b operational state 'up' configErr : if there is no peer ring, the ring brings all SAPs on path-a and path-b operational state 'up'; if there is a peer ring, the ring brings all SAPs on path-a and path-b operational state 'down' noPeer : the ring brings all SAPs of path-a and path-b operational state 'up' connected : the ring brings all SAPs of its own path operational state 'up' and all SAPs of the other path operational state 'down' broken : the ring brings all SAPs of path-a and path-b operational state 'up' localBroken : this system brings all SAPs of path-a and path-b operational state 'down' unless they belong to the excluded-path conflict : the ring brings all SAPs of its own path operational state 'up' and all SAPs of the other path operational state 'down' testingRing : the ring does not change the operational state of any SAP waitingForPeer: the ring does not change the operational state of any SAP |
Recovery | The recovery depends on the operational state of the ring: unknown : none shutdown : no recovery required configErr : correct the configuration of the ring on this system noPeer : no recovery required connected : no recovery required broken : repair the ring connection with the peer localBroken : repair the local failure or undo the administrative action that caused the failure conflict : make the ring configuration on this system consistent with the ring configuration on the peer testingRing : temporary state waitingForPeer : temporary state |
tmnxMcSyncClientAlarmCleared
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2006 |
Event name | tmnxMcSyncClientAlarmCleared |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.6 |
Default severity | warning |
Message format string | $tmnxMcPeerSyncClient$ back in sync with peer $tmnxMcPeerIpAddrForNotify$. |
Cause |
The event is generated when the application has the resources to become in sync again. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxMcSyncClientAlarmRaised
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2005 |
Event name | tmnxMcSyncClientAlarmRaised |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.5 |
Default severity | warning |
Message format string | $tmnxMcPeerSyncClient$ lost sync with peer $tmnxMcPeerIpAddrForNotify$. |
Cause |
The event is generated when the application runs out of resources to sync with the database. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxMcSyncClockSkewCleared
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2020 |
Event name | tmnxMcSyncClockSkewCleared |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.20 |
Default severity | warning |
Message format string | The system clock for MCS peer $tmnxMcPeerIpAddrForNotify$ differs $tmnxMcPeerClockSkew$ seconds from the local system clock. |
Cause | The MCS peer system clock time has returned to less than 60 seconds different than the local system clock. This notification would only be generated following a tmnxMcSyncClockSkewRaised notification. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxMcSyncClockSkewRaised
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2019 |
Event name | tmnxMcSyncClockSkewRaised |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.19 |
Default severity | warning |
Message format string | The system clock for MCS peer $tmnxMcPeerIpAddrForNotify$ differs $tmnxMcPeerClockSkew$ seconds from the local system clock. |
Cause | The MCS peer system clock time is greater than 60 seconds different than the local system clock. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxSrrpBecameBackup
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2024 |
Event name | tmnxSrrpBecameBackup |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.24 |
Default severity | minor |
Message format string | SRRP instance $tmnxSrrpOperID$ on interface $vRtrIfIndex$ changed state to backup - current master is $tmnxMcPeerIpAddrForNotify$ |
Cause |
The sending agent has transitioned to 'Backup' state. |
Effect | N/A |
|
Recovery | N/A |
tmnxSrrpBfdIntfSessStateChgd
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2026 |
Event name | tmnxSrrpBfdIntfSessStateChgd |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.25 |
Default severity | minor |
Message format string | BFD session on service $tmnxSrrpNotifBfdIntfSvcId$ interface $tmnxSrrpNotifBfdIntfIfName$ to peer $tmnxSrrpNotifBfdIntfDestIp$ changed state to $tmnxSrrpNotifBfdIntfSessState$. |
Cause | The operational state of BFD session of the SRRP instance changed. |
Effect | N/A |
|
Recovery | N/A |
tmnxSrrpDualMaster
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2013 |
Event name | tmnxSrrpDualMaster |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.13 |
Default severity | warning |
Message format string | SRRP ID $tmnxSrrpOperID$: Dual Master detected on both peer $tmnxMcPeerIpAddrForNotify$ / interface $tmnxMcRemoteGrpIfNameForNotify$ and local $tmnxMcPeerSrcIpAddr$ / interface $vRtrIfIndex$. |
Cause | Both the local and remote SRRP instances are in the master state. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxSrrpDuplicateSubIfAddress
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2021 |
Event name | tmnxSrrpDuplicateSubIfAddress |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.21 |
Default severity | warning |
Message format string | SRRP id $tmnxSrrpOperID$: IP Address on interface $vRtrIfIndex$ on local node $tmnxMcPeerSrcIpAddr$ conflicts with IP Address on node $tmnxMcPeerIpAddrForNotify$. |
Cause |
The IP address for a local subscriber interface conflicts with the IP address for a remote subscriber interface. |
Effect | N/A |
|
Recovery | Resolve IP address conflict. |
tmnxSrrpInstanceIdMismatch
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2009 |
Event name | tmnxSrrpInstanceIdMismatch |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.9 |
Default severity | warning |
Message format string | The SRRP Id from node $tmnxMcPeerIpAddrForNotify$ did not match srrp $tmnxSrrpOperID$ on local node $tmnxMcPeerSrcIpAddr$: interface $vRtrIfIndex$. |
Cause | The notification tmnxSrrpInstanceIdMismatch is generated when an SRRP instance has detected that at least one SAP it is protecting is associated with a different SRRP instance on the remote peer. |
Effect | One or more SAPs are not protected by SRRP. |
Recovery | Verify configuration on the local and remote end routers to ensure that all SAPs are associated with the same SRRP instance on both sides. |
tmnxSrrpOperDownInvalidMac
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2043 |
Event name | tmnxSrrpOperDownInvalidMac |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.39 |
Default severity | minor |
Message format string | tmnxSrrpOperDownInvalidMac notification from SRRP id $tmnxSrrpOperID$ on interface $vRtrIfIndex$. SRRP instance is not allowed to be operational. |
Cause | tmnxSrrpOperDownInvalidMac is generated when the operational virtual MAC of an SRRP instance conflicts with the MAC of the parent interface. |
Effect | The SRRP virtual router instance is not allowed to become operationally 'up'. |
Recovery | There is no recovery required for this notification. |
tmnxSrrpOperDownInvalidMacClear
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2044 |
Event name | tmnxSrrpOperDownInvalidMacClear |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.40 |
Default severity | minor |
Message format string | tmnxSrrpOperDownInvalidMac notification from SRRP id $tmnxSrrpOperID$ on interface $vRtrIfIndex$ has been cleared. |
Cause | The tmnxSrrpOperDownInvalidMacClear is generated when a previously occurring tmnxSrrpOperDownInvalidMac notification has been cleared. Operational virtual MAC of an IPv4 SRRP instance does not have any conflict with the MAC of the parent interface. |
Effect | The SRRP virtual router instance is allowed to become operationally 'up'. |
Recovery | There is no recovery required for this notification." |
tmnxSrrpPrivRetailMismatch
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2045 |
Event name | tmnxSrrpPrivRetailMismatch |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.41 |
Default severity | warning |
Message format string | SRRP id $tmnxSrrpOperID$: mismatch in private retail configuration for service $tmnxMcNotifyServiceId$ $tmnxMcNotifyTruthValue$ detected/resolved |
Cause | The notification tmnxSrrpPrivRetailMismatch is generated with a value of 'true' for tmnxMcNotifyServiceId when the list of private retail services received through SRRP-MCS synchronization does not match the list that is locally configured on this system, or with a value of 'false' when a matching list of private retail services is received subsequently. |
Effect | Downstream traffic received on the standby system for a subscriber associated with a misconfigured retail service can not be forwarded. |
Recovery | Restore consistency in the configuration of the private retail services on both systems. |
tmnxSrrpRedIfMismatch
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2012 |
Event name | tmnxSrrpRedIfMismatch |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.12 |
Default severity | warning |
Message format string | SRRP ID $tmnxSrrpOperID$: Redundant interface $tmnxMcRemoteRedIfNameForNotify$ on peer $tmnxMcPeerIpAddrForNotify$ / interface $tmnxMcRemoteGrpIfNameForNotify$ does not match local $tmnxMcPeerSrcIpAddr$ / interface $vRtrIfIndex$. |
Cause |
The local and remote redundant interfaces are not properly paired. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxSrrpSapMismatch
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2010 |
Event name | tmnxSrrpSapMismatch |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.10 |
Default severity | warning |
Message format string | SRRP id $tmnxSrrpOperID$: SAPs on peer interface $tmnxMcRemoteGrpIfNameForNotify$ do not match those on local interface $vRtrIfIndex$. |
Cause |
The SAPs SRRP is backing up on the local interface do not match with the ones on the remote interface. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxSrrpSapTagMismatch
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2011 |
Event name | tmnxSrrpSapTagMismatch |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.11 |
Default severity | warning |
Message format string | SRRP ID $tmnxSrrpOperID$: SAP encap of $sapEncapValue$ on peer interface $tmnxMcRemoteGrpIfNameForNotify$ has MCS tag $tmnxMcRemoteSyncTag$, which differs from local tag $tmnxMcPeerSyncPortEncapSyncTag$ on interface $vRtrIfIndex$. |
Cause |
The tag for a local SAP does not match those of the remote SAP. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxSrrpSubnetMismatch
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2007 |
Event name | tmnxSrrpSubnetMismatch |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.7 |
Default severity | warning |
Message format string | IP Address list from node $tmnxMcPeerIpAddrForNotify$ did not match the address list configured for SRRP instance $tmnxSrrpOperID$ on local node $tmnxMcPeerSrcIpAddr$: interface $vRtrIfIndex$. |
Cause |
The IP address list received through SRRP-MCS synchronization received from the current master does not match the local configured IP address list. |
Effect | This is an edge triggered notification. A second trap will not be generated for a packet from the same master until this event has been cleared. |
Recovery | No recovery is necessary. |
tmnxSrrpSubnetMismatchCleared
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2008 |
Event name | tmnxSrrpSubnetMismatchCleared |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.8 |
Default severity | warning |
Message format string | IP Address list from node $tmnxMcPeerIpAddrForNotify$ matched the address list configured for SRRP instance $tmnxSrrpOperID$ on local node $tmnxMcPeerSrcIpAddr$: interface $vRtrIfIndex$. |
Cause |
The mismatch in the IP address list received through SRRP-MCS synchronization received from the current master is cleared. |
Effect | N/A |
|
Recovery | No recovery is necessary. |
tmnxSrrpSystemIpNotSet
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2015 |
Event name | tmnxSrrpSystemIpNotSet |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.15 |
Default severity | warning |
Message format string | SRRP sending out advertisement packets before the system IP address has been set. |
Cause | SRRP tried to send out advertisement packets but the system IP address is not set. |
Effect | SRRP sends out advertisement packets with a source address of 0.0.0.0. |
Recovery | No recovery is necessary. |
tmnxSrrpTrapNewMaster
|
Property name | Value |
|---|---|
Application name | MC_REDUNDANCY |
Event ID | 2023 |
Event name | tmnxSrrpTrapNewMaster |
SNMP notification prefix and OID | TIMETRA-MC-REDUNDANCY-MIB.tmnxMcRedundancyNotifications.23 |
Default severity | minor |
Message format string | SRRP instance $tmnxSrrpOperID$ on interface $vRtrIfIndex$ (primary address $tmnxMcPeerIpAddrForNotify$) changed state to master |
Cause | The sending multi-chassis SRRP instance has transitioned to 'Master' state. |
Effect | N/A |
|
Recovery | N/A |