The 16-Port10-Gigabit Ethernet SFP+ line card is a Small Form Factor (SFP transceiver) optical line card introduced in Cisco IOS XR Release 3.9.1 on the Cisco ASR 9000 Series Router. The 16-Port10-Gigabit Ethernet SFP+ line card supports all of the Gigabit Ethernet commands and configurations currently supported on the router.

The 16-Port10-Gigabit Ethernet SFP+ line card is compatible with all existing Cisco ASR 9000 Series Router line cards, route/switch processors (RSPs), and chassis.

The Cisco ASR 9000 Series modular line cards provides a flexible solution to support multiple combinations of Ethernet ports, all in a single slot of the Cisco ASR 9000 Series Aggregation Services Routers. Modular line cards support a wide range of interfaces and densities offering the benefits of network scalability with lower initial costs and ease of upgrades.

The Cisco ASR 9000 Series modular line cards are designed for the Cisco ASR9000 Series Router which accepts pluggable modules. It allows you to cost effectively address lower density Gigabit Ethernet,10-Gigabit Ethernet, and 40-Gigabit Ethernet traffic. This line card is developed based on the ASR 9000 Enhanced Ethernet Network Processor (NP) and allows you to configure different interface types and also conserve chassis slots.

The Cisco ASR 9000 Series modular line cards accept two Ethernet Plugs (EP). Each Ethernet Plug provides optics, and support circuitry in order to provide GE, 10GE or 40GE ports.

The two versions of Modular Line Cards are:

• Cisco ASR 9000 Mod80 Modular Line Card – 2 ASR 9000 Enhanced Ethernet Network Processors (NP) which supports 2 pluggable Ethernet Plugs(EP), and 1 NP for each EP.

• Cisco ASR 9000 Mod160 Modular Line Card – 4 ASR 9000 Enhanced Ethernet Network Processors which supports 2 pluggable Ethernet Plugs, and 2 NPs for each EP.

Note	A9K-MPA-20X1GE supports a speed of 10Mbps or 100Mbps when using only GLC-TE optics, regardless of MOD models.

This table describes the default interface configuration parameters that are present when an interface is enabled on a Gigabit Ethernet or 10-Gigabit Ethernet modular services card and its associated PLIM.

Note

You must use the shutdown command to bring an interface administratively down. The interface default is no shutdown . When a modular services card is first inserted into the router, if there is no established preconfiguration for it, the configuration manager adds a shutdown item to its configuration. This shutdown can be removed only be entering the no shutdown command.

Layer 2 Virtual Private Network (L2VPN) connections emulate the behavior of a LAN across an L2 switched, IP or MPLS-enabled IP network, allowing Ethernet devices to communicate with each other as if they were connected to a common LAN segment.

The L2VPN feature enables service providers (SPs) to provide Layer 2 services to geographically disparate customer sites. Typically, an SP uses an access network to connect the customer to the core network. On the Cisco ASR 9000 Series Router, this access network is typically Ethernet.

Traffic from the customer travels over this link to the edge of the SP core network. The traffic then tunnels through an L2VPN over the SP core network to another edge router. The edge router sends the traffic down another attachment circuit (AC) to the customer's remote site.

On the Cisco ASR 9000 Series Router, an AC is an interface that is attached to an L2VPN component, such as a bridge domain, pseudowire, or local connect.

The L2VPN feature enables users to implement different types of end-to-end services.

Cisco IOS XR Software supports a point-to-point end-to-end service, where two Ethernet circuits are connected together. An L2VPN Ethernet port can operate in one of two modes:

• Port Mode—In this mode, all packets reaching the port are sent over the PW (pseudowire), regardless of any VLAN tags that are present on the packets. In VLAN mode, the configuration is performed under the l2transport configuration mode.

• VLAN Mode—Each VLAN on a CE (customer edge) or access network to PE (provider edge) link can be configured as a separate L2VPN connection (using either VC type 4 or VC type 5). In VLAN mode, the configuration is performed under the individual subinterface.

  Note	The system sets a limit of 24K single vlan tags per NP and a 64K LC limit on the following line cards: A9K-MOD400-SE A9K-MOD400-CM A9K-MOD200-SE/CM Cisco ASR 9000 Series 24-port and 48-port dual-rate 10GE/1GE SE/CM A9K-8x100 SE/CM A99-8x100 SE/CM

Switching can take place in three ways:

