Table Of Contents
Booting the CSS
CSS Software Overview
Connecting the Console
Powering Up the CSS
Powering Down the CSS
Booting the CSS for the First Time
Entering Your License Key
Configuring the Ethernet Management Port
Changing the Default Username and Password
Password-Protecting the Offline Diagnostic Monitor Menu
Booting the CSS on a Routine Basis
Performing Hardware Initialization and Power-On Diagnostics
Checking Results of Previous Shutdown
Logging into the CSS
Booting the CSS
This chapter describes the CSS disk directory structure, powering the CSS, and the CSS boot sequence.
This chapter contains the following sections:
•
CSS Software Overview
•
Connecting the Console
•
Powering Up the CSS
•
Powering Down the CSS
•
Booting the CSS for the First Time
•
Booting the CSS on a Routine Basis
CSS Software Overview
The CSS software contains the files to run the CSS including boot files, and directories for archiving and logging files, and MIB information. This software is preinstalled on the CSS 11800 Internal Disk Module (IDM), or CSS 11050 or CSS 11150 disk drive. For a CSS 11800 or CSS 11150, the disk can be a hard disk drive or an optional flash disk, an EPROM-based storage device.
You can also install the CSS software on a network drive on an NT system which the CSS can access through FTP. The Content Services Switch Documentation and System Software compact disk 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 configuring a network boot drive, refer to the Content Services Switch Basic Configuration Guide.
You can install a maximum of four software CSS versions on your CSS hard drive. For a CSS flash disk, you can install a maximum of two software versions. To view all versions installed on the CSS, use the show installed-software command.
To view the version currently running on the CSS, use the version command. The software version format is defined as follows:
From an FTP server, you can view the following directories:
•
The log directory contains the following log files:
–
boot.log - ASCII log of boot process
–
sys.log - ASCII log of system events (logging to disk is enabled by default to subsystem all and level info)
–
boot.bak - Backup of a previous boot log
–
sys.log.prev - Backup of a previous system log (if any)
•
The scripts directory contains default, profile, and sample scripts
•
The core directory contains any core dumps created by the CSS
•
The MIB directory contains MIB files which you can load into SNMP-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 CSS disk. Do not manipulate the files in these directories.
The software directory also contains the startup-config file. This file is an ASCII file containing commands the CSS executes at startup. This file is created when you:
•
Complete using the configuration script.
•
Issue the copy running-config startup-config or write memory command. These commands also save configuration changes to the startup-config during a CSS session.
•
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 Cisco Content Services Switch Command Reference.
To view general information about the CSS disk, enter:
Table 3-1 describes the fields in the show disk output.
Table 3-1 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 generating 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.
|
Connecting the Console
To connect a console to the CSS and power up the CSS, attach the console cable (provided in the accessory kit) to the Console port on the CSS 11050 or CSS 11150 front panel, or to the CSS 11800 SCM panel. Your terminal settings must match the following CSS default settings:
•
Baud Rate: 9600
•
Data Bits: 8
•
Flow Control: none
•
Parity: none
•
Stop Bits: 1
On the CSS 11050 or 11150 console cable, you must attach two snap-on ferrites provided in the Accessory kit. To attach the snap-on ferrites (see Figure 3-1):
1.
Position and attach the first ferrite .75 inches from the RJ-45 connector to the Console port.
2.
Attach the second ferrite behind the first ferrite.
Figure 3-1 Attaching Ferrites to a CSS 11050 or 11150 Console Cable
Powering Up the CSS
To power up the AC on a CSS 11050, CSS 11150, or CSS 11800:
1.
Attach the power cord to the CSS 11050 or CSS 11150 rear panel AC connector, or to the CSS 11800 AC connector (as described in Chapter 2, Cabling the CSS).
2.
Power on the CSS by toggling the power switch to the 1 (on) position.
For DC power on a CSS 11150 or CSS 11800, set the external disconnect device to the 1 (on) position.
Powering Down the CSS
To shutdown the CSS gracefully and avoid introducing lost or fragmented files, always use the shutdown command prior to removing power from the CSS. This command is available in boot mode.
For example:
Once the CSS shuts down all processes, you may remove power from the CSS.
Booting the CSS for the First Time
When the CSS initially boots up, it:
•
Performs hardware diagnostics.
•
Validates the integrity of the disk file system automatically. If the CSS:
–
Does not detect errors, it reports a status of OK and continues the boot process
–
Detects errors, it returns a status of DIRTY, runs a quick check disk automatically, and continues the boot process
•
Prompts you to:
–
Enter the software license key, located on a card in an envelope in the Accessory kit
–
Configure the IP address and subnet mask for the Ethernet Management port, used for CSS configuration and management only; this port does not route traffic
–
Change the default administrative login name (admin) and password (system)
–
Password-protect the Offline Diagnostic Monitor menu (Offline DM menu)
The initial boot-up prompts are described in the following sections.
Entering Your License Key
When the CSS completes hardware initialization and power-on diagnostics, you must enter a valid license key for the CSS software. The CSS does not require you to enter this key on subsequent startups.
Note
Your license key is located on a card in an envelope in the Accessory kit. If you cannot find the software license key, call the Cisco Licensing department in the Technical Assistance Center at (800) 553-2447 or email them at licensing@cisco.com.
The CSS prompts you to accept the license agreement. You must accept the license agreement or you cannot log into the CSS.
Then the CSS prompts you to enter your license key, as shown below:
Enter Software License Key: xxxxxxxxxxxx
When you enter:
•
A valid license number, the CSS prompts you to enter an IP address for the Ethernet Management port.
•
An invalid license number, the CSS redisplays the license prompt until you enter a valid number. If you do not enter a valid license number, you cannot log into the CSS.
Note
If you purchased the SSH Server option or the Network Proximity software option, its license key is on the CSS software license key card. After the CSS has booted and you log in, use the license command to enter the SSH Server license key. For example, enter:
# license
Enter Software License Key (q to quit):
At the prompt, enter the 12-digit option license key.
Configuring the Ethernet Management Port
Once you enter a valid license key at the boot prompt, the CSS displays the following message and prompt:
Use the Ethernet management port IP address to access the Content
Services Switch for configuration and management only. This port does
not route traffic and is not associated with VLAN circuits.
Do you wish to configure the Ethernet management port IP address
[y/n]?
Enter:
•
y to configure an IP address and subnet mask for the Ethernet Management port. The CSS prompts you for an IP address and then a subnet mask. You must enter a valid IP address or the CSS repeats the prompt until you do. The CSS does not accept an all zero IP address.
Caution 
The Ethernet Management port IP address must be a different subnet than any other CSS VLAN circuit subnet. If you do not make this IP address unique, you will not be able to access the port.
Enter IP Address [1.1.1.1]:
Enter subnet mask [255.0.0.0]
•
n to accept the default IP address (1.1.1.1) and subnet mask (255.0.0.0). The CSS does not prompt you for an IP address and subnet mask.
Changing the Default Username and Password
The CSS allows you to change the default username and password.
Access to this device is allowed using the default username and
password. For enhanced security we recommend that you change the
defaults. Do you want to change the defaults now (yes,no):
Enter:
•
yes to change the username and password. The CSS prompts you for this information and password confirmation.
Enter <administrator> username:
Enter <administrator> password:
Confirm <administrator> password:
•
no to keep the default username and password.
Password-Protecting the Offline Diagnostic Monitor Menu
Note
The Offline Diagnostic Monitor Menu options are described in the Content Services Switch Basic Configuration Guide, Chapter 1, Logging In and Getting Started.
The CSS prompts you to password-protect the Offline DM menu.
Set Password Protection for Offline Diagnostic Monitor menu (yes,no)
Enter:
•
yes to password-protect the Offline DM menu. When you password-protect the Offline DM menu, you need to enter the administrative username and password each time you access the menu.
The administrative username and password are required to access
the Offline Diagnostic Monitor menu.
Initializing the disk...........OK
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.
•
no to disable password-protection on the Offline DM menu.
The CSS then enables you to access the Offline DM menu.
Press any key to access the Offline Diagnostic Monitor menu...
To access the Offline DM menu, press any key within 5 seconds. If you do not wish to access the Offline DM menu after seeing this message, do not press a key.
After the CSS has completed the boot process, it displays the Cisco banner, copyright, and login prompt.
The CSS Ready LED remains lit and the Status LED blinks indicating that there is no configuration file. Log in to the CSS, as described in "Logging into the CSS" later in this chapter. Then, refer to Chapter 4, Configuring the CSS, for the procedure on using the configuration script.
Booting the CSS on a Routine Basis
When you power up the CSS (after initial start-up), the boot process:
•
Displays the software version and build number
•
Performs hardware initialization and power-on diagnostics
•
Checks the results of the previous shutdown
•
Provides access to the Offline Diagnostic Monitor (Offline DM) menu
•
Prompts you to log into the CSS
The boot-up sequence is described in the following sections.
Performing Hardware Initialization and Power-On Diagnostics
When you boot the CSS, it initializes the hardware and performs power-on diagnostics. During this time, the module Status and Ready LEDs blink to indicate the stages of the boot process. If a non-recoverable error occurs during the boot sequence, the module Status and Ready LEDs blink indefinitely until you reboot the CSS (using the reboot command) and the error is cleared.
•
The CSS 11050 or CSS 11150 boot process takes approximately 15 seconds to complete.
•
The CSS 11800 boot process takes approximately 1 to 3 minutes (depending on your configuration) to complete.
Table 3-2 defines the boot states and the Status and Ready LED blinking patterns.
Table 3-2 Module Status and Ready LED Boot Definitions
State Sequence
|
Status LED
|
Ready LED
|
1. Off line and not active
|
Off
|
Off
|
2. Offline testing
|
Off
|
Blinking
|
Offline tests detect an error
|
Blinking
|
Off
|
3. Off line and active (Offline Diagnostic Monitor is displayed)
|
On
|
On
|
4. On line and not active
|
On
|
Off
|
5. Online testing/Initialization
|
On
|
Blinking
|
Online tests detect an error
|
Blinking
|
On
|
6. On line and not active (Passive SCM or SFM)
|
On
|
Off
|
7. On line and active
|
Off
|
On
|
Boot diagnostics failed and the system cannot boot.
|
Blinking
|
Blinking
|
No configuration file exists on an initially-booted CSS. Log in to the CSS and create a configuration file. See "Logging into the CSS" later in this chapter. Then, refer to Chapter 4, Configuring the CSS.
|
Blinking
|
On
|
Checking Results of Previous Shutdown
When the CSS boots up, it checks the results of the previous shutdown. If the CSS:
•
Does not detect any errors, it reports a status of OK and continues with the boot process:
Reading configuration records...OK
Checking previous shutdown...OK
Initializing the disk...OK
•
Detects errors, it returns a status of DIRTY and runs a quick check disk automatically:
Reading configuration records...OK
Checking previous shutdown...DIRTY
Complete (/) Operation completed successfully
Initializing the disk...OK
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
The CSS 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 files and directories on the disk. The greater the number of installed files and directories, the longer it takes to complete the check disk.
Logging into the CSS
After the CSS has completed the boot process, it displays the start-up banner, copyright, and login prompt. If a startup-config is present, the CSS displays the following message:
Press CNTRL-C to abort running the startup-config
When you abort running the startup-config, the CSS does not use the existing startup-config. It enables you to log in and reconfigure the CSS to create a new running-config. Use this feature if you misconfigure your startup-config and it becomes unusable.
When you log in from:
•
A console, the CSS prompts you to
•
A Telnet session, this message is not displayed.
The CSS prompts you to enter a username and password. Enter the default user name admin and the default password system as lowercase text, or enter the administrative username and password you configured during the boot process or using the Offline DM menu. For security, the CSS does not display the password.
If you connect a console to the CSS after the CSS boots, your screen will be blank. Press <Enter> to display the username and password prompts.
If the CSS has never been configured, a configuration script runs automatically and prompts you to enter configuration information. Subsequent logins to the CSS do not automatically start the configuration script. Refer to Chapter 4, Configuring the CSS, for the procedure on using the configuration script.