-
Administration Guide vA1(7), Cisco ACE 4700 Series Application Control Engine Appliance
-
Index
-
Preface
-
Setting Up the ACE
-
Enabling Remote Access to the ACE
-
Managing ACE Software Licenses
-
Configuring Class Maps and Policy Maps
-
Managing the ACE Software
-
Viewing ACE Hardware and Software Configuration Information
-
Configuring Redundant ACE Appliances
-
Configuring SNMP
-
Configuring the XML Interface
-
Upgrading Your ACE Software
-
Feedback
Table Of Contents
Establishing a Console Connection on the ACE
Using the Setup Script to Enable Connectivity to the Device Manager
Connecting and Logging into the ACE
Changing the Administrative Password
Resetting the Administrator CLI Account Password
Configuring an ACE Inactivity Timeout
Configuring a Message-of-the-Day Banner
Configuring the Time, Date, and Time Zone
Setting the System Time and Date
Adjusting for Daylight Saving Time
Viewing the System Clock Settings
Synchronizing the ACE with an NTP Server
Configuring NTP Server and Peer Associations
Viewing NTP Statistics and Information
Configuring Terminal Display Attributes
Configuring Terminal Line Settings
Configuring Console Line Settings
Configuring Virtual Terminal Line Settings
Modifying the Boot Configuration
Setting the Boot Method from the Configuration Register
Setting the BOOT Environment Variable
Configuring the ACE to Bypass the Startup Configuration File During the Boot Process
Displaying the ACE Boot Configuration
Setting Up the ACE
This chapter describes how to initially configure basic settings on the Cisco 4700 Series Application Control Engine (ACE) appliance. It includes the following major sections:
•
Establishing a Console Connection on the ACE
•
•
•
•
•
•
•
•
•
For details on assigning VLANs to the ACE, configuring VLAN interfaces on the ACE, and configuring a default or static route on the ACE, see the Cisco 4700 Series Application Control Engine Appliance Routing and Bridging Configuration Guide.
Establishing a Console Connection on the ACE
You establish a direct serial connection between your terminal or a PC and the ACE by making a serial connection to the console port on the rear panel of the ACE. The ACE has one standard RS-232 serial port found on the rear panel that operates as the console port. The integrated serial port uses a 9-pin male D-shell connector. Use a straight-through cable to connect the switch to a DTE device, such as a terminal or a PC. For instructions on connecting a console cable to your ACE appliance, see the Cisco Application Control Engine Appliance Hardware Installation Guide.
Any device connected to this port must be capable of asynchronous transmission. Connection requires a terminal configured as 9600 baud, 8 data bits, hardware flow control on, 1 stop bit, no parity.
Note
Once connected, use any terminal communications application to access the ACE CLI. The following procedure uses HyperTerminal for Windows.
To access the ACE by using a direct serial connection, perform the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
•
•
•
•
•
Step 7
Step 8
switch login:Once a session is created, choose Save As from the File menu to save the connection description. Saving the connection description has the following two advantages:
•
•
Using the Setup Script to Enable Connectivity to the Device Manager
When you boot the ACE for the first time and the appliance does not detect a startup-configuration file, a setup script appears to guide you through the process of configuring a management VLAN on the ACE through one of its Gigabit Ethernet ports. The primary intent of the setup script is to simplify connectivity to the Device Manager GUI (as described in the Cisco 4700 Series Application Control Engine Appliance Device Manager GUI Quick Configuration Guide).
After you specify a gigabit Ethernet port, port mode, and a management VLAN, the setup script automatically applies the following default configuration:
•
•
•
•
The ACE provides a default answer in brackets [ ] for each question in the setup script. To accept a default configuration prompt, press Enter, and the ACE accepts the setting. To skip the remaining configuration prompts, press Ctrl-C any time during the configuration sequence.
Note
To configure the ACE from the setup script, perform the following steps:
Step 1
Step 2
Step 3
switch login: adminPassword: admin---- Basic System Configuration Dialog ----This setup utility will guide you through the basic configuration of the system. Setup configures only enough connectivity to theACE appliance Device Manager GUI of the system.*Note: setup is mainly used for configuring the system initially,when no configuration is present. So setup always assumes systemdefaults and not the current system configuration values.Press Enter at anytime to skip a dialog. Use ctrl-c at anytimeto skip the remaining dialogs.Would you like to enter the basic configuration dialog (yes/no):
Caution
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
The following configuration will be applied:interface gigabitEthernet 1/1switchport trunk allowed vlan 2no shutaccess-list ALL extended permit ip any anyclass-map type management match-any remote_accessmatch protocol xml-https anymatch protocol icmp anymatch protocol telnet anymatch protocol ssh anymatch protocol http anymatch protocol https anypolicy-map type management first-match first-match remote_mgmt_allow_policyclass remote_accesspermitinterface vlan 2ip address 192.168.1.10 255.255.255.0access-group input ALLservice-policy input remote_mgmt_allow_policyno shutdownip route 0.0.0.0 0.0.0.0 172.16.2.1Step 12
•
•
Step 13
•
•
Step 14
•
•
Connecting and Logging into the ACE
This section describes how to connect to the ACE as the default user from the ACE console port. Once you connect to the ACE as the default user, you can then log in and enter the configuration mode to configure the ACE. Only the Admin context is accessible through the console port; all other contexts can be reached through a Telnet or SSH remote access session.
The ACE creates the following default users at startup: admin, dm, and www.
•
•
Note
•
Later, when you configure interfaces and IP addresses on the ACE itself, you can remotely access the ACE CLI through an ACE interface by using a Telnet or SSH session. To configure remote access to the ACE CLI, see Chapter 2, Enabling Remote Access to the ACE. For details on configuring interfaces on the ACE, see the Cisco 4700 Series Application Control Engine Appliance Routing and Bridging Configuration Guide.
You can configure the ACE to provide a higher level of security for users accessing the ACE. For information about configuring user authentication for login access, see the Cisco 4700 Series Application Control Engine Appliance Security Configuration Guide.
To connect to the ACE and access configuration mode to perform initial configuration, perform the following steps:
Step 1
Step 2
switch login: adminPassword: adminBy default, both the username and password are admin.
The prompt changes to the following:
switch/Admin#To change the default login password, see the "Changing the Administrative Password" section for details.
Note
Caution
Step 3
switch/Admin# configureEnter configuration commands, one per line. End with CNTL/ZThe prompt changes to the following:
switch/Admin(config)#
Changing the Administrative Password
During the initial login process to the ACE, you enter the default user name admin and the default password admin in lowercase text. You cannot modify or delete the default administrative username; however, for security reasons, you must change the administrative password. If you do not change the administrative password, security on your ACE can be compromised because the administrative password is configured to be the same for every ACE shipped from Cisco Systems.
Caution
The administrative username and password are stored in Flash memory. Each time that you reboot the ACE, it reads the username and password from Flash memory. Global administrative status is assigned to the administrative username by default.
Note
To change the default administrative password, use the username command in configuration mode. The syntax of this command is as follows:
username admin [password [0 | 5] {password}]
The keywords, arguments, and options are:
•
•
•
•
•
, . / = + - ^ @ ! % ~ # $ * ( )
Note that the ACE encrypts clear text passwords in the running-config.
For example, to create a user named user1 that uses the clear text password mysecret_801, enter the following command:
switch/Admin(config)# username user1 password 0 mysecret_801To remove the username from the configuration, enter the following command:
switch/Admin(config)# no username user1Resetting the Administrator CLI Account Password
If you forget the password for the ACE administrator account and cannot access the ACE, you can recover the admin password during the initial bootup sequence of the ACE. You must have access to the ACE through the console port to be able to reset the password for the Admin user back to the factory-default value of admin.
Note
To reset the password that allows the Admin user access to the ACE, perform the following steps:
Step 1
Step 2
Step 3
Step 4
Daughter Card Found. Continuing...INIT: Entering runlevel: 3Testing PCI path ....This may take some time, Please wait ....PCI test loop , count 0PCI path is readyStarting services... <<<<< Press ESC when you see this messageEntering setup sequence...Reset Admin password [y/n] (default: n): yResetting admin password to factory default....Starting sysmgr processes.. Please wait...Done!!!switch login:Step 5
The boot process continues as normal and you are able to enter the admin password at the login prompt.
Assigning a Name to the ACE
The hostname is used for the command-line prompts and default configuration filenames. If you establish sessions to multiple devices, the hostname helps you track where you enter commands. By default, the hostname for the ACE is "switch." To specify a hostname for the ACE, use the host configuration mode command.
The syntax of this command is as follows:
hostname name
The name argument specifies a new hostname for the ACE. Enter a case-sensitive text string that contains from 1 to 32 alphanumeric characters.
For example, to change the hostname of the ACE from switch to ACE_1, enter the following command:
switch/Admin(config)# hostname ACE_1ACE_1/Admin(config)#Configuring an ACE Inactivity Timeout
By default, the inactivity timeout value is 5 minutes. You can modify the length of time that can occur before the ACE automatically logs off an inactive user by using the login timeout command in configuration mode. This command specifies the length of time that a user session can be idle before the ACE terminates the console, Telnet, or SSH session.
Note
The syntax for the login timeout command is as follows:
login timeout minutes
The minutes argument specifies the length of time that a user can be idle before the ACE terminates the session. Valid entries are from 0 to 60 minutes. A value of 0 instructs the ACE never to timeout. The default is 5 minutes.
For example, to specify a timeout period of 10 minutes, enter the following command:
host1/Admin(config)# login timeout 10To restore the default timeout value of 5 minutes, enter the following command.
host1/Admin(config)# no login timeoutTo display the configured login time value, use the show login timeout command in Exec mode. For example, enter the following command:
host1/Admin# show login timeoutLogin Timeout 10 minutes.Configuring a Message-of-the-Day Banner
You can configure a message in configuration mode to display as the message-of-the-day banner when a user connects to the ACE. Once connected to the ACE, the message-of-the-day banner appears, followed by the login banner and Exec mode prompt.
The syntax of this command is as follows:
banner motd text
The text argument is a line of message text to be displayed as the message-of-the-day banner. The text string consists of all characters following the first space until the end of the line (carriage return or line feed).
The # character functions as the delimiting character for each line. For the banner text, spaces are allowed but tabs cannot be entered at the CLI. To instruct the ACE to display multiple lines in a message-of -the-day banner, enter a new banner motd command for each line that you wish to add.
The banner message is a maximum of 80 characters per line, up to a maximum of 3000 characters (3000 bytes) total for a message-of-the-day banner. This maximum value includes all line feeds and the last delimiting character in the message.
To add multiple lines in a message-of -the-day banner, precede each line by using the banner motd command. The ACE appends each line to the end of the existing banner. If the text is empty, the ACE adds a carriage return (CR) to the banner.
You can include tokens in the form $(token) in the message text. Tokens will be replaced with the corresponding configuration variable. For example:
•
•
To use the $(hostname) in single line banner motd input, you must include double quotes (") around the $(hostname) so that the $ is interpreted as a special character at the beginning of a variable in the single line. For example:
switch/Admin(config)# banner motd #Welcome to "$(hostname)"...#Do not use the double quote character (") or the percent sign character (%) as a delimiting character in a single line message string.
For multi-line input, double quotes (") are not required for the token because the input mode is different from the single line mode. When you operate in multi-line mode, the ACE interprets the double quote character (") literally. The following example shows how to span multiple lines and uses tokens to configure the banner message:
switch/Admin(config)# banner motd #Enter TEXT message. End with the character '#'.================================Welcome to Admin Context--------------------------------Hostname: $(hostname)Tty Line: $(line)=================================#To replace a banner or a line in a multi-line banner, use the no banner motd command before adding the new lines.
To display the configured banner message, use the show banner motd command in Exec mode as follows:
host1/Admin# show banner motdConfiguring the Time, Date, and Time Zone
To manually configure the date, time, and time zone settings for an ACE, use the clock command.
You can automatically set the date and time of the ACE by synchronizing to a Network Time Protocol (NTP) server. For details, see the "Synchronizing the ACE with an NTP Server" section.
This section includes the following topics:
•
•
•
Setting the System Time and Date
To set the time and the date for an ACE, use the clock set command in Exec mode. When you enter this command, the ACE displays the current configured date and time.
The syntax of this command is as follows:
clock set hh:mm:ss DD MONTH YYYY
The arguments are:
•
•
For example, to specify a time of 1:38:30 and a date of October 7, 2007, enter:
host1/Admin# clock set 01:38:30 7 October 2007Tues Oct 7 01:38:30 PST 2007Follow these guidelines when you use NTP to automatically configure the ACE system clock:
•
•
Setting the Time Zone
To set the time zone for the ACE, use the clock timezone command in configuration mode. The ACE keeps time internally in Universal Time Coordinated (UTC) offset.
The syntax of this command is as follows:
clock timezone {zone_name{+ | -} hours minutes} | {standard timezone}
The keywords, arguments, and options are:
•
•
•
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Table 1-1 lists the common time zone acronyms that you can specify for the zone_name argument.
For example, to set the time zone to PDT and to set an UTC offset of -8 hours, enter:
host1/Admin(config)# clock timezone PDT -8 0To remove the clock timezone setting, use the no form of this command. For example, enter:
host1/Admin(config)# no clock timezoneAdjusting for Daylight Saving Time
To configure the ACE to change the time automatically to summer time (daylight savings time), use the clock summer-time command in configuration mode.
The first part of the command specifies when summer time begins, and the second part of the command specifies when summer time ends. All times are relative to the local time zone; the start time is relative to the standard time and the end time is relative to the summer time. If the starting month is after the ending month, the ACE assumes that you are found in the Southern Hemisphere.
The syntax of this command is as follows:
clock summer-time {daylight_timezone_name start_week start_day start_month start_time end_week end_day end_month end_time daylight_offset | standard timezone}
The keywords, arguments, and options are:
•
•
•
•
•
•
•
–
–
–
–
–
–
For example, to specify that summer time begins on the first Sunday in April at 02:00 and ends on the last Sunday in October at 02:00, with a daylight offset of 60 minutes, enter:
host1/Admin(config)# clock summer-time Pacific 1 Sun Apr 02:00 5 Sun Oct 02:00 60To remove the clock summer-time setting, use the no form of this command. For example, enter:
host1/Admin(config)# no clock summer-timeViewing the System Clock Settings
To display the system clock of the ACE, use the show clock command in Exec mode. The syntax of this command is as follows:
show clock
For example, to view the current clock settings, enter:
host1/Admin# show clockSun Oct 7 07:43:02 UTC 2007Synchronizing the ACE with an NTP Server
The Network Time Protocol (NTP) enables you to synchronize the ACE system clock to a time server. NTP is an Internet protocol designed to synchronize the clocks of computers over a network. Typically, an NTP network receives its time from an authoritative time source, such as a radio clock or an atomic clock attached to a time server, and assures accurate local time-keeping. NTP distributes this time across the network. The NTP protocol can synchronize distributed clocks within milliseconds over long time periods.
NTP runs over User Datagram Protocol (UDP), which runs over IP. NTP is documented in RFC 1305. All NTP communication uses Coordinated Universal Time (UTC), which is the same as Greenwich Mean Time.
An NTP server must be accessible by the client ACE.
Note
This section contains the following topics:
•
•
Configuring NTP Server and Peer Associations
An NTP association can be a peer association, which means that the ACE is willing to synchronize to the other system or to allow the other system to synchronize to the ACE. An NTP association can also be a server association, which means that only this system will synchronize to the other system, not the other way around. You can identify multiple servers; the ACE uses the most accurate server. To configure the ACE system clock to synchronize a peer (or to be synchronized by a peer) or to be synchronized by a time server, use the ntp command.
The syntax of this command is as follows:
ntp {peer ip_address1 [prefer] | server ip_address2 [prefer]}
Note
The keywords, arguments, and options are:
•
•
•
•
•
•
For example, to specify multiple NTP server IP addresses and identify a preferred server, enter:
host1/Admin(config)# ntp server 192.168.10.10 preferhost1/Admin(config)# ntp server 192.168.4.143host1/Admin(config)# ntp server 192.168.5.10For example, to form a peer association with a preferred peer, enter:
host1/Admin(config)# ntp peer 192.168.10.0 preferTo remove an NTP peer or server from the configuration, use the no form of this command. For example:
host1/Admin(config)# no ntp peer 192.168.10.0Viewing NTP Statistics and Information
You can configure the ACE to display the following NTP statistics and information:
•
•
•
•
•
The syntax of this command is as follows:
show ntp {peer-status | peers | statistics [io | local | memory | peer ip_address]
Note
The keywords, arguments, and options are:
•
•
•
•
•
•
•
•
For example, to display the status for all NTP servers and peers, enter:
switch/Admin# show ntp peer-status
Table 1-2 describes the fields in the show ntp peer-status command output.
For example, to display a summary of all peers, enter:
switch/Admin# show ntp peersTable 1-3 describes the fields in the show ntp peers command output.
For example, to display the NTP input/output statistics, enter:
switch/Admin# show ntp statistics ioTable 1-4 describes the fields in the show ntp statistics io command output.
For example, to display the counters maintained by the local NTP, enter:
switch/Admin# show ntp statistics localTable 1-5 describes the fields in the show ntp statistics local command output.
For example, to display the statistic counters related to the memory code, enter:
switch/Admin# show ntp statistics memoryTable 1-6 describes the fields in the show ntp statistics memory command output.
For example, to display the per-peer statistics counter of a peer, enter:
switch/Admin# show ntp statistics peer 192.168.1.2Table 1-7 describes the fields in the show ntp statistics peer command output.
.Clearing NTP Statistics
To clear NTP information, use the clear ntp statistics command in Exec mode. The syntax of this command is as follows:
clear ntp statistics {all-peers | io | local | memory}
The keywords are:
•
•
•
•
For example, to clear the NTP statistics for all peers, enter:
host1/Admin# clear ntp statistics all-peersFor example, to clear the NTP statistics for the I/O devices, enter:
host1/Admin# clear ntp statistics ioFor example, to clear the NTP statistics for the local devices, enter:
host1/Admin# clear ntp statistics localFor example, to clear the NTP statistics for memory, enter:
host1/Admin# clear ntp statistics memoryConfiguring Terminal Settings
You can access the ACE CLI as follows:
•
•
Note
This section contains the following topics:
•
•
For details on configuring remote access to the ACE CLI using SSH or Telnet, see Chapter 2, Enabling Remote Access to the ACE.
Configuring Terminal Display Attributes
You can specify the number of lines and the width for displaying information on a terminal during a console session. The maximum number of displayed screen lines is 511 columns. To configure the terminal display settings, use the terminal command in Exec mode. The terminal command allows you to set the width for displaying command output.
The syntax for the command is as follows:
terminal {length lines | monitor | session-timeout minutes | terminal-type text | width characters}
The keywords, arguments, and options are as follows:
•
•
•
Note
•
•
For example, to specify the VT200 terminal, set the number of screen lines to 35, and set the number of characters to 250, enter:
host1/Admin# terminal terminal-type vt200host1/Admin# terminal length 35host1/Admin# terminal width 250For example, to specify a terminal timeout of 600 minutes for the current session, enter:
host1/Admin# terminal session-timeout 600To reset a terminal setting to its default value, such as the screen line length, use the no form of the command:
host1/Admin# terminal no widthFor example, to start the current terminal monitoring session, enter:
host1/Admin# terminal monitorhost/Admin# %ACE-7-111009: User 'admin' executed cmd: terminal monitor%ACE-7-111009: User 'admin' executed cmd: terminal monitor......To stop the current terminal monitoring session, enter:
host1/Admin# terminal no monitorTo display the console terminal settings, use the show terminal Exec mode command. For example, enter:
host1/Admin# show terminalTTY: /dev/pts/0 Type: "vt100"Length: 25 lines, Width: 80 columnsSession Timeout: 60 minutesConfiguring Terminal Line Settings
This section describes how to configure the terminal line settings for accessing the ACE by a console or a virtual terminal. It includes the following procedures:
•
•
Configuring Console Line Settings
The console port is an asynchronous serial port on the ACE that allows you to directly access the appliance to perform an initial configuration through a standard RS-232 port with an RJ-45 connector. Any device connected to this port must be capable of asynchronous transmission. Connection requires a terminal configured as 9600 baud, 8 data bits, 1 stop bit, no parity.
Use the line console configuration mode command to configure the console interface settings. The CLI displays the console configuration mode.
To configure the line console settings from the console configuration mode, specify one or more of the following commands:
•
•
•
•
For example, to configure the console line settings for the ACE, enter:
host1/Admin# configEnter configuration commands, one per line. End with CNTL/Zhost1/Admin(config)#host1/Admin(config)# line consolehost1/Admin(config-console)# databits 6host1/Admin(config-console)# parity evenhost1/Admin(config-console)# speed 19200host1/Admin(config-console)# stopbits 1To disable a setting for the configured console line, use the no form of the command. For example:
host1/Admin(config-console)# no stopbits 1Use the show line console Exec mode command to verify the configured console settings for the ACE.
The syntax for this command is as follows:
show line console [connected]
The optional connected keyword displays the physical connection status.
For example, to display the configured console settings, enter:
host1/Admin# show line consoleline Console:Speed: 9600 baudsDatabits: 8 bits per byteStopbits: 1 bit(s)Parity: noneConfiguring Virtual Terminal Line Settings
Virtual terminal lines allow remote access to the ACE. A virtual terminal line is not associated with the console port; instead, it is a virtual port that allows you to access the ACE.
Use the line vty configuration mode command to configure the virtual terminal line settings. The CLI displays the line configuration mode. Use the session-limit command to configure the maximum number of terminal sessions per line.
The syntax for this command is as follows:
session-limit number
The number argument configures the maximum number of terminal sessions per line. The range is from 1 to 251.
For example, to configure a virtual terminal line, enter:
host1/Admin# configEnter configuration commands, one per line. End with CNTL/Zhost1/Admin(config)#host1/Admin(config)# line vtyhost1/Admin(config-line)# session-limit 23To disable a setting for the configured virtual terminal line, use the no form of the command. For example:
host1/Admin(config-line)# no session-limit 23Use the clear line command in Exec mode to close a specified vty session. The syntax for this command is as follows:
clear line vty_name
The vty_name argument specifies the name of the VTY session. Enter a maximum of 64 characters for the name of the virtual terminal.
For example, to close a specified vty session, enter:
host1/Admin# clear line vty vty1Modifying the Boot Configuration
You can control how the ACE performs its boot process. You can instruct the ACE to automatically boot the system image identified in the BOOT environment variable or you can manually identify the system boot image to use. In addition, you can choose to have the ACE load the startup-configuration file or ignore the startup-configuration file upon reboot.
This section describes how to modify the boot configuration of the ACE. It contains the following procedures:
•
•
•
•
Setting the Boot Method from the Configuration Register
The configuration register can be used to modify how the ACE performs its boot process, automatically or manually.
You can modify the boot method that the ACE uses at the next startup by setting the boot field in the software configuration register. The configuration register identifies how the ACE should boot.
To specify the configuration register boot setting, use the config-register configuration command. This command affects only the configuration register bits that control the boot field and leaves the remaining bits unaltered.
The syntax for the command is as follows:
config-register value
The supported value entries are as follows:
•
•
To set the boot field in the configuration register to automatically boot the system image identified in the BOOT environment variable upon reboot and to load the startup-configuration file stored in Flash memory, enter:
host1/Admin(config)# config-register 0x1To reset the config-register setting, enter:
host1/Admin(config)# no config-register 0x1Press Esc when the count down initiates on the GNU GRUB multiboot loader. The following GRUB menu appears.GNU GRUB version 0.95 (639K lower / 3144640K upper memory)*********************************************************************** image(c4710ace-mz.3.0.0_AB0_0.453.bin) ** image(c4710ace-mz.3.0.0_AB0_0.488.bin) *** ** **********************************************************************In the GRUB menu, use the arrow keys to select from the ACE images loaded in the Flash memory. The ACE image entry is highlighted in the list.
Perform one of the following actions:
•
•
•
If no ACE images are loaded in the Flash memory, the GNU GRUB multiboot loader appears as follows:
grub>Setting the BOOT Environment Variable
The BOOT environment variable specifies a list of image files on various devices from which the ACE can boot at startup. You can add several images to the BOOT environment variable to provide a fail-safe boot configuration. If the first file fails to boot the ACE, subsequent images that are specified in the BOOT environment variable are tried until the ACE boots or there are no additional images to attempt to boot. If there is no valid image to boot, the ACE enters ROMMON mode where you can manually specify an image to boot.
The ACE stores and executes images in the order in which you added them to the BOOT environment variable. If you want to change the order in which images are tried at startup, you can either prepend and clear images from the BOOT environment variable to attain the desired order or you can clear the entire BOOT environment variable and then redefine the list in the desired order.
To set the BOOT environment variable, use the boot system image: command. The syntax for this command is as follows:
boot system image:image_name
The image_name argument specifies the name of the system image file. If the file does not exist (for example, if you entered the wrong filename), then the filename is appended to the bootstring, and this message displays, "Warning: File not found but still added in the bootstring." If the file does exist, but is not a valid image, the file is not added to the bootstring, and the message "Warning: file found but it is not a valid boot image" displays.
For example, to set the BOOT environment variable, enter:
host1/Admin(config)# boot system image:c4710ace-mz.3.0.0_AB0_0.488.binConfiguring the ACE to Bypass the Startup Configuration File During the Boot Process
From the GRUB bootloader, the ACE includes an option that allows you to instruct the ACE to bypass the startup-configuration file stored on the appliance in the Flash memory (nonvolatile memory) during the boot process. You may require the ACE to bypass the startup configuration file during bootup in the following instances:
•
•
Note
To instruct the ACE to bypass the startup-configuration file during the boot process from the GRUB bootloader, perform the following steps:
1.
2.
3.
GNU GRUB version 0.95 (639K lower / 3144640K upper memory)******************************************************************* image(c4710ace-mz.3.0.0_AB0_0.453.bin) ** image(c4710ace-mz.3.0.0_AB0_0.488.bin) *** ** ******************************************************************4.
5.
6.
7.
kernel=(hd0,0)/ACE_APPLIANCE_RECOVERY_IMAGE.bin ro root=LABEL=/ auto console=tt yS0,9600n8 quiet bigphysarea=32768 ignorestartupcfg=1 [Linux-bzImage, setup=0x1400, size=0x43ff5d2]IP-Config: Incomplete network configuration information. INIT: version 2.85 bootingINIT: Entering runlevel: 3 Testing PCI path .... This may take some time, Please wait .... PCI test loop , count 0 PCI path is ready Starting services... .Starting sysmgr processes.. Please wait...Done!!!switch login: adminPassword: admin---- Basic System Configuration Dialog ----This setup utility will guide you through the basic configuration ofthe system. Setup configures only enough connectivity to theACE appliance Device Manager GUI of the system.*Note: setup is mainly used for configuring the system initially,when no configuration is present. So setup always assumes systemdefaults and not the current system configuration values.Press Enter at anytime to skip a dialog. Use ctrl-c at anytimeto skip the remaining dialogs.Would you like to enter the basic configuration dialog (yes/no):noCisco Application Control Software (ACSW)TAC support: http://www.cisco.com/tacCopyright (c) 1985-2007 by Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained herein are owned byother third parties and are used and distributed under license.Some parts of this software are covered under the GNU PublicLicense. A copy of the license is available athttp://www.gnu.org/licenses/gpl.html.
Note
You may now configure the ACE to define basic configuration settings for the appliance.
Displaying the ACE Boot Configuration
To display the current BOOT environment variable and configuration register setting, use the show bootvar command in Exec mode.
For example, to display the BOOT environment variable settings, enter:
host1/Admin# show bootvarBOOT variable = "image:/c4710ace-mz.3.0.0_AB0_0.488.bin;image:/c4710ace-mz.3.0.0_AB0_0.453.bin"Configuration register is 0x1Restarting the ACE
To reboot the ACE directly from its CLI and reload the configuration, use the reload command in Exec mode. The reload command reboots the ACE and performs a full power cycle of both the hardware and software. The reset process can take several minutes. Any open connections with the ACE are dropped after you enter the reload command.
Caution
When you specify reload, the ACE prompts you for confirmation and performs a cold restart of the ACE:
host1/Admin# reloadThis command will reboot the systemSave configurations for all the contexts. Save? [yes/no]: yesGenerating configuration....running config of context Admin savedPerform system reload. [yes/no]: [yes] yesShutting Down the ACE
To remove power from the ACE, press the power button found on the front panel.
Caution
