|
|
This chapter describes how to prepare for installing and configuring CiscoWorks, and provides worksheets to help you gather the necessary information.
Before you install the CiscoWorks network management software, confirm that your computer system meets the related hardware and software-version requirements. In addition, you should note any special requirements about how you want CiscoWorks installed. For example, CiscoWorks prompts you during installation to supply information such as where you want CiscoWorks installed and whether you are performing an upgrade or new installation.
If you do not have any special requirements, you can just press the Return key to accept a default selection.
To gather all the information you need to install CiscoWorks, first complete the Installation Worksheet on page 2-5. You can then refer to the worksheet, if necessary, as you proceed with the installation.
This section provides an overview of the recommended tasks to perform before installing and configuring CiscoWorks. Follow these steps to prepare for upgrading from CiscoWorks 1.0 or later, or for installing and configuring CiscoWorks for the first time. After completing these steps, you are ready to install and configure CiscoWorks on your system.
Before you install CiscoWorks on your system, make sure that your system meets the hardware and software requirements described in the following sections.
CiscoWorks requires the following hardware:
Software | Minimum Hard Disk Space Requirements |
|---|---|
| CiscoWorks | 150 MB |
| Sybase (provided with CiscoWorks) | 45 MB |
| SunNet Manager | 10 MB |
| Sybase tables storage | 25 MB |
| Total disk space (values are rounded up for improved performance) | 250 MB1 (minimum)
300 MB (recommended) |
| CiscoWorks Software and Applications | RAM Requirements |
|---|---|
| CiscoWorks1 software | 18 MB |
| CiscoWorks applications2 | 14 MB |
| Total RAM for CiscoWorks software and all CiscoWorks applications | 32 MB (minimum)
64 MB (recommended) |
| Total swap space | 64 MB (minimum)
128 MB (recommended) |
CiscoWorks requires the following software:
The Configuration Management application requires Cisco Systems Software Release 8.2 or later.
Depending on the router you are using, the Software Manager application requires a specific Cisco Systems Software Release according to the following table:
| Cisco Router Type | Router System Software Requirement |
|---|---|
| Cisco 3000 | Software Release 9.1(7.5) or later, or 9.1(8) or later |
| Cisco AGS+ | Software Release 9.1(7.5) or later, or 9.1(8) or later |
| Cisco 4000 | Software Release 9.14(3.4) or later, or 9.14(4) or later |
| Cisco 7000 | Software Releasen 9.17(5.2) or later, or 9.17(6) or later |
| All Cisco routers (collection of Cisco 3000, Cisco 4000, Cisco 7000, or AGS+ routers) | Software Release 9.21(0.26) or later; 9.21(1) or later; or 9.1(8) or later |
| Cisco 7000 routers on which you want to perform microcode upgrades | Software Release 9.17(5.2) or later; 9.17(6) or later; 9.21(0.32) or later; or 9.21(1) or later |
Before you install and configure CiscoWorks, use the CiscoWorks Installation and Configuration Worksheets to identify installation requirements and gather the information required for running the installation and configuration scripts.
When properly filled out, the CiscoWorks Installation Worksheet provides the information you must enter when running the ./extract_unbundled script, which physical installs CiscoWorks. After you install CiscoWorks, you are ready to configure it. The CiscoWorks Configuration Worksheet enables you to gather information required to run the ncsconfigure script, which physically configures CiscoWorks.
Complete both worksheets and refer to them when installing and configuring your CiscoWorks software.
The CiscoWorks Installation Worksheet and descriptions follow. (For your convenience, tear-out worksheets for installation and configuration are provided in Appendix B.)
This section explains each question on the Installation Worksheet. This information is required for the installation of CiscoWorks. To obtain and verify system information for some items in the worksheet, you will need to be logged in as a superuser. For information on how to log in as a superuser, refer to the section "Becoming a Superuser."
Your workstation must be running SunOS Version 4.1.2 or later before you can install CiscoWorks. To determine what version of SunOS you are using, enter the following command at the UNIX prompt:
hostname% uname -r
The SunOS version number displays on your monitor:
4.1.2
On your worksheet, indicate whether your system meets this requirement. If you check "No," you need to upgrade.
You must use OpenWindows Version 3.0 on your workstation. Confirm that your system is running this windowing system.
On your worksheet, indicate whether your system meets this requirement. If you check "No," you need to install OpenWindows Version 3.0.
SunNet Manager Software Release 2.0 must be installed on your workstation, before you can install CiscoWorks. To find out whether the SunNet Manager is installed on your system, enter the following command:
hostname% $SNMHOME/bin/snm_version
If you defined the SNHOME environment variable, the SunNet Manager software version displays. If the version number does not appear, reinstall the SunNet Manager software or refer to your Sun documentation for troubleshooting information.
On your worksheet, indicate whether your system meets this requirement. If you check "no," you need to upgrade.
CiscoWorks requires 250 MB of disk space in a single disk partition on your system. If the disk partitions on your system are full, with inadequate disk space available for CiscoWorks, create a disk partition, a file system, or both for CiscoWorks software.
On your worksheet, indicate whether your system meets this requirement. If you check "no," you need to increase the disk partition. If you are not sure whether your system meets this requirement, refer to the next section, "Calculating Disk Space Requirements."
Although the required disk space is displayed during installation, Cisco Systems recommends that you calculate the space ahead of time to ensure its availability. You need to allocate 45 MB of disk space for the CiscoWorks installation.
If you are upgrading from a previous version of CiscoWorks, add the amount of disk space used in the current $SYBASE/data directory, roughly 10 MB, to the 45 MB disk space requirement.
To estimate the disk space required for a CiscoWorks upgrade, perform the following steps at the UNIX prompt (%):
Step 1 Enter the following command:
This command reports the total number of kilobytes used by the $SYBASE/data directory.
Step 2 Divide the number of kilobytes in the $SYBASE/data directory by 1000.
This calculation gives you the approximate number of megabytes used in the $SYBASE/data directory.
Step 3 Add 45 MB to the number of megabytes calculated in step 2.
This is the disk space you will need to perform your installation upgrade.
Remember, if you are upgrading from a previous version of CiscoWorks, the process requires at least 10 MB of free space in the database.
To calculate the required disk space before you perform the installation, refer to Chapter 6, "Database Administration," in the CiscoWorks User Guide. To find out how much disk space is being used by your database, refer to the section "Verifying Available Disk Space" in the CiscoWorks User Guide for instructions on how to use the checkalloc command.
To find out how much disk space is available on your system, enter the following command:
hostname% df
The amount of disk space available in each file system is displayed. Select a file system that has sufficient disk space available for installing CiscoWorks. For detailed information on how to manage disk partitions and file systems, refer to the workstation and Network Administration publication.
The following overview summarizes the steps involved in creating a file system. For more information, refer to the workstation and Network Administration publication or the manual pages on mkfs, fsck, mkdir, fstab, and mount. If you are unfamiliar with repartitioning disks or creating file systems, contact a knowledgeable system administrator.
Step 1 Create an empty file system on the disk partition you plan to use.
Step 2 Verify the integrity of the empty file system.
Step 3 Create a mount point directory.
Step 4 Configure the file system table and edit the /etc/fstab file.
Step 5 Mount the new file system.
CiscoWorks requires a minimum of 32 MB of RAM (64 MB recommended). To find out how much RAM is available on your system, make sure you are logged in as a superuser. Then enter the following command at the UNIX prompt:
hostname# dmesg | grep mem
The entry "avail mem" indicates the amount of RAM memory available on your system.
On your worksheet, indicate whether your system has at least 32 MB of RAM. If you check "No," you need to upgrade.
CiscoWorks requires a minimum of 64 MB (128 MB recommended) of swap space on your system. To find out how much swap space is available on your system, make sure you are logged in as a superuser. Then use the following command at the UNIX prompt:
hostname# pstat -s
Output, similar to the following, displays on your monitor indicating the amount of swap space available on your system:
15608k allocated + 5960k reserved = 21568k used, 33448k available
In this case, total swap space is equal to 55016 (the sum of what is used and what is available). On your worksheet, indicate whether your system has at least 64 MB. If you check "No," you need to upgrade. If the swap space on your system is less than 64 MB, expand the swap space by following the instructions in the workstation & Network Administration publication.
After CiscoWorks is installed and configured, you can use several applications (nmconfman, nmconfig, nmautoinstall, nmswman, nmdevswman, nmpccmd, Configuration Snap-In Mgr, and Sync w/Sybase) with the Trivial File Transfer Protocol (TFTP). With TFTP and CiscoWorks, you can transfer configuration files between your system and other devices on your network that use SNMP.
In order for TFTP to operate, you must edit the /etc/inetd.conf file on your system as described in the section "Setting Up TFTP." You can perform this task either before or after CiscoWorks installation and configuration.
On your worksheet, indicate whether you want TFTP enabled on your system.
You can install CiscoWorks from a local or remote CD-ROM drive.
On your worksheet, indicate which method you will use.
If you are planning to install CiscoWorks from a CD-ROM drive attached to a remote system, find out whether you have a login account as a superuser (in other words, root) on that system. If you do not have superuser access to the remote system, contact the system administrator of the remote system to obtain a login account with superuser access to that system.
If you are installing CiscoWorks from a remote CD-ROM drive, obtain the complete host name of the remote system and make sure that this host name is listed in the /etc/hosts file on your system.
On your worksheet indicate whether you have superuser access, and enter the host name of the remote system.
The .rhosts file enables users to log into another user account on a remote system. If you plan to install CiscoWorks from a remote CD-ROM drive, the .rhosts file on that system must contain the host name of your local system and your username specified as a superuser. To verify the local host name and that your username is specified as superuser, access the .rhosts file by using a text editor such as vi or textedit.
For more information on the .rhosts file, refer to the SunOS Network Environment publication.
On your worksheet, indicate whether your host name is in the .rhosts file and your username is specified as a superuser.
The installation script requires you to specify the device name of the CD-ROM drive. You can either obtain the device name from your UNIX system administrator or display the contents of the /dev directory on your system by following these steps:
Step 1 Change to the /dev directory:
cd /dev
Step 2 Verify that you are in the /dev directory by entering the following command:
pwd
The directory path displays.
Step 3 List the devices available to your system to find out whether you have a device name similar to rs by entering the following command. (CD-ROM drives usually have device names similar to sr0, sr1, sr2, and so on.)
ls | more
A list of available devices displays on your monitor.
Step 4 To display the remainder of the list of devices, press the space bar.
If you cannot identify an appropriate device name for your CD-ROM drive, contact your UNIX system administrator for help in obtaining device information.
Check the appropriate box on your worksheet and, if applicable, specify the name of the device.
If you are installing CiscoWorks for the first time, check "new" on your worksheet.
If you are moving from an installed version of CiscoWorks (Version 1.0 or later) to Version 2.0, check "upgrade." If you are upgrading to CiscoWorks Version 2.0, you must fill out the additional "Upgrade Installation Information" section at the end of the worksheet.
 | Caution With CiscoWorks 2.0, a user can only belong to one group; therefore when upgrading, only the existing one-user-to-one-group associations will be preserved. After upgrading, you need to redefine all other user/group associations. |
