Advanced Configuration and Modification of the Management Ethernet Interface

This module describes the configuration of Management Ethernet interfaces.

Before you can use Telnet to access the router through the LAN IP address, you must set up a Management Ethernet interface and enable Telnet servers, as described in the Configuring General Router Features module of the System Setup and Software Installation Guide for Cisco NCS 6000 Series Routers . This module describes how to modify the default configuration of the Management Ethernet interface after it has been configured, as described in System Setup and Software Installation Guide for Cisco NCS 6000 Series Routers.


Note
Forwarding between physical layer interface modules (PLIM) ports and Management Ethernet interface ports is disabled by default. To enable forwarding between PLIM ports and Management Ethernet interface ports, use the rp mgmtethernet forwarding command.

Note
Although the Management Ethernet interfaces on the system are present by default, the user must configure these interfaces to use them for accessing the router, using protocols and applications such as Simple Network Management Protocol (SNMP), Common Object Request Broker Architecture (CORBA), HTTP, extensible markup language (XML), TFTP, Telnet, and command-line interface (CLI).

Feature History for Configuring Management Ethernet Interfaces

Release

Modification

Release 5.0.0

This feature was introduced.

Prerequisites for Configuring Management Ethernet Interfaces

You must be in a user group associated with a task group that includes the proper task IDs. The command reference guides include the task IDs required for each command. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.

Before performing the Management Ethernet interface configuration procedures that are described in this module, ensure that these tasks and conditions are met:

  • You have performed the initial configuration of the Management Ethernet interface.
  • You know how to apply the generalized interface name specification rack/slot/module/port .

Note
For transparent switchover, both active and standby Management Ethernet interfaces are expected to be physically connected to the same LAN or switch.

Information About Configuring Management Ethernet Interfaces

To configure Management Ethernet interfaces, you must understand the following concept:

Default Interface Settings

This table describes the default Management Ethernet interface settings that can be changed by manual configuration. Default settings are not displayed in the show running-config command output.

Table 1. Management Ethernet Interface Default Settings

Parameter

Default Value

Configuration File Entry

Speed in Mbps

Speed is autonegotiated.

speed [10 | 100 | 1000 ]

To return the system to autonegotiate speed, use the no speed [10 | 100 | 1000 ] command.

Duplex mode

Duplex mode is autonegotiated.

duplex {full | half }

To return the system to autonegotiated duplex operation, use the no duplex {full | half} command, as appropriate.

MAC address

MAC address is read from the hardware burned-in address (BIA).

mac-address address

To return the device to its default MAC address, use the no mac-address address command.

How to Perform Advanced Management Ethernet Interface Configuration

This section contains the following procedures:

Configuring a Management Ethernet Interface

Perform this task to configure a Management Ethernet interface. This procedure provides the minimal configuration required for the Management Ethernet interface.


Note
You do not need to perform this task if you have already set up the Management Ethernet interface to enable telnet servers.

SUMMARY STEPS

  1. configure
  2. interface MgmtEth interface-path-id
  3. ipv4 address ip-address mask
  4. mtu bytes
  5. no shutdown
  6. Do one of the following:
    • end
    • or
    • commit
    • or
  7. show interfaces MgmtEth interface-path-id

DETAILED STEPS

  Command or Action Purpose
Step 1

configure

Example:


RP/0/RP0/CPU0:routerconfigure terminal

Enters XR configuration mode.

Step 2

interface MgmtEth interface-path-id

Example:


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

Enters interface configuration mode and specifies the Ethernet interface name and notation rack /slot /module /port .

The example indicates port 0 on the card that is installed in slot 0.

Step 3

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 4

mtu bytes

Example:


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

(Optional) Sets the maximum transmission unit (MTU) byte value for the interface. The default is 1514.

  • The default is 1514 bytes.
  • The range for the Management Ethernet interface Interface mtu value is 64 to 1514 bytes.
Step 5

no shutdown

Example:


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

Removes the shutdown configuration, which removes the forced administrative down on the interface, enabling it to move to an up or down state.

