The Admin Drawer

This form is used to schedule a task and find the level of availability of each Cisco device on the network. The result can be viewed by using the Availability Reporter.

Before scheduling your first availability task you should use the Device Identification Manager tool to configure NATkit with a list of all your network devices. When a scheduled availability task is run for the first time the device information contained in the seed file tells NATkit which devices are on your network. The seed file contains the name or IP address of each network device, as well as login strings, passwords, and additional security information. This basic device data is used to communicate with each device.

Each time a scheduled availability task is run, NATkit communicates with each device on the network that it knows about. For NATkit to include additional devices in a scheduled availability run, you must add that device using the Device Identification Manager tool.

Availability Data

Availability for NATkit 2.0 is device availability, not network availability. Availability measures whether a device can be reached via ICMP echoes (pings) from the NATkit box.

A device is deemed as unavailable in the Daily Report if NATkit failed to receive a response in the last 8 or 24 hours. All pings to the device must have failed in the specified time period for the device to be marked as unavailable.

When you run an availability task, all the devices that NATkit knows about are pinged according to the schedule you specify. The data collected can be viewed in the following ways:

Devices not heard from
Devices that have missed pings
Availability trending

Scheduling Availability

To schedule an availability task, complete the following:

Step 1 Enter a name for the availability task.

Step 2 Set the Start Task timer by clicking pull-down lists and selecting a value.

Step 3 Set the End Task timer the same as the Start Task timer.

Note You can force the process to run "foreve" by setting the End timer to a date/time the same or earlier than the Start timer.

Step 4 Set the Run Task timer in the same way as the Start Task and End Task timers.

Step 5 To view availability, use the Availability Reporter.

Step 6 To review the settings for a scheduled availability run, use the Scheduler.

Advanced Timer

Step 1 Click Advanced Timer to bring up the Advanced Timer dialog box.

Step 2 Enter a name for the availability task.

Step 3 Set the Start Task timer by clicking pull-down lists and selecting a value.

Step 4 Set the End Task timer the same as the Start Task timer.

Note You can force the process to run "foreve"' by setting the End timer to a date/time the same or earlier than the Start timer.

Step 5 Set the Run Task timer in the same way as the Start Task and End Task timers.

Step 6 To view availability, use the Availability Reporter.

Step 7 To review the settings for a scheduled availability run, use the Scheduler.

NATkit Device Configuration

Use NATkit Device Configuration to schedule collection tasks and determine how the device configurations will be collected.

Configuration Collection Methods

NATkit 2.0 supports a new method of collecting device configurations, SNMP, in addition to the old method using Telnet. By default, the primary method is set to Telnet, and the secondary method to SNMP. Whenever SNMP is used, NATkit will send an SNMP set command to the device whose configuration is being collected. In order to successfully execute the set command, be sure that the RW community string is properly set and the TFTP service on your workstation is turned on.

To collect device configurations, complete the following:

Step 1 Select the primary method in which to collect NATkit devices (SNMP, Telnet, None).

Step 2 Select the secondary method in which to collect NATkit devices (SNMP, Telnet, None).

Step 3 Click Submit.

Note If you select SNMP as one of the collection methods, be sure that the TFTP service on your NATkit machine is turned on. Check the file /etc/inetd.configuration to verify this. NATkit also requires the TFTP service to use /tftpboot to do the file transfer.

Configuration Collection Scheduler

The Configuration Collection Scheduler form is used to schedule the periodic configuration collection task.

Before scheduling your first configuration task, you should define some devices first. Select Current Devices under Device Identification Manager in the NATkit Utilities drawer to view a list of devices that are defined. The following are just two of the many ways to add devices:

Select Add Devices under Inventory in the Admin drawer.
Define devices in a file and select Import from File under Inventory in the Admin drawer to insert them into NATkit.

Each time a scheduled configuration task is run, NATkit communicates with each device on the network that it knows about. For NATkit to include additional devices in a scheduled configuration run, make sure that the new devices have been properly defined.

