CISCO-OPTICAL-IF-CROSS-CONNECT-MIB Table View

This table lists all interfaces that are cross-connected
to one or more other interfaces.  The table is used to find
cross-connects that include a particular interface.

coifccInterfaceEntry row .1.3.6.1.4.1.9.10.68.1.1.1.1

An entry is created only when an interface is cross-connected
to one or more other interfaces (i.e. when the associated
entries in the coifccCrossConnectTable have been created).

An entry is deleted when an…

Indexes

IF-MIBifIndex

Column	Syntax	OID
coifccIfCrossConnectIdentifier The value of coifccCcIndex used in the coifccCrossConnectTable to identify a cross-connect that includes this interface. Each interface included in that cross-connect has an entry in this table with the same value of t…	Integer32 Constraints: range: 1-2147483547	.1.3.6.1.4.1.9.10.68.1.1.1.1.1

This table contains configuration and state information of
point-to-point and point-to-multipoint interface
cross-connects.
          
Each entry in the table models two bi-directional interfaces on
opposite sides of a bi-directional cross-connect.
          
For a point-to-point cross-connect, there can be up to four
entries in the table with the same value of coifccCcIndex, due
to the presence of protection interfaces.  
All four entries are associated with each other due to
APS configuration (for now, this would be done through
the CISCO-APS-MIB). If both sides A and B are configured
for 1+1 APS protection, and a cross-connect between
interfaces A and B is created, then the following
cross-connect entries will be present:
          
The cross-connect with coifccCcKind value 'provisioned' is the
one that is created through cross-connect configuration and the
cross-connects with coifccCcKind value 'protection' are those
that are created automatically due to APS configuration.
          
Low interface    High interface        coifccCcKind
          
A                B                     provisioned
A                B'                    protection
A'               B                     protection
A'               B'                    protection
          
When the cross-connect between A and B is deleted, all four
cross-connect entries will disappear.
          
Each side of the point-to-point cross-connect can have up to
two interfaces, for example when SONET 1+1 Automatic
Protection Switching (APS) is used.  Any one of the four
entries of a point-to-point cross-connect can be created,
and the remaining three entries will be created
automatically. However only the 'provisioned' entry can be
explicitly deleted, which also causes the corresponding
'protection' entries to be deleted.  Note that use of the
word 'protection' is different from its usage in SONET 1+1 APS.
In particular, there is no requirement that the 'provisioned'
cross-connect must be between the SONET 'working' interfaces.
          
          
A point-to-multipoint connection consists of one root and
many leaves.  Copies of the traffic received at the root
interface are transmitted out each of the leaf interfaces.
          
For a point-to-multipoint cross-connect with N leafs,
the manager creates N 'provisioned' entries in this table.
Where N is determined by the manager based on some application.
In the presence of  APS configuration, the same
point-to-multipoint (N leafs) cross-connect, in addition
to having N 'provisioned' entries in this table, can have upto
an additional 3N 'protection' entries automatically configured.
          
The terms low and high are chosen to represent numerical
ordering of the two interfaces associated with a cross-connect.
That is, the interface with the lower value of ifIndex is
termed 'low', while the other interface associated with the
cross-connect is termed 'high'.  This terminology is used to
provide directional information; for example, the
coifccCcL2HOperStatus applies to the low->high direction, and
coifccCcH2LOperStatus applies to the high->low direction.

coifccCrossConnectEntry row .1.3.6.1.4.1.9.10.68.1.2.3.1

This entry is used to model two bi-directional cross-connected
interfaces.

