The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This module describes the configuration of Ethernet interfaces.
The distributed 10-Gigabit, 40-Gigabit, 100-Gigabit Ethernet, 400-Gigabit Ethernet architecture and features deliver network scalability and performance, while enabling service providers to offer high-density, high-bandwidth networking solutions designed to interconnect the router with other systems in POPs, including core and edge routers, and Layer 3 switches.
 Tip |
You can programmatically configure and manage the Ethernet interfaces using |
Before configuring Ethernet interfaces, ensure that you meet the following conditions:
Know the interface IP address.
Ensure to specify the generalized interface name with the standard notation of rack/slot/module/port.
This section provides the following information:
The current release of the Cisco 8800 Series Routers support the following line cards:
36-port QSFP56-DD 400 GbE Line Card - This line card provides 14.4 Tbps via 36 QSFP56-DD ports. It also supports 100G, 2x100G, and 400G modules. If 36 of 2x100G modules are used, the line card can have 72 HundredGigE interfaces.
48-port QSFP28 100 GbE Line Card - This line card provides 4.8 Tbps with MACsec support on all ports. It also supports QSFP+ optics for 40G compatibility.
The 8800 Series line cards utilize multiple #ChipName forwarding ASICs to achieve high performance and bandwidth with line rate forwarding.
This table describes the default interface configuration parameters that are present when an interface is enabled on a 36-port Line Card or a 48-port Line Card.
 Note |
