Cisco 11503 Administration Guide - Page 97

Chapter 2 Specifying the CSS Boot Configuration Configuring a Boot Configuration Record for the Passive SCM For example: (config-boot)# passive primary boot-type boot-via-ftp arecord To remove the primary boot type from the passive SCM, enter: (config-boot)# no passive primary boot-type Configuring 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-path Configuring 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 ap0720001 OL-5647-02 Cisco Content Services Switch Administration Guide 2-13