|
|
To verify that Resource Manager was installed and configured correctly and to use all the Resource Manager modules, you need to add at least one device to the database. This chapter consists of the following sections:
In the previous chapter, you learned how to log in as an administrator. You can now add device information to the Resource Manager database. You need a manageable device (a device whose inventory information is tracked by Resource Manager) in order to verify the correct installation of Resource Manager. Log in to Resource Manager as the administrator as explained in the "Logging In as Administrator" section. You can add a device or import a device, as explained in the following sections.
Follow these steps to add device information:
Step 1 Click Admin on the button bar, then select Inventory > Add Devices. The Add a Single Device dialog box appears.
Step 2 Enter the access information and annotations for one device in the Add a Single Device dialog box. You must fill in the Device Name field. All other fields are optional. For more information about these fields, refer to the Resource Manager online help.
Step 3 Click Next. The Add Passwords dialog box appears. You must fill in the Read Community String field and verify the password. All other fields are optional. For more information about these fields, refer to the online help.
Step 4 To submit the basic device information to the device integration process, click Next. The Enter Authentication Information dialog box appears.
Step 5 If required, complete the Enter Authentication Information dialog box. All fields are optional. For more information about the fields, refer to the online help.
Step 6 Click Finish. The Single Device Add dialog box appears.
Step 7 Click View Status. The Add/Import Status Summary dialog box appears.
Use the Add/Import Status Summary dialog box to check the integration status of the device you specified. You should see the following device status:
| Device Status | Number of Devices |
|---|---|
| Managed | 0 |
| Alias | 0 |
| Pending | 1 |
| Conflicting | 0 |
| Suspended | 0 |
| Not Responding | 0 |
If the device responded very quickly, the Managed column might already contain 1 device when the Add/Import Status Summary dialog box appears.
Step 9 To update device status, click Update on the Add/Import Status Summary dialog box.
If the pending count goes from 1 to 0 after you click Update and the Managed field has 1 device, Resource Manager was installed and configured correctly. You might need to wait a couple of minutes for the device to become managed. Click Update on the Add/Import Status Summary dialog box every minute or so to check the current status of the device.
For more information about adding devices, refer to Learning to Use Cisco Resource Manager.
This section provides overview information about importing devices into the Resource Manager database. For complete instructions on importing devices, see Learning to Use Cisco Resource Manager or online help.
You can import devices in three ways:
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 the Resource Manager online help.
You can import devices by extracting data from your existing data source into a CSV file, then use this file as input into the Resource Manager database. You need to create a CSV file. Then, click Admin, and select Inventory > Import from File to access the CSV file and import the device information. For details and instructions on creating and importing from a CSV file, see Learning to Use Cisco Resource Manager or online help.
To import devices from CiscoWorks or CiscoWorks for Switched Internetworks (CWSI), the Sybase server must be running on the local host. In addition, you must make sure the user bin is a member of the CiscoWorks group before you start the Resource Manager server. To import devices from HP OpenView, HP OpenView must be running on the local host.
Click Admin, then select Inventory > Import from Local NMS to import devices from the databases listed in the Local Database Import dialog box. For details and instructions on importing from a local NMS database, see Learning to Use Cisco Resource Manager or online help.
To import devices from a remote NMS database, verify the remote shell daemon is running on the remote host and obtain access to the remote host. Click Admin, then select Inventory > Import from Remote NMS to import devices from the databases listed in the Remote Database Import dialog box. For details and instructions on importing from a remote NMS database, see Learning to Use Cisco Resource Manager or online help.
Now that you have added device information to the Resource Manager database, you can use the Resource Manager modules. This section explains how to set up each package:
You determine network availability and modify polling parameters with the Availability module. To access Availability, click Admin, then select 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 contains the 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.
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 Learning to Use Cisco Resource Manager and 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 syslog analysis, click
Admin, then select Syslog Analysis.
To set up syslog analysis, you need to perform the following tasks. Consult the online help for detailed instructions for these tasks.
Software Management performs system software, boot loader upgrades, and software configuration operations on groups of routers and switches. See the Cisco Resource Manager Release Notes for Solaris 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 8 MB of space for each image. You must also have a Trivial File Transfer Protocol (TFTP) 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 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 /usr/sbin/in.tftpd in.tftpd -s /tftpboot
Step 3 At the UNIX prompt, enter the following command to display the process identification 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 identified in Step 3)
Step 5 Verify that TFTP is enabled by entering either of the following commands:
# netstat -a | grep tftp
which returns output similar to the following:
or enter
localhost_machine_name
which returns the number of modules sent and received, for example
If the output indicates zero modules were received, 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 modules supported by TFTP. The /tftpboot directory is accessible by all users. If the /tftpboot directory does not exist, follow these steps to create it:
Step 1 Enter the following command to create the /tftpboot directory:
# mkdir /tftpboot
Step 2 Make sure all users have read, write, and execute permissions to the /tftpboot directory by entering the following command:
# chmod 777 /tftpboot
The /tftpboot directory now exists and has the correct permissions.Before you use Software Management, you might also need to modify the /usr/lib/cron/at.deny file as described in the following section.
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. In addition, if the usr/lib/cron/at.allow file exists, you need to add the user bin to the at.allow file.
Now that you have added device information and accessed additional Resource Manager modules, continue with the following section to learn about Resource Manager facilities and message logging.
|
|