TIMETRA-MC-REDUNDANCY-MIB: View SNMP OID List / Download MIB

This document is the SNMP MIB module to manage and provision the multi-chassis redundancy for the Alcatel-Lucent SROS device. Copyright 2006-2012 Alcatel-Lucent. 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 Alcatel-Lucent's proprietary intellectual property. Alcatel-Lucent retains all title and ownership in the Specification, including any revisions. Alcatel-Lucent grants all interested parties a non-exclusive license to use and distribute an unmodified copy of this Specification in connection with management of Alcatel-Lucent products, and without fee, provided this copyright notice and license appear on all copies. This Specification is supplied 'as is', and Alcatel-Lucent makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.

The compliance statement for management of multi-chassis redundancy on version 5.0 of the Alcatel-Lucent SROS series systems.

The compliance statement for management of multi-chassis redundancy on version 5.0 of the Alcatel-Lucent 7450 series systems.

The compliance statement for management of multi-chassis redundancy on version 5.0 of the Alcatel-Lucent 7710 series systems.

The compliance statement for management of multi-chassis redundancy on version 6.0 of the Alcatel-Lucent SROS series systems.

The compliance statement for management of multi-chassis redundancy on version 6.0 of the Alcatel-Lucent 7450 series systems.

The compliance statement for management of multi-chassis redundancy on version 6.0 of the Alcatel-Lucent 7710 series systems.

The compliance statement for management of multi-chassis redundancy on version 6.1 of the Alcatel-Lucent SROS series systems.

The compliance statement for management of multi-chassis redundancy on version 6.1 of the Alcatel-Lucent 7710 series systems.

The compliance statement for management of multi-chassis redundancy on version 7.0 of the Alcatel-Lucent 7450 series systems.

The compliance statement for management of multi-chassis redundancy on version 7.0 of the Alcatel-Lucent SROS series systems.

The compliance statement for management of multi-chassis redundancy on version 7.0 of the Alcatel-Lucent 7710 series systems.

The compliance statement for management of multi-chassis redundancy on version 8.0 of the Alcatel-Lucent 7450 series systems.

The compliance statement for management of multi-chassis redundancy on version 8.0 of the Alcatel-Lucent SROS series systems.

The compliance statement for management of multi-chassis redundancy on version 7.0 of the Alcatel-Lucent 7710 series systems.

The compliance statement for management of multi-chassis redundancy on version 9.0 of the Alcatel-Lucent 7450 series systems.

The compliance statement for management of multi-chassis redundancy on version 9.0 of the Alcatel-Lucent SROS series systems.

The compliance statement for management of multi-chassis redundancy on version 7.0 of the Alcatel-Lucent 7710 series systems.

The compliance statement for management of multi-chassis redundancy on version 9.0 of the Alcatel-Lucent 7450 series systems.

The compliance statement for management of multi-chassis redundancy on version 9.0 of the Alcatel-Lucent SROS series systems.

The compliance statement for management of multi-chassis redundancy on version 7.0 of the Alcatel-Lucent 7710 series systems.

The group of objects supporting multi-chassis redundancy on version 5.0 of the Alcatel-Lucent SROS series systems.

The group of objects supporting subscriber router redundancy on version 5.0 of the Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis notifications on Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis ring on the Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis peer synchronization on the Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis peer synchronization of DHCP Server information on the Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis redundancy on version 6.0 of the Alcatel-Lucdent SROS series systems.

The group of objects supporting SRRP BFD on version 6.1 of the Alcatel-Lucent SROS series systems.

The group of notification objects supporting multi-chassis redundacny SRRP on Alcatel-Lucent SROS 6.1 series systems.

The group of notification objects supporting multi-chassis redundacny L3 Ring on Alcatel-Lucent SROS 7.0 series systems.

The group of notification objects supporting multi-chassis redundacny peer group on Alcatel-Lucent SROS 7.0 series systems.

The group of objects supporting management of multi-chassis endpoint notification objects on Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis peer synchronization of subscriber host tracking information on the Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis Lag specific provider backbone feature objects on the Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis redundancy specific multi-home feature objects on the Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis redundancy specific TLS SAP objects on the Alcatel-Lucent SROS series systems.

The group of objects supporting subscriber router redundancy on on Alcatel-Lucent SROS series systems 8.0 release.

The group of objects supporting subscriber router redundancy on on Alcatel-Lucent SROS series systems 8.0 release.

The group of objects supporting multi-chassis redundancy on version 9.0 of the Alcatel-Lucent SROS series systems.

The group of objects supporting multi-chassis redundancy on version 10.0 of the Alcatel-Lucent SROS series systems.

The group of notification objects supporting multi-chassis redundacny SRRP on Alcatel-Lucent SROS 11.0 series systems.

The group of objects supporting multi-chassis redundancy on version 5.0 of the Alcatel-Lucent SROS series systems.

The group of notifications supporting multi-chassis ring on version 6.0 of the Alcatel-Lucent SROS series systems.

The group of notifications supporting multi-chassis redundancy on the Alcatel-Lucent SROS series systems.

The group of notifications supporting multi-chassis redundancy SRRP on the Alcatel-Lucent SROS series systems.

The group of notifications supporting multi-chassis endpoint on the Alcatel-Lucent SROS series systems.

The group of notifications supporting multi-chassis redundancy features the Alcatel-Lucent SROS 11.0 series systems.

The group of objects supporting multi-chassis redundancy on version 4.0 of the Alcatel-Lucent mobile-gateway system.

The tmnxMcPeerTable has an entry for each multi-chassis peer configured on this system.

Each row entry represents a particular multi-chassis peer. Entries are create/deleted by the user.

The value of tmnxMcPeerIpType indicates the address type of tmnxMcPeerIpAddr.

The value of tmnxMcPeerIpAddr indicates the address of the multi-chassis peer. Its type is specified by tmnxMcPeerIpType. It must be a valid unicast address.

The value of tmnxMcPeerRowStatus is used for creation/deletion of multi-chassis peers.

The value of tmnxMcPeerDescription specifies the textual description of this multi-chassis peer.

The value of tmnxMcPeerAuthKey specifies the authentication key used between this node and the multi-chassis peer. The authentication key can be any combination of letters or numbers. This object will always return an empty string on a read.

The value of tmnxMcPeerSrcIpType specifies the address type of tmnxMcPeerSrcIpAddr.

The value of tmnxMcPeerSrcIpAddr specifies the source address used to communicate with the multi-chassis peer. Its type is specified by tmnxMcPeerSrcIpType. It must be a valid unicast address.

The value of tmnxMcPeerAdminState specifies the administrative state of this multi-chassis peer.

The value of tmnxMcPeerSrcIpOperType indicates the operational source address type of tmnxMcPeerSrcIpOperAddr, the multi-chassis peer source IP address.

The value of tmnxMcPeerSrcIpOperAddr indicates the operational source address in use to communicate with the multi-chassis peer. Its type is specified by tmnxMcPeerSrcIpOperType.

The value of tmnxMcPeerRingsOperState indicates the operational state of this multi-chassis peer with respect to multi-chassis ring operation. If there are no entries in the tmnxMcRingTable associated with this peer, the value of tmnxMcPeerRingsOperState is 'unknown'.

The value of tmnxMcPeerName specifies the name of this multi-chassis peer.

The tmnxMcPeerSyncTable has an entry for each multi-chassis peer synchronization protocol.

Each row entry represents a particular multi-chassis peer synchronization protocol. Entries are create/deleted by the user.

The value of tmnxMcPeerSyncRowStatus is used for creation and deletion of a synchronization protocol with a multi-chassis peer.

The value of tmnxMcPeerSyncIgmp specifies whether IGMP protocol information should be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncIgmpSnooping specifies whether IGMP-snooping information should be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncSubMgmt specifies whether subscriber management IPoE information should be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncSrrp specifies whether SRRP information should be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncAdminState specifies the administrative status of the synchronization protocol with the multi-chassis peer.

The value of tmnxMcPeerSyncOperState indicates the operational status of the synchronization protocol with the multi-chassis peer.

The value of tmnxMcPeerSyncOperFlags 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 tmnxMcPeerSyncAdminState 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. Bits: 'connectionDown': 2, 'syncAdminDown': 0, 'platformMismatch': 5, 'internalError': 3, 'peerAdminDown': 1, 'appVersionMismatch': 6, 'mcsVersionMismatch': 4, 'appSupportMismatch': 7.

The value of tmnxMcPeerSyncStatus indicates the status of the synchronization process. Enumeration: 'outOfSync': 3, 'inSync': 1, 'syncInProgress': 2.

The value of tmnxMcPeerSyncLastSyncTime indicates the sysUpTime at the time the last synchronization with the peer was successful.

The value of tmnxMcPeerSyncNumEntries indicates the total number of entries in the MCS database per multi-chassis peer.

The value of tmnxMcPeerSyncLclDeletedEntries indicates the number of locally deleted entries in the MCS database per multi-chassis peer. Locally deleted entries are entries that are not being used by the local MCS client application.

The value of tmnxMcPeerSyncAlarmedEntries indicates the number of alarmed entries in the MCS database per multi-chassis peer. Entries with an alarm are entries that are not being used by the local client application due to resource constraints.

The value of tmnxMcPeerSyncRemNumEntries indicates the total number of entries in the MCS database of the multi-chassis peer.

The value of tmnxMcPeerSyncRemLclDelEntries indicates the number of locally deleted entries in the MCS database of the multi-chassis peer. Locally deleted entries are entries that are not being used by the remote MCS client application.

The value of tmnxMcPeerSyncRemAlarmedEntries indicates the number of alarmed entries in the MCS database of the multi-chassis peer. Entries with an alarm are entries that are not being used by the remote client application due to resource constraints.

The value of tmnxMcPeerSyncMcRing specifies whether mc-ring information should be synchronized with the multi-chassis peer. Setting this object to 'true(1)' enables the synchronization.

The value of tmnxMcPeerSyncMldSnooping specifies whether MLD-snooping information should be synchronized with the multi-chassis peer. Setting this object to 'true(1)' enables the synchronization.

The value of tmnxMcPeerSyncDhcpServer specifies whether DHCP Server information should be synchronized with the multi-chassis peer. Setting this object to 'true(1)' enables the synchronization.

The value of tmnxMcPeerSyncSubHostTrk specifies whether subscriber host tracking information should be synchronized with the multi-chassis peer. Setting this object to 'true(1)' enables the synchronization.

The value of tmnxMcPeerSyncSubMgmtPppoe specifies whether subscriber management PPPoE information should be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncIpsec specifies whether ipsec information is synchronized on this multi-chassis peer.

The value of tmnxMcPeerSyncMobile specifies whether the mobile management information should be synchronized with the multi-chassis peer.

The tmnxMcPeerSyncPortTable has an entry for each port that is being synchronized with a multi-chassis peer.

