StarOS Management Operations

This chapter provides information about software management operations on the VPC. Software management sections include:

Understanding the Local File System

The local VPC file system is made up of files that are stored on the following:
  • /flash – Flash memory allocated as vHDD-1 via the hypervisor is the default storage media for the StarOS image, CLI configuration, and crash log files used by the system.
  • /hd-raid – This is the storage space allocated as vHDD-2 by the hypervisor. It is used to store CDRs (Charging Data Records) and UDRs (Usage Data Records).

File Types Used by the Local File System

The following file types can be located in the local file system:
  • Operating System Software Image File: This binary file type is identified by its .bin extension. This file is StarOS and is loaded upon startup or reloading. This is an executable, read-only file that cannot be modified by end users.
  • CLI Configuration File: This file type is identified by its .cfg extension. These are text files that contain CLI commands that work in conjunction with the StarOS image. They determine services to be provided, hardware and software configurations, and other functions performed by the system. The files are typically created by the end user. You can modify the files both on and off-line and use descriptive long filenames.
  • System File: Only one file identified by a .sys extension is used by StarOS. The boot.sys file contains system-specific information, which describes how the system locates, and in what priority it loads, file groups (paired .bin and .cfg files) from its boot stack.
  • Abridged Crash Log: The abridged crash log, identified by its crashlog filename, contains summary information about software or hardware failures that occur on the system. This file is located in the /flash/crsh2/ directory on the device. You can view the contents of this file through the CLI, but you cannot modify the file.

Understanding the boot.sys File

StarOS uses the boot.sys file to store the prioritized boot stack parameters and file groups the system uses during startup. Modify this file only through StarOS CLI commands and not through external means. Boot parameters contain information StarOS needs to locate the StarOS image file, including:
  • bootmode: This setting is typically configured to normal, and identifies how StarOS starts.
  • boot stack information: The boot stack is made up of prioritized file group entries that designate the StarOS image file and the CLI configuration file to load.

When VPC is started for the first time, the boot.sys file is configured to use the normal boot mode and load the StarOS image from the /flash directory.

There is no CLI configuration file contained on the local file system. This causes StarOS to automatically start its CLI-based Quick Setup Wizard upon the first successful boot. Refer to the Getting Started chapter for more information on using the Quick Setup Wizard.

Maintaining the Local File System

Use StarOS CLI commands to manage and maintain the devices that make up the local file system. Execute all the commands described in this section in the Exec Mode. Unless otherwise specified, you must have security administrator or administrator privileges to execute these commands.

File System Management Commands

Use the commands in this section to manage and organize the local file system.

IMPORTANT:

For complete information on the following commands, see the Exec Mode Commands chapter of the Command Line Interface Reference.

Creating Directories

Use the mkdir command to create a new directory on the specified local device. This directory can then be incorporated as part of the path name for any file located in the local file system.

[local]host_name# mkdir { /flash | /hd-raid } /dir_name
Use the following command to create a directory named configs:
[local]host_name# mkdir /flash/configs

Renaming Files and Directories

Use the rename command to change the name of a file from its original name to a different name. Remember to use the same file extension, if applicable, to ensure that the file type remains unchanged.

[local]host_name# rename { /flash | /hd-raid } /src_filename { /flash | /hd-raid } /dst_filename [-noconfirm]]
Use the following command to rename the file iot_test.cfg to iot_accept.cfg on the /flash local device.
[local]host_name# rename /flash/iot_test.cfg /flash/iot_accept.cfg -noconfirm

IMPORTANT:

Use the rename command only within the same local device. You cannot rename a file and place it onto another local device at the same time. To move a renamed file, you must use the copy command.

Copying Files

These instructions assume that you are at the root prompt for the Exec mode:
[local]host_name#
To save your current configuration, enter the following command:
[local]host_name# copy from_url
to_url [ passive ] [ -noconfirm ]
To copy the configuration file system.cfg from the directory cfgfiles to the directory configs_old on /flash, enter the following command:
[local]host_name# copy /flash/cfgfiles/system.cfg /flash/configs_old/system_2011.cfg
To copy the configuration file simple_ip.cfg from the directory host_name_configs to an FTP server with an IP address of 192.168.34.156, on which you have an account with a username administrator and a password secure, use the following command:
[local]host_name# copy /flash/host_name_configs/simple_ip.cfg
ftp://administrator:secure@192.168.34.156/host_name_configs/ simple_ip.cfg
To copy a configuration file called init_config.cfg to the root directory of a TFTP server with a hostname of config_server, enter the following command:
[local]host_name# copy /flash/cfgfiles/init_confg.cfg
tftp://config_server/init_config.cfg

