Configuring physical ports with CLI

This section provides information to configure cards, MDAs, and ports.

Preprovisioning guidelines

SR OSs have a console port, either located on the CPM or CCM, or integrated into the chassis (on the 7750 SR-c4 models), to connect terminals to the router.

Configure command options from a system console connected to a router console port, using Telnet to access a router remotely or SSH to open a secure shell connection.

Predefining entities

To initialize a card, the chassis slot, line card type, and MDA type must match the preprovisioned command options. In this context, preprovisioning means to configure the entity type (such as the card type, MDA type, port, and interface) that is planned for a chassis slot, card, or MDA. Preprovisioned entities can be installed but not enabled or the slots can be configured but remain empty until populated. Provisioning means that the preprovisioned entity is installed and enabled.

You can:

  • Preprovision ports and interfaces after the line card and MDA types are specified.

  • Install line cards in slots with no pre-configuration command options specified. After the card is installed, the card and MDA types must be specified.

  • Install a line card in a slot provisioned for a different card type (the card does not initialize). The existing card and MDA configuration must be deleted and replaced with the current information.

Preprovisioning a port

Before a port can be configured, the slot must be preprovisioned with an allowed card type and the MDA must be preprovisioned with an allowed MDA type. Some recommendations to configure a port include:

  • Ethernet

    • Configure an access port for customer facing traffic on which services are configured.

    • An encapsulation type may be specified to distinguish services on the port or channel. Encapsulation types are not required for network ports.

    • To configure an Ethernet access port, see Ethernet access port.

  • SONET/SDH

    • SONET/SDH can be used only when configuring OC-3 and OC-12 SONET paths.

    • To configure a SONET path, see Configuring SONET/SDH ports.

    • Configure a network port or channel to participate in the service provider transport or infrastructure network.

    • Accounting policies can only be associated with network ports/channels and Service Access Ports (SAPs). Accounting policies are configured in the following context.

      configure log accounting-policy
    • To configure an Ethernet network port, see Ethernet network port.

  • channelized

    Channelized ports can only be configured on TDM satellites such as the channelized OC-3-SFP or channelized OC-12-SFP.

Maximizing bandwidth use

After ports are preprovisioned, Link Aggregation Groups (LAGs) can be configured to increase the bandwidth available between two nodes.

All physical links or channels in a LAG/bundle combine to form one logical connection. A LAG/bundle also provides redundancy in case one or more links that participate in the LAG/bundle fail. To configure channelized port for Sonet/SDH high speed channels (ASAP MDAs only), see Configuring SONET/SDH ports. For command syntax for LAG, see Configuring LAG.

Basic configuration

The most basic configuration must specify the following:

  • chassis slot

  • line card type (must be an allowed card type)

  • MDA slot

  • MDA (must be an allowed MDA type)

  • specific port to configure

The following is an example of card configuration for the 7750 SR.

MD-CLI