Each row entry represents a port to be synchronized. Entries are created/deleted by the user.

The value of tmnxMcPeerSyncPortId indicates the port to be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncPortRowStatus is used for creation and deletion of ports to be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncPortSyncTag specifies a synchronization tag to be used while synchronizing this port with the multi-chassis peer.

The tmnxMcPeerSyncPortEncapRangeTable has an entry for each port encapsulation value range to be synchronized with a multi-chassis peer.

Each row entry represents a range of encapsulation values on a port to be synchronized with a multi-chassis peer. Entries are created/deleted by the user.

The value of tmnxMcPeerSyncPortEncapType indicates the encapsulation type used to interpret tmnxMcPeerSyncPortEncapMin and tmnxMcPeerSyncPortEncapMax. Enumeration: 'qinq': 2, 'dot1q': 1.

The value of tmnxMcPeerSyncPortEncapMin indicates the minimum encapsulation value on the port indicated by tmnxMcPeerSyncPortId that will be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncPortEncapMax indicates the maximum encapsulation value on the port indicated by tmnxMcPeerSyncPortId that will be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncPortEncapRowStatus is used for creation and deletion of encapsulation value ranges over a specific port to be synchronized with the multi-chassis peer.

The value of tmnxMcPeerSyncPortEncapSyncTag specifies a synchronization tag to be used while synchronizing this encapsulation value range with the multi-chassis peer. This object MUST be specified at row creation time.

The value of tmnxMcLagConfigTableLastChanged indicates the sysUpTime at the time of the last modification of an entry in the tmnxMcLagConfigTable. If no changes were made to the table since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcLagConfigTable has an entry for each multi-chassis LAG configuration for the indicated peer.

Each row entry represents configuration data for a multi-chassis LAG configuration with a given peer. Rows are created or removed automatically by the system, each time a row is created or deleted in the tmnxMcPeerTable.

The value of tmnxMcLagConfigPeerLastChanged indicates the sysUpTime at the time of the last modification of this entry. If no changes were made to the entry since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcLagConfigPeerAdminstate specifies the administrative state of the multi-chassis lag with the indicated peer.

The value of tmnxMcLagConfigKeepALiveIvl specifies the mc-lag keepalive timer value in units of 0.1 sec. This defines the interval at which keep-alive messages are exchanged between two systems participating in mc-lag. These keep-alive messages are used to determine remote-node failure.

The value of tmnxMcLagConfigHoldOnNgbrFailure specifies how many tmnxMcLagConfigKeepALiveIvl intervals the standby node will wait for packets from the active node before assuming a redundant-neighbor node failure. This delay in switch-over operation is required to accommodate for different factors influencing node failure detection rate, such as IGP convergence, or HA switch-over times and to prevent that the standby node takes actions prematurely.

The value of tmnxMcLagConfigOperState indicates the operational status of this multi-chassis LAG peer. Enumeration: 'outOfService': 1, 'inService': 0.

The value of tmnxMcLagConfigPeerLastStateChge indicates the sysUpTime at the time of the last operational state change for this multi-chassis LAG peer. If no changes were made since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcLagConfigLagTableLastChanged indicates the sysUpTime at the time of the last modification of an entry in the tmnxMcLagConfigLagTable. If no changes were made to the table since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcLagConfigLagTable has an entry for each lag that participates in a multi-chassis configuration for the indicated peer.

Each row entry represents configuration data for a lag that participates in a multi-chassis configuration with a given peer. Rows can be created and deleted by the operator.

The value of tmnxMcLagConfigLagId identifies the Link Aggregation Group on this system that is to form a mc-lag configuration with the indicated peer.

The value of tmnxMcLagConfigLagLastChanged indicates the sysUpTime at the time of the last modification of this entry. If no changes were made to the entry since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcLagConfigLagRowStatus specifies the row status of this row.

The value of tmnxMcLagConfigLaglacpKey specifies a 16bit key that needs to be configured in the same manner on both sides of the mc-lag in order for the mc-lag to come up. The value of tmnxMcLagConfigLaglacpKey must be 0 when the value of tLagStandbySignaling of the corresponding LAG is 'powerOff (2)'. The value of tmnxMcLagConfigLaglacpKey cannot be 0 when the value of tLagStandbySignaling of the corresponding LAG is 'lacp (1)'.

The value of tmnxMcLagConfigLagSystemId specifies the system-id to be used in the context of mc-lag operation. The partner system will consider all ports using the same system-id, system priority and lacp-key as part of the same lag. In order to achieve this in mc-lag operation, both systems have to be configured with the same values. As long as the system does not have the connection with its redundant peer, it will use the locally defined value (chassis MAC address). After detecting a redundant node failure, the previously active system will keep on using the system-id configured here, while the standby system will switch to its locally defined value. The value of this object must be all zeroes when the value of tLagStandbySignaling of the corresponding LAG is 'powerOff (2)'. The value of this object cannot be all zeroes when the value of tLagStandbySignaling of the corresponding LAG is 'lacp (1)'.

The value of tmnxMcLagConfigLagSystemPriority specifies the system priority to be used in the context of mc-lag. The partner system will consider all ports using the same system-id, system priority and lacp-key as part of the same lag. In order to achieve this in mc-lag operation, both systems have to be configured with the same values. A low numeric value specifies a high system priority. The value of this object must be 0 when the value of tLagStandbySignaling of the corresponding LAG is 'powerOff (2)'. The value of this object cannot be 0 when the value of tLagStandbySignaling of the corresponding LAG is 'lacp (1)'.

The value of tmnxMcLagConfigLagRemoteLagId specifies the Lag ID on the remote system. If not specified, the value of this object will be set to the value of tmnxMcLagConfigLagId.

The value of tmnxMcLagConfigLagSrcBMacLSB specifies the value of last 16-bits of the MAC address used for all the traffic ingressing the MC-Lag links. The value '4294967295' indicates use of the lacp-key as source backbone MAC address LSB.

The value of tmnxMcLagConfigLagOperSrcBMacLSB indicates the operational value of last 16-bits of the MAC address used for all the traffic ingressing the MC-Lag links.

The tmnxSrrpOperTable has an entry for each Subscriber Router Redundancy Protocol instance configured on this system.

Each row entry represents a particular SRRP instance tied to a service group interface. Entries are created/deleted by the user.

The value of tmnxSrrpOperID indicates the unique SRRP ID of this SRRP instance.

The value of tmnxSrrpOperRowStatus is used for creation/deletion of SRRP instances.

The value of tmnxSrrpOperDescription specifies the textual description of this SRRP instance.

The value of tmnxSrrpOperGwMac specifies the MAC address used to override the default SRRP gateway MAC.

The value of tmnxSrrpOperGwOperMac indicates the operational MAC address used by this SRRP instance. When tmnxSrrpOperGwMac is set to the default, this address is calculated as the base VRRP MAC address with the last octet overridden by the lower 8 bits of tmnxSrrpOperID.

The value of tmnxSrrpOperPriority specifies the priority of this SRRP instance advertised to the neighbor router. It is compared to the neighbor router's priority, and the SRRP instance with the higher priority enters the master state and the one with the lower priority enters the backup state. If the priorities are identical, the system IP addresses are used as a tie-breaker.

The value of tmnxSrrpOperInUsePriority indicates the the current in-use priority of this SRRP instance. This value will be different from the base priority set by tmnxSrrpOperPriority when it is changed by a VRRP event.

The value of tmnxSrrpOperMasterPriority indicates the the current priority of the Master for this SRRP instance.

The value of tmnxSrrpOperKeepAliveInterval specifies the interval between SRRP advertisement messages send when operating in the master state.

The value of tmnxSrrpOperMsgPathSapPortId specifies the port ID of the SAP on which this SRRP instance will send its advertisements. This object MUST be set along with tmnxSrrpOperMsgPathSapEncapVal in the same SNMP PDU.

The value of tmnxSrrpOperMsgPathSapEncapVal specifies the encapsulation value of the SAP on which this SRRP instance will send its advertisements. This object MUST be set along with tmnxSrrpOperMsgPathSapPortId in the same SNMP PDU.

The value of tmnxSrrpOperAdminState specifies the administrative state of this SRRP instance.

The value of tmnxSrrpOperState indicates the operational state of this SRRP instance. disabled(0) The SRRP instance is administratively down. initialize(1) The SRRP instance is operationally down or is starting to discover its neighbor. backupRouting(2) The SRRP instance is in backup mode, but it is still forwarding traffic. The MAC address used to forward traffic is the native MAC address of the interface SRRP is running on. backupShunt(3) The SRRP instance is in backup mode. Any traffic it receives will be forwarded to the spoke-sdp on the redundant interface tied to the group interface this instance is running on. pendingRouting(4)The SRRP instance is in backup mode. A transient state when a master/pending-master is preempted and before it is going to backupRouting state. In this state, traffic destined to the SRRP gateway mac address received from a group interface will still be accepted and forwarded. pendingShunt(5) The SRRP instance is in backup mode. A transient state when a master/pending-master is preempted and before it is going to backupShunt state. In this state, traffic destined to the SRRP gateway mac address received from a group interface will still be accepted and forwarded. pendingMaster(6) The SRRP instance is in master mode. All traffic is forwarded using the native MAC address of the interface SRRP is running on. master(7) The SRRP instance is in master mode. All traffic is forwarded using the gateway MAC address of this SRRP instance. Enumeration: 'pendingShunt': 5, 'backupRouting': 2, 'pendingMaster': 6, 'disabled': 0, 'master': 7, 'initialize': 1, 'backupShunt': 3, 'pendingRouting': 4.

The value of tmnxSrrpOperMasterSince indicates the sysUpTime when the last master was chosen. When this instance is master, it indicates when it first became master. When it is backup, it indicates when the first SRRP advertisement message from the current SRRP master was received.

The value of tmnxSrrpOperVrrpPolicy1 specifies the first VRRP control policy associated with this SRRP instance.

The value of tmnxSrrpOperVrrpPolicy2 specifies the second VRRP control policy associated with this SRRP instance.

The value of tmnxSrrpOperFlags indicates the operational status of this SRRP instance. subnetMismatch(0) One the subnets that SRRP is backing up does not have a match with the peer. srrpIdMismatch(1) The peer has a different SRRP instance ID backing the same subnet. sapMismatch(2) The local SRRP instance is backing a different set of SAPs than the peer. sapTagMismatch(3) The local SRRP instance is backing a set of SAPs with different remote and local tags. redIfMismatch(4) The local SRRP instance and remote SRRP instance have mismatching redundant interfaces. dualMaster(5) Both SRRP instances are master at the same time. dupSubIfAddr(6) The IP address for a local subscriber interface conflicts with the IP address for a remote subscriber interface. Bits: 'srrpIdMismatch': 1, 'subnetMismatch': 0, 'dualMaster': 5, 'sapTagMismatch': 3, 'redIfMismatch': 4, 'sapMismatch': 2, 'dupSubIfAddr': 6.