Deleting Files

The delete command removes a designated file from its specified location on the local file system.

IMPORTANT:

This command does not support wildcard entries; each filename must be specified in its entirety.

CAUTION:

Do not delete the boot.sys file. If deleted, StarOS will not reboot on command and will be rendered inoperable.

[local]host_name# delete { /flash | /hd-raid }/filename [-noconfirm]
The following command deletes the file test.cfg from the /flash directory.
[local]host_name# delete /flash/test.cfg

Removing Directories

The rmdir command deletes a current directory on the specified local device. This directory can then be incorporated as part of the path name for any file located in the local file system.

IMPORTANT:

The directory you want to remove (delete) must be empty before executing the rmdir command. If the directory is not empty, the CLI displays a “Directory not empty” message and will not execute.

[local]host_name# rmdir url /dir_name
The following command deletes the empty directory configs in the /flash directory.
[local]host_name# rmdir /flash/configs

Formatting Local Devices

The format command performs a low-level format of a local device. This operation formats the device to use the FAT16 formatting method, which is required for proper read/write functionality with the operating system.

IMPORTANT:

Local devices that have been formatted using other methods such as NTFS or FAT32 may be used to store various StarOS, CLI configuration, and crash log files. However, when installing a new local device via the hypervisor for regular use, you should format the device prior to use. This ensures that the proper file allocation table format is used, preventing any possible discrepancies between other formats used with other operating systems.

CAUTION:

The filesystem format command removes all files and information stored on the device.

To format a local device for use by the local file system, enter the following command:

[local]host_name# filesystem format { /flash | /hd-raid }

Applying Pre-existing CLI Configuration Files

A pre-existing CLI configuration file is any .cfg file created to provide utility functions (such as clearing all statistics during testing) or created off-line using a text editor. Pre-existing configuration files stored on the local file system can be applied to a running system at any time.

CAUTION:

If a configuration file is applied to VPC currently running another StarOS CLI configuration, any like contexts, services, ports, IP address pools, or other configured items will be overwritten if the same command exists in the configuration file being applied. You must review the contents of the file being applied and understand the service ramification if a currently running command is overwritten. Also note that changes will not be saved automatically.

A CLI configuration file, or script containing CLI commands, can be applied to a running system by entering the following command at the Exec mode prompt:
[local]host_name# configure url [ verbose ]
The following command applies the pre-existing CLI configuration file clearcmds.cfg in the /flash directory.
[local]host_name# configure /flash/clearcmds.cfg

Viewing Files on the Local File System

This section describes how to view a variety of files.

Viewing the Contents of a Local Device

The contents, usage information, and file system directory structure of any local device can be viewed by entering the following command at the Exec mode prompt:

[local]host_name# directory { /flash | /usb1 | /hd-raid }

IMPORTANT:

The USB device must be pre-configured via the hypervisor for the usb1 keyword to work.

Viewing CLI Configuration and boot.sys Files

The contents of CLI configuration and boot.sys files, contained on the local file system, can be viewed off-line (without loading them into the OS) by entering the following command at the Exec mode prompt:

[local]host_name# show file url { /flash | /usb1 | /hd-raid } /filename

Where: url is the path name for the location of the file and filename is the name of the file, including any extension.

IMPORTANT:

The USB device must be pre-configured via the hypervisor for the usb1 keyword to work.

IMPORTANT:

Operator and inspector-level users can execute the show file command but cannot execute the directory command.

Validating an StarOS File

The StarOS image file, identified by its .bin extension, is a non-readable, non-editable file that executes on the system, creating its runtime operating system (OS).

It is important to verify a new StarOS image file before attempting to load it. To accomplish this, a proprietary checksum algorithm is used to create checksum values for each portion of the application stored within the .bin file during program compilation.

This information can be used to validate the actual file against the checksum values stored within the file during its compilation. If any portion of the image file has become corrupted (for example, the file was truncated or was transferred using ASCII mode instead of binary mode), then this information is reported and the file is deemed unusable.

To validate a StarOS image file, enter the following command at the Exec mode prompt:

[local]host_name# show version { /flash | /usb1 | /hd-raid } /[directory]/filename [all]
The output of this command displays the following information:
  • Version number
  • Image Description
  • Image Date
  • Boot Image
