Preparing to Use Essentials Applications

This chapter assumes that you have performed the client setup tasks described in Installing and Setting Up CiscoWorks2000 CD One on AIX.

This chapter consists of the following sections:

• If you installed CiscoWorks2000 CD One on the default port, enter:

Step 2 Click Connect. The Login Manager dialog box is replaced by the navigation tree.

• Proxy

• SNMP

• rcp

You can populate your network inventory by:

• Adding devices one at a time by entering the device information manually.

• Importing a group of devices from:

  • A comma-separated values (CSV) file or a device integration file (DIF) that you create from another information source.

  • A supported network management system (NMS) on the same host as your server (local import).

  • A supported NMS on a different host from your server (remote import).

Step 2 Enter the access information and annotations for one device.

You must fill in the Device Name field with the device name or IP address. For Inventory, all other fields in this dialog box are optional. For other applications, you might need to fill in other fields. For more information, refer to the Inventory online help.

Step 3 Click Next. The Enter Login Authentication Information dialog box appears.

You must fill in the Read Community String field and verify the password. For Inventory, all other fields in this dialog box are optional. For other applications, you might need to fill in other fields. For more information, refer to the online help.

Step 4 Click Next. The Enter Enable Authentication Information dialog box appears.

If required, complete this dialog box. For Inventory, all fields in this dialog box are optional. For more information, refer to the online help.

Step 5 Click Finish. The Add a Single Device dialog box appears.

Step 6 Click View Status. The Add/Import Status Summary dialog box appears.

Step 7 Use the Add/Import Status Summary dialog box to check the status of the device you specified. The dialog box should contain:

Device Status	Number of Devices
Managed	0
Alias	0
Pending	1
Conflicting	0
Suspended	0
Not Responding	0
Device Attribute Errors	0

If the device responded quickly, the Managed row might already contain one device.

If you added a device and the Add/Import Status Summary dialog box shows that the device status has not changed from pending within 15 minutes, check the status of all processes to make sure they are running normally:

To stop the DIServer process:

a. Select CiscoWorks2000 Server > Process Management > Stop Process. The Stop Process dialog box appears.

b. Click the Process radio button.

c. In the Process Name field, select DIServer, then click Finish.

To restart the DIServer process:

a. Select CiscoWorks2000 Server > Process Management > Start Process. The Start Process dialog box appears.

b. Click the Process radio button.

c. In the Process Name field, select DIServer, then click Finish.

After you configure your system and NMS, select Resource Manager Essentials > Administration > Inventory > Import from Remote NMS to import devices from the databases listed in the Remote Database Import dialog box.

To create the static view:

Step 2 Enter a view name, an optional description, and select a type of view (custom or private.) Only users with the system administrator role can create custom views.

Step 3 Select the view that has the devices you want to add from Views.

Step 4 Select the devices that you want from Devices and move them into Selected Devices.

To add another static view, repeat the procedure.

To make sure Contract Connection provides accurate contract status information, you must enter device serial numbers in the inventory entries of devices that have service contracts.

To check device attributes, select Resource Manager Essentials > Administration > Inventory > Check Device Attributes.

To edit device attributes:

Step 2 Select the device whose device information you want to edit, then click Next.

Step 3 Select one or more options, then click Next. A dialog box appears for each option you selected. The dialog box fields are blank; they do not display the current information.

• To retain the current value, leave the field blank.

• To change a value, enter the new information in the field. If you are changing a password, you must enter the username.

• To delete a value, click Delete next to the field. If you are deleting a password, you must also enter the username.

Note Verify your entries before you click Next in any dialog box. If you change device attributes, you cannot undo the change, except by reediting.

Step 5 When you finish with a dialog box:

Step 2 Select the test device view that you created from the All Views list, then click Add to add it to the Polled Views list.

This creates a view for Availability polling.

Note You must add views to the Polled Views list. Only polled views are monitored.

Step 3 Click Next. The Change Polling Options dialog box appears.

Step 4 Select 5 Minutes from the Verify device reachability every drop-down list, then click Finish.

Step 5 Wait for at least 10 minutes to make sure Availability polls the devices in your test device view.

