-
CSS Administration Guide (Software Version 7.30)
-
Using the CSS Scripting Language
-
Index
-
Preface
-
Booting, Logging In, and Getting Started
-
Configuring CSS Basics
-
Managing the CSS Software
-
Specifying the CSS Boot Configuration
-
Configuring User Profiles
-
Using the CSS Logging Features
-
Configuring the Domain Name Service
-
Configuring Simple Network Management Protocol (SNMP)
-
Configuring Remote Monitoring (RMON)
-
Using an XML Document to Configure the CSS
-
Using the CSS Scripting Language
-
Upgrading Your CSS Software
-
Using the Offline Diagnostic Monitor Menu
-
Troubleshooting the Boot Process
-
Table Of Contents
Specifying the CSS Boot Configuration
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
Secondary Boot Configuration Considerations
Specifying the Secondary Configuration Path
Configuring a Boot Configuration Record for the Passive SCM
Configuring the Passive SCM Gateway Address
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
Specifying the CSS Boot Configuration
This chapter describes how to set the boot configuration, both the primary and secondary boot files, for the CSS. Information in this chapter applies to all CSS models, except where noted.
This chapter contains the following major sections:
•
Specifying the Primary Boot Configuration
•
•
•
•
As an alternate procedure for managing the CSS boot configuration from the CLI, you can use the Offline DM menu. Refer to Appendix B, Using the Offline Diagnostic Monitor Menu, for details.
Boot Setup Quick Start
Table 4-1 provides a quick overview of the steps required to configure the CSS to boot from a primary boot file and from a secondary boot file. Each step includes the CLI command required to complete the task. For a complete description of each feature and all the options associated with the CLI command, see the sections following Table 4-1.
Table 4-1 Boot Setup Quick Start
1.
# ftp-record arrowrecord 192.168.19.21 bobo password "secret" /outgoingNote
2.
(config)# boot3.
(config-boot)# primary boot-file ap0720002(config-boot)# primary boot-type boot-via-ftp arrowrecord4.
(config-boot)# secondary boot-file ap0720001(config-boot)# secondary boot-type boot-via-disk5.
(config-boot)# exit6.
(config)# copy running-config startup-config
Accessing Boot Mode
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)#Specifying the Primary Boot Configuration
You can configure a primary location from which the CSS accesses the boot image. Use the primary command to specify the primary boot configuration. The options for this boot-mode command are as follows:
•
•
•
This section includes the following topics:
•
•
•
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 ap0720002To 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 for this boot mode command is:
primary boot-type [boot-via-disk|boot-via-ftp ftp_record| boot-via-network ftp_record]
The options and variables for this command are as follows:
•
•
•
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. Refer to Chapter 3, Managing the CSS Software, for details on creating an FTP record.
For example, 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 you properly connect the Ethernet Management port on the CSS to the network. The locations of the Ethernet Management port on the CSS are listed below.
•
•
When you select primary boot-type boot-via-network, make sure you:
•
–
–
–
•
Note
A network boot requires that the CSS contains an operational disk.
Specifying the Primary Configuration Path
An alternate configuration path allows multiple CSSs to use the same boot image while keeping their configuration information in separate directories. Use the primary config-path command to specify the alternate path to a network configuration for the network boot method. Note that 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 the path leads to a directory containing the script, log, and information subdirectories, and to the startup-config file. These subdirectories must contain the files in the corresponding subdirectories of the unzipped boot image. First, create these subdirectories on the FTP server, 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 configuration 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
You can configure a secondary location from which the CSS accesses the boot image when the primary boot configuration fails. 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 as follows:
•
•
•
This section includes the following topics:
•
•
•
Specifying the Secondary Boot File
To specify the secondary boot file that the CSS uses when the primary boot configuration fails, use the secondary boot-file command. 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 ap0720001To 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 for this boot mode command is:
secondary boot-type [boot-via-disk|boot-via-ftp ftp_record| boot-via-network ftp_record]
The options and variables for this command are as follows:
•
•
•
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. Refer to Chapter 3, Managing the CSS Software, for details on creating an FTP record.
For example, 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 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 you:
•
–
–
–
•
Note
A network boot requires that the CSS contains an operational disk.
Specifying the Secondary Configuration Path
An alternate configuration path allows multiple CSSs to use the same boot image while keeping their configuration information in separate directories. Use the secondary config-path command to specify the alternate path to a network configuration for the network boot method. Note that 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 the path leads to a directory containing the script, log, and information subdirectories, and to the startup-config file. These subdirectories must contain the files in the corresponding subdirectories of the unzipped boot image. First, create these subdirectories on the FTP server, 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 configuration 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
You can configure the individual components of the boot configuration record on the passive SCM installed in a CSS 11506 chassis. A passive module is a standby module in case of an active module failure. Use the passive command to configure the boot configuration record for the current passive SCM. The boot configuration record consists of the IP address, subnet mask, boot method, and boot file.
Using the sync options for the passive command, copy the boot configuration record from the active SCM to the passive SCM. In most CSS configurations, the active and passive SCMs have the same boot record.
The passive 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. The boot configuration record 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 track active-to-passive state transitions through a network management station, where you can receive SNMP host traps.
The passive command and its options affect only the current passive SCM. When you configure the passive SCM, the set values are loaded in to its NVRAM. If the passive SCM transitions to the active state, it continues to retain these values, but is no longer affected by these commands; boot commands are not saved in the running-config file.
This section includes the following topics:
•
•
•
•
•
•
•
•
•
•
Configuring the Passive SCM Gateway Address
Use the passive gateway address command to configure an Ethernet management port default gateway to load a boot file on a CSS across different subnets for the passive SCM. Enter the IP address for the passive SCM to be used upon CSS boot up. Do not enter an all-zero IP address.
For example:
(config-boot)# passive gateway address 172.16.3.6To change the passive SCM boot gateway address, reenter the passive gateway address command.
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 to be used upon 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 ap0720002To 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 for this boot mode command is:
passive primary boot-type [boot-via-disk|boot-via-ftp ftp_record| boot-via-network ftp_record]
The options and variables for the passive primary boot-type are as follows:
•
•
•
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. Refer to Chapter 3, Managing the CSS Software, for details on creating an FTP record.
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
An alternate configuration path allows multiple CSSs to use the same boot image while keeping their configuration information in separate directories. Use the passive primary config-path command to specify an alternate path to a network configuration for a passive SCM network boot method. Note that 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 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 on the FTP server, 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 name of the boot file 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 ap0720001To 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 for this boot mode command is:
passive secondary boot-type [boot-via-disk|boot-via-ftp ftp_record| boot-via-network ftp_record]
The options and variables for the passive secondary boot-type command are as follows:
•
•
•
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. Refer to Chapter 3, Managing the CSS Software, for details on creating an FTP record.
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
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. Use the passive secondary config-path command to specify the secondary alternate path to a network configuration for a passive SCM 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 on the FTP server, 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
To copy the primary and secondary boot configuration record from NVRAM of the active SCM to the passive SCM, use the passive sync command. For the CSS 11506, the passive sync command also copies the startup- configuration file and synchronizes 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 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 the boot configuration. For example:
(config-boot)# show boot-config!*********************** BOOT CONFIG ***********************ip address 172.16.36.58subnet mask 255.0.0.0primary boot-file ap0720001primary boot-type boot-via-diskBooting the CSS from a Network Drive
Network booting 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 the CSS 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 the software.
Note
Perform a network boot if you want multiple CSSs to use the same boot image while keeping their own configuration information. Provide an alternate path for the location of the configuration information. This information must exist on the same network file system as the boot image.
When using an alternate configuration path, make sure 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.
This section includes the following topics:
•
•
•
Configuring Network Boot for a Primary SCM
To configure network boot for a primary SCM on the CSS 11503 or CSS 11506:
1.
2.
3.
4.
For example:
# 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 the CSS 11503 or CSS 11506:
1.
2.
3.
(config-boot)# passive primary boot-type boot-via-network bootrecordTo display a list of configured FTP records, reenter the command and specify the ? character. 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
Use the show version command to display the network boot configuration. For example:
(config)# show versionVersion: sg0730002 (7.30.0.02)Network Path: e:/adi_directory/Config Path: e:/adi_directory/Flash (Locked): 7.20.0.03Flash (Operational):7.30.0.02Type: 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 sg0730002primary boot-type boot-via-networksubnet mask 255.0.0.0ip address 192.168.4.226Where to Go Next
Chapter 5, Configuring User Profiles, provides information about how to configure CSS user profiles in the default-profile file.