You must specify the directory where you want the CiscoWorks software to be installed. If the directory does not already exist on your system, the installation script creates the directory and installs the software in that directory. The default directory path name is /usr/nms.
On your worksheet, indicate where the CiscoWorks software will be installed. If applicable, specify the the directory path name you plan to use.
All workstations contain a kernel. In order for the Sybase Version 4.9.12 software to work on your 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 sun4c, sun4m, or sun4n) or the
/usr/sys/ARCH /conf directory.
Most systems use a generic kernel that is stored in a configuration file called GENERIC. If the kernel was customized for your system, it might be stored in a customized 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.
When you are logged in as superuser, you can also modify the kernel manually by following these steps:
Step 1 Back up your existing configuration file by entering the following command:
cp /vmunix /vmunix.bak
Step 2 Change directories by entering the following command:
cd /usr/share/ARCH/conf or /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 name of the kernel config file:
cp GENERIC <filename>
Step 4 Add the following lines anywhere in the /usr/sys/ARCH/conf/<filename> file or /usr/share/ARCH/conf/<filename> file:
Step 5 At the UNIX prompt, enter the following command:
This command executes the configuration process and builds a directory called ../filename. You then return to the UNIX prompt.
Step 6 At the UNIX prompt, enter the following command:
cd ../<filename>
This command creates a file called vmunix or vmunix_small.
Step 7 Copy the vmunix or vmunix_small file, created in the previous step, by entering the following command at the UNIX prompt:
Step 8 Restart your system. The modified kernel is now loaded and ready for use with Sybase.
Step 9 For more information on modifying the kernel, refer to the Workstation and Network Administration publication.
If you allow the installation script to modify the kernel configuration file, the script automatically saves the old kernel configuration file and names it as vmunix.syb_inst.
On your worksheet, indicate the name of the kernel configuration file. If you want the installation script to modify the existing kernel, check GENERIC. If you want the installation script to modify a customized configuration file on your system, specify the name of this file.
This section explains items in the worksheet that are applicable only if you are upgrading from an existing version of CiscoWorks to CiscoWorks Version 2.0.
Specify the directory of your existing CiscoWorks software. The installation script installs the new CiscoWorks software in the directory you specify here.
On your worksheet, check "/usr/nms" to accept the default, or specify the path name for the directory.
During installation, the installation script accesses the existing Sybase database on your system. In order to access the existing Sybase database, the script prompts you to enter the Sybase password.
On your worksheet, specify the Sybase password (sa and nmsuper).
The CiscoWorks installation script installs a new version of Sybase, which requires 45 megabytes of disk space. The database should have 10 megabytes of free space before running the upgrade.
On your worksheet, indicate whether your system meets this requirement. If you check "No," you need to upgrade.
CiscoWorks provides support for TACACS. TACACS is an authentication protocol that requires users to supply a username and password in order to access Cisco devices.
When prompted by the installation script, you must indicate whether your network system will be set up as a TACACS server. On your worksheet, indicate whether your system is to be set up as a TACACS server.
If you set up your network system as a TACACS server, the TACACS daemon startup facility will be automatically added to your /etc/rc.local file. During installation, if you respond Y[es] to set up a TACACS server, you are then asked whether you want the TACACS daemon to start automatically when you restart the system. If you answer N[o], the TACACS daemon will still be added to your etc/rc.local file but will be commented out. On your worksheet, indicate whether you want this functionality.
If you elect to set up a TACACS server, you need to supply a username when prompted by the installation script. The username you supply here is the one that is requested when a user attempts to remotely login to managed Cisco devices.
If you elect to set up a TACACS server, you need to supply a TACACS password. On your worksheet, indicate the password for the specified TACACS username.
The TACACS extended account, named $enable$, is used to access routers that use the extended TACACS mode. For more information on the $enable$ account, see "Adding the Special TACACS Account," in Chapter 6 of the CiscoWorks User Guide. On your worksheet, indicate whether you want your system to run in extended TACACS mode.
If you answered Y[es] to accept an extended TACACS mode, you are then prompted to supply the password for the special TACACS $enable$ account. On your worksheet indicate the password that should be used for the extended TACACS user account.
The CiscoWorks Configuration Worksheet and descriptions follow. For your convenience, tear-out worksheets are available in Appendix B.
This section explains each question on the Configuration Worksheet. This information is required for the configuration of CiscoWorks. For detailed information on the /etc/passwd and /etc/group files, usernames, user IDs, group names, and group IDs, refer to the Sun System & Network Administration publication.
On your worksheet, indicate whether the CiscoWorks installation is a new installation or an upgrade. If you performed an upgrade, you must complete the last section of the worksheet that requires additional information on the upgrade configuration.
On your worksheet, indicate /usr/nms to accept the default, or enter the directory path.
In order for CiscoWorks users to access and use CiscoWorks, they must belong to a CiscoWorks group that is specified in the /etc/group file on your system. The configuration script prompts you to supply the group name you want to use for CiscoWorks users. The default name for the group is CscWorks. If you are upgrading from CiscoWorks 1.0 or later, you can use the CiscoWorks group name that you used for the previous version of CiscoWorks.
On your worksheet, check "CscWorks" to accept the default, or specify a unique name for the CiscoWorks group.
In order for the CiscoWorks software to work on your system, you must specify a CiscoWorks login account and username when prompted by the configuration script. Cisco recommends that you use the default username cscworks. The configuration script adds the CiscoWorks login account and username to the /etc/passwd file. In addition, the username is added to the CiscoWorks group in the etc/group file.
On your worksheet, indicate that you accept the default username or specify a unique name for the CiscoWorks login account.
The CiscoWorks group, which is created and added to the /etc/group file by the ncsconfigure script, must be assigned a unique number. The configuration script proposes a default group ID number. If you specify a different group ID number for the CiscoWorks group, make sure that no other group specified in the /etc/group file uses it.
On your worksheet, check "55" to accept the default, or specify a unique group ID number for CiscoWorks.
In order to specify usernames while running the installation script and allow users to access and use CiscoWorks, the following prerequisites apply:
If you need to create user login accounts, refer to the instructions in Sun System & Network Administration publication.
On your worksheet, enter the usernames for users who have valid login accounts on your system and need to access CiscoWorks. If you are upgrading from a previous version of CiscoWorks, the configuration script displays the usernames of existing CiscoWorks users. You can either accept them and or add new usernames.
Users with valid login accounts and usernames on your system have unique user ID numbers that are specified in the /etc/passwd file. The CiscoWorks login account, which is created and added to the /etc/passwd file by the configuration script, requires a unique user ID number. The configuration script proposes a default user ID number (100). To specify a different user ID number for the CiscoWorks login account, make sure that no other user login account uses it.
On your worksheet, check "100" to accept the default number, or specify a unique user ID number for the CiscoWorks username.
For users with valid login accounts and usernames on your system, you must specify their full names for the CiscoWorks login account in the /etc/passwd file.The configuration script proposes a default full name (CiscoWorks).
On your worksheet, check "CiscoWorks" to accept the default name, or specify a different full name for the CiscoWorks login account name.
The configuration script installs the CiscoWorks software in a directory on your system. The default directory is /usr/nms.
On your worksheet, check "/usr/nms" to accept the default name, or specify a different subdirectory for the Sybase software.
As a user, you interact with the UNIX operating system by means of a shell. Two standard shells used on UNIX systems are the C-Shell and the Bourne Shell. The C-Shell (/bin/csh) is the default shell you will use for Sybase-related tasks that are performed at the UNIX prompt.
On your worksheet, check "/bin/csh" to accept the default name, or specify a different subdirectory for the Sybase software, and if applicable, specify a shell of your choice.
The CiscoWorks software includes Sybase Version 4.9.1 software. In order for the Sybase software to work on your system, you must specify a Sybase login account and username. During database configuration, the script prompts you to supply the username for Sybase. Cisco recommends that you use the default username sybase. The script then adds the sybase login account and username to the /etc/passwd file. In addition, the username is added to the CiscoWorks group in the /etc/group file.
On your worksheet, check "sybase" to accept the default username, or specify a unique name for the Sybase login account.
Users with valid login accounts and usernames on your system have unique user ID numbers that are specified in the /etc/passwd file. The Sybase login account, which is created and added to the
/etc/passwd file by the configuration script, must be assigned with a unique user ID number. The script proposes a default user ID number (101). If you specify a different user ID number for the sybase login account, make sure that no other user login account uses it.
On your worksheet, check "101" to accept the default user ID, or specify a unique user ID number for the Sybase username.
The Sybase group, which is created and added to /etc/group file by the ncsconfigure script, must be assigned a unique number. The configuration script proposes a default group ID number (55).
On your worksheet, check "55" to accept the default group ID number, or specify one that is not already in use by a group in the /etc/group file.
Sybase requires that users with valid login accounts and usernames have their full names specified in their /etc/passwd files. A full name must be specified for the Sybase login account.
On your worksheet, check "sybase" to accept the default Sybase username, or specify a different full name for the Sybase login account.
On your worksheet, indicate that you accept the default home directory, or specify a different directory for the CiscoWorks software.
As a user, you will interact with the UNIX operating system by means of a shell. Two standard shells used on UNIX systems are the C-Shell and the Bourne Shell. The C-Shell (/bin/csh) is the default shell you will use for Sybase-related tasks that are performed at the UNIX prompt.
On your worksheet, check "/bin/csh" to accept the default shell, or specify a shell of your choice.
The CiscoWorks software must identify the directory where SunNet Manager (SNM) Software was installed on your system. Unless you installed the SNM software in a different directory, the SNM software is generally installed in the default directory /usr/snm.
Verify the directory where the SNM software is installed on your system. If it is installed in the
/usr/snm directory, check "/usr/snm" on your worksheet. Otherwise, specify the directory where the SNM software was installed.
The CiscoWorks Log Manager application uses a centralized log file, /var/log/nmslog, which gets messages from the UNIX syslogd process. If you want these messages to be logged to a different file, you can specify a different filename.
On your worksheet, check "/var/log/nmslog" to accept the default log file, or specify a different filename where the messages can be logged.
The CiscoWorks Log Manager application uses a centralized log file that gets messages from the UNIX syslogd process. The default facility is local7.
If you want to log both CiscoWorks messages and Cisco device messages and view them through the Log Manager application, use the default facility local7. Cisco routers use the local7 facility. If you specify a facility in the range of local0 through local6, only CiscoWorks messages are logged.
Information about the facility you choose will be stored in the $NMSROOT/etc/nms.rc file. At a later time, you can change the facility you use by modifying the rc.local file and either setting the NMSSYSLOG environment variable or editing the nms.rc file. For instructions on performing these tasks, refer to the CiscoWorks User Guide.
On your worksheet, check "local7" to accept the default facility, or specify a facility of your choice.
The configuration script asks you whether it can erase any other applications that are using this facility. If you answer no, the CiscoWorks log utility might not be able to use the Syslog facility to do the following:
On your worksheet, indicate whether you want the script to erase applications using the facility.
CiscoWorks contains a centralized log file called nmslog. This log file can be automatically purged and backed up every day. As a result, the log purging utility is started automatically by the UNIX cron daemon.
On your worksheet, indicate whether you want the nmslog file to be purged and backed up automatically.
If you are upgrading from an existing version of CiscoWorks, the configuration script prompts you for additional information. Enter this information in the section "Additional Information for an Upgrade Configuration," at the end of the worksheet.
The CiscoWorks software contains new MIB files. Upon installation, any MIB files that already existed on your system are automatically backed up in a file called mibs.bak in the $NMSROOT/etc directory under the appropriate CiscoWorks directory.
Check the box on the worksheet to indicate that you want to save your old MIB files.
You can specify whether you want the CiscoWorks daemons and the Sybase dataserver to be started automatically whenever the system is rebooted. If you allow them to be started automatically, the startup commands are added to the /etc/rc.local file on your system. Otherwise, you need to perform this task manually.
On your worksheet, indicate whether you want the CiscoWorks daemons and Sybase dataserver to be started automatically.
To perform the tasks associated with installing and configuring CiscoWorks, you must log into your system as a superuser (root). Being a superuser allows you to perform functions restricted from normal users.
If you are a relatively inexperienced UNIX user, limit your activities as a superuser to the tasks described in this publication. As a superuser, you can adversely affect your operating environment if you are unaware of the effects of the commands you use.
To become a superuser, you must know the root password. In the following examples, the root password is rootpassword.
If you are not logged in, enter the following commands to log in as a superuser:
login:rootPassword: <rootpassword>
The UNIX prompt changes to a pound sign (#), indicating that you are logged in as a superuser.
If you are already logged in, but not as root, enter the following commands to change your login to root:
hostname%suPassword:<rootpassword>
The UNIX prompt changes to a pound sign (#), indicating that you are logged in as a superuser.
If you are upgrading from CiscoWorks 1.0 or later, perform the steps outlined in the following sections; otherwise skip to the section "Verifying Installation of SunOS and SunNet Manager."
CiscoWorks accesses the Sybase database, so you must close all database files and shut down your database before starting the backup process. If you do not perform these steps before you perform your backup, the integrity of your backup cannot be ensured.
To shut down the database, perform the following steps:
Step 1 Log into your system as a superuser.
Step 2 At your UNIX prompt, enter the following:
setenv SYBASE $NMSROOT/sybase
Step 3 Execute the isql binary by entering the following:
$SYBASE/bin/isql -Usa -P <password>
If you have changed the password for the Sybase sa account, enter that password. If you have not changed the password, do not supply a password.
After starting isql, the prompt 1> displays.
Step 4 Enter the shutdown command as follows:
shutdown
go
The database shuts down, and the UNIX prompt displays.
Back up your entire CiscoWorks system, including the $NMSROOT directory, current database and map files, as well as any additional Sybase data files. For information on making backups of UNIX files, refer to the UNIX manual pages on tar(1) or cpio(1).
| Caution To prevent any 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, follow the instructions in the Sun documentation to upgrade your version of SunOS to Version 4.1.2 or later. After you install SunOS Version 4.1.2 or later, follow the instructions in the SunNet Manager 2.0 User's Guide to install SunNet Manager.
The Trivial File Transfer Protocol (TFTP) enables you to transfer files to and from remote systems. With TFTP, the files belonging to the CiscoWorks applications nmconfman, nmconfig, nmautoinst, nmswman, nmdevswman, and nmsync can be accessed, copied, modified, and downloaded to another file.
You must verify that the TFTP daemon is enabled, the TFTP environment variable is set correctly, and a tftpboot directory exists. Instructions for these tasks follow.
If you are using the standard Sun software, verify that TFTP daemon is enabled, by completing the following steps:
Step 1 Log in as a superuser.
Step 2 Using a text editor such as vi or textedit, edit the /etc/inetd.conf file.
Step 3 Look in the file /etc/inetd.conf for the line that invokes tftpd. If the line begins with a pound sign [#], remove the sign with your text editor. Depending on your system, the line that invokes the TFTP daemon may look similar to the following:
#tftp dgram udp wait root /user/etc/in.tftpd in.tftpd -s /tftpboot
Step 4 Save the changes to the edited file and exit your text editor.
Step 5 At the UNIX prompt, enter the following command to display the process id number for the inetd configuration.
The system response is similar to the following:
119 ? S 0:05 inetd
The first number in the output is the process ID of the inetd configuration.
Step 6 To enable your system to read the edited /etc/inetd.conf file, enter the following command:
kill -HUP 119
Step 7 Verify that TFTP is enabled by entering the following:
netstat -a | grep tftp
The output should be similar to the following:
udp 0 0 *.tftp *.*
If there is no output, TFTP is not enabled.
For additional information on TFTP, refer to the UNIX manual pages on tftp and tftpd commands.
TFTPTYPE is an environment variable used by the ncsconfigure script to indicate which type of TFTP is being used. The Sun TFTP daemon requires that a file that is being transferred must first exist as a "dummy" file on the destination system. Other implementations require that the file does not exist on the destination system.
TFTPTYPE can take the value OVERWRITE (the file must exist and is overwritten) or NOOVERWRITE (the file cannot be overwritten; it must not exist). If you are using the standard Sun TFTP daemon, no action is required to set the TFTPTYPE variable. Otherwise, you must set TFTPTYPE accordingly.
The /tftpboot directory can be used to save and store configuration files that are loaded to a device when using CiscoWorks applications supported by TFTP. For example, the SNMP device configuration file is saved in the form of a TFTP boot file.
Creating and using the /tftpboot directory on your system is optional. The /tftpboot directory is accessible by all users. To protect the security of your system and limit access to it, you can choose not to set up this directory on your system. However, without a /tftpboot directory, you will be unable to use the following CiscoWorks applications: AutoInstall, Configuration Manager, and Software Library Manager.
If you upgraded from an earlier version of CiscoWorks, the /tftpboot directory might already exist on your system. In that case, you need not perform these steps.
To create the /tftpboot directory perform the following steps:
Step 1 If the /tftpboot directory does not exist, use the following command to create it:
Step 2 The /tftpboot directory must have the appropriate permissions. Modify the permissions with the following command:
chmod 777 /tftpboot
As a result, all users accessing the /tftpboot directory will have read, write, and execute permissions.
After completing the worksheets and other preparations required to install CiscoWorks, proceed to Chapter 3, "Installing and Configuring CiscoWorks" for instructions on installing and configuring the CiscoWorks software.
|
|