> Getting Started
> Following sucessful installation of the system hardware, you must configure a set of software parameters. You then save these settings in a system configuration file that is launched whenever the system is reloaded.
> This chapter provides instructions for connecting to the console port and creating the initial local context management configuration. It includes the following sections:

> • | ASR 5000 Configuration

> • | Using the ASR 5000 Quick Setup Wizard

> • | Using the CLI for Initial Configuration

> • | Configuring the System for Remote Access

> • | Configuring the Management Interface with a Second IP Address

> ASR 5000 Configuration
> The first time power is applied to the system, the active System Management Card (SMC) (typically the one installed in chassis slot 8) automatically launches a Quick Setup Wizard on its console port.
> The serial console port is located on the SPIO card installed in slot 24. This wizard is guides you through the initial configuration of the system.
> You can choose not to use the wizard and perform the initial configuration by issuing commands via the command line interface (CLI). You can manually launch the wizard by running the setup command in the Exec mode. Refer to the Command Line Interface Reference for details.
> The following sections describe how to configure the system.
> Using the ASR 5000 Quick Setup Wizard
> The Quick Setup Wizard consists of three parts:

> • | Configuring a context-level security administrator and hostname

> • | Configuring the Ethernet interface for out-of-band (OOB) management

> • | Configuring the system for remote CLI access via Telnet, Secure Shell (SSH), or File Transfer Protocol (FTP)

> The following figure and table provides a flow diagram that shows the run logic of the wizard along with additional information and notes.
> ASR 5000 Quick Setup Wizard Logic Diagram
> Quick Setup Wizard Logic Diagram Callout Descriptions

> Item | Description/Notes
> 1 | Enter or exit the wizard.
> • | Enter no at the prompt to automatically be directed to the command line interface (CLI). Proceed to the Using the CLI for Initial Configuration section for instructions on performing an initial system configuration with the CLI.
> • | Enter setup at the command prompt to re-invoke the wizard.
> 2 | Configure an administrative username/password and a hostname for the system.
> • | The name of the default administrative user configured through the wizard is admin.
> • | Administrative user names can be up to 32 alphanumeric characters and are case sensitive.
> • | Administrative user passwords can be up to 63 alphanumeric characters and are case sensitive.
> • | Configure a valid, non-null hostname. The hostname can consist of up to 63 alphanumeric characters and is case sensitive.
> 3 | Configure a single Switch Processor Input/Output (SPIO) out-of-band management interface for out-of-band system management.
> • | Traffic on the management LAN is not transferred over the same media as user data and control signaling.
> • | For security reasons, it is recommended that management functions be maintained on a separate network from user data and control signaling.
> • | Depending on the medium being used to access the network, Ethernet or fiber:
> • | SPIO1 represents either the Ethernet 1 or SFP 1 interface on the SPIO, as shown in the figure below. SPIO1 is the default.
> • | SPIO2 represents either the Ethernet 2 or SFP 2 interface on the SPIO.
> • | Use the RJ-45 interfaces to connect the system to the management network with CAT3 or CAT5 Ethernet cable. Use the SFP interfaces to connect the system to the management network with 1000Base-SX optical fiber cable. The default is rj-45.
> • | Configure an IP address, subnet mask, and gateway for the interface.
> • | Instructions for configuring the second management interface on the SPIO can be found in Configuring System Settings.
> 4 | Enable various remote access protocols for accessing the system.
> • | Secure Shell (SSH) uses TCP port number 22 by default, if enabled.
> • | SSH V1 and/or V2 are supported.
> • | If SSH is enabled, you can also enable SSH File Transfer Protocol (SFTP) server functionality.
> • | Telnet uses TCP port number 23 by default, if enabled.
> • | The File Transfer Protocol (FTP) uses TCP port number 21 by default, if enabled.
> For maximum security, it is recommended that you use only SSH v2.
> 5 | Review and/or modify the configuration of previous prompts.
> 1. | Enter the number of the prompt to be modified.
> 2. | Configure the parameter.
> 3. | Optional. Repeat step 1 and step 2 to modify additional settings.
> 4. | Enter “done” when you have completed all changes.
> 6 | Review the configure script created by the wizard based on your inputs. An example of a created script is displayed in the example below. Variables are displayed in italics (variable).
> 7 | Apply the configuration file to the system. Once applied, the parameter configuration is automatically saved to the system.cfg file stored on the primary SMC compact flash card.

