Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Provisioning a Transport Interface

 

Use this procedure to provision a transport interface on a UFM.

Prerequisites

  • The corresponding transceiver is provisioned.

  • The correct SERDES configuration must be applied on the UFM6 if you are configuring a 40ge interface on the UFM6. Otherwise, the configuration will fail and you will see a cfgFail alarm. The correct SERDES configuration is automatically applied if the UFM6 is inserted, reseated, or cold reloaded when the chassis is running software release 4.4 or higher.

  1. Enter configuration mode.
    bti7800# config
  2. Add the interface.

    The following example adds an OTU4 interface. See UFM Interfaces for information on setting the interface type.

    bti7800(config)# interface otu4:1/7/1/1
    Note

    This automatically creates a corresponding odu4:1/7/1/1 interface.

  3. Specify the frequency of the interface. This is required for interfaces with tunable transceivers.

    For example:

    bti7800(config-interface-otu4:1/7/1/1)# frequency 192.1
  4. Specify the type of FEC to use. The FEC type can only be changed when the interface is disabled.

    For example:

    bti7800(config-interface-otu4:1/7/1/1)# disabled

    See Forward error correction (FEC) types for information on supported values for the fec-type.

  5. Specify whether the corresponding ODU interface is a multiplexed (muxponding) or non-multiplexed (transponding) interface.Note

    Muxponding is only supported when multiplexing onto ODU4 interfaces.

    1. To configure a non-multiplexed interface:

      bti7800(config-interface-odu4:1/7/1/1)# multiplex-mode no-multiplex
    2. To configure a multiplexed interface:

      bti7800(config-interface-odu4:1/7/1/1)# multiplex-mode gmp-capable

      After you configure a multiplexed ODU4 interface and commit the changes, the lower-order subinterfaces are automatically created. Depending on the UFM, the system creates either ODU2 or ODU2e subinterfaces.

      Here is an example of the lower-order ODU2 subinterfaces within an ODU4 (truncated for clarity):

      bti7800(config)# do show interface table | include odu2:1/7/1/1

      Here is an example of the lower-order ODU2e subinterfaces within an ODU4 (truncated for clarity):

      bti7800(config)# do show interface table | include odu2e:1/5/2/1/2.1.2

      Here is an example of the lower-order ODU3 subinterfaces within an ODU4 (truncated for clarity):

      bti7800# show interface table | include odu3
    3. To change a subinterface between different ODU types::

      In some situations, you might want to change an ODU2 subinterface to an ODU2e subinterface and vice-versa. To do this, delete the subinterface you want to replace and create the desired subinterface.

      For example, the following deletes an ODU2e subinterface and creates a new ODU2 subinterface at that same location.

      bti7800(config)# no interface odu2e:1/5/2/1/2.1.2.5

      For example, the following deletes a set of ODU2e subinterfaces and creates a new ODU3 subinterface that uses the same tributary slots.

      bti7800(config)# no interface odu2e:1/14/2/1/1.1.1.1
      Note

      You must delete and create the subinterface before committing. If you commit in between the deletion and creation, you will get an error.

      For information on multiplexed interfaces, see Multiplexed Interfaces.

Release History Table
Release
Description
The correct SERDES configuration must be applied on the UFM6 if you are configuring a 40ge interface on the UFM6.
ODU3 subinterfaces within an ODU4