The value of tmnxSrrpOperMasterDownInterval indicates the time interval for the backup router to declare the master as down. It is calculated as (3 * Advertisement_Interval) + Skew_time where Skew_Time is calculated as (256 - Priority) / 256.

The value of tmnxSrrpOperMasterDownTimer indicates the current value of the Master Down Timer. When a backup router receives an SRRP advertisement from a master, it resets this timer to the value of the Master Down Interval and begins to count down. If the backup router does not receive an advertisement till this timer times out, it will assume that the master is down and will declare itself to be the master.

The value of tmnxSrrpOperSendFibPopulation specifies the mode used to send FIB population packets on this SRRP instance. When the value of tmnxSrrpOperSendFibPopulation is set to 'all', FIB population packets are sent for every subscriber VLAN. When the value of tmnxSrrpOperSendFibPopulation is set to 'outerTagOnly', FIB population pakckets are sent only on outer VLANs when the group interface SAPs are QinQ encapsulated. Enumeration: 'all': 1, 'outerTagOnly': 2.

The value of tmnxSrrpOperPreempt specifies whether to allow SRRP instance to override an existing master.

The value of tmnxSrrpOperOneGarpPerSap specifies whether to send one gratuitous ARP for each SAP.

The value of tmnxSrrpOperMonitorOperGrp specifies the name of the monitoring operation group.

The value of tmnxSrrpOperPriorityStep specifies the value by which the advertisement priority is decremented whenever a member of the operational-group monitored goes down. An 'inconsistentValue' error is returned if tmnxSrrpOperPriorityStep is set to non-default value and tmnxSrrpOperMonitorOperGrp is set to its default value.

The tmnxMcLagInfoLagTable has an entry for each lag that participates in a multi-chassis configuration for the indicated peer.

Each row entry represents operational data for a lag that participates in a multi-chassis configuration with a given peer. Rows are created or removed automatically by the system, each time a row is created or deleted in the tmnxMcLagConfigLagTable.

The value of tmnxMcLagActiveStandby indicates whether this mc-lag is active or standby. If the value of this object is 'true', this mc-lag is active.

The value of tmnxMcLagLacpIdInUse indicates whether or not the mc-lag values (i.e. system-id, system priority and lacp-key) are advertised to the Lacp peer. If the value of this object is 'true', the mc-lag values are advertised. Otherwise the normal lag values are advertised.

The value of tmnxMcLagExtendedTimeOut indicates whether or not the system is using the value of tmnxMcLagConfigHoldOnNgbrFailure. If this is 'true', the system is temporarily using a larger value than the value configured in tmnxMcLagConfigHoldOnNgbrFailure.

The value of tmnxMcLagSelectionLogic is a printable character string which contains information about the multi-chassis selection logic.

The value of tmnxMcLagConfigMismatchString is a printable character string which contains information about the multi-chassis configuration mismatch.

The value of tmnxMcLagConfigMismatchFlags indicates the operational status of the multi-chassis configuration. lagIsNotMultiChassis(0) The lag is not multi-chassis on the peer. localRemoteLagIdMismatch(1) Local - remote Lag ID mismatch with the peer. lagSelectionCriteriaMismatch(2) LAG selection criteria mismatch with the peer. lagEncapsulationMismatch(3) LAG Encapsulation mismatch with the peer. mcLacpkeyMismatch(4) MC lacp-key mismatch with the peer. mcSystemPriorityMismatch(5) MC system-priority mismatch with the peer. mcSystemIdMismatch(6) MC system-id mismatch with the peer. Bits: 'lagEncapsulationMismatch': 3, 'localRemoteLagIdMismatch': 1, 'mcSystemIdMismatch': 6, 'mcSystemPriorityMismatch': 5, 'mcLacpkeyMismatch': 4, 'lagSelectionCriteriaMismatch': 2, 'lagIsNotMultiChassis': 0.

The tmnxMcsClientAppTable has an entry for each application using the multi-chassis peer synchronization protocol configured on this system.

Each row entry represents a particular multi-chassis peer synchronization protocol application. Entries cannot be created and deleted via SNMP SET operations.

The value of tmnxMcsClientApplication indicates the type of application using multi-chassis synchronization.

The value of tmnxMcsClientNumEntries indicates the total number of entries in the MCS database per multi-chassis peer for a particular application.

The value of tmnxMcsClientLclDeletedEntries indicates the number of locally deleted entries in the MCS database per multi-chassis peer for a particular application. Locally deleted entries are entries that are not being used by the local MCS client application.

The value of tmnxMcsClientAlarmedEntries indicates the number of alarmed entries in the MCS database per multi-chassis peer for a particular application. Entries with an alarm are entries that are not being used by the local client application due to resource constraints.

The value of tmnxMcsClientRemNumEntries indicates the total number of entries in the MCS database on the multi-chassis peer for a particular application.

The value of tmnxMcsClientRemLclDelEntries indicates the number of locally deleted entries in the MCS database ont he multi-chassis peer for a particular application. Locally deleted entries are entries that are not being used by the remote MCS client application.

The value of tmnxMcsClientRemAlarmedEntries indicates the number of alarmed entries in the MCS database on the multi-chassis peer for a particular application. Entries with an alarm are entries that are not being used by the remote client application due to resource constraints.

The tmnxSrrpStatsTable has an entry for each Subscriber Router Redundancy Protocol instance configured on this system.

Each row entry represents the statistics for a particular SRRP instance tied to a service group interface. Entries are created/deleted in conjunction with entries in the tmnxSrrpOperTable

The value for tmnxSrrpStatsBecomeMaster indicates the total number of times that the virtual router's state has transitioned to master.

The value for tmnxSrrpStatsMasterChanges indicates the total number of times the virtual router has seen the master virtual router change.

The value for tmnxSrrpStatsAdvSent indicates the total number of SRRP advertisements sent by this virtual router.

The value for tmnxSrrpStatsAdvRcvd indicates the total number of SRRP advertisements received by this virtual router.

The value for tmnxSrrpStatsPriZeroPktsRcvd indicates the total number of SRRP packets received by the virtual router with a priority of '0'.

The value for tmnxSrrpStatsPriZeroPktsSent indicates the total number of SRRP packets sent by the virtual router with a priority of '0'.

The value for tmnxSrrpStatsPreemptEvents indicates the total number of times the virtual router has preempted another non-owner master with lower priority.

The value for tmnxSrrpStatsPreemptedEvents indicates the total number of times the virtual router has been preempted by another non-owner master with higher priority.

The value for tmnxSrrpStatsAdvIntDiscards indicates the total number of SRRP advertisement packets discarded because the advertisement interval in the received packet was different than the one configured for the local virtual router.

The value for tmnxSrrpStatsAdvIntErrors indicates the total number of SRRP advertisement packets received for which the advertisement interval is different than the one configured for the local virtual router.

The value for tmnxSrrpStatsBecomeBackupRouting indicates the total number of times that the virtual router's state has transitioned to backup routing state.

The value for tmnxSrrpStatsBecomeBackupShunt indicates the total number of times that the virtual router's state has transitioned to backup shunt.

The value for tmnxSrrpStatsBecomeNonMaster indicates the total number times that the virtual router's state has transitioned from master to a non-master state.

The value of tmnxMcRingTableLastChanged indicates the sysUpTime at the time of the last modification of an entry in the tmnxMcRingTable. If no changes were made to the table since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcRingTable has an entry for each multi-chassis ring that participates in a multi-chassis configuration for the indicated peer.

Each row entry represents configuration data for a ring that participates in a multi-chassis configuration with a given peer. Rows can be created and deleted by the operator.

The value of tmnxMcRingRowStatus specifies the row status of this row.

The value of tmnxMcRingLastChanged indicates the sysUpTime at the time of the last modification of this entry. If no changes were made to the entry since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcRingAdminState specifies the administrative state of the multi-chassis ring.

If the interface used for the inband control connection belongs to a VPRN service, the value of tmnxMcRingInbCtrlSvcId specifies its service ID. Otherwise, the value of tmnxMcRingInbCtrlSvcId is zero. In the latter case, the interface must belong to the Base router.

The value of tmnxMcRingInbCtrlIfName specifies the name of the IP interface used for the inband control connection. If the name is not configured, the ring cannot become operational.

The value of tmnxMcRingInbCtrlDestIpType specifies the type of host address stored in tmnxMcRingInbCtrlDestIp.

The value of tmnxMcRingInbCtrlDestIp specifies the destination IP address used in the inband control connection. If the address is not configured, the ring cannot become operational.

The value of tmnxMcRingVlanMap specifies the set of VLAN ID's associated with the SAP's that belong to Path B of this ring. A ring connection is sub-divided into 2 'channels', Path A and Path B. In normal operating condition, when the value of tmnxMcRingInfoOperState is equal to 'connected (5)', one peer system controls Path A, the other Path B, according to an arbitrary tie-breaker rule based on the peer systems' IP address. Otherwise, both peer systems control Path A and Path B. The SAP's associated with the excluded range, specified by the value of tmnxMcRingVlanMapExcl, are never controlled by either peer system. Path A is the complement of Path B. In the system that controls Path B, the value of the object tmnxMcRingInfoCtrlVlanMap is equal to 'true'. The value of tmnxMcRingVlanMap is a bitmap that associates bit i with VLAN ID i, with i in [0..4095]. 4095 corresponds to a dot1q default or capture SAP. In case of QinQ encapsulation, the outermost VLAN ID is referred to. Setting the value of tmnxMcRingVlanMap to the empty string is equivalent to setting it to 512 zeroes.

The value of tmnxMcRingVlanMapExcl specifies the set of VLAN ID's associated with the SAP's that are to be excluded from control by the multi-chassis ring. It is a bitmap that associates bit i with VLAN ID i, with i in [0..4094]. 4095 corresponds to a dot1q default or capture SAP. In case of QinQ encapsulation, the outermost VLAN ID is referred to. Setting the value of tmnxMcRingVlanMapExcl to the empty string is equivalent to setting it to 512 zeroes.

The value of tmnxMcRingInbCtrlDbMax specifies the maximum debounce time on the transition of the operational state of the inband control connection from 'connected (2)' to 'broken (3)'.

The value of tmnxMcRingInbCtrlDbAdmin specifies the administrative state of the debounce mechanism on the transition of the operational state of the inband control connection from 'connected (2)' to 'broken (3)'.

The value of tmnxMcRingType specifies the type of multi-chassis ring.

The value of tmnxMcRingInfoTableLastChanged indicates the sysUpTime at the time of the last change of an entry in the tmnxMcRingInfoTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcRingInfoTable has an entry for each multi-chassis ring that participates in a multi-chassis configuration for the indicated peer.

Each row entry in the tmnxMcRingInfoTable represents additional columns of operational data for a ring that participates in a multi-chassis operation with a given peer.