> ‌
> SPIO Interfaces
> config
> system hostname <hostname>
> context local
> administrator <admin_name> password <passwd>
> interface spio1
> ip address <ip_address> subnet
> #exit
> ip route 0.0.0.0 0.0.0.0 <gw_address> spio1
> ssh key <v1_key>
> ssh key <v2_rsa_key>
> ssh key <v2_dsa_key>
> server sshd
> subsystem sftp
> #exit
> no server telnetd
> server ftpd
> no server telnetd
> #exit
> port ethernet 24/1
> bind interface spio1 local
> no shutdown
> media rj45
> #exit
> end
> Important: Once configuration using the wizard is complete, proceed to instructions on configuring other system parameters.
> Using the CLI for Initial Configuration
> The initial configuration consists of the following:

> • | Configuring a context-level security administrator and hostname

> • | Configuring the Ethernet interface(s) on the SPIO that is installed behind the primary SMC

> • | Configuring the system for remote CLI access via Telnet, SSH, or FTP (secured or unsecured)

> This section provides instructions for performing these tasks using the CLI.

> Step 1 | At the CLI prompt, enter:

> [local]host_name# configure
> [local]host_name(config)#

> Step 2 | Enter the context configuration mode by entering the following command:

> [local]host_name(config)# context local
> [local]host_name(config-ctx)#
> The local context is the system’s management context. Contexts allow you to logically group services or interfaces. A single context can consist of multiple services and can be bound to multiple interfaces.

> Step 3 | Enter the following command to configure a context-level security administrator for the system:

> administrator <name> { password <password> | encrypted password <enc_password> } [ ftp ] [ no-cli ] [ timeout-absolute <absolute_time> ] [ timeout-idle <idle_time> ]

> Keyword/Variable | Description
> <name> | Specifies the security administrator’s name. The name can be between 1 and 32 alphanumeric characters and is case sensitive.
> password <password> | Specifies the password for the security administrator. The password can be between 1 and 63 alphanumeric characters and is case sensitive.
> encrypted password | Specifies the encrypted password for the security administrator. The keyword is only used by the system when you save configuration scripts. The system displays the encrypted keyword in the configuration file as a flag indicating that the variable following the keyword is the encrypted version of the plain text password. Only the encrypted password is saved as part of the configuration file.
> ftp | Specifies that the security administrator is allowed to access the system with the File Transfer Protocol (FTP). This option is useful to upload files (configuration or software images) to the system’s flash memory.
> no-cli | Specifies that the security administrator cannot access the system’s command line interface (CLI). Use this keyword in conjunction with the ftp keyword to allow access to the system with FTP only.
> timeout-absolute | Specifies the maximum amount of time that the operator can maintain a session with the system. The absolute_time is measured in seconds. Use any integer value between 0 and 300000000. The default absolute_time is 0. In the event that the absolute timeout value is reached, the operator session is automatically terminated.
> timeout-idle | Specifies the maximum amount of time that an operator session can remain idle before being automatically terminated. The idle_time is measured in seconds. Use any integer value between 0 and 300000000. The default idle_time is 0.

> ‌
> Important: You must configure a context-level security administrator during the initial configuration. After you complete the initial configuration process and end the CLI session, if you have not configured a security administrator, CLI access will be locked.

> Step 4 | Enter the following command at the prompt to exit the context configuration mode:

> [local]host_name(config-ctx)# exit
> [local]host_name(config)#

> Step 5 | Enter the following command to configure a hostname by which the system will be recognized on the network:

> [local]host_name(config)# system hostname <host_name>
> <host_name> is the name by which the system will be recognized on the network. The hostname can be up to 63 alphanumeric characters and is case sensitive.

> Step 6 | Configure the network interfaces on the SPIO using the following instructions:

> Step a | Enter the context configuration mode by entering the following commands:

> [local]host_name(config)# context local
> [local]host_name(config-ctx)#

> Step b | Enter the following command to specify a name for the interface:

> [local]host_name(config-ctx)#interface<interface_name>
> <interface_name> is the name of the interface. The interface name can be between 1 and 79 alphanumeric characters and is case sensitive. The following prompt appears as the system enters the Ethernet Interface Configuration mode:
> [local]host_name(config-if-eth)#