• AC-to-PW—Traffic reaching the PE is tunneled over a PW (and conversely, traffic arriving over the PW is sent out over the AC). This is the most common scenario.

• Local switching—Traffic arriving on one AC is immediately sent out of another AC without passing through a pseudowire.

• PW stitching—Traffic arriving on a PW is not sent to an AC, but is sent back into the core over another PW.

Keep the following in mind when configuring L2VPN on an Ethernet interface:

• L2VPN links support QoS (Quality of Service) and MTU (maximum transmission unit) configuration.

• If your network requires that packets are transported transparently, you may need to modify the packet’s destination MAC (Media Access Control) address at the edge of the Service Provider (SP) network. This prevents the packet from being consumed by the devices in the SP network.

Use the show interfaces command to display AC and PW information.

To configure a point-to-point pseudowire xconnect on an AC, refer to these documents:

• Cisco ASR 9000 Series Aggregation Services Router L2VPN and Ethernet Services Configuration Guide.

• Cisco ASR 9000 Series Aggregation Services Router L2VPN and Ethernet Services Command Reference

To attach Layer 2 service policies, such as QoS, to the Ethernet interface, refer to the appropriate Cisco IOS XR software configuration guide.

The Gigabit Ethernet interfaces support the following protocol standards:

These standards are further described in the sections that follow.

A MAC address is a unique 6-byte address that identifies the interface at Layer 2.

The MAC address accounting feature provides accounting information for IP traffic based on the source and destination MAC addresses on LAN interfaces. This feature calculates the total packet and byte counts for a LAN interface that receives or sends IP packets to or from a unique MAC address. It also records a time stamp for the last packet received or sent.

These statistics are used for traffic monitoring, debugging and billing. For example, with this feature you can determine the volume of traffic that is being sent to and/or received from various peers at NAPS/peering points. This feature is currently supported on Ethernet, FastEthernet, and bundle interfaces and supports Cisco Express Forwarding (CEF), distributed CEF (dCEF), flow, and optimum switching.

Note	A maximum of 512 MAC addresses per trunk interface are supported for MAC address accounting.

The Ethernet maximum transmission unit (MTU) is the size of the largest frame, minus the 4-byte frame check sequence (FCS), that can be transmitted on the Ethernet network. Every physical network along the destination of a packet can have a different MTU.

Cisco IOS XR software supports two types of frame forwarding processes:

• Fragmentation for IPv4 packets–In this process, IPv4 packets are fragmented as necessary to fit within the MTU of the next-hop physical network.

  Note	IPv6 does not support fragmentation.

• MTU discovery process determines largest packet that size–This process is available for all IPv6 devices, and for originating IPv4 devices. In this process, the originating IP device determines the size of the largest IPv6 or IPv4 packet that can be sent without being fragmented. The largest packet is equal to the smallest MTU of any network between the IP source and the IP destination devices. If a packet is larger than the smallest MTU of all the networks in its path, that packet is fragmented as necessary. This process ensures that the originating device does not send an IP packet that is too large.

Jumbo frame support is automatically enabled for frames that exceed the standard frame size. The default value is 1514 for standard frames and 1518 for 802.1Q tagged frames. These numbers exclude the 4-byte frame check sequence (FCS).

You can set the data traffic with jumbo frames of a maximum size of 9646 bytes for the line cards that are mentioned in this section.

Note	ASIC on 9000v considers all the packets greater than 1514 byte as oversized frame.

On the following line cards, you can configure a maximum MTU size of 9646.

• A99-32X100GE-CM

• A99-32X100GE-DENS

• A99-32X100GE-SE

• A99-32X100GE-TR

• A99-32X100GE-X-CM

• A99-32X100GE-X-SE

• A99-32X100GE-X-TR

• A99K-48x10GE-SE

• A99K-48x10GE-SE-TAA

• A99K-48x10GE-TAA

• A99K-48x10GE-TR

• A99K-48x10GE-TR-TAA

• A9K-20HG-FLEX-CM

• A9K-20HG-FLEX-SE

• A9K-20HG-FLEX-TR

• A9K-48x10GE-SE

• A9K-48x10GE-SE-TAA

• A9K-48x10GE-TAA

• A9K-48x10GE-TR

• A9K-48x10GE-TR-TAA

• A9K-8HG-FLEX-CM

• A9K-8HG-FLEX-SE