Cross-connects can be created through provisioning,
automatically by the network element, dynamically by using
control protocols (e…

Indexes

coifccCcIndex coifccCcLowIfIndex coifccCcHighIfIndex

Column	Syntax	OID
coifccCcIndex A unique value used to identify this cross-connect. For each interface associated with this cross-connect, the agent reports this cross-connect index value in the coifccIfCrossConnectIdentifier object of the correspond…	Integer32 Constraints: range: 1-2147483647	.1.3.6.1.4.1.9.10.68.1.2.3.1.1
coifccCcLowIfIndex The value of this object is equal to MIB II's ifIndex value of the interface for this cross-connect. The term low implies that this interface has the numerically lower ifIndex value than the other interface identified …	IF-MIBInterfaceIndex Type Constraints: range: 1..2147483647 Description: A unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must …	.1.3.6.1.4.1.9.10.68.1.2.3.1.2
coifccCcHighIfIndex The value of this object is equal to MIB II's ifIndex value of the interface for this cross-connect. The term high implies that this interface has the numerically higher ifIndex value than the other interface identifie…	IF-MIBInterfaceIndex Type Constraints: range: 1..2147483647 Description: A unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must …	.1.3.6.1.4.1.9.10.68.1.2.3.1.3
coifccCcSwitchType This object specifies the type of switching element used to implement this cross-connect. The value 'opticalCrossConnect' applies only when there is no optical-to-electrical conversion performed to implem…	Enumerationr/w Enumerated Values: 1 unknown 2 electricalCrossConnect 3 opticalCrossConnect 4 autoSelect	.1.3.6.1.4.1.9.10.68.1.2.3.1.4
coifccCcKind The type of call control used to establish a cross-connect. If no value of this object is provided when a row is activated through SNMP, then the value 'provisioned' is assigned by the agent. …	Enumerationr/w Enumerated Values: 1 provisioned 2 automatic 3 dynamic 4 protection 5 other	.1.3.6.1.4.1.9.10.68.1.2.3.1.5
coifccCcCreationTime The value of MIB II's sysUpTime object at the time this bi-directional cross-connect was created. If the current state was entered prior to the last re-initialization of the agent then this object contains a zero value.	SNMPv2-TCTimeStamp Based On: SNMPv2-SMITimeTicks Description: The value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset t…	.1.3.6.1.4.1.9.10.68.1.2.3.1.6
coifccCcL2HOperStatus The operational status of the cross-connect in the direction from the interface that has the numerically lower ifIndex value, to the interface that has the numerically higher ifIndex value.	CoifccCrossConnectOperStatus Type Values: 1 up 2 down 3 dormant 4 unknown	.1.3.6.1.4.1.9.10.68.1.2.3.1.7
coifccCcH2LOperStatus The operational status of the cross-connect in the direction from the interface that has the numerically higher ifIndex value, to the interface that has the numerically lower ifIndex value.	CoifccCrossConnectOperStatus Type Values: 1 up 2 down 3 dormant 4 unknown	.1.3.6.1.4.1.9.10.68.1.2.3.1.8
coifccCcL2HLastChange The value of MIB II's sysUpTime at the time this cross-connect entered its current operational state in the low to high direction. If the current state was entered prior to the last re-initialization of the agent then …	SNMPv2-TCTimeStamp Based On: SNMPv2-SMITimeTicks Description: The value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset t…	.1.3.6.1.4.1.9.10.68.1.2.3.1.9
coifccCcH2LLastChange The value of MIB II's sysUpTime at the time this cross-connect entered its current operational state in the high to low direction. If the current state was entered prior to the last re-initialization of the agent then …	SNMPv2-TCTimeStamp Based On: SNMPv2-SMITimeTicks Description: The value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset t…	.1.3.6.1.4.1.9.10.68.1.2.3.1.10
coifccCcRowStatus The status of this entry in the coifccCrossConnectTable. This object is used to create a cross-connect or to modify or delete an existing cross-connect. Write access does not apply to entries with coifcc…	SNMPv2-TCRowStatusr/w Type Values: 1 active 2 notInService 3 notReady 4 createAndGo 5 createAndWait 6 destroy Description: The RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of …	.1.3.6.1.4.1.9.10.68.1.2.3.1.11
coifccCcL2HAttenuation The value of this object indicates optical signal attenuation due to connectors, optical wavelength filters, optical switches, and other optical components, in the direction from the interface that has the numerically l…	1/10ths of dBInteger32r/w Constraints: range: -400-0	.1.3.6.1.4.1.9.10.68.1.2.3.1.12
coifccCcH2LAttenuation The value of this object indicates optical signal attenuation due to connectors, optical wavelength filters, optical switches, and other optical components, in the direction from the interface that has the numerically h…	1/10ths of dBInteger32r/w Constraints: range: -400-0	.1.3.6.1.4.1.9.10.68.1.2.3.1.13