You must use the shutdown command to bring an interface administratively down. The interface default is no shutdown . When a line 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. |
|
Parameter |
Configuration File Entry |
Default Value |
|---|---|---|
|
Flow control |
flow-control |
egress off ingress off |
|
MTU |
mtu |
|
|
MAC address |
mac address |
Hardware burned-in address (BIA) |
The Gigabit Ethernet interfaces support the following protocol standards:
These standards are further described in the sections that follow.
The IEEE 802.3 protocol standards define the physical layer and MAC sublayer of the data link layer of wired Ethernet. IEEE 802.3 uses Carrier Sense Multiple Access with Collision Detection (CSMA/CD) access at various speeds over various physical media. The IEEE 802.3 standard covers 10 Mbps Ethernet. Extensions to the IEEE 802.3 standard specify implementations for 40-Gigabit Ethernet and 100-Gigabit Ethernet.
Under the International Standards Organization’s Open Systems Interconnection (OSI) model, Ethernet is fundamentally a Layer 2 protocol. 10-Gigabit Ethernet uses the IEEE 802.3 Ethernet MAC protocol, the IEEE 802.3 Ethernet frame format, and the minimum and maximum IEEE 802.3 frame size. 10-Gbps Ethernet conforms to the IEEE 802.3ae protocol standards.
Just as 1000BASE-X and 1000BASE-T (Gigabit Ethernet) remained true to the Ethernet model, 10-Gigabit Ethernet continues the natural evolution of Ethernet in speed and distance. Because it is a full-duplex only and fiber-only technology, it does not need the carrier-sensing multiple-access with the CSMA/CD protocol that defines slower, half-duplex Ethernet technologies. In every other respect, 10-Gigabit Ethernet remains true to the original Ethernet model.
IEEE 802.3ba is supported on the Cisco 1-Port 100-Gigabit Ethernet PLIM beginning in Cisco IOS XR 7.0.11.
A MAC address is a unique 6-byte address that identifies the interface at Layer 2.
The Ethernet maximum transmission unit (MTU) is the size of the largest frame, minus the 4-byte frame check sequence (FCS), that the system transmits 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 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 unfragmented packet that the system can send. 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, the system fragments that packet as necessary. This process ensures that the originating device does not send an IP packet that is too large.
The system automatically enables the jumbo frame support 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).
The flow control that the system uses 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 that is used on standard management interfaces. You can activate or deactivate flow control for ingress traffic only. The system automatically implements flow control for egress traffic.
A VLAN is a group of devices on one or more LANs that the system configures so that they can communicate as if they are attached to the same wire, when in fact they are located on several different LAN segments. Because VLANs are based on logical instead of physical connections, it is 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 to 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.
In Cisco IOS XR, interfaces are, by default, main interfaces. A main interface is also known as a trunk interface, which you must not confuse with the word trunk in the context of VLAN trunking.
There are two types of trunk interfaces:
Physical
Bundle
On the router, the system automatically creates the physical interfaces when the router recognizes a card and its physical interfaces. However, the system does not automatically create bundle interfaces but you must create them at the time of cofiguration.
The following configuration samples are examples of the trunk interfaces that you can create:
interface HundredGigE 0/5/0/0
interface bundle-ether 1
A subinterface is a logical interface that the system create under a trunk interface.
To create a subinterface, you must first identify a trunk interface under which to place it. In case of bundle interfaces, if a trunk interface does not exist, you must create a bundle interface before creating any subinterfaces under it.
You can then assign a subinterface number to the subinterface that you want to create. 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 are 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, HundredGigE 0/5/0/0. A subinterface, HundredGigE 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 HundredGigE0/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 HundredGigE 0/5/0/0
Mon Sep 21 11:15:42.654 EDT
Building configuration...
interface HundredGigE 0/5/0/0
shutdown
!
interface HundredGigE 0/5/0/0.0
encapsulation dot1q 100
!
interface HundredGigE 0/5/0/1
shutdown
!
When a subinterface is first created, the 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, HundredGigE 0/5/0/0, followed by the display output for the subinterface HundredGigE 0/5/0/0.0.
RP/0/RSP0/CPU0:router# show interface HundredGigE 0/5/0/0
Mon Sep 21 11:12:51.068 EDT
HundredGigE0/5/0/0 is administratively down, line protocol is administratively down.
Interface state transitions: 0
Hardware is HundredGigE, 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 HundredGigE0/5/0/0.0
Mon Sep 21 11:12:55.657 EDT
HundredGigE0/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 HundredGigE 0/5/0/0
Mon Sep 21 11:42:27.100 EDT
Building configuration...
interface HundredGigE 0/5/0/0
negotiation auto
!
interface HundredGigE 0/5/0/0.0
encapsulation dot1q 100
!
interface HundredGigE 0/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 HundredGigE 0/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 HundredGigE 0/5/0/0
Mon Sep 21 11:42:57.262 EDT
Building configuration...
interface HundredGigE 0/5/0/0
negotiation auto
!
interface HundredGigE 0/5/0/1
shutdown
!
The following additional performance management enhancements are included in Cisco IOS XR Release 7.0.11:
You can retain performance management history statistics across a process restart or route processor (RP) failover using the new history-persistent keyword option for the performance-mgmt statistics interface command.
You can save performance management statistics to a local file using the performance-mgmt resources dump local command.
You can filter performance management instances by defining a regular expression group (performance-mgmt regular-expression command), which includes multiple regular expression indices that specify strings to match. You apply a defined regular expression group to one or more statistics or threshold templates in the performance-mgmt statistics interface or performance-mgmt thresholds interface commands.
Cisco IOS XR Software supports SyncE-capable Ethernet on the router. Frequency Synchronization enables you to distribute the precision clock signals around the network. The system injects a highly accurate timing signals into the router in the network. The timing signals use an external timing technology, such as Cesium atomic clocks, or GPS, and then pass the signals to 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 or SDH networks, but is now available on Ethernet for Cisco 8000 Series Router with Synchronous Ethernet capability. For more information, see Cisco 8000 Series Router System Management Configuration Guide.
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 router also supports the IEEE 802.1AB Link Layer Discovery Protocol (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, End of LLDPDU, 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 <Optional TLV> disable command.
LLDP frames use the IEEE 802.3 format, which consists of the following fields:
Destination address (6 bytes)—Uses a multicast address of 01-80-C2-00-00-0E.
Source address (6 bytes)—MAC address of the sending device or port.
LLDP Ethertype (2 bytes)—Uses 88-CC.
LLDP PDU (1500 bytes)—LLDP payload consisting of TLVs.
FCS (4 bytes)—Cyclic Redundancy Check (CRC) for error checking.
LLDP TLVs carry the information about neighboring devices within the LLDP PDU using the following basic format:
TLV Header (16 bits), which includes the following fields:
TLV Type (7 bits)
TLV Information String Length (9 bits)
TLV Information String (0 to 511 bytes)
LLDP is a one-way protocol. The basic operation of LLDP consists of a device enabled for transmit of LLDP information sending periodic advertisements of information in LLDP frames to a receiving device.
Devices are identified using a combination of the Chassis ID and Port ID TLVs to create an MSAP (MAC Service Access Point). The receiving device saves the information about a neighbor in a remote lldp cache for a certain amount of time as specified in the TTL TLV received from the neighbor, before aging and removing the information.
LLDP supports the following additional operational characteristics:
LLDP can operate independently in transmit or receive modes. On globall lldp enablement, the default mode is to operate in both transmit and receive modes.
LLDP operates as a slow protocol with transmission speeds not greater than one frame per five seconds.
LLDP packets are sent when the following occurs:
The packet update frequency specified by the lldp timer command is reached. The default is 30 seconds.
When a change in the values of the managed objects occurs from the local system’s LLDP MIB.
When LLDP is activated on an interface (3 frames are sent upon activation similar to CDP).
When an LLDP frame is received, the LLDP remote services and PTOPO MIBs are updated with the information in the TLVs.
LLDP supports the following actions on these TLV characteristics:
Interprets a neighbor TTL value of 0 as a request to automatically purge the information of the transmitting device. These shutdown LLDPDUs are typically sent prior to a port becoming inoperable.
An LLDP frame with a malformed mandatory TLV is dropped.
A TLV with an invalid value is ignored.
A copy of an unknown organizationally-specific TLV is maintained if the TTL is non-zero, for later access through network management.
The router supports the following LLDP functions:
IPv4 and IPv6 management addresses—In general, both IPv4 and IPv6 addresses will be advertised if they are available, and preference is given to the address that is configured on the transmitting interface.
If the transmitting interface does not have a configured address, then the system populates the TLV with an address from another interface. The advertised LLDP IP address is implemented according to the following priority order of IP addresses for interfaces on the router:
Locally configured address on the transmitting interface
MgmtEth0/RSP0RP0/CPU0/0
MgmtEth0/RSP0RP0/CPU0/1
MgmtEth0/RSP1RP1/CPU0/0
MgmtEth0/RSP1RP1/CPU0/1
Loopback interfaces
There are some differences between IPv4 and IPv6 address management in LLDP:
For IPv4, as long as the IPv4 address is configured on an interface, it can be used as an LLDP management address.
For IPv6, after the IPv6 address is configured on an interface, the interface status must be Up and pass the DAD (Duplicate Address Detection) process before it is can be used as an LLDP management address.
LLDP is supported for the nearest physically attached, non-tunneled neighbors.
LLDP is supported for Ethernet interfaces, L3 subinterfaces, bundle interfaces, and L3 bundle subinterfaces.
The following LLDP functions are not supported on the router:
LLDP-MED organizationally unique extension—However, interoperability still exists between other devices that do support this extension.
Tunneled neighbors, or neighbors more than one hop away.
LLDP TLVs cannot be disabled on a per-interface basis; However, certain optional TLVs can be disabled globally.
LLDP SNMP trap lldpRemTablesChange.
The following table allows you to configure the fabric bandwidth threshold level. This is a systemwide configuration that applies to all the line card NPUs in the chassis.
|
Type |
Definition |
Default |
Behavior |
|---|---|---|---|
|
Total fabric bandwidth |
Bandwidth between a line card and all 8 fabric cards in the chassis |
Not Applicable |
Constant |
|
Total required bandwidth |
Total fabric bandwidth x (bandwidth Threshold config) |
5% |
Configured value |
|
Lower required bandwidth |
Total fabric bandwidth x (bandwidth threshold config -10) |
5% |
Calculated value. When the available fabric bandwidth falls below this value, interfaces go down to avoid traffic black hole. |
|
Available bandwidth |
Total fabric bandwidth available for traffic. This is a function of number of links from un-isolated Fast Ethernet devices connecting to the NPU x 50G. |
Not Applicable |
— |
The default bandwidth threshold value is 5%, you can change the value by using the following command in increments of 10.
Following is a systemwide configuration that applies to all the line card NPUs in the chassis.
Router# configure terminal
Router (config)# hw-module profile bw-threshold <value>
Router (config)# commit
If the available bandwidth drops to being equal to or below the lower required bandwidth, then all network interfaces of the line card get disabled to reroute the traffic.
When total available bandwidth reaches the required bandwidth, then the network interfaces of the line card get re-enabled.
For example, consider that the bandwidth threshold is set to 20%.
If the available bandwidth goes below 10%, then network interfaces of the line cards are shut automatically.
If the available bandwidth goes above 20%, then network interfaces of the line cards are unshut automatically.
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:
This table shows the values of the LLDP default configuration on the router. To change the default settings, use the LLDP global configuration and LLDP interface configuration commands.
|
LLDP Function |
Default |
|---|---|
|
LLDP global state |
Disabled |
|
LLDP holdtime (before discarding) |
120 seconds |
|
LLDP timer (packet update frequency) |
30 seconds |
|
LLDP reinitialization delay |
2 seconds |
|
LLDP TLV selection |
All TLVs are enabled for sending and receiving. |
|
LLDP interface state |
Enabled for both transmit and receive operation when LLDP is globally enabled. |
RP/0/RSP0/CPU0:ios(config)# int HundredGigE 0/2/0/0
RP/0/RSP0/CPU0:ios(config-if)# no sh
RP/0/RSP0/CPU0:ios(config-if)#commit
RP/0/RSP0/CPU0:ios(config-if)#lldp ?
RP/0/RSP0/CPU0:ios(config-if)#lldp enable
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 HundredGigE0/1/0/0
shutdown
!
interface HundredGigE0/1/0/1
shutdown
!
interface HundredGigE0/1/0/2
shutdown
!
interface HundredGigE0/2/0/0
Shutdown
!
interface HundredGigE0/2/0/1
shutdown
!
interface HundredGigE0/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
HundredGigE0/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#To run LLDP on the router, you must enable it globally. When you enable LLDP globally, all interfaces that support LLDP are automatically enabled for both transmit and receive operations.
You can override this default operation at the interface to disable receive or transmit operations. For more information about how to selectively disable LLDP receive or transmit operations for an interface, see the Disabling LLDP Receive and Transmit Operation for an Interface section.
The following table describes the global attributes that you can configure:
| Attribute | Default | Range | Description |
|---|---|---|---|
| Holdtime | 120 | 0-65535 | Specifies the holdtime (in sec) that are sent in packets |
| Reinit | 2 | 2-5 | Delay (in sec) for LLDP initialization on any interface |
| Timer | 30 | 5-65534 | Specifies the rate at which LLDP packets are sent (in sec) |
To enable LLDP globally, complete the following steps:
RP/0//CPU0:router # configure
RP/0//CPU0:router(config) #lldp
end or commit
Running configuration
RP/0/RP0/CPU0:turin-5#show run lldp
Fri Dec 15 20:36:49.132 UTC
lldp
!
RP/0/RP0/CPU0:turin-5#show lldp neighbors
Fri Dec 15 20:29:53.763 UTC
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
SW-NOSTG-I11-PUB.cis Mg0/RP0/CPU0/0 120 N/A Fa0/28
Total entries displayed: 1
RP/0/RP0/CPU0:turin-5#show lldp neighbors mgmtEth 0/RP0/CPU0/0
Fri Dec 15 20:30:54.736 UTC
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
SW-NOSTG-I11-PUB.cis Mg0/RP0/CPU0/0 120 N/A Fa0/28
Total entries displayed: 1When you enable LLDP globally on the router using the lldp command, these defaults are used for the protocol.
To modify the global LLDP operational characteristics such as the LLDP neighbor information holdtime, initialization delay, or packet rate, complete the following steps:
|
Step 1 |
Example:Enters global configuration mode. |
|
Step 2 |
lldp holdtime seconds Example:(Optional) Specifies the length of time that information from an LLDP packet should be held by the receiving device before aging and removing it. |
|
Step 3 |
lldp reinit seconds Example:(Optional) Specifies the length of time to delay initialization of LLDP on an interface. |
|
Step 4 |
lldp timer seconds Example:(Optional) Specifies the LLDP packet rate. |
|
Step 5 |
end or commit Example:or Saves configuration changes.
|
Certain TLVs are classified as mandatory in LLDP packets, such as the Chassis ID, Port ID, and Time to Live (TTL) TLVs. These TLVs must be present in every LLDP packet. You can suppress transmission of certain other optional TLVs in LLDP packets.
To disable transmission of optional LLDP TLVs, complete the following steps:
|
Step 1 |
configure Example:Enters global configuration mode. |
|
Step 2 |
lldp tlv-select tlv-name disable Example:(Optional) Specifies that transmission of the selected TLV in LLDP packets is disabled. The tlv-name can be one of the following LLDP TLV types:
|
|
Step 3 |
end or commit Example:or Saves configuration changes.
|
When you enable LLDP globally on the router, all supported interfaces are automatically enabled for LLDP receive and transmit operation. You can override this default by disabling these operations for a particular interface.
To disable LLDP receive and transmit operations for an interface, complete the following steps:
|
Step 1 |
configure Example:Enters global configuration mode. |
|
Step 2 |
interface HundredGigE 0/2/0/0 Example:Enters interface configuration mode and specifies the Ethernet interface name and notation rack/slot/module/port. Possible interface types for this procedure are:
|
|
Step 3 |
lldp Example:(Optional) Enters LLDP configuration mode for the specified interface. |
|
Step 4 |
receive disable Example:(Optional) Disables LLDP receive operations on the interface. |
|
Step 5 |
transmit disable Example:(Optional) Disables LLDP transmit operations on the interface. |
|
Step 6 |
end or commit Example:or Saves configuration changes.
|
This section describes how you can verify the LLDP configuration both globally and for a particular interface.
To verify the LLDP global configuration status and operational characteristics, use the show lldp command as shown in the following example:
RP/0/RSP0/CPU0:router# show lldp
Wed Apr 13 06:16:45.510 DST
Global LLDP information:
Status: ACTIVE
LLDP advertisements are sent every 30 seconds
LLDP hold time advertised is 120 seconds
LLDP interface reinitialisation delay is 2 seconds
If LLDP is not enabled globally, the following output appears when you run the show lldp command:
RP/0/RSP0/CPU0:router# show lldp
Wed Apr 13 06:42:48.221 DST
% LLDP is not enabled
To verify the LLDP interface status and configuration, use the show lldp interface command as shown in the following example:
RP/0/RSP0/CPU0:router# show lldp interface HundredGigE 0/1/0/7
Wed Apr 13 13:22:30.501 DST
HundredGigE0/1/0/7:
Tx: enabled
Rx: enabled
Tx state: IDLE
Rx state: WAIT FOR FRAME
To monitor and maintain LLDP on the system or get information about LLDP neighbors, use one of the following commands:
| Command |
Description |
|---|---|
|
clear lldp counters |
Resets LLDP traffic counters or LLDP neighbor information. |
|
show lldp entry |
Displays detailed information about LLDP neighbors. |
|
show lldp errors |
Displays LLDP error and overflow statistics. |
|
show lldp neighbors |
Displays information about LLDP neighbors. |
|
show lldp traffic |
Displays statistics for LLDP traffic. |
This section provides the following configuration examples:
The following example shows how to configure an interface for a 10-Gigabit Ethernet modular services card:
RP/0//CPU0:router# configure
RP/0//CPU0:router(config)# interface TenGigE 0/0/0/1
RP/0//CPU0:router(config-if)# ipv4 address 172.18.189.38 255.255.255.224
RP/0//CPU0:router(config-if)# flow-control ingress
RP/0//CPU0:router(config-if)# mtu 1448
RP/0//CPU0:router(config-if)# mac-address 0001.2468.ABCD
RP/0//CPU0:router(config-if)# no shutdown
RP/0//CPU0:router(config-if)# end
Uncommitted changes found, commit them? [yes]: yes
RP/0//CPU0:router# show interfaces TenGigE 0/0/0/1
TenGigE0/0/0/1 is down, line protocol is down
Hardware is TenGigE, address is 0001.2468.abcd (bia 0001.81a1.6b23)
Internet address is 172.18.189.38/27
MTU 1448 bytes, BW 10000000 Kbit
reliability 0/255, txload Unknown, rxload Unknown
Encapsulation ARPA,
Full-duplex, 10000Mb/s, LR
output flow control is on, input flow control is on
Encapsulation ARPA,
ARP type ARPA, ARP timeout 01:00:00
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
The following example shows how to enable LLDP globally on the router and modify the default LLDP operational characteristics:
RP/0//CPU0:router# configure
RP/0//CPU0:router(config)# lldp
RP/0//CPU0:router(config)# lldp holdtime 60
RP/0//CPU0:router(config)# lldp reinit 4
RP/0//CPU0:router(config)# lldp timer 60
RP/0//CPU0:router(config)# commit
The following example shows how to disable a specific Gigabit Ethernet interface for LLDP transmission:
RP/0//CPU0:router# configure
RP/0//CPU0:router(config)# interface HundredGigE 0/2/0/0
RP/0//CPU0:router(config-if)# lldp
RP/0//CPU0:router(config-lldp)# transmit disable
When you have configured an Ethernet interface, you can configure individual VLAN subinterfaces on that Ethernet interface.
For information about modifying Ethernet management interfaces for the shelf controller (SC), route processor (RP), and distributed RP, see the Advanced Configuration and Modification of the Management Ethernet Interface later in this document.
For information about IPv6 see the Implementing Access Lists and Prefix Lists on Cisco IOS XR Software module in the Cisco IOS XR IP Addresses and Services Configuration Guide.
Use this procedure to create a basic Ethernet interface configuration.
|
Step 1 |
show version Example:(Optional) Displays the current software version, and can also be used to confirm that the router recognizes the line card. |
||
|
Step 2 |
show interfaces [ TenGigE FortyGigE HundredGigE FourHundredGigE] interface-path-id Example:(Optional) Displays the configured interface and checks the status of each interface port. |
||
|
Step 3 |
configure Example:Enters global configuration mode. |
||
|
Step 4 |
show interfaces [ TenGigE FortyGigE HundredGigE FourHundredGigE] interface-path-id Example:Enters interface configuration mode and specifies the Ethernet interface name and notation rack/slot/module/port. Possible interface types for this procedure are:
The examples of interface-path-id ranges are:
|
||
|
Step 5 |
ipv4 address ip-address mask Example:Assigns an IP address and subnet mask to the interface.
|
||
|
Step 6 |
flow-control {bidirectional| egress | ingress} Example:(Optional) Enables the sending and processing of flow control pause frames.
|
||
|
Step 7 |
mtu bytes Example:(Optional) Sets the MTU value for the interface.
|
||
|
Step 8 |
no shutdown Example:Removes the shutdown configuration, which forces an interface administratively down. |
||
|
Step 9 |
end or commit Example:or Saves configuration changes.
|
||
|
Step 10 |
show interfaces [ TenGigE FortyGigE HundredGigE FourHundredGigE] interface-path-id Example:(Optional) Displays statistics for interfaces on the router. |
This example shows how to configure an interface for a 100-Gigabit Ethernet line card:
RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/1/0/1
RP/0/RP0/CPU0:router(config-if)# ipv4 address 172.18.189.38 255.255.255.224
RP/0/RP0/CPU0:router(config-if)# mtu 1448
RP/0/RP0/CPU0:router(config-if)# no shutdown
RP/0/RP0/CPU0:router(config-if)# end
Uncommitted changes found, commit them? [yes]: yes
RP/0/RP0/CPU0:router# show interfaces HundredGigE 0/5/0/24
HundredGigE0/5/0/24 is up, line protocol is up
Interface state transitions: 1
Hardware is HundredGigE, address is 6219.8864.e330 (bia 6219.8864.e330)
Internet address is 3.24.1.1/24
MTU 9216 bytes, BW 100000000 Kbit (Max: 100000000 Kbit)
reliability 255/255, txload 3/255, rxload 3/255
Encapsulation ARPA,
Full-duplex, 100000Mb/s, link type is force-up
output flow control is off, input flow control is off
Carrier delay (up) is 10 msec
loopback not set,
Last link flapped 10:05:07
ARP type ARPA, ARP timeout 04:00:00
Last input 00:08:56, output 00:00:00
Last clearing of "show interface" counters never
5 minute input rate 1258567000 bits/sec, 1484160 packets/sec
5 minute output rate 1258584000 bits/sec, 1484160 packets/sec
228290765840 packets input, 27293508436038 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 15 broadcast packets, 45 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
212467849449 packets output, 25733664696650 bytes, 0 total output drops
Output 23 broadcast packets, 15732 multicast packets
39 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
RP/0/RP0/CPU0:router# show running-config interface HundredGigE 0/5/0/24
interface HundredGigE 0/5/0/24
mtu 9216
service-policy input linerate
service-policy output elinerate
ipv4 address 3.24.1.1 255.255.255.0
ipv6 address 3:24:1::1/64
flow ipv4 monitor perfv4 sampler fsm ingress
!
How to Configure Interfaces in Breakout Mode
The router supports transmission of traffic in the breakout mode. The breakout mode enables a 40 Gigabit Ethernet port to be split into four independent and logical 10 Gigabit Ethernet ports. The 4x10 breakout mode is supported on the following types of 40G modules:
QSFP-4x10-LR-S
QSFP-40G-SR4
The native 40G mode on QSFP-40G-SR4 is not supported.
The 36-port QSFP56-DD 400 GbE Line Card does not support the 4x10G breakout.
If port 24~35 on Cisco 8200 Series Routers are used for 4x10G breakout configuration, you must use even port numbers (24/26/28/30/32/34) for breakout configurations.
The system automatically disables the ports 25/27/29/31/33/35 if the ports with even numbers (24/26/28/30/32/34) are used for breakout configurations.
Use the hw-module port-range command to set the port range for the breakout configuration in the global configuration.
To remove the global hw-module port-range configuration, you must first remove the ‘breakout 4x10’ configuration under the controller.
For 4x10G breakout on 48-port Line Card, only QSFP-4x10-LR-S module is supported.
RP/0/RP0/CPU0:uut# configure
Fri Oct 11 23:58:47.165 UTC
RP/0/RP0/CPU0:uut(config)# controller optics 0/1/0/28
RP/0/RP0/CPU0:uut(config-Optics)# breakout 4x10
RP/0/RP0/CPU0:uut(config-Optics)# commit
Fri Oct 11 23:59:51.261 UTC
RP/0/RP0/CPU0:uut(config-Optics)# end
RP/0/RP0/CPU0:uut#RP/0/RP0/CPU0:uut# configure
Sat Oct 12 00:01:38.673 UTC
RP/0/RP0/CPU0:uut(config)# controller optics 0/1/0/28
RP/0/RP0/CPU0:uut(config-Optics)# no breakout 4x10
RP/0/RP0/CPU0:uut(config-Optics)# commit
Sat Oct 12 00:01:55.864 UTC
RP/0/RP0/CPU0:uut(config-Optics)# endRP/0/RP0/CPU0:uut# show running-config controller optics 0/1/0/28
Sat Oct 12 00:11:33.962 UTC
controller Optics0/1/0/28
breakout 4x10
!
RP/0/RP0/CPU0:uut# show int br location 0/1/CPU0 | i Te
Sat Oct 12 00:11:38.609 UTC
Te0/1/0/27/0 up up ARPA 10000 10000000
Te0/1/0/27/1 up up ARPA 10000 10000000
Te0/1/0/27/2 up up ARPA 10000 10000000
Te0/1/0/27/3 up up ARPA 10000 10000000
Te0/1/0/28/0 up up ARPA 10000 10000000
Te0/1/0/28/1 up up ARPA 10000 10000000
Te0/1/0/28/2 up up ARPA 10000 10000000
Te0/1/0/28/3 up up ARPA 10000 10000000
Feedback