The Start Task timer is adjusted to start the process instantaneously, if so desired. The End Task timer is adjusted for the process to run forever periodically, if so desired.

Collecting Device Configurations

The device data collected during a scheduled configuration is the current device configuration.

There are two ways to collect device configurations:

You can use the Configuration Scheduler to collect configurations periodically on all the devices on your network.
You can create a Syslog filter task to watch for configuration changes. (For more information, refer to the Syslog Filter Editor online help in NATkit.)

The recommended way to collect configuration changes on devices is to use both methods:

Create a configuration collection task to collect configuration changes initially, using the Configuration Scheduler. See the procedure "Scheduling a Configuration Task" described in the next section.

Note When collecting configuration data periodically (using the Configuration Scheduler), NATkit uses Telnet to port 23.

Configure all your network devices to log syslog messages to a syslog server and create a Syslog Filter task to collect device configuration data on an ongoing basis.

The recommended method described above allows NATkit to collect up-to-the-minute configuration change data with minimal impact to your network.

Scheduling a Configuration Task

To schedule a configuration task, complete the following:

Step 1 Enter a name for the configuration task.

Step 2 Set the Start Task timer by clicking on pull-down lists and selecting a value.

Step 3 Set the End Task timer the same as the Start Task timer.

Step 4 Set the Run Task timer in the same way as the Start Task and End Task timers.

Note We recommend NOT scheduling a configuration task more than twice a day. Depending on the size of your network, an inventory task may take up to 12 hours to complete. We advise against starting a configuration task while one is already running. Check the Scheduler to see when and how often you have a configuration task scheduled.

Step 5 To view your device configuration, select View Config.

Note Remember that NATkit is not updated until the scheduled configuration task is run.

Step 6 To review the settings for the scheduled configuration, select Scheduler.

Advanced Timer

Step 1 Click Advanced Timer to bring up the Advanced Timer dialog box.

Step 2 Enter a name for the configuration task.

Step 3 Set the Start Task timer by clicking on pull-down lists and selecting a value.

Step 4 Set the End Task timer the same as the Start Task timer.

Note You can force the process to run "forever" by setting the End Task timer to a date/time earlier than or the same as the Start Task timer.

Step 5 Set the Run Task timer in the same way as the Start Task and End Task timers.

Step 6 To view your device configuration, select View Config.

Note Remember that NATkit is not updated until the scheduled configuration task is run. To review the settings for the scheduled configuration, use the Configuration Scheduler.

Step 7 To review the settings for the scheduled configuration, select Scheduler.

Note Before scheduling your first configuration task you should use the Device Identification Manager tool to configure NATkit with a list of all your network devices.

NATkit Netsys Integration

Netsys provides a simulation of your network topology and facilitates offline network troubleshooting. Netsys is not offered along with NATkit. NSA clients must obtain it separately.

NATkit and Netsys

Netsys includes a configuration checker utility that performs the following function: Given a set of Cisco device configuration files it parses the configuration data to find catastrophic and informational messages. If you have Netsys installed in your system, NATkit integrates this functionality. NATkit collects the latest configurations from Cisco devices, runs the configuration files through the Netsys configuration checker utility, and collects the error report.

Note NATkit and Netsys need not run on the same machine to achieve integration. In fact, we recommend that they do not run on the same machine depending on the machine type and the network size, because Netsys and NATkit can both take a lot of CPU cycles to finish their respective tasks. If NATkit and Netsys are not on the same system, then NATkit only needs to know the directory in which Netsys binaries are installed. This could be achieved by NFS mounts on most UNIX systems.

FOR NFS MOUNTS PLEASE CONTACT YOUR UNIX ADMINISTRATOR.

Integration Parameters

To select the parameters for purging a Netsys Report, complete the following:

Step 1 Enter the directory where Netsys is installed:

Step 2 Select the period of time Netsys Reports are to be purged:

Step 3 Click Submit.

NATkit SNMP

Use NATkit SNMP to create and schedule polling profiles. A polling profile issues SNMP commands to collect data for the devices and variables you specify. The simplest SNMP Poller profile polls the specified devices and collects the variable values.

