|
|
NATkit 2.0 is a suite of web-based troubleshooting tools integrated into a network desktop. NATkit 2.0 includes a web-server component, web-based tools, and web browser capability, and is based on a client/server network architecture that connects multiple web-based clients to a network server. NATkit 2.0 enables the deployment, monitoring, and troubleshooting of devices across your network.
This chapter consists of the following sections:
Table 2-1 provides an overview of NATkit 2.0 installation, and references to more detailed information about each task. The information in the rest of this chapter follows the same order as the quick reference.
| Task | Steps | References | ||
|---|---|---|---|---|
| Step 1 Verify that server requirements are met. | "Server Requirements" section "Before You Begin" chapter, "System Requirements" section | ||
Step 2 Verify that client requirements are met. | "Client Requirements" section | |||
Step 3 (Optional) Verify that your intended device import software is supported. | ||||
Step 4 Note that NATkit 2.0 uses the server's IP address to communicate with clients. | "Using Server IP Address" section | |||
Step 5 Note the TCP ports that NATkit 2.0 uses and check for conflicts with existing applications. | "TCP and UDP Ports Used" section | |||
Step 6 Note the system files that are modified during installation. | ||||
| Step 1 Mount the NATkit 2.0 CD-ROM. | "Mounting and Unmounting on Solaris" appendix | ||
Step 2 Run the installation program. | ||||
Step 3 Answer any questions that result from the installation program's checks. | ||||
Step 4 Select the Express or Custom installation option. | ||||
| Step 1 Verify that the correct files and directories are installed. | "Troubleshooting" appendix, "Checking Files and Directories After Installation" section | ||
Step 2 Analyze installation error messages. | "Troubleshooting" appendix, "Understanding Installation Error Messages" section | |||
Step 3 Collect the server information to determine if the installation is complete. | "Troubleshooting" appendix, "Collecting Server Information" section |
Before you install NATkit 2.0, make sure your server and client environments meet the hardware and software requirements described in the following sections:
Make sure your server meets the following hardware and software requirements and software compatibility recommendations.
The NATkit 2.0 hardware and software requirements are given in the "Before You Begin" chapter, "System Requirements" section.
To verify the amount of available disk space in each of the specified partitions and directories, enter the following command:
# df -k directory
Where directory is the partition or directory for which you want to check the available disk space.
The software required for the NATkit 2.0 server is Solaris 2.5.1 with the latest patch set (contact natkit-support@cisco.com for more information) or Solaris 2.6. Patch 103738-03 is required for Solaris 2.5.1 only when a significant number of messages are processed by syslogd (the daemon process that reads and forwards system messages to the appropriate log file and users when necessary).
Use the showrev -p command to make sure the appropriate patches for your version of Solaris is applied. You can find additional information about the Sun patch at the following location:
http://www.cisco.com/kobayashi/sw-center/netmgmt/nat/
CDDM (Cisco DNS/DHCP Manager) can be downloaded from CCO and provides Syslog and TFTP daemons as part of its product. Make sure that you do not have the CDDM installed on the system on which you plan to install NATkit 2.0. NATkit 2.0 installation will fail if CDDM Syslog or TFTP are present on the system.
Clients use a web browser running on a workstation or PC to access the NATkit 2.0 server. The hardware and software requirements for client workstations or PCs are as follows:
NATkit 2.0 supports clients running the browsers shown in Table 2-2.
| Browser | Version |
|---|---|
Netscape Navigator | 4.5 or higher on Solaris 2.5.1 or 2.6, Windows NT 4.0, Windows 95, AIX 4.2.1 or 4.3, and HP-UX 10.20 or 11.0 |
Microsoft Internet Explorer | 4.01 with Internet Explorer Service Pack 2 or Internet Explorer 5.1 on Windows NT 4.0 or Windows 95/98/2000 |
To configure a client system to use with NATkit 2.0, follow these steps:
Step 1 On Microsoft Windows systems, set the display to use small fonts.
(a) Select Start > Settings > Control Panel. The Control Panel window appears.
(b) Double-click the Display icon. The Display Properties dialog box appears.
(c) Click the Settings tab. If Small Fonts is selected in the Font Size list, your display font is set correctly; go to Step 2.
(d) Select Small Fonts from the Font Size list, then click OK. The System Settings Change dialog box appears.
(e) Click Yes to restart your system. Windows restarts using the small display font.
Step 2 Configure the Web browser.
(a) Enable Java and JavaScript.
(b) Set your browser cache to at least 4 MB.
(c) Configure your browser to accept all cookies.
(d) Configure your browser to compare each page with its cached version every time it loads a page.
(e) (Internet Explorer only) Set the security level to Medium. Select View > Internet Options > Security, then select the Medium (more secure) radio button and click OK.
(f) (Internet Explorer only) Change the default timeout value to 20 minutes. Instructions are provided on the Microsoft Support Web site at the following URL:
http://support.microsoft.com/support/kb/articles/q181/0/50.asp
(g) Enable style sheets.
(h) Change the default font to a sans serif font for easier readability.
If you experience browser problems after configuring your browser as described above, increase your disk cache settings.
After the web browser is installed on the client machine, there are no additional disk space requirements. However, because the browser uses the local machine's disk to store cached information, make sure you have enough disk space for the amount of cached information you want to store. All NATkit information is stored on the NATkit 2.0 server.
Set the following environment variables for NATkit 2.0 system administrators. These variables are not required for tasks that users perform using the web interface.
NATkit 2.0 includes manual (man) pages for its command line commands. You can view these man pages in the following ways:
1. Set the MANPATH variable to include the path /opt/CSCOpx/man (where /opt/CSCOpx is the directory in which NATkit 2.0 was installed). Then you can view the man pages from any directory using the following command:
$ man pagename
Where pagename is the name of the man page. Refer to the section "Setting Environmental Variables" for information about setting up administrator systems.
2. If the MANPATH variable is not set, you can view the man pages while you are in the directory /opt/CSCOpx/man (where /opt/CSCOpx is the directory in which NATkit 2.0 was installed) using the following command:
man -M . pagename
Where pagename is the name of the man page.
3. If the MANPATH variable is not set, you can view the man pages from any directory using the following command:
man -M /opt/CSCOpx/man pagename
Where /opt/CSCOpx is the directory in which NATkit 2.0 was installed and pagename is the name of the man page.
Table 2-3 lists the software that NATkit 2.0 supports for importing device information. You can import devices remotely from a UNIX system only. NATkit 2.0 does not support remote device imports from Windows NT systems.
| Software | Version |
|---|---|
HP OpenView | 4.11, 5.01 |
CiscoWorks | 3.2, 4.0 |
CiscoWorks for Switched Internetworks (CWSI) | 2.1.1 |
CWSI Campus | 2.2 |
To avoid inconsistencies in how domain names are used in networks, NATkit 2.0 uses the IP address of the server on which you installed NATkit 2.0 when it interacts with web browsers. By using the IP address of the server, NATkit 2.0 reduces the likelihood of name lookup failures between the server and the client machines that run web browsers.
You then must restart the NATkit 2.0 server by entering the following commands as root:
# /etc/init.d/dmgtd stop # /etc/init.d/dmgtd start
In addition to the standard network ports (telnet, tftp, etc.) NATkit 2.0 uses the following TCP and UDP ports. These ports are added to /etc/services when you install NATkit 2.0:
http://server_name:1741
The NATkit 2.0 installation program detects whether any of the default TCP ports are already in use on your system and prompts you to enter an available TCP port number for each port that has a conflict.
Refer to the "Setting Up NATkit 2.0" chapter for more information about accessing the server. Refer to the "Troubleshooting" appendix if you encounter problems.
The following system files are modified during NATkit 2.0 installation:
This section describes how to install NATkit 2.0. This is normally done by the Cisco Net Tools team. This information is provided to help you understand NATkit 2.0 and for the rare case when NATkit 2.0 is installed by a customer.
The NATkit 2.0 installation program takes approximately 60 minutes on an Ultra 5 system.
To install NATkit 2.0, follow these steps:
Step 1 As root, mount the NATkit 2.0 CD-ROM.
Refer to the appendix "Mounting and Unmounting on Solaris" for detailed instructions for mounting the CD-ROM.
Step 2 Run the installation program.
For a local CD installation, enter the following commands:
# cd /cdrom/cdrom0/ # sh ./setup.sh
For a remote CD installation, enter the following commands:
# cd remotedir # sh ./setup.sh
where remotedir is the remote location where the NATkit 2.0 CD-ROM is mounted.
The following message is displayed:
Software Install Tool Started.
These preinstallation checks can generate two types of results:
Step 3 Answer any questions that result from the preinstallation checks. These questions could include one or more of the following:
The install takes all defaults and places the product into /opt/CSCOpx. No more questions will be asked of you.
If you entered Y when asked if you want the express installation, NATkit 2.0 is installed using the default TCP ports specified in the "TCP and UDP Ports Used" section and you do not need to answer any additional questions. The installation program keeps you updated on the status of the installation as it installs NATkit 2.0 and displays any error or warning messages on your screen. When the install completes, any error messages that appeared during the installation appear on the screen again, followed by the following message:
Software Install Tool Completed.
You have now completed the NATkit 2.0 installation. If you encountered any errors, check the installation log file /opt/CSCOpx/ciscoinstall.log (where /opt/CSCOpx is the directory in which you installed NATkit 2.0). For troubleshooting information, or to verify the directories installed on your system, refer to the "Troubleshooting" appendix.
Continue the installation process by setting up NATkit 2.0. Go to the "Setting Up NATkit 2.0" chapter for instructions.
To remove NATkit 2.0, follow these steps:
Step 1 Enter the following commands as root to start the uninstall script:
# cd /opt/CSCOpx/bin # sh ./uninstall.sh
where /opt is the directory you specified to install NATkit 2.0 if you did not use the default location.
A list of all installed NATkit 2.0 packages appears, followed by a [Yes] prompt.
Step 2 To remove all NATkit 2.0 packages, press Return or enter Y (yes). The specified packages are removed and a verification message appears. To cancel the removal of NATkit 2.0, enter N (no).
When you remove NATkit 2.0, the uninstall script removes the changes made to the /etc/services file. The /etc directory still contains all system file changes. The uninstall messages are written to the /var/tmp/ciscouninstall.log file.
When the uninstall script completes, two lists of packages appear on the screen: packages that were removed, and packages that could not be removed.
Step 3 Check /etc/syslog.conf for syslog changes. Check /etc/services to make sure port assignments for the Daemon Manager and web server have been removed. See the "Troubleshooting" appendix for more information.
To reinstall NATkit 2.0, follow the instructions in the "Running the NATkit 2.0 Installation Program" section.
Posted: Wed Jul 12 18:13:11 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.