Step 6

Do one of the following:

  • end
  • or
  • commit
  • or

Example:


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

Example:


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

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes: 

Uncommitted changes found, commit them before exiting(yes/no/cancel)? 
[cancel]:
    • Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to XR EXEC mode.
    • Entering no exits the configuration session and returns the router to XR EXEC mode without committing the configuration changes.
    • Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.
Step 7

show interfaces MgmtEth interface-path-id

Example:


RP/0/RP0/CPU0:router# show interfaces MgmtEth 0/RP0/CPU0/0

(Optional) Displays statistics for interfaces on the router.

Configuring the Duplex Mode for a Management Ethernet Interface

Perform this task to configure the duplex mode of the Management Ethernet interfaces for the RPs.

SUMMARY STEPS

  1. configure
  2. interface MgmtEth interface-path-id
  3. duplex [full | half ]
  4. Do one of the following:
    • end
    • or
    • commit
    • or

DETAILED STEPS

  Command or Action Purpose
Step 1

configure

Example:


RP/0/RP0/CPU0:router# configure

Enters XR configuration mode.

Step 2

interface MgmtEth interface-path-id

Example:


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

Enters interface configuration mode and specifies the Management Ethernet interface name and instance.

Step 3

duplex [full | half ]

Example:


RP/0/RP0/CPU0:router(config-if)# duplex full

Configures the interface duplex mode. Valid options are full or half .

Note 
To return the system to autonegotiated duplex operation, use the no duplex command.
Step 4

Do one of the following:

  • end
  • or
  • commit
  • or

Example:


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

Example:


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

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes: 

Uncommitted changes found, commit them before exiting(yes/no/cancel)? 
[cancel]:
    • Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to XR EXEC mode.
    • Entering no exits the configuration session and returns the router to XR EXEC mode without committing the configuration changes.
    • Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring the Speed for a Management Ethernet Interface

Perform this task to configure the speed of the Management Ethernet interfaces for the RPs.

SUMMARY STEPS

  1. configure
  2. interface MgmtEth interface-path-id
  3. speed {10 | 100 | 1000 }
  4. Do one of the following:
    • end
    • or
    • commit

DETAILED STEPS

  Command or Action Purpose
Step 1

configure

Example:


RP/0/RP0/CPU0:router# configure

Enters XR configuration mode.

Step 2

interface MgmtEth interface-path-id

Example:


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

Enters interface configuration mode and specifies the Management Ethernet interface name and instance.

Step 3

speed {10 | 100 | 1000 }

Example:


RP/0/RP0/CPU0:router(config-if)# speed 100

Configures the interface speed parameter.

speed options are or Mbps.

Note 
The default Management Ethernet interface speed is autonegotiated.
Note 
To return the system to the default autonegotiated speed, use the no speed command.
Step 4

Do one of the following:

  • end
  • or
  • commit

Example:


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

Example:


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

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes: 

Uncommitted changes found, commit them before exiting(yes/no/cancel)? 
[cancel]:
    • Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to XR EXEC mode.
    • Entering no exits the configuration session and returns the router to XR EXEC mode without committing the configuration changes.
    • Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Modifying the MAC Address for a Management Ethernet Interface

Perform this task to configure the MAC layer address of the Management Ethernet interfaces for the RPs.

SUMMARY STEPS

  1. configure
  2. interface MgmtEth interface-path-id
  3. mac-address address
  4. Do one of the following:
    • end
    • or
    • commit

DETAILED STEPS

  Command or Action Purpose
Step 1

configure

Example:


RP/0/RP0/CPU0:router# configure

Enters XR configuration mode.

Step 2

interface MgmtEth interface-path-id

Example:


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

Enters interface configuration mode and specifies the Management Ethernet interface name and instance.

Step 3

mac-address address

Example:


RP/0/RP0/CPU0:router(config-if)# mac-address 0001.2468.ABCD

Configures the MAC layer address of the Management Ethernet interface.

Note 
To return the device to its default MAC address, use the no mac-address address command.
Step 4

