Interfaces and Hardware Component Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

PDF

Interfaces and Hardware Component Configuration Guide for Cisco 8000 Series Routers, Cisco IOS XR Releases

Configure a Management Ethernet interface

Updated: July 31, 2026

Want to summarize with AI?

Log in

This topic provides the steps to configure a Management Ethernet interface, save the changes, and verify the resulting operational state.

Configure the Management Ethernet interface with an IPv4 address and subnet mask, optionally adjust the MTU, and bring the interface online for management traffic.

Use this procedure for the minimal configuration that is required on the Management Ethernet interface.

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

Specify the subnet mask as either a dotted-decimal mask, such as 255.255.0.0, or a prefix length, such as /16.

Before you begin

Complete the initial Management Ethernet interface setup and make sure that you understand the generalized interface naming format rack/slot/module/port .

Procedure

1.

Enter the configuration mode.

Example:

Router# configure
2.

Specify the Ethernet interface name and notation as, rack/slot/module/port.

Example:

Router(config)# interface MgmtEth 0/RP0/CPU0/0
3.

Assign the primary IPv4 address and subnet mask to the interface.

Example:

Router(config-if)# ipv4 address 1.76.18.150/16 (or) 
ipv4 address 1.76.18.150 255.255.0.0

You can specify the network mask in one of the two ways:

  • The network mask is represented in a four-part dotted decimal format. For instance, a mask of 255.255.0.0 signifies that each bit set to 1 indicates the corresponding bit in the address is part of the network address.

  • The system indicates the network mask as a slash (/) and number. For example, /16 in the example indicates that the first 16 bits of the mask are ones, and the corresponding bits of the address are the network address.
4.

Opyional: Specify the mtu value.

Example:

Router(config-if)# mtu 1488
Note

  • The maximum transmission unit (MTU) value for the management interface is 9678 bytes.

  • The default is 1514 bytes.

  • The valid range for Management Ethernet interface mtu values is from 64 through 9678 bytes.
5.

Remove the forced administrative shutdown so the interface can transition to an operational up or down state.

Example:

Router(config-if)# no shutdown
6.

End and save your configuration.

Example:

Router(config-if)# end
or
Router(config-if)# commit

  1. When you issue end , the system prompts you to commit changes before exiting.

    Example:

    Uncommitted changes found, commit them before exiting(yes/no/cancel)?
[cancel]:

  2. Enter yes to save the configuration, exit the configuration session, and return to EXEC mode.

  3. Enter no to exit the configuration session without committing the changes.

  4. Enter cancel to remain in the current configuration session without exiting or committing the changes.

  5. Use commit instead of end when you want to save the changes and remain in configuration mode.
7.

Verify the operational state of the interface.

Router# show running-config interface MgmtEth 0/RP0/CPU0/0
MgmtEth0/RP0/CPU0/0 is up, line protocol is up
  Interface state transitions: 3
  Hardware is Management Ethernet, address is 1005.cad8.4354 (bia 1005.cad8.4354)
  Internet address is 1.76.18.150/16
  MTU 1488 bytes, BW 1000000 Kbit (Max: 1000000 Kbit)
     reliability 255/255, txload 0/255, rxload 0/255
  Encapsulation ARPA,
  Full-duplex, 1000Mb/s, 1000BASE-T, link type is autonegotiation
  loopback not set,
  Last link flapped 00:00:59
  ARP type ARPA, ARP timeout 04:00:00
  Last input 00:00:00, output 00:00:02
  Last clearing of "show interface" counters never
  5 minute input rate 4000 bits/sec, 3 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     21826 packets input, 4987886 bytes, 0 total input drops
     0 drops for unrecognized upper-level protocol
     Received 12450 broadcast packets, 8800 multicast packets
              0 runts, 0 giants, 0 throttles, 0 parity
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     1192 packets output, 217483 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
     3 carrier transitions
This example shows advanced configuration and verification of the Management Ethernet interface on the RP: 
Router# configure
Router(config)# interface MgmtEth 0/RP0/CPU0/0
Router(config)# ipv4 address 1.76.18.150/16
Router(config-if)# no shutdown
Router(config-if)# commit
Router:Mar 26 01:09:28.685 :ifmgr[190]:%LINK-3-UPDOWN :Interface
MgmtEth0/RP0/CPU0/0, changed state to Up
Router(config-if)# end

This example shows VRF configuration and verification of the Management Ethernet interface on the router processor with the source address:

Router# show run interface MgmtEth 0/RP0/CPU0/0 
interface MgmtEth0/RP0/CPU0/0
 vrf httpupload
 ipv4 address 10.8.67.20 255.255.0.0
 ipv6 address 2001:10:8:67::20/48
!
 
Router# show run http 
Wed Jan 30 14:58:53.458 UTC
http client vrf httpupload
http client source-interface ipv4 MgmtEth0/RP0/CPU0/0
 
Router# show run vrf 
Wed Jan 30 14:59:00.014 UTC
vrf httpupload
!

What to do next

Use these verification results and examples as a baseline for related Management Ethernet interface procedures.