Table Of Contents
Using the Management Ethernet Interface
The Cisco ASR 1000 Series Routers have one Gigabit Ethernet Management Ethernet interface on each Route Processor.
Finding Feature Information in This Module
Your software release might not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Using the Management Ethernet Interface" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
This guide covers the following topics:
Gigabit Ethernet Management Interface Overview
The purpose of this interface is to allow users to perform management tasks on the router; it is basically an interface that should not and often cannot forward network traffic but can otherwise access the router, often via Telnet and SSH, and perform most management tasks on the router. The interface is most useful before a router has begun routing, or in troubleshooting scenarios when the SPA interfaces are inactive.
The following aspects of the Management Ethernet interface should be noted:
•Each RP has a Management Ethernet interface, but only the active RP has an accessible Management Ethernet interface (the standby RP can be accessed using the console port, however).
•IPv4, IPv6, and ARP are the only routed protocols supported for the interface.
•The interface provides a method of access to the router even if the SPA interfaces or the IOS processes are down.
•The Ethernet Management Interface cannot be used as a Lawful Intercept MD source interface.
•The Management Ethernet interface is part of its own VRF. This is discussed in more detail in the "Gigabit Ethernet Management Interface VRF" section.
Gigabit Ethernet Port Numbering
The Gigabit Ethernet Management port is always GigabitEthernet0.
In a dual RP configuration, the Management Ethernet interface on the active RP will always be Gigabit Ethernet 0, while the Management Ethernet interface on the standby RP will not be accessible using the Cisco IOS CLI in the same telnet session. The standby RP can be telnetted to through the console port, however.
The port can be accessed in configuration mode like any other port on the Cisco ASR 1000 Series Routers:Router#config tEnter configuration commands, one per line. End with CNTL/Z.Router(config)#interface gigabitethernet0Router(config-if)#
IP Address Handling in ROMmon and the Management Ethernet Port
On the Cisco ASR 1000 Series Routers, IP addresses can be configured in ROMmon (the IP_ADDRESS= and IP_SUBNET_MASK= commands) and through the use of the IOS command-line interface (the ip address command in interface configuration mode).
Assuming the IOS process has not begun running on the Cisco ASR 1000 Series Router, the IP address that was set in ROMmon acts as the IP address of the Management Ethernet interface. In cases where the IOS process is running and has taken control of the Management Ethernet interface, the IP address specified when configuring the Gigabit Ethernet 0 interface in the IOS CLI becomes the IP address of the Management Ethernet interface. The ROMmon-defined IP address is only used as the interface address when the IOS process is inactive.
For this reason, the IP addresses specified in ROMmon and in the IOS CLI can be identical and the Management Ethernet interface will function properly in single RP configurations.
In dual RP configurations, however, users should never configure the IP address in the ROMmon on either RP0 or RP1 to match each other or the IP address as defined by the IOS CLI. Configuring matching IP addresses introduces the possibility for an active and standby Management Ethernet interface having the same IP address with different MAC addresses, which will lead to unpredictable traffic treatment.
Gigabit Ethernet Management Interface VRF
The Gigabit Ethernet Management interface is automatically part of its own VRF. This VRF, which is named "Mgmt-intf," is automatically configured on the Cisco ASR 1000 Series Router and is dedicated to the Management Ethernet interface; no other interfaces can join this VRF. Therefore, this VRF does not participate in the MPLS VPN VRF or any other network-wide VRF.
Placing the management ethernet interface in its own VRF has the following effects on the Management Ethernet interface:
•Many features must be configured or used inside the VRF, so the CLI may be different for certain Management Ethernet functions on the Cisco ASR 1000 Series Routers than on Management Ethernet interfaces on other routers.
•Prevents transit traffic from traversing the router. Because all of the SPA interfaces and the Management Ethernet interface are automatically in different VRFs, no transit traffic can enter the Management Ethernet interface and leave a SPA interface, or vice versa.
•Improved security of the interface. Because the Mgmt-intf VRF has its own routing table as a result of being in its own VRF, routes can only be added to the routing table of the Management Ethernet interface if explicitly entered by a user.
The Management Ethernet interface VRF supports both IPv4 and IPv6 address families.
Common Ethernet Management Tasks
Because users can perform most tasks on a router through the Management Ethernet interface, many tasks can be done by accessing the router through the Management Ethernet interface.
This section documents tasks that might be common or slightly tricky on the Cisco ASR 1000 Series Routers. It is not intended as a comprehensive list of all tasks that can be done using the Management Ethernet interface.
This section covers the following processes:
Viewing the VRF Configuration
The VRF configuration for the Management Ethernet interface is viewable using the show running-config vrf command.
This example shows the default VRF configuration:Router# show running-config vrfBuilding configuration...Current configuration : 351 bytesvrf definition Mgmt-intf!address-family ipv4exit-address-family!address-family ipv6exit-address-family!(some output removed for brevity)
Viewing Detailed VRF Information for the Management Ethernet VRF
To see detailed information about the Management Ethernet VRF, enter the show vrf detail Mgmt-intf command:Router# show vrf detail Mgmt-intfVRF Mgmt-intf (VRF Id = 4085); default RD <not set>; default VPNID <not set>Interfaces:Gi0Address family ipv4 (Table ID = 4085 (0xFF5)):No Export VPN route-target communitiesNo Import VPN route-target communitiesNo import route-mapNo export route-mapVRF label distribution protocol: not configuredVRF label allocation mode: per-prefixAddress family ipv6 (Table ID = 503316481 (0x1E000001)):No Export VPN route-target communitiesNo Import VPN route-target communitiesNo import route-mapNo export route-mapVRF label distribution protocol: not configuredVRF label allocation mode: per-prefix
Setting a Default Route in the Management Ethernet Interface VRF
To set a default route in the Management Ethernet Interface VRF, enter the following command
ip route vrf Mgmt-intf 0.0.0.0 0.0.0.0 next-hop-IP-address
Setting the Management Ethernet IP Address
The IP address of the Management Ethernet port is set like the IP address on any other interface.
Below are two simple examples of configuring an IPv4 adress and an IPv6 address on the Management Ethernet interface.
IPv4 ExampleRouter(config)# interface GigabitEthernet 0Router(config-if)# ip address A.B.C.D A.B.C.D
IPv6 ExampleRouter(config)# interface GigabitEthernet 0
Router(config-if)# ipv6 address X:X:X:X::X
Telnetting over the Management Ethernet Interface
Telnetting can be done through the VRF using the Management Ethernet interface.
In the following example, the router telnets to 172.17.1.1 through the Management Ethernet interface VRF:Router# telnet 172.17.1.1 /vrf Mgmt-intf
Pinging over the Management Ethernet Interface
Pinging other interfaces using the Management Ethernet interface is done through the VRF.
In the following example, the router pings the interface with the IP address of 172.17.1.1 through the Management Ethernet interface:Router# ping vrf Mgmt-intf 172.17.1.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 172.17.1.1, timeout is 2 seconds:.!!!!Success rate is 80 percent (4/5), round-trip min/avg/max = 1/1/1 ms
Copy Using TFTP or FTP
To copy a file using TFTP through the Management Ethernet interface, the ip tftp source-interface GigabitEthernet 0 command must be entered before entering the copy tftp command because the copy tftp command has no option of specifying a VRF name.
Similarly, to copy a file using FTP through the Management Ethernet interface, the ip ftp source-interface GigabitEthernet 0 command must be entered before entering the copy ftp command because the copy ftp command has no option of specifying a VRF name.
TFTP ExampleRouter(config)# ip tftp source-interface gigabitethernet 0
FTP ExampleRouter(config)# ip ftp source-interface gigabitethernet 0
To allow the software clock to be synchronized by a Network Time Protocol (NTP) time server over the Management Ethernet interface, enter the ntp server vrf Mgmt-intf command and specify the IP address of the device providing the update.
The following CLI provides an example of this procedure.Router(config)# ntp server vrf Mgmt-intf 172.17.1.1
To specify the Management Ethernet interface as the source IP or IPv6 address for logging purposes, enter the logging host <ip-address> vrf Mgmt-intf command.
The following CLI provides an example of this procedure.Router(config)# logging host <ip-address> vrf Mgmt-intf
To specify the Management Ethernet interface as the source of all SNMP trap messages, enter the snmp-server source-interface traps gigabitEthernet 0 command.
The following CLI provides an example of this procedure:Router(config)# snmp-server source-interface traps gigabitEthernet 0
Domain Name Assignment
The IP domain name assignment for the Management Ethernet interface is done through the VRF.
To define the default domain name as the Management Ethernet VRF interface, enter the ip domain-name vrf Mgmt-intf domain command.Router(config)# ip domain-name vrf Mgmt-intf cisco.com
To specify the Management Ethernet interface VRF as a name server, enter the ip name-server vrf Mgmt-intf IPv4-or-IPv6-address command.Router(config)# ip name-server vrf Mgmt-intf IPv4-or-IPv6-address
RADIUS or TACACS+ Server
To group the Management VRF as part of a AAA server group, enter the ip vrf forward Mgmt-intf command when configuring the AAA server group.
The same concept is true for configuring a TACACS+ server group. To group the Management VRF as part of a TACACS+ server group, enter the ip vrf forwarding Mgmt-intf command when configuring the TACACS+ server group.
RADIUS Server Group ConfigurationRouter(config)# aaa group server radius helloRouter(config-sg-radius)# ip vrf forwarding Mgmt-intf
TACACS+ Server Group Exampleouter(config)# aaa group server tacacs+ helloRouter(config-sg-tacacs+)# ip vrf forwarding Mgmt-intf
VTY lines with ACL
To ensure an access control list (ACL) is attached to vty lines that are and are not using VRF, use the vrf-also option when attaching the ACL to the vty lines.Router(config)# line vty 0 4Router(config-line)# access-class 90 in vrf-also
MIB MIBs Link
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at this URL:
Feature Information for Using the Management Ethernet Interface
Table 3 lists the features in this module and provides links to specific configuration information.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 3 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Table 3 Feature Information for Using the Management Ethernet Interface
Feature Name Releases Feature Information
Using the Management Ethernet Interface
Cisco IOS XE 2.1S
This feature was introduced.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
Copyright © 2008 - 2013 Cisco Systems, Inc. All rights reserved.