coifcc Cross Connect Entry

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.g. GMPLS), or due to the presence of protection interfaces. When creating an entry through provisioning, the following procedures are used to cross-connect two interfaces: (1) The manager obtains a unique coifccCcIndex by reading the coifccCcIndexNext object. (2) Next, the manager creates a set of one or more rows in the Cross Connect Table. For a point-to-point connection, one row is created by the manager. For a point-to-multipoint connection, one row is created for each leaf to an unprotected interface, or one row is created for each leaf to a pair of protected interfaces. Additional rows for protection interfaces are created automatically by the agent. Each row is indexed by the ifIndex values of the two interfaces at the ends of that cross-connection. This set of rows is identified by a single value of coifccCcIndex. As each row is created, the agent checks if the requested topology is supported and also checks for internal errors in building the cross-connect. The coifccIfCrossConnectIdentifier values in the corresponding coifccInterfaceTable rows are filled in by the agent at this point. The traffic flow is turned on when the manager sets coifccCcRowStatus to active(1) or createAndGo(4). A cross-connect identified by a particular value of coifccCcIndex is released by setting coifccCcRowStatus of all rows identified by this value of coifccCcIndex, other than the rows with a coifccCcKind value of 'protection', to destroy(6). The agent may release associated resources, and the coifccIfCrossConnectIdentifier values in the corresponding coifccInterfaceTable are removed. Note that a situation when only a subset of the associated rows are deleted corresponds to a topology change. At the discretion of the agent, a cross-connect may be reconfigured by adding and/or deleting leafs to/from the topology as per the cross-connect establishment/retirement guidelines described below. Each leaf is added by creating a row with the same value of coifccCcIndex in this table. Each leaf is deleted by deleting a row with the same value of coifccCcIndex in the table. To delete an entire point-to-multipoint connection, all entries with the same coifccCcIndex value must be deleted.