TN-MC-REDUNDANCY-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TN-MC-REDUNDANCY-MIB

Organization: Nokia

Last Updated: 2012-09-01

Category: Nokia Carrier Ethernet, VRRP and Redundancy

Description: Covers multi-chassis redundancy group configuration and failover state for Nokia carrier Ethernet equipment.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is TN-MC-REDUNDANCY-MIB?

TN-MC-REDUNDANCY-MIB, despite its 'TN' prefix, is a Nokia enterprise MIB (per its module description, covering the Nokia 7x50 SR system) for managing multi-chassis redundancy peer relationships used in dual-homed link-aggregation deployments. It exposes tnMcPeerTable with peer IP address, authentication key, source IP binding, and both administrative and operational states for each redundancy peer. It is used to monitor software/hardware redundancy status: a mismatch between tnMcPeerAdminState and the peer's actual operational source-IP binding (tnMcPeerSrcIpOperType/Addr) reveals a multi-chassis redundancy relationship that's configured but not functioning, putting the network at risk of a split-brain condition if the active chassis fails. It complements standard link-aggregation (LACP) concepts and sits within the broader TIMETRA/Nokia SROS enterprise MIB tree. It is deployed on Nokia SROS routers (7750 SR, 7450 ESS) configured for multi-chassis link aggregation to provide chassis-level redundancy, and engineers consult the TN-MC-REDUNDANCY-MIB MIB definition when configuring peer relationships.

IPNetwork Monitor allows you to monitor SNMP objects defined in TN-MC-REDUNDANCY-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Nokia 1830 PSS (Photonic Service Switch) optical transport platform

Monitoring Examples

An admin would poll tnMcPeerTable and compare tnMcPeerAdminState against tnMcPeerSrcIpOperAddr/Type for each peer to confirm the redundancy relationship is both configured and operationally bound. A peer whose admin state is up but whose operational source IP fails to bind would indicate a broken multi-chassis redundancy link, risking a split-brain scenario if a failover were triggered. tnMcPeerAuthKey would be checked to confirm authentication is correctly configured between peers.

What Can Be Monitored

  • MC redundancy peer IP address
  • peer admin state
  • authentication key configuration
  • source IP operational address/type
  • peer row status
Imported Objects

From INET-ADDRESS-MIB

InetAddress
InetAddressPrefixLength
InetAddressType

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
DisplayString
MacAddress
RowStatus
TEXTUAL-CONVENTION
TimeInterval
TimeStamp
TruthValue

From TN-LAG-MIB

LAGInterfaceNumber

From TN-SAP-MIB

tnSapEncapValueOBJECT-TYPE
tnSapPortIdOBJECT-TYPE

From TN-SERV-MIB

tnSvcIdOBJECT-TYPE

From TN-TC-MIB

TItemDescription
TNamedItem
TNamedItemOrEmpty
TmnxAdminState
TmnxEnabledDisabled
TmnxEncapVal
TmnxOperState
TmnxPortID
TmnxServId
TmnxVRtrID

From TROPIC-GLOBAL-REG

tnSRMIBModulesOBJECT-IDENTITY
tnSRNotifyPrefixOBJECT-IDENTITY
tnSRObjsOBJECT-IDENTITY

From TROPIC-SYSTEM-MIB

tnSysSwitchIdOBJECT-TYPE

How to Use in IPNetwork Monitor

Example using tnMcPeerSyncNumEntries OID:

Select a Nokia SROS routers (7750 SR, 7450 ESS) configured for multi-chassis redundancy (peer admin/oper status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type tnMcPeerSyncNumEntries into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The value of tnMcPeerSyncNumEntries indicates the total number of entries in the MCS database per multi-chassis peer. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Manages Nokia carrier Ethernet multi-chassis redundancy group configuration and failover state.

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. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download TN-MC-REDUNDANCY-MIB