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

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.


Figure 1. ASR 5000 Quick Setup Wizard Logic Diagram

Table 1. Quick Setup Wizard Logic Diagram Callout Descriptions
Item Task 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 name is an alphanumeric string of 1 through 32 characters that is case sensitive.

Administrative user password is an alphaumeric string of 1 through 63 characters that is case sensitive.

Configure a valid, non-null hostname. The hostname is an alphanumeric string of 1 through 63 characters that is case sensitive.

3

Change chassis key value.

(Release 12.2 and higher)

A unique chassis key is configured at the factory for each system. This key is used to decrypt encrypted passwords found in generated configuration files. The system administrator can create a unique chassis key that will be used to encrypt passwords stored in configuration files.

Enter yes to set a new chassis key. Refer to the instructions in System Settings. Additional information can be found in System Security.

4

Configure a single 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, management functions should be maintained on a separate network from user data and control signaling.

The port nomenclature vaires based 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. 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 System Settings.

5

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, use only SSH v2.

6

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.

7

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).

8

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.




Figure 2. SPIO IP 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.

  1. At the CLI prompt, enter:
    [local]host_name# configure
    
    [local]host_name(config)#
  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.
  3. Enter the following command to configure a context-level security administrator for the system:
    administrator user_name [ encrypted ] password password | [ ecs ] [ expiry-date date_time ] [ ftp ] [ li-administration ] [ nocli ] [ noecs ] [ timeout-absolute timeout_absolute  ] [ timeout-min-absolute timeout_min_absolute ] [ timeout-idle timeout_idle ] [ timeout-min-idle timeout_min_idle ]
    

    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. For complete information on the above command, see the Context Configuration Mode Commands chapter of the Command Line Interface Reference.

  4. Enter the following command at the prompt to exit the context configuration mode:
    [local]host_name(config-ctx)# exit
    
    [local]host_name(config)#
    
  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 is an alphanumeric string of 1 through 63 characters that is case sensitive.
  6. Configure the network interfaces on the SPIO using the following instructions:
    1. Enter the context configuration mode by entering the following commands:
      [local]host_name(config)# context local
      
      [local]host_name(config-ctx)#
      
    2. 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 expressed as an alphanumeric string of 1 through 79 characters that is case sensitive. The following prompt appears as the system enters the Ethernet Interface Configuration mode:
      [local]host_name(config-if-eth)#
      
    3. Configure an IP address for the interface configured in the previous step by entering the following command:
      { ip address | ipv6
      address } ipaddress subnetmask
      

      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.

    4. Enter the following command to exit the Ethernet interface configuration mode:
      [local]host_name(config-if-eth)# exit
      
      [local]host_name(config-ctx)#
      
    5. 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
      
    6. Enter the following to exit from the context configuration mode:
      [local]host_name(config-ctx)# exit
      
      [local]host_name(config)#
      
    7. Enter the Ethernet Port Configuration mode:
      [local]host_name(config)#port ethernet slot#/port#
      
    8. 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.
    9. 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.
    10. Configure the port speed, if needed, by entering the following command:
      medium { auto | speed { 10 | 100 | 1000 | 10000 } duplex { full | half } }
      
    11. 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.

  1. Enter the context configuration mode by entering the following command:
    [local]host_name(config)# context local
    
    [local]host_name(config-ctx)#
    
  2. Configure the system to allow Telnet access, if desired:
    [local]host_name(config-ctx)# server telnetd
    
  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
    
  4. Configure the system to allow FTP access, if desired, by entering the following command:
    [local]host_name(config-ctx)# server ftpd
    
  5. Exit the configuration mode by entering the following command:
    [local]host_name(config-ctx)# end
    
    [local]host_name#
    
  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
    
  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
    
  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 
    
  9. Save your configuration as described in Verifying and Saving Your Configuration.

Configuring the Management Interface with a Second IP Address

If necessary, you can configure a second IP address on the SPIO management interface.

  1. Enter the configuration mode by entering the following command at the prompt:
    [local]host_name#  configure
    
    [local]host_name(config)#
    
  2. Enter the following to enter the context configuration mode:
    [local]host_name(config)# context local
    
    [local]host-name(config-ctx)#
    
  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)#
    
  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
    
  5. Exit the configuration mode by entering the following command:
    [local]host_name(config-if-eth)# end
    
  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
    
  7. Save your configuration as described in Verifying and Saving Your Configuration.