The value of tmnxMcRingInfoLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcRingInfoOperState indicates the operational state of the multi-chassis ring.

The value of the object tmnxMcRingInfoFailureReason is a printable character string that explains the reason why the tmnxMcRingInfoOperState is in one of the failed states.

The value of tmnxMcRingInfoInbCtrlOperState indicates the operational state of the inband control connection.

The value of tmnxMcRingInfoInbCtrlSrcIpType indicates the type of host address stored in tmnxMcRingInfoInbCtrlSrcIp.

The value of tmnxMcRingInfoInbCtrlSrcIp indicates the source IP address used in the inband control connection.

The value of tmnxMcRingInfoInbCtrlDbStart indicates the sysUpTime the last time that the debounce timer was started on the transition of the operational state of the inband control connection from 'connected (2)' to 'broken (3)'. If the debounce timer was never started, this object contains a zero value.

The value of tmnxMcRingInfoInbCtrlDbTime indicates the value of the debounce timer at the time indicated by the value of tmnxMcRingInfoInbCtrlDbStart. Data traffic may have been dropped starting from the time indicated by tmnxMcRingInfoInbCtrlDbStart during the interval indicated by tmnxMcRingInfoInbCtrlDbTime.

The value of tmnxMcRingInfoPortId indicates the port ID of the port associated with this ring.

The value of tmnxMcRingInfoVlanMap indicates the actual set of VLAN ID's associated with the SAP's that are controlled by the slave peer. It is a bitmap that associates bit i with VLAN ID i, with i in [0..4094]. An empty string is equivalent to 512 zeroes.

The value of tmnxMcRingInfoVlanMapExcl indicates the actual set of VLAN ID's associated with the SAP's that are excluded from control by the multi-chassis ring. It is a bitmap that associates bit i with VLAN ID i, with i in [0..4094]. An empty string is equivalent to 512 zeroes.

The value of tmnxMcRingInfoCtrlVlanMap indicates if this sytem is currently controlling the SAP's indicated by tmnxMcRingInfoVlanMap.

The value of tmnxMcRingInfoInbCtrlDbGuard indicates the value of the debounce guard time. The debounce guard time serves to reset the debounce mechanism on the transitions of the tmnxMcRingInfoInbCtrlOperState. If no such transitions occur during the debounce guard time, the debounce mechanism is reset.

The value of tmnxMcRingNodeTableLastChanged indicates the sysUpTime at the time of the last modification of an entry in the tmnxMcRingNodeTable. If no changes were made to the table since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcRingNodeTable has an entry for each access node that participates in a multi-chassis ring configuration for the indicated peer.

Each row entry represents configuration data related to an access node that participates in a multi-chassis ring configuration with a given peer. Rows can be created and deleted by the operator.

The value of tmnxMcRingNodeName specifies the unique name of a multi-chassis ring access node.

The value of tmnxMcRingNodeRowStatus specifies the row status of this row.

The value of tmnxMcRingNodeLastChanged indicates the sysUpTime at the time of the last modification of this entry. If no changes were made to the entry since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcRingNodeRncvAdminState specifies the administrative state of the Ring-Node Connectivity Verification of this ring node. When the value of tmnxMcRingInfoOperState in the corresponding tmnxMcRingInfoEntry is equal to 'broken', the Ring-Node Connectivity Verification operates automatically, regardless of the value of tmnxMcRingNodeRncvAdminState. This auto- matic operation uses the parameter values configured in this entry, except tmnxMcRingNodeRncvInterval.

The value of tmnxMcRingNodeRncvSvcId specifies the service ID of the SAP used for the Ring-Node Connectivity Verification of this ring node.

The value of tmnxMcRingNodeRncvEncapValue specifies the encapsulation value of the SAP used for the Ring-Node Connectivity Verification of this ring node. It is only meaningful if the value of tmnxMcRingNodeRncvSvcId is not zero. The value zero means that the SAP used for the Ring-Node Connectivity Verification of this ring node uses NULL encapsulation.

The value of tmnxMcRingNodeRncvSrcIpType specifies the type of host address stored in tmnxMcRingNodeRncvSrcIp.

The value of tmnxMcRingNodeRncvSrcIp specifies the source IP address used in the Ring-Node Connectivity Verification of this ring node.

The value of tmnxMcRingNodeRncvDestIpType specifies the type of host address stored in tmnxMcRingNodeRncvDestIp.

The value of tmnxMcRingNodeRncvDestIp specifies the destination IP address used in the Ring-Node Connectivity Verification of this ring node.

The value of tmnxMcRingNodeRncvInterval specifies the polling interval of the Ring-Node Connectivity Verification of this ring node.

The value of tmnxMcRingNodeRncvSrcMac specifies the source MAC address used for the Ring-Node Connectivity Verification of this ring node. The value 'all zeroes' specifies that the MAC address of the system management processor (CPM) is used.

The value of tmnxMcRingNodeInfoTableLastChgd indicates the sysUpTime at the time of the last change of an entry in the tmnxMcRingNodeInfoTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcRingNodeInfoTable has an entry for each access node that participates in a multi-chassis ring configuration for the indicated peer.

Each row entry represents operational data related to an access node that participates in a multi-chassis ring configuration with a given peer. Rows are created or removed automatically by the system.

The value of tmnxMcRingNodeInfoLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcRingNodeInfoLocOperState indicates the operational state of the ring node as monitored by the local chassis.

The value of tmnxMcRingNodeInfoRemOperState indicates the operational state of the ring node as monitored by the remote chassis.

The value of tmnxMcRingNodeInfoInUse indicates if this ring node is currently used by any subscriber or configured as ring-node on any SAP.

The value of the object tmnxMcRingNodeInfoFailureReason is a printable character string that explains the reason why the tmnxMcRingNodeInfoLocOperState is in one of the failed states.

The value of tmnxMcTlsCfgTableLastChanged indicates the sysUpTime at the time of the last change of an entry in the tmnxMcTlsCfgTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcTlsCfgTable has an entry for each TLS Service.

Each row entry in the tmnxMcTlsCfgTable represents additional columns in the TIMETRA-SERV-MIB::svcTlsInfoTable for attributes needed in a multi-chassis operation.

The value of tmnxMcTlsCfgLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcTlsCfgDefGwIpType specifies the type of host address stored in tmnxMcTlsCfgDefGwIp.

The value of tmnxMcTlsCfgDefGwIp specifies the default gateway IP address used in multi-chassis operation associated with this TLS service.

The value of tmnxMcTlsCfgDefGwMac specifies the default gateway MAC address used in multi-chassis operation associated with this TLS service.

The value of tmnxMcEpipeSapTableLastChanged indicates the sysUpTime at the time of the last change of an entry in the tmnxMcEpipeSapTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

A table that contains multi-chassis ring information for epipe SAP's.

Multi-chassis ring information about a specific epipe SAP.

The value of tmnxMcEpipeSapRowStatus specifies the row status of this row.

The value of tmnxMcEpipeSapLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcEpipeSapRingNodeName specifies the unique name of a multi-chassis ring access node. It is used to identify the multi-chassis ring node associated with this entry.

The value of tmnxMcsDhcpsTableLastChgd indicates the sysUpTime at the time of the last modification of an entry in the tmnxMcsDhcpsTable. If no changes were made to the table since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcsDhcpsTable has an entry for each DHCP Server that is being synchronized with a multi-chassis peer. Before creating an entry in this table, the entry in the tmnxMcPeerSyncTable that corresponds to this peer, must be created.

Each row entry represents a DHCP Server to be synchronized. Entries are created/deleted by the user.

The value of tmnxMcsDhcpsRtrID specifies the virtual router instance of the DHCP Server to be synchronized with the multi-chassis peer. The value '1' specifies that the DHCP Server belongs to the Base router. For a DHCP Server in the context of a VPRN service, the virtual router ID is indicated in the svcVRouterId of the svcBaseInfoTable.

The value of tmnxMcsDhcpsServerName specifies the DHCP Server to be synchronized with the multi-chassis peer.

This object allows entries to be created and deleted in the tmnxMcsDhcpsTable. The object tmnxMcsDhcpsSyncTag must be set when creating a new row.

The value of tmnxMcsDhcpsPeerIpType specifies the address type of tmnxMcsDhcpsPeerIpAddr. The value of tmnxMcsDhcpsPeerIpType must be set simultaneously with the value of tmnxMcsDhcpsPeerIpAddr and the value of tmnxMcsDhcpsSyncTag. When the value of tmnxMcsDhcpsRowStatus is set to 'createAndGo', the value of tmnxMcsDhcpsPeerIpType must be set, too. Modifying the value of tmnxMcsDhcpsPeerIpType while the value of tmnxMcsDhcpsRowStatus is equal to 'active', is only alllowed while the value of TIMETRA-DHCP-SERVER-MIB::tmnxDhcpsFoState for this DHCP Server is equal to 'partnerDown (5)'.

The value of tmnxMcsDhcpsPeerIpAddr specifies the address of the multi-chassis peer. Its type is specified by tmnxMcsDhcpsPeerIpType. It must be a valid unicast address. The value of tmnxMcsDhcpsPeerIpAddr must be set simultaneously with the value of tmnxMcsDhcpsPeerIpType and the value of tmnxMcsDhcpsSyncTag. When the value of tmnxMcsDhcpsRowStatus is set to 'createAndGo', the value of tmnxMcsDhcpsPeerIpAddr must be set, too. Modifying the value of tmnxMcsDhcpsPeerIpAddr while the value of tmnxMcsDhcpsRowStatus is equal to 'active', is only alllowed while the value of TIMETRA-DHCP-SERVER-MIB::tmnxDhcpsFoState for this DHCP Server is equal to 'partnerDown (5)'.

The value of tmnxMcsDhcpsSyncTag specifies a synchronization tag to be used while synchronizing this DHCP Server with the multi-chassis peer. The value of tmnxMcsDhcpsSyncTag must be set simultaneously with the value of tmnxMcsDhcpsPeerIpAddr and the value of tmnxMcsDhcpsPeerIpType. When the value of tmnxMcsDhcpsRowStatus is set to 'createAndGo', the value of tmnxMcsDhcpsSyncTag must be set, too. Modifying the value of tmnxMcsDhcpsSyncTag while the value of tmnxMcsDhcpsRowStatus is equal to 'active', is only alllowed while the value of TIMETRA-DHCP-SERVER-MIB::tmnxDhcpsFoState for this DHCP Server is equal to 'partnerDown (5)'.

Timestamp of the last change to the tmnxSrrpAssoBfdIntfTable either from adding a row or removing a row.

The tmnxSrrpAssoBfdIntfTable is a read-only table which provides a list of the BFD interfaces associated with the corrosponding SRRP instance. The BFD interface provides a fast mechanism for changing the state of an SRRP instance riding on the same subnet.

Each row entry in the tmnxSrrpAssoBfdIntfTable represents the BFD interface associated with SRRP instance tied to a service group interface.

