Table Of Contents
Logging in and Getting Started
Configuration Quick Start
Logging into the CSS
Changing the Administrative Username and Password
Restricting Modifications to the CSS User Database
Configuring Usernames and Passwords
Configuring an IP Address and Subnet Mask for the Ethernet Management Port
Configuring an IP Address
Configuring a Subnet Mask
Configuring an IP Route
Configuring Date, Time, and Time Zone
Configuring European Date
Synchronizing the CSS with an SNTP Server
Configuring the SNTP Server
Configuring the SNTP Poll-Interval
Showing SNTP Configuration Information
Configuring an FTP Record
Copying Files from an FTP Server
Rebooting the CSS
Shutting Down the CSS
Using the Offline Diagnostic Monitor Menu
Accessing the Offline Diagnostic Monitor Main Menu
Using the Boot Configuration Menu
Setting Primary Boot Configuration
Setting Secondary Boot Configuration
Setting IP Address, and Subnet Mask
Showing the Boot Configuration
Using the Advanced Options
Deleting a Software Version
Using the Security Options
Using the Disk Options
Enabling and Disabling Core Dumps
Showing Core Dumps
CSS Software Overview
Using the Running-Config and Startup-Config
Clearing the Running-Config and the Startup-Config
Showing the Running-Config
Showing the Startup-Config
Creating a Running-Config or Startup-Config Using a Text Editor
Archiving Files to the Archive Directory
Archiving a Log File
Archiving the Running-Config
Archiving Scripts
Archiving the Startup-Config
Clearing the Archive Directory
Restoring Files from the Archive Directory
Restoring an Archived Log File
Restoring an Archived Script File
Restoring an Archived Startup-Config
Copying Core Dumps to an FTP or TFTP Server
Copying Core Dumps to an FTP Server
Copying Core Dumps to a TFTP Server
Displaying CSS Configurations
Displaying Software Information
Displaying Hardware Information
Showing System Resources
Showing User Information
Showing Current Logins
Where to Go Next
Logging in and Getting Started
This chapter describes how to log into the CSS and configure an IP address, subnet mask, and default route. Included in this chapter is a description of the system software. It also contains information on using the Offline Diagnostic Monitor (Offline DM) menu. Information in this chapter applies to all CSS models except where noted.
CSS software is available in a Standard or Enhanced feature set. The Enhanced feature set contains all of the Standard feature set and also includes Network Address Translation (NAT) Peering, Domain Name Service (DNS), Demand-Based Content Replication (Dynamic Hot Content Overflow), Content Staging and Replication, and Network Proximity DNS. Proximity Database and SSH are optional features.
Note 
When you boot the CSS for the first time, the software prompts you to enter a valid license key for the Standard or Enhanced feature set, or for Proximity Database, depending on your intended use for the CSS. For details, refer to the Content Services Switch Getting Started Guide, Chapter 4, Booting the CSS.
If you are upgrading from the Standard to the Enhanced feature set or want to activate another optional feature that you purchased, refer to the Content Services Switch Getting Started Guide, Chapter 4, Booting the CSS.
If you configure your CSS for Proximity Database, you cannot use the CSS for flow control. For details on Proximity Database, refer to the Content Services Switch Advanced Configuration Guide.
This chapter contains the following sections:
•Configuration Quick Start
•Logging into the CSS
•Configuring an IP Address and Subnet Mask for the Ethernet Management Port
•Configuring an IP Route
•Configuring Date, Time, and Time Zone
•Synchronizing the CSS with an SNTP Server
•Configuring an FTP Record
•Rebooting the CSS
•Shutting Down the CSS
•Using the Offline Diagnostic Monitor Menu
•Enabling and Disabling Core Dumps
•CSS Software Overview
•Using the Running-Config and Startup-Config
•Archiving Files to the Archive Directory
•Restoring Files from the Archive Directory
•Displaying CSS Configurations
Configuration Quick Start
Table 1-1 is a Quick Start configuration table designed to help you configure the CSS quickly and easily. This table provides steps to:
•Log in and access config mode so you can configure the CSS for operation
•Access boot mode to configure an IP address for the Ethernet Management port
•Configure a subnet mask from boot mode
•Configure a default IP route
•Enter the date, time, and time zone (optional)
•Specify an SNTP server (optional)
•Configure an FTP record (optional)
•Save your configuration from the running-config to the startup-config
Following Table 1-1 is an overview of the CSS system software and commands for saving, archiving, and restoring system configuration files.
Once you configure the Ethernet Management port IP address, you can continue to use the Console port or you can use the Ethernet Management port to Telnet into the CSS and configure it remotely.
Table 1-1 Configuration Quick Start
Task and Command Example
|
1. Log into the CSS using the default administrative username admin and password system or the username and password you assigned during the boot process.
|
2. Access config mode.
|
3. Access boot mode to configure an IP address for the Ethernet Management port. This IP address must be on a different subnet than any other CSS VLAN circuit IP subnet or you will not be able to access the port. You must reboot the CSS for the new IP address to take effect.
(config-boot)# ip address 172.3.6.58
|
4. Configure a subnet mask in boot mode.
(config-boot)# subnet mask 255.255.255.0
|
5. Exit from boot mode to config mode to configure a default route as required.
(config)# ip route 0.0.0.0/0 192.168.3.123
|
6. Exit from config mode to configure a date. The clock date command does not allow backspacing. If you enter a wrong date, reenter the command with the new information.
Enter the date in the format mm-dd-yy.
Enter date: [03-11-00] 03-12-00
Use the date european-date command to enable the clock date command to accept date input in the format of day, month, and year.
# date european-date 12/03/00
|
7. Configure the time using the clock time command. The clock time command does not allow backspacing. If you enter the wrong time, reenter the command with the new information.
Enter the time in the format hh:mm:ss.
Enter time: [15:17:33] 16:17:33
|
8. If you are using an SNTP server to synchronize the system clock of the CSS, specify the time zone and Universal Time Coordinated (UTC) offset.
# clock timezone EST hours 3 before-UTC
|
9. If you are using an SNTP server to synchronize the system clock of the CSS, access the config mode and specify the SNTP server and the polling frequency.
(config)# sntp server 192.168.19.21 version 2
(config)# sntp poll-interval 90
|
10. Configure a File Transfer Protocol (FTP) record file to use when accessing an FTP server from the CSS. This step is optional.
# ftp-record arrowrecord 192.168.19.21 bobo password "secret"
/outgoing
|
11. Save your configuration changes (recommended). Configuration changes reside in a virtual file called the running-configuration. To save your current configuration, use the copy running-config startup-config command. If you do not save the running-config, all configuration changes are lost upon reboot.
# copy running-config startup-config
|
Logging into the CSS
To log into the CSS, use the default administrative username admin and default password system, or use the administrative username and password you configured during the boot process. The default username admin enables you to log in with SuperUser status.
If you have not changed the default administrative username and password, it is recommended that you change them immediately to safeguard the CSS against unauthorized logins.
Note When you power up the CSS (after initial start-up), the boot process provides access to the Offline Diagnostic Monitor (Offline DM) menu. The Offline DM Main menu allows you to set the boot configuration, show the boot configuration, select Advanced Options, or reboot the system. For details on using the Offline DM Main menu, refer to "Using the Offline Diagnostic Monitor Menu" in this chapter.
Changing the Administrative Username and Password
The administrative username and password are stored in non-volatile RAM (NVRAM). Each time you reboot the CSS, it reads them from NVRAM and reinserts them into the user database. You can change the administrative username and password, but because the information is stored in NVRAM, you cannot delete them permanently. If you delete the administrative username using the no username command, the CSS deletes the username from the running-config, but restores it from NVRAM when you reboot.
SuperUser status is assigned to the administrative username by default.
To change the administrative username or password, you may either:
•Access the Offline Diagnostic Monitor (Offline DM) menu during the boot process. For information on the Offline DM Main menu see "Using the Offline Diagnostic Monitor Menu" in this chapter.
•Use the username-offdm name password text command.
The following example uses the CLI command to change the default administrative username and password.
(config)# username-offdm bobo password secret
Restricting Modifications to the CSS User Database
By default, access to the CSS user database is not restricted. Nonrestricted access means any user with SuperUser privileges (local user, administrator, or technician) can:
•Create, modify, or delete usernames (user database entries)
•Clear the CSS running-config file
You can use the restrict user-database command to restrict the CSS user database to CSS users who are identified as either an administrator or a technician.
To restrict modification of the CSS user database, enter:
(config)# restrict user-database
To remove restrictions for modifying the CSS user database, enter:
(config)# no restrict user-database
Configuring Usernames and Passwords
The CSS supports a maximum of 32 usernames, including an administrator username and a technician username. You can assign each user that logs into the CSS with SuperUser or User status.
•User - Allows access to a limited set of commands that enable you to monitor and display CSS parameters, but not change them. A User prompt ends with the > symbol. To view the commands available in User mode, at the User prompt, enter ?.
By default, new users have only user-level status unless you configure them to have SuperUser status.
•SuperUser - Allows access to the full set of CLI commands, including those in User mode, that enable you to configure the CSS. A SuperUser prompt ends with the # symbol.
From SuperUser mode, you can enter global configuration mode and its subordinate configuration modes.
Use the username command to create usernames and passwords to log in to the CSS. The syntax for this global configuration mode command is:
username name [des-password|password] password {superuser}
{dir-access access}
Note Any user with SuperUser status can create CSS usernames. To allow only administrator or technician users to create usernames, use the restrict user-database command (see "Restricting Modifications to the CSS User Database" in this section).
The options and variables are as follows:
•name - Sets the username you want to assign or change. Enter an unquoted text string with no spaces and a maximum of 16 characters. To see a list of existing usernames, enter username ?.
•des-password - Specifies that the password you enter is the Data Encryption Standard (DES) form of the password. Use this option only when you are creating a script or a startup configuration file. Enter a DES-encrypted, case-sensitive, unquoted text string with no spaces from 6 to 64 characters.
Note If you specify the des-password option, you must know the encrypted form of the password to successfully log in to the CSS. You can find the CSS encrypted password in the Global section of the running-config. To display the running-config, use the show running-config command.
•password - Specifies that the password is not encrypted onyour display as you enter it. However, the CSS DES-encrypts the password in the running-config for extra security. Use this option when you use the CLI to create users. Enter a case-sensitive, unquoted text string with no spaces from 6 to 16 characters.
•password - The text string that you enter. The CSS allows all special characters in a password except for the percent sign (%).
•superuser - (Optional) Specifies SuperUser privileges to allow a user to access SuperUser mode. If you do not enter this option, the user can only access User mode.
•dir-access access - (Optional) Defines the CSS directory access privileges for the username. There are access privileges assigned to the seven CSS directories; Script, Log, Root (installed CSS software), Archive, Release Root (configuration files), Core, and MIBs. By default, users have both read- and write-access privileges (B) to all seven directories. Changing the access level also affects the use of the CLI commands associated with directories.
Enter one of the following access privilege codes for the CSS Script, Log, Root, Archive, Release Root, Core, and MIB directories, in this order:
–R - Read-only access to the CSS directory
–W - Write-only access to the CSS directory
–B - Both read- and write-access privileges to the CSS directory
–N - No access privileges to the CSS directory
The following example creates a SuperUser named picard with a password of captain.
(config)# username picard password "captain" superuser
Figure 1-1 shows how the access privilege settings corresponds to the CSS directories.
Figure 1-1 CSS Directory Access Privileges
For example, to define directory access for username picard, enter:
(config)# username picard password "captain" superuser NWBNNNR
To display a list of existing usernames, enter:
To remove an existing username, enter:
(config)# no username picard
To change a user password, reenter the username command and specify the new password. Remember to include SuperUser privileges if required. For example:
(config)# username picard password "flute" superuser
Caution The
no username command removes a user permanently. Make sure you want to perform this action because you cannot undo this command.
Configuring an IP Address and Subnet Mask for the Ethernet Management Port
To communicate with the CSS and issue Command Line Interface (CLI) commands using out-of-band management, you must assign an IP address to the Ethernet Management port. You may also want to configure a subnet mask that the CSS uses upon boot.
The Ethernet Management port is located on the:
•CSS 11050 and CSS 11150 rear panels
•CSS 11800 SCM front panel
The CSS enables you to configure an IP address and a subnet mask:
•At the prompts during the boot process
•Using the Offline Diagnostic Monitor (Offline DM) menu
•Using CLI commands
For information on configuring an IP address and subnet mask during the boot routine or using the Offline DM Main menu, refer to "Using the Offline Diagnostic Monitor Menu" in this chapter. For information on configuring an IP address and subnet mask using CLI commands, refer to the following sections.
Note You must reboot the CSS for the IP address to take effect.
Configuring an IP Address
To configure an IP address for the CSS Ethernet Management port, use the ip address option in boot mode. This command does not have a no version. To change the IP address, reissue the ip address command and enter the new IP address. The CSS does not accept an all zero IP address.
For example:
(config-boot)# ip address 172.3.6.58
Note You must reboot the CSS for the new IP address to take effect.
Caution The Ethernet Management port IP address must be a different subnet than any other CSS VLAN circuit IP subnet. If you do not make the Ethernet Management port IP address unique, you will not be able to access the port.
Configuring a Subnet Mask
To configure the CSS subnet mask, use the subnet mask option in boot mode. For example, enter:
(config-boot)# subnet mask 255.255.255.0
To remove the configured subnet mask, enter:
(config-boot)# no subnet mask
Configuring an IP Route
In order to establish IP connectivity to the CSS, a static IP route is required to connect the CSS to next hop router. A static route consists of a destination network address and mask and the next hop to reach the destination. You can also specify a default static route (using 0.0.0.0 as the destination network address and a valid next hop address) to direct frames for which no other destination is listed in the routing table. Default static routes are useful for forwarding otherwise unrouteable packets by the CSS.
When you configure a static IP route, the CSS periodically polls the next hop router with an internal ICMP keepalive service to ensure the router is functioning properly. If the router fails, the CSS removes any entries from the routing table that point to the failed router and stops sending traffic to the failed router. When the router recovers, the CSS:
•Becomes aware of the router
•Re-enters applicable routes into the routing table
To configure an IP route, use the ip route command and specify either an:
•IP address and a subnet mask prefix - For example, 192.168.1.0/24
or
•IP address and a subnet mask - For example, 192.168.1.0 255.255.255.0
The syntax for the ip route command to configure a default IP route is:
ip route IP address subnet mask IP address2
For example, enter:
(config)# ip route 0.0.0.0/0 192.168.3.123
The variables are:
•ip_address - The destination network address. Enter the IP address in dotted-decimal notation (for example, 192.168.11.1).
•subnet_mask - The IP subnet mask. Enter the mask as either:
–A prefix length in CIDR bitcount notation (for example, /24). Do not enter a space to separate the IP address from the prefix length.
–An IP address in dotted-decimal notation (for example, 255.255.255.0).
•ip_address2 - The next hop address for the route. Enter the IP address in dotted-decimal notation (for example, 192.168.11.1).
For complete information on configuring IP routes, refer to <Xref_Color>Chapter 3, Configuring CSS Network Protocols.
Configuring Date, Time, and Time Zone
To set the date, time, or time zone, use clock command. When you enter this command, the CSS displays the current date and time.
Note The clock command does not allow backspacing. If you enter the wrong date, time, or time zone, reenter the command with the new information.
To set the date, enter the clock date command. When you enter this command, a prompt appears and shows the current date in the format you must use to enter the new date. Enter the month, day, and year as integers with dash characters separating them. For example, enter June 15th 2001 as 06-15-2001.
Enter the new information in the format mm-dd-yy as shown:
Enter date: [10-03-00] 10-04-00
To set the time, enter the clock time command. This command sets the time in military-time (24-hour) format. When you enter this command, a prompt appears and shows the current time in the format you must use to enter the new time. Enter the hour, minutes, and seconds as integers, separated by colons.
Enter the new time in the format hh:mm:ss as shown:
Enter time: [15:12:38] 16:12:38
To specify a time zone for the CSS, which synchronizes the CSS system clock with an SNTP server, enter the clock timezone command. The time stored in the CSS is the local time. The Universal Time Coordinated (UTC, also know as Greenwich Mean Time) time is calculated by offsetting the time zone from the local time. You can apply a negative offset to the UTC (for example, -05:-23:+00) or a positive offset to the UTC (for example, +12:+00:+00).
Use the no form of the clock timezone command to reset the time zone information to 00:00:00, and also sets the clock to the new time without the time zone offset.
Note The use of the clock timezone command assumes that you are using the CSS with an SNTP server to synchronize the CSS system UTC time to that of a designated SNTP server. Without a configured SNTP server, the time zone information is not used. Refer to "Synchronizing the CSS with an SNTP Server" later in this chapter for details.
The syntax for the clock timezone command is:
clock timezone name hours hours {before-UTC|after-UTC} {minute
minutes {before-UTC|after-UTC}
The options and variables are:
•timezone name - The name of the time zone. Enter a name with a maximum of 32 characters and no spaces.
•hours hours - Sets the hours offset for the time zone. Enter a number from 0 to 12. This option is used in conjunction with the before-UTC option or after-UTC option to set the offset to either a positive or negative number.
•before-UTC - Sets the offset for Universal Time Coordinated (UTC) as a negative number. For example, if the hour offset is 12, before-UTC sets it to -12.
•after-UTC - Sets the offset for UTC as a positive number. This is the default offset.
•minute minutes - Sets the minutes offset for the time zone. Enter a number from 0 to 59. This option is used in conjunction with the before-UTC option or after-UTC option to set the offset to either a positive or negative number.
For example, to enter the new time zone for Eastern Standard Time (EST) with a -3 hour offset:
# clock timezone EST hours 3 before-UTC
To set the time zone offset back to 00:00:00 (and also set the clock to the new time without the time zone offset):
To display the current date and time, enter the show clock command:
Table 1-2 describes the fields in the show clock output.
Table 1-2 Field Descriptions for the show clock Command
Field
|
Description
|
Date
|
The configured date in the format of month, day, and year. For example, 06-15-2001 is June 15th 2001.
If you use the date european-date command, the format is day, month, and year. For example, the date June 15th 2001 is displayed as 15-06-2001.
|
Time
|
The configured time in the format of hour, minute, and second, for example 16:23:45.
Note If you configure an SNTP server, the show clock command displays the time adjusted with the time zone offset. The show clock command displays the UTC time from the SNTP server. If you configure a timezone, the show clock command displays the time adjusted with the timezone offset. For example, if the UTC time from the server is 16:30:43 and you configure a timezone negative offset of 5 hours and 30 minutes (-05:-30:+00), the displayed time becomes 11:00:43.
|
Timezone
|
The configured time zone offset from an SNTP server. All zeros (00:00:00) indicate that no offset was configured for the time zone. A negative symbol (-) indicates a negative offset to the UTC (for example, -05:-23:+00). A positive symbol (+) indicates a positive offset to the UTC (for example, +12:+00:+00).
|
Configuring European Date
Use the date european-date command to enable the clock date command to accept date input in the format of day, month, and year.
For example,
# date european-date 10/4/00
To reset the format for the clock date command to its default of month, day and year, enter:
Synchronizing the CSS with an SNTP Server
Use the sntp command to configure the SNTP (Simple Network Time Protocol) on the CSS. Use SNTP when you need to synchronize computer system clocks on the Internet to that of a designated SNTP server. SNTP is a simplified, client-only version of the Network Time Protocol (NTP) that enables the CSS time-of-day to be synchronized with any SNTP server.
Accurate time-of-day is provided by synchronizing to the Universal Time Coordinated (UTC) (also know as Greenwich Mean Time), which provides time within 100 milliseconds of the accurate time. You can configure information about the local time zone so the time is displayed correctly relative to the local time zone. The CSS can only receive the time from a single SNTP server (in unicast mode), and it cannot be used to provide time services to other devices.
Note Before you synchronize the CSS with an SNTP server, make sure you configure the proper time zone for the CSS (for example, to EST). Also make sure that the time difference between the CSS internal clock and the SNTP server clock is less than 24 hours. Otherwise, the CSS will not synchronize its clock with the SNTP server. To configure the time on the CSS, see "Configuring Date, Time, and Time Zone" earlier in this chapter for details.
For detailed information on configuring the SNTP server, consult the documentation provided with the server.
The options for this global configuration mode command are:
•sntp server - Specify the SNTP server.
•sntp poll-interval - Specify the poll interval for SNTP request messages.
Configuring the SNTP Server
Use the sntp server command to specify the SNTP server. The syntax for this command is:
sntp server ip_address {version number}
The options and variables are:
•server ip_address - The IP address for the SNTP server. Enter an IP address in dotted-decimal notation (for example, 192.168.1.0).
•version number - The version number of the SNTP server. Enter a version number between 1 and 4. The default is 1.
For example, to configure an SNTP server (running version number 3), enter:
(config)# sntp server 192.168.19.21 version 3
To remove the specified SNTP server, enter:
Configuring the SNTP Poll-Interval
Use the sntp poll-interval command to specify the poll interval for SNTP request messages. The poll interval is the time (in seconds) between successive SNTP request messages to the server. Continuous polling is critical for the CSS to obtain time from the SNTP server and ensure that the local time stays adjusted with the "real time" of the server. The valid entries are 16 to 16284 seconds. The default is 64 seconds.
For example, to specify an SNTP poll-interval of 90 seconds, enter:
(config)# sntp poll-interval 90
To return the SNTP poll-interval to its default setting of 64 seconds, enter:
(config)# no sntp poll-interval
Showing SNTP Configuration Information
To display the Simple Network Time Protocol (SNTP) configuration information on the CSS, enter the show sntp global command:
(config)# show sntp global
Table 1-3 describes the fields in the show sntp global output.
Table 1-3 Field Descriptions for the show sntp global Command
Field
|
Description
|
Server Address
|
The IP address for the SNTP server.
|
Version
|
The version number of the server. The default is 1.
|
Poll Interval
|
The time in seconds between SNTP request messages. The range is 16 to 16284. The default is 64.
|
TimeSinceLastUpdate
|
The time in seconds since the last server reply.
|
Server Status
|
The operating status of the SNTP server, UP or DOWN.
|
Configuring an FTP Record
Use the ftp-record command to create a File Transfer Protocol (FTP) record file to use when accessing an FTP server from the CSS. The syntax for this global configuration mode command is:
ftp-record ftp_record ipaddress_or_hostname username ["password|des-password des_password|encrypted-password encrypted_password] {base_directory}
The variables are:
•ftp_record - The name for the FTP record file. Enter an unquoted text string with no spaces and a maximum length of 16 characters.
•ip_address or hostname - The IP address or host name of the FTP server you want to access. Enter an IP address in dotted-decimal notation (for example, 192.168.11.1) or a mnemonic host name (for example, myhost.mydomain.com).
•username - A valid login username on the FTP server. Enter a case-sensitive unquoted text string with no spaces and a maximum length 16 characters.
•password - The password for the valid login username on the FTP server. Enter a case-sensitive quoted text string with no spaces and a maximum length of 16 characters.
•des_password - The Data Encryption Standard (DES) encrypted password for the valid login username on the FTP server. Enter a case-sensitive unquoted text string with no spaces and a maximum length of 64 characters.
•encrypted_password - The encrypted password for the valid login username on the FTP server. Enter a case-sensitive unquoted text string with no spaces and a maximum length of 16 characters.
•base_directory - An optional base directory when using this record. Enter the base directory name as a case-sensitive unquoted text string with no spaces and a maximum length of 64 characters.
The config-path and base directory path in the ftp-record associated with a network boot must not contain a pathname that collides with a non-network driver name (for example, c: or host:).
For example (using an encrypted password):
# ftp-record arrowrecord 192.168.19.21 bobo password "secret"
/outgoing
To delete the FTP record arrowrecord from the CSS, enter:
# no ftp-record arrowrecord
Copying Files from an FTP Server
Use the copy ftp command to copy files from an FTP server to the CSS. Before using this command, you must use the (config) ftp-record command to create an FTP record file containing the FTP server IP address, username, and password.
The options for this command are:
•copy ftp ftp_record filename boot-image - Copy a file from an FTP server to the CSS for use as the ArrowPoint Distribution Image (ADI). The file you copy to the CSS must be an ADI. Otherwise, the CSS rejects it.
•copy ftp ftp_record filename script script_filename - Copy a file from an FTP server to the script directory.
•copy ftp ftp_record filename startup-config - Copy a file from an FTP server to the startup configuration.
Rebooting the CSS
Use the reboot command to reboot the CSS. The syntax and option for this boot mode command are:
•reboot - Reboots the CSS
•reboot diags - Reboots the CSS and runs diagnostics
For example, to reboot the CSS and run diagnostics, enter:
(config-boot)# reboot diags
Shutting Down the CSS
Use the shutdown command in boot mode to shut down the CSS. This command shuts down all CSS processes so that you can power cycle the unit safely. For example:
Using the Offline Diagnostic Monitor Menu
During the boot process, the CSS enables you to access the Offline Diagnostic Monitor (Offline DM) menu. The Offline DM Main menu allows you to:
•Set the boot configuration:
–Configure a primary and secondary location from which the CSS accesses the boot image
–Configure an IP address for the CSS
–Configure a subnet mask
•Show the boot configuration
•Select Advanced Options to:
–Delete a software version from the disk
–Set a password for the Offline DM Main menu
–Set an administrative username and password
–Reformat the disk and perform a check disk
•Reboot the system
Accessing the Offline Diagnostic Monitor Main Menu
The CSS pauses the boot process for 5 seconds to enable you to press any character after the prompt and display the Offline Diagnostic Monitor Main menu.
To access the Offline Diagnostic Monitor Main menu:
1. Connect and configure a console to the CSS 11800 SCM console port, or the CSS 11050 or CSS 11150 front panel. Configure the console to the following default values: 9600 baud, no parity, 8 data bits, 1 stop bit, and flow control set to None.
2. Power on the CSS. After the CSS begins to boot (approximately 15 seconds), it displays the following message:
Press any key to access the Offline Diagnostic Monitor menu
At this point in the boot sequence, you may either:
•Take no action and let the CSS continue booting automatically with the default boot configuration
•Press any key to halt the boot process and display the Offline DM Main menu
3. If you choose to access the Offline DM Main menu, press any key before the 5-second window elapses.
The Offline DM Main menu is displayed as shown below. If 5 seconds elapse before you press a key, power down the CSS and then power it up again.
CSSxxx00 Offline Diagnostic Monitor, Version x.x
Enter the number of a menu selection:
1* Set Boot Configuration
2. Show Boot Configuration
An asterisk (*) next to a menu option indicates that the option contains a submenu.
Table 1-4 describes each menu item.
Table 1-4 Offline Diagnostic Monitor Menu Options
Menu Option
|
Enables you to....
|
1* Set Boot Configuration
|
1. Set Primary Boot Configuration
2. Set Secondary Boot Configuration
3. Set IP Address, and Subnet Mask
r. Return to previous menu
|
2. Show Boot Configuration
|
Display boot configurations (including primary and secondary boot configurations, records, and IP information).
|
3* Advanced Options
|
1. Delete a software version
2. Security Options
3. Disk Options
r. Return to previous menu
|
4. Reboot System
|
Reboot the CSS. The CSS displays the following message before rebooting:
Are you sure you want to reboot? (Y/N)
Enter:
•Y to reboot the CSS
•N to continue using the Offline DM Main menu
|
Using the Boot Configuration Menu
The flowchart in illustrates how the CSS uses the Boot Configuration information to complete the boot process.
Figure 1-2 Boot Configuration Flowchart
The Boot Configuration menu enables you to perform the following tasks as described in Table 1-5.
Table 1-5 Boot Configuration Options
Menu Option
|
Enables you to....
|
1. Set Primary Boot Configuration
|
Specify the primary location (Network, FTP, Disk, or Clear) from which the CSS accesses the boot image. The default location is Disk.
|
2. Set Secondary Boot Configuration
|
Specify the secondary location (Network, FTP, Disk, or Clear) from which the CSS accesses the boot image. The default location is Clear.
|
3. Set IP Address and subnet mask
|
Configure an IP address for the Ethernet Management port, and configure a subnet mask.
|
r. Return to previous menu
|
Display the Offline DM main menu.
|
The Boot Configuration menu is displayed as shown below.
Enter the number of a menu selection:
1. Set Primary Boot Configuration
2. Set Secondary Boot Configuration
3. Set IP Address and Subnet Mask
r Return to previous menu
Setting Primary Boot Configuration
The information you provide for the Primary Boot Configuration specifies the location from which the CSS accesses the primary boot image upon system reboot or when you download new software. When you select Set Primary Boot Configuration from the Boot Configuration menu, the CSS displays the following information. If you have previously entered information, the CSS displays the existing information and default values in [square brackets].
Configuring PRIMARY Boot Record
Boot via [N]etwork, [F]TP, [D]isk, or [C]lear: [D]
•Boot via Network allows you to boot the CSS via FTP from CSS software on a network-mounted file system on a remote system
•Boot via FTP allows you to download an ADI file containing CSS software that you want to install on the CSS drive
•Boot via Disk allows you to boot the CSS from software currently on the CSS drive
•Boot via Clear instructs the CSS to boot the CSS from the secondary boot record
Refer to the following sections for a description of each Primary Boot Record option:
•Specifying a Network-Mounted File System as the Primary Boot Record
•Specifying FTP as the Primary Boot Record
•Specifying Disk as the Primary Boot Record
•Specifying Clear as the Primary Boot Record
Specifying a Network-Mounted File System as the Primary Boot Record
Set the Primary Boot Record to Network when you want to boot the system from a network-mounted file system on a remote system (such as a PC or UNIX workstation) via FTP. Instead of the CSS disk, the network file system contains the CSS software. The CSS boots from this file system and loads the configuration into memory. Perform a network boot when:
•You want multiple CSSs to use the same boot image while keeping their own configuration information. You provide an alternate path for the location of the configuration information. However this information must exist on the same network file system with the boot image.
Note When using an alternate configuration path, make sure that the path leads to a directory containing the script, log, and info subdirectories. These subdirectories must contain the files in the corresponding subdirectories in the boot image. Create these subdirectories. Then copy the files from the boot image.
•The CSS has a disk failure. A network boot allows the CSS to boot independently from its disk and to load the configuration into memory.
Before the CSS can boot from the network:
•Locate the remote system on the network where you will copy the CSS software.
–Make sure that the CSS can access the system via FTP.
–Copy the CSS software zip file from the CSS CD onto the system disk.
–Create a directory and unzip the file into it. This directory will contain all of the boot files and directories.
•On the CSS, create an FTP record to the directory containing the CSS software on the network drive.
•Make sure that you cable the following port on the CSS to the network:
–CSS 11800 SCM 10/100 Mbps-Ethernet Management port
–CSS 11050 or CSS 11150 rear panel 10/100-Mbps Ethernet Management port
•Be aware of the following network boot restrictions:
–A network boot is not supported on UNIX workstations.
–The War-FTP daemon is not supported for network-booting the system software.
When you select Network, the CSS prompts you for the FTP kernel information.
1. Enter the FTP kernel path information. This path is the FTP daemon addressable location where the boot image has been unpacked. You must also include its IP address, and the username and password to access it. For example:
Enter the FTP Kernel path:[] k:/ap0500002
Enter FTP Server IP address:[] 10.3.6.58
Enter FTP Server authentication username:[] mandy
Enter FTP Server authentication password:[] fred
2. If the configuration information is not in the same directory as the boot image, enter an alternate path to the configuration files, including the startup-config and script files.
Note The CSS must be able to access the configuration path through the previously configured FTP server IP address, login username, and password.
For example:
Enter the FTP Config Path? [] k:/atlanta-config/
Press <Enter> to continue...
3. Press Enter to display the Boot Configuration menu.
4. Enter r to display the Offline DM Main menu.
5. Select Reboot the System to reboot the CSS.
When the CSS completes the current boot process, it:
•Accesses the network file system containing the boot image
•Boots the CSS using the boot image you specified
Specifying FTP as the Primary Boot Record
Set the Primary Boot Record to FTP when you want to upgrade the CSS software on the CSS disk. The CSS accesses the ADI or GZIP file containing the CSS software from an FTP server, copies it to the IDM, and unpacks it. Then the CSS boots from the hard drive.
Make sure that you cable the following port on the CSS to the network:
•CSS 11800 SCM 10/100 Mbps-Ethernet Management port
•CSS 11050 or 11150 rear panel 10/100-Mbps Ethernet Management port
When you select FTP, the CSS prompts you for the boot image filename and FTP information.
1. If required, enter a valid FTP pathname. For example:
Enter the boot image filename: /ftpimages/ap0500002
Enter FTP Server IP address: 10.3.6.58
Enter FTP Server authentication user name: mandy
Enter FTP Server authentication password: fred
The CSS queries if you want to access the boot image directly from the disk at the next reboot (that is, the next time you reboot the CSS after completing this current boot process).
Boot from Disk at next reboot? y/n
Press <Enter> to continue...
2. Enter either:
•y to copy the boot image from the FTP server to the disk. The CSS accesses the boot image directly from the disk at next reboot. The CSS also changes the information in the Primary Boot Record to Disk.
•n to FTP the boot image from the FTP server at next reboot.
3. Press Enter to display the Boot Configuration menu.
4. Enter r to display the Offline DM Main menu.
5. Select Reboot the System to reboot the CSS.
When the CSS completes the current boot process, it:
•Accesses the ADI file from the FTP server and unpacks (uncompresses) it
•Boots the CSS using the boot image you specified
Specifying Disk as the Primary Boot Record
When you select Disk as the Primary Boot Record, the CSS displays all boot image versions that reside on the disk. For example:
1. At the prompt, enter the boot image filename you wish to use.
Enter the boot image filename: ap0500002
2. Press Enter to display the Boot Configuration menu.
Press <Enter> to continue...
3. Press r to display the Offline DM Main menu.
4. Select Reboot the System to reboot the CSS. Upon reboot, the CSS boots up using the boot image you specified.
Specifying Clear as the Primary Boot Record
To use the Secondary Boot Record information instead of the Primary Boot Record to boot the CSS:
1. Select Clear as the Primary Boot Record.
2. Press Enter to display the Boot Configuration menu.
3. Press r to display the Offline DM Main menu.
4. Select Reboot the System to reboot the CSS. Upon reboot, the CSS uses the Secondary Boot Record.
Setting Secondary Boot Configuration
The information you provide for the Secondary Boot Configuration specifies the location from which the CSS accesses the boot image if you specified Clear as a Primary Boot Record or the Primary Boot Record fails.
Once you select Set Secondary Boot Configuration from the Boot Configuration menu, the CSS displays the following information. If you have previously entered information, the CSS displays the existing information and default values in
[square brackets].
Configuring SECONDARY Boot Record
Boot via [N]etwork, [F]TP, [D]isk, or [C]lear: [D]
•Boot via Network allows you to boot the CSS via FTP from CSS software on a network-mounted file system on a remote system
•Boot via FTP allows you to download an ADI file containing CSS software that you want to install on the CSS disk
•Boot via Disk allows you to boot the CSS from software currently on the CSS disk
•Boot via Clear instructs the CSS to boot the CSS from the primary boot record
Refer to the following sections for a description of each Primary Boot Record option:
•Specifying a Network-Mounted File System as the Secondary Boot Record
•Specifying FTP as the Secondary Boot Record
•Specifying Disk as the Secondary Boot Record
•Specifying Clear as the Secondary Boot Record
Specifying a Network-Mounted File System as the Secondary Boot Record
Set the Secondary Boot Record to Network when you want to boot the system from a network-mounted file system on a remote system via FTP. Instead of the CSS disk, the network file system contains the CSS software. The CSS boots from this file system and loads the configuration into memory. Perform a network boot when:
•You want multiple CSSs to use the same boot image while keeping their own configuration information. You provide an alternate path for the location of the configuration information. However this information must exist on the same network file system with the boot image.
Note When using an alternate configuration path, make sure that the path leads to a directory containing the script, log, and info subdirectories. These subdirectories must contain the files in the corresponding subdirectories in the boot image. Create these subdirectories. Then copy the files from the boot image.
•The CSS has a disk failure. A network boot allows the CSS to boot independently from its disk and to load the configuration into memory.
Before the CSS can boot from the network:
•Locate the remote system (such as a PC or UNIX workstation) on the network where you will copy the CSS software.
–Make sure that the CSS can access the system via FTP.
–Copy the CSS software zip file from the CSS CD onto the system disk.
–Create a directory and unzip the file into it. This directory will contain all of the boot files and directories.
•On the CSS, create an FTP record to the directory containing the CSS software on the network drive.
•Make sure that you cable the following port on the CSS to the network:
–CSS 11800 SCM 10/100 Mbps-Ethernet Management port
–CSS 11050 or CSS 11150 rear panel 10/100-Mbps Ethernet Management port
•Be aware of the following network boot restrictions:
–A network boot is not supported on UNIX workstations.
–The War-FTP daemon is not supported for network-booting the system software.
When you select Network, the CSS prompts you for the FTP kernel information.
1. Enter the FTP kernel path information. This path is the FTP daemon addressable location where the boot image has been unpacked. You must also include its IP address, and the username and password to access it. For example:
Enter the FTP Kernel path:[] k:/ap0500002
Enter FTP Server IP address:[] 10.3.6.58
Enter FTP Server authentication username:[] mandy
Enter FTP Server authentication password:[] fred
2. If the configuration information is not in the same directory as the boot image, enter an alternate path to the configuration files, including the startup-config and script files.
Note The CSS must be able to access the configuration path through the previously configured FTP server IP address, login username, and password.
For example:
Enter the FTP Config Path? [] k:/atlanta-config/
Press <Enter> to continue...
3. Press Enter to display the Boot Configuration menu.
4. Enter r to display the Offline DM Main menu.
5. Select Reboot the System to reboot the CSS.
When the CSS completes the current boot process, it:
•Accesses the network file system containing the boot image
•Boots the CSS using the boot image you specified
Specifying FTP as the Secondary Boot Record
Set the Secondary Boot Record value to FTP when you want to upgrade the CSS software on the CSS disk. The CSS accesses the ADI or GZIP file containing the CSS software from an FTP server, copies it to the IDM, and unpacks it. Then the CSS boots from the hard drive.
Make sure that you cable the following port on the CSS to the network:
•CSS 11800 SCM 10/100 Mbps-Ethernet Management port
•CSS 11050 or CSS 11150 rear panel 10/100-Mbps Ethernet Management port
When you select FTP, the CSS prompts you for the boot image filename and FTP information.
1. If required, enter a valid FTP pathname. For example:
Enter the boot image filename: /ftpimages/ap0500002
Enter FTP Server IP address: 10.3.6.58
Enter FTP Server authentication user name: mandy
Enter FTP Server authentication password: fred
The CSS queries if you want to access the boot image directly from the disk at the next reboot (that is, the next time you reboot the CSS after completing this current boot process).
Boot from Disk at next reboot? y/n
2. Enter either:
•y to copy the boot image from the FTP server to the disk. The CSS accesses the boot image directly from the disk at next reboot. The CSS also changes the information in the Secondary Boot Record to Disk.
•n to FTP the boot image from the FTP server at next reboot.
3. Press Enter to display the Boot Configuration menu.
Press <Enter> to continue...
4. Enter r to display the Offline DM Main menu.
5. Select Reboot the System to reboot the CSS.
When the CSS uses the Secondary Boot Record on reboot, it:
•Accesses the ADI file from the FTP server and unpacks (uncompresses) the file
•Boots the CSS using the boot image you specified
Specifying Disk as the Secondary Boot Record
When you select Disk as the Secondary Boot Record, the CSS displays all boot image versions that reside on the disk and prompts you to enter a boot image.
1. Enter a boot image filename.
Boot via [N]etwork, [F]TP, [D]isk, or [C]lear: [D]
Enter the boot image filename: ap0410008
2. Press Enter to display the Boot Configuration menu.
Press <Enter> to continue...
3. Enter r to display the Offline DM Main menu.
4. Select Reboot the System to reboot the CSS. Upon reboot, the CSS boots up using the boot image you specified.
Specifying Clear as the Secondary Boot Record
If you do not wish to specify a Secondary Boot Record:
1. Select Clear as the Secondary Boot Record.
2. Press Enter to display the Boot Configuration menu.
3. Enter r to display the Offline DM Main menu.
4. Select Reboot the System to reboot the CSS. Upon reboot, the CSS uses the Primary Boot Record.
Setting IP Address, and Subnet Mask
When you select Set IP Address and Subnet Mask from the Boot Configuration menu, the CSS prompts you to:
1. Enter an IP address for the Ethernet Management port. The CSS does not accept an all zero IP address. If you enter an all zero IP address, the CSS repeats the prompt until you enter an IP address.
Note The Ethernet Management port IP address must be a different subnet than any other CSS VLAN circuit IP subnet. If you do not make the Ethernet Management port IP address unique, you will not be able to access the port.
Enter IP Address: [0.0.0.0] 10.3.6.58
2. Enter a subnet mask.
Enter Subnet Mask: [0.0.0.0] 255.0.0.0
3. Press Enter to display the Boot Configuration menu.
Press <Enter> to continue...
4. Enter r to display the Offline DM Main menu.
5. Select Reboot the System to reboot the CSS.
Showing the Boot Configuration
When you select Show Boot Configuration from the Offline DM Main menu, the CSS displays the following boot information. Note that the Miscellaneous information only displays if you set password-protection on the Offline DM Main menu.
***************** Miscellaneous ********************
Offline Diagnostic Monitor menu is password-protected
***************** IP/MAC Information ***************
MAC Address 00-10-58-00-12-ca
***************** PRIMARY **************************
***************** SECONDARY ************************
1. Press Enter to display the Offline DM Main menu.
Press <Enter> to continue...
2. Enter option 3 to reboot the system. The following reboot confirmation is displayed:
Are you sure you want to reboot? (y/n)
3. Enter either:
•y to reboot
•n to continue using the Offline DM Main menu
Using the Advanced Options
The CSS hard disk enables you to store four versions of software (including the version you are currently running) and the flash disk allows you to store two versions of software. If you are storing the maximum number of software versions and wish to download a new version to the disk, you must delete a version before the CSS allows the download to begin.
When you select Advanced Options from the Offline DM Main menu, the CSS displays the Advanced Options menu:
A D V A N C E D O P T I O N S
Enter the number of a menu selection:
1. Delete a Software Version
r. Return to previous menu
Deleting a Software Version
To delete a software version from the disk:
1. Enter option 1 to display the software versions currently stored on the disk. The CSS prompts you to enter the software version to delete. For example:
Enter the software version to delete: ap0410008
2. Press Enter to redisplay the Advanced Options menu.
Press <Enter> to continue...
3. Enter r to display the Offline DM main menu.
4. Select Reboot the System to reboot the CSS.
Using the Security Options
The Security Options menu enables you to:
•Set Password Protection on the Offline Diagnostic Monitor menu
•Set Administrative Username and Password
The Security Options menu is shown below:
S E C U R I T Y O P T I O N S
Enter the number of a menu selection:
1. Set Password Protection for Offline Diagnostic Monitor menu
2. Set Administrative Username and Password
r. Return to previous menu
Setting Password Protection
The CSS enables you to password-protect the Offline DM Main menu to protect it against unauthorized access. The default is disabled; no password is required to access the Offline DM Main menu.
Caution Use care when password-protecting the Offline DM Main menu and ensure that you write down the new password. If you lose the new password, it cannot be recovered and you will be unable to access the Offline DM Main menu. The only solution, at that point, would be to contact the Cisco Technical Assistance Center (TAC) at 1-800-553-2447 or 1-408-526-7209. You can also email TAC at tac@cisco.com.
To access the Offline DM Main menu password protection option:
1. Enter option 1 from the Security Options menu.
Password protect Offline Diagnostic Monitor menu (yes,no):
The administrative username and password are required to access
the Offline Diagnostic Monitor menu.
•When you enter yes, the CSS prompts you to enter a username and password when you access the Offline DM Main menu.
•When you enter no, the CSS does not prompt for a username and password when you access the Offline DM Main menu.
2. Press Enter to redisplay the Security Options menu.
Press <Enter> to continue...
3. Enter r to return to the Advanced Options menu.
4. Enter r to return to the Offline DM Main menu.
5. Enter either:
•Option 4 to reboot the CSS
•Another option to continue using the Offline DM Main menu
Setting an Administrative Username and Password
For security reasons, you can change the administrative username and password through either the Offline DM Main menu or the username-offdm command. Unlike other usernames and passwords, the CSS saves the administrative username and password in nonvolatile RAM (NVRAM). Anytime you reboot the CSS, it reads them from NVRAM and reinserts them into the user database.
Note You cannot permanently delete an administrative username and password. If you delete them by using the no username command, they are removed from use until you reboot the CSS. When you reboot the CSS, it restores the username and password from NVRAM.
To configure an administrative username and password through the Offline DM Main menu:
1. Enter option 2 from the Security Options menu.
2. Enter a username. The CSS prompts for this username when you log in. The CSS also prompts for this username and password if you set password-protection on the Offline DM Main menu.
Enter [administrator] username (minimum 4 characters):
3. Enter a password. Note that the CSS does not display passwords.
Enter [administrator] password:
4. Re-enter the password for confirmation.
Confirm [administrator] password:
The CSS redisplays the Security Options menu.
5. Enter r to return to the Advanced Options menu.
6. Enter r to return to the Offline DM Main menu.
7. Enter either:
•Option 4 to reboot the CSS
•Another option to continue using the Offline DM Main menu
Using the Disk Options
The Disk Options menu enables you to:
•Format disk - Enables you to reformat the disk. This option permanently erases all data on the disk. If you wish to retain the startup-config, ensure that you move it off the CSS before reformatting the disk. Also make sure that you have a copy of the CSS software ADI file to reinstall on the CSS.
•Check disk - Enables you to run a quick check disk or a complete check disk.
•Check disk disable - Allows you to disable running check disk at boot time or enable it again. By default, check disk is enabled.
The Disk Options menu is shown below:
Enter the number of a menu selection:
r. Return to previous menu
Reformatting the Disk
If the CSS detects unrecoverable errors when performing a check disk, you must reformat the disk. Reformatting the disk erases all data from the disk permanently.
To reformat the disk:
1. Enter option 1 from the Disk Options menu.
Formatting the disk results in all disk data being permanently
erased.
Are you sure you want to continue? (yes,no):
Enter either:
•yes to reformat the disk.
•no to abort the reformat function. If the disk has unrecoverable errors and you do not reformat it, be aware that the file system may be corrupt and functionality is compromised.
2. The CSS queries whether you want to perform a quick format or a complete format.
Enter either:
•yes to reformat the disk using the quick format (does not perform cluster verification). Only use the quick format when you are certain of the disk integrity.
•no to reformat the disk including cluster verification.
After the CSS reformats the disk, it displays:
Operation completed successfully.
3. Enter r to return to the Advanced Options menu.
4. Enter r to return to the Offline DM Main menu.
Because the disk is empty, you must configure a primary boot record to instruct the CSS where to locate the new ADI file containing the CSS software.
5. Enter option 1 to set the primary boot configuration. Refer to "Setting Primary Boot Configuration" in this chapter.
If you do not set the primary boot configuration before booting the CSS, the boot process halts at the prompt:
Press any key to access the Offline Diagnostic Monitor menu...
You must enter the Offline DM Main menu to set the primary boot configuration.
Performing a Check Disk
When the CSS boots up, it checks the results of the previous shutdown. If the CSS:
•Does not detect errors, it reports a status of OK and continues the boot process
Reading configuration records...OK
Checking previous shutdown...OK
Initializing the disk...OK
•Detects errors, it returns a status of DIRTY
Reading configuration records...OK
Checking previous shutdown...DIRTY
Initializing the disk...OK
If the CSS reports that the disk is dirty, it has discovered errors on the disk. In this case, the CSS automatically perform a check disk to recover from the errors and maintain the integrity of the disk.
During a check disk, the CSS:
•Detects and recovers from the following error conditions:
–File Allocation Tables (FATs) are out of synchronization
–Sector write truncation revitalization (may occur from a power loss at the time the CSS is writing to the disk)
–Bad cluster identification and mapping in the FAT when reformatting the disk
–Crosslinked FAT entries
–Disk entry validation, name, size, cluster assignment, cluster chaining
–Recovery of lost clusters
•Cannot recover from sector failures within the first 754 sectors (for example, boot, primary/secondary FAT, root directory entries).
The amount of time the CSS requires to perform a check disk is proportional to the number of installed software releases and directories on the disk. The greater the number of installed software releases and directories, the longer it takes to complete the check disk.
To perform a check disk:
1. Enter option 2 from the Disk Options menu.
Choose whether or not you want the CSS to correct errors it detects. Enter either:
•yes to enable the CSS to correct recoverable errors it detects. When the CSS completes check disk, it displays a summary of what was fixed.
•no to prevent the CSS from correcting recoverable errors it detects. The CSS displays a summary of what would have fixed if you had run check disk.
Correct errors if discovered (yes,no):
2. Choose whether you want the CSS to perform a quick check disk or a complete check disk. Enter either:
•yes to instruct the CSS to perform a quick check disk (does not include cluster verification
•no to instruct the CSS to perform a complete check disk (includes cluster verification)
The CSS performs check disk. When completed, it displays:
Operation completed successfully.
Press <Enter> to continue...
3. Enter r to return to the Advanced Options menu.
4. Enter r to return to the Offline DM Main menu.
5. Enter option 4 to reboot the CSS.
Disabling or Enabling Check Disk
By default, the CSS performs a check disk when it boots. The Disk Options menu provides an option that allows you to disable the running of check disk or reenable it. When you select this option, it toggles to disable check disk if it is currently enabled, or to enable check disk if it is currently disabled.
For example, if check disk is currently enabled, to disable it:
1. Enter option 3 from the Disk Options menu.
2. Enter r to return to the Advanced Options menu.
3. Enter r to return to the Offline DM Main menu.
4. Enter option 2 to display the boot configuration.
When check disk is disabled, it displays the following:
****************** Miscellaneous **********************
***************** IP/MAC Information ***************
MAC Address: 00-10-58-00-12-ca
***************** PRIMARY **************************
***************** SECONDARY ************************
Press <Enter> to continue...
If check disk is currently disabled, to reenable it:
1. Enter option 3 from the Disk Options menu.
2. Enter r to return to the Advanced Options menu.
3. Enter r to return to the Offline DM Main menu.
4. Enter option 2 to display the boot configuration.
When check disk is enabled, no state information appears in the Miscellaneous field of the boot configuration:
***************** IP/MAC Information ***************
MAC Address: 00-10-58-00-12-ca
***************** PRIMARY **************************
***************** SECONDARY ************************
Press <Enter> to continue...
Enabling and Disabling Core Dumps
A core dump occurs when the CSS experiences a fatal error. The CSS allows you to enable or disable core dumps. Core dumps are enabled by default.
When the CSS experiences a fatal error and core dumps are enabled, the CSS:
•Writes information about the fatal error to the Core directory of the volume root (for example, c:\core) on either the:
–Hard disk, which can store up to 30 sequentially numbered dump files
–Flash disk, which stores one compressed dump file of 70 MB
•Reboots automatically
Note For a flash disk-based system, if the core dump file is older than 15 minutes, it may be overwritten. If you want to save the core dump file for later examination, archive it to another directory or disk before it is overwritten. For details on using the archive log command, refer to "Archiving a Log File" later in this chapter.
When the CSS experiences a fatal error and core dumps are disabled, the CSS reboots automatically. The CSS does not write information to the hard disk or the flash disk.
Note Core dump information is for Customer Support use only.
To disable core dumps, enter:
To reenable core dumps (the default setting), enter:
To show the CSS dump state, enter:
(config)# show dump-status
Showing Core Dumps
Use the show core command to display the core dump files stored in the Core directory of the volume root (for example, c:\core) on the hard disk or flash disk. This command is available only in SuperUser mode.
For example:
css150_3.50_6.1 JUN 30 10:45:24 130024448
css150_3.50_6.0 JUN 30 17:14:00 130024448
CSS Software Overview
The CSS software contains the files to run the CSS including boot files, directories for archiving and logging files, and MIB information. This software is pre-installed on the CSS conventional hard disk drive or an optional flash disk, a flash memory-based storage device (CSS 11150 and CSS 11800, only).
You can also install the CSS software on a network drive which the CSS can access through FTP. The Content Services Switch Documentation and System Software CD contains the CSS software for the network drive. This software is in ZIP format and must be copied and uncompressed on a network drive. For more information on booting the CSS from a network boot drive, refer to <Xref_Color>Chapter 2, Configuring User Profiles and CSS Parameters.
The CSS software is approximately 20 MB in size. If you have a hard disk-based system, you can install a maximum of four software versions on your CSS. If you have a flash disk-based system (CSS 11150 or CSS 11800), you can install a maximum of two software versions on your CSS.
To display the maximum number of versions allowed on your CSS, use the show installed-software version-limit command. To view all versions installed on the CSS, use the show installed-software command.
The software version format is defined as follows:
From an FTP server, you can view the following directories on the hard disk or flash disk:
•The log directory contains the following log files:
–boot.log - ASCII log of boot process
–boot.bak - Backup of the previous boot log
–sys.log - ASCII log of system events (logging to disk is enabled by default to subsystem all and level info)
–sys.log.prev - Backup of the previous system log file (if any)
•The scripts directory contains default, profile, and sample scripts.
•The core directory contains any core dumps created by the CSS. For information on copying core dumps to an FTP or TFTP server, refer to "Copying Core Dumps to an FTP or TFTP Server" later in this chapter.
•The MIB directory contains MIB files that you can load into SNTP-compliant network management software applications.
Note When you view the CSS software directories installed on a network drive, more directories are listed than those you can view on the hard disk or flash disk. These additional directories are reserved for internal use. Do not manipulate the files in these directories.
The software directory also contains the startup-config file. This is an ASCII file containing commands the CSS executes at startup. This file is created when you:
•Finish using the configuration script.
•Issue the copy running-config startup-config or write memory command. Both commands save configuration changes to the startup-config during a CSS session. The write memory command also archives the startup configuration file to the archive directory on the CSS (similar to the archive startup-config command, as described in "Archiving Files to the Archive Directory" in this chapter).
•Use File Transfer Protocol (FTP) to copy a startup-config file to the CSS.
The archive directory contains the files that you archive from the current software by using the archive command. These files include running-config, startup-config, log files, profile scripts, and scripts you create. You can view a list of archived files by using the show archive ? command.
To restore any archived files to the CSS, use the restore command. For more information on the archive and restore commands, refer to the "Archiving Files to the Archive Directory" and "Restoring Files from the Archive Directory" in this chapter.
To view general information about the CSS disk, use the show disk command. Table 1-6 describes the fields in the show disk output.
Table 1-6 Field Descriptions for the show disk Command
Field
|
Description
|
Disk Size
|
The total size of the disk in megabytes.
Note The CSS flash disk has a disk size of 350 MB, however 130 MB is reserved for the generation of dump files. This dump partition is not available to the CSS file system, and is not included in the Disk Size field. The CSS hard disk is allocated a similar but larger dump partition.
|
Disk Free
|
The available disk space in megabytes.
|
Bad Cluster Count
|
The number of bad clusters on the disk.
|
File Count
|
The number of files on the disk.
|
Directory Count
|
The number of directories on the disk.
|
Using the Running-Config and Startup-Config
When you make configuration changes to the CSS, the changes are placed in a virtual running-configuration file (running-config). Before you log out or reboot the CSS, you must copy the running-config to the startup-config to save configuration changes and have the CSS use this configuration on subsequent reboots.
To save the running-config to the CSS disk, use one of the following commands:
•copy running-config startup-config - Copies the running-config to the startup-config. The CSS uses the startup-config upon reboot. If you do not copy the running-config to the startup-config before you reboot, changes to the running-config are lost.
•write memory - Copies the running-config to the startup-config (similar to the copy running-config startup-config command). In addition, the write memory command also archives the startup configuration file to the archive directory on the CSS (similar to the archive startup-config command, as described in "Archiving Files to the Archive Directory" in this chapter).
•copy startup-config running-config - Copies the startup-config to the running-config and merges with the running-config.
The copy running-config command can also copy the running configuration to an FTP or TFTP server. The options for this command are:
•copy running-config ftp ftp_record filename - Copy the running configuration to an FTP server.
•copy running-config tftp IP address - Copy the running configuration to a TFTP server using the TFTP server IP address.
•copy running-config tftp hostname - Copy the running configuration to a TFTP server using the TFTP server hostname.
The copy startup-config command can copy the startup configuration to an FTP or TFTP server. The options for this command are:
•copy startup-config ftp ftp_record filename - Copy the startup configuration to an FTP server.
•copy startup-config tftp IP address - Copy the startup configuration to a TFTP server using the TFTP server IP address.
•copy startup-config tftp hostname - Copy the startup configuration to a TFTP server using the TFTP server hostname.
Clearing the Running-Config and the Startup-Config
To reset the running-config to the default configuration, use the clear running-config command in SuperUser mode. This command takes effect immediately. Note that the clear running-config command resets all configurations to their defaults.
Caution The execution of the
clear running-config command is restricted to CSS users who are identified as either an administrator or a technician.
For example:
To reset the startup-config to the default configuration, use the clear startup-config command in SuperUser mode. This command takes effect upon the next reboot. For example:
Showing the Running-Config
To display the CSS running configuration, use the show running-config command. The CSS does not display default configurations in the running-config. The syntax and options for this command are:
•show running-config - Display all components of the running-config.
•show running-config acl {index number} - Display Access Control List (ACL) information of the running-config. For information about a specific ACL, include its index number.
•show running-config circuit {circuit name} - Display the circuit components of one or all circuits in the running-config.
•show running-config global - Display the global components of the running-config.
•show running-config group {group name} - Display the valid existing group components of the running-config. For information about a specific group, enter the group name as a case-sensitive unquoted text string.
•show running-config header-field-group {name} - Display the valid existing header-field group components of the running-config. For information about a specific group, enter name as a case-sensitive unquoted text string with a maximum length of 16 characters. To see a list of header-field groups, enter show running-config header-field-group ?.
•show running-config interface interface name - Display a specific interface component of the running-config.
–For a CSS 11050 or CSS 11150, enter the interface name in interface-port format (for example, e2)
–For a CSS 11800, enter the interface name in slot/port format (for example, 3/1)
•show running-config interfaces - Display all the interface components of the running-config.
•show running-config keepalive {keepalive name} - Display the existing keepalive components of the running configuration. For information about a specific keepalive, enter keepalive_name as a case-sensitive unquoted text string and a maximum length of 32 characters. To see a list of keepalives, enter show keepalive-summary.
•show running-config owner {owner name} - Display the valid existing owner components of the running-config. For information about a specific owner, enter the owner name as a case-sensitive unquoted text string.
•show running-config service {service name} - Display the components of the running-config for a valid existing service. For information about a specific service, enter the service name as a case-sensitive unquoted text string.
•show running-config urql {urql name} - Display the components of the running-config for existing Uniform Resource Locator Qualifier Lists (URQL). For information about a specific URQL, enter the URQL name as a case-sensitive unquoted text string.
•show running-config dql {dql name} - Display Domain Qualifier List (DQL) information of the running-config. For information about a specific DQL, enter the DQL name as a case-sensitive unquoted text string.
•show running-config eql {eql name} - Display Extension Qualifier List (EQL) information of the running-config. For information about a specific EQL, enter the EQL name as a case-sensitive unquoted text string.
•show running-config nql {name} - Display Network Qualifier List (NQL) information of the running configuration. For information about a specific NQL, enter the NQL name as a case-sensitive unquoted text string.
•show running-config rmon-alarm - Display RMON alarm information of the running configuration.
•show running-config rmon-event - Display RMON event information of the running configuration.
•show running-config rmon-history - Display RMON history information of the running configuration.
An example of a running-config is shown below. Comments are preceded by an exclamation point (!). Note that the CSS does not display default values in the running- or startup-config even if you enter the values manually.
!************************ GLOBAL **********************
ip route 0.0.0.0/0 158.3.7.2
!********************** INTERFACE *********************
!*********************** CIRCUIT **********************
ip address 10.3.6.58 255.255.255.0
ip address 158.3.7.58 255.255.255.0
!*********************** SERVICE **********************
!************************ OWNER ***********************
Showing the Startup-Config
Once you copy the running-config to the startup-config, use the show startup-config command to display the startup-config. The CSS does not display default configurations in the startup-config.
The show startup-config command has two options:
•show startup-config - Display the startup-config
•show startup-config line-numbers - Display the startup-config with line numbers
An example of a startup-config is shown below. Comments are preceded by an exclamation point (!).
# show startup-config line-numbers
1. !Generated MAR 6 18:56:11
3. !********************** CIRCUIT **********************
5. ip address 192.168.2.170 255.255.255.0
6. ip address 192.168.1.108 255.255.255.0
7. !********************** SERVICE **********************
9. ip address 192.168.2.4
12. !*********************** OWNER ***********************
15. vip address 192.168.128.108
20. vip address 192.168.128.108
Creating a Running-Config or Startup-Config Using a Text Editor
If you create a running- or startup-config using a text editor, you must arrange the configuration information in the same order as an automatically created running- or startup-config. The CSS arranges configuration information in the following categories within the running-config and startup-config files:
•Global - Contains configuration information relating to the CSS (for example, default route IP address)
•Interface - Contains physical port and VLAN associations
•Circuit - Contains circuit VLAN IP addresses and subnet masks
•Keepalive - Contains the global keepalive configuration
•Service - Contains service names, IP addresses, and all service configuration information
•EQL - Contains Extension Qualifier List (EQL) configuration
•Owner - Contains owner name, content rule name, and content rules
•Group - Contains source group configurations
•RMON Event - Contains RMON event configurations
•RMON Alarm - Contains RMON alarm configurations
•RMON History - Contains RMON history configurations
•ACL - Contains ArrowPoint Control List (ACL) configurations
•URQL - Contains Uniform Resource Locator Qualifier List configurations (URQL)
Though the CSS organizes configuration information automatically, the order in which you configure the CSS is important because of interdependencies within CSS functionality. Enter configuration commands for features in the same sequence as they appear in the startup-config.
Archiving Files to the Archive Directory
Use the archive command and options to archive files. Archiving is useful when you update software and want to save a script, log, or startup-config file from a previous release of software. The archive directory on the CSS disk stores the archive files. This command is available only in SuperUser mode.
To display the contents of the archive directory, enter show archive ?. Archive files include running- and startup-config files, scripts, and user profiles. This command is available only in SuperUser mode.
Note You must archive your startup-config and scripts before you upgrade the CSS software or these files will be overwritten during the upgrade. Once the upgrade is complete and the CSS has rebooted, use the restore command to copy these files from the archive directory to be used as current startup-config and scripts.
The options for this command are:
•archive log - Archive a log file
•archive running-config - Archive a running configuration
•archive script - Archive a script file
•archive startup-config - Archive the startup configuration file
Archiving a Log File
Use the archive log command to archive a log file. The syntax for this command is:
archive log log_filename {archive_filename}
The variables are:
•log_filename - The filename of the log to archive. To see a list of log files, enter archive log ?.
•archive_filename - An optional name you want to assign to the archive file. Enter an unquoted text string with a maximum length of 32 characters.
Archiving the Running-Config
Use the archive running-config command to archive the running-config. Enter the archive_filename as the name you want to assign to the archive file. The archive_filename is an unquoted text string with a maximum length of 32 characters. The syntax for this command is:
archive running-config archive_filename
Archiving Scripts
Use the archive script command to archive a script file. The syntax for this command is:
archive script script_filename {archive_filename}
The variables are:
•script_filename - The filename of the script to archive. To see a list of scripts, enter archive script ?.
•archive_filename - An optional name you want to assign to the archive file. Enter an unquoted text string with a maximum length of 32 characters.
Archiving the Startup-Config
Use the archive startup-config command to archive the startup configuration file. Enter the archive_filename as an optional name you want to assign to the archive file. Enter an unquoted text string with a maximum length of 32 characters. The syntax for this command is:
archive startup-config {archive_filename}
Clearing the Archive Directory
Use the clear archive command to clear a file in the archive directory. Enter the archive_filename as the name of the archive file to clear. To list the archive files, enter clear archive ?. The syntax for this command is:
clear archive archive_filename
Restoring Files from the Archive Directory
Use the restore command to restore files previously archived in the CSS archive directory. The archive directory on the CSS disk stores log, script, and startup-config files. This command is available in SuperUser mode. The options for this command are:
•restore archive_filename log - Restore an archived log file to the log subdirectory
•restore archive_filename script - Restore an archived script file to the script subdirectory
•restore archive_filename startup-config - Restore an archived startup-config file to the startup configuration
Note The archive directory resides on the CSS hard drive. If you booted your CSS from a network-mounted system and your hard drive is not working, archive- and restore-related functions are suspended.
For more information on these options and associated variables, refer to the following sections.
Restoring an Archived Log File
Use the restore log command to restore an archived log file to the log subdirectory. The syntax for this command is:
restore archive_filename log {log_filename}
The variables are:
•archive_filename - The name of the archived log file. Enter an unquoted text string. To see a list of archived files, enter restore ?.
•log_filename - An optional name you want to assign to the restored log file. Enter an unquoted text string with a maximum length of 32 characters.
The following example restores the log file arrowlog to the log subdirectory and renames it to arrowpointlog.
# restore arrowlog log arrowpointlog
Restoring an Archived Script File
Use the restore archive_filename script command to restore an archived script file to the script subdirectory. The syntax is:
restore archive_filename script {script_filename}
The variables are:
•archive_filename - The name of the archived file. Enter an unquoted text string. To see a list of archived files, enter restore ?.
•script_filename - An optional name you want to assign to the script file. Enter an unquoted text string with a maximum length of 32 characters.
The following example restores the script arrowscript to the script subdirectory.
# restore arrowscript script
Restoring an Archived Startup-Config
Use the restore archive_filename startup-config command to restore an archived file to the startup configuration. Enter the archived startup-config filename as an unquoted text string. To see a list of archived files, enter restore ?.
Caution The restored file overwrites the startup configuration.
The syntax is:
restore archive_filename startup-config
The following example restores the archived startup-config arrowstart as the current startup-config.
# restore arrowstart startup-config
Copying Core Dumps to an FTP or TFTP Server
To copy core dumps from the CSS to a File Transfer Protocol (FTP) or Trivial File Transfer Protocol (TFTP) server, use the copy core command. The copy core command is available at the SuperUser prompt.
The options for this command are:
•copy core coredump_filename ftp
•copy core coredump_filename tftp
To see a list of core dumps, enter the copy core ? command.
Copying Core Dumps to an FTP Server
To copy a core dump to an FTP server, use the copy core ftp command. Before you copy a core dump from the CSS to an FTP server, you must create an FTP record file containing the FTP server IP address, username, and password. For information on configuring an FTP record, refer to "Configuring an FTP Record" in this chapter.
The syntax is:
# copy core coredump_filename ftp ftp_record filename
For example:
# copy core dumpfile ftp ftpserv1 starlogthurs
The variables are:
•coredump_filename - The name of the core dump on the CSS. Enter an unquoted text string with no spaces and a maximum length of 32 characters.
•ftp_record - The name of the FTP record file that contains the FTP server IP address, username, and password. Enter an unquoted text string with no spaces and a maximum length of 32 characters.
•filename - The name you want to assign to the file on the FTP server. Include the full path to the file. Enter an unquoted text string with no spaces and a maximum length of 32 characters.
Copying Core Dumps to a TFTP Server
To copy a core dump to an TFTP server, use the copy core tftp command.
The syntax is:
copy core coredump_filename tftp ip_address or hostname filename
The variables are:
•coredump_filename - The name of the core dump on the CSS. Enter an unquoted text string with no spaces and a maximum length of 32 characters.
•ip_address or hostname - The IP address or host name of the TFTP 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). If you wish to use a hostname, you must first set up a host table using the (config) host command.
•filename - The name you want to assign to the file on the TFTP server. Include the full path to the file. Enter an unquoted text string with no spaces and a maximum length of 32 characters.
Displaying CSS Configurations
The CSS Command Line Interface (CLI) provides a comprehensive set of show commands that display CSS configurations. The show commands are mode-independent; that is, they are available in each mode.
Note The CSS does not show configuration default values in the show displays. This applies even when you enter a command to configure a default value.
To display the list of show commands, enter:
Displaying Software Information
Use the version command in SuperUser mode to display the version of software currently running on the CSS. This display also shows the version of flash, whether the software is set to primary or secondary, and your license number.
For example:
Version: ap0500002 (5.00 Build 02)
Network Path: e:/adi_directory/
Config Path: e:/adi_directory/
Flash (Locked): 4.01 Build 3
Flash (Operational):4.10 Build 8
License Cmd Set: Standard Feature Set
Displaying Hardware Information
Use the show chassis command to display a chassis configuration. The syntax and options for this command are:
•show chassis - Display a summary of the chassis configuration.
•show chassis flash - Display the operational and locked flash version for the CSS 11150 and the CSS 11800 System Control Module (SCM) and Switch Fabric Module (SFM). An asterisk (*) character before a flash version and build number indicates it is the active flash.
•show chassis inventory - Display the physical configuration of the CSS including their part and serial numbers.
•show chassis slot number - Display the operational parameters for a slot in a 11800 CSS. Enter an integer value. To see a list of slots, enter show chassis slot ?.
•show chassis verbose - Display detailed information about the chassis configuration.
To view a summary of the chassis configuration, enter:
Note In the CSS 11050 and the CSS 11150, the Switch Control Module (SCM) and Switch Fabric Module (SFM) are combined on one integrated circuit card called the Switch Control Fabric Module (SCFM).
To view the chassis flash, enter:
To display the physical configuration of the CSS, enter:
Table 1-7 describes the fields in the show chassis output.
Table 1-7 Field Descriptions for the show chassis Command
Field
|
Description
|
Name
|
The model number of the CSS.
|
SW Version
|
The currently running software version on the CSS.
|
HW Major Version
|
The major version of the hardware.
|
HW Minor Version
|
The minor version associated with the hardware major version.
|
Serial Number
|
The serial number of the chassis flash.
|
Base MAC Address
|
The MAC address for the chassis.
|
Module Number
|
The slot number for the module.
|
Module Name
|
The name of the module.
|
Status
|
The status of the module. The possible states are:
•primary
•backup
•powered-off
•powered-on
•bad
•unknown
|
Port Number
|
The number of the Ethernet port.
|
Port Name
|
The name of the port.
|
Status
|
The status of the port. The possible states are:
•online
•offline-ok
•offline-bad
•bad
•going-online
•going-offline
•inserted
•post
•post-ok
•post-fail
•post-bad-comm
•any
•unknown-state
|
Operational
|
Active flash on the CSS.
|
Locked
|
The inactive flash version available on the CSS.
|
Chassis/Board
|
The hardware part comprising the CSS.
|
PN
|
The part number of the hardware.
|
Rev
|
The revision of the part.
|
Showing System Resources
Use the show system-resource command to display information about the size of the installed and free memory available on the:
•CSS 11050 and CSS 11150.
•CSS 11800 SCM and SFM modules. The CSS displays system resources for the primary SCM and SFM.
Table 1-8 describes the fields in the show system-resources output.
Table 1-8 Field Descriptions for the show system-resources Command
Field
|
Description
|
Installed Memory
|
The total memory size in the CSS
|
Free Memory
|
The amount of free memory available
|
CPU
|
The utilized percentage of the CPU
|
Buffer Statistics
|
Buffer Pool
|
The buffer pool index
|
Size
|
The size in bytes of each buffer in the buffer pool
|
Total
|
The total number of buffers in the buffer pool
|
Available
|
The current number of available buffers in the buffer pool
|
Failures
|
The number of failures to obtain a buffer from the buffer pool
|
Low Buffer Count
|
The lowest recorded number of available buffers
|
Showing User Information
To display all users currently defined in the CSS, enter:
(config)# show user-database
To display information for a specific user, enter:
(config)# show user-database picard
Table 1-9 describes the fields in the show user-database output.
Table 1-9 Field Descriptions for the show user-database Command
Field
|
Description
|
Virtual Authentication
|
Whether or not users must enter a username and password to log into the CSS.
|
Console Authentication
|
Whether or not console port authentication of locally-defined usernames and passwords logging into the CSS in enabled.
|
Username
|
The username.
|
Privilege Level
|
The privilege level of the user.
|
Type
|
The type of user. Types are:
•administrator (administrative username, created using the username-offdm command)
•technician (technician username, created using the username-technician command)
If the field is blank, the user is neither an administrator or technician.
Note The username-offdm command is for use by system administrative personnel only. The username-technician command is for use by technical personnel only.
|
Directory Access
|
The directory access privileges for the listed usernames (as specified through the dir-access option of the username command). There are a series of access privilege codes assigned to the seven CSS directories, in the following order: Script, Log, Root (installed CSS software), Archive, Release Root (configuration files), Core, and MIBs directories. By default, users have both read- and write-access privileges (B) to all seven directories. The levels for each of the CSS directories can be one of the following access privilege codes:
•R - Read-only access to the CSS directory
•W - Write-only access to the CSS directory
•B - Both read- and write-access privileges to the CSS directory (default for all users)
•N - No access privileges to the CSS directory
For example, BBNBNBB indicates that the user has no access to the root and release root directories, but has read and write access to the script, log, archive, core, and MIB directories.
|
Showing Current Logins
To display currently connected lines or sessions, use the show lines command. A connected line is a console or Telnet session. This command is available in all modes.
For example, to display currently connected lines or sessions, enter:
Table 1-10 describes the fields in the show lines output.
Table 1-10 Field Descriptions for the show lines Command
Field
|
Description
|
Line
|
The type of session. The * indicates your current session.
|
User
|
The login name of the user.
|
Login
|
The amount of time that the user has been logged on the CSS.
|
Idle
|
The amount of time that the session has been idle.
|
Location
|
The location where the session is occurring.
|
Where to Go Next
<Xref_Color>Chapter 2, Configuring User Profiles and CSS Parameters, provides information on how to configure user profiles and CSS parameters. This chapter also contains information on using the Content API and Command Scheduler features.
