System Settings

This chapter provides instructions for configuring the following system options:

It is assumed that the procedures to initially configure the system as described in Getting Started have been completed.

IMPORTANT:

The commands used in the configuration examples in this section are the most likely-used commands and/or keyword options. In many cases, other optional commands and/or keyword options are available. Refer to the Command Line Interface Reference for complete information.

Configuring a Second Management Interface

Refer to Getting Started for instructions on configuring a system management interface on the Management Input/Output (MIO) or Management Input/Output Universal (UMIO) card. This section provides described how to configure a second management interface.

Use the following example to configure a second management interface:
configure
   context local
      interface interface_name
         ip address ipaddress subnetmask
         exit
      ip route 0.0.0.0
0.0.0.0 gw_address interface_name
      exit
   port ethernet slot#/port#
      bind interface interface_name local
      no shutdown
      media [ rj45 | sfp ]
      end
Notes:
  • For port ethernet slot#, use the actual chassis slot in which the active MIO/UMIO is installed (slot number 5 or 6).
  • Enter IP addresses using IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.
  • For port ethernet port#, use the physical port on the MIO/UMIO card that will be used. This is either port 1 or 2. Port 1 represents the top-most port (either RJ-45 or SFP).
  • The MIO/UMIO is equipped with RJ-45 (1000Base-T copper) interfaces. The RJ-45 interfaces connect the system to the management network with CAT3 or CAT5 Ethernet cable.
  • Option: In the Ethernet Port configuration mode, configure the port speed, if needed, by entering the medium command. Refer to the Command Line Interface Reference for a complete explanation of this command.
  • In the { ip | ipv6 } route command, other keyword options, instead of the gateway IP address, are available and include: next-hop IP address, point-to-point, and tunnel.

Verifying and Saving Your Interface and Port Configuration

Verify that your interface configuration settings are correct by entering the following command:
show ip interface
The output from this command should be similar to that shown below. In this example an interface named mgmt2 was configured in the local context.
Intf Name:       mgmt2
Intf Type:       Broadcast
Description:     management2
VRF:             None
IP State:        UP (Bound
to 5/2)
IP Address:      192.168.100.3        Subnet Mask:     255.255.255.0 
Bcast Address:   192.168.100.255      MTU:             1500 
Resoln Type:     ARP                  ARP
timeout:     60 secs
L3 monitor LC-port
switchover: Disabled 
Number of Secondary
Addresses: 0 
Verify that the port configuration settings are correct by entering the following command:
show configuration
port slot#/port#

slot# is the chassis slot number of the line card where the physical port resides. slot# is either 5 or 6. port# is the number of the port (either 1 or 2).

This following command produces an output similar to the one shown below. It displays the configuration of port 2 of the MIO/UMIO installed in chassis slot 5. In this example, the port is bound to an interface called mgmt2.
config
  port ethernet 5/2
    description management2
    no shutdown
    bind interface
mgmt2 local
end

Save your configuration as described in the Verifying and Saving Your Configuration chapter.

Configuring System Timing

The system is equipped with a clock that supplies the timestamp for statistical counters, accounting records, logging, and event notification. After the initial configuration of the system clock, you can configure the system to communicate with one or more Network Time Protocol (NTP) server(s) to ensure that the clock is always accurate.

In the event of a power outage, the clock is maintained with an accuracy of +/- one minute per month for up to 10 years. This ensures that when power is restored, the system is ready to process sessions and generate accounting, log, and event data with accurate timestamps.

In addition to configuring the timing source, you must configure the system’s time zone.

Setting the System Clock and Time Zone

Use the following command example to configure the system clock and time zone:

clock set date:time
configure
   clock timezone timezone [ local ]
   end
Notes:
  • Enter the date and time in the format YYYY:MM:DD:HH:mm or YYYY:MM:DD:HH:mm:ss.
  • Refer to the online Help for the clock timezone command for a complete list of supported time zones.
  • The optional local keyword indicates that the time zone specified is the local timezone.
  • Daylight Savings Time is automatically adjusted for time zones supporting it.

Save your configuration as described in the Verifying and Saving Your Configuration chapter.

Verifying and Saving Your Clock and Time Zone Configuration

Enter the following command to verify that you configured the time and time zone correctly:

show clock

The output displays the date, time, and time zone that you configured.

Configuring Network Time Protocol Support

This section provides information and instructions for configuring the system to enable the use of the Network Time Protocol (NTP).

IMPORTANT:

Configure the system clock and time zone prior to implementing NTP support. This greatly reduces the time period that must be corrected by the NTP server.

Many of the services offered by the ASR 5x00 platform require accurate timekeeping derived through NTP. If the time reference(s) used by StarOS are not accurate, the services may be unreliable. For this reason it should be assumed that normal system operation requires that NTP be configured.

The system uses NTP to synchronize internal clocks on the chassis to external time sources (typically GPS NTP sources, or other Stratum 2 or 3 servers, switches or routers).