The value of tmnxSrrpAssoBfdIntfSvcId specifies the service ID of the interface running BFD.

The value of tmnxSrrpAssoBfdIntfIfName specifies the name of the interface running BFD.

The value of tmnxSrrpAssoBfdIntfDestIpType specifies the address type of tmnxSrrpAssoBfdIntfDestIp object.

The value of tmnxSrrpAssoBfdIntfDestIp specifies the destination IP address on the interface running BFD.

This object tmnxSrrpAssoBfdIntfRowStatus is used for creation or deletion of entries in the tmnxSrrpAssoBfdIntfEntry. Deletion of an entry in this table will not succeed if it is currently associated with any SRRP instance.

The value of tmnxSrrpAssoBfdIntfLastChanged specifies the time stamp of the last change to this row of this table.

The value of tmnxSrrpAssoBfdIntfSrcIpType indicates the address type of tmnxSrrpAssoBfdIntfSrcIp object.

The value of tmnxSrrpAssoBfdIntfSrcIp indicates the source IP address on the interface running BFD.

The value of tmnxSrrpAssoBfdIntfSessOperState indicates the operational state of the BFD session the SRRP instance is relying upon for its fast triggering mechanism.

The value of tmnxMcRingDbTableLastChanged indicates the sysUpTime at the time of the last modification of an entry in the tmnxMcRingDbTable. If no changes were made to the table since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcRingDbTableSize indicates the maximum number of entries that the tmnxMcRingDbTable can contain.

The tmnxMcRingDbTable has an entry for each time a multi-chassis ring's operational state change was debounced. Only up to the last n occurances are available, where n is equal to the value of tmnxMcRingDbTableSize.

Each row entry represents information about a debounce event. Rows are created automatically by the system.

The value of tmnxMcRingDbStart indicates the sysUpTime when the debounce timer was started on the transition of the operational state of the inband control connection from 'connected (2)' to 'broken (3)'.

The value of tmnxMcRingDbTime indicates the value of the debounce timer at the time indicated by the value of tmnxMcRingDbStart. Data traffic may have been dropped starting from the time indicated by tmnxMcRingDbStart during the interval indicated by tmnxMcRingDbTime.

The value of tmnxMcRingDbOperState indicates the operational state of the inband control connection after debouncing.

The value of tmnxMcL3RingSrrpTableLastChanged indicates the sysUpTime at the time of the last modification of an entry in the tmnxMcL3RingSrrpTable. If no changes were made to the table since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcL3RingSrrpTable has an entry for each multi-chassis layer-3 ring that participates in a multi-chassis configuration for the indicated peer with the indicated SRRP instance.

Each row entry represents configuration data for a layer 3 ring that participates in a multi-chassis configuration with a given peer of a given SRRP instance. Rows can be created and deleted by the operator.

The value of tmnxMcL3RingSrrpRowStatus specifies the row status of this row.

The value of tmnxMcL3RingSrrpLastChanged indicates the sysUpTime at the time of the last modification of this entry. If no changes were made to the entry since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcPeerEPTableLastChanged indicates the sysUpTime at the time of the last modification of an entry in the tmnxMcPeerEPTable. If no changes were made to the table since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcPeerEPTable has an entry for each multi-chassis peer end-point configured on this system.

Each row entry represents a particular multi-chassis peer end-point. Entries are create/deleted by the user.

The value of tmnxMcPeerEPRowStatus is used for creation/deletion of multi-chassis peer end-points.

The value of tmnxMcPeerEPLastChanged indicates the sysUpTime at the time of the last modification of this entry. If no changes were made to the entry since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcPeerEPAdminState specifies the administrative state of this multi-chassis peer end-point.

The value of tmnxMcPeerEPSysPriority specifies the system priority of this multi-chassis peer end-point.

The value of tmnxMcPeerEPKeepAliveIntvl specifies the interval at which keep-alive messages are exchanged between two peers participating in a multi-chassis end-point tunnel (MC-EP). These keep-alive messages are used to determine remote-node failures.

The value of tmnxMcPeerEPHoldOnNbrFail specifies the number of keep-alive intervals that the local peer will wait for packets from the multi-chassis end-point peer before assuming failure.

The value of tmnxMcPeerEPBootTimer specifies the time the multi-chassis end-point protocol keeps trying the establish a connection before assuming a failure of the remote-peer. This object is used at the boot-time only.

The value of tmnxMcPeerEPPassiveMode specifies whether passive-mode behavior is configured for the multi-chassis end-point tunnel.

The value of tmnxMcPeerEPBfd specifies whether bi-directional forwarding detection (BFD) is configured for this multi-chassis end-point peering tunnel.

The value of tmnxMcPeerEPOperState indicates the operational status of this multi-chassis end-point peer. Enumeration: 'outOfService': 1, 'inService': 0.

The value of tmnxMcPeerEPPeerLastStateChge indicates the sysUpTime at the time of the last operational state change for this multi-chassis end-point peer. If no changes were made since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcPeerEPPassiveModeOper indicates whether passive-mode behavior is operationally enabled on this multi-chassis end-point tunnel. This behavior can be operationally enabled if one of the end-point of the tunnel has tmnxMcPeerEPPassiveMode set to 'enabled'.

The value of tmnxMcPeerEPRefCount indicates how many service end-points are referencing this multi-chassis end-point.

The value of tmnxMcRedBgpMultiHomeBootTimer specifies how long the system waits after a node reboot before running the DF (designated- forwarder) election algorithm.

The value of tmnxMcRedBgpMultiHomeSiteTimer specifies the time-period the system keeps the local sites in standby status, waiting for BGP updates from remote PEs before running the DF (designated-forwarder) election algorithm to decide whether the site should be unblocked.

The value of tmnxMcTlsSapTableLastChanged indicates the sysUpTime at the time of the last change of an entry in the tmnxMcTlsSapTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

A table that contains multi-chassis ring information for vpls SAP's.

Multi-chassis ring information about a specific vpls SAP.

The value of tmnxMcTlsSapRowStatus specifies the row status of this row.

The value of tmnxMcTlsSapLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcTlsSapRingNodeName specifies the unique name of a multi-chassis ring access node. It is used to identify the multi-chassis ring node associated with this entry.

The value of tMcPeerIPsecTblLastChgd indicates the sysUpTime at the time of the last change of an entry in the tMcPeerIPsecTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tMcPeerIPsecTable has an entry for ipsec specific objects per multi-chassis peer configured on this system.

Each row entry represents ipsec specific objects in a particular multi-chassis peer. Entries are create/deleted by the user.

The value of tMcPeerIPsecRowStatus specifies the row status of this row.

The value of tMcPeerIPsecLastChgd indicates the sysUpTime at the time of the last modification of this entry. If no changes were made to the entry since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tMcPeerIPsecKeepAliveIntvl specifies the ipsec specific keepalive timer value in units of 0.1 sec. This defines the interval at which keep-alive messages are exchanged between two systems participating in mutli-chassis ipsec tunnels. These keep-alive messages are used to determine remote-node failure.

The value of tMcPeerIPsecHoldOnNgbrFail specifies how many tMcPeerIPsecKeepAliveIntvl intervals the standby node will wait for packets from the active node before assuming a redundant-neighbor node failure. This delay in switch-over operation is required to accommodate for different factors influencing node failure detection rate, such as IGP convergence, or HA switch-over times and to prevent that the standby node takes actions prematurely.

The value of tMcPeerIPsecBfdEnableSvc specifies the service ID of the interface running BFD.

The value of tMcPeerIPsecBfdIntfIfName specifies the name of the interface running BFD.

The value of tMcPeerIPsecBfdIntfDestIpType specifies the address type of tMcPeerIPsecBfdIntfDestIp object.

The value of tMcPeerIPsecBfdIntfDestIp specifies the destination IP address on the interface running BFD.

The value of tMcPeerIPsecDiscoveryIntvl specifies the maximum duration of the discovery interval during which a newly activated multi-chassis IPsec tunnel-group will remain dormant while trying to contact its redundant peer. Groups held dormant in this manner will neither pass traffic nor negotiate security keys. This interval ends when either the redundant peer is contacted and a master election occurs, or when the maximum duration expires.

The value of tMcPeerIPsecDiscoveryIntvlBoot specifies the maximum duration of an interval immediately following system boot up. When the normal discovery interval for a group would expire while the post-boot discovery interval is still active, then the group's discovery interval is extended until the post-boot discovery interval expires. This allows an extension to the normal discovery stage of groups following a chassis reboot, to account for the larger variance in routing convergence time.

The value of tMcPeerIPsecBfdEnableSvc specifies whether BFD is enabled on the interface. The 'inconsistentValue' error is returned if this object is set to non-default value and any of tMcPeerIPsecBfdEnableSvc, tMcPeerIPsecBfdIntfIfName, tMcPeerIPsecBfdIntfDestIpType, tMcPeerIPsecBfdIntfDestIp are set to non-default value.

The value of tMcPeerIPsecTnlGrpTblLastChgd indicates the sysUpTime at the time of the last change of an entry in the tMcPeerIPsecTnlGrpTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tMcPeerIPsecTnlGrpTable has an entry for each ipsec tunnel group specific to multi-chassis peer configured on this system.

Each row entry represents a particular ipsec tunnel group of multi-chassis peer. Entries are create/deleted by the user.

The value of tMcPeerIPsecTnlGrpId specifies the tunnel-group identifier for this row.

The value of tMcPeerIPsecTnlGrpRowStatus specifies the row status of this row.

The value of tMcPeerIPsecTnlGrpLastChgd indicates the sysUpTime at the time of the last modification of this entry. If no changes were made to the entry since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tMcPeerIPsecTnlGrpPeerGrpId specifies the tunnel-group identifier of the peer for this tunnel-group. A value of zero indicates that peer-group is not specified.

The value of tMcPeerIPsecTnlGrpPriority specifies the priority of this tunnel-group.

The value of tMcPeerIPsecTnlGrpPreempt specifies whether to allow mastership preemption by this tunnel group.

The value of tMcPeerIPsecTnlGrpAdminState specifies the admin state of this tunnel-group.

The value of tMcPeerIPsecTnlGrpOperState indicates the operational state of this tunnel-group communicating with the peer tunnel-group.

The value of tMcPeerIPsecTnlGrpMasterState indicates the result of the mastership election between this tunnel group entity and its peer.

The value of tMcPeerIPsecTnlGrpReason indicates the reason why tMcPeerIPsecTnlGrpOperState is out of service.

The tMcPeerIPsecTnlGrpForceSwitch specifies to perform manual mastership switch between this tunnel-group and its redundant peer.

The value of tmnxMcsTnlGrpTblLastChgd indicates the sysUpTime at the time of the last change of an entry in the tmnxMcsTnlGrpTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcsTnlGrpTable has an entry for each ipsec tunnel group specific to multi-chassis peer configured on this system.

