|
|
This chapter describes how to install and configure CiscoWorks software on Sun workstations.
Before installing CiscoWorks, you must complete the prerequisite steps described in the "Preparing to Install CiscoWorks" chapter. To install and configure CiscoWorks, you need to perform the following general tasks:
To perform the tasks associated with installing and configuring CiscoWorks, you must log in to your system as the superuser (root). Superusers can perform functions that normal users cannot.
 | Caution If you are a relatively inexperienced UNIX user, limit your activities as the superuser to the tasks described in this publication. As the superuser, you can adversely affect your operating environment if you are unaware of the effects of the commands you use. |
To become the superuser, you must know the root password. In the following examples, the root password is displayed as rootpassword. You must substitute your real password wherever you see rootpassword.
If you are not logged in, enter the following commands to log in as the superuser:
login:rootPassword:rootpassword#
Make sure that you start an X Window Manager session.
The UNIX prompt is a pound sign (#), indicating that you are logged in as the superuser.
If you are already logged in, but not as root, enter the following commands to change your login:
%suPassword:rootpassword#
The C shell prompt changes from a percent sign (%) to a pound sign (#), indicating that you are logged in as the superuser.
If you are not upgrading from a previous version of CiscoWorks, skip this section and go to "Mounting the CiscoWorks CD-ROM on a Local or Remote Drive"
Before you upgrade, you must perform the following tasks:
Since CiscoWorks uses the Sybase database, you must close all database files and shut down your database before starting the backup process.
To shut down the database, perform the following steps:
Step 1 Log in to your system as the superuser.
For information on how to become the superuser, refer to the section "Becoming the Superuser," earlier in this chapter.
Step 2 To ensure that your Sybase environment variable is set, enter the following:
setenv SYBASE $NMSROOT/sybase
Step 3 Execute the isql binary by entering the following:
$SYBASE/bin/isql -Usa -P <sa_password>
Enter the password, if you created one, for the Sybase SA account at your site. If you do not supply a password, the script assumes the value for password is null.
After starting isql, the prompt 1> appears.
Step 4 Enter the shutdown command as follows:
shutdown
go
The database shuts down, and the root prompt reappears.
Back up your entire CiscoWorks system, including the $NMSROOT directory, current database(s) and map files, as well as any additional Sybase data files. For information on backing up UNIX files, refer to the UNIX manual pages on tar(1) or cpio(1).
| Caution To prevent possible data loss, back up your system and database before installing CiscoWorks. |
After you shut down the Sybase database and back up your existing CiscoWorks software, verify that you are running the supported operating systems and network management software versions.
To verify your current operating system, enter uname -r.
To verify your current network management platform versions, enter one of the following:
$SNMHOME/bin/snm_versionIf you are not running the supported versions, follow the instructions to upgrade your operating system and the network management platform software. Follow the instructions in the Sun documentation to upgrade your version of SunOS to Version 4.1.3 or 4.1.4 (Solaris 1.X). After you install your operating system, follow the instructions in your NMS documentation to install one of the following:
SunNet Manager Version 2.2.3
Sun Net Manager Version 2.3
HP OpenView 3.31, 4.01, 4.1
Before you install CiscoWorks from a CD-ROM drive attached to your system or a remote system, connect a CD-ROM drive either to your workstation or to the remote workstation.
Retain the device number used by the CD-ROM drive for later use in installing CiscoWorks. After you log in as the superuser, the installation script prompts you to supply the device name of the local or the remote CD-ROM drive, or the name of the remote system and the device name of the remote drive.
The installation and configuration process takes a minimum of 20 to 30 minutes. Depending on your system performance and installation method, installation from a remote CD-ROM drive may take longer than 30 minutes.
| Caution Avoid exposing the CiscoWorks CD-ROM to direct sunlight because it might damage the contents. |
If you are using a CD-ROM drive that is connected to your workstation, refer to the following section, "Mounting on a Local Drive". If you are using a CD-ROM drive that is connected to a remote workstation, refer to the section "Mounting on a Remote Drive". These instructions are also provided in the CiscoWorks CD-ROM insert booklet shipped with the product.
To mount the CD-ROM on a local CD-ROM drive, perform the following steps:
Step 1 Log in as the superuser by entering su and the root password.
Step 2 If a /cdrom directory does not already exist, enter:
mkdir /cdrom
Step 3 Insert the CD-ROM in the drive.
Step 4 Mount the CD-ROM by entering:
/etc/mount -rt hsfs /dev/device_name /cdrom
-r mounts the CD-ROM in read-only mode.
-t indicates the type of filesystem, where hsfs specifies a filesystem with an ISO 9660 standard or High Sierra standard with Rock Ridge extensions and a CDFS filesystem.
device_name is the device that you mount, usually sr0.
If you do not use these options, media error messages may display on the console.
If you use a CD-ROM drive attached to a remote system, CiscoWorks does not consume disk space on the remote system because the software is copied across the network to the local workstation.
The root .rhosts file on the remote system must contain the host name of your local system and an entry for the user root. Otherwise, you cannot access the remote system to download software from its CD-ROM drive. For more information, refer to the rhosts UNIX manual page.
To mount CiscoWorks from a remote host, acquire the appropriate login account to mount the CD-ROM remotely.
To mount the CD-ROM on a remote CD-ROM drive, perform the following steps:
Step 1 Go to the remote machine and log in as the superuser by entering su and the root password.
Step 2 If a /cdrom directory does not already exist, enter:
mkdir /cdrom
Step 3 Insert the CD-ROM into the drive.
Step 4 Use a text editor to create an /etc/exports file, if one does not exist.
Step 5 If the remote machine is running SunOS, add the following line to the /etc/exports file, and then skip to Step 7:
/cdrom -ro
Step 6 If the remote machine is running Solaris, enter the following command, and then skip to step 10:
share -F nfs -o ro /cdrom/cdrom0
The CD is automatically mounted on a Solaris machine.
Step 7 If the remote machine is running SunOS, make sure that your workstation is enabled as an NFS server by entering:
ps -ax | grep nfsd | grep -v grep
ps -ax | grep rpc.mountd | grep -v grep
Both nfsd and rpc.mountd daemons must be running for a workstation to be an NFS server.
If no nfsd daemons are running, start some by entering:
/usr/etc/nfsd 8 &
If the rpc.mountd daemon is not running, start it by entering:
/usr/etc/rpc.mountd -n
Step 8 If the remote machine is running SunOS, mount the CD by entering:
/etc/mount -rt hsfs /dev/device_name /cdrom
-r mounts the CD-ROM in read-only mode.
-t indicates the type of filesystem, where hsfs specifies a filesystem with an ISO 9660 standard or High Sierra standard with Rock Ridge extensions and a CDFS filesystem.
device_name is the device that you mount, usually sr0.
If you do not use these options, media error messages may display on the console.
Step 9 If the remote machine is running SunOS, enter:
exportfs -a
Step 10 Go to the local machine and log in as the superuser by entering su and the root password.
Step 11 If a /cdrom directory does not already exist, enter:
mkdir /cdrom
Step 12 Mount the CD as follows.
If the remote CD-ROM is on a SunOS machine, enter:
/etc/mount remote_machinename:/cdrom /cdrom
If the remote CD-ROM is on a Solaris machine, enter:
/etc/mount remote_machinename:/cdrom/cdrom0 /cdrom
To install or upgrade the CiscoWorks files, perform the following steps:
Step 1 Depending on your network management platform, enter one of the following commands.
On SunNet Manager, enter:
cd /cdrom/SunOS_SNM
On HP OpenView 3.x, enter:
cd /cdrom/SunOS_OV3
Step 2 If you are installing CiscoWorks for the first time, enter:
setenv NMSROOT /usr/nmscw
Step 3 Extract the files from the CD-ROM by entering:
./extract_unbundled
Include the ./ in the extract_unbundled command to run the correct version of this command.
Step 4 Answer the system prompt questions.
Step 5 If you answered yes when prompted about automatic kernel modification, reboot your system after the installation. Rebooting ensures that the new kernel is used. Enter the following command:
reboot
If you answered no when prompted about automatic kernel modification, you must manually update the kernel before rebooting. This procedure is described in the "Manually Entered Sybase Modifications to the Kernel Configuration File" section of the CiscoWorks Installation Guide for SunOS.
Step 6 Log into your system as superuser (root) after your computer reboots:
root
password:rootpassword
Step 7 If you are upgrading from a previous version of CiscoWorks, shut down the CiscoWorks processes by entering:
source $NMSROOT/etc/install.cshrc
shutdown_nms
Step 8 Complete the configuration of CiscoWorks by entering:
/var/tmp/unbundled/cwconfigure
Answer the system prompt questions.
Step 9 To unmount and eject the CD-ROM from your local machine, enter the following commands:
cd /
# umount /cdrom
# eject /dev/device_name
Remove the CD-ROM from the drive and store it in a safe place.
Step 10 To unmount and eject the CD-ROM from a remote machine, enter the following commands from your local machine:
cd /
# umount /cdrom
Step 11 Log into the remote machine as root and enter the following commands:
cd /
# umount /cdrom
# eject /dev/device_name
Remove the CD-ROM from the drive and store it in a safe place.
Refer to the chapter "Validating CiscoWorks Installation" for installation verification procedures and customizing information.
All Sun workstations contain a kernel. The kernel is the heart of the UNIX system that is read when your system is started; it is the part of the operating system that allocates resources and controls processing.
If you are using a Sun workstation and want to manually update the kernel instead of having the installation script perform the changes, perform the following procedure. In order for Sybase Version 10.0.2 software to work on your Sun system, you must modify the kernel. The kernel is built from a configuration file in either the /usr/share/$ARCH/conf directory (where $ARCH could be defined as sun4c, sun4m, or sun4n) or the /usr/sys/$ARCH /conf directory.
Most systems use a generic kernel stored in a configuration file called GENERIC. If the kernel is customized for your system, it may be stored in a configuration file with a different name.
If you choose to allow the installation script to build the new kernel, it uses your current system configuration and automatically saves the old kernel configuration file as vmunix.syb_inst.
To modify the kernel manually (as the superuser), perform the following steps:
Step 1 Back up your existing kernel file by entering the following command:
cp /vmunix /vmunix.bak
Step 2 Change directories by entering the following command:
cd /usr/share/$ARCH/conf cd /usr/sys/$ARCH/conf
Step 3 Copy the base kernel configuration file (usually called GENERIC) to filename by entering the following command, where filename is the new name you assign to the kernel configuration file:
cp GENERIC filename
Step 4 Add the following lines anywhere in the new configuration file:
options "SHMSIZE=0x20000"
options "SEMMNS=640"
options "SHMMNI=256"
Step 5 Start the configuration process by entering the following command:
config filename
This command executes the configuration process and creates a directory called /usr/share/$ARCH/directoryname or /usr/sys/$ARCH/directoryname, where directoryname is the same as filename.
Step 6 Create the new kernel by entering the following command:
# cd ../directoryname
# make
Step 7 Copy the vmunix or vmunix_small file, created in the previous step, by entering the following command:
cp ./vmunix /vmunix
# cp ./vmunix_small /vmunix
Step 8 Reboot your system.
The modified kernel is now loaded and ready to use with Sybase.
For more information on modifying the kernel, refer to the Sun Workstation and Network Administration publication.
To ensure that CiscoWorks runs successfully, you may need to perform several post-installation tasks. The following sections contain instructions for these tasks:
During installation, several log files are created to track the installation process and provide diagnostic information if a problem arises.
When you are satisfied that CiscoWorks is properly installed and operating, you can remove each log file by entering the following command.
#rm /usr/tmp/unbundled/log/filename.log
rm *.log to remove the CiscoWorks log files because other applications can put log files in these directories, and you may need to keep those application's log files.
The log files are described in Table 2-1.
| Log Filename | Contents |
|---|---|
| cwconfigure.defs | Your responses to the prompts during the configuration. (This file is not removed because you may want to use the same answers if you need to reinstall CiscoWorks. The software will use these answers as the defaults when you next install CiscoWorks.) |
| cwconfigure.log | Configuration log messages. |
| cwinstall.log | Installation log messages. |
| install.log | Messages logged while extracting files from CD-ROM. |
CiscoWorks is based on the OSF/Motif windowing system and requires Motif key mapping. During installation, you are alerted that you need Motif key mapping. The installation script then offers to update the XKeysymDB (key mapping) file for you in case you are using a different platform, such as OPEN LOOK. If necessary, you can also manually update the XKeysymDB file by appending $NMSROOT/etc/XKeysymDB to your XKeysymDB file.
You can customize certain features of your CiscoWorks and NMS environments by modifying the X Windows resource files. X resources are listed in each user's .Xdefaults file or in the system X resource files located in the /usr/lib/X11/app-defaults directory. For example, you can change the window display colors, fonts, or sizes, or specify certain ways for CiscoWorks to run in your X Windows environment.
This section provides information on the following topics:
You can customize any X resource that CiscoWorks applications use, including colors, fonts, and sizes in CiscoWorks windows. To use your own colors, fonts, and sizes for CiscoWorks, perform one of the following procedures:
When working with CiscoWorks applications, you may notice that the window sizes 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 modify the default CiscoWorks window size, perform the following steps:
Step 1 Use a text editor such as vi to open the $HOME/XCiscoWorks file.
Step 2 Add the following line to your $HOME/XCiscoWorks file:
XCiscoWorks*geometry:500x400+0+0
Step 3 Save the $HOME/XCiscoWorks file and quit the text editor.
Step 4 Enter the following command at the UNIX prompt:
xrdb -merge ~/XCiscoWorks
CiscoWorks features an expanded Help system with hyperlinks (jumps to other help windows) to help you learn more about your CiscoWorks applications.
By default, hyperlinks display link text in forest green. To change the color, you can modify the X resource HyperHelp*LinkColor.
The current default help settings are modeled after Microsoft Help's color scheme. To change the default setting for windows, fonts, and other options, modify lines in your X resource HyperHelp file.
| Caution For CiscoWorks online help to display correctly on a system running SunOS and the OPEN LOOK window manager, you must run the following command before you start CiscoWorks, or add it to your .cshrc or .profile file so it is read when you log in to your system:% xrdb -merge /usr/lib/X11/app-defaults/HyperHelp |
To modify the X resources for your Help windows, perform the following steps:
Step 1 Change to the directory where the HyperHelp X resource file is located:
cd /usr/lib/X11/app-defaults
You may have put the HyperHelp file in a different directory; if so, change to the appropriate directory path.
Step 2 Use a text editor such as vi to alter any of the following X resources in the HyperHelp file:
Step 3 Save the HyperHelp file and exit.
Step 4 Restart the online help system to allow the new HyperHelp system changes to take effect.
To define the look of your text editor window, perform the following steps, substituting the appropriate options:
Step 1 Confirm that X Windows is running.
To start an X window session, enter x11start or xinit at the UNIX command line.
Step 2 Use a text editor such as vi to open the .Xdefaults file.
Step 3 Add a line with the following format to the .Xdefaults file:
EditorFormat:command_string %s
Where command_string is the value or name of the X resource. For example, to specify the vi editor located in /usr/local/bin, add the following line to the .Xdefaults file:
EditorFormat:/usr/local/bin/vi %s
For example, to specify the vuepad editor located in /usr/vue/bin, add the following line to the .Xdefaults file:
EditorFormat:/usr/vue/bin/vuepad %s
Step 4 Save the .Xdefaults file and quit the text editor.
To enable boot file generation, edit the .Xdefaults file to specify the on state by performing the following steps:
Step 1 Confirm that X Windows is running.
To start an X window enter x11start or xinit at the UNIX command line.
Step 2 Use a text editor such as vi to open the .Xdefaults file.
Step 3 Add the following line to the .Xdefaults file:
Bootfile:on
Step 4 Save the .Xdefaults file and quit the text editor.
After you install CiscoWorks for the first time, you may need to reinstall it. For example, some files on your workstation might become damaged or corrupted. Reinstalling means that you delete all of the existing CiscoWorks files and reinstall them from the same version of CiscoWorks. When you reinstall CiscoWorks, you can do a new or upgrade install, as appropriate.
|
|