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

    Universal Forwarding Modules

    The Universal Forwarding Module (UFM) is a service module that can be configured for transport services such as transponding and muxponding. It is available in different types with different capabilities, as follows:

    Note: The UFM6 is supported starting with release 4.1.

    Table 1: UFM Types

     

    UFM3

    UFM4

    UFM6

    Name

    Universal Forwarding Module

    Universal Forwarding Module with Integrated 100G Coherent MSA XCVR

    Universal Forwarding Module with Integrated 400G Coherent MSA XCVR

    PEC

    BT8A78UFM3

    BT8A78UFM4

    BT8A78UFM6-I02

    Integrated 100G Coherent MSA XCVR

    N

    Y

    N

    Integrated 400G Coherent MSA XCVR

    N

    N

    Y

    Number of BIC slots

    2

    1

    0

    Transport services

    Y

    Y

    Y

    BTI7801

    Y

    Y

    Y

    BTI7802

    Y

    Y

    Y

    BTI7814

    Y

    Y

    Y

    A UFM contains zero, one, or two slots for BTI Interface Cards. BTI Interface Cards (BICs) are modules that hold pluggable transceivers. Pluggable transceivers are inserted into a BIC, which in turn is inserted into a BIC slot of a supporting UFM. There are different types of BICs depending on the pluggables required. By housing different BICs, the same UFM can hold different combinations of 10-Gbps and 100-Gbps interfaces.

    UFM Location Identifiers

    Each addressable component in a BTI7800 system consists of a component name and a location identifier. Together, they uniquely identify components in a system. All location identifiers begin with a chassis/slot combination, which specifies the chassis and slot that the component resides in. The location can then be further qualified depending on the type of component and module being specified.

    For UFMs, the location identifiers differ depending on the UFM type. All UFM types have two subslots or groups. A subslot can represent a physical subslot or a fixed grouping of ports.

    UFM3 Location Identifiers

    The UFM3 consists of two subslots for BICs.

    Each BIC is addressed using the chassis/slot/subslot location identifier format. For example:

    • bic:1/5/1 represents the BIC in subslot 1 of the UFM in chassis 1 slot 5.

    Different BICs hold different types and numbers of transceivers. Each transceiver is addressed using the chassis/slot/subslot/port location identifier format. For example:

    Note: The figure above is for illustration only and is not intended to depict any particular BIC type.

    • sfpPlus:1/5/1/8 represents an SFP+ transceiver on port 8 of the first BIC.
    • cfp:1/5/2/1 represents a CFP transceiver on port 1 of the second BIC.

    Associated with each transceiver port is an interface. This interface is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • otu2:1/5/1/8 (otu2e:1/5/1/8) represents an OTU2 (OTU2e) interface on the above SFP+ transceiver.
    • otu4:1/5/2/1 represents an OTU4 interface on the above CFP transceiver.

    Within each OTU2 (OTU2e) is an ODU2 (ODU2e), which is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • odu2:1/5/1/8 (odu2e:1/5/1/8) represents the ODU2 (ODU2e) interface contained within the above OTU2 (OTU2e).

    Similarly, within each OTU4 is an ODU4, which is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • odu4:1/5/2/1 represents the ODU4 interface contained within the above OTU4.

    If the ODU4 is configured for multiplexing, the multiplexed ODU2 (ODU2e) subinterfaces are addressed using the chassis/slot/subslot/port.subinterface location identifier format. For example:

    • odu2:1/5/2/1.5 (odu2e:1/5/2/1.5) represents the fifth ODU2 (ODU2e) subinterface multiplexed into the above ODU4/OTU4.

    UFM4 Location Identifiers

    The UFM4 consists of an integrated 100G Coherent MSA XCVR and a subslot for a single BIC. The 100G Coherent MSA XCVR is conceptually located in subslot 1 and the BIC is located in subslot 2.

    The 100G Coherent MSA XCVR is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • msa:1/5/1/1 represents the 100G Coherent MSA XCVR on a UFM in chassis 1 slot 5 subslot 1 port 1. This transceiver is always in subslot 1 port 1. It consists of a single 100-Gbps port.

    Associated with the 100G Coherent MSA XCVR port is a single 100-Gbps interface. This interface is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • otu4:1/5/1/1 represents the OTU4 interface for the above transceiver.

    Within the OTU4 is an ODU4, which is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • odu4:1/5/1/1 represents the ODU4 interface contained within the above OTU4.

    If the ODU4 is configured for multiplexing, the multiplexed ODU2 subinterfaces are addressed using the chassis/slot/subslot/port.subinterface location identifier format. For example:

    • odu2:1/5/1/1.5 represents the fifth ODU2 subinterface multiplexed into the above ODU4/OTU4.

    The BIC in this UFM is addressed using the chassis/slot/subslot location identifier format. For example:

    • bic:1/5/2 represents the BIC in the above UFM. The BIC in this UFM is always in subslot 2.

    Different BICs hold different types and numbers of transceivers. Each transceiver is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • sfpPlus:1/5/2/8 represents an SFP+ transceiver on port 8 of the above BIC.

    Associated with each transceiver port is an interface. This interface is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • 10ge:1/5/2/8 represents a 10-Gigabit Ethernet interface on the above SFP+ transceiver.

    UFM6 Location Identifiers

    The UFM6 consists of ten QSFP (six QSFP+ ports and four dual-mode QSFP+/QSFP28) ports and one integrated 400G Coherent MSA XCVR. The ten QSFP ports are located conceptually in subslot 1, and the 400G Coherent MSA XCVR is located conceptually in subslot 2. These are labeled Port Group 1 and Port Group 2 on the UFM faceplate.

    Note: The six QSFP+ ports are client ports 3, 4, 5, 8, 9, and 10. The four dual-mode QSFP+/QSFP28 ports are client ports 1, 2, 6, and 7.

    Each QSFP+ or QSFP28 transceiver is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • qsfp:1/5/1/8 represents a QSFP+ transceiver in a UFM6 in chassis 1 slot 5 subslot 1 port 8.
    • qsfp28:1/5/1/1 represents a QSFP28 transceiver in a UFM6 in chassis 1 slot 5 subslot 1 port 1.

    The QSFP+ transceiver supported for UFM6 carries four individual fiber pairs, with each fiber pair attached to a separate internal 10-Gbps interface. Each 10-Gbps interface is addressed using the chassis/slot/subslot/port/subport location identifier format. For example:

    • 10ge:1/5/1/8/3 represents a 10-Gigabit Ethernet interface attached to the third fiber pair of the above QSFP+ transceiver.

    The QSFP28 transceiver supports one 100-Gbps interface, which is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • 100ge:1/5/1/1 represents a 100-Gigabit Ethernet interface on the above QSFP28 transceiver.

    The 400G Coherent MSA XCVR is addressed using the chassis/slot/subslot/port location identifier format. For example:

    • msa400:1/5/2/1 represents the 400G Coherent MSA XCVR in a UFM6 in chassis 1 slot 5 subslot 2 port 1. This transceiver consists of a single internal 400-Gbps port.

    The internal 400-Gbps port in the 400G Coherent MSA XCVR is divided into the two 200-Gbps ports that are visible on the faceplate, with each 200-Gbps port carrying a single optical channel. The optical channel represents the optical signal and contains the settings and attributes that govern the constituent 100-Gbps signals. The optical channel is represented as an interface. It is addressed using the chassis/slot/subslot/port/subport.och location identifier format. For example:

    • och:1/5/2/1/2.1 represents the optical channel interface on the second 200-Gbps subport of the above transceiver.

    Depending on the modulation chosen, each optical channel can contain one or two 100-Gbps signals. Each 100-Gbps signal is attached to a logical 100-Gbps (OTU4) interface. The 100-Gbps interface is addressed using the chassis/slot/subslot/port/subport.och.tributary location identifier format. For example:

    • otu4:1/5/2/1/2.1.2 represents the second 100-Gbps interface in the above optical channel.

    Note: If the optical channel modulation is configured to allow only one 100-Gbps signal, that signal must be on the first 100-Gbps interface (for example, otu4:1/5/2/1/2.1.1). If the modulation is configured to allow two 100-Gbps signals, then you can use either of the two 100-Gbps interfaces (for example, otu4:1/5/2/1/2.1.1 or otu4:1/5/2/1/2.1.2) even if you are only configuring one 100-Gbps interface.

    Within the OTU4 is an ODU4, which is addressed using the chassis/slot/subslot/port/subport.och.tributary location identifier format. For example:

    • odu4:1/5/2/1/2.1.2 represents the ODU4 interface contained within the above OTU4.

    If the ODU4 is configured for multiplexing, the multiplexed ODU2 (ODU2e) subinterfaces are addressed using the chassis/slot/subslot/port/subport.och.tributary.subinterface location identifier format. For example:

    • odu2:1/5/2/1/2.1.2.5 (odu2e:1/5/2/1/2.1.2.5) represents the fifth ODU2 (ODU2e) subinterface multiplexed into the above ODU4/OTU4.

    Provisioning UFM Equipment

    Provisioning UFM equipment consists of provisioning the UFM itself, the BTI Interface Cards (BICs) if applicable, and the transceivers.

    Provisioning a UFM

    Use this procedure to add a UFM to a chassis.

    If auto-provisioning is enabled and you do not want to pre-provision, then you can skip this procedure because the system automatically provisions the UFM when you insert the UFM into the chassis.

    The type of UFM you are adding is specified by the ufm-type attribute, as shown in the following table:

    UFM

    ufm-type

    UFM3

    dual-bic-non-switching

    UFM4

    msa-non-switching

    UFM6

    msa400-10g-100g-client

    Note: UFM types not listed above have been deprecated.

    1. Enter configuration mode.
      bti7800# config
      bti7800(config)#
    2. Add the UFM and specify the type of UFM you are adding.

      For example, the following adds a UFM4 to chassis 1 slot 2:

      bti7800(config)# equipment chassis:1 module ufm:1/2
      Value for 'ufm-type' [dual-bic-non-switching,dual-bic-switching,msa-non-switching,msa-switching,msa400-10g-100g-client]: msa-non-switching 
      bti7800(config-module-ufm:1/2)# 
    3. Apply the changes.
      bti7800(config-module-ufm:1/2)# commit
      Commit complete. 

    Provisioning a BTI Interface Card (BIC)

    Use this procedure to add a BIC.

    If auto-provisioning is enabled and you do not want to pre-provision, then you can skip this procedure because the system automatically provisions the BIC when the system detects the presence of the BIC. The system detects the presence of the BIC in these situations:

    • The BIC is inserted into a UFM that is already installed in the chassis.
    • The BIC is inserted into an uninstalled UFM that is then installed into the chassis.

    The type of BIC you are adding is specified by the bic-type attribute, as shown in the following table:

    BIC

    bic-type

    12x SFP+ BIC

    sfp-bic

    1x CFP BIC

    cfp-bic

    1. Enter configuration mode.
      bti7800# config
      bti7800(config)#
    2. Add the BIC to the desired BIC slot in the UFM.

      The following example adds a 1x CFP BIC to BIC slot 2 in the UFM in slot 7:

      bti7800(config)# equipment chassis:1 module ufm:1/7 bic bic:1/7/2
      Value for 'bic-type' [cfp-bic,qsfp-bic,sfp-bic]: cfp-bic 
      bti7800(config-bic-bic:1/7/2)#
    3. Apply the configuration changes.

      For example:

      bti7800(config-bic-bic:1/7/2)# commit
      Commit complete. 

    Provisioning a Transceiver

    Use this procedure to add a transceiver. A transceiver component can be added to a BIC or to a UFM with fixed ports or to a UFM with an integrated transceiver.

    If auto-provisioning is enabled and you do not want to pre-provision, then you can skip this procedure because the system automatically provisions the transceiver when the system detects the presence of the transceiver. The system detects the presence of the transceiver in these situations:

    • The transceiver is inserted into a BIC that is already installed in the chassis.
    • The transceiver is inserted into an uninstalled BIC that is then installed into a UFM in the chassis.
    • The transceiver is inserted into an uninstalled BIC that is then inserted into an uninstalled UFM that is then installed in the chassis.
    • The transceiver is inserted into a UFM that is already installed in the chassis.
    • The transceiver is inserted into an uninstalled UFM that is then installed in the chassis.
    • For a UFM with an integrated transceiver, the system detects the integrated transceiver when the UFM is inserted into the chassis.
    1. Enter configuration mode.
      bti7800# config
      bti7800(config)#
    2. Add a transceiver.

      You can add a transceiver to a BIC or you can add a transceiver directly to a UFM. The type of transceiver you are adding is specified by the optical-format attribute. For more details on the optical-format attribute, see the BTI7800 Series Command Line Reference Guide.

      1. To add a transceiver to an existing BIC on a UFM3 or UFM4:

        The following example adds a fixed-wavelength single-channel SFP+ transceiver to port 3 of an existing BIC in subslot 2 of the UFM in slot 2.

        bti7800(config)# equipment chassis:1 module ufm:1/2 bic bic:1/2/2 transceiver sfpPlus:1/2/2/3
        Value for 'optical-format' [fixedX1,fixedX4,fixedX10,tunableX1,...]: fixedX1 
        bti7800#(config-transceiver-sfpPlus:1/2/2/3)# 
      2. To add a transceiver component to the 100G Coherent MSA XCVR in an existing UFM4:

        The following example adds a tunable single-channel CFP transceiver to an existing UFM in slot 2.

        bti7800(config)# equipment chassis:1 module ufm:1/2 transceiver msa:1/2/1/1
        Value for 'optical-format' [fixedX1,fixedX4,fixedX10,tunableX1,...]: tunableX1 
        bti7800#(config-transceiver-msa:1/2/1/1)# 

        Note: The integrated transceiver in a UFM4 is a tunable CFP transceiver that is always addressed using subslot 1 port 1.

      3. To add a client-side transceiver to an existing UFM6:

        The following example adds a QSFP+ transceiver to an existing UFM in slot 5.

        bti7800(config)# equipment chassis:1 module ufm:1/5 transceiver qsfp:1/5/1/3
        Value for 'optical-format' [fixedX1,fixedX4,fixedX10,none,...]: fixedX4 
        bti7800(config-transceiver-qsfp:1/5/1/3)# 

        Note: The client-side transceivers in UFM6 are always addressed using subslot 1.

      4. To add a transceiver component to the 400G Coherent MSA XCVR in an existing UFM6:

        The following example adds a 400-Gbps transceiver to an existing UFM6 in slot 5.

        bti7800(config)# equipment chassis:1 module ufm:1/5 transceiver msa400:1/5/2/1
        Value for 'optical-format' [fixedX1,fixedX4,fixedX10,none,...]: tunableX2 
        bti7800(config-transceiver-msa400:1/5/2/1)#  

        Note: The integrated transceiver in UFM6 is always addressed using subslot 2 port 1.

    3. Optionally, configure the PEC.

      You do not normally need to configure the PEC. If you do configure the PEC, ensure that the PEC matches the PEC of the transceiver that you install. You cannot configure PECs for integrated transceivers.

      1. For transceivers that do not have a 740-xxxxxx code assigned, enter the PEC.

        For example:

        bti7800#(config-transceiver-sfpPlus:1/2/2/3)# pec BP3AM6MS
      2. For transceivers that do have a 740-xxxxxx code assigned, enter the 740-xxxxxx code.

        For example:

        bti7800(config-transceiver-qsfp:1/5/1/3)# pec 740-058730
    4. Apply the configuration changes.

      For example:

      bti7800(config)# commit
      Commit complete. 

    Replacing a UFM3 or a UFM4

    When replacing a UFM4 with a similarly equipped UFM3, or replacing a UFM3 with a similarly equipped UFM4, the system can automatically unprovision the old UFM and provision the new UFM. This is called auto-reprovisioning, and includes the unprovisioning of the old equipment, interfaces, and cross-connects, and the reprovisioning of the new equipment, interfaces, and cross-connects.

    Auto-reprovisioning automatically removes configuration for the old UFM, adds configuration for the new UFM, and modifies any parameters that are not compatible with the new UFM.

    When auto-reprovisioning is performed successfully, the new UFM boots seamlessly into the new configuration, preserving all provisioned interfaces and cross-connects. No manual reconfiguration is necessary.

    This section describes the software configuration changes that automatically result from this replacement procedure. For the replacement procedure itself, see the BTI7800 Series Hardware Overview and Installation Guide.

    Qualifying Criteria

    The system automatically reprovisions a UFM when the following criteria are met:

    UFM Replacement

    Criteria

    Notes

    UFM4 to UFM3

    • Auto-reprovisioning is enabled. See Configuring Auto-Reprovisioning.
    • A UFM3 is inserted into a slot that is provisioned for a UFM4.
    • An MSA transceiver is configured on the UFM4 being replaced.

    The inserted UFM3 should have a 1x CFP BIC installed in BIC slot 1, and a 100G Coherent CFP installed in that BIC. The UFM3 should also have the same equipment installed in BIC slot 2 as the UFM4 being replaced.

    If the inserted UFM3 is not equipped as described, auto-reprovisioning still takes place but alarms might be raised indicating missing or mismatched equipment.

    UFM3 to UFM4

    • Auto-reprovisioning is enabled. See Configuring Auto-Reprovisioning.
    • A UFM4 is inserted into a slot that is provisioned for a UFM3.
    • A 1x CFP BIC is configured in BIC slot 1 of the UFM3 being replaced.
    • A 100G Coherent CFP is configured on the 1x CFP BIC.

    The inserted UFM4 should have the same equipment installed in BIC slot 2 as the UFM3 being replaced.

    If the inserted UFM4 is not equipped as described, auto-reprovisioning still takes place but alarms might be raised indicating missing or mismatched equipment.

    Note: Auto-reprovisioning does not apply to any other UFM replacement procedure.

    Provisioning Changes

    When the qualifying criteria are met, the system performs the following provisioning changes:

    Table 2: Reprovisioning When Replacing a UFM4 with a UFM3

    Parameter

    Old Value (UFM4)

    New Value (UFM3)

    equipment chassis module ufm ufm-type

    msa-non-switching

    dual-bic-non-switching

    equipment chassis module ufm pec

    BT8A78UFM4

    BT8A78UFM3

    equipment chassis module ufm transceiver msa

    Exists.

    Removed.

    equipment chassis module ufm bic in BIC slot 1

    Does not exist.

    Created.

    equipment chassis module ufm bic bic-type for the BIC in BIC slot 1

    --

    cfp-bic

    equipment chassis module ufm bic admin-status for the BIC in BIC slot 1

    --

    up

    equipment chassis module ufm bic transceiver cfp for the BIC in BIC slot 1

    Does not exist.

    Created.

    equipment chassis module ufm bic transceiver cfp optical-format for the CFP in the BIC in BIC slot 1

    --

    tunableX1

    equipment chassis module ufm bic transceiver cfp admin-status for the CFP in the BIC in BIC slot 1

    --

    Set to the same value as the original equipment chassis module ufm transceiver msa admin-status.

    equipment chassis module ufm bic transceiver cfp custom for the CFP in the BIC in BIC slot 1

    --

    Set to the same values as the original equipment chassis module ufm transceiver msa custom fields.

    interface

    Might exist.

    Unchanged.

    If an interface for the MSA transceiver exists, then the same interface is now implicitly associated with the new CFP transceiver.

    If an interface for the MSA transceiver does not exist, then an interface for the new CFP transceiver also does not exist.

    interface otu4 cprws

    32-symbols

    48-symbols

    8-symbols

    6-symbols

    4-symbols

    3-symbols

    cross-connect

    Might exist.

    Unchanged.

    Table 3: Reprovisioning When Replacing a UFM3 with a UFM4

    Parameter

    Old Value (UFM3)

    New Value (UFM4)

    equipment chassis module ufm ufm-type

    dual-bic-non-switching

    msa-non-switching

    equipment chassis module ufm pec

    BT8A78UFM3

    BT8A78UFM4

    equipment chassis module ufm transceiver msa

    Does not exist.

    Created.

    equipment chassis module ufm transceiver msa optical-format

    --

    tunableX1

    equipment chassis module ufm transceiver msa admin-status

    --

    Set to the same value as the original equipment chassis module ufm bic transceiver cfp admin-status.

    equipment chassis module ufm transceiver msa custom

    --

    Set to the same values as the original equipment chassis module ufm bic transceiver cfp custom fields.

    equipment chassis module ufm bic in BIC slot 1

    Exists.

    Removed.

    equipment chassis module ufm bic transceiver cfp

    Exists.

    Removed.

    interface

    Might exist.

    Unchanged.

    If an interface for the CFP transceiver exists, then the same interface is now implicitly associated with the new MSA transceiver.

    If an interface for the CFP transceiver does not exist, then an interface for the new MSA transceiver also does not exist.

    interface otu4 cprws

    48-symbols

    32-symbols

    6-symbols

    8-symbols

    3-symbols

    4-symbols

    interface otu4 tx-power

    -15dBm to -5dBm

    -5dBm

    -5dBm to 1dBm

    Unchanged.

    cross-connect

    Might exist.

    Unchanged.

    Note: Auto-reprovisioning does not change any parameters for the equipment or interfaces in BIC slot 2.

    Alarm Behavior

    Under normal situations, when you insert a UFM into a slot provisioned for a UFM of another type, an Equipment Mismatch (eqptMism) alarm is raised against the inserted UFM.

    In situations where auto-reprovisioning takes place, this alarm is suppressed.

    Post-Upgrade Verification

    After you replace the UFM, use the following commands to verify that the new UFM has been configured correctly:

    • show inventory to verify that the new UFM and BICs are in inventory
    • show equipment to verify that the new UFM and BICs are operationally up
    • show running-config equipment chassis:1 module ufm to verify that the module configuration is correct
    • show running-config interface to verify that the previous interface configuration has been properly propagated
    • show running-config cross-connect to verify that the previous cross-connect configuration has been properly propagated
    • show conditions to ensure that no unexpected condition or alarm exists

    Configuring a Loopback on a UFM Interface

    Use this procedure to place a UFM interface into loopback mode.

    Both facility and terminal loopbacks are supported, as follows:

    Loopback type

    Supported interfaces

    Description

    Facility loopback

    OTU, SONET/SDH, Ethernet interfaces

    Traffic arriving on the facility (link) is both looped back and allowed to pass straight through. Traffic in the opposite direction is dropped.

    For the looped-back traffic on OTU interfaces, the OTU overhead is regenerated and the FEC bytes are recalculated.

    Terminal loopback

    OTU, SONET/SDH, Ethernet interfaces

    Note: Terminal loopback is not supported on an OTU interface that contains an ODU configured for multiplexing.

    Traffic arriving from a remote source (from the direction of the backplane) is both looped back and allowed to pass straight through to the local link. Traffic in the opposite direction is dropped.

    1. Enter configuration mode.
      bti7800# config
      bti7800(config)#
    2. Disable the interface that is to be placed into loopback mode.

      For example:

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

      The interface no longer passes traffic in either direction.

    3. Place the interface into loopback mode.
      1. To configure a facility loopback:
        bti7800(config-interface-otu4:1/7/1/1)# loopback-mode facility
      2. To configure a terminal loopback:
        bti7800(config-interface-otu4:1/7/1/1)# loopback-mode terminal
    4. Apply the configuration changes.

      For example:

      bti7800(config-interface-otu4:1/7/1/1)# commit
      Commit complete. 

      The interface starts to pass traffic through and loop traffic back in accordance with the loopback type.

    Release History Table

    Release
    Description
    The UFM6 is supported starting with release 4.1.

    Modified: 2017-07-06