Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Provisioning Transponding and Muxponding Cross-Connects

    Supported Cross-Connects

    Cross-connects can be created between interfaces within the same UFM (unless otherwise noted). Depending on what you are cross-connecting, you can be regenerating, transponding, or muxponding.

    The following table lists the cross-connects that are supported:

    Note: The A and B designations in the tables below are used only to distinguish between the two cross-connect endpoints. They are assigned arbitrarily and are interchangeable.

    Note: When cross-connecting two 10-Gbps interfaces on a UFM3 equipped with 12x SFP+ BICs, both interfaces must reside on the same BIC.

    Table 1: UFM Cross-Connects

    Description

    Interface A

    Interface B

    Supported UFMs

    Rate

    Regenerating

    10GbE to/from 10GbE

    10ge on any SFP+ transceiver

    10ge on any SFP+ transceiver

    UFM3

    UFM4

    10GbE

    OTU2 to/from OTU2

    odu2 on any SFP+ transceiver

    odu2 on any SFP+ transceiver

    UFM3

    UFM4

    ODU2

    OTU4 to/from OTU4

    odu4 on any CFP transceiver or on the 100G Coherent MSA XCVR

    odu4 on any CFP transceiver or on the 100G Coherent MSA XCVR

    UFM3

    UFM4

    ODU4

    Transponding

    10GbE to/from OTU2

    10ge on any SFP+ transceiver

    odu2 on any SFP+ transceiver

    UFM3

    UFM4

    ODU2

    SONET/SDH (OC-192/STM-64/10GbE WAN PHY) to/from OTU2

    oc192/stm64/wanoc192/wanstm64 on any SFP+ transceiver

    odu2 on any SFP+ transceiver

    UFM3

    UFM4

    ODU2

    100GbE to/from OTU4

    100ge on CFP transceivers, with the following exclusions:

    100ge is not supported on the 100G Coherent CFP transceiver or on the 100G Coherent MSA XCVR

    odu4 on any CFP transceiver or on the 100G Coherent MSA XCVR

    UFM3

    UFM4

    ODU4

    100GbE to/from OTU4

    100ge on QSFP28 transceivers

    odu4 on the 400G Coherent MSA XCVR

    UFM6

    ODU4

    See Table 2.

    Muxponding

    10GbE to/from OTU4

    10ge on any SFP+ transceiver

    odu2 on any CFP transceiver or on the 100G Coherent MSA XCVR

    UFM3

    UFM4

    ODU2

    10GbE to/from OTU4

    10ge on any QSFP+ transceiver

    odu2e on the 400G Coherent MSA XCVR

    UFM6

    ODU2e

    See Table 2.

    OTU2 to/from OTU4

    odu2 on any SFP+ transceiver

    odu2 on any CFP transceiver or on the 100G Coherent MSA XCVR

    UFM3

    UFM4

    ODU2

    OTU2e to/from OTU4

    odu2e on any SFP+ transceiver

    odu2e on any CFP transceiver

    UFM3

    ODU2e

    SONET/SDH (OC-192/STM-64/10GbE WAN PHY) to/from OTU4

    oc192/stm64/wanoc192/wanstm64 on any SFP+ transceiver

    odu2 on any CFP transceiver or on the 100G Coherent MSA XCVR

    UFM3

    UFM4

    ODU2

    Table 2: UFM6 Cross-Connect Mappings

    Description

    Interface A

    Interface B

    Transponding

    100GbE to/from OTU4

    100ge:chassis/slot/1/1

    odu4:chassis/slot/2/1/1.1.1

    100ge:chassis/slot/1/2

    odu4:chassis/slot/2/1/1.1.2

    100ge:chassis/slot/1/6

    odu4:chassis/slot/2/1/2.1.1

    100ge:chassis/slot/1/7

    odu4:chassis/slot/2/1/2.1.2

    Muxponding

    10GbE to/from OTU4

    10ge:chassis/slot/1/1/1

    odu2e:chassis/slot/2/1/1.1.1.1

    10ge:chassis/slot/1/1/2

    odu2e:chassis/slot/2/1/1.1.1.2

    10ge:chassis/slot/1/1/3

    odu2e:chassis/slot/2/1/1.1.1.3

    10ge:chassis/slot/1/1/4

    odu2e:chassis/slot/2/1/1.1.1.4

    10ge:chassis/slot/1/2/1

    odu2e:chassis/slot/2/1/1.1.1.5

    10ge:chassis/slot/1/2/2

    odu2e:chassis/slot/2/1/1.1.1.6

    10ge:chassis/slot/1/2/3

    odu2e:chassis/slot/2/1/1.1.1.7

    10ge:chassis/slot/1/2/4

    odu2e:chassis/slot/2/1/1.1.1.8

    10ge:chassis/slot/1/3/1

    odu2e:chassis/slot/2/1/1.1.1.9

    10ge:chassis/slot/1/3/2

    odu2e:chassis/slot/2/1/1.1.1.10

    10ge:chassis/slot/1/3/3

    odu2e:chassis/slot/2/1/1.1.2.1

    10ge:chassis/slot/1/3/4

    odu2e:chassis/slot/2/1/1.1.2.2

    10ge:chassis/slot/1/4/1

    odu2e:chassis/slot/2/1/1.1.2.3

    10ge:chassis/slot/1/4/2

    odu2e:chassis/slot/2/1/1.1.2.4

    10ge:chassis/slot/1/4/3

    odu2e:chassis/slot/2/1/1.1.2.5

    10ge:chassis/slot/1/4/4

    odu2e:chassis/slot/2/1/1.1.2.6

    10ge:chassis/slot/1/5/1

    odu2e:chassis/slot/2/1/1.1.2.7

    10ge:chassis/slot/1/5/2

    odu2e:chassis/slot/2/1/1.1.2.8

    10ge:chassis/slot/1/5/3

    odu2e:chassis/slot/2/1/1.1.2.9

    10ge:chassis/slot/1/5/4

    odu2e:chassis/slot/2/1/1.1.2.10

    10ge:chassis/slot/1/6/1

    odu2e:chassis/slot/2/1/2.1.1.1

    10ge:chassis/slot/1/6/2

    odu2e:chassis/slot/2/1/2.1.1.2

    10ge:chassis/slot/1/6/3

    odu2e:chassis/slot/2/1/2.1.1.3

    10ge:chassis/slot/1/6/4

    odu2e:chassis/slot/2/1/2.1.1.4

    10ge:chassis/slot/1/7/1

    odu2e:chassis/slot/2/1/2.1.1.5

    10ge:chassis/slot/1/7/2

    odu2e:chassis/slot/2/1/2.1.1.6

    10ge:chassis/slot/1/7/3

    odu2e:chassis/slot/2/1/2.1.1.7

    10ge:chassis/slot/1/7/4

    odu2e:chassis/slot/2/1/2.1.1.8

    10ge:chassis/slot/1/8/1

    odu2e:chassis/slot/2/1/2.1.1.9

    10ge:chassis/slot/1/8/2

    odu2e:chassis/slot/2/1/2.1.1.10

    10ge:chassis/slot/1/8/3

    odu2e:chassis/slot/2/1/2.1.2.1

    10ge:chassis/slot/1/8/4

    odu2e:chassis/slot/2/1/2.1.2.2

    10ge:chassis/slot/1/9/1

    odu2e:chassis/slot/2/1/2.1.2.3

    10ge:chassis/slot/1/9/2

    odu2e:chassis/slot/2/1/2.1.2.4

    10ge:chassis/slot/1/9/3

    odu2e:chassis/slot/2/1/2.1.2.5

    10ge:chassis/slot/1/9/4

    odu2e:chassis/slot/2/1/2.1.2.6

    10ge:chassis/slot/1/10/1

    odu2e:chassis/slot/2/1/2.1.2.7

    10ge:chassis/slot/1/10/2

    odu2e:chassis/slot/2/1/2.1.2.8

    10ge:chassis/slot/1/10/3

    odu2e:chassis/slot/2/1/2.1.2.9

    10ge:chassis/slot/1/10/4

    odu2e:chassis/slot/2/1/2.1.2.10

    Provisioning a Transponding Cross-Connect on a UFM3 or UFM4

    Use this procedure to provision a cross-connect that transponds between interfaces on the same UFM3 or UFM4. See Supported cross-connects for more information.

    1. Enter configuration mode.
      bti7800# config
      bti7800(config)#
    2. Create the interfaces to be cross-connected.

      See Provisioning a Transport Interface for information on creating transport interfaces. Ensure neither interface is configured for multiplexing.

      The following lists the interfaces created on the UFM in slot 7 (for example):

      bti7800(config)# do show interface | include 1/7
      Name                                    : 100ge:1/7/2/1   
      Name                                    : odu4:1/7/1/1   
      Name                                    : otu4:1/7/1/1 
    3. Configure the cross-connect.

      The following example cross-connects the 100-Gigabit Ethernet interface with the ODU4 interface:

      bti7800(config)# cross-connect 100ge:1/7/2/1 odu4:1/7/1/1
      bti7800(config-cross-connect-100ge:1/7/2/1/odu4:1/7/1/1)# 
    4. Optionally, specify the service name.

      For example:

      bti7800(config-cross-connect-100ge:1/7/2/1/odu4:1/7/1/1)# service-name circuit_17
    5. Apply the changes.
      bti7800(config-cross-connect-100ge:1/7/2/1/odu4:1/7/1/1)# commit
      Commit complete. 
    6. Optionally, show the resulting cross-connect.

      For example:

      bti7800(config-cross-connect-100ge:1/7/2/1/odu4:1/7/1/1)# do show cross-connect table | include circuit_17
      2   100ge:1/7/2/1   odu4:1/7/1/1     2way       odu4      circuit_17 

    Provisioning a Transponding Cross-Connect on a UFM6

    Use this procedure to provision a cross-connect that transponds between a 100-Gbps client interface and an OTU4 interface on a UFM6.

    1. Enter configuration mode.
      bti7800# config
      bti7800(config)#
    2. Create the interfaces to be cross-connected.

      See Provisioning a Transport Interface for information on creating transport interfaces.

      Note: The cross-connect mapping between the client 100-Gbps interface and line ODU4 interface is fixed and cannot be changed. Ensure that the interfaces you create conform to the required mapping. See Supported cross-connects for more information.

      1. Create the optical channel interface.

        The optical channel represents the attributes that must be the same for all contained OTU4 signals. The optical channel interface must exist before you can create an OTU4 interface.

      2. Create the line OTU4 interface. Configure the automatically created ODU4 interface as a non-multiplexed interface.
      3. Create the 100-Gbps interface.

      The following lists the interfaces created on the UFM6 in slot 5 (for example):

      bti7800(config)# do show interface | include 1/5
      Name                                    : 100ge:1/5/1/1   
      Name                                    : odu4:1/5/2/1/1.1.1   
      Name                                    : otu4:1/5/2/1/1.1.1   
      Name                                    : och:1/5/2/1/1.1 
    3. Configure the cross-connect.

      The following cross-connects the line ODU4 interface with the client 100-Gbps interface:

      bti7800(config)# cross-connect odu4:1/5/2/1/1.1.1 100ge:1/5/1/1
      bti7800(config-cross-connect-odu4:1/5/2/1/1.1.1 100ge:1/5/1/1)#  
    4. Optionally, specify the service name.

      For example:

      bti7800(config-cross-connect-odu4:1/5/2/1/1.1.1 100ge:1/5/1/1)# service-name circuit_2129
    5. Apply the changes.
      bti7800(config-cross-connect-odu4:1/5/2/1/1.1.1 100ge:1/5/1/1)# commit
      Commit complete. 
    6. Optionally, show the resulting cross-connect.

      For example:

      bti7800(config-cross-connect-odu4:1/5/2/1/1.1.1 100ge:1/5/1/1)# do show cross-connect table
      Cross-Connect  Source-Name         Destination-Name   Direction   Rate    Service-Name 
      -------------  -----------------   -----------------  ----------  ------  ------------- 
      1              odu4:1/5/2/1/1.1.1  100ge:1/5/1/1      2way        odu4    circuit_2129 

    Provisioning a Muxponding 10-Gbps-to-ODU2/ODU4 Cross-Connect

    Use this procedure to provision a cross-connect that muxponds between a 10-Gbps interface and an ODU2 interface within a higher-order ODU4 on the same UFM3 or UFM3. This procedure uses a 10-Gigabit Ethernet interface as an example, but the same procedure can be used for other 10-Gbps interfaces by specifying a different type of 10-Gbps interface. See Supported cross-connects for information about the cross-connects these modules support.

    1. Enter configuration mode.
      bti7800# config
      bti7800(config)#
    2. Create the interfaces to be cross-connected.

      See Provisioning a Transport Interface for information on creating transport interfaces.

      1. Create the OTU4 interface. Make sure the automatically created ODU4 interface is configured for multiplexing.
      2. Create the 10-Gbps interface. Make sure this interface is not configured for multiplexing.

      The following lists the interfaces created on the UFM in slot 7 (for example):

      bti7800(config)# do show interface | include 1/7
      Name                                    : 10ge:1/7/2/1   
      Name                                    : odu2:1/7/1/1.1   
      Name                                    : odu2:1/7/1/1.2   
      Name                                    : odu2:1/7/1/1.3   
      Name                                    : odu2:1/7/1/1.4   
      Name                                    : odu2:1/7/1/1.5   
      Name                                    : odu2:1/7/1/1.6   
      Name                                    : odu2:1/7/1/1.7   
      Name                                    : odu2:1/7/1/1.8   
      Name                                    : odu2:1/7/1/1.9   
      Name                                    : odu2:1/7/1/1.10   
      Name                                    : odu4:1/7/1/1   
      Name                                    : otu4:1/7/1/1 

      When you configure the odu4:1/7/1/1 interface for multiplexing, the system automatically creates 10 subinterfaces odu2:1/7/1/1.1 to odu2:1/7/1/1.10, and configures the odtg and tributary-slot-list attributes on the odu4:1/7/1/1 interface appropriately.

    3. Configure the cross-connect.

      The following example cross-connects the 10-Gbps interface with one of the subinterfaces on the ODU4:

      bti7800(config)# cross-connect 10ge:1/7/2/1 odu2:1/7/1/1.4
      bti7800(config-cross-connect-10ge:1/7/2/1/odu2:1/7/1/1.4)#  
    4. Optionally, specify the service name.

      For example:

      bti7800(config-cross-connect-10ge:1/7/2/1/odu2:1/7/1/1.4)# service-name circuit_1714
    5. Apply the changes.
      bti7800(config-cross-connect-10ge:1/7/2/1/odu2:1/7/1/1.4)# commit
      Commit complete. 
    6. Optionally, show the resulting cross-connect.

      For example:

      bti7800(config-cross-connect-10ge:1/7/2/1/odu2:1/7/1/1.4)# do show cross-connect table | include circuit_1714
      2  10ge:1/7/2/1  odu2:1/7/1/1.4  2way   odu2   circuit_1714 

    Provisioning a Muxponding OTU2e-to-ODU2e/ODU4 Cross-Connect

    Use this procedure to provision a cross-connect that muxponds between an OTU2e interface and an ODU2e subinterface within a higher-order ODU4 on the UFM3.

    1. Enter configuration mode.
      bti7800# config
      bti7800(config)#
    2. Create the OTU4 and OTU2e interfaces.

      See Provisioning a Transport Interface for information on creating transport interfaces.

      1. Create the OTU4 interface. Make sure the automatically created ODU4 interface is configured for multiplexing.

        When you configure the ODU4 interface for multiplexing, the system automatically creates 10 ODU2 subinterfaces; for example, odu2:1/5/2/1.1 to odu2:1/5/2/1.10.

      2. Create the OTU2e interface.
      3. Optionally, show the created interfaces. For example:
        bti7800(config)# do show interface | include 1/5
        Name                                    : odu2:1/5/2/1.1   
        Name                                    : odu2:1/5/2/1.2   
        Name                                    : odu2:1/5/2/1.3   
        Name                                    : odu2:1/5/2/1.4   
        Name                                    : odu2:1/5/2/1.5   
        Name                                    : odu2:1/5/2/1.6   
        Name                                    : odu2:1/5/2/1.7   
        Name                                    : odu2:1/5/2/1.8   
        Name                                    : odu2:1/5/2/1.9   
        Name                                    : odu2:1/5/2/1.10   
        Name                                    : odu2e:1/5/1/1   
        Name                                    : odu4:1/5/2/1   
        Name                                    : otu2e:1/5/1/1   
        Name                                    : otu4:1/5/2/1 
    3. Create an ODU2e subinterface within the higher-order ODU4 interface. The ODU2e sub- interface must exist before you can configure the cross-connect.
      1. Delete an ODU2 subinterface from the ODU4 interface, and then create an ODU2e subinterface. For example:
        bti7800(config-interface-odu4:1/5/2/1)# no interface odu2:1/5/2/1.1
        bti7800(config-interface-odu4:1/5/2/1)# interface odu2e:1/5/2/1.1 type otnOdu 
        bti7800(config-interface-odu2e:1/5/2/1.1)# commit 
        Commit complete. 
      2. Optionally, show the interfaces. For example:
        bti7800(config)# do show interface | include 1/5
        Name                                    : odu2:1/5/2/1.2   
        Name                                    : odu2:1/5/2/1.3   
        Name                                    : odu2:1/5/2/1.4   
        Name                                    : odu2:1/5/2/1.5   
        Name                                    : odu2:1/5/2/1.6   
        Name                                    : odu2:1/5/2/1.7   
        Name                                    : odu2:1/5/2/1.8   
        Name                                    : odu2:1/5/2/1.9   
        Name                                    : odu2:1/5/2/1.10   
        Name                                    : odu2e:1/5/1/1   
        Name                                    : odu2e:1/5/2/1.1   
        Name                                    : odu4:1/5/2/1   
        Name                                    : otu2e:1/5/1/1   
        Name                                    : otu4:1/5/2/1 
    4. Configure the cross-connect.

      The following example cross-connects the ODU2e subinterface on the ODU4 to the ODU2e interface on the client side:

      bti7800(config)# cross-connect odu2e:1/5/2/1.1 odu2e:1/5/1/1
      bti7800(config-cross-connect-odu2e:1/5/2/1.1 odu2e:1/5/1/1)#  
    5. Optionally, specify the service name.

      For example:

      bti7800(config-cross-connect-odu2e:1/5/2/1.1 odu2e:1/5/1/1)# service-name circuit_2129
    6. Apply the changes.
      bti7800(config-cross-connect-odu2e:1/5/2/1.1 odu2e:1/5/1/1)# commit
      Commit complete. 
    7. Optionally, show the resulting cross-connect.

      For example:

      bti7800(config-cross-connect-odu2e:1/5/2/1.1 odu2e:1/5/1/1)# do show cross-connect table
      Cross-Connect   Source-Name        Destination-Name   Direction   Rate 
      -------------   -----------------  -----------------  ----------  ----- 
      1               odu2e:1/5/2/1.1    odu2e:1/5/1/1      2way        odu2e 

    Provisioning a Muxponding 10-Gbps-to-ODU2e/ODU4 Cross-Connect

    Use this procedure to provision a cross-connect that muxponds between a 10-Gbps interface and an ODU2e interface within a higher-order ODU4 on the UFM6. This procedure uses a 10-Gigabit Ethernet interface as an example. See Supported cross-connects for information about the cross-connects this module supports.

    1. Enter configuration mode.
      bti7800# config
      bti7800(config)#
    2. Create the interfaces to be cross-connected.

      See Provisioning a Transport Interface for information on creating transport interfaces.

      Note: The cross-connect mapping between the client 10-Gbps interface and line ODU2e subinterface on the ODU4 is fixed and cannot be changed. Ensure that the interfaces you create conform to the required mapping. See Supported cross-connects for more information.

      1. Create the optical channel interface.

        The optical channel represents the attributes that must be the same for all contained OTU4 signals. The optical channel interface must exist before you can create the OTU4 interfaces.

      2. Create the OTU4 interface. Make sure the automatically created ODU4 interface is configured for multiplexing.
      3. Create the 10-Gbps interface.

      The following lists the interfaces created on the UFM in slot 5 (for example):

      bti7800(config)# do show interface | include 1/5
      Name                                    : 10ge:1/5/1/1/1   
      Name                                    : odu2e:1/5/2/1/1.1.1.1   
      Name                                    : odu2e:1/5/2/1/1.1.1.2   
      Name                                    : odu2e:1/5/2/1/1.1.1.3   
      Name                                    : odu2e:1/5/2/1/1.1.1.4   
      Name                                    : odu2e:1/5/2/1/1.1.1.5   
      Name                                    : odu2e:1/5/2/1/1.1.1.6   
      Name                                    : odu2e:1/5/2/1/1.1.1.7   
      Name                                    : odu2e:1/5/2/1/1.1.1.8   
      Name                                    : odu2e:1/5/2/1/1.1.1.9   
      Name                                    : odu2e:1/5/2/1/1.1.1.10   
      Name                                    : odu4:1/5/2/1/1.1.1  
      Name                                    : otu4:1/5/2/1/1.1.1   
      Name                                    : och:1/5/2/1/1.1 

      When you configure the odu4:1/5/2/1/1.1.1 interface for multiplexing, the system automatically creates 10 subinterfaces odu2e:1/5/2/1/1.1.1.1 to odu2e:1/5/2/1/1.1.1.10 and configures the odtg and tributary-slot-list attributes on the odu4:1/5/2/1/1.1.1 interface appropriately.

    3. Configure the cross-connect.

      The following cross-connects the 10-Gbps interface with the associated ODU2e subinterface on the ODU4:

      bti7800(config)# cross-connect 10ge:1/5/1/1/1 odu2e:1/5/2/1/1.1.1.1
      bti7800(config-cross-connect-10ge:1/5/1/1/1 odu2e:1/5/2/1/1.1.1.1)#  
    4. Optionally, specify the service name.

      For example:

      bti7800(config-cross-connect-10ge:1/5/1/1/1 odu2e:1/5/2/1/1.1.1.1)# service-name circuit_2129
    5. Apply the changes.
      bti7800(config-cross-connect-10ge:1/5/1/1/1 odu2e:1/5/2/1/1.1.1.1)# commit
      Commit complete. 
    6. Optionally, show the resulting cross-connect.

      For example:

      bti7800(config-cross-connect-10ge:1/5/1/1/1 odu2e:1/5/2/1/1.1.1.1)# do show cross-connect table
      Cross-Connect  Source-Name     Destination-Name       Direction   Rate    Service-Name 
      -------------  --------------  --------------------   ----------  ------  ------------- 
      1              10ge:1/5/1/1/1  odu2e:1/5/2/1/1.1.1.1  2way        odu2e   circuit_2129 

    Modified: 2017-04-28