• A9K-8HG-FLEX-TR

When the MTU size is larger, more data can be sent in fewer number of packets. As each packet contains a header, a small number of packets means less header data to be transmitted. Thus, larger size MTU helps in transmitting more actual data faster and efficiently.

To determine an optimal MTU size for your network, you can use the ping test. The Ping command tests the reachability of devices in a network using the echo request and reply messages within the Internet Control Message Protocol (ICMP). Within the router, the supported maximum local ping size is 9580 for these LCs.

For the list of line cards mentioned in this section, the MTU size of the Cisco ASR 9000 platform control-packets is 9580.

For details of configuring the MTU size, see Configuring MTU.

The flow control used on 10-Gigabit Ethernet interfaces consists of periodically sending flow control pause frames. It is fundamentally different from the usual full- and half-duplex flow control used on standard management interfaces. Flow control can be activated or deactivated for ingress traffic only. It is automatically implemented for egress traffic.

A VLAN is a group of devices on one or more LANs that are configured so that they can communicate as if they were attached to the same wire, when in fact they are located on a number of different LAN segments. Because VLANs are based on logical instead of physical connections, it is very flexible for user and host management, bandwidth allocation, and resource optimization.

The IEEE's 802.1Q protocol standard addresses the problem of breaking large networks into smaller parts so broadcast and multicast traffic does not consume more bandwidth than necessary. The standard also helps provide a higher level of security between segments of internal networks.

The 802.1Q specification establishes a standard method for inserting VLAN membership information into Ethernet frames.

The Virtual Router Redundancy Protocol (VRRP) eliminates the single point of failure inherent in the static default routed environment. VRRP specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VPN concentrators on a LAN. The VRRP VPN concentrator controlling the IP addresses associated with a virtual router is termed as the primary concentrator, and forwards packets sent to those IP addresses. When the primary concentrator becomes unavailable, a backup VPN concentrator takes over.

For more information on VRRP, see the Implementing VRRP module of Cisco ASR 9000 Series Router IP Addresses and Services Configuration Guide.

Hot Standby Routing Protocol (HSRP) is a proprietary protocol from Cisco. HSRP is a routing protocol that provides backup to a router in the event of failure. Several routers are connected to the same segment of an Ethernet, FDDI, or token-ring network and work together to present the appearance of a single virtual router on the LAN. The routers share the same IP and MAC addresses and therefore, in the event of failure of one router, the hosts on the LAN are able to continue forwarding packets to a consistent IP and MAC address. The transfer of routing responsibilities from one device to another is transparent to the user.

HSRP is designed to support non disruptive switchover of IP traffic in certain circumstances and to allow hosts to appear to use a single router and to maintain connectivity even if the actual first hop router they are using fails. In other words, HSRP protects against the failure of the first hop router when the source host cannot learn the IP address of the first hop router dynamically. Multiple routers participate in HSRP and in concert create the illusion of a single virtual router. HSRP ensures that one and only one of the routers is forwarding packets on behalf of the virtual router. End hosts forward their packets to the virtual router.

The router forwarding packets is known as the active router. A standby router is selected to replace the active router should it fail. HSRP provides a mechanism for determining active and standby routers, using the IP addresses on the participating routers. If an active router fails a standby router can take over without a major interruption in the host's connectivity.

HSRP runs on top of User Datagram Protocol (UDP), and uses port number 1985. Routers use their actual IP address as the source address for protocol packets, not the virtual IP address, so that the HSRP routers can identify each other.

For more information on HSRP, see the Implementing HSRP module of Cisco ASR 9000 Series Router Cisco IOS XR

Link autonegotiation ensures that devices that share a link segment are automatically configured with the highest performance mode of interoperation. Use the negotiation auto command in interface configuration mode to enable link autonegotiation on an Ethernet interface. On line card Ethernet interfaces, link autonegotiation is disabled by default.

Note	The negotiation auto command is available on Gigabit Ethernet interfaces only.

This table describes the performance of the system for different combinations of the speed modes. The specified command produces the resulting system action, provided that you have configured autonegotiation on the interface.

Fast Ethernet interfaces must be continuously monitored in order to detect any link that is not working due to BER errors (bit error rate) and to bring down the interface connected to that link. The Fast Polling feature polls interfaces at a fast rate and brings down the interface in case of BER errors, thereby minimizing service impact. The Fast Polling feature for WAN-PHY reduces convergence time to 150 ms on the ASR 9000 Enhanced Ethernet line card and the ASR 9000 High Density 100GE Ethernet line cards with 10G and higher rate ports.

