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.


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), HTTP, extensible markup language (XML), TFTP, Telnet, and command-line interface (CLI).

Prerequisites for Configuring Management Ethernet Interfaces

Before performing the Management Ethernet interface configuration procedures that are described in this chapter, be sure that the following 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.

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.

SUMMARY STEPS

  1. configure
  2. interface MgmtEth interface-path-id
  3. ipv4 address ip-address mask
  4. mtu bytes
  5. no shutdown
  6. end or commit
  7. show interfaces MgmtEth interface-path-id

DETAILED STEPS

Step 1

configure

Example:


RP/0/RP0/CPU0:router# configure

Enters global 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 RP card that is installed in slot 0.

Step 3

ipv4 address ip-address mask

Example:


RP/0/RP0/CPU0:router(config-if)# ipv4 address 1.76.18.150/16 (or) 
ipv4 address 1.76.18.150 255.255.0.0

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.255.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, /16 indicates that the first 16 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 1488

(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 values 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

end or commit

Example:


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

or 


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 EXEC mode.

  • Entering no exits the configuration session and returns the router to 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.

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-if)# ipv4 address  1.76.18.150/16

RP/0/RP0/CPU0:router(config-if)# no shutdown
RP/0/RP0/CPU0:router(config-if)# commit 
RP/0/RP0/CPU0:router: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 

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

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

interface MgmtEth0/RP0/CPU0/0
 mtu 1488
 ipv4 address 1.76.18.150/16
 ipv6 address 2002::14c:125a/64
 ipv6 enable
!
The following example displays VRF configuration and verification of the Management Ethernet interface on the RP with source address:

RP/0/RP0/CPU0: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
!
 
RP/0/RP0/CPU0: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
 
RP/0/RP0/CPU0:router# show run vrf   
Wed Jan 30 14:59:00.014 UTC
vrf httpupload
!

IPv6 Stateless Address Auto Configuration on Management Interface

Perform this task to enable IPv6 stateless auto configuration on Management interface.

SUMMARY STEPS

  1. configure
  2. interface MgmtEth interface-path-id
  3. ipv6 address autoconfig
  4. end or commit
  5. show ipv6 interfaces interface-path-id

DETAILED STEPS

Step 1

configure

Example:


RP/0/RP0/CPU0:router# configure

Enters global 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 RP card that is installed in slot 0.

Step 3

ipv6 address autoconfig

Example:


RP/0/RP0/CPU0:router(config-if)# ipv6 address autoconfig

Enable IPv6 stateless address auto configuration on the management port.

Step 4

end or commit

Example:


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

or 


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 EXEC mode.

  • Entering no exits the configuration session and returns the router to 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 5

show ipv6 interfaces interface-path-id

Example:


RP/0/RP0/CPU0:router# show ipv6 interfaces gigabitEthernet 0/2/0/0

(Optional) Displays statistics for interfaces on the router.

Example

This example displays : 


RP/0/RP0/CPU0:router# configure 
RP/0/RP0/CPU0:router(config)# interface MgmtEth 0/RP0/CPU0/0 
RP/0/RP0/CPU0:router(config-if)# ipv6 address autoconfig 
RP/0/RP0/CPU0:router(config-if)# commit 
RP/0/RP0/CPU0:router# show ipv6 interfaces gigabitEthernet 0/2/0/0 

Fri Nov  4 16:48:14.372 IST
GigabitEthernet0/2/0/0 is Up, ipv6 protocol is Up, Vrfid is default (0x60000000)
  IPv6 is enabled, link-local address is fe80::d1:1eff:fe2b:baf 
  Global unicast address(es):
    5::d1:1eff:fe2b:baf [AUTO CONFIGURED], subnet is 5::/64  <<<<<<  auto configured address 
  Joined group address(es): ff02::1:ff2b:baf ff02::2 ff02::1
  MTU is 1514 (1500 is available to IPv6)
  ICMP redirects are disabled
  ICMP unreachables are enabled
  ND DAD is enabled, number of DAD attempts 1
  ND reachable time is 0 milliseconds
  ND cache entry limit is 1000000000
  ND advertised retransmit interval is 0 milliseconds
  Hosts use stateless autoconfig for addresses.
  Outgoing access list is not set
  Inbound  common access list is not set, access list is not set
  Table Id is 0xe0800000
  Complete protocol adjacency: 0
  Complete glean adjacency: 0
  Incomplete protocol adjacency: 0
  Incomplete glean adjacency: 0
  Dropped protocol request: 0
  Dropped glean request: 0

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. end or commit