Each row entry represents a particular ipsec tunnel group of multi-chassis peer to be synchronized. Entries are create/deleted by the user.

The value of tmnxMcsTnlGrpRowStatus specifies the row status of this row.

The value of tmnxMcsTnlGrpSyncTag specifies the synchronization tag assigned to this tunnel-group to be synchronized on this multi-chassis peer. Value of this object must be set at the time of creation of the entry.

The tMcPeerTnlGrpStatTable has statistics entry for each ipsec tunnel group specific to multi-chassis peer configured on this system.

Each row entry represents a particular ipsec tunnel statistics group of multi-chassis peer.

The value of tMcPeerTnlGrpStatDynInstalled indicates the number of dynamic multi-chassis tunnel installed on this tunnel-group to be synchronized on this multi-chassis peer.

The value of tMcPeerTnlGrpStatDynInstalled indicates the number of dynamic multi-chassis tunnel being installed on this tunnel-group to be synchronized on this multi-chassis peer.

The value of tMcPeerTnlGrpStatDynAwaitConf indicates the number of dynamic multi-chassis tunnel awaiting configuration on this tunnel-group to be synchronized on this multi-chassis peer.

The value of tMcPeerTnlGrpStatDynFailed indicates the number of dynamic multi-chassis tunnel failed to install on this tunnel-group to be synchronized on this multi-chassis peer.

The value of tMcPeerTnlGrpStatInstalled indicates the number of static multi-chassis tunnel installed on this tunnel-group to be synchronized on this multi-chassis peer.

The value of tMcPeerTnlGrpStatInstalled indicates the number of static multi-chassis tunnel being installed on this tunnel-group to be synchronized on this multi-chassis peer.

The value of tMcPeerTnlGrpStatAwaitConf indicates the number of static multi-chassis tunnel awaiting configuration on this tunnel-group to be synchronized on this multi-chassis peer.

The value of tMcPeerTnlGrpStatFailed indicates the number of static multi-chassis tunnel failed to install on this tunnel-group to be synchronized on this multi-chassis peer.

The value of tmnxMcLagStatsPktsRx indicates how many MC-Lag control packets with valid authentication were received on this system.

The value of tmnxMcLagStatsPktsRxKeepalive indicates how many valid MC-Lag control packets of type keepalive were received on this system.

The value of tmnxMcLagStatsPktsRxConfig indicates how many valid MC-Lag control packets indicating the lag configuration were received on this system.

The value of tmnxMcLagStatsPktsRxPeerConfig indicates how many valid MC-Lag control packets indicating the peer configuration were received on this system.

The value of tmnxMcLagStatsPktsRxState indicates how many valid MC-Lag control packets indicating the lag state were received on this system.

The value of tmnxMcLagStatsDropPktKpaliveTask indicates how many MC-Lag control packets were dropped on this system because of invalid size, authentication or unknown peer.

The value of tmnxMcLagStatsDropPktTooShort indicates how many MC-Lag control packets were dropped on this system because the packet was too small.

The value of tmnxMcLagStatsDropPktVerifyFaild indicates how many MC-Lag control packets were dropped on this system because of invalid formatting.

The value of tmnxMcLagStatsDropTlvInvalidSize indicates how many MC-Lag control packets were dropped on this system because of invalid size.

The value of tmnxMcLagStatsDropOutOfSeq indicates how many MC-Lag control packets were dropped on this system because they were out of sequence.

The value of tmnxMcLagStatsDropUnknownTlv indicates how many MC-Lag control packets were dropped on this system because they contained an unknown TLV.

The value of tmnxMcLagStatsDropTlvInvldLagId indicates how many MC-Lag control packets were dropped on this system because they refer to an invalid or non multi-chassis lag.

The value of tmnxMcLagStatsDropMD5 indicates how many MC-Lag control packets were dropped on this system because they failed MD5 authentication.

The value of tmnxMcLagStatsDropUnknownPeer indicates how many MC-Lag control packets were dropped on this system because they are coming from an unknown peer.

The value of tmnxMcLagStatsPktsTx indicates how many MC-Lag control packets were transmitted from this system.

The value of tmnxMcLagStatsPktsTxKeepalive indicates how many MC-Lag control packets were transmitted from this system of type keepalive.

The value of tmnxMcLagStatsPktsTxConfig indicates how many MC-Lag control packets were transmitted from this system of type lag config.

The value of tmnxMcLagStatsPktsTxPeerConfig indicates how many MC-Lag control packets were transmitted from this system of type peer config.

The value of tmnxMcLagStatsPktsTxState indicates how many MC-Lag control packets were transmitted from this system of type lag state.

The value of tmnxMcLagStatsPktsTxFailed indicates how many MC-Lag control packets failed to be transmitted.

The tmnxMcLagPeerStatsTable has an entry for each multi-chassis peer configured on this system.

Each row entry represents a collection of statistics for a multi-chassis peer. Entries cannot be created and deleted via SNMP SET operations.

The value of tmnxMcLagPeerStatsPktsRx indicates how many valid MC-Lag control packets were received on this system from the peer.

The value of tmnxMcLagPeerStatsPktsRxKpalive indicates how many valid MC-Lag control packets of type keepalive were received on this system from the peer.

The value of tmnxMcLagPeerStatsPktsRxConfig indicates how many valid MC-Lag control packets of type lag config were received on this system from the peer.

The value of tmnxMcLagPeerStatsPktsRxPeerCfg indicates how many valid MC-Lag control packets of type peer config were received on this system from the peer.

The value of tmnxMcLagPeerStatsPktsRxState indicates how many valid MC-Lag control packets of type lag state were received on this system from the peer.

The value of tmnxMcLagPeerStatsDropStateDsbld indicates how many MC-Lag control packets were dropped on this system from the peer because the peer was administratively disabled.

The value of tmnxMcLagPeerStatsDropPktTooShrt indicates how many MC-Lag control packets were dropped on this system from the peer because the packet was too short.

The value of tmnxMcLagPeerStatsDropTlvInvldSz indicates how many MC-Lag control packets were dropped on this system from the peer because the packet size was invalid.

The value of tmnxMcLagPeerStatsDropTlvInvldId indicates how many MC-Lag control packets were dropped on this system from the peer because the packet referred to an invalid or non multi-chassis lag.

The value of tmnxMcLagPeerStatsDropOutOfSeq indicates how many MC-Lag control packets were dropped on this system from the peer because the packet was out of sequence.

The value of tmnxMcLagPeerStatsDropUnknownTlv indicates how many MC-Lag control packets were dropped on this system from the peer because the packet contained an unknown TLV.

The value of tmnxMcLagPeerStatsDropMD5 indicates how many MC-Lag control packets were dropped on this system from the peer because the packet failed MD5 authentication.

The value of tmnxMcLagPeerStatsPktsTx indicates how many MC-Lag control packets were transmitted from this system to the peer.

The value of tmnxMcLagPeerStatsPktsTxKpalive indicates how many MC-Lag control packets of type keepalive were transmitted from this system to the peer.

The value of tmnxMcLagPeerStatsPktsTxPeerCfg indicates how many MC-Lag control packets of type peer config were transmitted from this system to the peer.

The value of tmnxMcLagPeerStatsPktsTxFailed indicates how many MC-Lag control packets failed to be transmitted from this system to the peer.

The tmnxMcLagLagStatsTable has an entry for each lag that participates in a multi-chassis configuration for the indicated peer.

Each row entry represents a collection of statistics for a lag that participates in a multi-chassis configuration with a given peer. Entries cannot be created and deleted via SNMP SET operations.

The value of tmnxMcLagLagStatsPktsRxConfig indicates how many MC-Lag control packets of type lag config were received on this system from the peer for this lag.

The value of tmnxMcLagLagStatsPktsRxState indicates how many MC-Lag control packets of type lag state were received on this system from the peer for this lag.

The value of tmnxMcLagLagStatsPktsTxConfig indicates how many MC-Lag control packets of type lag config were sent on this system to the peer for this lag.

The value of tmnxMcLagLagStatsPktsTxState indicates how many MC-Lag control packets of type lag state were sent on this system to the peer for this lag.

The value of tmnxMcLagLagStatsPktsTxFailed indicates how many MC-Lag control packets failed to be transmitted on this system to the peer for this lag.

The tmnxMcPeerSyncStatsTable has an entry for each multi-chassis peer synchronization protocol entry.

Each row entry represents a collection of statistics for a multi-chassis synchronization protocol entry. Entries cannot be created and deleted via SNMP SET operations.

The value of tmnxMcPeerSyncPktsTxAll indicates the total number of packets transmitted to the multi-chassis peer.

The value of tmnxMcPeerSyncPktsTxHello indicates the number of hello packets transmitted to the multi-chassis peer.

The value of tmnxMcPeerSyncPktsTxData indicates the number of data packets transmitted to the multi-chassis peer.

The value of tmnxMcPeerSyncPktsTxOther indicates the number of all other packet types transmitted to the multi-chassis peer.

The value of tmnxMcPeerSyncPktsTxErr indicates the number of packet transmission errors.

The value of tmnxMcPeerSyncPktsRxAll indicates the total number of packets received from the multi-chassis peer.

The value of tmnxMcPeerSyncPktsRxHello indicates the number of hello packets received from the multi-chassis peer.

The value of tmnxMcPeerSyncPktsRxData indicates the number of hello packets received from the multi-chassis peer.

The value of tmnxMcPeerSyncPktsRxOther indicates the number of all other packet types received from the multi-chassis peer.

The value of tmnxMcPeerSyncPktsRxErr indicates the number of erroneous packets received from the multi-chassis peer.

The value of tmnxMcPeerSyncPktsRxErrHeader indicates the number of packets with header decode errors received from the multi-chassis peer.

The value of tmnxMcPeerSyncPktsRxErrBody indicates the number of packets with body decode errors received from the multi-chassis peer.

The value of tmnxMcPeerSyncPktsRxErrSeqNum indicates the number of packets with sequence number errors received from the multi-chassis peer.

The value of tmnxMcrPeerStatsTableLastChanged indicates the sysUpTime at the time of the last change of an entry in the tmnxMcrPeerStatsTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcrPeerStatsTable has an entry for each multi-chassis peer.

Each row entry in the tmnxMcrPeerStatsTable represents additional columns of operational data for a multi-chassis peer.

The value of tmnxMcrPeerStatsLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcrPeerStatsRx indicates how many valid MC-Ring signalling messages were received from the peer.

The value of tmnxMcrPeerStatsRxMcsIdReq indicates how many valid MCS ID requests were received from the peer.

The value of tmnxMcrPeerStatsRxMcsIdRsp indicates how many valid MCS ID responses were received from the peer.

The value of tmnxMcrPeerStatsRxRingExistsReq indicates how many valid 'ring exists' requests were received from the peer.

