CISCO-OPTICAL-IF-CROSS-CONNECT-MIB

        This MIB module is used to create and monitor cross-connects
(horizontal relationships) between peer interfaces on the same
network element.  Vertical relationships (e.g. between lambdas
and the optical fiber in which the lambdas are carried) are
represented in the ifStackTable from the IF-MIB.
        
This MIB can be used to model various types of cross-connects
between peer interfaces, including time-division (e.g.
SDH/SONET, PDH), wavelength (lambda), and spatial switching
(e.g. incoming port or fiber to outgoing port or fiber).
        
This MIB does not apply to cross-connects between packet flows
(e.g. packets in the same forwarding equivalence class at a
MPLS-capable switch or router) or cell flows (e.g. ATM Virtual
Path connections or ATM Virtual Channel connections), since
there are scalability issues in modeling each packet flow or
cell flow as a logical interface.
        
The switching element performing the cross-connect function can
be electrical (e.g. SDH/SONET switch) or optical (e.g. passive
optical add/drop multiplexer)
        
Cross-connects can be created through provisioning,
automatically by the network element, or dynamically by using
control protocols (e.g. GMPLS).
        
The cross-connect model includes support for pairs of
interfaces used to protect each other (e.g. SONET 1+1
Automatic Protection Switching).  Cross-connects to protection
interfaces may be shown in this MIB module.
    
Source file
CISCO-OPTICAL-IF-CROSS-CONNECT-MIB
Last revised
Identity
ciscoOpticalIfCrossConnectMIB
Base OID
1.3.6.1.4.1.9.10.68
Imported Objects
CISCO-SMI ciscoExperiment
IF-MIB ifIndex InterfaceIndex
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC RowStatus TEXTUAL-CONVENTION (no object page) TimeStamp
Net-SNMP examples using the cisco 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 'CISCO-OPTICAL-IF-CROSS-CONNECT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-OPTICAL-IF-CROSS-CONNECT-MIB::ciscoOpticalIfCrossConnectMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-OPTICAL-IF-CROSS-CONNECT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-OPTICAL-IF-CROSS-CONNECT-MIB::ciscoOpticalIfCrossConnectMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (27)
.1.3.6.1.4.1.9.10.68
.1.3.6.1.4.1.9.10.68.1
.1.3.6.1.4.1.9.10.68.1.1
.1.3.6.1.4.1.9.10.68.1.1.1
.1.3.6.1.4.1.9.10.68.1.1.1.1
Integer32
.1.3.6.1.4.1.9.10.68.1.1.1.1.1
.1.3.6.1.4.1.9.10.68.1.2
Integer32
.1.3.6.1.4.1.9.10.68.1.2.1
.1.3.6.1.4.1.9.10.68.1.2.2
.1.3.6.1.4.1.9.10.68.1.2.3
.1.3.6.1.4.1.9.10.68.1.2.3.1
Integer32
.1.3.6.1.4.1.9.10.68.1.2.3.1.1
.1.3.6.1.4.1.9.10.68.1.2.3.1.10
.1.3.6.1.4.1.9.10.68.1.2.3.1.11
1/10ths of dBInteger32
.1.3.6.1.4.1.9.10.68.1.2.3.1.12
1/10ths of dBInteger32
.1.3.6.1.4.1.9.10.68.1.2.3.1.13
.1.3.6.1.4.1.9.10.68.1.2.3.1.2
.1.3.6.1.4.1.9.10.68.1.2.3.1.3
Enumeration
.1.3.6.1.4.1.9.10.68.1.2.3.1.4
Enumeration
.1.3.6.1.4.1.9.10.68.1.2.3.1.5
.1.3.6.1.4.1.9.10.68.1.2.3.1.6
.1.3.6.1.4.1.9.10.68.1.2.3.1.7
.1.3.6.1.4.1.9.10.68.1.2.3.1.8
.1.3.6.1.4.1.9.10.68.1.2.3.1.9
.1.3.6.1.4.1.9.10.68.2
.1.3.6.1.4.1.9.10.68.2.1
.1.3.6.1.4.1.9.10.68.2.2
Dependencies (7) 5 direct · 2 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
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. CISCO-OPTICAL-IF-CROSS-CONNECT-MIBciscoselected
Type Definitions (1)
Enumeration
up(1)
down(2)
dormant(3)
unknown(4)
Conformance Groups (3)
Object needed to implement Interfaces with
Cross-connects.
.1.3.6.1.4.1.9.10.68.2.2.1
Collection of objects needed to implement
interface Cross-connects.
.1.3.6.1.4.1.9.10.68.2.2.2
Collection of objects used to indicate attenuation
across optical cross-connects.
.1.3.6.1.4.1.9.10.68.2.2.3
Compliance Statements (2)

OID .1.3.6.1.4.1.9.10.68.2.1.1
The compliance statement for entities which implement
the Cisco Interface Cross-connect MIB
Required groups
Object refinements
ObjectAccessSyntaxDescription
coifccCcSwitchType readonly
Write access is not required.

OID .1.3.6.1.4.1.9.10.68.2.1.2
The compliance statement for entities which implement
the Cisco Interface Cross-connect MIB
Required groups
mandatory coifccInterfaceGroup
mandatory coifccCrossConnectGroup
optional coifccAttenuationGroup May be implemented by elements providing optical
cross-connects.
Object refinements
ObjectAccessSyntaxDescription
coifccCcSwitchType readonly
Write access is not required.
coifccCcKind readonly
Write access is not required.
coifccCcRowStatus readonly
Write access does not apply when the only supported value
of coifccCcKind is 'automatic', or when the only two
supported values are 'automatic' and 'protection'.
coifccCcL2HAttenuation readonly
Write access is not required.
coifccCcH2LAttenuation readonly
Write access is not required.