- Preface
- Getting Started
- Configuring Dashboards
- Using the Startup Wizard
- Setting Up the Sensor
- Configuring Interfaces
- Configuring Policies
- Defining Signatures
- Using the Signature Wizard
- Configuring Event Action Rules
- Configuring Anomaly Detection
- Configuring Global Correlation
- Configuring SSH and Certificates
- Configuring Attack Response Controller for Blocking and Rate Limiting
- Managing Time-Based Actions
- Configuring SNMP
- Configuring External Product Interfaces
- Managing the Sensor
- Monitoring the Sensor
- Initializing the Sensor
- Logging In to the Sensor
- Understanding Cisco IPS Software
- Upgrading, Downgrading, and Installing System Images
- System Architecture
- Signature Engines
- Troubleshooting
- Open Source License Files
- Glossary
- Index
Cisco Intrusion Prevention System Device Manager Configuration Guide for IPS 7.1
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- April 4, 2011
Chapter: Upgrading, Downgrading, and Installing System Images
- Understanding Upgrades, Downgrades, and System Images
- Supported FTP and HTTP/HTTPS Servers
- Upgrading the Sensor
- Configuring Automatic Upgrades
- Downgrading the Sensor
- Recovering the Application Partition
- Installing System Images
- ROMMON
- TFTP Servers
- Connecting an Appliance to a Terminal Server
- Installing the IPS4240 and IPS4255 System Images
- Installing the IPS4260 System Image
- Installing the IPS4270-20 System Image
- Installing the IPS4345 and IPS4360 System Images
- Installing the IPS4510 and IPS4520 System Images
- Installing the ASA 5500 AIP SSM System Image
- Installing the ASA 5500-X IPS SSP System Image
- Installing the ASA 5585-X IPSSSP System Image
Upgrading, Downgrading, and Installing System Images
This chapter describes how to upgrade, downgrade, and install system images. It contains the following sections:
Understanding Upgrades, Downgrades, and System Images
Note
After you upgrade any IPS software on your sensor, you must restart the IDM to see the latest software features.
Note You cannot downgrade the sensor using the recovery partition. To downgrade to an earlier version, you must install the appropriate system image file (.img file).
Note During a signature upgrade all signature configurations are retained, both the signature tunings as well as the custom signatures. During a signature downgrade the current signature configuration is replaced with the old signature configuration. So if the last signature set had custom signatures and/or signature tunings, these are restored during the downgrade.
You can upgrade and downgrade the software on the sensor. Upgrading applies a service pack, signature update, signature engine update, minor version, major version, or recovery partition file. Downgrading removes the last applied service pack or signature update from the sensor.
You can recover the application partition image on your sensor if it becomes unusable. Using the recover command lets you retain your host settings while other settings revert to the factory defaults.
To install a new system image on the sensor, use ROMMON, the bootloader file, or the maintenance partition depending on which platform you have. When you install a new system image on your sensor, all accounts are removed and the default cisco account is reset to use the default password cisco . After installing the system image, you must initialize the sensor again.
After you reimage and initialize your sensor, upgrade your sensor with the most recent service pack, signature update, signature engine update, minor update, major update, and recovery partition files.
- For the procedure for initializing the sensor, see Initializing the Sensor.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
Supported FTP and HTTP/HTTPS Servers
The following FTP servers are supported for IPS software updates:
- WU-FTPD 2.6.2 (Linux)
- Solaris 2.8
- Sambar 6.0 (Windows 2000)
- Serv-U 5.0 (Windows 2000)
- MS IIS 5.0 (Windows 2000)
The following HTTP/HTTPS servers are supported for IPS software updates:
- For the procedure for downloading IPS software updates from Cisco.com, see Obtaining Cisco IPS Software.
- For the procedure for configuring automatic updates, see Configuring Automatic Upgrades.
Upgrading the Sensor
Note For the IDM procedure for upgrading the sensor, see Manually Updating the Sensor.
This section explains how to use the upgrade command to upgrade the software on the sensor. It contains the following topics:
- IPS 7.1 Upgrade Files
- Upgrade Notes and Caveats
- Manually Upgrading the Sensor
- Upgrading the Recovery Partition
IPS 7.1 Upgrade Files
The currently supported IPS 7.1( x ) versions are 7.1(1)E4, 7.1(2)E4, 7.1(3)E4, and 7.1(4)E4, 7.1(5)E4, 7.1(6)E4, 7.1(7)E4, and 7.1(8)E4. All IPS sensors are not supported in each 7.1( x ) version.
For a list of the specific IPS filenames and the IPS versions that each sensor supports, refer to the Release Notes for your IPS version found at this URL:
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/prod_release_notes_list.html
For the procedure for obtaining these files on Cisco.com, see Obtaining Cisco IPS Software .
Upgrade Notes and Caveats
For a list of the upgrade notes and caveats for each IPS version, refer to the Release Notes for your IPS version found at this URL:
http://www.cisco.com/en/US/products/hw/vpndevc/ps4077/prod_release_notes_list.html
Manually Upgrading the Sensor
Note During a signature upgrade all signature configurations are retained, both the signature tunings as well as the custom signatures. During a signature downgrade the current signature configuration is replaced with the old signature configuration. So if the last signature set had custom signatures and/or signature tunings, these are restored during the downgrade.
Note Do not change the filename. You must preserve the original filename for the sensor to accept the update.
Use the upgrade source-url command to apply service pack, signature update, engine update, minor version, major version, or recovery partition file upgrades. The following options apply:
– ftp:—Source URL for an FTP network server. The syntax for this prefix is:
ftp://[[username@]location][/relativeDirectory]/filename
ftp://[[username@]location][//absoluteDirectory]/filename
Note You are prompted for a password.
– scp:—Source URL for the SCP network server. The syntax for this prefix is:
scp://[[username@]location][/relativeDirectory]/filename
scp://[[username@]location][//absoluteDirectory]/filename
Note You are prompted for a password. You must add the remote host to the SSH known hosts list.
– http:—Source URL for the web server. The syntax for this prefix is:
http://[[username@]location][/directory]/filename
Note The directory specification should be an absolute path to the desired file.
– https:—Source URL for the web server. The syntax for this prefix is:
https://[[username@]location][/directory]/filename
Note The directory specification should be an absolute path to the desired file. The remote host must be a TLS trusted host.
Note The CLI output is an example of what your configuration may look like. It will not match exactly due to the optional setup choices, sensor model, and IPS 7.1 version you have installed.
To upgrade the sensor, follow these steps:
Download the appropriate file to an FTP, SCP, HTTP, or HTTPS server that is accessible from your sensor.
Step 2 Log in to the CLI using an account with administrator privileges.
Step 3 Enter configuration mode.
The URL points to where the update file is located, for example, to retrieve the update using FTP, enter the following:
Step 5 Enter the password when prompted.
Step 6 Enter yes to complete the upgrade.
Note Major updates, minor updates, and service packs may force a restart of the IPS processes or even force a reboot of the sensor to complete installation.
Note The operating system is reimaged and all files that have been placed on the sensor through the service account are removed.
Step 7 Verify your new sensor version.
- For the IDM procedure for upgrading the sensor, see Manually Updating the Sensor.
- For a list of supported FTP and HTTP/HTTPS servers, see Supported FTP and HTTP/HTTPS Servers.
- For the procedure for locating software on Cisco.com and for obtaining an account with cryptographic privileges, see Obtaining Cisco IPS Software.
Upgrading the Recovery Partition
Note Recovery partition images are generated for major and minor updates and only in rare situations for service packs or signature updates.
Note You cannot downgrade the sensor using the recovery partition. To downgrade to an earlier version, you must install the appropriate system image file (.img file).
Use the upgrade command to upgrade the recovery partition with the most recent version so that it is ready if you need to recover the application partition on your sensor. Recovery partition images are generated for major and minor updates and only in rare situations for service packs or signature updates.
To upgrade the recovery partition on your sensor, follow these steps:
Download the appropriate recovery partition image file to an FTP, SCP, HTTP, or HTTPS server that is accessible from your sensor.
Step 2 Log in to the CLI using an account with administrator privileges.
Step 3 Enter configuration mode.
Step 4 Upgrade the recovery partition.
Step 5 Enter the server password. The upgrade process begins.
Note This procedure only reimages the recovery partition. The application partition is not modified by this upgrade. To reimage the application partition after the recovery partition, use the recover application-partition command.
- For a list of supported FTP and HTTP/HTTPS servers, see Supported FTP and HTTP/HTTPS Servers.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
- For the procedure for using the recover command, see Recovering the Application Partition.
Configuring Automatic Upgrades
This section describes how to configure the sensor to automatically look for upgrades in the upgrade directory. It contains the following topics:
Understanding Automatic Upgrades
You can configure the sensor to look for new upgrade files in your upgrade directory automatically. For example, several sensors can point to the same remote FTP server directory with different update schedules, such as every 24 hours, or Monday, Wednesday, and Friday at 11:00 pm.
You specify the following information to schedule automatic upgrades:
- Server IP address
- Path of the directory on the file server where the sensor checks for upgrade files
- File copy protocol (SCP or FTP)
- Username and password
- Upgrade schedule
You must download the software upgrade from Cisco.com and copy it to the upgrade directory before the sensor can poll for automatic upgrades.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
- For the procedure for adding the SCP server to the SSH known hosts list, see Defining Known Host RSA Keys.
Using the auto-upgrade Command
Use the auto-upgrade-option enabled command in the service host submode to configure automatic upgrades. The following options apply:
- cisco-server —Enables automatic signature and engine updates from Cisco.com.
- cisco-url —Specifies the Cisco server locator service. You do not need to change this unless the www.cisco.com IP address changes.
- default — Sets the value back to the system default setting.
- directory — Specifies the directory where upgrade files are located on the file server. A leading ‘/’ indicates an absolute path.
- file-copy-protocol — Specifies the file copy protocol used to download files from the file server. The valid values are ftp or scp .
Note If you use SCP, you must use the ssh host-key command to add the server to the SSH known hosts list so the sensor can communicate with it through SSH.
- ip-address —Specifies the IP address of the file server.
- password —Specifies the user password for Cisco server authentication.
- schedule-option —Specifies the schedules for when Cisco server automatic upgrades occur. Calendar scheduling starts upgrades at specific times on specific days. Periodic scheduling starts upgrades at specific periodic intervals.
– calendar-schedule —Configures the days of the week and times of day that automatic upgrades will be performed.
– days-of-week —Specifies the days of the week on which auto-upgrades will be performed. You can select multiple days: sunday through saturday are the valid values.
– no —Removes an entry or selection setting.
– times-of-day —Specifies the times of day at which auto-upgrades will begin. You can select multiple times. The valid value is hh:mm[:ss] .
– periodic-schedule —Specifies the time that the first automatic upgrade should occur, and how long to wait between automatic upgrades.
– interval —Specifies the number of hours to wait between automatic upgrades. Valid values are 0 to 8760.
– start-time —Specifies the time of day to start the first automatic upgrade. The valid value is hh:mm[:ss] .
- user-name —Specifies the username for server authentication.
- user-server —Enables automatic upgrades from a user-defined server.
Configuring Automatic Upgrades
If you get an unauthorized error message while configuring an automatic update, make sure you have the correct ports open on any firewalls between the sensor and Cisco.com. For example, you need port 443 for the initial automatic update connection to www.cisco.com, and you need port 80 to download the chosen package from a Cisco file server. The IP address may change for the Cisco file server, but you can find it in the lastDownloadAttempt section in the output of the show statistics host command.
Note To check the status of the last automatic update or the next scheduled automatic update, run the show statistics host command and check the Auto Update Statistics section.
To schedule automatic upgrades, follow these steps:
Log in to the CLI using an account with administrator privileges.
Step 2 Enter automatic upgrade submode.
Step 3 Configure the sensor to automatically look for new upgrades either on Cisco.com or on your file server:
a. On Cisco.com. Continue with Step 4.
c. Specify the IP address of the file server.
d. Specify the directory where the upgrade files are located on the file server.
e. Specify the file server protocol.
Note If you use SCP, you must use the ssh host-key command to add the server to the SSH known hosts list so the sensor can communicate with it through SSH.
Step 4 Specify the username for authentication.
Step 5 Specify the password of the user.
Step 6 Specify the scheduling:
a. For calendar scheduling (starts upgrades at specific times on specific day):
b. For periodic scheduling (starts upgrades at specific periodic intervals):
Step 8 Exit automatic upgrade submode.
Step 9 Press Enter to apply the changes or type no to discard them.
- For the IDM procedure for automatically upgrading the sensor, see Configuring Automatic Update.
- For a list of supported FTP and HTTP/HTTPS servers, see Supported FTP and HTTP/HTTPS Servers.
- For the procedure for adding the SCP server to the SSH known hosts list, see Defining Known Host RSA Keys.
Downgrading the Sensor
Note You cannot downgrade the sensor using the recovery partition. To downgrade to an earlier version, you must install the appropriate system image file (.img file).
Use the downgrade command to remove the last applied signature upgrade or signature engine upgrade from the sensor. To remove the last applied signature update or signature engine update from the sensor, follow these steps:
Log in to the sensor using an account with administrator privileges.
Step 2 Enter global configuration mode.
Step 3 If there is no recently applied service pack or signature update, the downgrade command is not available.
Recovering the Application Partition
You can recover the application partition image for the sensor if it becomes unusable. Some network configuration information is retained when you use this method, which lets you have network access after the recovery is performed. Use the recover application-partition command to boot to the recovery partition, which automatically recovers the application partition on your sensor. If you have upgraded your recovery partition to the most recent version before you recover the application partition image, you can install the most up-to-date software image.
Because you can execute the recover application-partition command through a Telnet or SSH connection, we recommend using this command to recover sensors that are installed at remote locations.
Note When you reconnect to the sensor after recovery, you must log in with the default username and password cisco.
Recovering the Application Partition Image
To recover the application partition image, follow these steps:
Download the recovery partition image file to an FTP, HTTP, or HTTPS server that is accessible from your sensor.
Step 2 Log in to the CLI using an account with administrator privileges.
Step 3 Enter configuration mode.
Note To upgrade the recovery partition the sensor must already be running the current IPS 7.1 software.
Step 4 Recover the application partition image.
Step 5 Enter yes to continue. Shutdown begins immediately after you execute the recover command. Shutdown can take a while, and you will still have access to the CLI, but access will be terminated without warning.
The application partition is reimaged using the image stored on the recovery partition. You must now initialize the sensor with the setup command.The IP address, netmask, access lists, time zone, and offset are saved and applied to the reimaged application partition. If you executed the recover application-partition command remotely, you can SSH to the sensor with the default username and password ( cisco / cisco ) and then initialize the sensor again with the setup command. You cannot use Telnet until you initialize the sensor because Telnet is disabled by default.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
- For the procedure for using the setup command, see Initializing the Sensor.
- For the procedure for upgrading the recovery partition to the most recent version, see Upgrading the Recovery Partition.
Installing System Images
This section contains the procedures for installing system images on the appliances and modules. It contains the following topics:
- ROMMON
- TFTP Servers
- Connecting an Appliance to a Terminal Server
- Installing the IPS 4240 and IPS 4255 System Images
- Installing the IPS 4260 System Image
- Installing the IPS 4270-20 System Image
- Installing the IPS 4345 and IPS 4360 System Images
- Installing the IPS 4510 and IPS 4520 System Images
- Installing the ASA 5500 AIP SSM System Image
- Installing the ASA 5500-X IPS SSP System Image
- Installing the ASA 5585-X IPS SSP System Image
For the procedure for using the recover application-partition command, see Recovering the Application Partition.
ROMMON
Some Cisco sensors include a preboot CLI called ROMMON, which lets you boot images on sensors where the image on the primary device is missing, corrupt, or otherwise unable to boot the normal application. ROMMON is particularly useful for recovering remote sensors as long as the serial console port is available.
Access to ROMMON is available only through the serial console port, a Cisco-standard asynchronous RS-232C DTE available in an RJ-45F connector on the sensor chassis. The serial port is configured for 9600 baud, 8 data bits, 1 stop bit, no parity, and no flow control.
For the procedure for using a terminal server, see Connecting an Appliance to a Terminal Server.
TFTP Servers
ROMMON uses TFTP to download an image and launch it. TFTP does not address network issues such as latency or error recovery. It does implement a limited packet integrity check so that packets arriving in sequence with the correct integrity value have an extremely low probability of error. But TFTP does not offer pipelining so the total transfer time is equal to the number of packets to be transferred times the network average RTT. Because of this limitation, we recommend that the TFTP server be located on the same LAN segment as the sensor. Any network with an RTT less than a 100 milliseconds should provide reliable delivery of the image. Be aware that some TFTP servers limit the maximum file size that can be transferred to ~32 MB.
Connecting an Appliance to a Terminal Server
A terminal server is a router with multiple, low speed, asynchronous ports that are connected to other serial devices. You can use terminal servers to remotely manage network equipment, including appliances.
To set up a Cisco terminal server with RJ-45 or hydra cable assembly connections, follow these steps:
Connect to a terminal server using one of the following methods:
- For terminal servers with RJ-45 connections, connect a rollover cable from the console port on the appliance to a port on the terminal server.
- For hydra cable assemblies, connect a straight-through patch cable from the console port on the appliance to a port on the terminal server.
Step 2 Configure the line and port on the terminal server. In enable mode, enter the following configuration, where # is the line number of the port to be configured.
Step 3 Be sure to properly close a terminal session to avoid unauthorized access to the appliance. If a terminal session is not stopped properly, that is, if it does not receive an exit(0) signal from the application that initiated the session, the terminal session can remain open. When terminal sessions are not stopped properly, authentication is not performed on the next session that is opened on the serial port.
Installing the IPS 4240 and IPS 4255 System Images
Note This procedure is for the IPS 4240, but is also applicable to the IPS 4255. The system image for the IPS 4255 has “4255” in the filename.
You can install the IPS 4240 and IPS 4255 system image by using the ROMMON on the appliance to TFTP the system image onto the compact flash device.
To install the IPS 4240 and IPS 4255 system image, follow these steps:
Download the IPS 4240 system image file to the tftp root directory of a TFTP server that is accessible from your IPS 4240.
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of your IPS 4240.
Step 3 Press Break or Esc at the following prompt while the system is booting to interrupt boot. Press the spacebar to begin boot immediately.
Note You have ten seconds to press Break or Esc.
The system enters ROMMON mode. The rommon> prompt appears.
Step 4 Check the current network settings.
The variables have the following definitions:
- Address—Local IP address of the IPS 4240
- Server—TFTP server IP address where the application image is stored
- Gateway—Gateway IP address used by the IPS 4240
- Port—Ethernet interface used for the IPS 4240 management
- VLAN—VLAN ID number (leave as untagged)
- Image—System image file/path name
- Config—Unused by these platforms
Note Not all values are required to establish network connectivity. The address, server, gateway, and image values are required. If you are not sure of the settings needed for your local environment, contact your system administrator.
Step 5 If necessary, change the interface used for the TFTP download.
Note The default interface used for TFTP downloads is Management 0/0, which corresponds to the MGMT interface of the IPS 4240.
Step 6 If necessary, assign an IP address for the local port on the IPS 4240.
Note Use the same IP address that is assigned to the IPS 4240.
Step 7 If necessary, assign the TFTP server IP address.
Step 8 If necessary, assign the gateway IP address.
Step 9 Verify that you have access to the TFTP server by pinging it from your local Ethernet port with one of the following commands.
Step 10 If necessary define the path and filename on the TFTP file server from which you are downloading the image.
Note The path is relative to the default tftpboot directory of the UNIX TFTP server. Images located in the default tftpboot directory do not have any directory names or slashes in the IMAGE specification.
Step 11 Enter set and press Enter to verify the network settings.
Note You can use the sync command to store these settings in NVRAM so they are maintained across boots. Otherwise, you must enter this information each time you want to boot an image from ROMMON.
Step 12 Download and install the system image.
Note If the network settings are correct, the system downloads and boots the specified image on the IPS 4240. Be sure to use the IPS 4240 image.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
Installing the IPS 4260 System Image
You can install the IPS 4260 system image by using the ROMMON on the appliance to TFTP the system image onto the flash device.
To install the IPS 4260 system image, follow these steps:
Download the IPS 4260 system image file to the tftp root directory of a TFTP server that is accessible from your IPS 4260.
Make sure you can access the TFTP server location from the network connected to your IPS 4260 Ethernet port.
Step 3 Press Ctrl-R at the following prompt while the system is booting.
Note You have five seconds to press Ctrl-R.
Step 4 If necessary, change the port used for the TFTP download.
The port in use is listed just after the platform identification. In the example, port Management 0/0 is being used.
Note The default port used for TFTP downloads is Management 0/0, which corresponds with the command and control (MGMT) interface of the IPS 4260.
Note Ports Management 0/0 (MGMT) and GigabitEthernet 0/1 (GE 0/1) are labeled on the back of the chassis.
Step 5 Specify an IP address for the local port on the IPS 4260.
Note Use the same IP address that is assigned to the IPS 4260.
Step 6 Specify the TFTP server IP address.
Step 7 Specify the gateway IP address.
Step 8 Verify that you have access to the TFTP server by pinging it from the local Ethernet port.
Step 9 Specify the path and filename on the TFTP file server from which you are downloading the image.
Note The path is relative to the default tftpboot directory of the UNIX TFTP server. Images located in the default tftpboot directory do not have any directory names or slashes in the file location.
Step 10 Download and install the system image.
Note The IPS 4260 reboots once during the reimaging process. Do not remove power from the IPS 4260 during the update process or the upgrade can become corrupted.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
Installing the IPS 4270-20 System Image
You can install the IPS 4270-20 system image by using the ROMMON on the appliance to TFTP the system image onto the compact flash device.
To install the IPS 4270-20 system image, follow these steps:
Download the IPS 4270-20 system image file to the tftp root directory of a TFTP server that is accessible from your IPS 4270-20.
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of your IPS 4270-20.
Note The controller type errors are a known issue and can be disregarded.
Step 3 Press Break or Esc at the following prompt while the system is booting to interrupt boot. Press the spacebar to begin boot immediately.
Note You have ten seconds to press Break or Esc.
The system enters ROMMON mode. The rommon> prompt appears.
Step 4 Check the current network settings.
The variables have the following definitions:
- Address—Specifies the local IP address of the IPS 4270-20.
- Server—Specifies the TFTP server IP address where the application image is stored.
- Gateway—Specifies the gateway IP address used by the IPS 4270-20.
- Port—Specifies the Ethernet interface used for IPS 4270-20 management.
- VLAN—Specifies the VLAN ID number (leave as untagged).
- Image—Specifies the system image file/path name.
- Config—Unused by these platforms.
Note Not all values are required to establish network connectivity. The address, server, gateway, and image values are required. If you are not sure of the settings needed for your local environment, contact your system administrator.
Step 5 If necessary, assign an IP address for the local port on the IPS 4270-20.
Note Use the same IP address that is assigned to the IPS 4270-20.
Step 6 If necessary, assign the TFTP server IP address.
Step 7 If necessary, assign the gateway IP address.
Step 8 Verify that you have access to the TFTP server by pinging it from your local Ethernet port with one of the following commands:
Step 9 If necessary define the path and filename on the TFTP file server from which you are downloading the image.
Note The path is relative to the UNIX TFTP server default tftpboot directory. Images located in the default tftpboot directory do not have any directory names or slashes in the IMAGE specification.
Step 10 Enter set and press Enter to verify the network settings.
Note You can use the sync command to store these settings in NVRAM so they are maintained across boots. Otherwise, you must enter this information each time you want to boot an image from ROMMON.
Step 11 Download and install the system image.
Note If the network settings are correct, the system downloads and boots the specified image on the IPS 4270-20. Be sure to use the IPS 4270-20 image.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
Installing the IPS 4345 and IPS 4360 System Images
Note This procedure is for IPS 4345, but is also applicable to IPS 4360. The system image for IPS 4360 has “4360” in the filename.
You can install the IPS 4345 and IPS 4360 system image by using the ROMMON on the appliance to TFTP the system image on to the compact flash device.
To install the IPS 4345 and IPS 4360 system image, follow these steps:
Download the IPS 4345 system image file to the tftp root directory of a TFTP server that is accessible from your IPS 4345.
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of your IPS 4345.
Step 3 Press Break or Esc at the following prompt while the system is booting to interrupt boot. Press the spacebar to begin boot immediately.
Note You have ten seconds to press Break or Esc.
The system enters ROMMON mode. The rommon> prompt appears.
Step 4 Check the current network settings.
The variables have the following definitions:
- Address—Local IP address of the IPS 4345.
- Server—TFTP server IP address where the application image is stored.
- Gateway—Gateway IP address used by the IPS 4345.
- Port—Ethernet interface used for the IPS 4345 management.
- VLAN—VLAN ID number (leave as untagged).
- Image—System image file/path name.
- Config—Unused by these platforms.
Note Not all values are required to establish network connectivity. The address, server, gateway, and image values are required. If you are not sure of the settings needed for your local environment, contact your system administrator.
Step 5 If necessary, change the interface used for the TFTP download.
Note The default interface used for TFTP downloads is Management 0/0, which corresponds to the MGMT interface of the IPS 4345.
Step 6 If necessary, assign an IP address for the local port on the IPS 4345.
Note Use the same IP address that is assigned to the IPS 4345.
Step 7 Assign the TFTP server IP address.
Step 8 If necessary, assign the gateway IP address.
Step 9 Verify that you have access to the TFTP server by pinging it from your local Ethernet port with one of the following commands:
Step 10 If necessary define the path and filename on the TFTP file server from which you are downloading the image.
Note The path is relative to the default tftpboot directory of the UNIX TFTP server. Images located in the default tftpboot directory do not have any directory names or slashes in the IMAGE specification.
Step 11 Enter set and press Enter to verify the network settings.
Note You can use the sync command to store these settings in NVRAM so they are maintained across boots. Otherwise, you must enter this information each time you want to boot an image from ROMMON.
Step 12 Download and install the system image.
Note If the network settings are correct, the system downloads and boots the specified image on the IPS 4345. Be sure to use the IPS 4345 image.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
Installing the IPS 4510 and IPS 4520 System Images
Note The following procedure references the IPS 4510 but it also refers to the IPS 4520.
You can install the IPS 4510 and IPS 4520 system image by using the ROMMON on the appliance to TFTP the system image onto the compact flash device.
To install the IPS 4510 system image, follow these steps:
Download the IPS 4510 system image file to the tftp root directory of a TFTP server that is accessible from your IPS 4510.
Note Make sure you can access the TFTP server location from the network connected to the Management port of your IPS 4510.
Step 3 Press Break or Esc at the following prompt while the system is booting to interrupt boot. Press the spacebar to begin boot immediately.
Note You have ten seconds to press Break or Esc.
The system enters ROMMON mode. The rommon> prompt appears.
Step 4 Check the current network settings.
The variables have the following definitions:
- Address—Specifies the local IP address of the IPS 4510.
- Server—Specifies the TFTP server IP address where the application image is stored.
- Gateway—Specifies the gateway IP address used by the IPS 4510.
- Port—Specifies the Ethernet interface used for IPS 4510 management.
- VLAN—Specifies the VLAN ID number (leave as untagged).
- Image—Specifies the system image file/path name.
- Config—Unused by these platforms.
Note Not all values are required to establish network connectivity. The address, server, gateway, and image values are required. If you are not sure of the settings needed for your local environment, contact your system administrator.
Step 5 If necessary, assign an IP address for the Managment port on the IPS 4510.
Note Use the same IP address that is assigned to the IPS 4510.
Step 6 If necessary, assign the TFTP server IP address.
Step 7 If necessary, assign the gateway IP address.
Step 8 Verify that you have access to the TFTP server by pinging it from your local Ethernet port with one of the following commands:
Step 9 If necessary define the path and filename on the TFTP file server from which you are downloading the image.
Note The path is relative to the UNIX TFTP server default tftpboot directory. Images located in the default tftpboot directory do not have any directory names or slashes in the IMAGE specification.
Step 10 Enter set and press Enter to verify the network settings.
Note You can use the sync command to store these settings in NVRAM so they are maintained across boots. Otherwise, you must enter this information each time you want to boot an image from ROMMON.
Step 11 Download and install the system image.
Note If the network settings are correct, the system downloads and boots the specified image on the IPS 4510. Be sure to use the IPS 4510 image.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
Installing the ASA 5500 AIP SSM System Image
Note Be sure the TFTP server that you specify can transfer files up to 60 MB in size.
Note This process can take approximately 15 minutes to complete, depending on your network and the size of the image.
If the ASA 5500 AIP SSM suffers a failure and the module application image cannot run, you can transfer application images from a TFTP server to the module using the adaptive security appliance CLI. The adaptive security appliance can communicate with the module ROMMON application to transfer the image.
To install the system image of the ASA 5500 AIP SSM, follow these steps:
Download the system image file to the tftp root directory of a TFTP server that is accessible from your adaptive security appliance.
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of the adaptive security appliance.
Step 2 Log in to the adaptive security appliance.
Step 4 Configure the recovery settings for the ASA 5500 AIP SSM.
Note If you make an error in the recovery configuration, use the hw-module module 1 recover stop command to stop the system reimaging and then you can correct the configuration.
Step 5 Specify the TFTP URL for the system image.
Step 6 Specify the command and control interface of the ASA 5500 AIP SSM.
Note The port IP address is the management IP address of the ASA 5500 AIP SSM.
Step 7 Leave the VLAN ID at 0.
Step 8 Specify the default gateway of the ASA 5500 AIP SSM.
This transfers the image from the TFTP server to the ASA 5500 AIP SSM.
Step 10 Periodically check the recovery until it is complete.
Note The status reads Recovery during recovery and reads Up when reimaging is complete.
Note The Status field in the output indicates the operational status of the ASA 5500 AIP SSM. An ASA 5500 AIP SSM operating normally shows a status of “Up.” While the adaptive security appliance transfers an application image to the ASA 5500 AIP SSM, the Status field in the output reads “Recover.” When the adaptive security appliance completes the image transfer and restarts the ASA 5500 AIP SSM, the newly transferred image is running.
Note To debug any errors that may happen in the recovery process, use the debug module-boot command to enable debugging of the system reimaging process.
Step 11 Session to the ASA 5500 AIP SSM and initialize it with the setup command.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
Installing the ASA 5500-X IPS SSP System Image
Note Be sure the TFTP server that you specify can transfer files up to 60 MB in size.
Note The CLI output is an example of what your configuration may look like. It will not match exactly due to the optional setup choices, sensor model, and IPS 7.1 version you have installed.
To install the system image on the ASA 5500-X IPS SSP, follow these steps:
Download the IPS system image file corresponding to your ASA platform to the tftp root directory of a TFTP server that is accessible from your adaptive security appliance.
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of the adaptive security appliance.
Step 2 Log in to the adaptive security appliance.
Step 4 Copy the IPS image to the disk0 flash of the adaptive security appliance.
Step 5 Image the ASA 5500-X IPS SSP.
Step 6 Execute the recovery. This transfers the image from the TFTP server to the ASA 5500-X IPS SSP and restarts it.
Step 7 Periodically check the recovery until it is complete.
Note The Status field in the output indicates the operational status of the ASA 5500-X IPS SSP. An ASA 5500-X IPS SSP operating normally shows a status of “Up.” While the adaptive security appliance transfers an application image to the ASA 5500-X IPS SSP, the Status field in the output reads “Recover.” When the adaptive security appliance completes the image transfer and restarts the ASA 5500-X IPS SSP, the newly transferred image is running.
Note To debug any errors that may happen in the recovery process, use the debug module-boot command to enable debugging of the system reimaging process.
Step 8 Session to the ASA 5500-X IPS SSP and initialize it with the setup command.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for locating software on Cisco.com, see Obtaining Cisco IPS Software.
Installing the ASA 5585-X IPS SSP System Image
This section describes how to install the ASA 5585-X IPS SSP system image using the hw-module command or ROMMON, and contains the following topics:
Installing the ASA 5585-X IPS SSP Using the hw-module Command
Note Be sure the TFTP server that you specify can transfer files up to 60 MB in size.
Note This process can take approximately 15 minutes to complete, depending on your network and the size of the image.
Note The CLI output is an example of what your configuration may look like. It will not match exactly due to the optional setup choices, sensor model, and IPS 7.1 version you have installed.
To install the system image, transfer the software image from a TFTP server to the ASA 5585-X IPS SSP using the adaptive security appliance CLI. The adaptive security appliance can communicate with the ROMMON application of the ASA 5585-X IPS SSP to transfer the image.
To install the ASA 5585-X IPS SSP software image, follow these steps:
Download the ASA 5585-X IPS SSP system image file to the tftp root directory of a TFTP server that is accessible from your adaptive security appliance.
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of your adaptive security appliance.
Step 2 Log in to the adaptive security appliance.
Step 4 Configure the recovery settings for the ASA 5585-X IPS SSP.
Note If you make an error in the recovery configuration, use the hw-module module 1 recover stop command to stop the system reimaging and then you can correct the configuration.
Step 5 Specify the TFTP URL for the software image.
Step 6 Specify the command and control interface of the ASA 5585-X IPS SSP.
Note The port IP address is the management IP address of the ASA 5585-X IPS SSP.
Step 7 Leave the VLAN ID at 0.
Step 8 Specify the default gateway of the ASA 5585-X IPS SSP.
Step 9 Execute the recovery. This transfers the software image from the TFTP server to the ASA 5585-X IPS SSP and restarts it.
Step 10 Periodically check the recovery until it is complete.
Note The status reads Recovery during recovery and reads Up when installation is complete.
Note The Status field in the output indicates the operational status of the ASA 5585-X IPS SSP. An ASA 5585-X IPS SSP operating normally shows a status of “Up.” While the adaptive security appliance transfers the software image to the ASA 5585-X IPS SSP, the Status field in the output reads “Recover.” When the adaptive security appliance completes the software image transfer and restarts the ASA 5585-X IPS SSP, the newly transferred image is running.
Note To debug any errors that may happen during this process, use the debug module-boot command to enable debugging of the software installation process.
Step 11 Session to the ASA 5585-X IPS SSP.
Step 12 Enter cisco three times and your new password twice.
Step 13 Initialize the ASA 5585-X IPS SSP with the setup command.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for initializing the ASA 5585-X IPS SSP, see ASA 5500-X IPS SSP Advanced Setup.
Installing the ASA 5585-X IPS SSP System Image Using ROMMON
You can install the ASA 5585-X IPS SSP system image by using the ROMMON on the adaptive security appliance to TFTP the system image onto the ASA 5585-X IPS SSP.
To install the ASA 5585-X IPS SSP system image, follow these steps:
Download the ASA 5585-X IPS SSP system image file to the tftp root directory of a TFTP server that is accessible from your adaptive security appliance.
Note Make sure you can access the TFTP server location from the network connected to the Ethernet port of your adaptive security appliance.
Step 2 Boot the ASA 5585-X IPS SSP.
Step 3 Press Break or Esc at the following prompt while the system is booting to interrupt boot. Press the spacebar to begin boot immediately.
Note You have ten seconds to press Break or Esc.
The system enters ROMMON mode. The rommon> prompt appears.
Step 4 Check the current network settings.
The variables have the following definitions:
- Address—Specifies the local IP address of the ASA 5585-X IPS SSP.
- Server—Specifies the TFTP server IP address where the application image is stored.
- Gateway—Specifies the gateway IP address used by the ASA 5585-X IPS SSP.
- Port—Specifies the ethernet interface used for the ASA 5585-X IPS SSP management.
- VLAN—Specifies the VLAN ID number (leave as untagged).
- Image—Specifies the system image file/path name.
- Config—Specifies the unused by these platforms.
Note Not all values are required to establish network connectivity. The address, server, gateway, and image values are required. If you are not sure of the settings needed for your local environment, contact your system administrator.
Step 5 If necessary, change the interface used for the TFTP download.
Note The default interface used for TFTP downloads is Management 0/0, which corresponds to the management interface of the ASA 5585-X IPS SSP.
Step 6 If necessary, assign an IP address for the local port on the ASA 5585-X IPS SSP.
Note Use the same IP address that is assigned to the ASA 5585-X IPS SSP.
Step 7 If necessary, assign the TFTP server IP address.
Step 8 If necessary, assign the gateway IP address.
Step 9 Verify that you have access to the TFTP server by pinging it from your local Ethernet port with one of the following commands.
Step 10 If necessary define the path and filename on the TFTP file server from which you are downloading the image.
Note The path is relative to the default tftpboot directory of the UNIX TFTP server. Images located in the default tftpboot directory do not have any directory names or slashes in the IMAGE specification.
Step 11 Enter set and press Enter to verify the network settings.
Note You can use the sync command to store these settings in NVRAM so they are maintained across boots. Otherwise, you must enter this information each time you want to boot an image from ROMMON.
Step 12 Download and install the system image.
Note If the network settings are correct, the system downloads and boots the specified image on the ASA 5585-X IPS SSP. Be sure to use the ASA 5585-X IPS SSP image.
- For more information about TFTP servers, see TFTP Servers.
- For the procedure for initializing the IPS SSP, see ASA 5500-X IPS SSP Advanced Setup.
Feedback