TN-MC-REDUNDANCY-MIB :: tnMcPeerSyncOperFlags

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TN-MC-REDUNDANCY-MIB › tnMcPeerSyncOperFlags

tnMcPeerSyncOperFlags

Module: TN-MC-REDUNDANCY-MIB

OID (symbolic): TN-MC-REDUNDANCY-MIB::tnMcPeerSyncOperFlags

OID (numeric): 1.3.6.1.4.1.7483.6.1.2.40.1.2.1.8

Node type: OBJECT-TYPE

Type: Bits

Access: read-only

Description: The value of tnMcPeerSyncOperFlags indicates the reason that the synchronization protocol with the multi-chassis peer is down.

syncAdminDown(0) Synchronization is administratively down. No recovery needed.

peerAdminDown(1) The peering is administratively down. No recovery needed.

connectionDown(2) There is a problem with the connection to the multi-chassis peer. The connection will be automatically repaired. No recovery needed

internalError(3) There has been an irrecoverable internal error. The synchronization protocol cannot come up again without user intervention. The user must set the tnMcPeerSyncAdminState to 'outOfService', then 'inService'.

mcsVersionMismatch(4) There is a mismatch between the versions of the multi-chassis sync protocol running on each peer.

platformMismatch(5) There is a mismatch between the platforms of each peer the multi-chassis sync protocol is running on.

appVersionMismatch(6) There is a mismatch between the versions of applications attempting to use the multi-chassis sync protocol on the two peers.

appSupportMismatch(7) There is a mismatch between the applications supported by the multi-chassis sync protocol on each peer.

What is tnMcPeerSyncOperFlags?

A set of bit flags explaining why the synchronization protocol with this peer is down, e.g. syncAdminDown, peerAdminDown, connectionDown, internalError, or a version/platform/app mismatch between the two peers. internalError specifically requires the admin to cycle tnMcPeerSyncAdminState through outOfService then inService to recover.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.7483.6.1.2.40.1.2.1.8
snmpwalk -v2c -c public <target> TN-MC-REDUNDANCY-MIB::tnMcPeerSyncOperFlags

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.7483.6.1.2.40.1.2.1.8.1
snmpget -v2c -c public <target> TN-MC-REDUNDANCY-MIB::tnMcPeerSyncOperFlags.1

Start monitoring Nokia SROS routers (7750 SR, 7450 ESS) configured for multi-chassis redundancy (peer admin/oper status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TN-MC-REDUNDANCY-MIB::tnMcPeerSyncOperFlags OID value, configure state conditions and alerts, and monitor any Nokia SROS routers (7750 SR, 7450 ESS) configured for multi-chassis redundancy (peer admin/oper status) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.7483tropicTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.6tnProductsTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.6.1tnSRMIBTROPIC-GLOBAL-REG
1.3.6.1.4.1.7483.6.1.2tnSRObjsTROPIC-GLOBAL-REG
Numeric OIDNameModule
1.3.6.1.4.1.7483.6.1.2.40tnMcRedundancyTN-MC-REDUNDANCY-MIB
1.3.6.1.4.1.7483.6.1.2.40.1tnMcRedundancyObjsTN-MC-REDUNDANCY-MIB
1.3.6.1.4.1.7483.6.1.2.40.1.2tnMcPeerSyncTableTN-MC-REDUNDANCY-MIB
1.3.6.1.4.1.7483.6.1.2.40.1.2.1tnMcPeerSyncEntryTN-MC-REDUNDANCY-MIB
1.3.6.1.4.1.7483.6.1.2.40.1.2.1.8tnMcPeerSyncOperFlagsTN-MC-REDUNDANCY-MIB