Configuring Ethernet Interfaces

This module describes the configuration of Ethernet interfaces.

The following distributed ethernet architecture delivers network scalability and performance, while enabling service providers to offer high-density, high-bandwidth networking solutions.

  • 1-Gigabit

  • 10-Gigabit

  • 25-Gigabit

  • 40-Gigabit

  • 100-Gigabit


Tip

You can programmatically configure and manage the Ethernet interfaces using openconfig-ethernet-if.yang and openconfig-interfaces.yang OpenConfig data models. To get started with using data models, see the Programmability Configuration Guide for Cisco NCS 540 Series Routers.

These solutions are designed to interconnect the router with other systems in point-of-presence (POP)s, including core and edge routers and Layer 2 and Layer 3 switches.

Restrictions

Router does not support configuration of the static mac address.

Configuring Physical Ethernet Interfaces

Restrictions and Important Guidelines

  • NC55-MPA-12T-S supports 1G optics in eight ports. The ports are 0 to 3 and 8 to 11.

  • NC55-MPA-12T-S supports 10G optics in ports 4 to 7.

Use this procedure to create a basic Ethernet interface configuration.

Procedure

Step 1

show version

Example:


RP/0/RP0/CPU0:router# show version

(Optional) Displays the current software version, and can also be used to confirm that the router recognizes the line card.

Step 2

show interfaces [GigE | TenGigE | TwentyFiveGigE| FortyGigE | HundredGigE] interface-path-id

Example:


RP/0/RP0/CPU0:router# show interface HundredGigE 0/0/1/0

(Optional) Displays the configured interface and checks the status of each interface port.

Step 3

configure

Example:


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

Enters global configuration mode.

Step 4

interface [GigE | TenGigE| TwentyFiveGigE| FortyGigE | HundredGigE] interface-path-id

Example:


RP/0/RP0/CPU0:router(config)# interface HundredGigE 0/0/1/0

Enters interface configuration mode and specifies the Ethernet interface name and notation rack/slot/module/port. Possible interface types for this procedure are:

  • GigE

  • 10GigE

  • 25GigE

  • 40GigE

  • 100GigE

    Note

     

    • The example indicates a 100-Gigabit Ethernet interface in the line card in slot 1.

The supported interface-path-id ranges are:

  • GigE — 0/0/0/0 - 0/0/0/31

  • TenGigE — 0/0/0/0 - 0/0/0/31

  • TwentyFiveGigE — 0/0/0/24 - 0/0/0/31

  • FortyGigE — 0/0/1/0 - 0/0/1/1

  • HundredGigE — 0/0/1/0 - 0/0/1/1

Step 5

ipv4 address ip-address mask

Example:


RP/0/RP0/CPU0:router(config-if)# ipv4 address 172.18.189.38 255.255.255.224

Assigns an IP address and subnet mask to the interface.

  • Replace ip-address with the primary IPv4 address for the interface.

  • Replace mask with the mask for the associated IP subnet. The network mask can be specified in either of two ways:

  • The network mask can be a four-part dotted decimal address. For example, 255.0.0.0 indicates that each bit equal to 1 means that the corresponding address bit belongs to the network address.

  • The network mask can be indicated as a slash (/) and number. For example, /8 indicates that the first 8 bits of the mask are ones, and the corresponding bits of the address are network address.

Step 6

mtu bytes

Example:


RP/0/RP0/CPU0:router(config-if)# mtu 2000

(Optional) Sets the MTU value for the interface.

  • The configurable range for MTU values is 1514 bytes to 9646 bytes.

  • The default is 1514 bytes for normal frames and 1518 bytes for 802.1Q tagged frames.

Step 7

no shutdown

Example:


RP/0/RP0/CPU0:router(config-if)# no shutdown

Removes the shutdown configuration, which forces an interface administratively down.

Step 8

show interfaces [GigE TenGigE TwentyFiveGigE TwentyFiveGigE FortyGigE HundredGigE ] interface-path-id

Example:


RP/0/RP0/CPU0:router# show interfaces HundredGigE 
0/0/1/0

(Optional) Displays statistics for interfaces on the router.

Example

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/0/1/0 
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 2000 

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/0/1/0 
HundredGigE0/0/1/0 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/0/1/0 

