|
|
In the previous chapter, you added information for one device. Because you have added at least one device to the database, you can use the Resource Manager packages. This chapter provides information about setting up the Resource Manager packages and includes the following sections:
If you would rather continue populating the Resource Manager database before accessing the Resource Manager packages, see the Learning to Use Cisco Resource Manager manual for detailed instructions on importing devices from a file, from a local Network Management System (NMS) database, or from a remote NMS database.
Administrators use the Inventory package (Admin > Inventory) to look at the hardware configuration and software characteristics of managed devices. Before you can use Inventory, you need to log in with a valid administrator password and add devices to the Resource Manager database by using Inventory > Add Devices or the import functions.
You can add devices one at a time, from a file, from a local NMS database, or from a remote NMS database. In order to import devices from an NMS database, the Resource Manager administrator might have to work with the system administrator of the host on which the NMS database is running. For more information on importing locally or remotely, refer to Resource Manager online help.
The devices must be managed devices before you can use the inventory management features to view reports on the hardware and software characteristics. Once you have added managed devices, you can use the inventory management features without performing any other setup functions.
You determine network availability and modify polling parameters with the Availability package. To access Availability, click on Admin > Availability.
Before you can use Availability, you must configure at least one view (a group of devices) to be monitored, as shown in the following steps:
Step 1 Click Admin, then select Availability > Change Polling Options.
The Select Polled Views dialog box appears. The All Views list on the left contains all available views from which to choose. The Polled Views list on the right is the list of views to be polled.
Step 2 To add a view for monitoring, select one view from the All Views list, then click Add. The view is added to the Polled Views list on the right.
Step 3 Click Next. The Change Polling Options dialog box appears.
Step 4 To change the polling parameters, select a value from the list to change.
Step 5 Click Finish. The Availability Options dialog box appears notifying you that the availability options have been successfully changed.
Step 6 To exit the Availability folder, click on another folder in the navigation tree.
Now that you have configured one view and specified polling parameters, you can monitor devices and run various reports. For details about using Availability, see the Learning to Use Cisco Resource Manager manual and the Cisco Resource Manager online help.
Syslog analysis lets you centrally log and track messages generated by devices. You can use the logged error message data to analyze router and network performance. You can customize syslog analysis to produce the information and message reports that are important to your operation. To access the syslog analysis package, click
Admin > Syslog Analysis.
Before you can use syslog analysis, the administrator must configure the routers to forward syslog messages to Resource Manager. Follow these steps to enable router syslog messages to be sent to the Resource Manager server. You must repeat these steps for each router.
Step 1 Telnet to the device and login (host is used in the following example). The prompt changes to
host>
Step 2 Enter the command enable and the enable password. The prompt becomes
host#
Step 3 To enter the configuration mode, enter the command configure terminal. The prompt changes to
host(config)#
Step 4 To make sure logging is enabled, enter the command logging on.
Step 5 To specify the server that is to receive the router syslog messages, enter the following command:
logging 123.45.678.90
where 123.45.678.90 is the IP address of the Resource Manager server. Alternatively, you can enter the DNS name.
Step 6 To limit the type of messages that are logged to the Resource Manager server, enter logging trap informational. Informational indicates severity level 6, which means all messages from level 0 to 6 (from emergencies to informational) will be logged to the Resource Manager server.
Step 7 Exit the Telnet session.
Your routers are now configured to forward syslog messages to Resource Manager. Continue with the following section to complete the setup required for syslog analysis.
Now that you have enabled router syslog messages to be sent to the Resource Manager server, you need to verify that the syslog configuration file (/etc/syslog.conf) has the following settings:
The following sections explain how to configure and verify that the syslog configuration file has the correct settings.
You need to make sure that the syslog configuration file has the facility.level definition set to local7.info.The installation script adds this line to /etc/syslog.conf if it does not already exist. If CiscoWorks, or another package that uses the local7.info facility, is installed on the same server as Resource Manager, this line will already exist.
To ensure the file path is correct, examine the /etc/syslog.conf file and make sure it contains a line with local7.info that looks similar to
local7.info /var/log/syslog_info
The filename, syslog_info, might be different on your machine. Substitute syslog_info for the filename on your machine in the remaining sections.
Make sure the file path for the configuration file exists and is correct by following these steps:
Step 1 To make sure the /var/log/syslog_info file exists, enter the following command:
# ls -l /var/log/syslog_info
You should get something similar to
Step 2 If you do not receive a message similar to the one above, and the file does not exist, enter the following command:
# touch /var/log/syslog_info
You need to make sure that the syslog daemon (syslogd) can read and write to the configuration file by following these steps:
Step 1 To check the file permissions for the syslog_info file, enter the following command:
# ls -l /var/log/syslog_info
You should get something similar to
Step 2 If the file permissions are anything other than rw-rw-r--, enter the following command:
# chmod 664 /var/log/syslog_info
This sets the correct read and write permissions for the syslog_info file.
Before using syslog analysis, you need to make sure that the sa_filter.conf file exists in the /opt/CSCOpx/objects/data directory. This file specifies which router messages to exclude from Resource Manager. Administrators can edit the sa_filter.conf file to specify which messages to exclude. See Cisco Resource Manager online help for detailed instructions on editing the sa_filter.conf file.
Software Management performs system software, boot loader or microcode upgrades, and software configuration operations on groups of routers and switches. See the Cisco Resource Manager Release Notes for the devices supported by Software Management.
Before you can use Software Management, you must have sufficient space to store the software image files. You should have 2 to 4 MB of space for each image. You must also have a TFTP (Trivial File Transfer Protocol) server in order to use Software Management.
TFTP enables you to transfer files to and from remote systems. During the installation of Software Management, if the installation tool cannot find a TFTP server, it tries to add one. If the installation tool cannot successfully find or create a TFTP server, you need to create one.
You must first verify that the TFTP server is enabled and that a /tftpboot directory exists, as explained in the following sections.
If you are using the standard Solaris software, you can add and configure the TFTP server (TFTPD) by following these 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.
#], remove the pound sign with your text editor. Depending on your system, the line that invokes the TFTP server might look similar to the following:
tftp dgram udp wait root /user/etc/in.tftpd in.tftpd -s /tftpboot
Step 3 At the UNIX prompt, enter the following command to display the process identication number for the inetd configuration.
# /usr/bin/ps -ef | grep -v grep | grep inetd
The system response is similar to the following:
The first number in the output (119) is the process identification number of the inetd configuration.
Step 4 To enable your system to read the edited /etc/inetd.conf file, enter the following command:
kill -HUP 119 (where 119 is the process identification number)
Step 5 Verify that TFTP is enabled by entering the following command:
# netstat -a | grep tftp
The output should be similar to the following:
If there is no output, TFTP is not enabled. Repeat these steps, beginning with Step 1, to make sure you have enabled TFTP.
The /tftpboot directory is used to save and store files that are loaded to a device when using Resource Manager packages supported by TFTP. The /tftpboot directory is accessible by all users.
To create the /tftpboot directory, follow these steps:
Step 1 If the /tftpboot directory does not exist, use the following command to create it:
# mkdir /tftpboot
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 have read, write, and execute permissions.
Now that you have performed the necessary setup tasks, you can use Software Management.
Continue with Chapter 4, "Facility Administration and Message Logging," to learn more about Resource Manager error and log messages.
Software Management uses at to schedule Software Management image transfers to devices, and the process that performs the download is executed as bin. Solaris includes the user bin in the /usr/lib/cron/at.deny file. Because the software transfer operation requires bin to be able to run at, you need to remove the user bin from this file. Use a text editor to remove the user bin from the /usr/lib/cron/at.deny file.
|
|