The value of tmnxMcrPeerStatsRxRingExistsRsp indicates how many valid 'ring exists' responses were received from the peer.

The value of tmnxMcrPeerStatsRxKeepAlive indicates how many valid MC-Ring control packets of type 'keepalive' were received from the peer.

The value of tmnxMcrPeerStatsTx indicates how many valid MC-Ring signalling messages were transmitted to the peer.

The value of tmnxMcrPeerStatsTxMcsIdReq indicates how many valid MCS ID requests were transmitted to the peer.

The value of tmnxMcrPeerStatsTxMcsIdRsp indicates how many valid MCS ID responses were transmitted to the peer.

The value of tmnxMcrPeerStatsTxRingExistsReq indicates how many valid 'ring exists' requests were transmitted to the peer.

The value of tmnxMcrPeerStatsTxRingExistsRsp indicates how many valid 'ring exists' responses were transmitted to the peer.

The value of tmnxMcrPeerStatsTxKeepAlive indicates how many valid MC-Ring control packets of type 'keepalive' were transmitted to the peer.

The value of tmnxMcrRingStatsTableLastChanged indicates the sysUpTime at the time of the last change of an entry in the tmnxMcrRingStatsTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcrRingStatsTable has an entry for each multi-chassis ring that participates in a multi-chassis configuration for the indicated peer.

Each row entry in the tmnxMcrRingStatsTable represents additional columns of operational data for a ring that participates in a multi-chassis operation with a given peer.

The value of tmnxMcrRingStatsLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcrRingStatsRxSapsChanged indicates how many valid 'SAPs changed info' signalling messages were received from the peer for this multi-chassis ring.

The value of tmnxMcrRingStatsTxSapsChanged indicates how many valid 'SAPs changed info' signalling messages were transmitted to the peer for this multi-chassis ring.

The value of tmnxMcrRingStatsRxOpaqueDelivrd indicates how many valid opaque signalling messages were received from the peer and delivered for this multi-chassis ring.

The value of tmnxMcrRingStatsRxOpaqueNoDest indicates how many valid opaque signalling messages were received from the peer and for which no destination could be found.

The value of tmnxMcrRingStatsTxOpaque indicates how many valid opaque signalling messages were transmitted to the peer for this multi-chassis ring.

The value of tmnxMcrStatsRx indicates how many MC-Ring signalling packets were received by this system.

The value of tmnxMcrStatsRxTooShort indicates how many MC-Ring signalling packets were received by this system that were too short.

The value of tmnxMcrStatsRxWrongAuth indicates how many MC-Ring signalling packets were received by this system with invalid authentication.

The value of tmnxMcrStatsRxInvalidTlv indicates how many MC-Ring signalling packets were received by this system with invalid TLV.

The value of tmnxMcrStatsRxIncomplete indicates how many MC-Ring signalling packets were received by this system that were incomplete.

The value of tmnxMcrStatsRxUnknownType indicates how many MC-Ring signalling packets were received by this system that were of unknown type.

The value of tmnxMcrStatsRxUnknownPeer indicates how many MC-Ring signalling packets were received by this system that were related to an unknown peer.

The value of tmnxMcrStatsRxUnknownRing indicates how many MC-Ring signalling packets were received by this system that were related to an unknown ring.

The value of tmnxMcrStatsRxUnknownRingNode indicates how many MC-Ring signalling packets were received by this system that were related to an unknown ring node.

The value of tmnxMcrStatsRxDelivrdToPeer indicates how many MC-Ring signalling packets were received by this system that were correctly delivered to their peer.

The value of tmnxMcrStatsRxDelivrdToRing indicates how many MC-Ring signalling packets were received by this system that were correctly delivered to their ring.

The value of tmnxMcrStatsRxDelivrdToRingNode indicates how many MC-R signalling packets were received by this system that were correctly delivered to their ring node.

The value of tmnxMcrStatsTx indicates how many MC-Ring signalling packets were transmitted by this system.

The value of tmnxMcrStatsTxNoBuffer indicates how many MC-Ring signalling packets could not be transmitted by this system due to a lack of packet buffers.

The value of tmnxMcrStatsTxTransmitFailed indicates how many MC-Ring signalling packets could not be transmitted by this system due to a transmission failure.

The value of tmnxMcrStatsMissedConfigEvent indicates the number of missed configuration events on this system.

The value of tmnxMcrStatsMissedBfdEvent indicates the number of missed BFD events on this system.

The value of tmnxMcrStatsTxUnknownDest indicates how many MC-R signalling packets were dropped because the destination was unknown.

The value of tmnxMcrRingNodeStatsTableLastChanged indicates the sysUpTime at the time of the last change of an entry in the tmnxMcrRingNodeStatsTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcrRingNodeStatsTable has an entry for each access node that participates in a multi-chassis ring configuration for the indicated peer.

Each row entry represents statistics related to an access node that participates in a multi-chassis ring configuration with a given peer. Rows are created or removed automatically by the system.

The value of tmnxMcrRingNodeStatsLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcrRingNodeStatsRxDetect indicates how many valid 'detected ring node' signalling messages were received from the peer for this multi-chassis ring node.

The value of tmnxMcrRingNodeStatsRxDetectAck indicates how many valid 'detected ring node' signalling messages were acknowledged by the peer for this multi-chassis ring node.

The value of tmnxMcrRingNodeStatsRncvRxResp indicates how many valid connectivity verification messages were received from this multi-chassis ring node.

The value of tmnxMcrRingNodeStatsTxDetect indicates how many valid 'detected ring node' signalling messages were transmitted to the peer for this multi-chassis ring node.

The value of tmnxMcrRingNodeStatsTxDetectAck indicates how many valid 'detected ring node' signalling messages were acknowledged to the peer for this multi-chassis ring node.

The value of tmnxMcrRingNodeStatsRncvTxReq indicates how many valid connectivity verification messages were transmitted to this multi-chassis ring node.

The value of tmnxMcrRingNodeStatsRncvRtTime indicates the round-trip-time of the last successful connectivity verification for this multi-chassis ring node. If there has not been a successful connectivity verification, the value of tmnxMcrRingNodeStatsRncvRtTime is zero.

The tmnxMcEPPeerStatsTable has an entry for each multi-chassis peer configured on this system.

Each row entry represents a collection of statistics for a multi-chassis peer. Entries cannot be created and deleted via SNMP SET operations.

The value of tmnxMcEPPeerStatsPktsRx indicates how many valid MC-Endpoint control packets were received on this system from the peer.

The value of tmnxMcEPPeerStatsPktsRxKpalive indicates how many valid MC-Endpoint control packets of type keepalive were received on this system from the peer.

The value of tmnxMcEPPeerStatsPktsRxConfig indicates how many valid MC-Endpoint control packets of type end-point config were received on this system from the peer.

The value of tmnxMcEPPeerStatsPktsRxPeerCfg indicates how many valid MC-Endpoint control packets of type peer config were received on this system from the peer.

The value of tmnxMcEPPeerStatsPktsRxState indicates how many valid MC-Endpoint control packets of type end-point state were received on this system from the peer.

The value of tmnxMcEPPeerStatsDropStateDsbld indicates how many MC-Endpoint control packets were dropped on this system from the peer because the peer was administratively disabled.

The value of tmnxMcEPPeerStatsDropPktTooShrt indicates how many MC-Endpoint control packets were dropped on this system from the peer because the packet was too short.

The value of tmnxMcEPPeerStatsDropTlvInvldSz indicates how many MC-Endpoint control packets were dropped on this system from the peer because the packet size was invalid.

The value of tmnxMcEPPeerStatsDropTlvInvldId indicates how many MC-Endpoint control packets were dropped on this system from the peer because the packet referred to an invalid or non multi-chassis end-point.

The value of tmnxMcEPPeerStatsDropOutOfSeq indicates how many MC-Endpoint control packets were dropped on this system from the peer because the packet was out of sequence.

The value of tmnxMcEPPeerStatsDropUnknownTlv indicates how many MC-Endpoint control packets were dropped on this system from the peer because the packet contained an unknown TLV.

The value of tmnxMcEPPeerStatsDropMD5 indicates how many MC-Endpoint control packets were dropped on this system from the peer because the packet failed MD5 authentication.

The value of tmnxMcEPPeerStatsPktsTx indicates how many MC-Endpoint control packets were transmitted from this system to the peer.

The value of tmnxMcEPPeerStatsPktsTxKpalive indicates how many MC-Endpoint control packets of type keepalive were transmitted from this system to the peer.

The value of tmnxMcEPPeerStatsPktsTxPeerCfg indicates how many MC-Endpoint control packets of type peer config were transmitted from this system to the peer.

The value of tmnxMcEPPeerStatsPktsTxFailed indicates how many MC-Endpoint control packets failed to be transmitted from this system to the peer.

The value of tmnxMcEPPeerStatsDropEpNoPeer indicates how many pkts were dropped because MC-Endpoint does not have a MC-peer assigned yet or MC-Endpoint is attached to a different peer.

The value of tmnxMcEpStatsPktsRx indicates how many MC-EP control packets with valid authentication were received on this system.

The value of tmnxMcEpStatsPktsRxKeepalive indicates how many valid MC-EP control packets of type keepalive were received on this system.

The value of tmnxMcEpStatsPktsRxConfig indicates how many valid MC-EP control packets indicating the lag configuration were received on this system.

The value of tmnxMcEpStatsPktsRxPeerConfig indicates how many valid MC-EP control packets indicating the peer configuration were received on this system.

The value of tmnxMcEpStatsPktsRxState indicates how many valid MC-EP control packets indicating the lag state were received on this system.

The value of tmnxMcEpStatsDropPktKpaliveTask indicates how many MC-EP control packets were dropped on this system because of invalid size, authentication or unknown peer.

The value of tmnxMcEpStatsDropPktTooShort indicates how many MC-EP control packets were dropped on this system because the packet was too small.

The value of tmnxMcEpStatsDropPktVerifyFailed indicates how many MC-EP control packets were dropped on this system because of invalid formatting.

The value of tmnxMcEpStatsDropTlvInvalidSize indicates how many MC-EP control packets were dropped on this system because of invalid size.

The value of tmnxMcEpStatsDropOutOfSeq indicates how many MC-EP control packets were dropped on this system because they were out of sequence.

The value of tmnxMcEpStatsDropUnknownTlv indicates how many MC-EP control packets were dropped on this system because they contained an unknown TLV.

The value of tmnxMcEpStatsDropTlvInvldEpId indicates how many MC-EP control packets were dropped on this system because they refer to an invalid or non multi-chassis lag.

The value of tmnxMcEpStatsDropMD5 indicates how many MC-EP control packets were dropped on this system because they failed MD5 authentication.

The value of tmnxMcEpStatsDropUnknownPeer indicates how many MC-EP control packets were dropped on this system because they are coming from an unknown peer.

The value of tmnxMcEpStatsPktsTx indicates how many MC-EP control packets were transmitted from this system.

