CSS Administration Guide (Software Version 7.20) - Configuring User Profiles [Cisco CSS 11500 Series Content Services Switches]

Table Of Contents

Configuring User Profiles

User Profiles Overview

Configuring User Terminal Parameters

Configuring Terminal Idle

Configuring Terminal Length

Configuring the More Terminal Prompt

Configuring Terminal Netmask-Format

Configuring Terminal Timeout

Configuring Idle Timeout

Using Expert Mode

Changing the CLI Prompt

Modifying the History Buffer

Displaying the History Buffer

Copying and Saving User Profiles

Copying the Running Profile to the Default-Profile

Copying the Running Profile to a User Profile

Copying the Running Profile to an FTP Server

Copying the Running Profile to a TFTP Server

Configuring a Login Banner

Where to Go Next

Configuring User Profiles

This chapter describes how to configure user profiles. Information in this chapter applies to all models of the CSS, except where noted.

This chapter contains the following major sections:

•User Profiles Overview

•Configuring User Terminal Parameters

•Configuring Idle Timeout

•Using Expert Mode

•Changing the CLI Prompt

•Modifying the History Buffer

•Copying and Saving User Profiles

•Configuring a Login Banner

User Profiles Overview

The CSS contains a default-profile file that resides in the scripts directory on the CSS disk (hard disk or Flash disk). This file contains settings that are user-specific; that is, they apply uniquely to each user when that user logs in.

You can customize the following settings for each user:

•CLI prompt

•Expert mode

•History buffer

•Terminal parameters

•Login banner

Though the settings are user-specific, each default setting applies to all users until the user saves the default-profile file to a username-profile (where username is the current login username). You can continue using the default-profile file to ensure all users logging in to a CSS use the same settings. See the "Copying and Saving User Profiles" section for information on saving the default-profile file.

If you change a user setting and want to save this setting in the scripts directory of the current ADI, use the copy profile command. If you do not save this setting, the CSS stores the setting temporarily in a running profile. If you attempt to log out of the CSS without saving profile changes, the CSS prompts you that profile changes have been made and allows you to save or discard the changes.

When you upgrade the ADI, the CSS deletes all user profile from the current ADI directory. If you wish to save user profiles permanently, use the save_profile command. This command saves the profiles in both the scripts and archive directories in the current ADI. The archive directory is not overwritten during a software upgrade.

To access the CSS disk, FTP to the CSS. Use the appropriate commands to access the scripts directory and list the contents of the default-profile file. When logged into the CSS, use the show profile command to display either the default-profile file or your username-profile file.

For example:
# show profile
@prompt CSS11503
@no expert
alias all reboot "@configure;boot;rebo"
alias all shutdown "@configure;boot;shutd"
alias all logon "@configure;logging line \${LINE};exit"
alias all logoff "@configure;no logging line \${LINE};exit"
alias all aca-load "@script play service-load"
alias all dnslookup "@script play dnslookup"
alias super save_config "copy running-config startup-config;archive 
startup-config"
alias super setup "script play setup"
alias super upgrade "script play upgrade"
alias super monitor "script play monitor"
alias super save_profile "copy profile user-profile;archive script 
admin-profile
"
set CHECK_STARTUP_ERRORS "1" session
Configuring User Terminal Parameters

Use the terminal command to configure terminal parameters. These parameters control output to the system terminal screen. Terminal parameters are user-specific; that is, they apply uniquely to each CSS user.

Use the copy profile user-profile command to add terminal command parameters to your user profile so that the parameters are used each time you log in. Otherwise, you must reenter the commands for the parameters to take effect each time you log in.

This section includes the following topics:

•Configuring Terminal Idle

•Configuring Terminal Length

•Configuring the More Terminal Prompt

•Configuring Terminal Netmask-Format

•Configuring Terminal Timeout

Configuring Terminal Idle

Use the terminal idle command to set the length of time a session can be idle before the CSS terminates a console or Telnet session. This command is available in the User and SuperUser modes. Enter an idle time between 0 and 65535 minutes. The default value is 0 (disabled).

To set a terminal idle time, enter:
# terminal idle 15
To restore the terminal idle time to the default state of disabled, enter:
# no terminal idle
Configuring Terminal Length

