Preparing to Use Essentials Applications

Table Of Contents

Preparing To Use Essentials Applications

Quick Reference

Setting Up Inventory

Adding or Importing Inventory Data

Adding Device Information for a Single Device

Importing Devices from a File

Importing Devices from a Local NMS

Importing Devices from a Remote NMS

Creating a Device View

Obtaining CCO Login Privileges

Changing Device Attributes (Including Serial Numbers)

Performing Optional Inventory Setup Tasks

Setting Up Availability

Setting Up Syslog Analysis

Configuring Routers and Switches for Syslog Analysis

Configuring Cisco IOS Devices for Syslog

Configuring Catalyst 5000 Series Devices for Syslog

Verifying the Settings in the Syslog Configuration File

Verifying the Syslog Analyzer

Setting Up the Configuration Archive

Entering Passwords

Modifying Device Configurations

Setting Up Software Management

Adding Device Passwords to the Inventory

Setting Software Management Preferences

Obtaining CCO Login Privileges

Setting Up TFTP

Enabling the TFTP Daemon

Creating the tftpboot Directory

Setting Up RCP

Creating the RCP Remote User Account

Enabling the RCP Daemon

Selecting RCP as the Active File Transfer Method

Allowing the User bin To Use at and cron

Performing Optional Software Management Setup Tasks

Preparing To Use Essentials Applications

---

Now that you have installed and set up Essentials, you must configure the Essentials applications for use. This chapter assumes the following:

•That you have installed Essentials and performed the setup tasks described in the "" chapter.

•That you are logged on to the Essentials server with administrator privileges. If you are not, you might not be able to perform all the tasks.

This chapter consists of the following sections:

•Quick Reference

•Setting Up Inventory

•Setting Up Availability

•Setting Up Syslog Analysis

•Setting Up the Configuration Archive

•Setting Up Software Management

Quick Reference

provides an overview of preparing to use Essentials applications and references to more detailed information about each task. The information in the rest of this chapter follows the same order as the quick reference.

Table 5-1 Preparing To Use Essentials Applications Quick Reference 

Task	Steps	References
1 Set up Inventory	Step 1 Create the network inventory by doing either of the following: –Add device information by adding one device at a time. –Import device information from a file or an NMS database.	"Adding or Importing Inventory Data" section
	Step 2 Create a device view.	"Creating a Device View" section
	Step 3 Obtain login privileges to Cisco Connection Online (CCO).	•"Obtaining CCO Login Privileges" section •CCO home page at www.cisco.com
	Step 4 (Optional) Enter device serial numbers for devices that have Contract Connection service contracts by changing the device attributes.	"Changing Device Attributes (Including Serial Numbers)" section
	Step 5 (Optional) Perform the following optional Inventory setup tasks: –Schedule Inventory Polling and Collection. –Set Change Report Filters. –Display a detailed device report.	"Performing Optional Inventory Setup Tasks" section
2 Set up Availability	Step 1 Create an availability view with at least two devices.	•"Setting Up Availability" section •"Creating a Device View" section
	Step 2 Verify that Availability functions correctly.	•"Setting Up Availability" section
3 Set up Syslog Analysis	Step 1 Configure your routers for Syslog Analysis.	"Configuring Routers and Switches for Syslog Analysis" section
	Step 2 Verify the settings in the Syslog configuration file.	"Verifying the Settings in the Syslog Configuration File" section
	Step 3 Verify that syslog messages are being processed by the Syslog Analyzer.	"Verifying the Syslog Analyzer" section
4 Set up Software Management	Step 1 Add the device passwords to the inventory.	"Adding Device Passwords to the Inventory" section
	Step 2 Set your Software Management preferences.	"Setting Software Management Preferences"section
	Step 3 Obtain login privileges to CCO for importing software images.	•"Obtaining CCO Login Privileges" section •CCO home page at www.cisco.com
	Step 4 Set up TFTP.	"Setting Up TFTP" section
	Step 5 Set up RCP.	"Setting Up RCP" section
	Step 6 Allow the user bin to use at and cron.	"Allowing the User bin To Use at and cron" section
	Step 7 (Optional) Perform the following optional Software Management setup tasks. –Create a baseline software image. –Schedule the Browse Defects job to run periodically. –Schedule the Synchronize Library job to run periodically. –Create one or more approver lists if you want to use the Maker-Checker option. –Add a device software image to the software library. –Distribute a software image to a device or group of devices.	"Performing Optional Software Management Setup Tasks" section

Setting Up Inventory

This section describes the tasks that you must perform to set up the Inventory application.

Adding or Importing Inventory Data

You must have at least two managed devices (devices whose inventory information is tracked by Essentials) to verify the correct installation of Essentials. To manage your network, you need to add the device information for all your managed devices.