To configure the fast polling for WAN-PHY on ASR 9000 Enhanced Ethernet line card, use the wanphy poll-timer value-in-milliseconds command in configuration mode.

The fast polling for WAN-PHY on ASR 9000 High Density 100GE Ethernet line card is enabled by default.

This feature helps in early detection of a link loss between two devices and prevents any service impact. To enable this feature user must configure a receiving optical power threshold value. Whenever the receiving power crosses the threshold, the power degrade alarm is raised. The alram resets after the power exceeds threshold value by 2db.

For example, consider you have configured receiving optical power threshold value to -10db. When the input power on the interface reduces below -10db due to fiber degradation, then the optical power alarm is raised. After fiber degradation is attended power value will improve. Once the power value crosses above -8db, that is 2db more than threshold configured, then the alarm resets.

To configure the receiving power optical threshold value, use optical-power alarm rx <value in db> command in interface configuration mode.

Use this show command to view the alarm status:

• show controllers <ethernet-interface> internal

Use this command to view threshold value configured, and the minimum and maximum threshold value:

• show controllers <ethernet-interface> control

In Cisco IOS XR, interfaces are, by default, main interfaces. A main interface is also called a trunk interface, which is not to be confused with the usage of the word trunk in the context of VLAN trunking.

There are three types of trunk interfaces:

• Physical

• Bundle

On the Cisco ASR 9000 Series Router, physical interfaces are automatically created when the router recognizes a card and its physical interfaces. However, bundle interfaces are not automatically created. They are created when they are configured by the user.

The following configuration samples are examples of trunk interfaces being created:

• interface gigabitethernet 0/5/0/0

• interface bundle-ether 1

A subinterface is a logical interface that is created under a trunk interface.

To create a subinterface, the user must first identify a trunk interface under which to place it. In the case of bundle interfaces, if one does not already exist, a bundle interface must be created before any subinterfaces can be created under it.

The user then assigns a subinterface number to the subinterface to be created. The subinterface number must be a positive integer from zero to some high value. For a given trunk interface, each subinterface under it must have a unique value.

Subinterface numbers do not need to be contiguous or in numeric order. For example, the following subinterfaces numbers would be valid under one trunk interface:

1001, 0, 97, 96, 100000

Subinterfaces can never have the same subinterface number under one trunk.

In the following example, the card in slot 5 has trunk interface, GigabitEthernet 0/5/0/0. A subinterface, GigabitEthernet 0/5/0/0.0, is created under it.

RP/0/RSP0/CPU0:router#  conf
Mon Sep 21 11:12:11.722 EDT
RP/0/RSP0/CPU0:router(config)#  interface GigabitEthernet0/5/0/0.0
RP/0/RSP0/CPU0:router(config-subif)# encapsulation dot1q 100
RP/0/RSP0/CPU0:router(config-subif)# commit

RP/0/RSP0/CPU0:Sep 21 11:12:34.819 : config[65794]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'root'. Use 'show configuration commit changes 1000000152' to view the changes.

RP/0/RSP0/CPU0:router(config-subif)# end

RP/0/RSP0/CPU0:Sep 21 11:12:35.633 : config[65794]: %MGBL-SYS-5-CONFIG_I : Configured from console by root
RP/0/RSP0/CPU0:router#

The show run command displays the trunk interface first, then the subinterfaces in ascending numerical order.

RP/0/RSP0/CPU0:router# show run | begin GigabitEthernet0/5/0/0
Mon Sep 21 11:15:42.654 EDT
Building configuration...
interface GigabitEthernet0/5/0/0
 shutdown
!
interface GigabitEthernet0/5/0/0.0
 encapsulation dot1q 100
!
interface GigabitEthernet0/5/0/1
 shutdown
!

When a subinterface is first created, the Cisco ASR 9000 Series Router recognizes it as an interface that, with few exceptions, is interchangeable with a trunk interface. After the new subinterface is configured further, the show interface command can display it along with its unique counters:

The following example shows the display output for the trunk interface, GigabitEthernet 0/5/0/0, followed by the display output for the subinterface GigabitEthernet 0/5/0/0.0.

