|
|
Validating CiscoWorks Installation
Validation is the process of configuring and testing installed software for proper operation.
To make CiscoWorks operational, you perform the following tasks:
To use NetView for AIX, CiscoWorks, and Sybase, you must define the appropriate environment variables and paths in your .cshrc or .kshrc file. The environment variables and paths are explained in Table 4-1.
Table 4-1 Environment Variables
| Environment Variable | Explanation |
|---|---|
| NMSROOT | Refers to the directory /usr/nms where the CiscoWorks software is installed. |
| SYBASE | Refers to the directory path where Sybase is located. The default is $NMSROOT/sybase10, which usually equates to /usr/nms/sybase10 |
| LANG | Must be En_US. |
| HHHOME | Refers to the directory where online help is stored. Must be $NMSROOT/help. |
| HHPATH | Refers to the directory where the hypertext help program resides. Must be $NMSROOT/hyperhelp/bin. |
| PATH | Must include the directories /usr/OV/bin, $NMSROOT/bin, $NMSROOT/etc, and $SYBASE/bin (the directories for NetView for AIX, CiscoWorks, and Sybase). |
| MANPATH | Refers to the directory path for finding man pages. It should include $NMSROOT/man. |
| DISPLAY | Refers to the X11 display with which CiscoWorks operates. The default is :0 or hostname:0.0 |
| DSQUERY | Refers to the Sybase data server to be used. The default is CW_SYBASE. |
| CW_POLLDB | Refers to the default CiscoWorks polling database name polldb. |
| CW_NMSDB | Refers to the default CiscoWorks network management database nms. |
| BACKUP_SERVER_NAME | Refers to the default Sybase backup server CW_BACKUP_SERVER. |
| BACKUP_SERVER_HOME | Refers to the default directory of the backup server, $NMSROOT/sybase10/install. |
| ESQRDIR | Refers to the default directory of the Easy SQL Report generator (Sybase ESQR), /usr/nms/bin. |
| VVTERM | Enables Sybase ESQR to operate. The default is xterm. |
| VVTERMCAP | Enables Sybase ESQR to operate. The default is /usr/nms/bin/vvtermcap. |
Because the environment variables set in a user's .kshrc or .cshrc file apply to that user only, the .cshrc or .kshrc file of every CiscoWorks user must be modified to include the variables in Table 4-1. The following steps describe a method of concatenating a script of commands from the /usr/nms/install directory to each .cshrc or .kshrc file. When executed in the .cshrc or .kshrc file, the commands establish all required environment variables and paths for the user.
hostname# cd /users/william hostname# ls .kshrc .cshrc
.kshrc
.cshrc
hostname# cat /usr/nms/install/install.kshrc >> .kshrc
hostname# cat /usr/nms/install/install.cshrc >> .cshrc
hostname# cat .kshrc #---Environment variables for NetView, CiscoWorks, and Sybase---## (more lines here)
hostname# cat .cshrc #---Environment variables for NetView, CiscoWorks, and Sybase---## (more lines here)
hostname% source .cshrc
hostname% . .kshrc
hostname% printenv | more
hostname% set | more
Several CiscoWorks applications exchange configuration files and software images with Simple Network Management Protocol (SNMP) devices on the network by means of the Trivial File Transfer Protocol (TFTP). For TFTP to operate, you must perform the following steps:
A daemon is a process that performs a specific background function on behalf of an application.
Create a TFTP boot directory in which device configuration files will be stored. This task is optional because the directory will be accessible to all users and is a security hole. Without the boot directory, you are unable to use the following CiscoWorks applications: AutoInstall Manager, Configuration Management, and the Device Software Manager. Therefore, creation of the boot directory is recommended.
To create the TFTP boot directory, make sure you are logged in as the root user and perform the following steps:
hostname# mkdir /tftpboot
hostname# chmod 777 /tftpboot
As a result, all users of the TFTP boot directory will have read, write, and execute permissions.
TFTP enables transfer of files between the following CiscoWorks applications and SNMP-enabled network devices: Configuration Management, AutoInstall Manager, Software Library Manager, Device Software Manager, and Configuration Snap-In Manager. For those applications to operate, the TFTP daemon must operate.
Use the System Management Interface Tool (SMIT) to enable the TFTP daemon. For additional information on TFTP, refer to the AIX man pages on the tftp and tftpd commands. Enable and verify the TFTP daemon by completing the following steps:
hostname# smit
hostname# grep tftp /etc/inetd.conf
tftp dgram udp wait nobody /etc/tftpd tftpd -n -d /tftpboot
After proper installation and configuration, CiscoWorks applications are integrated into the structure of NetView for AIX. To verify the CiscoWorks installation and configuration, access NetView for AIX and display the menu of CiscoWorks applications as follows:
hostname% nv6000
Table 4-2 CiscoWorks Applications under NetView for AIX
| NetView for AIX Menu | CiscoWorks Application | CiscoWorks Application Enabled When |
|---|---|---|
| Monitor | Description: Contacts CW - Health Monitor... CW - Environmental Monitor... CW - Real-Time Graphs... CW - Device Polling... CW - Polling Summary... Workgroup Director |
One Cisco device is selected on the network map. One Cisco device is selected on the network map. On the network map, one Cisco device is selected that contains an Environmental Monitor Card. One Cisco device is selected on the network map. Always enabled. Always enabled. One Cisco device is selected on the network map. |
| Administer> CW - System Administer> CW - Devices Administer> CW - Software Images Administer> CW - Security |
Process Mgr... Global Command Mgr... Global Command Scheduler... Device Mgmt... Configuration Mgr... Configuration Snap-In Mgr... AutoInstall Mgr... Software Library Mgr... Software Inventory Mgr... Device Software Mgr... SA Password... Security Mgr... Domain Mgr... TACACS Mgr... |
Always enabled. Always enabled. Always enabled. Always enabled. Always enabled. Always enabled. Always enabled. On the network map, one Cisco device is selected that contains Flash memory. Always enabled. On the network map, one Cisco device is selected that contains Flash memory. Always enabled. Always enabled. Always enabled. Always enabled. |
| Diagnose |
Network Conn.> CW - Path Tool CW - Show Commands... |
Always enabled. One Cisco device is selected on the network map. |
| Misc | Sync w/Sybase... Sync Selected... CW - Login... CW - Logout... CW - ToolBox Sybase ESQR... |
Always enabled. One or more Cisco devices are selected on the network map. Always enabled. Always enabled. Always enabled. One Cisco device is selected on the network map. |
If no CiscoWorks applications are visible under the NetView for AIX menus, the installation might have been unsuccessful. Look for the CiscoWorks file in the /usr/OV/registration/C directory. If the file is not there, contact a TAC representative.
After verifying that CiscoWorks applications appear in the NetView for AIX menus, see "Customizing CiscoWorks 3.0" which immediately follows, or go straight to the chapter "CiscoWorks Getting Started."
Customizing CiscoWorks 3.0 is optional and can be done now or at any time in the future.
CiscoWorks 3.0 is based on the OSF/Motif windowing system and requires Motif key mapping. If necessary, you can also manually update the XKeysymDB file by appending $NMSROOT/etc/XKeysymDB to your XKeysymDB file.
Some operations of CiscoWorks and NetView for AIX are determined by X Windows. You can customize the way you work with CiscoWorks on NetView for AIX by modifying your .Xdefaults file. For example, you can change the colors that NetView for AIX displays by changing your X Windows environment. (Refer to your IBM documentation for instructions.) Or, you can specify certain ways in which CiscoWorks runs in your X Windows environment.
This section provides information on the following topics:
All X Windows resources used by CiscoWorks applications can be customized, including colors and fonts. By overwriting the default resources used in CiscoWorks, you can customize the colors and fonts to meet your needs. To use your own colors and fonts for CiscoWorks, perform one of the following procedures:
Refer to your AIX documentation for details.
Defining the look of your text editor window requires that you add the following command to the .Xdefaults file, substituting the appropriate options:
hostname% startx
hostname% vi $HOME/.Xdefaults
* EditorFormat:command string %s
* EditorFormat:/usr/local/bin/emacs %s
When a configuration file is loaded from the database to a device, an image of the loaded configuration file can be saved in the TFTP boot file in the /tftpboot directory. If the device is down, you can still retrieve the image of the configuration file from the TFTP boot directory that is defined in the /etc/inetd.conf file (usually /tftpboot). The TFTP boot directory, however, may not provide a secure storage location because almost all users can access this directory. Therefore, you may want the boot file generation feature to be turned off.
By default, CiscoWorks does not enable the boot file generation feature in the TFTP boot directory. To activate it, use a text editor to modify the .Xdefaults file.
*Bootfile:on
# xrdb -merge $HOME/.Xdefaults
When working with CiscoWorks applications, you may notice that the window sizes may vary from application to application. The layout of the window and the size of its text and graphics is preset to be large enough to contain all the elements that define the window. However, you can resize the window without obscuring the text.
To reset the default CiscoWorks window size, perform the following steps:
"XCiscoWorks*geometry: 500x400+0+0"
hostname% xrdb -merge < ~/XCiscoWorks
The next time you run CiscoWorks, the window size will be the default.
Perform these steps only when you suspect a problem with the operation of the CiscoWorks applications.
A daemon is a process that performs a specific background function on behalf of an application. CiscoWorks 3.0 has several daemons. SMIT offers control of the following CiscoWorks 3.0 daemon processes:
Perform the following steps to display the status of, start, or stop CiscoWorks daemons:
hostname# smit
|
|
Copyright 1988-1995 © Cisco Systems Inc.