DETAILED STEPS

Step 1

configure

Example:


RP/0/RP0/CPU0:router# configure

Enters global 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

end or commit

Example:


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

or 


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 EXEC mode.

  • Entering no exits the configuration session and returns the router to 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.

SUMMARY STEPS

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

DETAILED STEPS

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.

Information About Configuring Management Ethernet Interfaces

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

Dense Wavelength Division Multiplexing Tunable Optics

The Dense Wavelength-Division Multiplexing (DWDM) wavelengths of the DWDM-SFP10G-C module on the Cisco NCS 5500 Series Aggregation Services Routers is tunable. You can configure the DWDM ITU wavelengths by using the itu channel command in the interface configuration mode. The itu channel command ensures that the traffic continues to flow.

The following table contains the wavelength mapping information for the DWDM module:

Channel Frequency (THz) Wavelength (nm)
1

191.35

1566.723
2

191.40

1566.314
3

191.45

1565.905
4

191.50

1565.496
5

191.55

1565.087
6

191.60

1564.679
7

191.65

1564.271
8

191.70

1563.863
9

191.75

1563.455
10

191.80

1563.047
11

191.85

1562.640
12

191.90

1562.233
13

191.95

1561.826
14

192.00

1561.419
15

192.05

1561.013
16

192.10

1560.606
17

192.15

1560.200
18

192.20

1559.794
19

192.25

1559.389
20

192.30

1558.983
21

192.35

1558.578
22

192.40

1558.173
23

192.45

1557.768
24

192.50

1557.363
25

192.55

1556.959
26

192.60

1556.555
27

192.65

1556.151
28

192.70

1555.747
29

192.75

1555.343
30

192.80

1554.940
31

192.85

1554.537
32

192.90

1554.134
33

192.95

1553.731
34

193.00

1553.329
35

193.05

1552.926
36

193.10

1552.524
37

193.15

1552.122
38

193.20

1551.721
39

193.25

1551.319
40

193.30

1550.918
41

193.35

1550.517
42

193.40

1550.116
43

193.45

1549.715
44

193.50

1549.315
45

193.55

1548.915
46

193.60

1548.515
47

193.65

1548.115
48

193.70

1547.715
49

193.75

1547.316
50

193.80

1546.917
51

193.85

1546.518
52

193.90

1546.119
53

193.95

1545.720
54

194.00

1545.322
55

194.05

1544.924
56

194.10

1544.526
57

194.15

1544.128
58

194.20

1543.730
59

194.25

1543.333
60

194.30

1542.936
61

194.35

1542.539
62

194.40

1542.142
63

194.45

1541.746
64

194.50

1541.349
65

194.55

1540.953
66

194.60

1540.557
67

194.65

1540.162
68

194.70

1539.766
69

194.75

1539.371
70

194.80

1538.976
71

194.85

1538.581
72

194.90

1538.186
73

194.95

1537.792
74

195.00

1537.397
75

195.05

1537.003
76

195.10

1536.609
77

195.15

1536.216
78

195.20

1535.822
79

195.25

1535.429
80

195.30

1535.036
81

195.35

1534.643
82

195.40

1534.250
83

195.45

1533.858
84

195.50

1533.465
85

195.55

1533.073
86

195.60

1532.681
87

195.65

1532.290
88

195.70

1531.898
89

195.75

1531.507
90

195.80

1531.116
91

195.85

1530.725
92

195.90

1530.334
93

195.95

1529.944
94

196.00

1529.553
95

196.05

1529.163

96

196.10

1528.773

Note

For more information on limitations of this feature and details about optical parameters, see https://www.cisco.com/c/en/us/products/collateral/interfaces-modules/dwdm-transceiver-modules/data_sheet_c78-711186.html.