-
CSS Administration Guide (Software Version 7.10)
-
Index
-
About This Guide
-
Logging In and Getting Started
-
Configuring Interfaces and Circuits
-
Configuring CSS Network Protocols
-
Configuring OSPF
-
Using the CSS Logging Features
-
Configuring User Profiles and CSS Parameters
-
Configuring Simple Network Management Protocol (SNMP)
-
Configuring Remote Monitoring (RMON)
-
Upgrading Your CSS Software
-
Using the Offline Diagnostic Monitor Menu
-
Table Of Contents
Logging In and Getting Started
Changing the Administrative Username and Password
Restricting Modifications to the CSS User Database
Configuring Usernames and Passwords
Configuring an IP Address, Subnet Mask, and Default Gateway for the Ethernet Management Port
Configuring a Management Port Default Gateway
Configuring Date, Time, and Time Zone
Synchronizing the CSS with an SNTP Server
Configuring the SNTP Poll-Interval
Showing SNTP Configuration Information
Copying Files from an FTP Server
Specifying a Disk for Booting, Logging, and Core Dumps
Selecting a Disk for the Primary Boot Record
Selecting a Disk for the Secondary Boot Record
Selecting a Disk for Core Dumps
Showing the Disk Mapping Configurations
Managing the CSS Boot Configuration
Unpacking an ArrowPoint Distribution Image
Removing an ArrowPoint Distribution Image
Specifying the Primary Boot Configuration
Specifying the Primary Boot File
Specifying the Primary Boot Type
Primary Boot Configuration Considerations
Specifying the Primary Configuration Path
Specifying the Secondary Boot Configuration
Specifying the Secondary Boot File
Specifying the Secondary Boot Type
Specifying the Secondary Configuration Path
Configuring a Boot Configuration Record for the Passive SCM
Configuring the Passive SCM IP Address
Configuring the Passive SCM Primary Boot File
Configuring the Passive SCM Primary Boot Type
Configuring the Passive SCM Primary Configuration Path
Configuring the Passive SCM Secondary Boot File
Configuring the Passive SCM Secondary Boot Type
Configuring the Passive SCM Secondary Configuration Path
Configuring the Passive SCM Subnet Mask
Copying Configuration Information from the Active SCM to the Passive SCM
Showing the Boot Configuration
Booting the CSS from a Network Drive
Configuring Network Boot for a Primary SCM
Configuring Network Boot for a Passive SCM
Showing Network Boot Configurations
Using the Running-Config and Startup-Config Files
Clearing the Running Configuration and the Startup Configuration
Showing the Running Configuration
Showing the Startup Configuration
Creating a Running Configuration or Startup Configuration Using a Text Editor
Archiving Files to the Archive Directory
Archiving the Running-Config File
Archiving the Startup-Config File
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 File
Copying Core Dumps to an FTP or TFTP Server
Copying Core Dumps to an FTP Server
Copying Core Dumps to a TFTP Server
Displaying Software Information
Displaying Hardware Information
Logging In and Getting Started
This chapter describes the basic initial configuration procedures for the CSS, such as configuring an IP address and subnet mask, configuring the date and time, and configuring boot mode. Also included in this chapter is a description of the system software. Information in this chapter applies to all CSS models, except where noted.
Note
You must enter a software license key when you boot the CSS for the first time. For details, refer to the Cisco Content Services Switch Hardware Installation Guide, Chapter 3, Booting the CSS.
If you configure your 11000 series CSS for Proximity Database, you cannot use the CSS for load balancing. For details on Proximity Database, refer to the Cisco Content Services Switch Advanced Configuration Guide, Chapter 5, Configuring Network Proximity.This chapter contains the following sections:
•
•
•
•
•
•
•
•
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:
•
•
•
•
•
•
•
•
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.
Logging in to the CSS
To log in to 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, Cisco Systems recommends that you change them immediately to safeguard the CSS against unauthorized logins.
Note
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 permanently delete them. 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:
•
•
The following example uses the CLI command to change the default administrative username and password.
(config)# username-offdm bobo password secretRestricting 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:
•
•
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-databaseTo remove restrictions for modifying the CSS user database, enter:
(config)# no restrict user-databaseConfiguring 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.
•
By default, new users have only user-level status unless you configure them to have SuperUser status.
•
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
The options and variables are as follows:
•
•
Note
•
•
•
•
Enter one of the following access privilege codes for the CSS Script, Log, Root, Archive, Release Root, Core, and MIB directories, in this order:
–
–
–
–
The following example creates a SuperUser named picard with a password of captain.
(config)# username picard password "captain" superuserFigure 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 NWBNNNRTo display a list of existing usernames, enter:
(config)# username ?To remove an existing username, enter:
(config)# no username picardTo 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
Configuring an IP Address, Subnet Mask, and Default Gateway for the Ethernet Management Port
To communicate with the CSS and enter 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 and a default gateway (to load a boot file on a CSS across different subnets) that the CSS uses upon boot.
The Ethernet Management port is located on the:
•
•
•
The CSS enables you to configure an IP address, a subnet mask, and a default gateway:
•
•
•
For information on configuring an IP address, subnet mask, and default gateway during the boot routine or using the Offline DM Main menu, refer to Appendix B, Using the Offline Diagnostic Monitor Menu. For information on configuring an IP address, subnet mask, and default gateway using CLI commands, see the following sections.
Note
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, reenter the ip address command and enter the new IP address.
Note
An IP address of 0.0.0.0 for the Ethernet Management port is a legal setting, and will disable the management port upon reboot. If you enter 0.0.0.0, and attempt to use the subnet mask command (see below), the following message appears: The mask cannot be set because the IP address is 0.0.0.0.
To specify an Ethernet Management port IP address, enter:
(config)# boot(config-boot)# ip address 172.3.6.58
Note
Configuring a Subnet Mask
To configure the CSS subnet mask, use the subnet mask option in boot mode. For example:
(config)# boot(config-boot)# subnet mask 255.255.255.0To remove the configured subnet mask, enter:
(config-boot)# no subnet maskConfiguring a Management Port Default Gateway
To configure a CSS management port default gateway for use in the Offline DM, use the gateway address command in boot mode. The gateway command allows you to boot the CSS from the Offline DM when the boot image resides on a different subnet. This command does not have a no form. To change the gateway address, reenter the gateway address command and enter the new IP address. For example:
(config)# boot(config-boot)# gateway address 172.16.57.2To disable the default gateway address, enter an address of 0.0.0.0.
If you have a second SCM installed in a CSS 11503, CSS 11506, or CSS 11800, use the passive gateway address command to configure the management port gateway address in the passive SCM boot-config.
Note
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:
•
•
To configure an IP route, use the ip route command and specify either an:
•
or
•
The syntax for the ip route command to configure a default IP route is:
ip route ip_address subnet mask ip_address2
For example:
(config)# ip route 0.0.0.0 /0 192.168.3.123The variables are:
•
•
–
–
•
For complete information on configuring IP routes, refer to 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
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 2002 as 06-15-2002.
Enter the new information in the format mm-dd-yy as shown:
# clock dateEnter date: [10-03-02] 10-04-02To 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:
# clock timeEnter time: [15:12:38] 16:12:38To 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 to set the clock to the new time without the time zone offset.
Note
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:
•
•
•
•
•
To enter the new time zone for Eastern Standard Time (EST) with a -3 hour offset:
# clock timezone EST hours 3 before-UTCTo set the time zone offset back to 00:00:00 (and also set the clock to the new time without the time zone offset):
# no clock timezoneTo display the current date and time, enter the show clock command:
# show clockTable 1-2 describes the fields in the show clock output.
Configuring European Date
Use the date european-date global configuration command to enable the clock date command to accept date input in the format of day, month, and year.
(config)# date european-date 12/03/02For example:
(config)# date european-date 12/03/02To reset the format for the clock date command to its default of month, day and year, enter:
(config)# no date european-dateSynchronizing 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
For detailed information on configuring the SNTP server, consult the documentation provided with the server.
The options for this global configuration mode command are:
•
•
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:
•
•
To configure an SNTP server (running version number 3), enter:
(config)# sntp server 192.168.19.21 version 3To remove the specified SNTP server, enter:
(config)# no sntp serverConfiguring 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 matches the "real time" of the server. The valid entries are 16 to 16284 seconds. The default is 64 seconds.
To specify an SNTP poll-interval of 90 seconds, enter:
(config)# sntp poll-interval 90To return the SNTP poll-interval to its default setting of 64 seconds, enter:
(config)# no sntp poll-intervalShowing SNTP Configuration Information
To display the Simple Network Time Protocol (SNTP) configuration information on the CSS, enter the show sntp global command. For example:
(config)# show sntp globalTable 1-3 describes the fields in the show sntp global output.
CSS Software Overview
The CSS software contains the files needed to run the CSS, including boot files, directories for archiving and logging files, and MIB files. This software is pre-installed on the CSS conventional hard disk or an optional Flash disk, a Flash memory-based storage device.
•
•
The CSS software image is available from the Cisco Systems Web site (www.cisco.com) as an ArrowPoint Distribution Image (ADI), network boot ZIP (.zip) image, or GZIP-compressed (adi-gz) image.
You can install the CSS software on an FTP server, which the CSS accesses through the File Transfer Protocol (FTP). The CSS accesses the ADI or GZIP file containing the CSS software from an FTP server, copies the file to the CSS disk, and unpacks it. The CSS then boots from the disk.
You can also install the CSS software on a network-mounted drive on a remote system, which the CSS accesses through FTP. Network boot uses a special ZIP version of WebNS that ends with a .zip extension. Instead of the CSS disk, the network file system contains the CSS software. This software must be copied and uncompressed on the network drive. For information on booting the CSS from a network boot drive, refer to the "Booting the CSS from a Network Drive" section.
The CSS software version format is defined as follows:
To display the software versions installed on the CSS, use the show version and show installed-software commands, as described in "Displaying Software Information" later in this chapter.
From an FTP server, you can view the following directories on the hard disk or flash disk:
•
–
–
–
–
•
•
•
Note
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:
•
•
•
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, see the "Archiving Files to the Archive Directory" and "Restoring Files from the Archive Directory" in this chapter.
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}
Note
The variables are:
•
•
•
•
•
•
•
The config-path and base directory path in the ftp-record associated with a network boot must not contain a pathname that conflicts with a non-network drive name (for example, c: or host:).
For example (using an encrypted password):
# ftp-record arrowrecord 192.168.19.21 bobo password "secret" /outgoingTo delete the FTP record arrowrecord from the CSS, enter:
# no ftp-record arrowrecordCopying Files from an FTP Server
Use the copy ftp command to copy files from an FTP server to the CSS. This command is available in SuperUser mode. 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:
•
•
•
Configuring Disks
The CSS 11501 and the Switch Control Module (SCM) in the CSS 11503 and CSS 11506 contain two PCMCIA slots for a hard disk or flash disk. These disks contain the CSS system software, and are also used for logging and storing off-line system files. The two disks are identified by the PCMCIA slots (slot 0 and slot 1) in which they are installed. Disk 0 is the default storage location for the primary and secondary boot records in the CSS. The default storage location for log files and core dumps in the CSS is the specified disk from which the CSS boots (disk 0 or disk 1).
If you want to reconfigure the data storage use of disks 0 and 1 in the CSS, use the map command. The map command allows you to specify the disk that contains the primary boot record, contains the secondary boot record, stores log files, and stores core dumps. You can mix and match the storage location of these files between the two disks. For example, you can store the primary boot record on disk 0 and the secondary boot record on disk 1, and redirect the storage of output logs and core dumps to disk 1.
In addition to specifying the file storage locations, you can also:
•
•
•
•
•
Note
Logging to a CSS disk can cause the performance of the CSS to degrade.
Note
Formatting a Disk
Use the format command to format and create the Core and Archive directories on a specified disk. The format command permanently erases all data on the disk. This command is available only in SuperUser mode.
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.
To format a disk, use the following commands:
•
•
Note
For example, to format the disk in slot 1, enter:
# format 1The CSS queries you about formatting the disk.
Formatting the disk results in all disk data beingpermanently erased.Are you sure you want to continue? (yes,no):Enter:
•
•
Specifying a Disk for Booting, Logging, and Core Dumps
Use the map commands to specify the disk (slot 0 or slot 1) that the CSS uses to store the primary boot record, the secondary boot record, logging output file, and core dumps. By default, disk 0 is the default storage location for the primary and secondary boot records in the CSS. The default storage location for log files and core dumps is the specified disk from which the CSS boots (disk 0 or disk 1).
The options for the map command are:
•
•
•
•
Use the no form of each command to remove mapping to the specified disk and return the setting to the default disk. Refer to the following sections for more information on these options and associated variables.
Selecting a Disk for the Primary Boot Record
Use the map primary-boot command to select the disk that contains the primary boot record of the CSS. The default storage location for the primary boot record is disk 0. Valid selections are 0 (for the disk in slot 0) and 1 (for the disk in slot 1). This command is available only in SuperUser mode.
For example, to select the disk in slot 1 as the storage location for the primary boot record, enter:
# map primary-boot 1To return the storage location of the primary boot record back to the disk in slot 0, enter:
# no map primary-bootor
# map primary-boot 0Selecting a Disk for the Secondary Boot Record
Use the map secondary-boot command to select the disk that contains the secondary boot record of the CSS. The default storage location for the secondary boot record is disk 0. Valid selections are 0 (for the disk in slot 0) and 1 (for the disk in slot 1). This command is available only in SuperUser mode.
For example, to select the disk in slot 1 as the storage location for the secondary boot record, enter:
# map secondary-boot 1To return the storage location of the secondary boot record back to the disk in slot 0, enter:
# no map secondary-bootor
# map secondary-boot 0Selecting a Disk for Core Dumps
Use the map core command to select the disk that stores core dump files when the CSS experiences a fatal error. The default storage location for core dump files is the disk from which the CSS boots (disk 0 or disk 1). For example, if the CSS boots from disk 1, then disk 1 becomes the default storage location for core dump files.
Valid selections are 0 (disk in slot 0) and 1 (disk in slot 1). This command is available only in SuperUser mode.
Note
For example, to select the disk in slot 1 as the storage location for core dumps, enter:
# map core 1To return the storage location for core dumps back to boot disk, enter:
# no map coreSelecting a Disk for Logging
Use the map log command to select the disk on which you want to store log files. The default storage location for log files is the disk from which the CSS boots (disk 0 or disk 1). For example, if the CSS boots from disk 0, then disk 0 becomes the default storage location for log files.
Valid selections are 0 (disk in slot 0) and 1 (disk in slot 1). This command is available only in SuperUser mode.
For example, to select the disk in slot 1 as the storage location for log files, enter:
# map log 1To return the storage location of log files back to the boot disk, enter:
# no map logCopying Files Between Disks
Use the copy command to copy the startup configuration, logs, scripts, archive, and boot image files from one disk (source) to the second disk (destination) in a CSS. The CSS software automatically creates the software directory and hierarchy on the destination disk. This command is available in SuperUser mode.
The syntax is:
copy source_disk_slot {log filename {destination filename}|logs|script filename {destination filename}|scripts|archive filename {destination filename}|archives|boot-image filename|startup-config}
The options and variables are:
•
Note
•
•
•
•
•
•
•
•
•
•
•
Note the following restrictions for the copy command when copying information between two disks in the CSS:
•
•
Showing the Disk Mapping Configurations
Use the show map command to display the mapping configuration of the two disks in slot 0 and slot 1 in a 11500 series CSS. This command displays the disk assignment of primary-boot record, secondary-boot record, core dump files, and logging output. This command is available in all modes.
For example:
(config)# show mapMSD Mapping:Primary-Boot: 0Secondary-Boot: 0Core: 1Log: 1Displaying Files from a Disk
Use the show command to display the specified archive, log, script, or startup configuration file stored on a specific disk in the 11500 series CSS. The syntax is:
show disk_slot {log filename|script filename|archive filename|
startup-config}The options are:
•
•
•
•
•
Clearing Files from a Disk
Use the clear command to delete the specified file (startup configuration, logs, scripts, archive file) stored on a specific disk. This command is available in SuperUser mode. The syntax is:
clear disk_slot {log filename|script filename|archive filename|
startup-config}The options are:
•
•
•
•
•
Managing the CSS Boot Configuration
Boot configuration mode contains all the commands necessary to boot the CSS and maintain the software revision. To access this mode, use the boot command from global configuration mode.
To access boot mode, enter:
(config)# bootThe CSS enters boot mode.
(config-boot)#For information about commands available in boot mode, refer to the following sections:
•
•
•
•
•
•
•
Note
Unpacking an ArrowPoint Distribution Image
Use the unpack command to unpack the ArrowPoint Distribution Image (ADI) on the CSS disk. Enter the ADI filename as an unquoted text string with a maximum of 32 characters. For example:
(config-boot)# unpack sg0710001.adi
Note
Removing an ArrowPoint Distribution Image
Use the remove command to remove an ArrowPoint Distribution Image (ADI) that is not currently running on the CSS. For a dual-disk 11500 series CSS, you need to identify the specified disk.
To remove a software versions installed on the CSS, use the following commands:
•
•
To display a list of ADIs installed on your CSS, enter remove ?. To display the ADI you are currently running, use the version command.
To remove an ADI, enter:
(config-boot)# remove sg0710001To remove an ADI from a disk in slot 1 of a dual-disk 11500 series CSS, enter:
(config-boot)# remove sg0710001 1Specifying the Primary Boot Configuration
Use the primary command to specify the primary boot configuration. The options for this boot-mode command are:
•
•
•
See the following sections for more information on these options and associated variables.
Specifying the Primary Boot File
Use the primary boot-file command to specify the primary boot file. Enter the primary boot file as an unquoted text string with no spaces and a maximum of 64 characters.
To specify the primary boot filename, enter:
(config-boot)# primary boot-file sg0710002To display a list of boot filenames, enter:
(config-boot)# primary boot-file ?To remove the primary boot file, enter:
(config-boot)# no primary boot-fileSpecifying the Primary Boot Type
Use the primary boot-type command to specify the location from which the CSS accesses the primary boot image upon system reboot or when you download new software. The syntax and options for the primary boot-type command are:
•
•
•
Note
The ftp_record variable is 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.
To configure the primary boot-type to boot-via-disk, enter:
(config-boot)# primary boot-type boot-via-diskTo remove the primary boot type, enter:
(config-boot)# no primary boot-typePrimary Boot Configuration Considerations
When you select primary boot-type boot-via-ftp or primary boot-type boot-via-network, make sure that you properly connect the Ethernet Management port on the CSS to the network. Note the locations of the Ethernet Management port on the CSS as listed below.
•
•
•
•
When you select primary boot-type boot-via-network, make sure that you:
•
–
–
–
•
Note
A network boot requires that the CSS 11501, 11503, or 11506 contains an operational disk.
Specifying the Primary Configuration Path
Use the primary config-path command to specify the alternate path to a network configuration for the network boot method. An alternate configuration path allows multiple CSSs to use the same boot image while keeping their configuration information in separate directories. The CSS must be able to access the configuration path through an FTP server as defined in the FTP record for the network boot method.
When using an alternate configuration path, make sure that the path leads to a directory containing the script, log, and information subdirectories, and the startup-config file. These subdirectories must contain the files in the corresponding subdirectories of the unzipped boot image. First, create these subdirectories, then copy the files from the boot image to the subdirectories.
Enter the configuration pathname as an unquoted text string with no spaces and a maximum of 64 characters.
To configure the primary config path, enter:
(config-boot)# primary config-path f:/bootdir/To remove the primary network configuration path, enter:
(config-boot)# no primary config-pathSpecifying the Secondary Boot Configuration
Use the secondary command to specify the secondary boot configuration. The CSS uses the secondary boot configuration when the primary boot configuration fails. The options for this boot mode command are:
•
•
•
For more information on these options and associated variables, see the following sections.
Specifying the Secondary Boot File
Use the secondary boot-file command to specify the secondary boot file that the CSS uses when the primary boot configuration fails. Enter the boot file as an unquoted text string with no spaces and a maximum of 64 characters.
To specify the secondary boot filename, enter:
(config-boot)# secondary boot-file sg0710001To display a list of secondary boot filenames, enter:
(config-boot)# secondary boot-file ?To remove the secondary boot file, enter:
(config-boot)# no secondary boot-fileSpecifying the Secondary Boot Type
Use the secondary boot-type command to specify the secondary boot configuration. The syntax and options for the secondary boot-type command are:
•
•
•
Note
Enter the ftp_record as 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.
To specify the secondary boot type as boot-via-disk, enter:
(config-boot)# secondary boot-type boot-via-diskTo remove the secondary boot type, enter:
(config-boot)# no secondary boot-typeSecondary Boot Configuration Considerations
When you select secondary boot-type boot-via-ftp or secondary boot-type boot-via-network, make sure that you properly connect the Ethernet Management port on the CSS to the network. Note the locations of the Ethernet Management port on the CSS as listed below.
•
•
•
•
When you select secondary boot-type boot-via-network, make sure that you:
•
–
–
–
•
Note
A network boot requires that the CSS 11501, 11503, or 11506 contains an operational disk.
Specifying the Secondary Configuration Path
Use the secondary config-path command to specify the alternate path to a network configuration for the network boot method. An alternate configuration path allows multiple CSSs to use the same boot image while keeping their configuration information in separate directories. The CSS must be able to access the configuration path through an FTP server as defined through the FTP record for the network boot method.
When using an alternate configuration path, make sure that the path leads to a directory containing the script, log, and information subdirectories, and the startup-config file. These subdirectories must contain the files in the corresponding subdirectories of the unzipped boot image. First, create these subdirectories, then copy the files from the boot image to the subdirectories.
Enter the configuration pathname as an unquoted text string with no spaces and a maximum of 64 characters.
To configure the secondary config path, enter:
(config-boot)# secondary config-path f:/bootdir/To remove the secondary network configuration path, enter:
(config-boot)# no secondary config-pathConfiguring a Boot Configuration Record for the Passive SCM
Use the passive command to configure the boot configuration record for the current passive SCM installed in a CSS 11506 or CSS 11800. The boot configuration record consists of the IP address, subnet mask, boot method, and boot file.
Using the sync options for this command, you can copy the boot configuration record from the active SCM to the passive SCM. In most CSS configurations, the active and passive SCMs will have the same boot record.
This command also allows you to configure the individual components of the boot configuration record on the passive SCM. For example, you can configure a boot record on the passive SCM that has a software version that differs from the active SCM. This allows you to run a new software version on the active SCM and have an older software version on the passive SCM.
You can also configure a different IP address on the passive SCM to track an active-to-passive state transition between the SCMs. You can accomplish this through a network management station, where you can receive SNMP host traps.
Note
The options for this boot mode command are:
•
•
•
•
•
•
•
•
•
•
•
•
•
For more information on these options and associated variables, refer to the following sections.
Configuring the Passive SCM IP Address
Use the passive ip address command to configure the boot IP address for the passive SCM. Enter the IP address for the passive SCM that will be used on CSS boot up. Do not enter an all-zero IP address.
For example:
(config-boot)# passive ip address 172.16.3.6To change the passive SCM boot IP address, reenter the passive ip address command.
Configuring the Passive SCM Primary Boot File
Use the passive primary boot-file command to specify the primary boot image for the passive SCM. Enter the filename of the primary boot image for the passive SCM as an unquoted text string with no spaces and a maximum of 64 characters. To display a list of filenames, enter passive primary boot-file ?.
For example:
(config-boot)# passive primary boot-file sg0710002To remove the primary boot file from the passive SCM, enter:
(config-boot)# no passive primary boot-fileConfiguring the Passive SCM Primary Boot Type
Use the passive primary boot-type command to specify the location from which the CSS accesses the primary boot image for the passive SCM upon system reboot or when you download new software. The syntax and options for the passive primary boot-type are:
•
•
•
Note
Enter the ftp_record as 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.
For example:
(config-boot)# passive primary boot-type boot-via-ftp arecordTo remove the primary boot type from the passive SCM, enter:
(config-boot)# no passive primary boot-typeConfiguring the Passive SCM Primary Configuration Path
Use the passive primary config-path command to specify the alternate path to a network configuration for the network boot method for the passive SCM. An alternate configuration path allows multiple CSSs to use the same boot image while keeping their configuration information in separate directories. The CSS must be able to access the configuration path through an FTP server as defined through the FTP record for the network boot method.
When using an alternate configuration path, make sure that the path leads to a directory containing the script, log, and information subdirectories, and the startup-config file. These subdirectories must contain the files in the corresponding subdirectories in the unzipped boot image. First, create these subdirectories, then copy the files from the boot image to the subdirectories.
Enter the configuration path for network configuration. Enter an unquoted text string with no spaces and a maximum of 64 characters. For example:
(config-boot)# passive primary config-path c:/bootdir/To remove the primary network configuration path, enter:
(config-boot)# no passive primary config-pathConfiguring the Passive SCM Secondary Boot File
Use the passive secondary boot-file command to specify the secondary boot image for the passive SCM. Enter the boot file name for the primary boot image as an unquoted text string with no spaces and a maximum of 64 characters. To display a list of boot filenames, enter passive secondary boot-file ?. For example:
(config-boot)# passive secondary boot-file sg0710001To remove the secondary boot file from the passive SCM, enter:
(config-boot)# no passive secondary boot-fileConfiguring the Passive SCM Secondary Boot Type
Use the passive secondary boot-type command to specify the secondary boot configuration for the passive SCM. The secondary boot configuration is used when the primary configuration fails. The syntax and options for the passive secondary boot-type command are:
•
•
•
Note
Enter the ftp_record as 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.
For example:
(config-boot)# passive secondary boot-type boot-via-diskTo remove the secondary boot type from the passive SCM, enter:
(config-boot)# no passive secondary boot-typeConfiguring the Passive SCM Secondary Configuration Path
Use the passive secondary config-path command to specify the secondary alternate path to a network configuration for the network boot method for the passive SCM. An alternate configuration path allows multiple CSSs to use the same boot image while keeping their configuration information in separate directories. The CSS must be able to access the configuration path through an FTP server as defined through the FTP record for the network boot method.
When using an alternate configuration path, make sure that the path leads to a directory containing the script, log, and information subdirectories, and the startup-config file. These subdirectories must contain the files in the corresponding subdirectories of the unzipped boot image. First, create these subdirectories, then copy the files from the boot image to the subdirectories.
Enter the configuration path as an unquoted text string with no spaces and a maximum of 64 characters.
For example:
(config-boot)# passive secondary config-path c:/bootdir/To remove the primary network configuration path, enter:
(config-boot)# no passive secondary config-pathConfiguring the Passive SCM Subnet Mask
Use the passive subnet mask command to configure the system boot subnet mask for the passive SCM.
For example:
(config-boot)# passive subnet mask 255.255.0.0Copying Configuration Information from the Active SCM to the Passive SCM
Use the passive sync command to copy the primary and secondary boot configuration record from the nonvolatile RAM (NVRAM) of the active SCM to the passive SCM. For the CSS 11506, the passive sync command also copies the start configuration and synchromizes the clock time from the active SCM to the passive SCM. This command is available in boot mode.
To synchronize specific boot configuration, startup configuration, or clock time information between the active SCM and the passive SCM in a CSS 11506, use the following passive sync commands:
•
•
•
•
To copy the primary and secondary boot configuration record, startup configuration, and clock time on a CSS 11506, enter:
(config-boot)# passive syncTo copy the boot configuration record from the active SCM to the passive SCM in a CSS 11506, enter:
(config-boot)# passive sync boot-configShowing the Boot Configuration
Use the show boot-config command to display your boot configuration. For example:
(config-boot)# show boot-config!*********************** BOOT CONFIG ***********************ip address 172.16.36.58subnet mask 255.0.0.0primary boot-file sg0710001primary boot-type boot-via-diskBooting the CSS from a Network Drive
The network booting feature enables you to boot the CSS from a network drive using a .zip file of the CSS software version located on www.cisco.com. When you configure a CSS 11050, 11150, or 11800 for network boot, the disk (hard or flash) is not required. To avoid affecting network bandwidth consumption, do not configure logging to disk when booting the CSS from a network drive.
When you configure a CSS 11501, 11503, and 11506 for network boot, the CSS must contain an operational disk (hard or Flash).
Use your customer login and password to access www.cisco.com. From this location, you can access the page listing the network boot .zip file versions of CSS software. Click an image to download it.
Note
Perform a network boot if:
•
When using an alternate configuration path, make sure that the path leads to a directory containing the script, log, and information 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.
•
You can configure network boot for primary and passive SCMs in CSS models 11503, 11506, or 11800, as described in the following sections.
Configuring Network Boot for a Primary SCM
To configure network boot for a primary SCM:
1.
2.
3.
4.
# ftp-record bootrecord 192.168.19.21 bobo encrypted-password "secret" e:/adi_directory/This directory must contain the unzipped files.
5.
(config-boot)# primary boot-type boot-via-network bootrecord6.
(config-boot)# primary config-path e:/adi_directory/Configuring Network Boot for a Passive SCM
To configure network boot for a passive SCM on CSS models 11503, 11506, or 11800:
1.
2.
3.
(config-boot)# passive primary boot-type boot-via-network bootrecordTo display a list of configured ftp records, reenter the command and use "?". For example:
(config-boot)# passive primary boot-type boot-via-network bootrecord ?4.
(config-boot)# primary config-path e:/adi_directory/Showing Network Boot Configurations
To display the network boot configuration, use the show version command. For example:
(config)# show versionVersion: sg0710001 (7.10 Build 1)Network Path: e:/adi_directory/Config Path: e:/adi_directory/Flash (Locked): 7.10 Build 1Flash (Operational):7.10 Build 2Type: PRIMARYLicensed Cmd Set(s):Standard Feature SetEnhanced Feature SetSecure Management
Note
To display network boot configuration information, use the show boot-config command. For example:
(config)# show boot-config!*********************** BOOT CONFIG ***********************secondary config-path e:/adi_directory/secondary boot-type boot-via-network Secondary-Bootprimary boot-file sg0710001primary boot-type boot-via-networksubnet mask 255.0.0.0ip address 192.168.4.226Using the Running-Config and Startup-Config Files
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 contents of the running-config file to the startup-config file to save configuration changes and have the CSS use this configuration on subsequent reboots.
Note
To save the running-config file to the CSS disk, use one of the following commands:
•
•
•
The copy running-config command can also copy the running configuration to an FTP or TFTP server. This command is available in SuperUser mode. The options for this command are:
•
•
•
The copy startup-config command can copy the startup configuration to an FTP or TFTP server. This command is available in SuperUser mode. The options for this command are:
•
•
•
Clearing the Running Configuration and the Startup Configuration
To reset the CSS running configuration 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
For example:
# clear running-configTo reset the startup configuration to the default configuration, use the clear startup-config command in SuperUser mode. This command takes effect upon the next reboot. For example:
# clear startup-configShowing the Running Configuration
To display the CSS running configuration, use the show running-config command. The CSS does not display default configurations in the CSS running configuration. The syntax and options for this command are:
•
•
•
•
•
•
•
•
•
–
–
•
•
•
•
•
•
•
•
•
•
An example of a running-config file is shown below. Comments are preceded by an exclamation point (!). Note that the CSS does not display default values in the CSS running configuration or startup configuration even if you manually enter the values.
# show running-config!************************ GLOBAL **********************ip route 0.0.0.0/0 158.3.7.2!********************** INTERFACE *********************interface e1bridge vlan 2interface e2bridge vlan 2!*********************** CIRCUIT **********************circuit VLAN1ip address 10.3.6.58 255.255.255.0circuit VLAN2ip address 158.3.7.58 255.255.255.0!*********************** SERVICE **********************service serv1ip address 10.3.6.1activeservice serv2ip address 10.3.6.2active!************************ OWNER ***********************owner arrowpoint.comcontent rule1ip address 158.3.7.43protocol tcpport 80add service Serv1add service Serv2activeShowing the Startup Configuration
Once you copy the contents of the running-config file to the startup-config file, use the show startup-config command to display the CSS startup configuration. The CSS does not display default configurations in the startup-config file.
The show startup-config command has two options:
•
•
An example of a CSS startup configuration with line numbers is shown below. Comments are preceded by an exclamation point (!).
# show startup-config line-numbers1. !Generated MAR 6 18:56:112. configure3. !********************** CIRCUIT **********************4. circuit VLAN15. ip address 192.168.2.170 255.255.255.06. ip address 192.168.1.108 255.255.255.07. !********************** SERVICE **********************8. service s19. ip address 192.168.2.410. keepalive type none11. active12. !*********************** OWNER ***********************13. owner rose14. content rule-L315. vip address 192.168.128.10816. add service s117. active18. content rule-L519. add service s120. vip address 192.168.128.10821. url "/*"22. activeCreating a Running Configuration or Startup Configuration Using a Text Editor
If you create a running or startup configuration using a text editor, you must arrange the configuration information in the same order as an automatically created running or startup configuration. The CSS arranges configuration information in the following categories within the running-config and startup-config files:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Though the CSS automatically organizes configuration information, 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 file.
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.
To display the contents of the archive directory, enter show archive ?. Archive files include running configuration and startup configuration files, scripts, and user profiles.
Note
The options for this command are:
•
•
•
•
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:
•
•
Archiving the Running-Config File
Use the archive running-config command to archive the running-config file. 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 of 32 characters. The syntax for this command is:
archive running-config archive_filename
Note
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:
•
•
Archiving the Startup-Config File
Use the archive startup-config command to archive the startup-config 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 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 configuration files. The options for this command are:
•
•
•
Note
For more information on these options and associated variables, see 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:
•
•
The following example restores the log file arrowlog to the log subdirectory and renames it to arrowpointlog.
# restore arrowlog log arrowpointlogRestoring 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:
•
•
The following example restores the script arrowscript to the script subdirectory.
# restore arrowscript scriptRestoring an Archived Startup-Config File
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 syntax is:
restore archive_filename startup-config
The following example restores the archived startup-config file arrowstart as the current startup-config file.
# restore arrowstart startup-configCopying 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. This command is available in SuperUser mode. A core dump occurs when the CSS experiences a fatal error.
Note
The options for this command are:
•
•
To see a list of core dumps, enter the copy core ? command.
Note
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. This command is available in SuperUser mode. For information on configuring an FTP record, see "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 starlogthursThe variables are:
•
•
•
Copying Core Dumps to a TFTP Server
To copy a core dump to an TFTP server, use the copy core tftp command. This command is available in SuperUser mode. The syntax is:
copy core coredump_filename tftp ip_address or hostname filename
The variables are:
•
•
•
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
To display the list of show commands, enter:
(config)# show ?Displaying Software Information
To display the software versions installed on the CSS, use the following commands:
•
•
•
•
Note
For example:
# show versionVersion: sg0710001 (7.10 Build 1)Network Path: e:/adi_directory/Config Path: e:/adi_directory/Flash (Locked): 7.10 Build 1Flash (Operational):7.10 Build 2Type: PRIMARYLicense Cmd Set(s): Standard Feature SetEnhanced Feature SetSSH ServerDisplaying Hardware Information
Use the show chassis command to display a chassis configuration for the CSS. The syntax and options for this command are:
•
•
•
•
•
•
For example, to view a summary of the CS chassis configuration, enter:
# show chassisTable 1-4 describes the fields in the show chassis output.
Table 1-5 describes the fields in the show chassis slot output.
Table 1-6 describes the fields in the show chassis verbose output.
Table 1-7 describes the fields in the show chassis flash output.
Table 1-8 describes the fields in the show chassis inventory output.
Table 1-9 describes the fields in the show chassis session-processors output.
Showing System Resources
Use the show system-resources command to display information about the size of the installed and free memory available on the:
•
•
•
Table 1-10 describes the fields in the show system-resources output.
Use the show system-resources cpu_summary command to display a summary of the CPU utilization by all modules in the CSS 11501, CSS 11503, or CSS 11506 chassis.
Table 1-11 describes the fields in the show system-resources cpu_summary output.
Showing System Uptime
Use the show uptime command to display the length of time the CSS has been running. The time is displayed in hour:minute:second format. For the CSS 11503 or CSS 11506, this command shows the length of time each module has been running. For the CSS 11800, this command also shows the uptime for each SCM and SFM.
To display how long the CSS has been running, enter:
# show uptimeUptime:10 days 03:25:22Showing Disk Information
To view general information about the CSS hard disk or flash disk, use the show disk command. The information includes the total number of clusters on the disk, the free space available, and the number of files, folders, and bad clusters on it.
To display specific 11500 series CSS disk information, use the following show disk commands:
•
•
To display CSS disk information for the disk in slot 0, enter:
# show disk 0Volume: ctotal # of clusters: 32878bytes per cluster: 16384free clusters: 20037bad clusters: 0free bytes: 328286208 (328 MB)max contiguous free bytes: 282689536 (282 MB)files: 1264folders: 66total bytes in files: 195908877lost chains: 0total bytes in lost chains: 0Table 1-12 describes the fields in the show disk output.
Showing User Information
To view CSS operating information related to a single user, or to multiple users, use the show user-database command. This command displays user information related to login privileges, the type of user, and directory access privileges.
To display all users currently defined in the CSS, enter:
(config)# show user-databaseTo display information for a specific user, enter:
(config)# show user-database picardTable 1-13 describes the fields in the show user-database output.
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.
To display currently connected lines or sessions, enter:
(config)# show linesTable 1-14 describes the fields in the show lines output.
Rebooting the CSS
Use the reboot command to reboot the CSS. For example:
(config-boot)# rebootShutting 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:
(config)# boot(config-boot)# shutdownWhere to Go Next
Chapter 2, Configuring Interfaces and Circuits, provides information on how to configure the CSS interfaces and circuits, and bridge interfaces to VLANs.