Use the terminal length command to set the number of output lines the CLI displays on the terminal screen. This command is available in User and SuperUser modes. Enter the number of lines you want the CLI to display, from 2 to 65535. The default is 25 lines.

To set the line number to 35, enter:
# terminal length 35
To reset the number of lines to the default of 25 lines, enter:
# no terminal length
Configuring the More Terminal Prompt

Use the terminal more command to display the --More-- prompt at the bottom of the terminal screen. When you enter the question mark (?) character at the command line to get help about a command, the CSS displays 24 lines on the terminal. The --More-- prompt indicates that additional CLI commands are to follow. Press the Space bar to continue viewing the next series of commands (or press the Return key to display only the next line). This command is available in User and SuperUser modes. The default is enabled.

You can also toggle the terminal more function on and off within a session by using the Esc-M key sequence.

To enable support for the --More-- terminal prompt, enter:
# terminal more
To disable support for the --More-- terminal prompt, enter:
# no terminal more
Configuring Terminal Netmask-Format

Use the terminal netmask-format command to determine how the CSS displays subnet masks in show screens. This command is available in User and SuperUser modes. The options for this command are as follows:

•terminal netmask-format bitcount - Displays masks in classless interdomain routing (CIDR) bitcount (for example, /24).

•terminal netmask-format decimal - Displays masks in dotted-decimal format (for example, 255.255.255.0). This is the default format.

•terminal netmask-format hexadecimal - Displays masks in hexadecimal format (for example, OXFFFFFFOO).

For example, to display subnet masks in bit-count format, enter:
# terminal netmask-format bitcount
To restore the default display format (decimal), enter:
# no terminal netmask format
Configuring Terminal Timeout

Use the terminal timeout command to set the total amount of time a session can be logged in before the CSS terminates a console or Telnet session. This command is available in User and SuperUser modes. Enter a timeout value between 0 and 65535 minutes. The default value is 0 (disabled).

For example, to set the terminal timeout value to 30 minutes, enter:
# terminal timeout 30
To restore the terminal timeout value to the default state of disabled, enter:
# no terminal timeout
Configuring Idle Timeout

Use the idle timeout command to globally set the total amount of time all sessions can be active before the CSS terminates a console or Telnet session. Enter a timeout value between 0 and 65535 minutes. The default value is enabled for 5 minutes.

To override the idle timeout value for a specific session, configure the terminal timeout command. Terminal commands are user-specific; that is, they apply uniquely to each CSS user.

We recommend that you configure the idle timeout for at least 30 minutes. Setting this value to 30 minutes:

•Cleans up idle Telnet sessions

•Helps prevent busy conditions due to a high number of active Telnet sessions

To set an idle timeout value, enter:
(config)# idle timeout 15
To restore the terminal timeout value to the default of enabled for 5 minutes, enter:
(config)# no idle timeout
Using Expert Mode

Expert mode allows you to turn the CSS confirmation capability on or off. Expert mode is available in SuperUser mode and is off by default. When expert mode is off, the CSS prompts you for confirmation when you:

•Execute commands that could delete or change operating parameters

•Exit a terminal session (console or Telnet) without copying the running configuration to the startup configuration

•Create services, owners, and content rules

Caution Turning expert mode on disables the CSS from prompting you for confirmation when you make changes. When you exit from the CSS, all configuration changes are automatically saved to the profile and to the running-config file. You are not prompted for confirmation to save the changes.

To enable expert mode, enter:
# expert
To allow the CSS to prompt you for confirmation before executing configuration commands, enter:
# no expert
For example, when you enter the command to create an owner and expert mode is off, the CSS prompts you to verify the command, enter:
(config)# owner arrowpoint.com
Create owner <arrowpoint.com>, [y/n]:y
(config-owner[arrowpoint.com])#
Changing the CLI Prompt