You can populate your network inventory in the following ways:

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

•Import a group of devices from one of the following sources:

•A comma-separated value (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)

To import devices from an NMS database, you 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 Essentials online help.

The following sections describe how to add device information using these methods. For additional information, refer to Getting Started with Resource Manager Essentials and the online help.

Adding Device Information for a Single Device

To add device information, follow these steps:

---

Step 1 Select Admin > Inventory > Add Devices. The Add a Single Device dialog box appears.

Step 2 Enter the access information and annotations for one device. You must fill in the Device Name field. All other fields are optional. For more information about these fields, refer to the Essentials 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 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.

Step 8 Use the Add/Import Status Summary dialog box to check the 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 one device when the Add/Import Status Summary dialog box appears.

Step 9 Click Update on the Add/Import Status Summary dialog box to update device status.

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 the current status of the device.

For additional information, refer to Getting Started with Resource Manager Essentials and the online help.

Importing Devices from a File

You can import devices by extracting data from your existing data source into a comma-separated value (CSV) file or device integration file (DIF), then using this file as input into the Essentials database. First create a CSV or DIF file, then click Admin > Inventory > Import from File to access the CSV or DIF file and import the device information. For additional information, refer to Getting Started with Resource Manager Essentials or online help.

Importing Devices from a Local NMS

To import devices from CiscoWorks or CiscoWorks for Switched Internetworks (CWSI), the database 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 Essentials server. To import devices from HP OpenView, HP OpenView must be running on the local host.

Select Admin > Inventory > Import from Local NMS to import devices from the databases listed in the Local Database Import dialog box. For additional information, refer to Getting Started with Resource Manager Essentials or online help.

Importing Devices from a Remote NMS

Before you can import devices from a remote NMS, you must perform several system and NMS configuration steps, depending on the NMS you are using. For additional information, refer to Getting Started with Resource Manager Essentials or online help.

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

Creating a Device View

To set up and verify the Essentials applications, you must create a static device view (a grouping of devices) that includes at least two devices. For additional information, refer to Getting Started with Resource Manager Essentials or online help.

To create the static view, follow these steps:

---

Step 1 Select Admin > Device Views > Add Static Views. The Add Static Views dialog box appears.

Step 2 Select the view that has the devices you want to add from the Views list. If you have not configured any views previously, select All.

Step 3 Select the devices that you want to add from the Devices list.

Step 4 Click Next. The Save Static View dialog box appears.

Step 5 Enter the view name and view description.

Step 6 Click Finish.

Obtaining CCO Login Privileges

You must have login privileges to CCO to use several features of Essentials, including Contract Connection. If you do not have login privileges, refer to the CCO home page, www.cisco.com, to obtain a login.

Changing Device Attributes (Including Serial Numbers)

To ensure that your devices have the correct device access, password information, and user information, you can change the device attributes.

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

To edit device attributes, including serial numbers, follow these steps:

---

Step 1 Select Admin > Inventory > Change Device Attributes. The Change Device Attributes dialog box appears.

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

Step 3 To change the serial numbers, select Device Serial Numbers, then click Next. The Edit Device Serial Numbers dialog box appears.

Step 4 Enter the device name and serial number, then click Next.

Performing Optional Inventory Setup Tasks

Now that you have set up Inventory, you can perform some optional tasks to prepare your Essentials environment to perform inventory management tasks. Refer to the online help for information about the following tasks:

•Scheduling Inventory Polling and Collection

•Setting Change Report Filters

•Displaying a Detailed Device Report

Setting Up Availability

To verify that Availability is working correctly, you must have a test device view with at least two devices. You can use the device view that you created during Inventory setup, assuming that you added at least two devices to it. Use this test device view to verify that Availability displays the devices in the view in the Reachability Dashboard.

To verify Availability using the test device view that you created, follow these steps:

---

Step 1 Select Admin > Availability > Change Polling Options.

Step 2 Select the test device view that you created in 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 by Availability.

---

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 ensure that Availability polls the devices in your test device view.

Step 6 Select Tasks > Availability > Reachability Dashboard. The Reachability Dashboard appears.

The devices in your test device view should appear in the Reachability Dashboard.

Now that you have configured one Availability view and specified polling parameters, you can monitor devices and run various reports. For details about using Availability, refer to Getting Started with Resource Manager Essentials and 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 router and network performance. You can customize Syslog Analysis to produce the information and message reports that are important to your operation. The following sections describe how to set up Syslog Analysis.

Configuring Routers and Switches for Syslog Analysis

Before you can use Syslog Analysis, you must configure the routers (Cisco IOS devices) and switches (Catalyst 5000 series devices) to forward messages to Essentials or a system on which you have installed the distributed Syslog Analyzer collector. For more information about setting up routers for message logging, refer to the online help, the Cisco IOS Software Documentation on CCO (for Cisco IOS devices), and the appropriate Catalyst 5000 series reference guides (for Catalyst 5000 series devices).