If an invalid file is found, the system displays a failure message similar to these:
Failure: Image /flash/image_version.bin
CRC check failed!
Failure: /flash/image.bin, has
a bad magic number

Configuring the Boot Stack

The boot stack consists of a prioritized listing of StarOS image-to-CLI configuration file associations. These associations determine which StarOS image and configuration file gets loaded during StarOS startup or upon a reload or reboot. Though multiple associations can be configured, StarOS uses the association with the highest priority.

In the event that there is an error processing this association (for example, one of the files cannot be located), StarOS attempts to use the association with the next highest priority. Priorities range from 1 to 100, with 1 being the highest priority. The maximum number of boot stack entries that may be configured in the boot.sys file is 10.

Boot stack information is contained in the boot.sys file, described in Understanding the bootsys File. In addition to boot stack entries, the boot.sys file contains any configuration commands required to define the system boot method as explained in the section that follows.

Local-Boot Method

The local-boot method uses the StarOS image and configuration files stored locally. Upon startup or reboot, StarOS looks on /flash or /hd-raid for the specific software image and accompanying configuration text file. When using the local-booting method, you only need to configure boot stack parameters.

Viewing the Current Boot Stack

To view the boot stack entries contained in the boot.sys file run the Exec mode show boot command.

IMPORTANT:

Operator and inspector-level users can execute the show boot command.

The example below shows the command output for a local booting configuration. Notice that in this example both the image file (operating system software) and configuration file (CLI commands) are located on the /flash device.
boot system priority
10 \
    image /flash/staros.bin \
    config /flash/system.cfg
To identify the boot image priority that was loaded at the initial boot time enter:
[local]host_name# show boot initial-config
The example below displays the output:
Initial (boot
time) configuration:
      image tftp://192.168.1.161/tftpboot/image_filename.bin \
       config /flash/system.cfg
      priority 1

Adding a New Boot Stack Entry

IMPORTANT:

Before performing this procedure, verify that there are less than 10 entries in the boot.sys file and that a higher priority entry is available (minimally there is no priority 1 entry in the boot stack). for more information, refer to Viewing the Current Boot Stack.

If priority 1 is in use, then you must renumber the existing entry(ies) to ensure that at least that priority is available. The maximum number of boot stack entries that can be contained in the boot.sys file is 10. If there are already 10 entries in the boot stack, you must delete at least one of these entries (typically, the lowest priority) and, if necessary, renumber some or all of the other entries before proceeding. for more information, see Deleting a Boot Stack Entry.

This procedure details how to add new boot stack entries to the boot.sys file. Make sure you are at the Exec mode prompt and enter the following commands:
configure
   boot system priority number image image_url config cfg_url

IMPORTANT:

If the URL is a USB device, the USB port must be pre-configured via the hypervisor for the usb1 keyword to work.

The following command creates a new boot stack entry, using a boot priority of 3.
[local]host_name(config)# boot system priority
3 image /flash/image_filename.bin config /flash/general.cfg

IMPORTANT:

Boot stack changes saved to the boot.sys file are not executed until StarOS is rebooted.

Deleting a Boot Stack Entry

This procedure details how to remove an individual boot stack entry from the boot.sys file. Make sure you are at the Exec mode prompt and enter the following commands:

configure
   no boot system priority number

Where number specifies the boot priority used for the boot stack entry. This command removes that specific entry from the boot stack, causing the boot.sys file to be overwritten.

Upgrading StarOS

The following information is required prior to performing a StarOS upgrade:
  • Current StarOS version
  • New StarOS version
  • Upgrade method

StarOS Release Version

StarOS can be configured to provide services and perform pre-defined functions through commands issued from the CLI.

The StarOS image is delivered as a single binary file (.bin file extension) and is loaded as a single instance.

Refer to the Release Notes supplied with the StarOS code drop for the binary file name.

Download the StarOS Image from the Support Site

Access to the Cisco support site and download facility is username and password controlled. You must have an active customer account to access the site and download the StarOS image.

Download the software image to a network location from which it can be uploaded to the /flash device.

Contact your Cisco representative or Cisco TAC for additional information.

Transfer the StarOS Image to /flash

Transfer the new operating system image file to the /flash using one of the following methods:
  • Copy the file from a network location by entering the following command:
    [local]host_name# copy from_url
    to_url [-noconfirm]
    
  • Transfer the file to the /flash device using an FTP client with access to the system.

    IMPORTANT:

    Whenever transferring a StarOS image file using the file transfer protocol (FTP), the FTP client must be configured to transfer the file using binary mode. Failure to use binary transfer mode will make the transferred operating system image file unusable.

  • Transfer the file to the /flash device using an SFTP client with access to the system.
