Table Of Contents
Preparing to Install PDM
Important Notes
Installation Checklist
Preparing to Install PDM
Determining the IP Address of Your Server
Windows 2000, or Windows XP
Sun Solaris
Linux
Preparing to Install PDM
If you are upgrading from a previous version, you can use TFTP, FTP or HTTP(s) from the firewall to copy the PDM image to your firewall.
This section includes the following topics:
•Important Notes
•Installation Checklist
•Preparing to Install PDM
•Determining the IP Address of Your Server
Important Notes
• CLI Command Support—PDM Version 4.1 uses CLI to configure the device.
• Multiple PDM Sessions—PDM allows multiple PCs or workstations to each have one browser session open with the same firewall. A single firewall can support up to 32 concurrent PDM sessions. Only one session per browser per PC or workstation is supported for a particular firewall.
• FWSM OS Version—PDM Version 4.1 for FWSM requires FWSM Release 2.3 or 2.2.
• Caveats—Use Bug Navigator II on CCO to view current caveat information. You can access Bug Navigator II at:
http://www.cisco.com/support/bugtools
• Changing OS Color Schemes—If you change the color scheme of your operating system while PDM is running, you should restart PDM or some PDM screens might not display correctly.
• Installing New PDM Versions—When you install a new version of PDM, or when using one PDM release with another, close all browser sessions before launching PDM.
• Java Plug-in Supported—PDM Version 4.1 supports Java Plug-in 1.4.2 and 5.0 on Windows 2000 and XP. PDM 4.1 supports Java Plug-in 1.4.2 on Sun Solaris and Red Hat Linux.. Click Browser Requirements> Java Plug-in for more information.
• Browser SSL Encryption Settings—Enable available encryption options for SSL in the browser preferences.
Installation Checklist
Confirm the following before you install PDM:
•Verify that all system requirements are met. See the requirements listed in Chapter 1, "Overview."
•Confirm that you are running the correct software version. (If you have command line access to your firewall, you can use the CLI show version command to display the version currently running on your firewall.)
•Verify that you have a TFTP or FTP server available.
•Confirm that you are a registered Cisco user. If you are not a registered user, go to http://tools.cisco.com/RPF/register/register.do and complete the form to register.
Preparing to Install PDM
Before installing PDM, be aware of the following:
•Save or print your firewall configuration. (You can save a copy of your configuration by using the firewall CLI write terminal command to display your configuration. You can then cut and paste the displayed configuration into a text file.)
•Write down your activation key. (View your activation key by using the firewall CLI show version command.)
•If you are upgrading the software, obtain the PDM software from http://www.cisco.com/cisco/software/navigator.html and download the image onto your firewall unit, using HTTP protocol, TFTP or an FTP server.
Note For additional information on upgrading your Cisco PDM or FWSM software, see Switch/Router System Requirements and FWSM Requirements. Also, see the Catalyst 6500 Series Switch and Cisco 7600 Series Router Firewall Services Module Configuration Guide Release 2.3 for more information
http://www.cisco.com/en/US/products/hw/modules/ps2706/ps4452/tsd_products_support_model_home.htm
•PDM works with the firewall command-line interface (CLI). If you are using PDM, and make changes to your firewall configuration outside PDM, click Refresh in PDM to update PDM with the current firewall configuration.
Determining the IP Address of Your Server
Loading a firewall or PDM image requires you to use TFTP server, FTP or HTTP(S).
This section provides the information required to determine your IP address, and includes the following topics:
•Windows 2000, or Windows XP
•Sun Solaris
•Linux
Windows 2000, or Windows XP
On a Windows workstation, click Start>Accessories>Command Prompt to launch the Windows command-line interface and then enter the ipconfig command as shown in the following example:
Windows 2000 IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 209.165.200.225
Subnet Mask . . . . . . . . . . . : 255.255.255.224
Default Gateway . . . . . . . . . : 10.21.196.33
In this example, the server IP address is 209.165.200.225 with a network mask of 255.255.255.224.
Sun Solaris
Enter the /sbin/ifconfig -a command to view your IP address, as shown in the following example:
lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
inet 127.0.0.1 netmask ff000000
hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
inet 209.165.200.225 netmask ffffffe0 broadcast 209.165.200.255
(In this example, the IP address of the host is 209.165.200.225 with a netmask of 255.255.255.224. ffffffe0 is the hexadecimal equivalent to 255.255.255.224).
Linux
Enter the /sbin/ifconfig command to view your IP address, as shown in the following example:
eth0 Link encap:Ethernet HWaddr 00:D0:B7:5D:C0:56
inet addr:209.165.200.225 Bcast:209.165.200.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:189576 errors:0 dropped:0 overruns:0 frame:0
TX packets:414837371 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
Interrupt:10 Base address:0x3000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:75397725 errors:0 dropped:0 overruns:0 frame:0
TX packets:75397725 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
In this example, the IP address of the computer is 209.165.200.225 with a netmask of 255.255.255.224. The remainder of the display provides information on the status of data transmission through the server.