This document is the SNMP MIB module to manage and provision the
multi-chassis redundancy for the Nokia SROS device.
Copyright 2006-2018 Nokia. All rights reserved. Reproduction of this
document is authorized on the condition that the foregoing copyright
notice is included.
This SNMP MIB module (Specification) embodies Nokia's proprietary
intellectual property. Nokia retains all title and ownership in the
Specification, including any revisions.
Nokia grants all interested parties a non-exclusive license to use and
distribute an unmodified copy of this Specification in connection with
management of Nokia products, and without fee, provided this copyright
notice and license appear on all copies.
This Specification is supplied 'as is', and Nokia makes no warranty,
either express or implied, as to the use, operation, condition, or
performance of the Specification.
The notification tmnxMcRedundancyPeerStateChanged is sent when the
connection to a specific peer is lost or established.
tmnxSrrpSapMismatch
.1.3.6.1.4.1.6527.3.1.3.40.0.10
The notification tmnxSrrpSapMismatch is generated when the SAPs SRRP
is backing up on the local interface do not match with the ones on the
remote interface.
tmnxSrrpSapTagMismatch
.1.3.6.1.4.1.6527.3.1.3.40.0.11
The notification tmnxSrrpSapTagMismatch is generated when the tag for
a local SAP do not match those of the remote SAP.
tmnxSrrpRedIfMismatch
.1.3.6.1.4.1.6527.3.1.3.40.0.12
The notification tmnxSrrpRedIfMismatch is generated when the local and
remote redundant interfaces are not properly paired.
tmnxSrrpDualMaster
.1.3.6.1.4.1.6527.3.1.3.40.0.13
The notification tmnxSrrpDualMaster is generated when both the local
and remote SRRP instances are in the master state.
tmnxMcLagInfoLagChanged
.1.3.6.1.4.1.6527.3.1.3.40.0.14
The notification tmnxMcLagInfoLagChanged is generated when entries in
tmnxMcLagInfoLagTable were changed.
tmnxSrrpSystemIpNotSet
.1.3.6.1.4.1.6527.3.1.3.40.0.15
The notification tmnxSrrpSystemIpNotSet is generated when SRRP tries
to send out advertisement packets but the system IP address has not
yet been set.
tmnxMcRingOperStateChanged
.1.3.6.1.4.1.6527.3.1.3.40.0.16
[CAUSE] The notification tmnxMcRingOperStateChanged is generated when
the operational state of a multi-chassis ring's 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. E.g. 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 SAP's of path-a
and path-b in operational state 'up'. configErr : if there is no peer
ring, the ring brings all SAP's on path-a and path-b in operational
state 'up'; if there is a peer ring, the ring brings all SAP's on
path-a and path-b in operational state 'down'. noPeer : the ring
brings all SAP's of path-a and path-b in operational state 'up'.
connected : the ring brings all SAP's of its own path in operational
state 'up' and all SAP's of the other path in operational state
'down'. broken : the ring brings all SAP's of path-a and path-b in
operational state 'up'. localBroken : this system brings all SAP's of
path-a and path-b in operational state 'down' unless they belong to
the excluded-path. conflict : the ring brings all SAP's of its own
path in operational state 'up' and all SAP's of the other path in
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.
tmnxMcRingInbCtrlOperStateChgd
.1.3.6.1.4.1.6527.3.1.3.40.0.17
[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
.1.3.6.1.4.1.6527.3.1.3.40.0.18
[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; only 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.
tmnxMcSyncClockSkewRaised
.1.3.6.1.4.1.6527.3.1.3.40.0.19
The notification tmnxMcSyncClockSkewRaised is generated when the MCS
peer system clock time is greater than 60 seconds different than the
local system clock.
tmnxMcRedundancyMismatchDetected
.1.3.6.1.4.1.6527.3.1.3.40.0.2
The notification tmnxMcRedundancyMismatchDetected is sent when a
configuration mismatch is detected.
tmnxMcSyncClockSkewCleared
.1.3.6.1.4.1.6527.3.1.3.40.0.20
The notification tmnxMcSyncClockSkewCleared is generated when 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.
tmnxSrrpDuplicateSubIfAddress
.1.3.6.1.4.1.6527.3.1.3.40.0.21
The notification tmnxSrrpDuplicateSubIfAddress is generated when the
IP address for a local subscriber interface conflicts with the IP
address for a remote subscriber interface.
tmnxMcPeerRingsOperStateChanged
.1.3.6.1.4.1.6527.3.1.3.40.0.22
[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.
tmnxSrrpTrapNewMaster
.1.3.6.1.4.1.6527.3.1.3.40.0.23
The tmnxSrrpTrapNewMaster trap indicates that the sending
multi-chassis SRRP instance has transitioned to 'Master' state.
tmnxSrrpBecameBackup
.1.3.6.1.4.1.6527.3.1.3.40.0.24
The tmnxSrrpBecameBackup trap is generated when the sending
multi-chassis SRRP instance has transitioned to 'Backup' state.
tmnxSrrpBfdIntfSessStateChgd
.1.3.6.1.4.1.6527.3.1.3.40.0.25
The notification tmnxSrrpBfdIntfSessStateChgd is generated when the
operational state of BFD session of the SRRP instance changes.
tmnxMcPeerEPBfdSessionOpen
.1.3.6.1.4.1.6527.3.1.3.40.0.26
The tmnxMcPeerEPBfdSessionOpen notification is generated when the
multi-chassis endpoint is attempting to open BFD session to the
multi-chassis endpoint peer.
tmnxMcPeerEPBfdSessionClose
.1.3.6.1.4.1.6527.3.1.3.40.0.27
The tmnxMcPeerEPBfdSessionClose notification is generated when the
multi-chassis endpoint is closing BFD session to the multi-chassis
endpoint peer.
tmnxMcPeerEPBfdSessionUp
.1.3.6.1.4.1.6527.3.1.3.40.0.28
The tmnxMcPeerEPBfdSessionUp notification is generated when
operational state of the BFD session between the multi-chassis
endpoint and its peer is changed to 'up'.
tmnxMcPeerEPBfdSessionDown
.1.3.6.1.4.1.6527.3.1.3.40.0.29
The tmnxMcPeerEPBfdSessionDown notification is generated when
operational state of the BFD session between the multi-chassis
endpoint and its peer is changed to 'down'.
tmnxMcRedundancyMismatchResolved
.1.3.6.1.4.1.6527.3.1.3.40.0.3
The notification tmnxMcRedundancyMismatchResolved is sent when all
configuration mismatches are resolved.
tmnxMcPeerEPOperDown
.1.3.6.1.4.1.6527.3.1.3.40.0.30
The tmnxMcPeerEPOperDown notification is generated when the
multi-chassis endpoint detects timeout communicating with the
multi-chassis endpoint peer.
tmnxMcPeerEPOperUp
.1.3.6.1.4.1.6527.3.1.3.40.0.31
The tmnxMcPeerEPOperUp notification is generated when the
multi-chassis endpoint clears timeout condition in communicating with
the multi-chassis endpoint peer.
tmnxMCEPSessionPsvModeEnabled
.1.3.6.1.4.1.6527.3.1.3.40.0.32
The notification tmnxMCEPSessionPsvModeEnabled is generated when
passive-mode for the session between the multi-chassis endpoint and
its peer is 'enabled' from either local or peer endpoint.
tmnxMCEPSessionPsvModeDisabled
.1.3.6.1.4.1.6527.3.1.3.40.0.33
The notification tmnxMCEPSessionPsvModeDisabled is generated when
passive-mode for the session between the multi-chassis endpoint and
its peer is 'disabled' from both local and peer.
tMcPeerIPsecTnlGrpMasterStateChg
.1.3.6.1.4.1.6527.3.1.3.40.0.34
[CAUSE] The notification tMcPeerIPsecTnlGrpMasterStateChg is generated
whenever mastership election state of a tunnel-group changes.
[EFFECT] This notification 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
.1.3.6.1.4.1.6527.3.1.3.40.0.35
[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.
tmnxMcOmcrStatFailedChanged
.1.3.6.1.4.1.6527.3.1.3.40.0.37
[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.
tmnxMcOmcrClientNumEntriesHigh
.1.3.6.1.4.1.6527.3.1.3.40.0.38
[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
786432. 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
setup 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.
tmnxSrrpOperDownInvalidMac
.1.3.6.1.4.1.6527.3.1.3.40.0.39
[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.
tmnxMcPeerSyncStatusChanged
.1.3.6.1.4.1.6527.3.1.3.40.0.4
The notification tmnxMcPeerSyncStatusChanged is generated when the
status of the synchronization with the multi-chassis peer changes.
tmnxSrrpOperDownInvalidMacClear
.1.3.6.1.4.1.6527.3.1.3.40.0.40
[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
.1.3.6.1.4.1.6527.3.1.3.40.0.41
[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.
tmnxMcSyncClientAlarmRaised
.1.3.6.1.4.1.6527.3.1.3.40.0.5
The notification tmnxMcSyncClientAlarmRaised is generated when a
multi-chassis sync client has at least one locally deleted entry in
the database.
tmnxMcSyncClientAlarmCleared
.1.3.6.1.4.1.6527.3.1.3.40.0.6
The notification tmnxMcSyncClientAlarmCleared is generated when a
multi-chassis sync client has no locally deleted entries in the
database.
tmnxSrrpSubnetMismatch
.1.3.6.1.4.1.6527.3.1.3.40.0.7
The notification tmnxSrrpSubnetMismatch is generated when the IP
address list received through SRRP-MCS synchronization received from
the current master does not match the local configured IP address
list.
This is an edge triggered notification. A second notification will not
be generated for a packet from the same master until this event has
been cleared.
tmnxSrrpSubnetMismatchCleared
.1.3.6.1.4.1.6527.3.1.3.40.0.8
The notification tmnxSrrpSubnetMismatchCleared is generated when the
mismatch in the IP address list received through SRRP-MCS
synchronization received from the current master is cleared.
tmnxSrrpInstanceIdMismatch
.1.3.6.1.4.1.6527.3.1.3.40.0.9
[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.