Do one of the following:

  • end
  • or
  • commit

Example:


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

Example:


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

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes: 

Uncommitted changes found, commit them before exiting(yes/no/cancel)? 
[cancel]:
    • Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to XR EXEC mode.
    • Entering no exits the configuration session and returns the router to XR EXEC mode without committing the configuration changes.
    • Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.
  • Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Verifying Management Ethernet Interface Configuration

Perform this task to verify configuration modifications on the Management Ethernet interfaces for the RPs.

SUMMARY STEPS

  1. show interfaces MgmtEth interface-path-id
  2. show running-config interface MgmtEth interface-path-id

DETAILED STEPS

  Command or Action Purpose
Step 1

show interfaces MgmtEth interface-path-id

Example:


RP/0/RP0/CPU0:router# show interfaces MgmtEth 0/RP0/CPU0/0

Displays the Management Ethernet interface configuration.

Step 2

show running-config interface MgmtEth interface-path-id

Example:


RP/0/RP0/CPU0:router# show running-config interface MgmtEth 0/RP0/CPU0/0

Displays the running configuration.

Configuration Examples for Management Ethernet Interfaces

This section provides the following configuration examples:

Configuring a Management Ethernet Interface: Example

This example displays advanced configuration and verification of the Management Ethernet interface on the RP: 


RP/0/RP0/CPU0:router# configure
RP/0/RP0/CPU0:router(config)# interface MgmtEth 0/RP0/CPU0/0
RP/0/RP0/CPU0:router(config)# ipv4 address 172.29.52.70 255.255.255.0
RP/0/RP0/CPU0:router(config-if)# speed 100
RP/0/RP0/CPU0:router(config-if)# duplex full
RP/0/RP0/CPU0:router(config-if)# no shutdown
RP/0/RP0/CPU0:router(config-if)# commit
RP/0/RP0/CPU0:Mar 26 01:09:28.685 :ifmgr[190]:%LINK-3-UPDOWN :Interface MgmtEth0/RP0/CPU0/0, changed state to Up
RP/0/RP0/CPU0:router(config-if)# end



RP/0/RP0/CPU0:router# show interfaces MgmtEth 0/RP0/CPU0/0
 
MMgmtEth0/RP0/CPU0/0 is up, line protocol is up
Hardware is Management Ethernet, address is 0011.93ef.e8ea (bia 0011.93ef.e8ea
)
Description: Connected to Lab LAN
Internet address is 172.29.52.70/24
MTU 1514 bytes, BW 100000 Kbit
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set,
ARP type ARPA, ARP timeout 04:00:00
Last clearing of "show interface" counters never
5 minute input rate 3000 bits/sec, 7 packets/sec
5 minute output rate 0 bits/sec, 1 packets/sec
30445 packets input, 1839328 bytes, 64 total input drops
0 drops for unrecognized upper-level protocol
Received 23564 broadcast packets, 0 multicast packets
0 runts, 0 giants, 0 throttles, 0 parity
57 input errors, 40 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
171672 packets output, 8029024 bytes, 0 total output drops
Output 16 broadcast packets, 0 multicast packets
0 output errors, 0 underruns, 0 applique, 0 resets
0 output buffer failures, 0 output buffers swapped out
1 carrier transitions


RP/0/RP0/CPU0:router# show running-config interface MgmtEth 0/RP0/CPU0/0
 
interface MgmtEth0/RP0/CPU0/0
description Connected to Lab LAN
ipv4 address 172.29.52.70 255.255.255.0
!

Additional References

These sections provide references related to Management Ethernet interface configuration.

Related Documents

Standards

Standards

Title

No new or modified standards are supported by this feature, and support for existing standards has not been modified by the feature.

—

MIBs

MIBs

MIBs Link

There are no applicable MIBs for this module.

To locate and download MIBs for selected platforms using Cisco IOS XR Software, use the Cisco MIB Locator found at the following URL:

http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

RFCs

RFCs

Title

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

—

Technical Assistance

Description

Link

The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/support