RP/0/RSP0/CPU0:router# show interface gigabitEthernet 0/5/0/0
Mon Sep 21 11:12:51.068 EDT
GigabitEthernet0/5/0/0 is administratively down, line protocol is administratively down.
  Interface state transitions: 0
  Hardware is GigabitEthernet, address is 0024.f71b.0ca8 (bia 0024.f71b.0ca8)
  Internet address is Unknown
  MTU 1514 bytes, BW 1000000 Kbit
     reliability 255/255, txload 0/255, rxload 0/255
  Encapsulation 802.1Q Virtual LAN,
  Full-duplex, 1000Mb/s, SXFD, link type is force-up
  output flow control is off, input flow control is off
  loopback not set,
  ARP type ARPA, ARP timeout 04:00:00
  Last input never, output never
  Last clearing of "show interface" counters never
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 total input drops
     0 drops for unrecognized upper-level protocol
     Received 0 broadcast packets, 0 multicast packets
              0 runts, 0 giants, 0 throttles, 0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 total output drops
     Output 0 broadcast packets, 0 multicast packets
     0 output errors, 0 underruns, 0 applique, 0 resets
     0 output buffer failures, 0 output buffers swapped out
     0 carrier transitions


RP/0/RSP0/CPU0:router# show interface gigabitEthernet0/5/0/0.0
Mon Sep 21 11:12:55.657 EDT
GigabitEthernet0/5/0/0.0 is administratively down, line protocol is administratively down.
  Interface state transitions: 0
  Hardware is VLAN sub-interface(s), address is 0024.f71b.0ca8
  Internet address is Unknown
  MTU 1518 bytes, BW 1000000 Kbit
     reliability 255/255, txload 0/255, rxload 0/255
  Encapsulation 802.1Q Virtual LAN, VLAN Id 100,  loopback not set,
  ARP type ARPA, ARP timeout 04:00:00
  Last input never, output never
  Last clearing of "show interface" counters never
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 total input drops
     0 drops for unrecognized upper-level protocol
     Received 0 broadcast packets, 0 multicast packets
     0 packets output, 0 bytes, 0 total output drops
     Output 0 broadcast packets, 0 multicast packets

This example shows two interfaces being created at the same time: first, the bundle trunk interface, then a subinterface attached to the trunk:

RP/0/RSP0/CPU0:router# conf
Mon Sep 21 10:57:31.736 EDT
RP/0/RSP0/CPU0:router(config)# interface Bundle-Ether1
RP/0/RSP0/CPU0:router(config-if)# no shut
RP/0/RSP0/CPU0:router(config-if)# interface bundle-Ether1.0
RP/0/RSP0/CPU0:router(config-subif)# encapsulation dot1q 100
RP/0/RSP0/CPU0:router(config-subif)# commit
RP/0/RSP0/CPU0:Sep 21 10:58:15.305 : config[65794]: %MGBL-CONFIG-6-DB_COMMIT : C
onfiguration committed by user 'root'. Use 'show configuration commit changes 10
00000149' to view the changes.
RP/0/RSP0/CPU0:router# show run | begin Bundle-Ether1
Mon Sep 21 10:59:31.317 EDT
Building configuration..
interface Bundle-Ether1
!
interface Bundle-Ether1.0
 encapsulation dot1q 100
!

You delete a subinterface using the no interface command.

RP/0/RSP0/CPU0:router#
RP/0/RSP0/CPU0:router# show run | begin GigabitEthernet0/5/0/0
Mon Sep 21 11:42:27.100 EDT
Building configuration...
interface GigabitEthernet0/5/0/0
 negotiation auto
!
interface GigabitEthernet0/5/0/0.0
 encapsulation dot1q 100
!
interface GigabitEthernet0/5/0/1
 shutdown
!
RP/0/RSP0/CPU0:router# conf
Mon Sep 21 11:42:32.374 EDT
RP/0/RSP0/CPU0:router(config)# no interface GigabitEthernet0/5/0/0.0
RP/0/RSP0/CPU0:router(config)# commit
RP/0/RSP0/CPU0:Sep 21 11:42:47.237 : config[65794]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'root'. Use 'show configuration commit changes 1000000159' to view the changes.
RP/0/RSP0/CPU0:router(config)# end
RP/0/RSP0/CPU0:Sep 21 11:42:50.278 : config[65794]: %MGBL-SYS-5-CONFIG_I : Configured from console by root
RP/0/RSP0/CPU0:router# show run | begin GigabitEthernet0/5/0/0
Mon Sep 21 11:42:57.262 EDT
Building configuration...
interface GigabitEthernet0/5/0/0
 negotiation auto