Verify that the image file was successfully transferred to the /flash device by running the following Exec mode command:
[local]host_name# directory /flash

The image filename should appear in the displayed output.

Run the show version /flash/image_filename command to verify the build information.
[local]host_name# show version /flash/image_filename.bin

Saving a Copy of the Current Configuration File

Prior to upgrading to a new StarOS release, you should copy and rename the current configuration file to the /flash device and to an off-chassis location (external memory device or network URL). This renamed copy assures that you will have a fallback, loadable configuration file should a problem be encountered during the upgrade.

Off-line Software Upgrade

An off-line software upgrade can be performed for any VPC, upgrading from any version of StarOS to any other version, regardless of version number. This process is considered off-line because while many of the steps can be performed while the VPC is currently supporting sessions, the last step of this process requires a reload to actually apply the StarOS upgrade.

This procedure assumes that you have a CLI session established and are placing the new StarOS .bin image file onto the local file system. To begin, make sure you are at the Exec mode prompt.

Configure a Newcall Policy

Configure a newcall policy from the Exec mode to meet your service requirements. When enabled the policy redirects or rejects new calls in anticipation of the StarOS reload that completes the upgrade process. This reduces the amount of service disruption to subscribers caused by the system reload that completes the upgrade.

IMPORTANT:

Newcall policies are created on a per-service basis. If you have multiple services running on the VPC, you can configure multiple newcall policies.

The general syntax for newcall policies is described below:
[local]host_name# newcall policy service_type { all | name service_name } reject

Keyword availability varies by service_type. For a complete description of the newcall policy command with all its associated keywords, see the Exec Mode Commands chapter of the Command Line Interface Reference.

Configure a Message of the Day Banner

Optional: Configure a “Message of the Day” banner informing other management users that the system will be rebooted by entering the following command from the Global Configuration mode prompt.
[local]host_name(config)# banner motd “banner_text”

banner_text is the message that you would like to be displayed and can be up to 2048 alphanumeric characters. Note that banner_text must begin with and end in double quotation marks (“ “). For more information in entering CLI banner information, see the CLI Reference. The banner is displayed when an administrative user logs onto the CLI.

Back up the Current CLI Configuration File

Back up the current CLI configuration file by entering the following command:
[local]host_name# copy from_url to_url [-noconfirm]

This creates a mirror-image of the CLI configuration file linked to the operating system defined in the current boot stack entry.

The following command example creates a backup copy of the file general.cfg located on the /flash device to the file general_3652.cfg:
[local]host_name# copy /flash/general.cfg /flash/general_3652.cfg

Create a New Boot Stack Entry

Create a new boot stack entry for the new file group, consisting of the new operating system image file and the currently used CLI configuration file by entering the following Global Configuration command:
[local]host_name(config)# boot system priority number image image_url /flash/filename config cfg_url /flash/filename

Assign the next highest priority to this entry, by using the N-1 method, wherein you assign a priority number that is one number less than your current highest priority.

IMPORTANT:

Run the Exec mode show boot command to verify that there are less than 10 entries in the boot.sys file and that a higher priority entry is available (minimally there is no priority 1 entry in the boot stack).

If priority 1 is in use, you must renumber the existing entries to ensure that at least that priority is available.

The maximum number of boot stack entries that can be contained in the boot.sys file is 10. If there are already 10 entries in the boot stack, you must delete at least one of these entries (typically, the lowest priority) and, if necessary, renumber some or all of the other entries before proceeding. Use the no boot system priority command to delete a book stack entry.
[local]host_name# configure
[local]host_name(config)# no boot system priority number
To add new boot stack entries to the boot.sys file enter the following commands:
[local]host_name# configure
[local]host_name(config)# boot system priority number image image_url config cfg_url

For information on using the boot system priority command, refer to Adding a New Boot Stack Entry.

Save the Running Configuration

Save the currently running, upgraded configuration prior to rebooting StarOS.

To save the running configuration to the current configuration file:
[local]host_name# save configuration /flash

Reboot StarOS

Reboot StarOS by entering the following command:
[local]host_name# reload [-noconfirm]

As StarOS reboots, it loads the new StarOS image and its corresponding CLI configuration file using the new boot stack entry configured earlier.

After the reboot is completed, establish a CLI session and enter the show version command to verify that the active software version is correct.