Step 6 Select Resource Manager Essentials > Availability > Reachability Dashboard. The Reachability Dashboard appears.

Step 7 Click the view name. The devices in your test device view should appear in the Availability Monitor.

Step 2 Enter enable and the enable password. The prompt changes to host#.

Step 3 Enter configure terminal. You are now in configuration mode, and the prompt changes to host(config)#.

Step 4 To make sure logging is enabled, enter logging on.

Severity level informational means all messages from alerts to informationals will be logged to the server.

Step 7 Verify that Syslog is running:

a. From the CiscoWorks2000 interface, select CiscoWorks2000 Server > Administration > Process Management > Process Status. The Process Status dialog box appears.

b. Verify that the entry for Syslog Analyzer has the status Running.

Step 2 Enter enable and the enable password. The prompt changes to host(enable).

Step 3 To make sure logging is enabled, enter set logging server enable.

Step 4 To specify the server to receive the Catalyst switch syslog messages, enter set logging server 123.45.67.89 (where 123.45.67.89 is the IP address of the server).

Step 5 Set the appropriate logging trap level by entering set logging level 6.

Severity level 6 means all messages from level 0-5 (from alerts to notifications) will be logged to the server.

Step 6 Verify that Syslog is running.

a. From the CiscoWorks2000 interface, select CiscoWorks2000 Server > Process Management > Process Status. The Process Status dialog box appears.

b. Verify that the entry for Syslog Analyzer has the status Running.

local7.info     path/filename
 

where path/filename is the full path to a file.

Step 2 Make sure the syslog process (syslogd) can both read and write to the file.

Step 3 If you modified the /etc/syslog.conf file, restart the syslog process (syslogd). Enter the following command to stop and restart syslogd:

/bin/startsrc -s syslogd start and /bin/startsrc -s syslogd stop
 

If the start and stop command does not work, enter:

Step 2 Make a nondestructive change to the router configuration. For example, change the contents of the login banner by entering:

# enable
# configure terminal
 

The prompt changes to #>.

#> banner motd /
This is a test /
#> end
 

Step 3 Wait approximately 2 minutes for the Syslog message to be processed by the server.

Step 4 Select Resource Manager Essentials > Syslog Analysis > Standard Reports. The Standard Reports dialog box appears.

Step 5 Select the device for which you made a change. Click Help if needed.

Step 6 Click Next. The Select Dates and Report Type dialog box appears.

Step 7 Select:

• All Messages in the Report Type list.

• Today from the Dates list.

Step 8 Click Finish. The Syslog-Standard report appears.

Device software image files are up to 4 MB in size. To determine how much space you need, multiply the number of device software image files you plan to store by 4 MB. For example, if you plan to store 30 software image files, you need at least 120 MB in /var.

Step 2 Change preferences as appropriate.

For more information, refer to the online help.

Step 3 After you finish:

During Software Management installation, if the installation tool cannot find a TFTP server, it tries to add one. If the installation tool cannot find or create a TFTP server, install and enable the TFTP server and verify that a /tftpboot directory exists, as explained in the following sections.

You can choose the name of this user account because you can configure the Essentials server to use any user account. The default user account name is cwuser. The examples in this procedure use the default name cwuser. If you choose to use a different name, substitute that name for cwuser.

To create and configure the rcp remote user account, follow these steps while logged in as root:

# useradd -m -c "user account to authenticate remote copy operations" \ cwuser
 

Step 2 Navigate to the cwuser home directory.

Step 3 Create the .rhosts file by entering:

# touch .rhosts
 

Step 4 Change the owner of the .rhosts file by entering:

# chown cwuser:bin .rhosts
 

Step 5 Change the permissions of the .rhosts file by entering:

# chmod 0664 .rhosts
 

Step 6 If you did not use the default user name cwuser, use the user account that you created as the rcp remote user account.

a. Log on to the server as admin.

b. Select Resource Manager Essentials > Administration > Inventory > System Configuration.

The System Configuration dialog box appears.

Step 2 Using a text editor, edit the /etc/inetd.conf file.