By default, NTP is not enabled externally and should be configured when the system is initially installed. When enabled, the active MIO/UMIO will synchronize with external sources. If not enabled, the active MIO/UMIO will use its local clock as a time source. In the event of an NTP server or network outage, an already running MIO/UMIO will continue to use NTP to maintain time accuracy, but in a holdover mode.

All cards with CPUs synchronize to the active MIO/UMIO internally. This occurs even if an external NTP server is not configured. In the event of a MIO/UMIO switchover, all other cards will start synchronizing with the newly active MIO/UMIO automatically.

The system should have:
  • NTP enabled.
  • NTP configured for use in the local context only. Use of other contexts (which can be specified in the enable configurable) will cause issues.
  • NTP configured for at least three external NTP servers. With three or more servers, outlyers and broken or misconfigured servers can be detected and excluded. Generally, the more servers the better (within reason).

IMPORTANT:

Do not configure any external NTP servers using the prefer keyword. The NTP clock selection algorithms already have the built-in ability to pick the best server. Use of prefer usually results in a poorer choice than NTP can determine for itself.

IMPORTANT:

Do not change the maxpoll, minpoll, or version keyword settings unless instructed to do so by Cisco TAC.

Use the following example to configure the necessary NTP association parameters:
configure
   ntp
      enable
      server ip_address1
      server ip_address2
      server ip_address3
      end
Notes:
  • By default context_name is set to local. This is the recommended configuration.
  • A number of options exist for the server command. Refer to theNTP Configuration Mode Commands chapter in the Command Line Interface Reference for more information.
  • Enter the IP address of NTP servers using IPv4 dotted-decimal or IPv6 colon-separated-hexadecimal notation.

IMPORTANT:

Configure the system with at least three (preferably four) NTP servers.

Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Configuring NTP Servers with Local Sources

NTP can use network peers, local external clocks (such as GPS devices), or a local clock with no external source.

A local clock with no external source is usually a last-resort clock when no better clock is available. It is typically configured on a site's intermediate NTP server so that when a WAN network outage occurs, hosts within the site can continue to synchronize amongst themselves.

You can configure this in ntpd or on many commercially available NTP devices. This local clock should always have a high stratum number (8+) so that under normal conditions (when real sources are available) this local clock will not be used.

Using a Load Balancer

The NTP daemon and protocol assume that each configured server is running NTP. If a NTP client is configured to synchronize to a load balancer that relays and distributes packets to a set of real NTP servers, the load balancer may distribute those packets dynamically and confuse the NTP client. NTP packets are latency and jitter sensitive. Relaying them through a load balancer can confuse the NTP client and is not a supported practice.

Verifying the NTP Configuration

Verify the NTP configuration is correct. Enter the following command at the Exec mode prompt:
show ntp associations

The output displays information about all NTP servers. See the output below for an example deploying two NTP servers.