Verify the Running Software Version

After StarOS has successfully booted, verify that the new StarOS version is running by executing the Exec mode show version command.
[local]host_name# show version

Restoring the Previous Software Image

If for some reason you need to undo the upgrade, perform the upgrade again except:

  • Specify the locations of the upgrade software image and configuration files.
then
  • Specify the locations of the original software image and configuration files.

Upgrading ICSR

The procedure for upgrading primary and backup ICSR instances is described in the Interchassis Session Recovery chapter. Essentially the procedure requires upgrading the primary and standby VPCs using the off-line method while each is in standby mode.

Performing Dynamic Software Updates

StarOS allows the runtime loading of plugins. All StarOS builds include a “default” baseline plugin.

This feature is currently used to dynamically update the detection logic used to filter P2P applications via the Application Detection and Control (ADC) feature.

Patching is the process used to install a plugin as an incremental update to a StarOS release. One plugin can be provided to multiple, compatible, concurrent product releases. A plugin is distributed in the form of a compressed distribution kit via the internet or by other means (USB stick, CD, etc.).

A plugin is a functional software entity that provides incremental updates to a pre-existing StarOS software component. Plugins have the characteristic of being dynamically loadable at runtime and do not require a system restart. A plugin has a name and one or more versions. All plugin names are known to the system at product release.

For complete information on the Dynamic Software Update process, refer to the ADC Administration Guide.

Managing License Keys

License keys define capacity limits (number of allowed subscriber sessions) and available features on VPC. Adding new license keys allows you to increase capacity and add new features as your subscriber base grows.

New System License Keys

New StarOS images are delivered with no license keys installed. In most cases, you receive the license key in electronic format (usually through e-mail).

When StarOS boots with no license key installed, a default set of restricted session use and feature licenses is installed. The following Exec Mode command lists the license information:
[local]host_name# show license information

Session Use and Feature Use Licenses

Session use and feature use licenses are software mechanisms that provide session limit controls and enable special features within StarOS. These electronic licenses are stored in the StarOS configuration file that is loaded each time VPC is initialized or restarted.
  • Session use licenses limit the number of concurrent sessions that a VPC is capable of supporting per service type and are acquired on an as-needed basis. This allows carriers to pay only for what they are using and easily increase capacity as their subscriber base grows.
  • Feature use licenses enable specific features/functionality within StarOS and are distributed based on the total number of sessions supported by VPC.

Installing New License Keys

Use the instructions below to install a new license key.

Cutting and Pasting the Key

If you have a copy of the license, use the following configuration to cut and paste just the license key part:

  1. From the Exec mode, enter the following:
    configure
    
       license key license
    
       exit
    
    license is the license key string. The license can be an alphanumeric string of 1 through 1023 characters that is case sensitive. Copy the license key as shown in the example below, including the “\ (double-quote slash). Please note: this is not a functional license.
    "\
    
    VER=1|C1M=000-0000-00|C1S=03290231803|C2M=11-1111-11-1|C2S=\STCB21M82003R80411A4|DOI=0000000000|DOE=00000000|ISS=1|NUM=13459|0000000000000|LSP=000000|LSH=000000|LSG=500000|LSL=500000\|FIS=Y|FR4=Y|FPP=Y|FCS=Y|FTC=Y|FMG=Y|FCR=Y|FSR=Y|FPM=Y|FID=Y|SIG=MCwCF\Esnq6Bs/XdmyfLe7rHcD4sVP2bzAhQ3IeHDoyyd6388jHsHD99sg36SG267gshssja77
    
    end
    
  2. Verify that the license key just entered was accepted by entering the following command at the Exec mode prompt:
    show license key
    
    The new license key should be displayed. If it is not, return to the Global configuration mode and re-enter the key using the license key command.
  3. Verify that the license key enabled the correct functionality by entering the following command:
    [local]host_name# show license information  
    
    All license keys and the new session capacity or functionality enabled should be listed. If the functionality or session capacity enabled by the new key is incorrect, please contact your service representative.
  4. Save your configuration as described in the Verifying and Saving Your Configuration chapter.

    CAUTION:

    Failure to save the new license key configuration in the current CLI configuration file will result in the loss of any of the new features enabled by the license key once the system is reloaded.

Adding License Keys to Configuration Files

License keys can be added to a new or existing configuration file.

IMPORTANT:

License key information is maintained as part of the CLI configuration. Each time a key is installed or updated, you must re-save the configuration file.

  1. Open the configuration file to which the new license key commands are to be copied.
  2. Copy the license as shown in the example, including the “\ (double-quote slash). Please note: this is not a functional license.
    "\
    
    VER=1|C1M=000-0000-00|C1S=03290231803|C2M=11-1111-11-1|C2S=\STCB21M82003R80411A4|DOI=0000000000|DOE=00000000|ISS=1|NUM=13459|0000000000000|LSP=000000|LSH=000000|LSG=500000|LSL=500000\|FIS=Y|FR4=Y|FPP=Y|FCS=Y|FTC=Y|FMG=Y|FCR=Y|FSR=Y|FPM=Y|FID=Y|SIG=MCwCF\Esnq6Bs/XdmyfLe7rHcD4sVP2bzAhQ3IeHDoyyd6388jHsHD99sg36SG267gshssja77
    
    end
    
  3. Paste the license key into the configuration

    IMPORTANT:

    Paste the license key information at the beginning of the configuration file to ensure the system has the expected capacity and features before it configures contexts.

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

License Expiration Behavior

When a license expires, there is a built-in grace period of 30 days that allows normal use of the licensed session use and feature use licenses. This allows you to obtain a new license without any interruption of service.

The following Exec mode command lists the license information including the date the grace period is set to expire:
[local]host_name# show license information  

Requesting License Keys

License keys for the system can be obtained through your Cisco account representative. Specific information is required before a license key may be generated:

  • Sales Order or Purchase Order information
  • Desired session capacity
  • Desired functionality

Viewing License Information

To see the license detail, enter the following command from the Exec mode:

[local]host_name# show license information [ full | key [ full ] ] 

Deleting a License Key

Use the procedure below to delete the session and feature use license key from a configuration. You must be a security administrator or administrator.

configure
   no license key
   exit
[local]host_name# show license key

The output of this command should display: “No license key installed”.

Managing Local-User Administrative Accounts

Unlike context-level administrative accounts which are configured via a configuration file, information for local-user administrative accounts is maintained in a separate file in flash memory and managed through the software’s Shared Configuration Task (SCT). Because local-user accounts were designed to be compliant with ANSI T1.276-2003, the system provides a number of mechanisms for managing these types of administrative user accounts.

Configuring Local-User Password Properties

Local-user account password properties are configured globally and apply to all local-user accounts. The system supports the configuration of the following password properties:
  • Complexity: Password complexity can be forced to be compliant with ANSI T1.276-2003.
  • History length: How many previous password versions should be tracked by the system.
  • Maximum age: How long a user can use the same password.
  • Minimum number of characters to change: How many characters must be changed in the password during a reset.
  • Minimum change interval: How often a user can change their password.
  • Minimum length: The minimum number of characters a valid password must contain.

Refer to the local-user password command in Global Configuration Mode Commands in the Command Line Interface Reference for details on each of the above parameters.

Configuring Local-User Account Management Properties

Local-user account management includes configuring account lockouts and user suspensions.

Local-User Account Lockouts

Local-user accounts can be administratively locked for the following reasons:
  • Login failures: The configured maximum login failure threshold has been reached. Refer to the local-user max-failed-logins command in Global Configuration Mode Commands in the Command Line Interface Reference for details
  • Password Aging: The configured maximum password age has been reached. Refer to the local-user password command in Global Configuration Mode Commands in the Command Line Interface Reference for details.

Accounts that are locked out are inaccessible to the user until either the configured lockout time is reached (refer to the local-user lockout-time command in Global Configuration Mode Commands in the Command Line Interface Reference) or a security administrator clears the lockout (refer to the clear local-user command in Exec Mode Commands in the Command Line Interface Reference).

IMPORTANT:

Local-user administrative user accounts could be configured to enforce or reject lockouts. Refer to the local-user username command in Global Configuration Mode Commands in the Command Line Interface Reference for details.

Local-User Account Suspensions

Local-user accounts can be suspended as follows:

configure
   suspend local-user name
A suspension can be removed by entering:
configure
   no suspend local-user name

Changing Local-User Passwords

Local-user administrative users can change their passwords using the password change command in the Exec mode. Users are prompted to enter their current and new passwords.

Security administrators can reset passwords for local-users by entering the following command from the root prompt in the Exec mode:
[local]host_name# password change username name

name is the name of the local-user account for which the password is to be changed. When a security administrator resets a local-user’s password, the system prompts the user to change their password the next time they login.

All new passwords must adhere to the password properties configured for the system.