[ex:]
A:admin@node-2# info
    configure {
        card 6 {
            card-type iom4-e
            mda 1 {
                mda-type me1-100gb-cfp2
            }
            fp 1 {
            }
        }
        card 7 {
            card-type iom4-e
            mda 1 {
                mda-type me10-10gb-sfp+
            }
            mda 2 {
                mda-type me1-100gb-cfp2
            }
            fp 1 {
            }
        }
        card 8 {
            card-type iom4-e
            mda 1 {
                mda-type me10-10gb-sfp+
            }
        }

classic CLI

A:node-2> admin display-config 
echo "Card Configuration"
#--------------------------------------------------
    card 6
        card-type iom4-e
        no shutdown
    exit
    card 7
        card-type iom4-e
        mda 1
            mda-type me10-10gb-sfp+
            no shutdown
        exit
        mda 2
            mda-type me1-100gb-cfp2
            no shutdown
        exit
        no shutdown
    exit
    card 8
        card-type iom4-e
        no shutdown
    exit
#--------------------------------------------------

The following is an example of card configurations for the 7950 XRS.

MD-CLI

[ex:/configure card 1]
A:admin@node-2# info
    card-type xcm-x20
    mda 1 {
        mda-type cx2-100g-cfp
           }
    mda 2 {
        mda-type cx20-10g-sfp
            }
    fp 1 {
    }

classic CLI

A:node-2>configure card 1# info
----------------------------------------------
        card-type xcm-x20
        mda 1
            mda-type cx2-100g-cfp
            no shutdown
        exit
        mda 2
            mda-type cx20-10g-sfp
            no shutdown
        exit
        no shutdown
----------------------------------------------

Common configuration tasks

The following sections are basic system tasks that must be performed.

Configuring cards and MDAs

Card configurations include a chassis slot designation. A slot must be preconfigured with the type of cards and MDAs which are allowed to be provisioned.

The following example shows card and MDA configurations for the 7750 SR or 7450 ESS.

MD-CLI

[ex: /configure card 8]
A:admin@node-2# info
    card-type iom4-e
    mda 1 {
        mda-type me10-10gb-sfp+
    }
    mda 2 {
        mda-type me1-100gb-cfp2
    }
    fp 1 {
    }

classic CLI

A:node-2>config>card# info
#--------------------------------------------------
    card 8
        card-type iom4-e
        mda 1
            mda-type me10-10gb-sfp+
            no shutdown
        exit
        mda 2
            mda-type me1-100gb-cfp2
            no shutdown
        exit
        no shutdown
              exit
#----------------------------------------------

The following example shows card configurations for the 7950 XRS.

MD-CLI

[ex:/configure card 1]
A:admin@node-2# info
    card-type xcm-x20
    mda 1 {
        mda-type cx20-10g-sfp
           }
    mda 2 {
        mda-type cx2-100g-cfp
            }
    fp 1 {
    }

classic CLI

A:node-2>config>card# info
----------------------------------------------
        card-type xcm-x20
        mda 1
            mda-type cx20-10g-sfp
            no shutdown
        exit
        mda 2
            mda-type cx2-100g-cfp
            no shutdown
        exit
        no shutdown
----------------------------------------------

Configuring FP network pools

FP-level pools are used by ingress network queues. Network policies can be applied (optional) to create and edit QoS pool resources for ingress network queues. Network-queue and slope policies are configured in the following context.
configure qos

The following example shows an FP pool configuration for 7750 SR or 7450 ESS.

MD-CLI
[ex:/configure card 1 fp 1]
A:admin@node-2# info
    ingress {
        network {
            queue-policy "10"
            pool "default" {
                slope-policy "slope1"
                resv-cbs {
                    cbs 50
                }
            }
        }
    }
classic CLI
A:node-2>config>card>fp# info
----------------------------------------------
            ingress
                network
                    pool "default"
                        resv-cbs 50
                        slope-policy "slope1"
                    exit
                    queue-policy "10"
                exit
            exit
----------------------------------------------

Configuring ports

This section provides the CLI and examples to configure port command options.

Configuring port pools

The buffer space is portioned out on a per port basis. Each port gets an amount of buffering which is its fair-share based on the port’s bandwidth compared to the overall active bandwidth.

This mechanism takes the buffer space available and divides it into a portion for each port based on the port’s active bandwidth relative to the amount of active bandwidth for all ports associated with the buffer space. The number of ports sharing the same buffer space depends on the type of MDAs populated on the IOM. An active port is considered to be any port that has an active queue associated. After a queue is created for the port, the system allocates the appropriate amount of buffer space to the port. This process is independently performed for both ingress and egress.

Normally, the amount of active bandwidth is considered as opposed to total potential bandwidth for the port when determining the port’s fair share. If a port is channelized and not all bandwidth is allocated, only the bandwidth represented by the configured channels with queues configured is counted toward the bandwidth represented by the port. Also, if a port may operate at variable speeds (as in some Ethernet ports), only the current speed is considered. Based on the above, the number of buffers managed by a port may change because of queue creation and deletion, channel creation and deletion and port speed variance on the local port or other ports sharing the same buffer space.

After the active bandwidth is calculated for the port, the result may be modified through the use of the following commands.
  • MD-CLI
    configure port modify-buffer-allocation percentage-of-rate egress
    configure port modify-buffer-allocation percentage-of-rate ingress
  • classic CLI
    configure port modify-buffer-allocation egr-percentage-of-rate
    configure port modify-buffer-allocation ing-percentage-of-rate
The default value of each is 100% which allows the system to use all of the ports active bandwidth when deciding the relative amount of buffer space to allocate to the port. When the value is explicitly modified, the active bandwidth on the port is changed according to the specified percentage. If a value of 50% is given, the ports active bandwidth is multiplied by 5, if a value of 150% is given, the active bandwidth is multiplied by 1.5. The ports rate percentage command options may be modified at any time.

To modify (in this example, to double) the size of buffer allocated on ingress for a port.

MD-CLI
configure port 1/2/1 modify-buffer-allocation-rate percentage-of-rate ingress 200
classic CLI
configure port 1/2/1 modify-buffer-allocation-rate ing-percentage-of-rate 200

To modify (in this example, to double) the size of buffer allocated on egress for a port.

MD-CLI
configure port 1/2/1 modify-buffer-allocation-rate percentage-of-rate egress 200
classic CLI
configure port 1/2/1 modify-buffer-allocation-rate egr-percentage-of-rate 200

The default buffer allocation has the following characteristics:

  • Each port manages a buffer according to its active bandwidth (ports with equal active bandwidth get the same buffer size).

  • An access port has 2 default pools created: access-ingress and access-egress.

  • A network port has 2 default pools created: ingress-FP (common pool for all ingress network ports) and network-egress.

  • All queues defined for a port receive buffers from the same buffer pool.

The following example shows port pool configurations.

MD-CLI
[ex:/configure port 1/1/1]
A:admin@node-2# info
    admin-state enable
    access {
        egress {
            pool "default" {
                slope-policy "slopePolicy1"
            }
        }
    }
    network {
        egress {
            pool "default" {
                slope-policy "slopePolicy2"
            }
        }
    }
classic CLI
A:node-2>config>port# info 
----------------------------------------------
        access
            egress
                pool
                    slope-policy "slopePolicy1"
                exit
            exit
        exit
        network
            egress
                pool
                    slope-policy "slopePolicy2"
                exit
            exit
        exit
        no shutdown
----------------------------------------------

The following shows a CBS configuration over subscription example.

MD-CLI
[ex:/configure port 1/1/1]
A:admin@node-2# info
    admin-state enable
    access {
        ingress {
            pool "default" {
                amber-alarm-threshold 10
                resv-cbs {
                    cbs 10
                    amber-alarm-action {
                        step 1
                        max 30
                    }
                }
            }
        }
    }
    ethernet {
        mode access
        encap-type dot1q
    }
classic CLI
A:node-2>config>port# info 
----------------------------------------------
        access
            ingress
                pool 
                    amber-alarm-threshold 10
                    resv-cbs 10 amber-alarm-action step 1 max 30
                exit
            exit
        exit
        ethernet
            mode access
            encap-type dot1q
        exit
        no shutdown

Changing hybrid-buffer-allocation

The following example shows a hybrid-buffer-allocation value change (from default) for ingress. In this example, the network-egress buffer pool is two times the size of the access-egress.

MD-CLI
[ex:/configure port 1/1/2 hybrid-buffer-allocation]
A:admin@node-2# info
    egress-weight {
        access 20
        network 40
    }
classic CLI
A:node-2config>port>hybrid-buffer-allocation# info 
----------------------------------------------
egr-weight access 20 network 40

Changing the APS configuration

Note: Nokia recommends grouping working lines and protect lines on separate IOMs.

APS configuration rules:

  • A working port must be added first. Then a protection port can be added or removed at any time.

  • A protection port must be shutdown before being removed from an APS group.

  • A path cannot be configured on a port before the port is added to an APS group.

  • A working port cannot be removed from an APS group until the APS port path is removed.

  • When ports are added to an APS group, all path-level configurations are available only on the APS port level and configuration on the physical member ports are blocked.

  • For a multichassis APS group, only one member circuit (either working or protect) can be added. Note that the neighbor IP address of an APS group must be configured before adding a member circuit in it. The configuration of a non-zero neighbor IP address indicates the APS group as multichassis. Thus, the member circuit and services must be removed before adding or removing the neighbor IP address (for example, before converting an APS group from multichassis to single-chassis or single-chassis to multichassis).

The following shows an example configuration for a TDM SC-APS group using SONET/SDH channelization, and a Cpipe service using an APS SAP and a physical TDM SAP.

MD-CLI
[ex:/configure port 1/1/1]
A:admin@node-2# info
    admin-state enable
    sonet-sdh {
        speed oc3
    }

[ex:/configure aps 1]
A:admin@node-2# info
    protect-circuit 2/1/4
    working-circuit 1/1/2

[ex:/configure port aps-1]
A:admin@node-2# info
    admin-state enable
    sonet-sdh {
        path sts1-1 {
        }
        path sts1-3 {
        }
        path vt15-1.1.1 {
        }
        path vt15-3.7.4 {
        }
    }
    tdm {
        ds1 1.1.1 {
            clock-source node-timed
            framing ds1-unframed
            channel-group 1 {
            }
        }
        ds1 3.7.4 {
            clock-source node-timed
            framing ds1-unframed
            channel-group 1 {
            }
        }
    }

[ex:/configure service cpipe "221"]
A:admin@node-2# info
    customer "1"
    vc-type satop-t1
    sap aps-1:0/32 {
    }
classic CLI
A:node-2>config# port 1/1/1
----------------------------------------------
    sonet-sdh
        speed oc3
    exit
    no shutdown
----------------------------------------------
A:node-2>config>port# aps-1
----------------------------------------------
    aps
        working-circuit 1/1/2
        protect-circuit 2/1/4
    exit
    sonet-sdh
            path sts1-1
            exit
            path sts1-3
            exit
            path vt15-1.1.1
            exit
            path vt15-3.7.4
            exit
        exit
        tdm
            ds1 1.1.1
                framing ds1-unframed
                clock-source node-timed
                channel-group 1
                exit
            exit
            ds1 3.7.4
                framing ds1-unframed
                clock-source node-timed
                channel-group 1
                exit
            exit
        exit
    exit
    no shutdown
    exit
----------------------------------------------
A:node-2>cpipe 221 customer 1 vc-type satop-t1 create
            sap aps-100.1.1.1.1 create
            exit
            sap tsat-1/1/1.1.1.1.1 create
            exit
        exit

The following shows an example of the configuration for the working circuit/node of an MC-APS group.

MD-CLI
[ex:/configure]
A:admin@node-2# info
    aps 1 {
        neighbor 192.0.2.2
        working-circuit 1/1/2
    }
...
port aps-1 {
        admin-state enable
        description "APS Group"
    }
classic CLI
A:node-2>config>port# info
----------------------------------------------
        description "APS Group"
        aps
            neighbor 192.0.2.2
            working-circuit 1/1/2
        exit 
        no shutdown 
----------------------------------------------

The following shows an example of the configuration for the protect circuit/node of an MC-APS group.

MD-CLI
[ex:/configure aps 1]
A:admin@node-2# info
    neighbor 192.0.2.1
    protect-circuit 2/1/4
...
port aps-1 {
        admin-state enable
        description "APS Group"
    }
classic CLI
A:node-2>config>port# info
----------------------------------------------
        description "APS Group"
        aps
            neighbor 192.0.2.1
            protect-circuit 2/1/4
        exit 
        no shutdown 
----------------------------------------------

Configuring Ethernet ports

Ethernet network port

A network port is network facing and participates in the service provider transport or infrastructure network processes.

The following example shows a network port configuration.

MD-CLI
[ex:/configure port A/3]
A:admin@node-2# info
    admin-state enable
    description "Ethernet network port"

classic CLI
A:node-2config>port# info 
----------------------------------------------
        description "Ethernet network port"
        ethernet
        exit
        no shutdown
----------------------------------------------
Ethernet access port

Services are configured on access ports used for customer-facing traffic. If a Service Access Port (SAP) is to be configured on a port, it must be configured as access mode. When a port is configured for access mode, the appropriate encapsulation type can be specified to distinguish the services on the port. After a port has been configured for access mode, multiple services may be configured on the port.

The following example shows an Ethernet access port configuration.

MD-CLI
[ex:/configure port 1/2/3]
A:admin@node-2# info
    admin-state enable
    description "Ethernet access port"
    access {
        egress {
            pool "default" {
                slope-policy "slopePolicy1"
            }
        }
    }
    ethernet {
        mode access
        encap-type dot1q
    }
    network {
        egress {
            pool "default" {
                slope-policy "slopePolicy2"
            }
        }
    }
classic CLI
A:node-2>config>port# info
----------------------------------------------
        description "Ethernet access port"
        access
            egress
                pool
                    slope-policy "slopePolicy1"
                exit
            exit
        exit
        network
            egress
                pool
                    slope-policy "slopePolicy2"
                exit
            exit
        exit
        ethernet
            mode access
            encap-type dot1q
        exit
        no shutdown
----------------------------------------------
Configuring an 802.1x authentication port

The following example shows an 802.1x port configuration.

MD-CLI
[ex:/configure port 1/2/4 ethernet dot1x]
A:admin@node-2# info detail
...
    admin-state enable
    max-authentication-requests 2
    port-control auto
    quiet-period 60
    radius-policy dot1xpolicy
    server-timeout 30
    supplicant-timeout 30
    transmit-period 30
    tunneling false
    tunnel-dot1q true
    tunnel-qinq true
    re-authentication {
        period 3600
    }
   ...
classic CLI
A:node-2>config>port>ethernet>dot1x# info detail
----------------------------------------------
                 port-control auto
                 radius-plcy dot1xpolicy
                 re-authentication
                 re-auth-period 3600
                 max-auth-req 2
                 transmit-period 30
                 quiet-period 60
                 supplicant-timeout 30
                 server-timeout 30
                 no tunneling
                 no shutdown
----------------------------------------------

Configuring SONET/SDH ports

Only the TDM satellite has native SONET/SDH ports.

When an Ethernet port is configured in WAN mode (xgig wan), you can change specific SONET/SDH command options to reflect the SONET/SDH requirements for this port.

The following CLI output shows an example of a SONET/SDH configuration for a WAN PHY Ethernet port.

MD-CLI
[ex:/configure port 1/2/4]
A:admin@node-2# info
    ethernet {
        xgig wan
    sonet-sdh {
        sd-threshold 4
        suppress-low-order-alarms true
        tx-dus true
        section-trace {
            increment-z0
        }
        path sts192 {
            signal-label 0x20
            trace-string "hello"
            report-alarm {
                pais true
            }
        }
    }
classic CLI
A:node-2config>port# info
----------------------------------------------
        shutdown
        ethernet
            xgig wan
        exit
        sonet-sdh
            tx-dus
            suppress-lo-alarm
            threshold ber-sd rate 4
            section-trace increment-z0
            path
                trace-string "hello"
                report-alarm pais
                signal-label 0x20
            exit
        exit
----------------------------------------------

Configuring channelized ports

When configuring channelized ports, the port ID is specified in different ways depending on the level of channelization. Ethernet ports cannot be channelized. Channelization options available on the 7750 SR channelized MDAs lists the channelization options and port syntax available on the 7750 SR channelized MDAs.

Table 1. Channelization options available on the 7750 SR channelized MDAs
Framing Channelization/mapping option Channelized MDAs supporting services on the port/channel

Up to 2,048 kb/s (n*DS0 within E1 up to E1)

SDH

STM4>AUG4>AUG1>VC4>TUG3>TUG2>VC12

TDM satellite configured in mode t1-chstm4-sfp

SDH

STM4>AUG4>AUG1>VC3>TUG2>VC12

TDM satellite configured in mode ts4-chstm1-sfp

Up to 1,544 kb/s (n*DS0 within DS1 up to DS1)

SDH

STM4>AUG4>AUG1>VC4>TUG3>TUG2>TU11>VC11

TDM satellite configured in mode ts1-chstm4-sfp

SDH

STM4>AUG4>AUG1>VC4>TUG3>TUG2>TU12>VC11

None

SDH

STM4>AUG4>AUG1>VC3>TUG2>VC11

TDM satellite configured in mode ts4-chstm1-sfp

SONET

OC12>STS12>STS1 SPE>VT GROUP>VT1.5 SPE

TDM satellite configured in mode ts1-choc12-sfp or in mode ts4-choc3-sfp

Note: The E1 encapsulation in the ASAP MDA and in the channelized MDAs is compliant to G.704 and G.703. The G.703 feature allows a user to configure an unstructured E1 channel on deep channel MDAs and ASAP MDAs. In G.704, time slot 0 carries timing information by a service provider and therefore, only 31 slots are available to the end user. In G.703, all 32 time slots are available to the end user. Timing is provided by the end user.

A port ID for channels has one of the following syntax as applicable to channelization and mapping options where the port configuration syntax is slot/mda/port (Channelized port syntax examples).

Table 2. Channelized port syntax examples
Port ID for physical port speed
Channel speed OC12/STM4 OC3/STM1 DS3/E3

SONET/SDH

STS3/STM1

port.sts3-{1 to 4}

port.sts3

STS1/STM0

port.sts1-{1 to 4}.{1 to 3}

port.sts1-{1 to 3}

TUG3

port.tug3-{1 to 4}.{1 to 3}

port.tug3-{1 to 3}

VT15/VC1.11

port.vt15-{1 to 4}.{1 to 3}.{1 to 4}.{1 to 7}

port.vt15-{1 to 3}.{1 to 4}.{1 to 7}

VT2/VC12 1

port.vt2-{1 to 4}.{1 to 3}.{1 to 3}.{1 to 7}

port.vt2-{1 to 3}.{1 to 3}.{1 to 7}

TDM

DS1 in VT2

port.{1 to 4}.{1 to 3}.{1 to 3}.{1 to 7}

port.{1 to 3}.{1 to 3}.{1 to 7}

DS1 in VT15

port.{1 to 4}.{1 to 3}.{1 to 4}.{1 to 7}

port.{1 to 3}.{1 to 4}.{1 to 7}

E1 in VT2

port.{1 to 4}.{1 to 3}.{1 to 3}.{1 to 7}

port.{1 to 3}.{1 to 3}.{1 to 7}

1 Supported by TDM satellite.
Verify the MDA type

To ensure that you have a channel-capable MDA, verify that the MDA-type you are configuring by entering a show mda command.

The MDAs shown in the MDA Provisioned column in the following output are a 12-port channelized DS3 MDA (m12-ds3) on card 1, MDA slot 1, and a 1-port channelized OC12-SFP MDA (m1-choc12-sfp) on card 1, MDA slot 2.

Use the following command to display MDA slot 1.

show mda 1
===============================================================================
MDA 1/1
===============================================================================
Slot  Mda   Provisioned           Equipped              Admin     Operational  
            Mda-type              Mda-type              State     State        
-------------------------------------------------------------------------------
1     1     m12-ds3               m12-ds3               up        provisioned  
===============================================================================
===============================================================================
MDA 1/2
===============================================================================
Slot  Mda   Provisioned           Equipped              Admin     Operational  
            Mda-type              Mda-type              State     State        
-------------------------------------------------------------------------------
1     2     m1-choc12-sfp         m1-choc12-sfp         up        provisioned  
===============================================================================
Configuring a channelized OC-12-SFP port

Channelized OC-12 port structure shows the logic of the channelized OC-12 port configuration.

Figure 1. Channelized OC-12 port structure

The following shows an example to configure a channelized port on a 1-port channelized OC-12-SFP MDA.

A:node-2>config# port 5/2/1

At this level you must choose the tributary. When provisioning nodes on a channelized OC-12 MDA, you must provision the parent STS1-1 SONET path first.

The following example shows the output.

MD-CLI
[ex:/configure port 5/2/1]
A:admin@node-2# info
sonet-sdh {
        path sts1-1.1 {
            admin-state enable
        }
    }
classic CLI
A:node-2>config>port>sonet-sdh# info
----------------------------------------------
        sonet-sdh
            path sts1-1.1
                no shutdown
            exit
        exit
----------------------------------------------

To set the channelized mode on a port, the command option must be in a shutdown state. Clear channel uses out-of-band signaling, not in-band signaling, so the channel's entire bit rate is available. Channelized ports use in-band signaling and must be explicitly enabled.

MD-CLI
[ex:/configure port 5/2/1]
A:admin@node-2# info
    tdm {
        ds3 1.1.1 {
            admin-state enable
            channelized ds1
        }
    }
classic CLI
A:node-2>config>port# tdm
A:node-2>config>port>tdm# ds1 1.1.1 
A:node-2>config>port>tdm>ds1# shutdown
A:node-2>config>port>tdm>ds1# channelized ds1
A:node-2>config>port>tdm>ds1# no shutdown
A:node-2>config>port>tdm>ds1# exit

The following example shows the output.

MD-CLI
[ex:/configure port 5/2/1]
A:admin@node-2# info
    admin-state enable
    sonet-sdh {
        path sts3-1 {
            admin-state enable
        }
        path sts1-1.1 {
            admin-state enable
        }
    }
classic CLI
A:node-2>config>port# info
----------------------------------------------
        sonet-sdh
            path sts3-1
                no shutdown
            exit
            path sts1-1.1
                no shutdown
            exit
        exit
        no shutdown
----------------------------------------------

In the TDM context, up to 24 timeslots can be configured per channel group.

MD-CLI
[ex:/configure port 5/2/1 tdm ds1 1.1.1]
A:admin@node-2# info
    channel-group 1 {
        admin-state enable
        timeslot [1]
    }
    channel-group 2 {
        admin-state enable
        timeslot [2]
    }
classic CLI
A:node-2>config>port>tdm# info
----------------------------------------------
        sonet-sdh
            path sts3-1
                no shutdown
            exit
            path sts1-1.1
                no shutdown
            exit
        exit
        tdm
            ds1 ds1-1.1.1
                channel-group 1        (see SAP 5/2/1.1.1.1.1 below)
                    timeslots 1
                    no shutdown
                exit
                channel-group 2        (see SAP 5/2/1.1.1.1.2 below)
                    timeslots 2
                    no shutdown
                exit
                no shutdown
            exit
        exit
        no shutdown
----------------------------------------------

Services can be applied to the configured channelized ports. The following example shows the CLI usage to configure a customer IES service with interface SAPs on the channelized ports. See the 7450 ESS, 7750 SR, 7950 XRS, and VSR Services Overview Guide for information about how to configure services.

MD-CLI
[ex:/configure service ies "104"]
A:admin@node-2# info
    customer "1"
    interface "testA" {
        sap 5/2/1:1.1 {
        }
        ipv4 {
            primary {
                address 192.168.1.1
                prefix-length 24
            }
        }
    }
    interface "testB" {
        sap 5/2/1:1.2 {
        }
        ipv4 {
            primary {
                address 192.168.2.1
                prefix-length 24
            }
        }
    }
classic CLI
A:node-2>config>service>ies# info
----------------------------------------------
            interface "testA" create
                address 192.168.1.1/24
                sap 5/2/1.1.1.1.1 create
                exit
            exit
            interface "testB" create
                address 192.168.2.1/24
                sap 5/2/1.1.1.1.2 create
                exit
            exit
            no shutdown
----------------------------------------------

The following output shows the channelized ports applied to SAPs on the IES service configuration.

MD-CLI
[ex:/configure service ies "104"]
A:admin@node-2# info
    customer "1"
    interface "testA" {
        sap 5/2/1:1.1 {
        }
        ipv4 {
            primary {
                address 192.168.1.1
                prefix-length 24
            }
        }
    }
    interface "testB" {
        sap 5/2/1:1.2 {
        }
        ipv4 {
            primary {
                address 192.168.2.1
                prefix-length 24
            }
        }
    }
classic CLI
A:node-2>config>service>ies# info
----------------------------------------------
            interface "testA" create
                address 192.168.1.1/24
                sap 5/2/1.1.1.1.1 create
                exit
            exit
            interface "testB" create
                address 192.168.2.1/24
                sap 5/2/1.1.1.1.2 create
                exit
            exit
            no shutdown
----------------------------------------------

Configuring channelized STM1/OC3 command options

The following example shows basic syntax to configure channelized STM1/OC3 command options.

The following example shows the configuration output.

MD-CLI
[ex:/configure port 5/2/1]
A:admin@node-2# info
    admin-state enable
    sonet-sdh {
        framing sdh
        group tug3-1 {
            payload vt2
        }
        group tug3-3 {
            payload vt2
        }
        path sts3 {
            admin-state enable
            trace-string "H0-path"
        }
        path vt2-1.1.1 {
            admin-state enable
            trace-string "L0-path 3.7.3"
        }
        path vt2-3.7.3 {
            admin-state enable
        }
    }
    tdm {
        e1 1.1.1 {
            admin-state enable
            channel-group 1 {
                admin-state enable
                timeslot [2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32]
            }
            channel-group 2 {
                admin-state enable
                timeslot [2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32]
            }
        }
    }
classic CLI
A:node-2>config>port# info
------------------------------------------------------------------------------------
        sonet-sdh
            framing sdh
            path sts3
                trace-string "HO-path"
                no shutdown
            exit
            group tug3-1 payload vt2
            group tug3-3 payload vt2
            path vt2-1.1.1
                trace-string "LO-path 3.7.3"
                no shutdown
            exit
            path vt2-3.7.3
                no shutdown
            exit
        exit
        tdm
            e1 1.1.1
                channel-group 1
                    timeslots 2-32
                    no shutdown
                exit
                no shutdown
            exit
            e1 3.7.3
                channel-group 2
                    timeslots 2-32
                    no shutdown
                exit
                no shutdown
            exit
        exit
        no shutdown
----------------------------------------------
Example Cpipe port configurations

Before a Cpipe service can be provisioned, the following entities must be configured:

Configuring a DS1 port

The following shows an example of a DS1 port configured for CES:

To display information for the following DS1 port, use the following command.

show port 1/5/1.1.3.1
===============================================================================
TDM DS1 Interface
===============================================================================
Description        : DS1
Interface          : 1/5/1.1.3,1 
Type               : ds1                     Framing              : esf       
Admin Status       : up                      Oper Status          : up        
Physical Link      : yes                     Clock Source         : loop-timed
Signal Mode        : none                                                     
Last State Change  : 10/31/2006 14:23:12     Channel IfIndex      : 580943939 
Loopback           : none                    Invert Data          : false     
Remote Loop respond: false                   In Remote Loop       : false     
Load-balance-algo  : default                 Egr. Sched. Pol      : n/a       
BERT Duration      : N/A                     BERT Pattern         : none      
BERT Synched       : 00h00m00s               Err Insertion Rate   : 0         
BERT Errors        : 0                       BERT Status          : idle      
BERT Total Bits    : 0                                                        
Cfg Alarm          : ais los                                                  
Alarm Status       :                                                          
===============================================================================
Configuring a channel group

The following shows an example of a DS1 channel group configured for CES:

To display information for the DS1 channel group, use the following command.

show port 1/5/1.1.3.1
===============================================================================
TDM DS0 Chan Group
===============================================================================
Description        : DS0GRP
Interface          : 1/5/1.1.3.1                                              
TimeSlots          : 1-12                                                      
Speed              : 64                      CRC                  : 16         
Admin Status       : up                      Oper Status          : up         
Last State Change  : 10/31/2006 14:23:12     Chan-Grp IfIndex     : 580943940  
Configured mode    : access                  Encap Type           : cem        
Admin MTU          : 4112                    Oper MTU             : 4112       
Physical Link      : Yes                     Bundle Number        : none       
Idle Cycle Flags   : flags                   Load-balance-algo    : default    
Egr. Sched. Pol    : n/a                                                       
===============================================================================
A:sim216# 

Configuring OTU port command options

The following example shows an OTU port configuration:

MD-CLI
[ex:/configure port 3/2/1 otu]
A:admin@node-2# info detail
 ...
    fec enhanced
    otu2-lan-data-rate 11.049
    sd-threshold 7
    sf-threshold 5
    sf-sd-method fec
    report-alarm {
        loc true
        los true
        lof true
        lom true
        otu-ais false
        otu-ber-sf true
        otu-ber-sd false
        otu-bdi true
        otu-tim false
        otu-iae false
        otu-biae false
        fec-sf true
        fec-sd false
        fec-fail false
        fec-uncorr false
        odu-ais false
        odu-oci false
        odu-lck false
        odu-bdi false
        odu-tim false
        opu-plm false
    }
    ...
    path-monitoring {
        trail-trace-identifier {
         ## mismatch-reaction
            expected {
                auto-generated
             ## string
             ## bytes
            }
            transmit {
                auto-generated
             ## string
             ## bytes
            }
        }
    }
    payload-structure-identifier {
        payload {
            expected auto
         ## mismatch-reaction
            transmit auto
        }
    }
    section-monitoring {
        trail-trace-identifier {
         ## mismatch-reaction
            expected {
                auto-generated
             ## string
             ## bytes
            }
            transmit {
                auto-generated
             ## string
             ## bytes
            }
        }
    }
classic CLI
A:node-2>config>port>otu# info detail
----------------------------------------------
           otu2-lan-data-rate 11.049
           sf-sd-method fec
           sf-threshold 5
           sd-threshold 7
           fec enhanced
           no report-alarm otu-ais otu-ber-sd otu-tim otu-iae otu-biae fec-sd
           no report-alarm fec-fail fec-uncorr odu-ais odu-oci odu-lck odu-bdi
           no report-alarm odu-tim opu-plm
           report-alarm loc los lof lom otu-ber-sf otu-bdi fec-sf
           sm-tti
               tx auto-generated
               expected auto-generated
               no mismatch-reaction
           exit
           pm-tti
               tx auto-generated
               expected auto-generated
               no mismatch-reaction
           exit
           psi-payload
               tx auto
               expected auto
               no mismatch-reaction
           exit
----------------------------------------------

The following example shows the show port port-id otu detail for the preceding default OTU configuration.

show port 3/2/1 otu detail
===============================================================================
OTU Interface
===============================================================================
OTU Status         : Enabled                    FEC Mode         : enhanced
Async Mapping      : Disabled                   Data Rate        : 11.049 Gb/s
 
Cfg Alarms         : loc los lof lom otu-ber-sf otu-bdi fec-sf
Alarm Status       :
SF/SD Method       : FEC                        SF Threshold     : 1E-5
                                                SD Threshold     : 1E-7
 
SM-TTI Tx (auto)   : ALA-A:3/2/1/C44
SM-TTI Ex (bytes)  : (Not Specified)
SM-TTI Rx          : ALA-A:5/2/1/C34
OTU-TIM reaction   : none
 
PM-TTI Tx (auto)   : ALA-A:3/2/1/C44
PM-TTI Ex (bytes)  : (Not Specified)
PM-TTI Rx          : ALA-A:5/2/1/C34
ODU-TIM reaction   : none
 
PSI-PT Tx (auto)   : 0x03 (syncCbr)
PSI-PT Ex (auto)   : 0x03 (syncCbr)
PSI-PT Rx          : 0x03 (syncCbr)
OPU-PLM reaction   : none
===============================================================================
OTU Statistics
===============================================================================
Elapsed Seconds                                                10
-------------------------------------------------------------------------------
Near End Statistics                                     Count
-------------------------------------------------------------------------------
FEC Corrected 0s                                                0
FEC Corrected 1s                                                0
FEC Unrrectable Sub-rows                                        0
FEC ES                                                          0
FEC SES                                                         0
FEC UAS                                                         0
Pre-FEC BER                                             0.000E+00
Post-FEC BER                                            0.000E+00
-------------------------------------------------------------------------------
SM BIP8                                                         0
SM ES                                                           0
SM SES                                                          0
SM UAS                                                          0
SM-BIP8-BER                                             0.000E+00
-------------------------------------------------------------------------------
PM BIP8                                                         0
PM ES                                                           0
PM SES                                                          0
PM UAS                                                          0
PM-BIP8-BER                                             0.000E+00
-------------------------------------------------------------------------------
NPJ                                                             0
PPJ                                                             0
 
-------------------------------------------------------------------------------
Far End Statistics                                      Count
-------------------------------------------------------------------------------
SM BEI                                                          0
PM BEI                                                          0
===============================================================================

The window over which the Bit Error Rate (BER) determined is based on the configured threshold level. The higher the error rate the shorter the window and as the error rate decreases the window increases. Configured BER thresholds and window lengths lists the configured BER thresholds and corresponding window lengths.

Table 3. Configured BER thresholds and window lengths
Configured BER threshold Window length

10^-3

8ms

10^-4

8ms

10^-5

8ms

10^-6

13ms

10^-7

100ms

10^-8

333ms

10^-9

1.66s

Configuring LAG

LAG configurations should include at least two ports. Other considerations include:

  • A maximum of 64 ports (depending on the lag-id) can be included in a LAG. All ports in the LAG must share the port characteristics inherited from the primary port.

  • Autonegotiation must be disabled or set limited mode for ports that are part of a LAG to guarantee a specific port speed.

  • Ports in a LAG must be configured as full duplex.

The following example shows the LAG configuration output.

MD-CLI
[ex:/configure lag "lag-2"]
A:admin@node-2# info
    description "LAG2"
    mac-address 04:68:ff:00:00:01
    dynamic-cost true
    port-threshold {
        value 4
        action down
    }
    port 1/1/1 {
    }
    port 1/3/1 {
    }
    port 1/5/1 {
    }
    port 1/7/1 {
    }
    port 1/9/1 {
    }
 
classic CLI
A:node-2>config>lag# info detail
----------------------------------------------
        description "LAG2"
        mac 04:68:ff:00:00:01
        port  1/1/1
        port  1/3/1
        port  1/5/1
        port  1/7/1
        port  1/9/1
        dynamic-cost
        port-threshold 4 action down
----------------------------------------------
Configuring BFD on LAG links

BFD can be configured under the LAG context to create and establish the micro-BFD session per link after the LAG and associated links have been configured. An IP interface must be associated with the LAG or a VLAN within the LAG, if dot1q encapsulation is used, before the micro-BFD sessions can be established.

The following contexts are used to configure BFD over LAG links:

  • MD-CLI
    configure lag bfd-liveness family
  • classic CLI
     configure lag bfd family

Complete the following steps to enable and configure BFD over the individual LAG links:

When configuring the local and remote IP address for the BFD over LAG link sessions, the local-ip-address value should always match an IP address associated with the IP interface to which this LAG is bound.  In addition, the remote-ip-address value should match an IP address on the remote system and should also be in the same subnet as the local-ip-address.  If the LAG bundle is re-associated with a different IP interface, the local-ip-address and remote-ip-address values should be modified to match the new IP subnet. The local-ip-address and remote-ip-address values do not have to match a configured interface in the case of tagged LAG/ports.

The optional command options that can be configured for the BFD over LAG links include:

  • Transmit Interval

  • Receive Interval

  • Multiplier

  • Max-Wait-for-Up-Time, this command option controls how long a link remains active if BFD is enabled after the LAG and associated links are active and in a forwarding state.

  • Max-Time-Admin-Down, this command option controls how long the system waits before bringing the associated link out of service if an admin down message is received from the far-end.

  1. Enable BFD within the LAG context, which also enters the CLI into the BFD context.
  2. Configure the address family which is to be used for the micro BFD sessions. Only one address family can be configured per LAG.
  3. Configure the local-IP address to be used for the BFD sessions.
  4. Configure the remote-IP address to be used for the BFD sessions.
    MD-CLI
    [ex:/configure]
    A:admin@node-2# info
      ...
        lag "lag-2" {
            admin-state enable
            bfd-liveness {
                ipv4 {
                    admin-state enable
                    receive-interval 1000
                    transmit-interval 1000
                    local-ip-address 10.120.1.2
                    remote-ip-address 10.120.1.1
                }
            }
        }
    classic CLI
    A:node-2config>lag# info 
    ----------------------------------------------
            bfd
                family ipv4
                    local-ip-address 10.120.1.2
                    receive-interval 1000
                    remote-ip-address 10.120.1.1
                    transmit-interval 1000
                    no shutdown
                exit
            exit
            no shutdown
    

Configuring G.8031 protected Ethernet tunnels

Ethernet tunnel configuration can include at most two paths. Other considerations include:

  • A path contains one member port and one control-tag (backbone VLAN ID/BVID).

  • If the user wants to replace an existing member port or a control-tag, the whole path needs to be shutdown first. The alternate path is activated as a result keeping the traffic interruption to a minimum. Then the whole path must be deleted and re-created. To replace an existing member port or control tag, the whole path needs to be shutdown first. The alternate path is activated as a result keeping traffic interruption to a minimum. Then the whole path must be deleted, the alternate path precedence modified to primary before re-creating the new path.

  • The Ethernet tunnel inherits the configuration from the first member port. The following port-level configuration needs to be the same between member ports of an Ethernet tunnel:

    configure port ethernet access egress queue-group
    configure port access egress pool 
    configure port ethernet dot1q-etype 
    configure port ethernet qinq-etype
    configure port ethernet pbb-etype
    configure port ethernet mtu
    • MD-CLI
      configure port ethernet egress port-scheduler-policy
    • classic CLI
      configure port ethernet egress-scheduler-policy
  • The user can update these port command options only if the port is the sole member of an Ethernet tunnel. This means that in the example that follows, the user needs to remove port 1/1/4 and port 1/1/5 before being allowed to modify 1/1/1 for the preceding command options.

Note: The following information applies to the classic CLI.
classic CLI
A:node-2>config# eth-tunnel 1
    path 1
        member 1/1/1
    path 2
        member 1/1/4
A:node-2>config# eth-tunnel 2
    path 1
        member 1/1/1
    path 2
        member 1/1/5

The following example shows eth-tunnel configuration output.

classic CLI
A:node-2>config# port 1/1/1
ethernet
    encap-type dot1q
A:node-2>config> port 2/2/2
ethernet
    encap-type dot1q
A:node-2>config# eth-tunnel 1
    path 1
        member 1/1/1
        control-tag 100
        precedence primary
        eth-cfm
            mep 51 domain 1 association 1
            ccm-enable
            low-priority-defect allDef
            mac-address 00:AE:AE:AE:AE:AE
            control-mep
            no shutdown
    no shutdown
    path 2
        member 2/2/2 
        control-tag 200
        eth-cfm    
            mep 52 domain 1 association 2 
            ccm-enable
            low-priority-defect allDef
            mac-address 00:BE:BE:BE:BE:BE
            control-mep
            no shutdown
    no shutdown

Configuring connectors and connector ports

Some assemblies have support for QSFP28 or QSFP-DD transceiver modules. These modules have different variants, some of which provide multiple physical ports out of a single module (breakout modules). There is a QSFP28 breakout module that supports ten physical 10 Gb Ethernet ports. On assemblies that support these breakout variants, the front panel cages are modeled as connectors instead of as direct ports. The connector must be configured for the type of breakout module that is to be inserted and then the appropriate ports are created and can be configured. The options for breakout on specific connectors depend on both the card type and level (or XMA type and level). See the applicable installation guides for details.

The connector reference is in the format slot/mda/connector (for example, 1/1/c3) and the ports owned by the connector use the format slot/mda/connector/port. For example, in a 7750 SR-1 with the 6-port QSFP28 mda-e-xp installed in the first MDA slot, initially there are no ports available, only six connectors:

Use the following command to display the MDA information.

show mda
===============================================================================
MDA Summary
===============================================================================
Slot  Mda   Provisioned Type                            Admin     Operational
                Equipped Type (if different)            State     State
-------------------------------------------------------------------------------
1     1     me6-100gb-qsfp28                            up        up

Use the following command to display the port information.

show port
===============================================================================
Ports on Slot 1
===============================================================================
Port          Admin Link Port    Cfg  Oper LAG/ Port Port Port   C/QS/S/XFP/
Id            State      State   MTU  MTU  Bndl Mode Encp Type   MDIMDX
-------------------------------------------------------------------------------
1/1/c1        Up    No   Down                 - unkn unkn conn
1/1/c2        Up    No   Down                 - unkn unkn conn
1/1/c3        Up    No   Down                 - unkn unkn conn
1/1/c4        Up    No   Down                 - unkn unkn conn
1/1/c5        Up    No   Down                 - unkn unkn conn
1/1/c6        Up    No   Down                 - unkn unkn conn
===============================================================================

After configuring a module with four 10 Gb breakout ports in connector position 1/1/c1 and a module with one 100 Gb breakout port in connector position 1/1/c2, the physical ports are created.

Use the following commands to configure the port.

configure port 1/1/c1 connector breakout c4-10g
configure port 1/1/c2 connector breakout c1-100g

Use the following command to display the updated port information.

show port
===============================================================================
Ports on Slot 1
===============================================================================
Port          Admin Link Port    Cfg  Oper LAG/ Port Port Port   C/QS/S/XFP/
Id            State      State   MTU  MTU  Bndl Mode Encp Type   MDIMDX
-------------------------------------------------------------------------------
1/1/c1        Up    No   Link Up              - unkn unkn conn   40GBASE-SR4
1/1/c1/1      Down  No   Down    9212 9212    - netw null xgige  
1/1/c1/2      Down  No   Down    9212 9212    - netw null xgige  
1/1/c1/3      Down  No   Down    9212 9212    - netw null xgige  
1/1/c1/4      Down  No   Down    9212 9212    - netw null xgige  
1/1/c2        Down  No   Link Up              - unkn unkn conn   100GBASE-LR4
1/1/c2/1      Down  No   Down    1578 1578    - netw null cgige
1/1/c3        Up    No   Down                 - unkn unkn conn
1/1/c4        Up    No   Down                 - unkn unkn conn
1/1/c5        Up    No   Down                 - unkn unkn conn
1/1/c6        Up    No   Down                 - unkn unkn conn

These physical ports can now be used as Ethernet port references in other commands.

Use the following command to display the transceiver information that is shown under the connector.

show port 1/1/c1
===============================================================================
QSFP28 Connector
===============================================================================
Description        : QSFP28 Connector
Interface          : 1/1/c1
Admin State        : up
Oper State         : up
IfIndex            : 104939520
Last State Change  : 10/31/2017 13:23:22
Last Cleared Time  : N/A                        DDM Events       : Enabled
Breakout           : c4-10g

Transceiver Data

Transceiver Status : operational
Transceiver Type   : QSFP28
Model Number       : 3HE10551AARA01  NOK  IPU3BFVEAA
TX Laser Wavelength: 850 nm                     Diag Capable     : yes
Number of Lanes    : 4
Connector Code     : MPO 1x12                   Vendor OUI       : 44:7c:7f
Manufacture date   : 2017/03/12                 Media            : Ethernet
Serial Number      : INHAG8480890
Part Number        : TR-FC85S-NNO
Optical Compliance : 100GBASE-SR4 or 25GBASE-SR
Link Length support: 70m for OM3; 100m for OM4

===============================================================================
Transceiver Digital Diagnostic Monitoring (DDM)
===============================================================================
                              Value High Alarm  High Warn   Low Warn  Low Alarm
-------------------------------------------------------------------------------
Temperature (C)               +29.8     +80.0      +75.0       -5.0      -10.0
Supply Voltage (V)             3.29      3.63       3.46       3.14       2.97
===============================================================================

===============================================================================
Transceiver Lane Digital Diagnostic Monitoring (DDM)
===============================================================================
                                 High Alarm   High Warn    Low Warn   Low Alarm
-------------------------------------------------------------------------------
Lane Tx Bias Current (mA)              12.0        10.0         4.5         3.0
Lane Tx Output Power (dBm)             5.40        2.40       -8.40      -11.40
Lane Rx Optical Pwr (avg dBm)          5.40        2.40      -10.30      -13.30

-------------------------------------------------------------------------------
Lane ID Temp(C)/Alm       Tx Bias(mA)/Alm   Tx Pwr(dBm)/Alm   Rx Pwr(dBm)/Alm
-------------------------------------------------------------------------------
    1              -               7.1             -0.08             -4.56
    2              -               0.0/L-WA       -40.00/L-WA       -40.00/L-WA
    3              -               0.0/L-WA       -40.00/L-WA       -40.00/L-WA
    4              -               0.0/L-WA       -40.00/L-WA       -40.00/L-WA
===============================================================================

Use the following command to display the Ethernet-related items under the connector ports.

show port 1/1/c1/1
===============================================================================
Ethernet Interface
===============================================================================
Description        : 10-Gig Ethernet
Interface          : 1/1/c1/1                   Oper Speed       : 10 Gbps
Link-level         : Ethernet                   Config Speed     : N/A
Admin State        : up                         Oper Duplex      : full
Oper State         : up                         Config Duplex    : N/A
Physical Link      : Yes                        MTU              : 9212
Single Fiber Mode  : No                         Min Frame Length : 64 Bytes
IfIndex            : 104939521                  Hold time up     : 0 seconds
Last State Change  : 10/31/2017 13:23:23        Hold time down   : 0 seconds
Last Cleared Time  : N/A
Phys State Chng Cnt: 1                          RS-FEC Mode      : None

Configured Mode    : network                    Encap Type       : null
Dot1Q Ethertype    : 0x8100                     QinQ Ethertype   : 0x8100
PBB Ethertype      : 0x88e7
Ing. Pool % Rate   : 100                        Egr. Pool % Rate : 100
Ing. Pool Policy   : n/a
Egr. Pool Policy   : n/a
Net. Egr. Queue Pol: default
Egr. Sched. Pol    : n/a
HS Scheduler Plcy  : default
HS Port Pool Plcy  : default
Monitor Port Sched : Disabled
Monitor Agg Q Stats: Disabled
Auto-negotiate     : N/A                        MDI/MDX          : N/A
Oper Phy-tx-clock  : not-applicable
Accounting Policy  : None                       Collect-stats    : Disabled
Acct Plcy Eth Phys : None                       Collect Eth Phys : Disabled
Egress Rate        : Default                    Ingress Rate     : Default
Load-balance-algo  : Default                    LACP Tunnel      : Disabled
Access Bandwidth   : Not-Applicable             Booking Factor   : 100
Access Available BW: 0
Access Booked BW   : 0
Sflow              : Disabled

Suppress Threshold : 2000                       Reuse Threshold  : 1000
Max Penalties      : 16000                      Max Suppress Time: 20 seconds
Half Life          : 5 seconds

Down-when-looped   : Disabled                   Keep-alive       : 10
Loop Detected      : False                      Retry            : 120
Use Broadcast Addr : False

Sync. Status Msg.  : Disabled                   Rx Quality Level : N/A
Tx DUS/DNU         : Disabled                   Tx Quality Level : N/A
SSM Code Type      : sdh

Down On Int. Error : Disabled                   DOIE Tx Disable  : N/A

CRC Mon SD Thresh  : Disabled                   CRC Mon Window   : 10 seconds
CRC Mon SF Thresh  : Disabled

EFM OAM            : Disabled                   EFM OAM Link Mon : Disabled
Ignr EFM OAM State : False

Configured Address : 00:03:fa:2b:ef:1a
Hardware Address   : 00:03:fa:2b:ef:1a
Cfg Alarm          : remote local
===============================================================================

===============================================================================
Traffic Statistics
===============================================================================
                                                   Input                 Output
-------------------------------------------------------------------------------
Octets                                                 0                      0
Packets                                                0                      0
Errors                                                 0                      0
Utilization (300 seconds)                          0.00%                  0.00%

===============================================================================
Port Statistics
===============================================================================
                                                   Input                 Output
-------------------------------------------------------------------------------
Unicast Packets                                        0                      0
Multicast Packets                                      0                      0
Broadcast Packets                                      0                      0
Discards                                               0                      0
Unknown Proto Discards                                 0
===============================================================================

===============================================================================
Ethernet-like Medium Statistics
===============================================================================
Alignment Errors :                   0  Sngl Collisions  :                   0
FCS Errors       :                   0  Mult Collisions  :                   0
SQE Test Errors  :                   0  Late Collisions  :                   0
CSE              :                   0  Excess Collisns  :                   0
Too long Frames  :                   0  Int MAC Tx Errs  :                   0
Symbol Errors    :                   0  Int MAC Rx Errs  :                   0
In Pause Frames  :                   0  Out Pause Frames :                   0
===============================================================================

Configuring GNSS ports

Some 7750 SR FP5 CPMs are equipped with an integrated GNSS receiver and GNSS RF port for retrieval and recovery of GPS and Galileo signals.

Note: GPS signal recovery must always be enabled in the system when using the GNSS receiver.

Use the commands in the following context to configure integrated GNSS RF ports including antenna-cable delay, signal recovery, and elevation-mask angle.

configure port gnss