TIMETRA-CHASSIS-INTERCONNECT-MIB
This document is the SNMP MIB module for the Nokia SROS implementation
for managing the components used in connecting chassis together.
Copyright 2013-2018 Nokia. All rights reserved. Reproduction of this
document is authorized on the condition that the foregoing copyright
notice is included.
This SNMP MIB module (Specification) embodies Nokia's
proprietary intellectual property. Nokia retains all
title and ownership in the Specification, including any
revisions.
Nokia grants all interested parties a non-exclusive license to use and
distribute an unmodified copy of this Specification in connection with
management of Nokia products, and without fee, provided this copyright
notice and license appear on all copies.
This Specification is supplied `as is', and Nokia makes no warranty,
either express or implied, as to the use, operation, condition, or
performance of the Specification.
- Source file
TIMETRA-CHASSIS-INTERCONNECT-MIB- Last revised
- Identity
timetraChassisInterconMIBModule- Base OID
1.3.6.1.4.1.6527.1.1.3.94
Imported Objects
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | RowStatus TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue |
| TIMETRA-CHASSIS-MIB | tmnxChassisIndex tmnxChassisNotifyCpmCardSlotNum tmnxChassisNotifyFabricSlotNum tmnxCpmCardSlotNum tmnxFabricSlotNum tmnxHwClass |
| TIMETRA-GLOBAL-MIB | timetraSRMIBModules tmnxSRConfs tmnxSRNotifyPrefix tmnxSRObjs |
| TIMETRA-PORT-MIB | tmnxDDMFailedObject (no object page) tmnxDDMLaneIdOrModule (no object page) TmnxSFFStatus |
| TIMETRA-TC-MIB | TmnxAdminState TmnxPortID |
Net-SNMP examples using the nokia MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'TIMETRA-CHASSIS-INTERCONNECT-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-CHASSIS-INTERCONNECT-MIB::timetraChassisInterconMIBModule'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TIMETRA-CHASSIS-INTERCONNECT-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-CHASSIS-INTERCONNECT-MIB::timetraChassisInterconMIBModule'
Objects (42)
Showing 42 of 42 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.6527.1.1.3.94 |
||
.1.3.6.1.4.1.6527.3.1.1.94 |
||
.1.3.6.1.4.1.6527.3.1.1.94.1 |
||
.1.3.6.1.4.1.6527.3.1.1.94.2 |
||
.1.3.6.1.4.1.6527.3.1.1.94.2.1 |
||
.1.3.6.1.4.1.6527.3.1.1.94.2.2 |
||
.1.3.6.1.4.1.6527.3.1.1.94.2.3 |
||
.1.3.6.1.4.1.6527.3.1.2.94 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1.1 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1.1.1 |
||
|
Unsigned32
|
.1.3.6.1.4.1.6527.3.1.2.94.1.1.1.1 |
|
.1.3.6.1.4.1.6527.3.1.2.94.1.1.1.2 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1.1.1.3 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1.1.1.4 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1.2 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1.2.1 |
||
|
Unsigned32
|
.1.3.6.1.4.1.6527.3.1.2.94.1.2.1.1 |
|
.1.3.6.1.4.1.6527.3.1.2.94.1.2.1.2 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1.2.1.3 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1.2.1.4 |
||
|
Enumeration
|
.1.3.6.1.4.1.6527.3.1.2.94.1.2.1.5 |
|
.1.3.6.1.4.1.6527.3.1.2.94.1.2.1.6 |
||
.1.3.6.1.4.1.6527.3.1.2.94.1.2.1.7 |
||
.1.3.6.1.4.1.6527.3.1.2.94.2 |
||
.1.3.6.1.4.1.6527.3.1.2.94.2.1 |
||
.1.3.6.1.4.1.6527.3.1.2.94.3 |
||
|
|
.1.3.6.1.4.1.6527.3.1.2.94.3.1 |
|
|
|
.1.3.6.1.4.1.6527.3.1.2.94.3.2 |
|
|
|
.1.3.6.1.4.1.6527.3.1.2.94.3.2.1 |
|
|
|
Unsigned32
|
.1.3.6.1.4.1.6527.3.1.2.94.3.2.1.1 |
|
|
.1.3.6.1.4.1.6527.3.1.2.94.3.2.1.2 |
|
|
|
.1.3.6.1.4.1.6527.3.1.2.94.3.2.1.3 |
|
|
|
.1.3.6.1.4.1.6527.3.1.2.94.3.2.1.4 |
|
|
|
.1.3.6.1.4.1.6527.3.1.2.94.3.2.1.5 |
|
|
|
.1.3.6.1.4.1.6527.3.1.2.94.3.2.1.6 |
|
|
|
.1.3.6.1.4.1.6527.3.1.2.94.3.2.1.7 |
|
.1.3.6.1.4.1.6527.3.1.3.94 |
||
.1.3.6.1.4.1.6527.3.1.3.94.0 |
||
.1.3.6.1.4.1.6527.3.1.3.94.0.1 |
||
.1.3.6.1.4.1.6527.3.1.3.94.0.2 |
||
.1.3.6.1.4.1.6527.3.1.3.94.0.3 |
Dependencies (14) 7 direct · 7 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- SNMPv2-CONFrfc
- SNMPv2-TCrfc
- SNMP-FRAMEWORK-MIBrfc
- TIMETRA-GLOBAL-MIBnokia
- INET-ADDRESS-MIBrfc
- TIMETRA-TC-MIBnokia
- TIMETRA-CHASSIS-MIBnokia
- ATM-TC-MIBrfc
- IANAifType-MIBrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- IEEE8021-PAE-MIBrfc
- TIMETRA-PORT-MIBnokia
- TIMETRA-CHASSIS-INTERCONNECT-MIBnokiaselected
Type Definitions (2)
| Enumeration |
up(1)invalidConnection(2)noLink(3)indeterminate(4) |
|
| Enumeration |
up(1)invalidConnection(2)noLink(3)indeterminate(4)unsupportedSff(5) |
Conformance Groups (8)
|
The group of notifications supporting the interconnect capabilities
for the chassis on Nokia SROS series systems in release 12.0. |
.1.3.6.1.4.1.6527.3.1.1.94.2.1.1
|
|
|
The group of notification-objects supporting the interconnect
capabilities for the chassis on release 12.0 of Nokia SROS series systems. |
.1.3.6.1.4.1.6527.3.1.1.94.2.1.2
|
|
|
The group of objects supporting the interconnect port capabilities for
the control plane on Nokia SROS series systems in release 12.0. |
.1.3.6.1.4.1.6527.3.1.1.94.2.1.3
|
|
|
tmnxCpmIcPortDown tmnxCpmIcPortUp tmnxCpmIcPortSFFInserted tmnxCpmIcPortSFFRemoved tmnxCpmNoLocalIcPort tmnxCpmLocalIcPortAvail tmnxCpmIcPortSFFStatusFailure tmnxCpmIcPortDDMFailure tmnxCpmIcPortDDMClear
The group of notifications supporting the interconnect port
capabilities for the control plane on Nokia SROS series systems in release 12.0. |
.1.3.6.1.4.1.6527.3.1.1.94.2.1.4
|
|
|
tmnxSfmIcPortOperState tmnxSfmIcPortSFFEquipped tmnxSfmIcPortSFFStatus tmnxSfmIcPortDegradeState tmnxSfmIcPortMisconSfm tmnxSfmIcPortMisconSfmIcPort
The group of objects supporting the interconnect port capabilities for
the switch fabric on Nokia SROS series systems in release 12.0. |
.1.3.6.1.4.1.6527.3.1.1.94.2.1.5
|
|
|
tmnxSfmIcPortDown tmnxSfmIcPortUp tmnxSfmIcPortSFFInserted tmnxSfmIcPortSFFRemoved tmnxSfmIcPortSFFStatusFailure tmnxSfmIcPortDDMFailure tmnxSfmIcPortDDMClear tmnxSfmIcPortDegraded tmnxSfmIcPortDegradedClear
The group of notifications supporting the interconnect port
capabilities for the switch fabric on Nokia SROS series systems in release 12.0. |
.1.3.6.1.4.1.6527.3.1.1.94.2.1.6
|
|
|
tmnxInterChassisLinkV16v0Group
obsolete
|
tmnxICLTableLastChange tmnxICLRowStatus tmnxICLLastChanged tmnxICLAdminState tmnxICLPrimaryChassisPortId tmnxICLSecondaryChassisPortId tmnxICLOperState
The group of objects supporting the Inter-chassis Link capabilities on
Nokia SROS series systems in release 16.0. |
.1.3.6.1.4.1.6527.3.1.1.94.2.2.1
|
|
tmnxICLTableLastChange tmnxICLRowStatus tmnxICLLastChanged tmnxICLAdminState tmnxICLPrimaryChassisPortId tmnxICLSecondaryChassisPortId tmnxICLOperState
The group of objects supporting the Inter-chassis Link capabilities
that were obsoleted on Nokia SROS series systems in release 20.0. |
.1.3.6.1.4.1.6527.3.1.1.94.2.3.1
|
Compliance Statements (2)
OID
.1.3.6.1.4.1.6527.3.1.1.94.1.1The compliance statement for the management of chassis interconnect
capabilities on SROS series systems for release 12.0.
capabilities on SROS series systems for release 12.0.
Required groups
| mandatory | tmnxChassIcNotifV12v0Group | |
| mandatory | tmnxChassIcNotifyObjsV12v0Group | |
| mandatory | tmnxCpmIcPortV12v0Group | |
| mandatory | tmnxCpmIcPortNotifV12v0Group | |
| mandatory | tmnxSfmIcPortV12v0Group | |
| mandatory | tmnxSfmIcPortNotifV12v0Group |
OID
.1.3.6.1.4.1.6527.3.1.1.94.1.2The compliance statement for the management of chassis interconnect
capabilities on SROS series systems for release 16.0.
capabilities on SROS series systems for release 16.0.
Required groups
| mandatory | tmnxInterChassisLinkV16v0Group |
Notifications / Traps (20)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.6527.3.1.3.94.0.1.1 |
[CAUSE] The tmnxInterChassisCommsDown alarm is generated when the
active CPM cannot reach the far-end chassis. [EFFECT] The resources on the far-end chassis are not available. This event for the far-end chassis means that the CPM, SFM, and XCM cards in the far-end chassis will reboot and remain operationally down until communications are re-established. [RECOVERY] Ensure that all CPM interconnect ports in the system are properly cabled together with working cables. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.1.2 |
[CAUSE] The tmnxInterChassisCommsUp notification is generated when the
control communications are re-established between the active CPM and the far-end chassis. [EFFECT] The resources on the far-end chassis are now available. This event for the far-end chassis means that the CPM, SFM and XCM cards in the far-end chassis will start the process of coming back into service. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.2.1 |
[CAUSE] The tmnxCpmIcPortDown alarm is generated when the CPM
interconnect port is not operational. The reason may be a cable connected incorrectly, a disconnected cable, a faulty cable, or a misbehaving CPM interconnect port or card. [EFFECT] At least one of the control plane paths used for inter-chassis CPM communication is not operational. Other paths may be available. [RECOVERY] A manual verification and testing of each CPM interconnect port is required to ensure fully functional operation. Physical replacement of cabling may be required. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.2.2 |
[CAUSE] The tmnxCpmIcPortUp notification is generated when the CPM
interconnect port is operational again. [EFFECT] A control plane communication path between CPM cards in the different chassis have been established. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.2.3 |
[CAUSE] The tmnxCpmIcPortSFFInserted notification is generated when
the small form factor (SFF) pluggable optical module (e.g. QSFP) is inserted into a CPM interconnect port. [EFFECT] This event is for notification only. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.2.4 |
[CAUSE] The tmnxCpmIcPortSFFRemoved notification is generated when the
SFF (e.g. QSFP) is removed from the CPM interconnect port. Removing an SFF causes both this trap, and also a tmnxCpmIcPortDown event. [EFFECT] Removing the SFF will cause the CPM interconnect port to go down. This port will no longer be able to be used as part of the control plane between chassis but other paths may be available. [RECOVERY] Insert a working SFF into the port. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.2.5 |
[CAUSE] The tmnxCpmNoLocalIcPort alarm is generated when the CPM
cannot reach the other chassis using its local CPM interconnect ports. [EFFECT] Another control communications path may still be available between the CPM and the other chassis via the mate CPM in the same chassis. If that alternative path is not available then complete disruption of control communications to the other chassis will occur and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the active CPM indicates that a further failure of the local CPM interconnect ports on the standby CPM will cause complete disruption of control communications to the other chassis and the tmnxInterChassisCommsDown alarm is raised. A tmnxCpmNoLocalIcPort alarm on the standby CPM indicates that a CPM switchover may cause temporary disruption of control communications to the other chassis while the rebooting CPM comes back into service. [RECOVERY] Ensure that all CPM interconnect ports in the system are properly cabled together with working cables. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.2.6 |
[CAUSE] The tmnxCpmLocalIcPortAvail notification is generated when the
CPM re-establishes communication with the other chassis using its local CPM interconnect ports. [EFFECT] A new control communications path is now available between the CPM and the other chassis. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.2.7 |
[CAUSE] The tmnxCpmIcPortSFFStatusFailure notification is generated
when the value of tmnxCpmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. [EFFECT] The SFF device is not operational and the associated CPM interconnect port can not be used. The SFF and port will not recover without operator intervention. [RECOVERY] Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
|
|
TIMETRA-CHASSIS-MIBtmnxChassisNotifyCpmCardSlotNum tmnxNotifyIcPortNum TIMETRA-PORT-MIB::tmnxDDMFailedObject (unresolved reference) TIMETRA-PORT-MIB::tmnxDDMLaneIdOrModule (unresolved reference)
|
.1.3.6.1.4.1.6527.3.1.3.94.0.2.8 |
[CAUSE] The tmnxCpmIcPortDDMFailure notification is generated when an
SFF in a CPM interconnect port that supports Digital Diagnostic Monitoring (DDM) enters a failed state. |
|
TIMETRA-CHASSIS-MIBtmnxChassisNotifyCpmCardSlotNum tmnxNotifyIcPortNum TIMETRA-PORT-MIB::tmnxDDMFailedObject (unresolved reference) TIMETRA-PORT-MIB::tmnxDDMLaneIdOrModule (unresolved reference)
|
.1.3.6.1.4.1.6527.3.1.3.94.0.2.9 |
[CAUSE] The tmnxCpmIcPortDDMFailure notification is generated when an
SFF in a CPM interconnect port that supports Digital Diagnostic Monitoring (DDM) clears a failed state. |
.1.3.6.1.4.1.6527.3.1.3.94.0.3.1 |
[CAUSE] The tmnxSfmIcPortDown alarm is generated when the SFM
interconnect port is not operational. The reason may be a cable connected incorrectly, a disconnected cable, a faulty cable, or a misbehaving SFM interconnect port or SFM card. [EFFECT] This port can no longer be used as part of the user plane fabric between chassis. Other fabric paths may be available resulting in no loss of capacity. [RECOVERY] A manual verification and testing of each SFM interconnect port is required to ensure fully functional operation. Physical replacement of cabling may be required. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.3.2 |
[CAUSE] The tmnxSfmIcPortUp notification is generated when the SFM
interconnect port is operational again. [EFFECT] This port can now be used as part of the user plane fabric between chassis. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.3.3 |
[CAUSE] The tmnxSfmIcPortSFFInserted notification is generated when
the Small Form Factor (SFF) pluggable optical module (e.g. CXP) is inserted into an SFM interconnect port. [EFFECT] This event is for notification only. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.3.4 |
[CAUSE] The tmnxSfmIcPortSFFRemoved notification is generated when the
SFF (e.g. CXP) is removed from the SFM interconnect port. [EFFECT] Removing the module will cause the port to go down. This port can no longer be used as part of the user plane fabric between chassis. Other fabric paths may be available resulting in no loss of capacity. [RECOVERY] Insert a working SFF into the SFM interconnect port. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.3.5 |
[CAUSE] The tmnxSfmIcPortSFFStatusFailure notification is generated
when the value of tmnxSfmIcPortSFFStatus results in a value other than 'not-equipped (0)', or 'operational (1)'. [EFFECT] The SFF device is not operational and the associated SFM interconnect port can not be used. The SFF and port will not recover without operator intervention. [RECOVERY] Remove and re-insert the SFF device. If the problem persists then replace the SFF device. |
|
|
TIMETRA-CHASSIS-MIBtmnxChassisNotifyFabricSlotNum tmnxNotifyIcPortNum TIMETRA-PORT-MIB::tmnxDDMFailedObject (unresolved reference) TIMETRA-PORT-MIB::tmnxDDMLaneIdOrModule (unresolved reference)
|
.1.3.6.1.4.1.6527.3.1.3.94.0.3.6 |
[CAUSE] The tmnxSfmIcPortDDMFailure notification is generated when an
SFF in an SFM interconnect port that supports Digital Diagnostic Monitoring (DDM) enters a failed state. |
|
TIMETRA-CHASSIS-MIBtmnxChassisNotifyFabricSlotNum tmnxNotifyIcPortNum TIMETRA-PORT-MIB::tmnxDDMFailedObject (unresolved reference) TIMETRA-PORT-MIB::tmnxDDMLaneIdOrModule (unresolved reference)
|
.1.3.6.1.4.1.6527.3.1.3.94.0.3.7 |
[CAUSE] The tmnxSfmIcPortDDMFailure notification is generated when an
SFF in an SFM interconnect port that supports Digital Diagnostic Monitoring (DDM) clears a failed state. |
.1.3.6.1.4.1.6527.3.1.3.94.0.3.8 |
[CAUSE] The tmnxSfmIcPortDegraded notification is generated when the
system has detected a degradation of the switch fabric that is associated with a particular SFM interconnect port. The value of tmnxSfmIcPortDegradeState will reflect this condition by having a value that is NOT 'none (1)'. If the value of tmnxSfmIcPortDegradeState is 'degraded (2)' the SFM interconnect port can still carry some traffic but not at the full capacity of the port. The port and attached cable are not necessarily the cause of the degradation but are a likely cause. [EFFECT] Switch fabric capacity on this port is reduced when tmnxSfmIcPortDegradeState is degraded. This may not be causing any impact to service because of redundancy in the fabric. [RECOVERY] Although it may not be necessary to maintain full service, replacing the affected components may restore some fabric capacity. |
|
.1.3.6.1.4.1.6527.3.1.3.94.0.3.9 |
[CAUSE] The tmnxSfmIcPortDegradedClear notification is generated when
the switch fabric associated with the SFM interconnect port is not degraded. This occurs when the value of tmnxSfmIcPortDegradeState is 'none (1)'. |