Table Of Contents
Preparing to Use Essentials Applications
Adding or Importing Inventory Data
Adding Device Information Manually
Changing Device Attributes (Credentials and Serial Numbers)
Setting Up and Verifying Availability
Configuring Devices for Syslog Analysis
Verifying the Settings in the Syslog Configuration File
Setting Up Software Management
Verifying Space Required for Downloaded Files
Adding Device Passwords to Inventory
Setting Software Management Preferences
Creating the /tftpboot Directory
Creating the rcp Remote User Account
Selecting rcp as the Active File Transfer Method
Allowing the User casuser to Use at and cron
Setting Up Configuration Management
Modifying Device Configurations
Make Sure Devices Are rcp-enabled
Make Sure Devices Are SSH-enabled
Configure Devices for Syslog Analysis
Verifying Device Configurations
Preparing to Use Essentials Applications
After installing and setting up Resource Manager Essentials (Essentials), you must configure the server for Essentials and configure the Essentials applications for use.
This chapter assumes that you have performed the client setup tasks described in Installation and Setup Guide for Common Services on Solaris.
This chapter consists of:
•
Setting Up and Verifying Availability
•
•
Preparation Overview
Table 2-1 lists the prerequisite tasks for using Essentials applications. It contains references to more detailed information about each task.
Table 2-1 Preparing To Use Essentials Applications Task Overview
1.
Enter information about the proxy server, SNMP, SMTP, and rcp
2.
Configure items on the devices that are to be monitored by Essentials.
3.
a.
•
•
b.
c.
If you do not have login privileges, go to the Cisco.com home page, www.cisco.com, to obtain a login.
d.
"Changing Device Attributes (Credentials and Serial Numbers)" section.
e.
•
•
•
Inventory online help.
4.
a.
"Setting Up and Verifying Availability" section and "Creating a Device View" section.
b.
5.
a.
b.
"Verifying the Settings in the Syslog Configuration File" section.
c.
6.
a.
b.
c.
If you do not have login privileges, go to the Cisco.com, to obtain a login.
d.
e.
f.
g.
•
•
•
•
•
Software Management online help.
7.
a.
b.
c.
d.
•
•
•
•
"Setting Up NetConfig" section and NetConfig online help.
e.
•
•
•
•
NetConfig online help.
Accessing the Server
When you access the CiscoWorks Server, the CiscoWorks screen appears with the Login Manager displayed.
To access the server from a client system, enter any one of these URLs in your web browser:
•
http://server_name:1741•
https://server_name:1742where server_name is the hostname of the server on which you installed Essentials.
•
http://server_name:port_numberwhere server_name is the name of the server on which you installed Common Services and Essentials, and port_number is the alternative port assigned during the installation. See the User Guide for CiscoWorks Common Services for information about administrator logins.
Logging In
To perform server setup tasks, you must log in as the system administrator:
Step 1
User Name: adminPassword: passwordFigure 2-1 Login Manager Dialog Box
Step 2
The Login Manager dialog box is replaced by the navigation tree.
Configuring the Server
You can configure system-wide information for Essentials applications using the System Configuration option. You should verify that the defaults are correct, if not enter the corrections.
Step 1
The System Configuration dialog box appears (Figure 2-2).
Figure 2-2 System Configuration Dialog Box
Step 2
•
•
•
•
See Table 2-2 for descriptions of the information in each dialog box tab.
Step 3
Step 4
The dialog box is displayed until you select another option from navigation tree.
Setting Device Credentials
Several important items must be configured correctly on every Cisco device that will be managed and monitored through Essentials.
Details about each application and the tasks involved in setting the credentials are available later in this document. For details see Table 2-1.
Table 2-3 lists all the applications and the device credentials required for proper functioning of the applications.
Table 2-3 Applications and the Device Credentials
NetConfig
Required
Required
Required
Not required1
NetShow
Required
Required
Required
Not required
Config Editor
Required
Required
Required
Not required2
ChangeAudit
Not required
Not required
Required
Not required
Configuration Management (Telnet)
Required
Required
Required
Not required
Configuration Management (TFTP)3
Not required
Not required
Required
Required
Inventory
Not required
Not required
Required
Not required
SWIM
Required4
Required4
Required
Required
Syslog
Not required
Not required
Required
Not required
Availability
Required
Required
Required
Not required
1 After execution of a job, NetConfig provides an option to fetch the configuration using TFTP. SNMP Read/Write credentials are required in such cases.
2 After execution of a job, Config Editor provides an option to fetch the configuration using TFTP. SNMP Read/Write credentials are required in such cases.
3 The file vlan.dat can be fetched only if telnet password and enable password are supplied.
4 Required in case of few devices like PIX devices, Cisco 2950 series switches.
Setting Up Inventory
As a network administrator, you need to be able to quickly troubleshoot problems on the network, identify when network capacity is being reached, and provide information to management on the number and types of devices that are used on the network.
If the network goes down, one of the first things you will need to know is what devices are running on the network. The Inventory application in Essentials caters to these requirements.
This section describes the tasks that you must perform to set up the Inventory application.
For detailed information see User Guide for Resource Manager Essentials 3.5.
Adding or Importing Inventory Data
You must have at least one managed device (a device whose inventory information is tracked by Essentials) to verify correct Essentials installation. To manage your network, you need to add device information for all your managed devices.
To populate your network inventory:
•
•
–
–
–
–
The supported NMS software is described in the "Supported NMS Environments for Device Import" section.
Adding Device Information Manually
This section describes how to add devices one at a time and how to troubleshoot problems you might have, using this method.
Step 1
The Add a Single Device dialog box appears.
Step 2
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
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
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
The Single Device Add dialog box appears.
Step 6
The Add/Import Status Summary dialog box appears.
Step 7
The dialog box should contain:
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.
Step 8
If the pending count goes from 1 to 0 after you click Update and the Managed field has 1 device, Essentials 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 current device status.
If you added a device and the Add/Import Status Summary dialog box shows that the device status has not changed from Pending even after 15 minutes, check the status of all processes to make sure they are running normally.
•
•
Even if the DIServer process has the state Running Normally, it might be in an error state. You need to stop and restart it.
•
a.
The Stop Process dialog box appears.
b.
c.
•
a.
The Start Process dialog box appears.
b.
c.
Step 9
The device status should change to Managed within a couple of minutes.
Importing Devices
You can import devices either from a file or a network management system (NMS). The NMS can be either local or remote.
•
•
For a list of supported NMS software, see the"Supported NMS Environments for Device Import" section.
•
–
–
–
•
–
If you have difficulty importing device information:
•
•
For additional information, refer to the online help.
Creating a Device View
After you have added devices into the Essentials inventory database, you can define views to logically group devices into locations, types, or areas of responsibility. Device Views allow you to quickly view reports on all devices of a certain type or with specific characteristics, such as all Catalyst® switches.
Three categories of device views are available in Essentials:
•
•
•
Two different types of views can be created within the Custom or Private categories (all system views are dynamic views):
•
If devices are added to the inventory with the same value, or an existing devices attribute is changed to the same value, as the value for the attribute that a dynamic view is based on, then they will be automatically added to the view.
An example of a dynamic view is all devices with Cisco IOS Version 12.0. Any devices that currently have this attribute would be included in the device view. All system views are dynamic.•
To set up and verify the Essentials applications, you must create a static device view (a group of devices) that includes at least one device. For additional information, refer to the online help.
To create a static device view:
Step 1
The Add Static Views dialog box appears.
Step 2
Step 3
Step 4
Step 5
Changing Device Attributes (Credentials and Serial Numbers)
To make sure your devices have the correct device access, password information, and user information, you can change the device attributes.
Contract Connection lets you verify which of your Cisco IOS® devices are covered by a service contract. Contract Connection uses Inventory Manager, Cisco.com and the Cisco internal contract tracking service, Contract Agent, to provide the status of your service coverage.
For Contract Connection to provide accurate contract status information, you must enter device serial numbers to the inventory entries of devices that have service contracts.
To edit device attributes:
Step 1
The Change Device Attributes dialog box appears.
Step 2
The Change Device Attributes dialog box displays the options.
Step 3
A dialog box appears for each option you selected. The dialog box fields are blank; they do not display the current information.
Step 4
•
•
•
Note
Step 5
•
•
Setting Up and Verifying Availability
If users experience connectivity problems while trying to reach certain resources or services on the network, you should check whether or not any devices have gone down. If a device is unreachable, you will want to find out when it was last operational and if any abnormal reloads have occurred.
The Availability function within Essentials helps you track whether a device can be reached on your network.
To verify that the Availability function is working correctly, you must have a test device view with at least one device. You can use the view you created during Inventory setup. Use this test view to verify that the Availability function displays the devices in the Reachability Dashboard.
Step 1
The Select Polled Views dialog box appears.
Step 2
This creates a view for Availability polling.
Note
Step 3
The Change Polling Options dialog box appears.
Step 4
Step 5
Step 6
The Reachability Dashboard appears.
Step 7
The devices in your test device view should appear in the Availability Monitor.
Now that you have configured one Availability view and specified polling parameters, you can monitor devices and run reports. For details about using Availability, refer to the online help.
Setting Up Syslog Analysis
Syslog Analysis lets you centrally log and track messages generated by devices. You can use the logged error message data to analyze device and network performance. You can customize Syslog Analysis to produce the information and message reports that are important to your operation.
See the online help for more information about Syslog Analysis.
Setting up Syslog Analysis involves:
•
•
Specifying Country Codes
You must update the country code entry in the file, Sa.properties with the appropriate country code to make sure the Syslog timestamp conversion works correctly. Sa.properties is located in the directory, $NMSROOT/lib/classpath/com/cisco/nm/sysloga/sa, where $NMSROOT is the directory in which CiscoWorks is installed.
The country code is the 3-letter abbreviation specified according the ISO_3166 document.
For a list of country codes, refer to the file, CountryCode.txt, located in the directory, $NMSROOT/lib/classpath/com/cisco/nm/sysloga/CountryCode.txt.
Note
To terminate Syslog Analyzer, at the command prompt, enter:
$NMSROOT/bin/pdterm SyslogAnalyzerTo start Syslog Analyzer, at the command prompt, enter:
$NMSROOT/bin/pdexec SyslogAnalyzerConfiguring Devices for Syslog Analysis
Before you can use Syslog Analysis, you must configure your devices to forward messages to Essentials or to a system on which you have installed the distributed Syslog Analyzer Collector. For more information about setting up devices for message logging, refer to the online help, the Cisco IOS software documentation on Cisco.com (for Cisco IOS devices), and the appropriate reference guides.
Configuring Cisco IOS Devices
To configure Cisco IOS devices:
Step 1
The prompt changes to host>.
Step 2
Step 3
The prompt changes to host#.
Step 4
You are now in configuration mode, and the prompt changes to host(config)#.
Step 5
Step 6
Step 7
Step 8
a.
The Process Status dialog box appears.
b.
Step 9
Configuring Catalyst Devices
To configure Catalyst devices:
Step 1
The prompt changes to host>.
Step 2
The prompt changes to host(enable)
Step 3
Step 4
Step 5
Severity level 6 means all messages from levels 0-6 (from alerts to notifications) will be logged to the server.
Step 6
a.
The Process Status dialog box appears.
b.
Step 7
Verifying the Settings in the Syslog Configuration File
To check the path and permissions of the file pointed to by local7.info in the syslog configuration file /etc/syslog.conf on the server:
The first occurrence of local7 in the syslog.conf file, must contain the path for the Syslog message source.
Step 1
local7.info path/filenamewhere path/filename is the full path to a file.
Step 2
If you modified the /etc/syslog.conf file, you must restart the syslog process (syslogd). Enter the following command to stop and restart syslogd:
/etc/init.d/syslog start and /etc/init.d/syslog stopIf the start and stop command does not work, enter:
kill -HUP `cat /etc/syslog.pid`Step 3
Verifying the Syslog Analyzer
To verify that the Syslog Analyzer is processing messages from the network:
Step 1
Step 2
# enable# configure terminalThe prompt changes to #>.
#> banner motd /This is a test /#> endStep 3
Step 4
The Standard Reports dialog box appears.
Step 5
Step 6
The Select Dates and Report Type dialog box appears.
Step 7
•
•
Step 8
The Syslog-Standard report appears.
Verify that the report contains the Syslog message that the configuration change generated .
Setting Up Software Management
Cisco is constantly improving the quality and functionality of device software. As a network administrator, you need to know what versions are currently running on your devices, and you must keep informed of new software versions available to identify when upgrades are needed.
When software upgrades are required, you must plan for and manage the upgrade to minimize the disruption to the end users. The process of manually upgrading multiple devices on the network can be a very time-consuming and error-prone process.
Software Management application performs system software upgrades, boot loader upgrades, and software configuration operations on groups of routers and switches. For more information about setting up Software Management, see the online help.
Setting up Software Management involves the following:
•
•
•
•
Verifying Space Required for Downloaded Files
Software Management files downloaded to the server from the Cisco.com or the product CD-ROM are stored in the /var directory or its subdirectories. Make sure there is enough space in the /var directory for all files that you plan to download.
Device software image files maybe in a range from 4 MB to 20 MB in size. In addition, you need space for some smaller downloaded files and temporary files. To accommodate these needs, add at least 20% to the space needed for software image files for your final space calculation in the /var directory.
Adding Device Passwords to Inventory
Before you can use Software Management to manage device software images, you must add the required device passwords to Inventory. To add device passwords to Inventory, see the "Changing Device Attributes (Credentials and Serial Numbers)" section or the online help.
Setting Software Management Preferences
Software Management has many preferences you can set to control how the application behaves. To set preferences:
Step 1
The Edit Preferences dialog box appears.
Step 2
Step 3
•
•
Setting Up TFTP
A file transfer server must be installed on your system. You must enable a Trivial File Transfer Protocol (TFTP) server because it is the default file transfer server type.
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.
Enabling the TFTP Daemon
If you are using standard Solaris software, you can add and configure the TFTP server (TFTPD).
Step 1
Step 2
•
tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot•
Step 3
# /usr/bin/ps -ef | grep -v grep | grep inetdThe system response is similar to:
root 119 1 0 12:56:14 ? 0:00 /usr/bin/inetd -sThe first number in the output (119) is the process identification number of the inetd configuration.
Step 4
# kill -HUP 119where 119 is the process identification number identified in Step 3.
Step 5
# netstat -aor
# grep tftpwhich should return output similar to:
*.tftp Idleor enter:
# /opt/CSCOpx/bin/mping -s tftp localhost_machine_namewhich returns the number of modules sent and received, for example:
sent:5 recvd:5 . ..If the output shows that zero modules were received, TFTP is not enabled. Repeat these steps, beginning with Step 1, to make sure you have enabled TFTP.
Creating the /tftpboot Directory
Essentials uses the /tftpboot directory when transferring files between the Essentials server and network devices. The files are removed after the transfer is complete, but multiple jobs (for example, image distribution, image import, or config file scan) could be running at the same time.
Each of these jobs requires its own space. Software image sizes, for example, can be up to 20 MB. To ensure that jobs run successfully, make sure there is sufficient space available in the /tftpboot directory.
If the /tftpboot directory does not exist on your system, you must create it:
Step 1
# mkdir /tftpbootStep 2
# chmod 777 /tftpbootThe /tftpboot directory now exists and has the correct permissions.
Setting Up rcp
You can enable a remote copy (rcp) server on the server and select it as the active file transfer server. If you select rcp as the active server and then try to transfer files to a device that does not support rcp, Essentials uses TFTP to transfer the files.
Creating the rcp Remote User Account
To use rcp, you must create a user account on the system to act as the remote user to authenticate the rcp commands issued by devices. This user account must own an empty .rhosts file in its home directory to which the user casuser has write access.
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:
Step 1
# useradd -m -c "user account to authenticate remote copy operations" \ cwuserStep 2
Step 3
# touch .rhostsStep 4
# chown cwuser:casusers .rhostsStep 5
# chmod 0664 .rhostsStep 6
a.
b.
c.
d.
Enabling the rcp Daemon
To add and configure standard Solaris rcp server software:
Step 1
Step 2
•
shell stream tcp nowait root /usr/sbin/in.rshd in.rshd•
Step 3
# /usr/bin/ps -ef | grep -v grep | grep inetdThe system response is similar to:
root 119 1 0 12:56:14 ? 0:00 /usr/bin/inetd -sThe first number in the output (119) is the process identification number of the inetd configuration.
Step 4
# kill -HUP 119where 119 is the process identification number identified in Step 3.
Step 5
# netstat -a | grep shellwhich should return output similar to:
*.shell *.* 0 0 0 0 LISTEN
Selecting rcp as the Active File Transfer Method
If you have enabled rcp as the file transfer method, Essentials uses rcp to transfer device software images. For devices that do not support rcp, Essentials uses TFTP to transfer files.
You can disable rcp if you do not want Essentials to use it with any devices.
Step 1
Step 2
Step 3
Allowing the User casuser to Use at and cron
Software Management uses at and cron to schedule Software Management image transfers to devices. The process that performs the download is executed as casuser, so the user casuser must be allowed to use at and cron.
To allow the user casuser to use at:
•
•
•
To allow the user casuser to use cron:
•
•
•
Setting Up Configuration Management
One of the most difficult but most important things to manage on network devices is the device configuration. Often a change to the device configuration leads to network performance issues and faults. The device configuration is the key to how a device operates on the network and traffic is passed.
As the network administrator, you need to be able to control and track changes to device configurations in order to minimize errors and assist in troubleshooting problems. This can be very difficult if several people are making changes to the device configurations. It can also become very repetitive and time-consuming to have to make the same update to each individual device on the network. Configuration Management application can help simplify and automate these tasks.
Before Configuration Management can gather device configurations, you need to update the Essentials database with passwords (credentials) and modify device configurations.
Entering Device Credentials
Before the configuration archive can use Telnet to gather device configurations, enter the following device credentials:
•
•
•
–
–
–
If you already added devices or imported them into Inventory and did not specify this information, you can change the device attributes.
See the "Changing Device Attributes (Credentials and Serial Numbers)" section or the Inventory online help for more information.
Modifying Device Configurations
You need to modify your device configurations so that Configuration Management can gather the configurations. After you perform the following procedures and your devices become managed, the configuration files are collected and stored in the configuration archive.
Make Sure Devices Are rcp-enabled
Make sure the devices are rcp-enabled by logging into each device and entering the following commands in the device configurations:
# ip rcmd rcp-enable# ip rcmd remote-host local_username 123.45.678.90 remote_username enablewhere 123.45.678.90 is the IP address or hostname of the system on which Essentials is installed. The default remote_username and local_username are casuser.
Make Sure Devices Are SSH-enabled
Make sure the devices are SSH-enabled by logging into each device and entering the commands for the following kinds of devices:
•
For Catalyst Switches Running CatOS
To enable SSH on Catalyst switches do the following:
Step 1
sec-cat6000> (enable) set crypto key rsa 1024A message similar to the following appears:
Generating RSA keys..... [OK]Step 2
sec-cat6000> (enable) ssh_key_process: host/server key size: 1024/768Step 3
sec-cat6000> (enable) show crypto keyA message similar to the following appears:
RSA keys were generated at: Mon Jul 23 2001, 15:03:30 1024 65537 15144146953605773328536717047857098506066347687468697169639403524406206785753387015 508885256996914783305378400669569876102078109594986481799653300180108447858634 727730676971852564183862430018810088305612411373816928200786743760582755731334 485293321996682019301329470978268059063378215479385405498193061651Step 4
Note
WARNING!! IP permit list has no entries!sec-cat6000> set ip permit 172.18.124.0 255.255.255.0A message similar to the following appears:172.18.124.0 with mask 255.255.255.0 added to IP permit list.Step 5
sec-cat6000> (enable) set ip permit enable sshA message similar to the following appears:
SSH permit list enabled.Step 6
sec-cat6000> (enable) sho ip permitA message similar to the following appears:
Telnet permit list disabled.Ssh permit list enabled.Snmp permit list disabled.Permit List Mask Access-Type---------------- ---------------- -------------172.18.124.0 255.255.255.0 telnet ssh snmpDenied IP Address Last Accessed Time Type----------------- ------------------ ------
For Cisco IOS Routers
To enable SSH on Cisco IOS Routers do the following:
For example, if you want router1 to act as an SSH client to the another router, you can add SSH to a second router, say router2. The routers will then be in a client-server arrangement, with router1 acting as the server and router2 acting as the client. The IOS SSH client configuration on router2 is the same as required for the SSH server configuration on router1.
Step 1
hostname router1A message similar to the following appears:
username username password 0 passwordStep 2
ip domain-name domain-nameStep 3
cry key generate rsaA message similar to the following appears:
ip ssh time-out 60ip ssh authentication-retries 2Step 4
Note
line vty 0 4transport input SSH
Configure Devices for Syslog Analysis
Configure your devices for Syslog Analysis if you want the device configurations to be gathered and stored automatically in the configuration archive when syslog messages are received. See the "Setting Up Syslog Analysis" section or refer to the online help for more information.
Modifying Device Security
Configuration Management must be able to run certain commands on devices to archive their configurations. You must disable the security on devices that prevents Configuration Management from running the commands shown in Table 2-4.
Setting Up NetConfig
The NetConfig function provides wizard-based templates to simplify and reduce the time it takes to roll out global changes to network devices. These templates can be used to execute one or more configuration commands on multiple devices at the same time.
For example, if you want to change passwords on a regular basis to increase security on devices, you can use the appropriate password template to update passwords on all devices at once. A copy of all updated configurations will be stored in the configuration archive.
This section describes how to set up NetConfig. This involves:
•
Verifying Device Configurations
NetConfig can configure only devices that have archived configurations. Use the Archive Status report to:
•
•
Step 1
The Configuration Archive Status Summary dialog box appears.
Step 2
Step 3
•
•
a.
b.
The Running Configuration Status report appears.
c.
d.
•
•
For more information, see the Configuration Management online help
Verifying Device Credentials
Verify that every device you want to configure using NetConfig has the correct device credentials entered in the Inventory application. NetConfig must have access to the correct credentials to make device configuration changes.
To verify device credentials, select Resource Manager Essentials > Inventory > Check Device Attributes. If any devices that you want to configure have incorrect credentials, see the "Changing Device Attributes (Credentials and Serial Numbers)" section or the online help.
Modifying Device Security
In addition to running the configuration commands that you assign to each job, NetConfig must be able to run certain commands on devices to configure them. You must disable the security on devices that prevents NetConfig from running the commands listed in Table 2-5.
Verify Device Prompts
NetConfig requires particular CLI prompt formats:
If the telnet transport mechanism is used, the following prompts are applicable.
•
–
–
•
–
–
If the secure shell (SSH) transport mechanism is used, the following prompts are applicable. There is no support for FastSwitch devices in the SSH transport mechanism.
•
–
–
•
–
–
Default prompts use this formatting. If you have changed your defaults, verify that the prompts meet these requirements, and change them if they do not.
Configuration Job Setup
Configuration Job Setup window allows you to set up these:
•
•
Transport Protocol Order for NetConfig, NetShow and Config Editor jobs
You can set the protocol order for NetConfig, Config Editor and NetShow jobs to download configurations and for NetConfig and Config Editor to fetch configurations. This setup provides the flexibility of using your preferred protocol order for fetching and downloading the configuration.
Step 1
The Configuration Job Setup dialog box appears.
Step 2
Step 3
Step 4
A confirmation message appears.
Step 5
For more information, see the Configuration Job Setup online help.
Password Policy for NetConfig, NetShow and Config Editor Jobs
You have the option of entering your user name and password for job execution. If you enter your username and password, Essentials ignores the username and password in the database and uses the newly entered username and password, instead. If you do not enter your username and password, Essentials uses the user name and password in its database.
This option of entering the username and password for job execution helps in high security installations where device passwords are changed at frequent intervals. For example, the passwords may be changed every 60-90 seconds.
Step 1
The Configuration Job Setup dialog box appears.
Step 2
Step 3
Step 4
A confirmation message appears.
Step 5
For more information, see the Configuration Job Setup online help.
Logging Out
To end your administrator tasks, you must log out of CiscoWorks.
Step 1
Step 2
The Login Manager dialog box replaces the navigation tree.