+----Peer
Selection: ( ) - Rejected / No
Response 
|                    (x) - False
Tick
|                    (.) - Excess
|                    (-) - Outlyer
|                    (+) - Candidate
|                    (#) - Selected
|                    (*) - System
Peer
|                    (o) - PPS
Peer
v
remote           local      st
poll reach  delay   offset    disp
=======================================================================
*10.0.4.5        0.0.0.0          3   64    1
0.00060  0.000019 0.00029
*10.0.4.5        0.0.0.0          3   64    1
0.00060  0.000019 0.00029

The following table describes the parameters output by the show ntp associations command.

Column Title Description

remote

List of the current NTP servers. One of these characters precedes each IP address to show the server’s current condition:
  • ( ) Rejected/No response
  • X False tick
  • . Excess
  • - Outlyer
  • + Candidate
  • # Selected
  • * System peer
  • (o) PPS peer

refid

Last reported NTP reference to which the server is synchronizing.

st

NTP server stratum level.

t

Communication type: broadcast, multicast, etc.

when

Number of seconds since the last contact.

poll

Polling interval between the system and the NTP server.

reach

Octal value of the reachability shift register indicating which responses were received for the previous eight polls to this NTP server.

delay

Round-trip delay (in milliseconds) for messages exchanged between the system and the NTP server.

offset

Number of milliseconds by which the system clock must be adjusted to synchronize it with the NTP server.

jitter

Jitter in milliseconds between the system and the NTP server.



Enabling CLI Timestamping

To display a timestamp (date and time) for every command that is executed on the CLI, enter the following command at the root prompt for the Exec mode:

timestamps

The date and time appear immediately after you execute the command.

Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Configuring System Administrative Users

Getting Started describes how to configure a context-level security administrator for the system.

This section provides instructions for configuring additional administrative users having the following privileges:
  • Security Administrators: have read-write privileges and can execute all CLI commands, including those available to Administrators, Operators, and Inspectors
  • Administrators: have read-write privileges and can execute any command in the CLI except for a few security-related commands that can only be configured by Security Administrators. Administrators can configure or modify system settings and execute all system commands, including those available to the Operators and Inspectors.
  • Operators: have read-only privileges to a larger subset of the Exec Mode commands. They can execute all commands that are part of the inspector mode, plus some system monitoring, statistic, and fault management functions. Operators do not have the ability to enter the Config Mode.
  • Inspectors: are limited to a few read-only Exec Mode commands. The bulk of these are show commands for viewing a variety of statistics and conditions. An Inspector cannot execute show configuration commands and does not have the privilege to enter the Config Mode.

Configuration instructions are categorized according to the type of administrative user: context-level or local-user.

IMPORTANT:

For information on the differences between these user privileges and types, refer to Getting Started.

Configuring Context-level Administrative Users

This section contains information and instructions for configuring context-level administrative user types.

Configuring Context-level Security Administrators

Use the example below to configure additional security administrators:
configure
   context local
      administrator user_name { [ encrypted ]  password password }
      end
Notes:
  • Additional keyword options are available that identify active administrators or place time thresholds on the administrator. Refer to the Command Line Interface Reference for more information about the administrator command.

Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Configuring Context-level Administrators

Use the example below to configure context-level configuraiton administrators:

configure
   context local
      config-administrator user_name { [ encrypted ]  password password }
      end
Notes:
  • Additional keyword options are available that identify active administrators or place time thresholds on the administrator. Refer to the Command Line Interface Reference for more information about the config-administrator command.

Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Configuring Context-level Operators

Use the example below to configure context-level operators:

configure
   context local
      operator user_name { [ encrypted ]  password password }
      end
Notes:
  • Additional keyword options are available that identify active administrators or place time thresholds on the administrator. Refer to the Command Line Interface Reference for more information about the operator command.

Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Configuring Context-level Inspectors

Use the example below to configure context-level inspectors:

configure
   context local
      inspector user_name { [ encrypted ]  password password }
      end
Notes:
  • Additional keyword options are available that identify active administrators or place time thresholds on the administrator. Refer to the Command Line Interface Reference for more information about the inspector command.

Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Verifying Context-level Administrative User Configuration

Verify that the configuration was successful by entering the following command:

show configuration context
local
This command displays all of the configuration parameters you modified within the Local context during this session. The following displays sample output for this command. In this example, a security administrator named testadmin was configured.
config
  context local
    interface mgmt1
      ip address 192.168.1.10 255.255.255.0
    #exit
    subscriber default
    #exit
    administrator testadmin
encrypted password fd01268373c5da85
    inspector testinspector
encrypted password 148661a0bb12cd59
exit
  port ethernet 5/1
    bind interface
mgmt1 local
  #exit

Configuring Local-User Administrative Users

Use the example below to configure local-user administrative users:

configure
   local-user
username name
   end
Notes:
  • Additional keyword options are available identify active administrators or place time thresholds on the administrator. Refer to the Command Line Interface Reference for more information about the local-user username command.

Save the configuration as described in theVerifying and Saving Your Configuration chapter.

Verifying Local-User Configuration

Verify that the configuration was successful by entering the following command:

show local-user verbose
This command displays information on configured local-user administrative users. A sample output for this command appears below. In this example, a local-user named SAUser was configured.
Username:                SAUser
  Auth Level:            secadmin
  Last Login:            Never
  Login Failures:        0
  Password Expired:      Yes
  Locked:                No
  Suspended:             No
  Lockout on Pw Aging:   Yes
  Lockout on Login
Fail: Yes 

Updating Local User Database

Update the local user (administrative) configuration by running the following Exec mode command. This command should be run immediately after creating, removing or editing administrative users.
update local-user database

Configuring TACACS+ for System Administrative Users

This section describes TACACS+ (Terminal Access Controller Access Control System+) AAA (Authentication Authorization and Accounting) service functionality and configuration on the ASR 5x00.

Operation

TACACS+ is a secure, encrypted protocol. By remotely accessing TACACS+ servers that are provisioned with the administrative user account database, the ASR 5x00 can provide TACACS+ AAA services for system administrative users. TACACS+ is an enhanced version of the TACACS protocol that uses TCP instead of UDP.

The ASR 5x00 system serves as the TACACS+ Network Access Server (NAS). As the NAS the system requests TACACS+ AAA services on behalf of authorized system administrative users. For the authentication to succeed, the TACACS+ server must be in the same local context and network accessed by the system.

The system supports TACACS+ multiple-connection mode. In multiple-connection mode, a separate and private TCP connection to the TACACS+ server is opened and maintained for each session. When the TACACS+ session ends, the connection to the server is terminated.

TACACS+ is a system-wide function on the ASR 5x00. TACACS+ AAA service configuration is performed in TACACS Configuration Mode. Enabling the TACACS+ function is performed in the Global Configuration Mode. The system supports the configuration of up to three TACACS+ servers.

Once configured and enabled on the system, TACACS+ authentication is attempted first. By default, if TACACS+ authentication fails, the system then attempts to authenticate the user using non-TACACS+ AAA services, such as RADIUS.

IMPORTANT:

For releases after 15.0 MR4, TACACS+ accounting (CLI event logging) will not be generated for Lawful Intercept users with privilege level set to 15 and 13.

User Account Requirements

Before configuring TACACS+ AAA services on the ASR 5x00, note the following TACACS+ server and system user account provisioning requirements.

TACACS+ User Account Requirements

The TACACS+ server must be provisioned with the following TACACS+ user account information:

  • A list of known administrative users.
  • The plain-text or encrypted password for each user.
  • The name of the group to which each user belongs.
  • A list of user groups.
  • TACACS+ privilege levels and commands that are allowed/denied for each group.

IMPORTANT:

TACACS+ privilege levels are stored as Attribute Value Pairs (AVPs) in the network’s TACACS+ server database. Users are restricted to the set of commands associated with their privilege level. A mapping of TACACS+ privilege levels to ASR 5x00 CLI administrative roles and responsibilities is provided in the table below.


Table 1. Default Mapping of TACACS+ Privilege Levels to CLI Administrative Roles
TACACS+ Privilege Level CLI Administrative Access Privileges
CLI FTP ECSEMS Lawful Intercept CLI Role

0

Yes

No

No

No

Inspector

1

Yes

No

Yes

No

Inspector

2

No

Yes

No

No

Inspector

3

Yes

Yes

No

No

Inspector

4

Yes

Yes

Yes

No

Inspector

5

Yes

No

No

No

Operator

6

Yes

No

Yes

No

Operator

7

No

Yes

No

No

Operator

8

Yes

Yes

No

No

Operator

9

Yes

Yes

Yes

No

Operator

10

Yes

No

No

No

Administrator

11

Yes

No

Yes

No

Administrator

12

No

Yes

No

No

Administrator

13

Yes

Yes

No

Yes

Administrator

14

Yes

Yes

Yes

No

Administrator

15

Yes

Yes

Yes

Yes

Administrator



User Account Requirements

TACACS+ users who are allowed administrative access to the system must have the following user account information defined on the ASR 5x00:

  • username
  • password
  • administrative role and privileges

IMPORTANT:

For instructions on defining users and administrative privileges on the system, refer to Configuring System Administrative Users.

Configuring TACACS+ AAA Services

This section provides an example of how to configure TACACS+ AAA services for administrative users on the system.

CAUTION:

When configuring TACACS+ AAA services for the first time, the administrative user must use non-TACACS+ services to log into the ASR 5x00. Failure to do so will result in the TACACS+ user being denied access to the system.

Log in to the system using non-TACACS+ services.

Use the example below to configure TACACS+ AAA services on the system:
configure
   tacacs mode
      server priority priority_number ip-address tacacs+srvr_ip_address
      end
Note:
  • server priority priority_number: Must be an integer from 1 to 3 (releases prior to 18.2) or 1 through 4 (releases 18.2+), that specifies the order in which this TACACS+ server will be tried for TACACS+ authentication. 1 is the highest priority, and 3 or 4 is the lowest. The priority number corresponds to a configured TACACS+ server.
  • ip-address: Must be the IPv4 address of a valid TACACS+ server that will be used for authenticating administrative users accessing this system via TACACS+ AAA services.
  • By default, the TACACS+ configuration will provide authentication, authorization, and accounting services.
Enable TACACS+ on the ASR 5x00:
configure
   aaa tacacs+
   end

Save the configuration as described in the Verifying and Saving Your Configuration chapter.

IMPORTANT:

For complete information on all TACACS+ Configuration Mode commands and options, refer to the TACACS Configuration Mode Commands chapter in the Command Line Reference.

Verifying the TACACS+ Configuration

This section describes how to verify the TACACS+ configuration.

Log out of the system CLI, then log back in using TACACS+ services.

IMPORTANT:

Once TACACS+ AAA services are configured and enabled on the ASR 5x00, the system first will try to authenticate the administrative user via TACACS+ AAA services. By default, if TACACS+ authentication fails, the system then continues with authentication using non-TACACS+ AAA services.

At the Exec Mode prompt, enter the following command:
show tacacs 

The output of the show tacacs commands provides summary information for each active TACACS+ session such as username, login time, login status, current session state and privilege level.

An example of this command’s output is provided below. In this example, a system administrative user named asradmin has successfully logged in to the system via TACACS+ AAA services.
active session #1:
   login username                : asradmin 
   login tty                     : /dev/pts/1 
   time of login                : Fri
Oct 22 13:19:11 2011 
   login server priority        : 1
   current login status         : pass
   current session state        : user
login complete 
   current privilege
level      : 15
   remote client application    : ssh
   remote client ip
address     : 111.11.11.11 
   last server reply
status     : -1
total TACACS+ sessions          : 1 

IMPORTANT:

For details on all TACACS+ maintenance commands, refer to the Command Line Interface Reference.

Configuring a Chassis Key

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.

IMPORTANT:

The Quick Setup Wizard also prompts the user to enter a chassis key value.

The Exec mode chassis key value key_string command identifies the chassis which can encrypt and decrypt encrypted passwords in the configuration file. If two or more chassis are configured with the same chassis key value, the encrypted passwords can be decrypted by any of the chassis sharing the same chassis key value. As a corollary to this, a given chassis key value will not be able to decrypt passwords that were encrypted with a different chassis key value.

The key_string is an alphanumeric string of 1 through 16 characters. The chassis key is stored as a one-way encrypted value, much like a password. For this reason, the chassis key value is never displayed in plain-text form.

The Exec mode chassis keycheck key_string command generates a one-way encrypted key value based on the entered key_string. The generated encrypted key value is compared against the encrypted key value of the previously entered chassis key value. If the encrypted values match, the command succeeds and keycheck passes. If the comparison fails, a message is displayed indicating that the key check has failed. If the default chassis key (no chassis key) is currently being used, this key check will always fail since there will be no chassis key value to compare against.

Use the chassis keycheck command to verify whether multiple chassis share the same chassis key value.

IMPORTANT:

Only a user with Security Administrator or Administrator privilege can execute the chassis key value and chassis keycheck commands.

For additional information, refer to the Exec Mode Commands chapter in the Command Line Interface Reference.

Beginning with Release 15.0, the chassis ID will be generated from an input chassis key using the SHA2-256 algorithm followed by base36 encoding. The resulting 44-character chassis ID will be stored in the same chassisid file in flash.

Release 14 and Release 15 chassis IDs will be in different formats. Release 15 will recognize a Release 14 chassis ID and consider it as valid. Upgrading from 14.x to 15.0 will not require changing the chassis ID or configuration file.

However, if the chassis key is reset in Release 15 through the setup wizard or chassis-key CLI command, a new chassis ID will be generated in Release 15 format (44 instead of 16 characters). Release14 builds will not recognize the 44-character chassis ID. If the chassis is subsequently downgraded to Release 14, a new 16-character chassis ID will be generated. To accommodate the old key format, you must save the configuration file in pre-v12.2 format before the downgrade. If you attempt to load a v15 configuration file on the downgraded chassis, StarOS will not be able to decrypt the password/secrets stored in the configuration file.

Configuring MIO/UMIO Port Redundancy

Port redundancy for MIOs provides an added level of redundancy that minimizes the impact of network failures that occur external to the system. Examples include switch or router port failures, disconnected or cut cables, or other external faults that cause a link down error.

CAUTION:

To ensure that system card and port-level redundancy mechanisms function properly, disable the Spanning Tree protocol on devices connected directly to any system port. Failure to turn off the Spanning Tree protocol may result in failures in the redundancy mechanisms or service outage.

By default, the system provides port-level redundancy when a failure occurs, or you issue the port switch to command. In this mode, the ports on active and standby MIO/UMIO cards have the same MAC address, but since only one of these ports may be active at any one time there are no conflicts. This eliminates the need to transfer MAC addresses and send gratuitous ARPs in port failover situations. Instead, for Ethernet ports, three Ethernet broadcast packets containing the source MAC address are sent so that the external network equipment (switch, bridge, or other device) can re-learn the information after the topology change. However, if card removal is detected, the system sends out gratuitous ARPs to the network because of the MAC address change that occurred on the specific port.

With port redundancy, if a failover occurs, only the specific port(s) become active. For example; if port 5/1 fails, then port 6/1 becomes active, while all other active ports on the line card in slot 5 remain in the same active state. In port failover situations, use the show port table command to check that ports are active on both cards and that both cards are active.

Take care when administratively disabling a port that is one of a redundant pair. A redundant pair comprises both the active and standby ports—for example 5/1 and 6/1. If 5/1 is active, administratively disabling 5/1 through the CLI does not make 6/1 active. It disables both 5/1 and 6/1 because an action on one port has the same effect on both. Refer to Creating and Configuring Ethernet Interfaces and Ports in System Interface and Port Configuration Procedures.

With automatic card-level redundancy, there is no port-level redundancy in an MIO/UMIO failover. The standby MIO/UMIO becomes active and all ports on that card become active. The system automatically copies all the MAC addresses and configuration parameters used by the failed MIO/UMIO to its redundant counterpart. The ports on MIOs keep their original MAC addresses, and the system automatically copies the failed MIO/UMIO’s configuration parameters to its redundant counterpart.

Port redundancy can be configured to be revertive or non-revertive. With revertive redundancy service is returned to the original port when service is restored.

This feature requires specific network topologies to work properly. The network must have redundant switching components or other devices that the system is connected to. The following diagrams show examples of a redundant switching topologies and how the system reacts to various external network device scenarios.


Figure 1. Network Topology Example Using MIO/UMIO Port Redundancy

Figure 2. Port Redundancy Failover in Cable Defect Scenario

In the example above, an Ethernet cable is cut or unplugged, causing the link to go down. When this event occurs, the system, with port-mode redundancy enabled, recognizes the link down state and makes port 6/1 the active port. The switching device, using some port redundancy scheme, recognizes the failure and enables the port on the secondary switch to which the MIO/UMIO in slot 6 is connected, allowing it to redirect and transport data.


Figure 3. Port Redundancy Failover in External Network Device Failure Scenario

In the example above, a switch failure causes a link down state on all ports connected to that switch. This failure causes all redundant ports on the line card in slot 6 to move into the active state and utilize the redundant switch.

Configuring MIO/UMIO Port Redundancy Auto-Recovery

You can configure a port auto-recovery feature. When a port failure occurs and the preferred port is returned to service (link is up), control is automatically returned to that port. By default, ports are in a non-revertive state, meaning that no ports are preferred; a manual port switch is required to return use to the original port.

IMPORTANT:

This feature is applied on a per port basis (via the preferred slot keyword), allowing you to configure specific ports to be used on individual MIOs. For example, you could configure ports 10 through 19 as preferred on the MIO/UMIO in slot 5, and configure ports 20 through 29 as the preferred ports on the MIO/UMIO in slot 6.

Use the following example to configure a preferred port for revertive, automatic return to service when a problem has cleared:
configure
   port ethernet slot#/port#
      preferred slot slot#
      end
Notes
  • If you do specify a preference, redundancy is revertive to the specified card. If you do not specify a preference, redundancy is non-revertive.
  • Repeat for each additional port that you want to make preferred.

Save the configuration as described in theVerifying and Saving Your Configuration chapter.

Verifying Port Redundancy Auto-Recovery

Verify port information by entering the following command

show port info slot#/port#

slot# is the chassis slot number of the MIO/UMIO card on which the physical port resides.

port# is the physical port on the MIO/UMIO.

The following shows a sample output of this command for port 1 on the MIO/UMIO in slot 5:
[local]host_name# show
port info 5/1
Port: 5/1
  Port Type               : 1000 Ethernet
  Role                    : Management Port
  Description             : (None
Set)
  Redundancy Mode         : Port
Mode
  Redundant With          : 6/1
  Preferred Port          : Non-Revertive
  Physical ifIndex        : 83951616
  Administrative State    : Enabled
  Configured Duplex       : Auto
  Configured Speed        : Auto
  Configured Flow Control : Enabled
  Interface MAC Address   : 
02-05-47-B8-2F-41
  Fixed MAC Address       : 
02-05-47-B8-2F-41
  Link State              : Up
  Link Duplex             : Full
  Link Speed              : 1000
Mb
  Flow Control            : Disabled
  Link Aggregation
Group  : None
  Logical ifIndex         : 83951617
  Operational State       : Up, Active

Configuring Data Processing Card (DPC) Availability

As discussed in the Understanding the System Boot Process section of Understanding System Operation and Configuration, when the system initially boots up, all installed DPCs and or UDPCs are placed into standby mode. You must activate some of these cards in order to configure and use them for session processing. One DPC/UDPC may remain in standby mode for redundancy.

This section describes how to activate DPCs and specify their redundancy.

IMPORTANT:

Refer to the ASR 5500 Installation Guide for information about system hardware configurations and redundancy.

Enter the following command to check the operational status of all DPCs:
show card table

This command lists the DPCs installed in the system by their slot number, their operational status, and whether or not the card is a single point of failure (SPOF).

Use the following example to configure DPC/UDPC availability:
configure
  card slot#
    mode { active | standby } 
  end
Notes:
  • When activating cards, remember to keep at least one DPC/UDPC in standby mode for redundancy.
  • Repeat for every other DPC/UDPC in the chassis that you wish to activate.

Save the configuration as described in the Verifying and Saving Your Configuration chapter.

Verifying Card Configurations

Verify that the configuration was successful. Enter the following command:

show card table

Any DPC/UDPC that you made active should now have an operational status of Active.

Configuring ASR 5500 Link Aggregation

A Link Aggregation Group (LAG) works by exchanging control packets via Link Aggregation Control Protocol (LACP) over configured physical ports with peers to reach agreement on an aggregation of links as defined in IEEE 802.3ad. The LAG sends and receives the control packets directly on physical ports.

Link aggregation (also called trunking or bonding) provides higher total bandwidth, auto-negotiation, and recovery by combining parallel network links between devices as a single link. A large file is guaranteed to be sent over one of the links, which removes the need to address out-of-order packets.

LAG and Master Port

Logical port configurations (VLAN and binding) are defined in the master port of the LAG. If the master port is removed because of a card removal/failure, another member port becomes the master port (resulting in VPN binding change and outage), unless there is a redundant master port available.

IMPORTANT:

The master port on which VLAN can be created for VPN binding must always be configured on the active/master MIO/UMIO. The redundancy between MIO/UMIO 5 and MIO/UMIO 6 automatically causes both ports to be the master with the same VLANs configured and active.

LAG and Port Redundancy

ASR 5500 LAG implementation assumes that:
  • LAG ports on MIO/UMIO 5 and MIO/UMIO 6 are connected to two Ethernet switches.
  • LAG ports on MIO/UMIO 5 and MIO/UMIO 6 are both active at the same time.
  • Ports on MIO/UMIO 5 and MIO/UMIO 6 are redundant with each other.

All ports in a LAG can be auto-switched to another MIO/UMIO when certain active port counts or bandwidth thresholds are crossed.

LAG and Multiple Switches

This feature connects subscriber traffic ports on MIOs to ports on Ethernet switches. A port failure/switch forces all ports in a LAG to switch to the other MIO/UMIO when a specified threshold is crossed. This works in a way similar to the auto-switch feature for port redundancy. LACP runs between the ASR 5500 and the Ethernet switch, exchanging relevant pieces on information, such as health status.

The following table summarizes typical LAG functionality on an MIO/UMIO card.


Table 2. MIO/UMIO LAG Functionality
ASR 5500 LAGID Ethernet Switch A Ethernet Switch B
MIO/UMIO Port 11 1 Port 1 ----
MIO/UMIO Port 12 1 Port 2 ----
MIO/UMIO Port 13 1 ---- Port 1


Multiple Switches with L2 Redundancy

To handle the implementation of LACP without requiring standby ports to pass LACP packets, two separate instances of LACP are started on redundant cards. The two LACP instances and port link state are monitored to determine whether to initiate an auto-switch (including automatic L2 port switch).

The figure below shows an LAG established across two MIO/UMIO daughter card ports with L2 redundancy.


Figure 4. LAG with L2 Redundancy, Two Ethernet Switches

An LACP implementation with L2 redundancy cannot pass traffic even though standby ports have link up. For example, with two MIO/UMIO cards connected to two different Ethernet switches and all ports in the same LAG, failure of ports would not trigger a LAG switch until the active port number ratio flipped (more ports down than up).

Port States for Auto-Switch

Ports are classified in one of four states to determine whether to start auto-switching. See the table below.

For counters, State(x) represents the number of ports on a card in that state.


Table 3. Auto-Switch Port States
State Counter Description
Link L(x) Physical link up
Standby S(x) Link up but in standby mode
Waiting W(x) Waiting for Link Aggregation Control Protocol negotiation
Aggregated A(x) Aggregation formed


Hold Time

Once the LAG manager switches to another LACP instance, it does not consider another change for a short period to let link and LACP negotiation settle down. This “hold time” is configurable.

The LAG manager also enters/extends the hold period when an administrator manually switches ports to trigger a card switch.

Preferred Slot

You can define which card is preferred per LAG group as a preferred slot. When a preferred MIO/UMIO slot is specified, it is selected for the initial timeout period to make the selection of a switch less random.

Port preference is not allowed in this mode.

Auto-Switch Criteria

The following criteria determine the switching of card x to card y to provide better bandwidth while allowing manual intervention. The evaluation of the criteria occurs outside of the hold period.

Ports are automatically switched from card x to card y when A(y) ? = 1, at least one port is in aggregated state on card y, and one of the following conditions is true (in order of precedence):

  • L(x) L(y) Less ports with link Up on card x than card y
  • S(x) S(y) More ports in Standby state on card x than card y
  • W(x) W(y) More ports in Waiting state on card x than card y
  • A(x) A(y) Fewer ports in Aggregated state on card x than card y
  • Card y is preferred
  • Card y is selected.

Link Aggregation Control

One port in an aggregation group is configured as a master so that all traffic (except control traffic) in the aggregation group logically passes through this port. It is recommended that you configure link-aggregation on the master port first when enabling LAG, and unconfigure the master port last when disabling LAG.

The following command creates link aggregation group N with port slot#/port# as master. Only one master port is allowed for a group. N must be in the range of [1...255].
configure
   port ethernet slot#/port#
      link-aggregation
master group N
      exit

IMPORTANT:

Link Aggregation Control Protocol (LACP) starts running only when the master port is enabled.

Use the following command to add a port as member of link aggregation group number N only if the master port is assigned. Otherwise, it is added to the group when the master port is assigned:
   port ethernet slot#/port#
      link-aggregation
member group N
      exit

IMPORTANT:

The VPN can only bind the master port, and a VLAN can only be created on the master port. A failure message is generated if you attempt to bind to a link aggregation member port.

Each system that participates in link aggregation has a unique system ID that consists of a two-byte priority (where the lowest number [0] has the highest priority) and a six-byte MAC address derived from the first port’s MAC address. The following command sets the system priority used to form the system ID. P is a hex in the range [0x0000..0xFFFF]. The default is 0x8000.
   card slot#
      link-aggregation
system-priority P

Ports in a system are assigned keys. The group number maps directly to the key, whereupon only ports with the same key can be aggregated. Ports on each side of the link use a different aggregation key.

The system ID, port key and port ID of two peers form the Link Aggregation Group Identifier (LAGID). You can aggregate links having the same LAGID. Systems are often configured initially with each port in its own aggregation (requiring a separate key per port), or with all ports in the same aggregation (a single key for all ports). Negotiation via LACP would qualify the actual aggregation.

Systems exchange information about system ID, port key and port ID with peers across the physical links using LACP.

LACP packets are defined with the Slow Protocol format. Each system sends out its own (“actor”) information and its last received information about its peer (“partner”) over the physical link.

Use the following commands to set the LACP parameters. LACP can run in active mode to send LACP packets periodically, or in passive mode, in which it only responds to LACP packets it receives.

LACP can send packets at either a auto (30s) or fast (1s) rate. The defaults for this release are Active and Auto; see the sample configuration below:
config
   port ethernet slot#/port#
      link-aggregation
lacp { active | passive } [ rate { auto | fast } | timeout { long | short } ]

Peers send out LACP packets when the state changes or if a difference is found from a received LACP packet about its own state.

Corresponding ports on an MIO/UMIO redundant pair cannot be active at the same time. Redundant ports share the same MAC address, so after a failover is resolved, the original port rejoins the link aggregation group.

Redundancy Options

For L2 redundancy set the following option on the master port for use with the whole group:

link-aggregation
redundancy standard [hold-time sec ] [preferred slot { card_number | none } 

Standard redundancy treats all cards in the group as one group.

Horizontal Link Aggregation with Two Ethernet Switches

When a LAG contains two sets of ports each connecting to a different switch, the operator has the ability to specify the slot/port (connected to the destination switch) when switching ports.

The Exec mode link-aggregation port switch to slot/port command configures this option. The slot/port is any valid port connected to the destination switch. The following criteria apply to the setting of this option:

  • slot/port must support LAG.
  • slot/port must be configured with LAG.
  • slot/port must not be already actively distributing
  • slot/port must have negotiated a link aggregation partner in standard mode.
  • slot/port's partner must have an equal or higher in standard mode.
  • slot/port's partner bundle must have equal or higher bandwidth in standard mode.
  • Switching to slot/port must not violate preference within hold-time in standard mode.

Link Aggregation Status

To check the status of link aggregation, use the following commands:

  • show port table
  • show port info slot/port

A single character is used to display LAG physical port status in the output of the show port table command. See the table below.


Table 4. LAG Port Status
Display Description
LA+ Port is actively used for distributing.
LA- Port failed to negotiate LACP.
LA~ (tilde) Port negotiated LACP but another peer was selected.
LA* Port is (re)negotiating LACP.


Configuring a Demux Card

You can dedicate a DPC/UDPC or MIO/UMIO to function as a demux card. Demux is a generic term for signal demultiplexing tasks. These are the tasks are responsible for parsing call setup (signaling packets) and distributing the calls internally. For this reason there almost as many tasks running on a demux card as there are services.

The vpnmgr tasks responsible for each context also run on the demux card. The number of vpnmgr tasks correspond to the number of contexts. A vpnmgr is responsible for IP address assignment to mobile equipment, IP routing (such as BGP, OSPF), as well as a variety of associated tasks.

Overview

Designating a DPC/UDPC or MIO/UMIO as a demux card frees up resources for session handling, which has the potential to increase system throughput. However, there is no increased support in total subscriber capacity due to other system resource restrictions.

This feature is disabled by default and can be enabled via the Global Configuration mode require demux command. It is only supported for a limited number of products. Refer to the product Administration Guide for additional information.

To support this feature session recovery must also be enabled via the Global Configuration mode require session recovery command.

IMPORTANT:

After enabling demux card and session recovery, you must save the configuration and reboot the ASR 5500 to enable this feature.

CAUTION:

Enabling the Demux on MIO/UMIO feature changes resource allocations within the system. This directly impacts an upgrade or downgrade between StarOS versions in ICSR configurations. Contact Cisco TAC for procedural assistance prior to upgrading or downgrading your ICSR deployment.

MIO/UMIO Demux Restrictions

The following restrictions apply when enabling an MIO/UMIO as a demux card:
  • The require demux management-card command must be configured before any service or contexts have been created on the system. The command will not execute after a mode of operation has been selected for the chassis.
  • Only the following services currently support the designation of an MIO/UMIO card for demux functions: GGSN, SGW, PGW, HA, SAE-GW and L2TP LNS. These services are supported only when they are deployed as consumer gateways.
  • SGSN, MME, HNBGW, HeNBGW, SaMOG, PDG, PDIF, ePDG, IPSG, PDSN, HSGW, L2TP LAC, NEMO, CSCF, FA, and WSG are not supported. Enterprise or corporate gateways (GGSN, HA, PGW, etc.) are also not supported.
  • You should not enable demux functionality on MIO for configurations that require a large number of tunnels.
  • After the ASR 5500 has booted with demux functions running on an MIO/UMIO, you cannot configure non-supported services. A maximum of eight Demux Managers are supported. Any attempt to add more than eight Demux Managers will be blocked.
  • Service/products requiring a large number of VPN Managers, VRFs and/or Demux Managers must not enable demux functions on an MIO.
  • With demux functions running on an MIO, the ASR 5500 supports a maximum of 10 contexts, 64 interfaces per context, and 250 VRFs per system.
  • ICSR upgrades require compatible configurations and Methods of Procedure (MOPs).

Implementation of this feature assumes that CEPS (Call Events Per Second) and the number of subscribers will remain constant, and only the data rate will increase. This ensures that the CPU demand will not increase on the MIO/UMIO.

IMPORTANT:

Contact Cisco TAC for additional assistance when assessing the impact to system configurations when enabling the Demux on MIO/UMIO feature.

Configuration

For releases prior to 15.0, to configure a DPC/UDPC as a demux card enter the following CLI commands:
configue
  require demux card
  end
For release 15.0+, to configure a DPC/UDPC as a demux card enter the following CLI commands:
configue
  require demux processing-card
  end
To configure an MIO/UMIO as a demux card enter the following CLI commands:
configue
  require demux management-card
  end