Configuring Cisco IOS Devices for Syslog

To configure Cisco IOS devices for Syslog, follow these steps:

---

Step 1 Telnet to the device and log in. The prompt changes to host>.

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.

Step 5 To specify the Essentials server that is to receive the router syslog messages, enter logging 123.45.67.89 (where 123.45.67.89 is the IP address of the server).

Step 6 To limit the types of messages that can be logged to the Essentials server, set the appropriate logging trap level by entering logging trap informational.

Informational signifies severity level 6, which means all messages from levels 0-5 (from emergencies to notifications) will be logged to the Essentials server.

Step 7 Verify that Syslog is running.

(a) From the Essentials interface, select System Admin > Process Status. The Process Status dialog box appears.

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

Step 8 Verify that the Syslog configuration file settings are correct. Refer to the "Verifying the Settings in the Syslog Configuration File" section for instructions.

Configuring Catalyst 5000 Series Devices for Syslog

To configure Catalyst 5000 series devices for Syslog, follow these steps

---

Step 1 Telnet to the device and log in. The prompt changes to host>.

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

Step 3 Enter set logging server enable to make sure logging is enabled.

Step 4 Enter set logging server 123.45.678.90 (where 123.45.678.90 is the IP address of the server) to specify the Essentials server that is to receive the router syslog messages.

Step 5 To limit the types of messages that can be logged to the Essentials server, set the appropriate logging trap level by entering set logging level informational.

Informational signifies severity level 6, which means all messages from levels 0-5 (from emergencies to notifications) will be logged to the Essentials server.

Step 6 Verify that Syslog is running.

(a) From the Essentials interface, select System Admin > Process Status. The Process Status dialog box appears.

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

Step 7 Verify that the Syslog configuration file settings are correct. Refer to the "Verifying the Settings in the Syslog Configuration File" section for instructions.

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 Essentials server, follow these steps:

---

Step 1 Make sure that the facility.level definition is set to local7.info, and that the following line is present (note that there must be a tab between local7.info and the path/filename):

local7.info     path/filename

Where path/filename is the full pathname of a file.

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

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

kill -HUP `cat /etc/syslog.pid`

Verifying the Syslog Analyzer

To verify that syslog messages from the network are being processed by Syslog Analyzer, follow these steps:

---

Step 1 Log in to a managed router that is configured to send Syslog messages to the Essentials server with appropriate login privileges to make configuration changes.

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

# enable

# configure terminal

The prompt changes to #>.

#> banner motd /

This is a test /

#> end

Step 3 Wait approximately two minutes for the Syslog message generated by the router configuration change to be processed by the server.

Step 4 From Essentials, select Tasks > 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 the following:

•All Messages in the Report Type list.

•Today from the Dates list.

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

Verify that the report contains the Syslog message generated by the configuration change that you made.

Setting Up the Configuration Archive

Before the configuration archive can gather device configurations, you need to update the Essentials database with passwords and modify device configurations.

Entering Passwords

Before the configuration archive can gather device configurations, you need to specify the Read and Write community strings, Telnet and Enable passwords, and TACACS, Local, and RCP information for the devices. If you already added or imported devices and did not specify this information, you can change the device attributes. Refer to the Inventory online help or Getting Started with Essentials for more information.

Enter the following information for all devices:

•Read and Write community strings, and Telnet and Enable passwords for the devices. See the Inventory online help for more information about these fields.

•TACACS, Local, and RCP information for the devices. See the Inventory online help for more information about these fields.

Modifying Device Configurations

You need to modify your device configurations to enable the configuration archive to gather the configurations by performing the following steps:

---

Step 1 Make sure the devices are RCP-enabled by entering the following commands in the device configurations:

# ip rcmd rcp-enable

# ip rcmd remote-host remote_username 123.45.678.90 local_username 
enable

where 123.45.678.90 is the IP address of the machine where Essentials is installed. (Alternatively, you can enter the host name instead of the IP address.) The default remote_username and local_username are cwuser.

Step 2 Configure your devices for Syslog Analysis. See the "Setting Up Syslog Analysis" section for more information.

After you have performed these steps on your devices and they become managed, the configuration files are collected and stored in the configuration archive.

Setting Up Software Management

Software Management performs system software, boot loader upgrades, and software configuration operations on groups of routers and switches. See the Resource Manager Essentials Release Notes for AIX for the devices supported by Software Management. For more information about setting up Software Management, refer to the online help.

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.

This section describes the tasks that you must perform to set up Software Management.

Adding Device Passwords to the Inventory

Before you can manage device software images using Software Management, you must add the required device passwords to the device inventory. For additional information about device passwords, refer to the online help.