interface HundredGigE 0/0/1/0
 mtu 9216
 
 ipv4 address 3.24.1.1 255.255.255.0
 ipv6 address 3:24:1::1/64
 flow ipv4 monitor perfv4 sampler fsm ingress
!

Information About Configuring Ethernet

This section provides the following information sections:

Default Configuration Values for 100-Gigabit Ethernet

This table describes the default interface configuration parameters that are present when an interface is enabled on a 10-Gigabit Ethernet or 100-Gigabit Ethernet 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.

Table 1. 100-Gigabit Ethernet line card Default Configuration Values

Parameter

Configuration File Entry

Default Value

MTU

mtu

  • 1514 bytes for normal frames

  • 1518 bytes for 802.1Q tagged frames.

  • 1522 bytes for Q-in-Q frames.

MAC address

mac address

Hardware burned-in address (BIA)

Ethernet MTU

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 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 will be 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 enable 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 following list describes the properties of MTUs:

  • Each physical port can have a different MTU.

  • Main interface of each bundle can have one MTU value.

  • L3 sub-interface (bundle or physical) shares MTU profiles and can have a maximum of 3 unique configured MTUs per NPU.


    Note

    L2 sub-interface MTU is not supported.

Link Layer Discovery Protocol (LLDP)

Cisco Discovery Protocol (CDP) is a device discovery protocol that runs over Layer 2. Layer 2 is also known as the data link layer that runs on all Cisco-manufactured devices, such as routers, bridges, access servers, and switches. CDP allows the network management applications to automatically discover and learn about other Cisco devices that connect to the network.

To support non-Cisco devices and to allow for interoperability between other devices, it 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.

With LLDP, you can also access the information about a particular physical network connection. If you use a non-Cisco monitoring tool (via SNMP,) LLDP helps you identify the Object Identifiers (OIDs) that the system supports. The following are the supported OIDs:

  • 1.0.8802.1.1.2.1.4.1.1.4

  • 1.0.8802.1.1.2.1.4.1.1.5

  • 1.0.8802.1.1.2.1.4.1.1.6

  • 1.0.8802.1.1.2.1.4.1.1.7

  • 1.0.8802.1.1.2.1.4.1.1.8

  • 1.0.8802.1.1.2.1.4.1.1.9

  • 1.0.8802.1.1.2.1.4.1.1.10

  • 1.0.8802.1.1.2.1.4.1.1.11

  • 1.0.8802.1.1.2.1.4.1.1.12

Enabling LLDP Globally

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.

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:

  1. RP/0/RP0/CPU0:router # configure

  2. RP/0/RP0/CPU0:router(config) #lldp

  3. end or commit

Running configuration

RP/0/RP0/CPU0:router-5#show run lldp
Fri Dec 15 20:36:49.132 UTC
lldp
!

RP/0/RP0/CPU0:router#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:router#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: 1

Enabling LLDP Per Interface

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/RP0/CPU0:router(config)# int gigabitEthernet 0/2/0/0

  2. RP/0/RP0/CPU0:router(config-if)# no sh

  3. RP/0/RP0/CPU0:router(config-if)#commit

  4. RP/0/RP0/CPU0:router(config-if)#lldp ?

  5. RP/0/RP0/CPU0:router(config-if)#lldp enable

  6. RP/0/RP0/CPU0:router(config-if)#commit

Running configuration

RP/0/RP0/CPU0:router#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/0/0/0
 shutdown
!
interface GigabitEthernet0/0/0/1
 shutdown
!
interface GigabitEthernet0/0/0/2
 shutdown
!
interface GigabitEthernet0/0/0/3
 Shutdown
!
interface GigabitEthernet0/0/0/4
 shutdown
!
interface GigabitEthernet0/0/0/5
 shutdown
!
end

Verification

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


GigabitEthernet0/0/0/3:
        Tx: enabled
        Rx: enabled
        Tx state: IDLE
        Rx state: WAIT FOR FRAME
RP/0/RP0/CPU0:router# 

RP/0/RP0/CPU0:router# 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/0/0/3           120        R               Gi0/0/0/3       <====== LLDP enabled only on GigEth0/0/0/3 and neighborship seen for the same.

Total entries displayed: 1

RP/0/RP0/CPU0:router#