!
interface GigabitEthernet0/5/0/1
 shutdown
!

Cisco IOS XR Software provides support for SyncE-capable Ethernet on the Cisco ASR 9000 Series Router. Frequency Synchronization provides the ability to distribute precision clock signals around the network. Highly accurate timing signals are initially injected into the Cisco ASR 9000 Series Router in the network from an external timing technology (such as Cesium atomic clocks, or GPS), and used to clock the physical interfaces of the router. Peer routers can then recover this precision frequency from the line, and also transfer it around the network. This feature is traditionally applicable to SONET/SDH networks, but is now provided over Ethernet for Cisco ASR 9000 Series Aggregation Services Routers with Synchronous Ethernet capability. For more information, see Cisco ASR 9000 Series Aggregation Services Router System Management Configuration Guide.

Note	LLDP is not supported on the FP-X line cards.

The Cisco Discovery Protocol (CDP) is a device discovery protocol that runs over Layer 2 (the Data Link layer) on all Cisco-manufactured devices (routers, bridges, access servers, and switches). CDP allows network management applications to automatically discover and learn about other Cisco devices connected to the network.

To support non-Cisco devices and to allow for interoperability between other devices, the Cisco ASR 9000 Series Router also supports the IEEE 802.1AB LLDP. LLDP is also a neighbor discovery protocol that is used for network devices to advertise information about themselves to other devices on the network. This protocol runs over the Data Link Layer, which allows two systems running different network layer protocols to learn about each other.

LLDP supports a set of attributes that it uses to learn information about neighbor devices. These attributes have a defined format known as a Type-Length-Value (TLV). LLDP supported devices can use TLVs to receive and send information to their neighbors. Details such as configuration information, device capabilities, and device identity can be advertised using this protocol.

In addition to the mandatory TLVs (Chassis ID, Port ID, and Time-to-Live), the router also supports the following basic management TLVs, which are optional:

• Port Description

• System Name

• System Description

• System Capabilities

• Management Address

These optional TLVs are automatically sent when LLDP is active, but you can disable them as needed using the lldp tlv-select disable command.

When you enable LLDP globally, all interfaces that support LLDP are automatically enabled for both transmit and receive operations. However, if you want to enable LLDP per interface, perform the following configuration steps:

1. RP/0/RSP0/CPU0:ios(config)# int gigabitEthernet 0/2/0/0

2. RP/0/RSP0/CPU0:ios(config-if)# no sh

3. RP/0/RSP0/CPU0:ios(config-if)#commit

4. RP/0/RSP0/CPU0:ios(config-if)#lldp ?

5. RP/0/RSP0/CPU0:ios(config-if)#lldp enable

6. RP/0/RSP0/CPU0:ios(config-if)#commit

Running configuration

RP/0/RSP0/CPU0:ios#sh running-config  
Wed Jun 27 12:40:21.274 IST
Building configuration...
!! IOS XR Configuration 0.0.0
!! Last configuration change at Wed Jun 27 00:59:29 2018 by UNKNOWN
!
interface GigabitEthernet0/1/0/0
 shutdown
!
interface GigabitEthernet0/1/0/1
 shutdown
!
interface GigabitEthernet0/1/0/2
 shutdown
!
interface GigabitEthernet0/2/0/0
 Shutdown
!
interface GigabitEthernet0/2/0/1
 shutdown
!
interface GigabitEthernet0/2/0/2
 shutdown
!
end

Verification

Verifying the config
==================
RP/0/RSP0/CPU0:ios#sh lldp interface <===== LLDP enabled only on GigEth0/2/0/0
Wed Jun 27 12:43:26.252 IST


GigabitEthernet0/2/0/0:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME
RP/0/RSP0/CPU0:ios# 

RP/0/RSP0/CPU0:ios# show lldp neighbors 
Wed Jun 27 12:44:38.977 IST
Capability codes:
        (R) Router, (B) Bridge, (T) Telephone, (C) DOCSIS Cable Device
        (W) WLAN Access Point, (P) Repeater, (S) Station, (O) Other

Device ID       Local Intf          Hold-time  Capability     Port ID
ios             Gi0/2/0/0           120        R               Gi0/2/0/0       <====== LLDP enabled only on GigEth0/2/0/0 and neighborship seen for the same.