The CLI default prompt appears as the CSS product model number followed by the number (#) symbol. The CSS adds a # to the prompt automatically to indicate SuperUser mode. To change the default prompt, enter the prompt command. For example:
CSS11506# prompt CSS1-lab
CSS1-lab# 
You can enter a maximum of 15 characters.

To save the new prompt, add it to your user- or default-profile file. To restore the prompt to the default, use the no form of the prompt command.

For example:
CSS11506# no prompt
Modifying the History Buffer

Use the history command to modify the CLI history buffer length. The history buffer stores the most recent CLI commands that you enter. Enter the number of lines you want in the history buffer as an integer from 0 to 256. The default is 20. This command is available only in SuperUser mode.

To set the history buffer to 80 lines, enter:
# history length 80
To disable the history function (setting of 0), enter:
# history length 0
To restore the history buffer to the default of 20 lines, enter:
# no history length
Displaying the History Buffer

Use the show history command to display the contents of the history buffer. The history buffer is cleared automatically upon reboot.

For example:
# show history
	history
	show history
	show ip routes
	show ip summary
	show ip stat
	clock
	clock date
	clock time
	show history
Copying and Saving User Profiles

Use the copy profile command to copy the running profile from the CSS to the default-profile file, an FTP server, a TFTP server, or your user-profile file. This command is available only in SuperUser mode.

If you exit the CSS without copying changes in the running profile to your username-profile or default-profile file, the CSS prompts you that the profile has changed and queries whether you want to save your changes. If you respond with y, the CSS copies the running profile to your username-profile or the default-profile.

This section includes the following topics:

•Copying the Running Profile to the Default-Profile

•Copying the Running Profile to a User Profile

•Copying the Running Profile to an FTP Server

•Copying the Running Profile to a TFTP Server

Copying the Running Profile to the Default-Profile

Use the copy profile default-profile command to copy the running profile to the default profile. This command is available only in SuperUser mode.

For example:
# copy profile default-profile
Copying the Running Profile to a User Profile

Use the copy profile user-profile command to copy the changes made to the running profile to the user profile. This command is available only in SuperUser mode. This command creates a file username-profile if one does not exist (where username is the current username).

For example:
# copy profile user-profile
Copying the Running Profile to an FTP Server

Use the copy profile ftp command to copy the running profile to an FTP server. This command is available only in SuperUser mode. The syntax is:

copy profile ftp ftp_record filename
The variables for this command are as follows:

•ftp_record - The name of the FTP record file that contains the server IP address, username, and password. Enter an unquoted text string with no spaces and a maximum of 32 characters.

•filename - The name you want to assign to the file on the server. Include the full path to the file. Enter an unquoted text string with no spaces.

For example:
# copy profile ftp arrowrecord \records\arrowftprecord
Copying the Running Profile to a TFTP Server

Use the copy profile tftp command to copy the running profile to a TFTP server. This command is available only in SuperUser mode. The syntax is:
copy profile tftp ip_or_host filename
The variables for this command are as follows:

•ip_or_host - The IP address or host name of the server to receive the file. Enter an IP address in dotted-decimal notation (for example, 192.168.11.1) or in mnemonic host-name format (for example, myhost.mydomain.com).

•filename - The name you want to assign to the file on the server. Include the full path to the file. Enter an unquoted text string with no spaces and a maximum of 32 characters.

For example:
# copy profile tftp 192.168.3.6 \home\bobo\bobo-profile
Configuring a Login Banner

Use the set BANNER command to create and display a custom banner that appears after you log in to a CSS. The banner is an ASCII text file that you provide, and it resides in the CSS script directory. Because this feature is part of your user profile, you can have your own custom banner associated with your login name.

To configure a login banner, use the set BANNER command as follows.

1. Use any text editor (for example, Notepad or Wordpad) to create a custom banner and save it as a text file in the CSS script directory. Line width has a maximum of 80 characters.

2. Set the environment variable BANNER and point to the mybanner file:
# set BANNER "mybanner" session
The keyword session causes the CSS to create the environment variable every time you log in.

3. Enter the following to complete the configuration:
# copy profile user-profile
The next time you log in to the CSS, you see your custom banner.

To provide the same banner for all users, replace the command in Step 3 with:
# copy profile default-profile
Where to Go Next

Chapter 11, Configuring CSS Remote Access Methods provides information on configuring CSS remote access methods, including the Secure Shell Daemon (SSH) protocol, the Remote Authentication Dial-In User Service (RADIUS) protocol, and the Terminal Access Controller Access Control System (TACACS+) protocol.

	CSS Administration Guide (Software Version 7.20)
	Configuring User Profiles
CSS Administration Guide (Software Version 7.20) Index Preface Booting, Logging In, and Getting Started Configuring CSS Basics Managing the CSS Software Specifying the CSS Boot Configuration Configuring Interfaces and Circuits Configuring CSS Network Protocols Configuring Open Shortest Path First (OSPF) Using the CSS Logging Features Configuring Flow and Port Mapping Parameters Configuring User Profiles Configuring CSS Remote Access Methods Configuring Simple Network Management Protocol (SNMP) Configuring Remote Monitoring (RMON) Upgrading Your CSS Software Using the Offline Diagnostic Monitor Menu Troubleshooting the Boot Process	Download this chapter Configuring User Profiles Download the complete book Cisco Content Services Switch Administration Guide (Software Version 7.20), Book-Length PDF (PDF - 4 MB) Table Of Contents Configuring User Profiles User Profiles Overview Configuring User Terminal Parameters Configuring Terminal Idle Configuring Terminal Length Configuring the More Terminal Prompt Configuring Terminal Netmask-Format Configuring Terminal Timeout Configuring Idle Timeout Using Expert Mode Changing the CLI Prompt Modifying the History Buffer Displaying the History Buffer Copying and Saving User Profiles Copying the Running Profile to the Default-Profile Copying the Running Profile to a User Profile Copying the Running Profile to an FTP Server Copying the Running Profile to a TFTP Server Configuring a Login Banner Where to Go Next Configuring User Profiles This chapter describes how to configure user profiles. Information in this chapter applies to all models of the CSS, except where noted. This chapter contains the following major sections: •User Profiles Overview •Configuring User Terminal Parameters •Configuring Idle Timeout •Using Expert Mode •Changing the CLI Prompt •Modifying the History Buffer •Copying and Saving User Profiles •Configuring a Login Banner User Profiles Overview The CSS contains a default-profile file that resides in the scripts directory on the CSS disk (hard disk or Flash disk). This file contains settings that are user-specific; that is, they apply uniquely to each user when that user logs in. You can customize the following settings for each user: •CLI prompt •Expert mode •History buffer •Terminal parameters •Login banner Though the settings are user-specific, each default setting applies to all users until the user saves the default-profile file to a username-profile (where username is the current login username). You can continue using the default-profile file to ensure all users logging in to a CSS use the same settings. See the "Copying and Saving User Profiles" section for information on saving the default-profile file. If you change a user setting and want to save this setting in the scripts directory of the current ADI, use the copy profile command. If you do not save this setting, the CSS stores the setting temporarily in a running profile. If you attempt to log out of the CSS without saving profile changes, the CSS prompts you that profile changes have been made and allows you to save or discard the changes. When you upgrade the ADI, the CSS deletes all user profile from the current ADI directory. If you wish to save user profiles permanently, use the save_profile command. This command saves the profiles in both the scripts and archive directories in the current ADI. The archive directory is not overwritten during a software upgrade. To access the CSS disk, FTP to the CSS. Use the appropriate commands to access the scripts directory and list the contents of the default-profile file. When logged into the CSS, use the show profile command to display either the default-profile file or your username-profile file. For example: # show profile @prompt CSS11503 @no expert alias all reboot "@configure;boot;rebo" alias all shutdown "@configure;boot;shutd" alias all logon "@configure;logging line \${LINE};exit" alias all logoff "@configure;no logging line \${LINE};exit" alias all aca-load "@script play service-load" alias all dnslookup "@script play dnslookup" alias super save_config "copy running-config startup-config;archive startup-config" alias super setup "script play setup" alias super upgrade "script play upgrade" alias super monitor "script play monitor" alias super save_profile "copy profile user-profile;archive script admin-profile " set CHECK_STARTUP_ERRORS "1" session Configuring User Terminal Parameters Use the terminal command to configure terminal parameters. These parameters control output to the system terminal screen. Terminal parameters are user-specific; that is, they apply uniquely to each CSS user. Use the copy profile user-profile command to add terminal command parameters to your user profile so that the parameters are used each time you log in. Otherwise, you must reenter the commands for the parameters to take effect each time you log in. This section includes the following topics: •Configuring Terminal Idle •Configuring Terminal Length •Configuring the More Terminal Prompt •Configuring Terminal Netmask-Format •Configuring Terminal Timeout Configuring Terminal Idle Use the terminal idle command to set the length of time a session can be idle before the CSS terminates a console or Telnet session. This command is available in the User and SuperUser modes. Enter an idle time between 0 and 65535 minutes. The default value is 0 (disabled). To set a terminal idle time, enter: # terminal idle 15 To restore the terminal idle time to the default state of disabled, enter: # no terminal idle Configuring Terminal Length Use the terminal length command to set the number of output lines the CLI displays on the terminal screen. This command is available in User and SuperUser modes. Enter the number of lines you want the CLI to display, from 2 to 65535. The default is 25 lines. To set the line number to 35, enter: # terminal length 35 To reset the number of lines to the default of 25 lines, enter: # no terminal length Configuring the More Terminal Prompt Use the terminal more command to display the --More-- prompt at the bottom of the terminal screen. When you enter the question mark (?) character at the command line to get help about a command, the CSS displays 24 lines on the terminal. The --More-- prompt indicates that additional CLI commands are to follow. Press the Space bar to continue viewing the next series of commands (or press the Return key to display only the next line). This command is available in User and SuperUser modes. The default is enabled. You can also toggle the terminal more function on and off within a session by using the Esc-M key sequence. To enable support for the --More-- terminal prompt, enter: # terminal more To disable support for the --More-- terminal prompt, enter: # no terminal more Configuring Terminal Netmask-Format Use the terminal netmask-format command to determine how the CSS displays subnet masks in show screens. This command is available in User and SuperUser modes. The options for this command are as follows: •terminal netmask-format bitcount - Displays masks in classless interdomain routing (CIDR) bitcount (for example, /24). •terminal netmask-format decimal - Displays masks in dotted-decimal format (for example, 255.255.255.0). This is the default format. •terminal netmask-format hexadecimal - Displays masks in hexadecimal format (for example, OXFFFFFFOO). For example, to display subnet masks in bit-count format, enter: # terminal netmask-format bitcount To restore the default display format (decimal), enter: # no terminal netmask format Configuring Terminal Timeout Use the terminal timeout command to set the total amount of time a session can be logged in before the CSS terminates a console or Telnet session. This command is available in User and SuperUser modes. Enter a timeout value between 0 and 65535 minutes. The default value is 0 (disabled). For example, to set the terminal timeout value to 30 minutes, enter: # terminal timeout 30 To restore the terminal timeout value to the default state of disabled, enter: # no terminal timeout Configuring Idle Timeout Use the idle timeout command to globally set the total amount of time all sessions can be active before the CSS terminates a console or Telnet session. Enter a timeout value between 0 and 65535 minutes. The default value is enabled for 5 minutes. To override the idle timeout value for a specific session, configure the terminal timeout command. Terminal commands are user-specific; that is, they apply uniquely to each CSS user. We recommend that you configure the idle timeout for at least 30 minutes. Setting this value to 30 minutes: •Cleans up idle Telnet sessions •Helps prevent busy conditions due to a high number of active Telnet sessions To set an idle timeout value, enter: (config)# idle timeout 15 To restore the terminal timeout value to the default of enabled for 5 minutes, enter: (config)# no idle timeout Using Expert Mode Expert mode allows you to turn the CSS confirmation capability on or off. Expert mode is available in SuperUser mode and is off by default. When expert mode is off, the CSS prompts you for confirmation when you: •Execute commands that could delete or change operating parameters •Exit a terminal session (console or Telnet) without copying the running configuration to the startup configuration •Create services, owners, and content rules Caution Turning expert mode on disables the CSS from prompting you for confirmation when you make changes. When you exit from the CSS, all configuration changes are automatically saved to the profile and to the running-config file. You are not prompted for confirmation to save the changes. To enable expert mode, enter: # expert To allow the CSS to prompt you for confirmation before executing configuration commands, enter: # no expert For example, when you enter the command to create an owner and expert mode is off, the CSS prompts you to verify the command, enter: (config)# owner arrowpoint.com Create owner <arrowpoint.com>, [y/n]:y (config-owner[arrowpoint.com])# Changing the CLI Prompt The CLI default prompt appears as the CSS product model number followed by the number (#) symbol. The CSS adds a # to the prompt automatically to indicate SuperUser mode. To change the default prompt, enter the prompt command. For example: CSS11506# prompt CSS1-lab CSS1-lab# You can enter a maximum of 15 characters. To save the new prompt, add it to your user- or default-profile file. To restore the prompt to the default, use the no form of the prompt command. For example: CSS11506# no prompt Modifying the History Buffer Use the history command to modify the CLI history buffer length. The history buffer stores the most recent CLI commands that you enter. Enter the number of lines you want in the history buffer as an integer from 0 to 256. The default is 20. This command is available only in SuperUser mode. To set the history buffer to 80 lines, enter: # history length 80 To disable the history function (setting of 0), enter: # history length 0 To restore the history buffer to the default of 20 lines, enter: # no history length Displaying the History Buffer Use the show history command to display the contents of the history buffer. The history buffer is cleared automatically upon reboot. For example: # show history history show history show ip routes show ip summary show ip stat clock clock date clock time show history Copying and Saving User Profiles Use the copy profile command to copy the running profile from the CSS to the default-profile file, an FTP server, a TFTP server, or your user-profile file. This command is available only in SuperUser mode. If you exit the CSS without copying changes in the running profile to your username-profile or default-profile file, the CSS prompts you that the profile has changed and queries whether you want to save your changes. If you respond with y, the CSS copies the running profile to your username-profile or the default-profile. This section includes the following topics: •Copying the Running Profile to the Default-Profile •Copying the Running Profile to a User Profile •Copying the Running Profile to an FTP Server •Copying the Running Profile to a TFTP Server Copying the Running Profile to the Default-Profile Use the copy profile default-profile command to copy the running profile to the default profile. This command is available only in SuperUser mode. For example: # copy profile default-profile Copying the Running Profile to a User Profile Use the copy profile user-profile command to copy the changes made to the running profile to the user profile. This command is available only in SuperUser mode. This command creates a file username-profile if one does not exist (where username is the current username). For example: # copy profile user-profile Copying the Running Profile to an FTP Server Use the copy profile ftp command to copy the running profile to an FTP server. This command is available only in SuperUser mode. The syntax is: copy profile ftp ftp_record filename The variables for this command are as follows: •ftp_record - The name of the FTP record file that contains the server IP address, username, and password. Enter an unquoted text string with no spaces and a maximum of 32 characters. •filename - The name you want to assign to the file on the server. Include the full path to the file. Enter an unquoted text string with no spaces. For example: # copy profile ftp arrowrecord \records\arrowftprecord Copying the Running Profile to a TFTP Server Use the copy profile tftp command to copy the running profile to a TFTP server. This command is available only in SuperUser mode. The syntax is: copy profile tftp ip_or_host filename The variables for this command are as follows: •ip_or_host - The IP address or host name of the server to receive the file. Enter an IP address in dotted-decimal notation (for example, 192.168.11.1) or in mnemonic host-name format (for example, myhost.mydomain.com). •filename - The name you want to assign to the file on the server. Include the full path to the file. Enter an unquoted text string with no spaces and a maximum of 32 characters. For example: # copy profile tftp 192.168.3.6 \home\bobo\bobo-profile Configuring a Login Banner Use the set BANNER command to create and display a custom banner that appears after you log in to a CSS. The banner is an ASCII text file that you provide, and it resides in the CSS script directory. Because this feature is part of your user profile, you can have your own custom banner associated with your login name. To configure a login banner, use the set BANNER command as follows. 1. Use any text editor (for example, Notepad or Wordpad) to create a custom banner and save it as a text file in the CSS script directory. Line width has a maximum of 80 characters. 2. Set the environment variable BANNER and point to the mybanner file: # set BANNER "mybanner" session The keyword session causes the CSS to create the environment variable every time you log in. 3. Enter the following to complete the configuration: # copy profile user-profile The next time you log in to the CSS, you see your custom banner. To provide the same banner for all users, replace the command in Step 3 with: # copy profile default-profile Where to Go Next Chapter 11, Configuring CSS Remote Access Methods provides information on configuring CSS remote access methods, including the Secure Shell Daemon (SSH) protocol, the Remote Authentication Dial-In User Service (RADIUS) protocol, and the Terminal Access Controller Access Control System (TACACS+) protocol.
	© 1992-2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.