To add device passwords to the device inventory, follow these steps:

---

Step 1 Select Admin > Inventory > Change Device Attributes. The Change Device Attributes dialog box appears.

Step 2 Select the device whose device information you want to edit, then click Next. The Change dialog box appears.

Step 3 Select the options for the passwords that you want to enter, then click Next. A dialog box appears for each option you select.

Read and write community strings are required and Telnet password is recommended for Software Management.

Step 4 In each dialog box, enter the password required for the device, then click Next.

Setting Software Management Preferences

Software Management has many preferences that you can set to control how the application behaves. To set these preferences, follow these steps:

---

Step 1 Select Admin > Software Management > Edit Preferences. The Edit Preferences dialog box appears.

Step 2 Change the preferences settings as appropriate.

For more information about Software Management preferences settings, refer to the online help.

Step 3 After you finish, do one of the following:

•Click Finish to save your changes.

•Click Default to display the default configuration.

Obtaining CCO Login Privileges

You must have login privileges to CCO to use several features of Essentials, including Software Management. If you do not have login privileges, refer to the CCO home page, www.cisco.com, to obtain a login.

Setting Up TFTP

You must have a file transfer server 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 AIX software, you can add and configure the TFTP server (TFTPD) by following these steps:

---

Step 1 Log in as a superuser.

Step 2 Edit the /etc/inetd.conf file using a text editor such as vi or textedit.

•Look in the file /etc/inetd.conf for the line that invokes TFTPD. If the line begins with a pound sign [#], 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/tftpd  tftpd  -d /tftpboot

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

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:

root  119   227  0  12:56:14 -           0:00 /usr/bin/inetd

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:

udp 0 0 *.tftp *.*

or enter:

# /usr/CSCOpx/bin/mping -s tftp localhost_machine_name

which 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 9 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, follow these steps to create it:

---

Step 1 Enter the following command:

# 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.

Setting Up RCP

You can also enable a Remote Copy (RCP) server and select it as the active file transfer server. If you select RCP as the active server and then attempt to transfer files to a device that does not support RCP, Essentials will use TFTP to transfer the files. The following sections describe how to enable RCP and select it as the active file transfer method.

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 bin 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 Add a user account named cwuser to the system by entering the following command:

# mkuser  becos="user account to authenticate remote copy operations" \ 
cwuser

Step 2 Navigate to the cwuser home directory.

Step 3 Create the .rhosts file by entering the following command:

# touch .rhosts

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

# chown cwuser:bin .rhosts

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

# chmod 0664 .rhosts

Step 6 If you did not use the default user name cwuser, configure the Essentials server to use the user account that you created as the RCP remote user account.

(a) Log on to the Essentials server as admin.

(b) Select Admin > System Admin > System Configuration.

The System Configuration dialog box appears.

(c) Select the RCP tab.

(d) Enter the name of the user account that you just created in the User Name field, then click Finish.

Enabling the RCP Daemon

To add and configure the standard AIX RCP server software, follow these steps:

---

Step 1 Log in as a superuser.

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 your 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/rshd   rshd

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

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:

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

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 rshd is enabled by entering the following command:

# netstat -a | grep shell

which should return output similar to the following:

tcp   0   0  *.shell    *.*     LISTEN

Selecting RCP as the Active File Transfer Method

By default, Essentials uses RCP with devices that support RCP. 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 RCP with any devices. To do this, follow these steps:

---

Step 1 Select Admin > Software Management > Edit Preferences.

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

Allowing the User bin 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 bin, so the user bin must be allowed to use at and cron.

To allow the user bin to use at, follow these steps:

---

Step 1 If an at.allow file exists in the directory /var/adm/cron, make sure that bin is listed in it. Add bin to the at.allow file using a text editor if necessary.

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

Step 3 If neither an at.allow nor an at.deny file exists 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, follow these steps:

---

Step 1 If a cron.deny file exists in the directory /usr/lib/cron, make sure that bin is not listed in it. Remove bin from the cron.deny file using a text editor if necessary.

Step 2 If a cron.allow file exists in the directory /usr/lib/cron, make sure that bin is listed in it. Add bin to the cron.allow file using a text editor if necessary.

Step 3 If neither a cron.allow nor a cron.deny file exists in the directory /usr/lib/cron, create a cron.allow file and add bin to it using a text editor.

Performing Optional Software Management Setup Tasks

Now that you have set up Software Management, you can perform some optional tasks that will prepare your Essentials environment to perform software management tasks. Refer to the online help for information about the following optional tasks:

•Creating a baseline software image

•Scheduling the Browse Defects job

•Scheduling the Synchronize Library job

•Creating Maker-Checker approver Lists

•Adding a device image to the software library

•Distributing a software image