• Look in the file /etc/inetd.conf for the line that invokes rshd. If the line begins with a pound sign (#), remove the pound sign with a text editor. Depending on your system, the line that invokes the rshd server might look similar to the following:

shell  stream  tcp   nowait  root   /usr/sbin/in.rshd   in.rshd

• Save the changes to the edited file and exit the text editor.

Step 3 At the UNIX prompt, enter the following 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:

root  119   1  0  12:56:14 ?           0:00 /usr/bin/inetd -s
 

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:

# kill -HUP 119 
 

where 119 is the process identification number identified in Step 3.

Step 5 Verify that rshd is enabled by entering:

# netstat -a | grep shell
 

which should return output similar to the following:

You can disable rcp if you do not want Essentials to use it with any devices.

Step 2 Select Use RCP for image transfer (when applicable).

To allow the user bin to use at:

Step 2 If an at.deny file exists in the /var/adm/cron directory, make sure bin is not listed in it. If necessary, remove bin from the at.deny file using a text editor.

Step 3 If neither an at.allow nor an at.deny file exist in the directory /var/adm/cron, create an at.allow file and add bin to it using a text editor.

To allow the user bin to use cron:

Step 2 If a cron.allow file exists in the /var/adm/cron directory, make sure bin is listed in it. If necessary, add bin to the cron.allow file using a text editor.

If you already added devices or imported them into Inventory and did not specify this information, you can change the device attributes.

When you integrate Essentials with Netsys running on a remote Windows NT system, you must perform some setup tasks that are not required when you integrate with Netsys running on the CiscoWorks2000 server or on a remote UNIX system.

The first procedure regenerates the baseline using the previous Netsys setup information, which is preserved during the upgrade. The previous reports are deleted and the baseline on the Netsys server is overwritten.

Step 2 Review events on the system generated by the source CRMrsh to determine if any errors occurred.

a. Select Start > Programs > Administrative Tools (Common) > Event Viewer to open the event viewer.

b. Select File > Application to view the application log.

c. Locate events with the source CRMrsh by using either the View > Filter Events... or View > Find... commands. Refer to the Event Viewer online help for more information.

Step 3 If the Event Viewer does not provide any useful information about Netsys integration problems, modify the debug level and repeat the setup process, as described in the following steps:

a. Start the Registry Editor by entering the command regedit at the command prompt or in the Run dialog box.

b. Select the registry key, My Computer > HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > crmrsh > Parameters.

The possible values for Debug level are 0x1, 0x2, 0x4 and 0x6.

c. Set the value of Debug to 0x06 to get the most detailed debug output in the Event Viewer.

d. Restart CRMrsh services by entering the following commands:

net stop crmrsh
 
net start crmrsh
 

e. Repeat the Netsys setup process on the CiscoWorks2000 server and use the Event Viewer to find any errors.

Step 4 If you find the CRMrsh message "The Client is not authorized to do remote commands" in the Event Viewer, follow these steps to correct the problem:

a. Verify that the CiscoWorks2000 host name is entered in the hosts file on the Netsys server.

b. Determine if the CiscoWorks2000 host name is resolved to a fully qualified name in the event log. If so, use the fully qualified host name (for example, cw2000.cisco.com) when you enter the crmrsh addrhost command.

c. Verify that the CiscoWorks2000 user name is entered correctly by examining the Registry keys rhosts and rusers, which are located at the Registry path, My Computer > HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > crmrsh > Parameters.

Step 2 Click Update at the bottom of the dialog box to update the archive status.

Step 3 Click on a device status to view details:

• Click Successful to display information about which configurations are archived. Click Close to close the window and return to the Configuration Archive Status Summary dialog box.

• Click Failed to display information about which configurations could not be obtained. To update the archive for failed devices, click on one or more device names or click Select All, then click Update Archive. The Running Configuration Status report appears. Click Update Status to refresh the device status in the archive. Click Close to return to the Configuration Archive Status Summary dialog box.

• Click Not Supported to display the devices not supported by the configuration archive. Click Close to return to the Configuration Archive Status Summary dialog box.

• Click Partial Failure to display the Catalyst 5000 devices whose submodules were not pulled into the archive. Click Close to return to the Archive Status Summary dialog box.