> Step c | Configure an IP address for the interface configured in the previous step by entering the following command:

> { ip address | ipv6 address } <ipaddress> <subnetmask>

> Variable | Description
> IPv4 – ip address
> ipaddress | Specifies the IP address for the interface in IPv4 dotted-decimal format.
> subnetmask | Specifies the subnet mask for the interface in IPv4 dotted-decimal or CIDR notation.
> IPv6 – ipv6 address
> ipaddress | Specifies the IP address for the interface in IPv6 colon-separated format.
> subnetmask | Specifies the subnet mask for the interface in IPv6 colon-separated or CIDR notation.

> ‌
> Important: If you are executing this command to correct an address or subnet that was mis-configured with the Quick Setup Wizard, you must verify the default route and port binding configuration. Use step 11 and step 6 of this procedure. If there are issues, perform steps 7e through 7k to reconfigure the information.

> Step d | Enter the following command to exit the Ethernet interface configuration mode:

> [local]host_name(config-if-eth)# exit
> [local]host_name(config-ctx)#

> Step e | Configure a static route, if required, to point the system to a default gateway. Entering the following command:

> { ip | ipv6 } route <gw_address> <interface_name>

> Variable | Description
> gw_address | Specifies the IP address of the default gateway in IPv4 dotted-decimal format or IPv6 colon-separated format.
> interface_name | Specifies the name of the interface that was configured in step 7b.

> ‌

> Step f | Enter the following to exit from the context configuration mode:

> [local]host_name(config-ctx)# exit
> [local]host_name(config)#

> Step g | Enter the Ethernet Port Configuration mode:

> port ethernet <slot#>/<port#>

> Variable | Description
> slot# | The actual chassis slot in which the SPIO is installed. This could be either slot number 24 or 25.
> port# | The physical port on the SPIO that will be used. This will be either port 1 or 2. Port 1 represents the top most port (either RJ-45 or SFP).

> ‌

> Step h | Bind the port to the interface that you created in step 7b. Binding associates the port and all of its settings to the interface. Enter the following command:

> [local]host_name(config-port-<slot#/port#>)# bind interface <interface_name> local
> [local]host_name(config-port-<slot#/port#>)# no shutdown
> <interface_name> is the name of the interface that you configured in step 7b.

> Step i | Specify which Ethernet media you are using. Enter the following:

> [local]host_name(config-port-<slot#/port#>)# media [ rj45 | sfp ]
> The SPIO is equipped with dual RJ-45 and dual SFP interfaces. The RJ-45 interfaces connect the system to the management network with CAT3 or CAT5 Ethernet cable. The SFP interfaces connect the system to the management network with 1000Base-SX optical fiber cable.

> Step j | Configure the port speed, if needed, by entering the following command:

> medium { auto | speed { 10 | 100 | 1000 | 10000 } duplex { full | half } }

> Keyword/Variable | Description
> auto | Configures the system to auto detect the port speed. This is the default setting.
> speed | Specifies the port speed for the port itself. When manually configuring the port speed, you must ensure that the network server configuration supports the speed and duplex configuration. The possible rates are:
> • | 10 = 10 Mbps
> • | 100 = 100 Mbps
> • | 1000 = 1000 Mbps
> Use 1000 Mbps only for the SFP ports on the GELC/GLC2, QGLC or SPIO Line Cards. If you manually configure the port speed, you must also configure the duplex mode.
> duplex | If you manually configure the speed, you must also use this parameter to configure the duplex mode. You can implement either a full or half duplex mode. Ethernet networking rules dictate that if a device whose interface is configured to auto-negotiate is communicating with a device that is manually configured to support full duplex mode, the first device negotiates with the manually configured speed of the second device, but only communicates in half duplex mode.

> ‌

> Step k | Exit the Ethernet Interface Configuration mode by entering the command:

> [local]host_name(config-port-<slot#/port#>)# exit
> [local]host_name(config)#
> Important: Refer below for instructions on configuring the SPIO management interface with a second IP address.
> Configuring the System for Remote Access
> Configure the system for remote access. An administrative user may access the system from a remote location over a local area network (LAN) or wide area network (WAN):

> • | Telnet

> • | Secure Shell (SSH)

> • | File Transfer Protocol (FTP) (secured or unsecured)

> • | Trivial File Transfer Protocol (TFTP)

> Important: If there are two simultaneous telnet sessions, and one administrator deletes the context into which the other administrator is logged, the administrator in the deleted context will not be automatically kicked into the local context. Although the deleted context will still appear in the CLI prompt, context specific commands will generate errors.
> Important: For maximum security, use SSH v2.

> Step 1 | Enter the context configuration mode by entering the following command:

> [local]host_name(config)# context local
> [local]host_name(config-ctx)#

> Step 2 | Configure the system to allow Telnet access, if desired:

> [local]host_name(config-ctx)# server telnetd

> Step 3 | Configure the system to allow SSH access, if desired:

> [local]host_name(config-ctx)# ssh generate key [ type { v1-rsa | v2-rsa | v2-dsa } ]
> Important: v2-rsa is the recommended key type.
> [local]host_name(config-ctx)# server sshd
> [local]host_name(config-sshd)# subsystem sftp
> [local]host_name(config-sshd)# exit

> Step 4 | Configure the system to allow FTP access, if desired, by entering the following command:

> [local]host_name(config-ctx)# server ftpd

> Step 5 | Exit the configuration mode by entering the following command:

> [local]host_name(config-ctx)# end
> [local]host_name#

> Step 6 | Verify the configuration by entering the following command:

> [local]host_name# show configuration
> The CLI output should be similar to the sample output:
> context local
> interface <interface_name>
> ip address <ipaddress> <subnetmask>
> exit
> subscriber default
> exit
> administrator <admin_name> password <admin_password>
> server telnetd
> server ftpd
> ssh generate key
> server sshd
> subsystem sftp
> exit
> port ethernet 24/1
> bind interface <interface_name> local
> exit
> port ethernet 24/1
> no shutdown
> exit
> snmp engine-id local 800007e580ed826c191ded2d3d
> end

> Step 7 | Verify the configuration of the IP routes by entering the following command:

> [local]host_name# show ip route
> The CLI output should be similar to the sample output:
> "*" indicates the Best or Used route.
> Destination Nexthop Protocol Prec Cost Interface
> *0.0.0.0/0 <ipaddress> static 1 0 spio1
> *<network> 0.0.0.0 connected 0 0 spio1

> Step 8 | Verify the interface binding by entering the following command:

> [local]host_name# show ip interface name <interface_name>
> <interface_name> is the name of the interface that was configured in step 7b.The CLI output should be similar to the sample output:
> Intf Name: spio1Intf Type: Broadcast
> Description:
> IP State: UP (Bound to 24/1 untagged, ifIndex 402718721)
> IP Address: <ipaddress> Subnet Mask: <subnetmask>
> Bcast Address: <bcastaddress> MTU: 1500
> Resoln Type: ARP ARP timeout: 3600 secs
> L3 monitor LC-port switchover: Disabled
> Number of Secondary Addresses: 0

> Step 9 | Save your configuration as described in the Verifying and Saving Your Configuration chapter.

> Configuring the Management Interface with a Second IP Address
> If necessary, you can configure a second IP address on the SPIO management interface.

> Step 1 | Enter the configuration mode by entering the following command at the prompt:

> [local]host_name# configure
> [local]host_name(config)#

> Step 2 | Enter the following to enter the context configuration mode:

> [local]host_name(config)# context local
> [local]host-name(config-ctx)#

> Step 3 | Enter the interface slot number and port number by entering the following command:

> [local]host_name(config-ctx)# 24/1
> [local]host_name(config-if-eth)#

> Step 4 | Enter the secondary IP address and subnet mask by entering the following command:

> [local]host_name(config-if-eth)# { ip | ipv } address ipaddress subnet_mask secondary

> Step 5 | Exit the configuration mode by entering the following command:

> [local]host_name(config-if-eth)# end

> Step 6 | Confirm the interface ip addresses by entering the following command:

> [local]host_name# show config context local
> The CLI output should look similar to this example:
> config
> context local
> interface <interface_name>
> ip address <ipaddress> <subnetmask>
> ip address <ipaddress> <subnetmask> secondary
> #exit

> Step 7 | Save your configuration as described in the Verifying and Saving Your Configuration chapter.

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883