Total entries displayed: 1

RP/0/RSP0/CPU0:ios#

Unidirectional Link Routing(UDLR) feature allows a port to unidirectionally transmit or receive traffic. Therefore, instead of using two strands of fiber for a full-duplex Gigabit Ethernet or 10Gigabit Ethernet port, UDLR uses only one strand of fiber that either transmits or receives the one-way traffic depending on the configuration. This improves the effectiveness and also enables you to double the bandwidth with existing fiber infrastructure.

Cisco IOS XR Software supports Unidirectional Link Routing feature on these line cards:

• A9K- 24T-TR 24-port 10 Gigabit Ethernet line cards

• A9K- 24T-SE 24-port 10 Gigabit Ethernet line cards

• A9K- 36T-TR 36-port 10 Gigabit Ethernet line cards

• A9K- 36T-SE 36-port 10 Gigabit Ethernet line cards

UDLR is used for applications such as video streaming, where most of the traffic is sent as unacknowledged unidirectional video broadcast streams.

This section provides the following configuration procedures:

Note	LLDP is not supported on the FP-X line cards.

This section includes the following configuration topics for LLDP:

Note	Oversubscription will be supported on these line cards in a future release of IOS XR 6.2.x train.

The 24-port and 48-port dual-rate line cards support GE and 10GE speeds.

Note	See 24-Port 10-Gigabit Ethernet/Gigabit Ethernet Line Card with SFP+ or SFP and 48-Port 10-Gigabit Ethernet/Gigabit Ethernet Line Card with SFP+ or SFP sections in the Cisco ASR 9000 Series Aggregation Services Router Ethernet Line Card Installation Guide for information on the line cards.

Note	The 24-port line card has a single Network Processor Unit (NPU). The 48-port line card has two NPUs (one for each group of 24 ports). Configuring more than 20x10GE ports per NPU could result in line drops across all ports, depending on the packet size and traffic type.

To configure the port mode for either GE or 10GE, use the hw-module location location port-mode run-lengthxspeed[,run-lengthxspeed] command, where:

• run-length – The number of consecutive same-speed ports, divisible by 4. Valid values are:

  • 24-port line card: 4, 8, 12, 16, 20, 24

  • 48-port line card: 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48

• speed – Valid values are 1 (for GE) or 10 (for 10GE)

Note

Observe the following restrictions: The total for run-length must equal the total number of ports (either 24 or 48). If you configure the speed of the first port in a set of 12 ports to 1 (GE), then all 12 ports in that set must be 1G (for example: 12x1). If you configure the speed of the first port in a set of 12 ports to 10 (10G), then ports can be mixed in groups of 4 (for example: 4x10,4x1,4x10; or 8x10,4x1; or 12x10). The following example is a valid port-mode configuration on the 48-port line card: port-mode 4x10,8x1,12x10,12x1,12x10 The following example is not a valid port-mode configuration on the 48-port line card: port-mode 4x1,8x10,12x10,12x1,12x10

The following procedure is for configuring the port speed on the 48-port 10-Gigabit Ethernet/Gigabit Ethernet Line Cards:

1. Enter global configuration mode and specify that the console terminal will be the source of the configuration commands:

   
   RP/0/RSP0/CPU0:router# configure terminal
   
   

2. Specify the port mode:

   
   RP/0/RSP0/CPU0:router(config)# hw-module location 0/5/CPU0 port-mode 4x10,8x1,12x10,12x1,12x10
   
   

3. Enter the commit command to commit all changes you made to the running configuration:

   RP/0/RSP0/CPU0:router(config)# commit

A dual-mode optic operates in two modes. You can convert the speed of a dual-mode optic from one to another using the hw-module location node-id port port number breakout interface command.

Cisco 100G and 40G SR-BiDi QSFP Transceiver optic (QSFP-40/100G-SRBD) is a dual-mode optic. By default, the optic works in 100G mode.

In 40-Gbps mode, the Cisco QSFP 40/100-Gbps BiDi transceiver supports link lengths of 100 and 150 meters on laser-optimized OM3 and OM4 multimode fibers, respectively. In 100-Gbps mode, it supports 70 and 100 meters on OM3 and OM4, respectively.

FEC is not supported on QSFP-40/100G-SRBD optic.

Support for QSFP-40/100G-SRBD optic is available on following hardware:

• Cisco ASR 9901 Router

  Note	Configuring breakout on port 20 will shut down ports 10 and 11. Configuring breakout on port 21 will shut down ports 24 and 25. Use the no shutdown command to reenable these ports.

• Cisco ASR 9000 12-Port 100GE line card (A99-12x100GE)

• Cisco ASR 9000 4-Port 100GE line card (A9K-4x100GE)

RP/0/RSP0/CPU0:router (config)# hw-module location 0/0/CPU0 port 21 breakout 1xFortyGigE
RP/0/RSP0/CPU0:router (config)# commit

RP/0/RSP0/CPU0:router# show controllers FortyGigE 0/0/0/21/0 internal 
Wed Nov 11 06:34:26.861 UTC

Internal data for interface: FortyGigE0/0/0/21/0
Subport Number : 0
Port Number : 21
Bay Number : 0
Ifinst : 6
Ifinst Subport : 21
Board Type : 0x003d1013
 
Bandwidth(Kbps) : 40000000
Transport mode : LAN
BIA MAC addr : badb.ad03.a84d
Oper. MAC addr : badb.ad03.a84d
Egress MAC addr : badb.ad03.a84d
Port Available : true
Status polling is : enabled
Status events are : enabled
I/F Handle : 0x04001300
Cfg Link Enabled : tx/rx enabled
H/W Tx Enable : yes
MTU : 1514
H/W Speed : 40 Gbps
H/W Loopback Type : None
FEC : Disable
H/W FlowCtrl Type : None
H/W AutoNeg Enable : Off
Rx OPD : Not Supported
H/W Link Defects : (0x0000000000000000) none
H/W Raw Link Defects : (0x0000000000000000) none
Link Up : yes
Link Led Status : Link up -- Green/Amber
Serdes fw version : 100.0
Pluggable Present : yes
Pluggable Type : 100/40G SRBD
Pluggable PID : QSFP-40/100-SRBD
Pluggable Compl. : Compliant
Pluggable Type Supp.: Supported
Pluggable PID Supp. : Supported

Router(config)#interface interface name
Router(config-if)#mtu size in bytes
Router(config-if)commit

Example

Router(config)#interface Bundle-Ether1
Router(config-if)#mtu 9646
Router(config-if)#commit
Wed Feb  2 07:50:50.275 UTC

Bundle-Ether1 is the interface name.

Router#show ipv4 interface br
Wed Feb  2 07:51:08.732 UTC

Interface               IP-Address      Status     Protocol  Vrf-Name
Bundle-Ether1           10.0.0.2        Up          Up       default 
Bundle-Ether2           10.1.1.2        Up          Up       default 
MgmtEth0/RSP0/CPU0/0    10.3.3.238      Up          Up       default 
MgmtEth0/RSP1/CPU0/0    unassigned      Shutdown    Down     default 
HundredGigE0/1/0/40     unassigned      Up          Up       default 
HundredGigE0/1/0/41     unassigned      Up          Up       default 
HundredGigE0/1/0/42     unassigned      Shutdown    Down     default 
HundredGigE0/1/0/43     unassigned      Shutdown    Down     default 
Router#show in
infra-sec-keys  inline-service  install  interfaces
inventory       

Router#show interfaces Bundle-Ether 1
Wed Feb  2 07:52:55.249 UTC
Bundle-Ether1 is up, line protocol is up 
  Interface state transitions: 1
  Hardware is Aggregated Ethernet interface(s), address is 10f3.1176.f6a4
  Internet address is 10.0.0.2/24
  MTU 9646 bytes, BW 100000000 Kbit (Max: 100000000 Kbit)
     reliability 250/255, txload 0/255, rxload 0/255
  Encapsulation ARPA,
  Full-duplex, 100000Mb/s

This section describes the procedures to configure slices and port-groups on the Cisco ASR 9000 Series 5th Generation Line Cards, and includes the following topics:

The router supports transmission of traffic in the breakout mode. The breakout mode enables a 100GbE or 400GbE port to be split into multiple independent and logical GbE ports.

Breakout Mode options:

• 1x400GbE

• 1x100GbE

• 2x100GbE

• 4x100GbE

• 2x40GbE

• 1x40GbE

• 4x25GbE

• 4x10GbE

Note	The supported breakout mode is dependent on the port and optic transceiver module.

These examples show how to configure breakout in a port.