Searching for Devices

The following is the entry screen to create an SNMP Poller profile. You use this screen to filter all the devices on your network. After you enter the appropriate search string (see the following), you are presented with a list that represents some or all of the devices on your network.

Step 1 Enter a search string for the desired devices:

The search string can include multiple patterns separated by spaces, for example:
171* nsa*.
The search field recognizes exclusive ORs. This example searches for all devices: 171* OR nsa*.

Step 2 Click Submit to run the filter. The second SNMP Poller screen, Device/Variable Selection, appears and displays a list of devices matching your search string.

Note The search routine uses an exclusive OR. If you enter more than one search string, separated by a space, NATkit displays a list of found devices matching the last recognized string.

SNMP Poller Scheduler

The SNMP Poller Profile Scheduling screen allows you to set two options:

Specify the time the profile is run by setting the start, end, and periodic times.
Choose to have the profile use one of the following thresholds:
- Default variable thresholds
- Remove all variable thresholds
- Change the variable thresholds

Device Variable Thresholds

Threshold settings are used by SNMP Poller to create exceptions statistics when data collected by the profile is viewed. The threshold is a data trigger point for a device variable. Thresholds are also used to trigger the Event Dispatcher to run any custom correlation settings you have specified in your profile.

When you choose default thresholds, SNMP Poller creates exception statistics based on the default threshold values of a variable. When you choose to remove thresholds, no exceptions statistics are collected. Choosing change thresholds and clicking NEXT PAGE displays the Change Thresholds/Set Correlation Options screen. You can select and change the variable's threshold value of any variable before submitting the profile for execution.

Setting the Start, End, and Periodic Polling Times

Use the standard NATkit timer to set start, end, and run task times. By setting the end time equal to the start time, or setting the end time to an earlier date than the start time (for which you will need to use the Advanced Timer), you ensure that the profile runs "forever."

Threshold Settings

The three types of Threshold settings are as follows:

Default Thresholds to collect exceptions statistics on device variables.
Change Thresholds and click Next Page to change threshold values and optionally add custom correlation settings.
Remove Thresholds so that no exceptions statistics are collected.

NATkit Syslog

The NATkit Syslog screen begins the creation or editing process of a Syslog filter task. The following screens comprise Syslog Filter task creation:

Initial Syslog Editor Filter screen --- used to specify whether you are creating or editing a filter task.
Create Filter Task screen is used to:
- Name the task
- Specify a Syslog daemon log file and spooling frequency
- Choose a correlation type
Filter Task Editing screen --- used to add or delete filter correlation settings to your Syslog Filter task.
Task Confirmation screen --- used to confirm Syslog filter tasks with default correlation or no correlation attributes before the task is submitted to the Scheduler.
Custom Correlation screen --- used to specify Syslog message filters and any corresponding actions to invoke when the message is encountered.

Creating a Task

The Create Filter Task screen is used to:

Name the filter task
Specify a syslog log file and spooling frequency
Choose a correlation type

Creating a Syslog Filter Task with Default or No Correlation

Step 1 Select Create New Syslog Filter Task from the main Syslog Filter Editor screen.

Step 2 Click Next to continue on to the Syslog spool correlation creation process.

Step 3 Enter a name for the new Syslog Filter task in the Enter Name of Task to Schedule field.

The name may contain a combination of numerals and characters, but must begin with a letter and may not contain any special characters or spaces. For example, Syslog_br75 is an acceptable task name.

Note Unless you have specified more than one log file in your syslog.conf file, you should not need to create more than one Syslog Filter task. See the Syslog Filter Editor help topic for more information.

Step 4 Enter the full path name of the NATkit syslog file in the Enter Name of File to Spool field. This is the file specified in the syslog.conf file.

Step 5 Select Use Default Correlation or No Correlation.

Step 6 Click Next.

Step 7 Click Submit on the confirmation screen to send the Syslog filter task to the Configuration Scheduler.

Creating a Syslog Filter Task with Custom Correlation

To create a syslog filter task using custom correlation, complete the following:

Step 1 Follow steps 1 through 4 in the procedure "Creating a Syslog Filter Task with Default or No Correlation" section.

Step 2 Select Create Custom Correlation.

Step 3 Click Next Page to display the Custom Correlation screen.

Step 4 Click Submit to send the Syslog filter task to the Configuration Scheduler.

Combining Default and Custom Correlation in a Syslog Filter Task

To create your Syslog Filter task to include the filters in the default correlation and add any additional filters, complete the following:

Step 1 Follow steps 1 through 4 in the procedure "Creating a Syslog Filter Task with Default or No Correlation" section.

Step 2 Select Use Default Correlation.

Step 3 Click Next Page.

Step 4 Click Submit on the confirmation screen to send the Syslog filter task to the Configuration Scheduler.

Step 5 Edit the task to add Syslog message filters.

Before you create a Syslog filter task be sure you have edited your syslog.conf file to include the required event type(s) and log file(s). Refer to your UNIX or Sun documentation for more information regarding this file.

Note Unless your syslog.conf file stipulates multiple log files, there is no need for more than one Syslog Filter task to be created.

If your Syslog daemon is running from a remote server (not the NATkit workstation), be sure you have performed an NFS mount.

Editing a Task

This screen is used to edit a Syslog profile. You can add or delete Syslog events to your Syslog profile and change correlation settings on this screen.

Choosing a Syslog Profile

: To select a syslog profile to edit, complete the following:

Step 1 Click the drop-down list to see a list of Syslog profiles, and select one for editing.

Step 2 Click Next Page to begin editing the profile.

Deleting a Syslog Event

: Click Delete to the right of the Syslog event you want to remove from your Syslog profile.

Adding a Syslog Event

: Click Add to go to the Custom Correlation screen to add Syslog events.

Note If you inadvertently delete a Syslog event from your Syslog profile, you can add it again by using the Add button.

Confirming a Task

The Confirming a Task screen is used to confirm your Syslog profile before you submit it to the NATkit Scheduler. You check the specifications of your Syslog profile on this screen.

Syslog Correlation

Refer to the online help in NATkit 2.0 for complete instructions.

NATkit WAN Switches

The following sections provide information that will allow you to view or delete WAN switches, configure the Trapd spooler, and schedule CLI collections:

Delete WAN Switches
Trapd Log Scheduler
CLI Scheduler

Deleting WAN Switches

You can delete any installed WAN switch either individually or as a group.

To delete an individual WAN switch, complete the following:

Step 1 Select Delete Individual Device.

Step 2 Enter the name of the device to delete in the Device Name field.

Step 3 Click Submit to permanently delete the device.

To delete a WAN switch from a file, complete the following:

Step 1 Select Delete Devices from File.

Step 2 Enter the name of the file to delete in the Input File Name field.

Step 3 Click Submit to permanently delete the devices from the file.

Note Once a device or file is deleted, it is gone and must be reinstalled to be used again.

Trapd Log Scheduler

The Trapd spooler gathers and interprets messages logged in the trapd.log file of HP OpenView for WAN switching nodes based on input from the user.

Step 1 Enter a task name.

Step 2 Enter a filename of the log to spool.

Step 3 Click Submit to display the scheduler results.

Note The StrataCom log task is limited to read-only WAN switches in the trapd.log file of HP OpenView.

The trapd.log file should be physically accessible to the machine running NATkit 2.0.

CLI Scheduler

The CLI Scheduler is used to schedule the CLI Collection module in NATkit 2.0. You can specify the start and end times, or periodic time intervals at which this collection program will run.

Step 1 Enter the name of the task to be scheduled in the Enter Name of Task field:

Step 2 Click the desired node, command profile and commands:

Step 3 Select the desired Start Task, End Task, and Run Task options.

Step 4 Or you can click Advanced Timer to bring up the the Advanced Timer for more specific Start Task, End Task, and Run Task options:

Step 5 Click Submit to schedule task.

Note The StrataCom CLI interface is designed to work with StrataCom nodes only.

Table of Contents

The Admin Drawer