The value of tmnxMcEpStatsPktsTxKeepalive indicates how many MC-EP control packets were transmitted from this system of type keepalive.

The value of tmnxMcEpStatsPktsTxConfig indicates how many MC-EP control packets were transmitted from this system of type lag config.

The value of tmnxMcEpStatsPktsTxPeerConfig indicates how many MC-EP control packets were transmitted from this system of type peer config.

The value of tmnxMcEpStatsPktsTxState indicates how many MC-EP control packets were transmitted from this system of type lag state.

The value of tmnxMcEpStatsPktsTxFailed indicates how many MC-EP control packets failed to be transmitted.

The value of tmnxMcEpStatsDropEpNoPeer indicates how many MC-EP control packets were dropped on this system because no peer was assigned or peer did not match.

The value of tmnxMcPeerIpAddrTypeForNotify indicates the address type of tmnxMcPeerIpAddrForNotify.

The value of tmnxMcPeerIpAddrForNotify indicates the address of the multi-chassis peer to be used in notifications. Its type is specified by tmnxMcPeerIpAddrTypeForNotify.

The value of tmnxMcPeerSyncClient indicates which client has caused the generation of tmnxMcSyncClientAlarmRaised or tmnxMcSyncClientAlarmCleared.

The value of tmnxMcRemoteGrpIfNameForNotify indicates the name of a remote group interface.

The value of tmnxMcRemoteRedIfNameForNotify indicates the name of a remote redundant interface.

The value of tmnxMcRemoteSyncTag indicates the sync tag of a remote object.

The value of tmnxMcLagConfigLagIds is a bitmap that indicates a set of tmnxMcLagConfigLagId's.

The value of tmnxMcPeerClockSkew indicates the difference, in seconds, between the MCS peer system clock time and the local system clock.

The value of tmnxSrrpNotifBfdIntfSvcId specifies the service ID of the interface running BFD in the notification.

The value of tmnxSrrpNotifBfdIntfIfName specifies the name of the interface running BFD in the notification.

The value of tmnxSrrpNotifBfdIntfDestIpType specifies the address type of tmnxSrrpNotifBfdIntfDestIp object.

The value of tmnxSrrpNotifBfdIntfDestIp specifies the destination IP address on the interface running BFD in the notification.

The value of tmnxSrrpNotifBfdIntfSessState indicates the operational state of BFD session on the interface in the notification.

The value of tmnxMcPeerEPBfdSessionOpenStatus indicates the status of multi-chasis endpoint's attempt to open BFD session to the multi-chassis endpoint peer. Enumeration: 'clientAppUseIfFail': 4, 'nonSysLoopbackIf': 2, 'ok': 0, 'clientUseSessionFail': 3, 'invalidSrcAddr': 1.

The value of tmnxMcPeerEPPsvModeConfigState indicates the configuration state of passive-mode with peer. Enumeration: 'mismatchResolved': 2, 'mismatch': 1.

The value of tMcPeerIPsecTnlGrpMasterStateOld indicates the older mastership election state of the tunnel-group from which it transitioned to tMcPeerIPsecTnlGrpMasterState.

The value of tmnxMcPeerMobileTableLstChgd indicates the sysUpTime at the time of the last change of an entry in the tmnxMcPeerMobileTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcPeerMobileTable has an entry for each multi-chassis mobile configuration for the indicated peer.

Each row entry represents configuration data for a multi-chassis mobile control protocol with the given peer. Entries are create/deleted by the user.

The value of tmnxMcPeerMobileRowStatus is used for creation/deletion of multi-chassis mobile configuration entries.

The value of tmnxMcPeerMobileBFDEnable specifies if the Bi-directional Forwarding Detection (BFD) is to be associated with this peer. The multi-chassis mobile redundancy protocol will use the BFD state to determine the liveliness of its peer.

The value of tmnxMcPeerMobileRouteAdvHoldTmr specifies the amount of time each node would wait before changing the multi-chassis mobile state for each tracked interface (e.g. from mobile-slave to mobile-master).

The value of tmnxMcPeerMobileHoldOnNbrFail specifies the number of keep alive intervals that may expire before the local node decides that the peer has failed.

The value of tmnxMcPeerMobileKeepAlvIntvl specifies the interval at which the keep-alive messages are sent to the peer when Bi-directional Forwarding Detection (BFD) is not enabled or is down.

The value of tmnxMcPeerMobileHoldDownTmr specifies the amount of time the node will not announce any routes for loopback interfaces.

The value of tmnxMcPeerMobileAdminState specifies the administrative status of the mobile redundancy protocol with the multi-chassis peer.

The value of tmnxMcPeerMobileLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcPeerMobileMtu indicates the Maximum Transmission Unit (MTU) of the Internet Protocol (IP) layer between the mobile gateways participating in geo-redundancy.

The value of tmnxMcPeerMobileMGTableLstChgd indicates the sysUpTime at the time of the last change of an entry in the tmnxMcPeerMobileMGTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcPeerMobileMGTable has entries of mobile-gateways that participate in the geo-redundancy.

Each row entry represents a mobile-gateway which is configured to participate in the geo-redundancy. Entries are create/deleted by the user.

The value of tmnxMcPeerMobileMGRowStatus is used for creation/deletion of multi-chassis peer mobile-gateway entries. In order for the row creation to succeed, values for tmnxMcPeerIpType, tmnxMcPeerIpAddr, tmnxMcPeerMobileMGId and tmnxMcPeerMobileMGRole must be included in the same SNMP SET PDU as tmnxMcPeerMobileRowStatus. Otherwise, the SET request will fail with an 'inconsistentValue' error.

The value of tmnxMcPeerMobileMGId specifies the gateway-id of the mobile-gateway that will participate in the multi-chassis configuration.

The value of tmnxMcPeerMobileMGRole specifies the role of the mobile-gateway that will participate in the multi-chassis configuration. Enumeration: 'primary': 1, 'secondary': 2.

The value of tmnxMcPeerMobileMGRefPtTrigger specifies whether the local node to wait for any or all reference points to pass their respective packet-count thresholds before performing a redundancy action. Enumeration: 'all': 1, 'any': 2.

The value of tmnxMcPeerMobileMGAdminState specifies the administrative status of the mobile gateway, participating in the mobile redundancy protocol, with the multi-chassis peer.

The value of tmnxMcPeerMobileMGLastChanged indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The value of tmnxMcPeerMobMGRefPtTableLstChgd indicates the sysUpTime at the time of the last change of an entry in the tmnxMcPeerMobileMGRefPtTable. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The tmnxMcPeerMobileMGRefPtTable has an entry for each reference point of the mobile gateway participating in the geo-redundancy.

Each row entry represents a threshold packet count associated with each reference-point of a mobile-gateway, which is configured to participate in the geo-redundancy. Entries are create/deleted by the user.

The value of tmnxMcPeerMobileMGRefPtRowStatus is used for creation/deletion of reference point entries for mobile-gateways participating in geo-redundancy.

The value of tmnxMcPeerMobileMGRefPt specifies the reference-point of the mobile-gateway participating in the geo-redundancy for which the packet count threshold is configured. Enumeration: 's5s8': 3, 's11': 1, 's1': 2.

The value of tmnxMcPeerMobileMGRefPtPktCnt specifies the minimum number of packets that must be received before the local node performs a redundancy action.

The value of tmnxMcPeerMobileMGRefPtLastChngd indicates the sysUpTime at the time of the last change of this entry. If no changes occurred since the last re-initialization of the local network management subsystem, then this object contains a zero value.

The notification tmnxMcRedundancyPeerStateChanged is sent when the connection to a specific peer is lost or established.

The notification tmnxMcRedundancyMismatchDetected is sent when a configuration mismatch is detected.

The notification tmnxMcRedundancyMismatchResolved is sent when all configuration mismatches are resolved.

The notification tmnxMcPeerSyncStatusChanged is generated when the status of the synchronization with the multi-chassis peer changes.

The notification tmnxMcSyncClientAlarmRaised is generated when a multi-chassis sync client has atleast one locally deleted entry in the database.

The notification tmnxMcSyncClientAlarmCleared is generated when a multi-chassis sync client has no locally deleted entries in the database.

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.

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.

The notification tmnxSrrpInstanceIdMismatch is generated when any one of the SAPs SRRP is backing up is backed by a different SRRP instance on the remote peer.

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.

The notification tmnxSrrpSapTagMismatch is generated when the tag for a local SAP do not match those of the remote SAP.

The notification tmnxSrrpRedIfMismatch is generated when the local and remote redundant interfaces are not properly paired.

The notification tmnxSrrpDualMaster is generated when both the local and remote SRRP instances are in the master state.

The notification tmnxMcLagInfoLagChanged is generated when entries in tmnxMcLagInfoLagTable were changed.

The notification tmnxSrrpSystemIpNotSet is generated when SRRP tries to send out advertisement packets but the system IP address has not yet been set.

The notification tmnxMcRingOperStateChanged is generated when the operational state of a multi-chassis ring changes.

The notification tmnxMcRingInbCtrlOperStateChgd is generated when the operational state of a multi-chassis ring's inband control connection changes.

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.

The notification tmnxMcSyncClockSkewRaised is generated when the MCS peer system clock time is greater than 60 seconds different than the local system clock.

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.

The notification tmnxSrrpDuplicateSubIfAddress is generated when the IP address for a local subscriber interface conflicts with the IP address for a remote subscriber interface.

The notification tmnxMcPeerRingsOperStateChanged is sent when the operational state - with respect to multi-chassis ring operation - of a peer changes.

The tmnxSrrpTrapNewMaster trap indicates that the sending multi-chassis SRRP instance has transitioned to 'Master' state.

The tmnxSrrpBecameBackup trap is generated when the sending multi-chassis SRRP instance has transitioned to 'Backup' state.

The notification tmnxSrrpBfdIntfSessStateChgd is generated when the operational state of BFD session of the SRRP instance changes.

The tmnxMcPeerEPBfdSessionOpen notification is generated when the multi-chassis endpoint is attempting to open BFD session to the mutli-chassis endpoint peer.

The tmnxMcPeerEPBfdSessionClose notification is generated when the multi-chassis endpoint is closing BFD session to the multi-chassis endpoint peer.

The tmnxMcPeerEPBfdSessionUp notification is generated when operational state of the BFD session between the multi-chassis endpoint and its peer is changed to 'up'.

The tmnxMcPeerEPBfdSessionDown notification is generated when operational state of the BFD session between the multi-chassis endpoint and its peer is changed to 'down'.

The tmnxMcPeerEPOperDown notification is generated when the multi-chassis endpoint detects time-out communicating with the multi-chassis endpoint peer.

The tmnxMcPeerEPOperUp notification is generated when the multi-chassis endpoint clears time-out condition in communicating with the multi-chassis endpoint peer.

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.

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.

[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.