cc/td/doc/product/rtrmgmt/netsys/nt
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Keeping Baselines Up-to-date

Keeping Baselines Up-to-date

Overview

As your network configurations change, you will need to update your baseline files periodically so that topology views and reports present an accurate picture of your system as it currently exists.

You can update your baseline whenever you want from the Cisco Netsys Baseliner Tools menu, or you can use the command-line utilities:

Although collection and report generation can be scheduled individually, you may find it more convenient to execute them in sequence from a batch file. This ensures that report generation takes place only after collection has finished.

For information about running these utilities from a batch file, see the section "Automated Batch File Processing" elsewhere in this chapter.

The command line utilities also make it easy to automate the process of publishing to a web server.

For information about viewing Cisco Netsys Baseliner data in a web browser, see the chapter "Web Reports and Topologies."

Data Collection

Router configurations can be obtained directly from your network by running the Cisco Netsys Baseliner software's getconfig utility, which uses the TCP/IP Telnet protocol to issue a write term command to each router you have specified. Output from each Telnet session can be used to update your baseline directly, or the data can be captured to a file (which will have the same name as the router's hostname unless you have specified a different name for the file).

There are two ways to invoke this utility: you can select the Collect Cisco Configurations command on the Tools menu in the Cisco Netsys Baseliner main window, or you can use the DOS command-line batch file that was included in the Netsys directory when you installed the software.

If you have just installed the software and have not yet created a baseline, you will have to use the batch file in order to use this utility. The wizard will not be enabled if a baseline is not open.

Collecting Configuration Files from the Command Line

To create configuration files from the command line, you must first create an ASCII text file that lists the routers for which data is to be collected. You may give this file any name and locate it anywhere you want, as long as it is accessible from a DOS command line (and the filename does not contain anything other than letters, numbers, hyphens or space characters).

When you run getconfig.bat, the text file identifying your routers must be specified as the first argument. Data will be collected for each properly formatted entry contained in this file.

Configuration files will be written to the directory that is specified as the batch file's second command-line argument.

Automated collection can be done only with the command-line utilities, not with the wizard.

Specifying Routers for Collection

Router parameters are specified through a series of option switches and variables contained in an ASCII text file.

Here is a sample entry that collects data for a single router (lines preceded by #, as well as blank lines, are ignored when the file is read by the getconfig utility):

#router soleil with login password netsys and enable password netsys_ep

-h soleil -p netsys -e netsys_ep

This will cause the getconfig utility to issue a write term command to the router named soleil, using the Telnet communications protocol. (This requires that you have an open TCP/IP connection at the time you run the getconfig utility. Telnet capability is provided by Microsoft Windows NT.)

Configuration data for this router will be stored in a file named soleil, which will be written into whatever directory you specify as the second argument for getconfig.bat.

The -h switch is the only one that the getconfig utility requires for each entry. All other switches are considered by the Cisco Netsys Baseliner software to be optional. However, the entry must conform to the requirements of the specific router. That is, if the router requires a password, you must include the correct password switch, or the router will not respond to the Telnet message.

The -nomask switch causes the utility to copy login passwords, enable passwords, and SNMP community strings as entered. If this switch is not used, these variables will be masked by the string XXXXXX when the configuration file is written.

Option switches used in the input file are as follows:

-h <hostname>---name used to communicate with the router via Telnet (IP address notation is acceptable); may or may not be the same as the name set by the hostname command in the router's configuration file

-p <login password>---password required to log in to router

-u <login user name>---user name for logging in to router (for those routers that require both a user name and a password)

-U <enable user name>---user name required to enter privileged exec mode (for those routers that require both a user name and a password to get into privileged mode); if not specified, the log-in user name will be used

-e <enable password>---password required to enter privileged exec mode; if only one password (either -p or -e) is specified, it will be used as both the log-in and enable password

-a <ip address>---alternate identifier for Telnet connection, for use if the hostname specified by the -h switch fails (however, the hostname is still used as the filename for configuration output, and the -h switch must still be used)

-t <number of seconds>---length of time in seconds to wait for output to arrive via Telnet connection; this value will default to 10 seconds if none is specified

-c <configuration filename>---name of output file for configuration information (overrides the default behavior of using the hostname as the filename)

-s <suffix>---suffix to be appended to the output configuration file's name; for example, if you include the string -s -config in the identifier for a router named netsys, the config file will be named netsys-config

-nomask---allows the login and enable passwords and the SNMP community string to be viewed in the configuration file; if this switch is not specified, these variables will be shown as XXXXXX

-f <filename>---name of a file containing hostnames, passwords, and other parameters for routers whose configurations are to be retrieved; use of this switch causes the getconfig utility to extract router data from the specified file

An exception to the -h switch requirement occurs when the -f switch is used by itself. The -f switch could be the only entry in the file---but all entries in the file specified by the -f switch must contain the -h switch.

The getconfig utility will read router data from your input file until it encounters an -f switch. It will then extract information from the file specified. When that entire file has been read, the utility will return to the initial input file and continue. It is also possible to nest -f switches inside files specified by previous -f switches.

If you specify a filename and then you specify any optional parameters (such as users or passwords), the specified values will be used for those devices named in the secondary file without a value for the option.

If the following example is entered into your primary input file, the username jsmith and password password will be used for those devices that are specified without a username or password in the file secondaryfile.txt:

-f secondaryfile.txt -u jsmith -p password

If secondaryfile.txt includes the following:

-h soleil -u jdoe -p netsys

-h soleil_2

-h soleil_3

then the username for the router soleil will be set as jdoe and the login password will be set as netsys, but for soleil_2 and soleil_3 the username will be jsmith and the login password will be password.

Running the Getconfig Utility

When you have entered routers and option parameters into an ASCII text file as described above, open a DOS window and change the current directory to the Netsys directory (the location of your Cisco Netsys Baseliner installation).

To run the getconfig.bat file, enter getconfig and its required parameters at the DOS prompt and press the Enter key.

The batch file requires two arguments---your input file, and a path to the directory where you want the configuration files written, in that order. If the specified directory does not exist, it will be created for you.

You should not specify the baseline's existing config subdirectory as the target directory. If you are using the run_ngs utility in conjunction with getconfig, the run_ngs utility will transfer the newly collected files into the config subdirectory when it is done with them. (See the section "Updating the Baseline from the Command Line" elsewhere in this chapter.) But the run_ngs utility needs access to both new and old configuration files in order to properly update your baseline and generate reports.

Paths may be absolute, or relative to the directory in which the batch file is located. The utility will overwrite files in the output directory, allowing you to use the same batch file for routine collection. However, if you want to preserve previous copies of configuration files, you should copy or move them out of the target directory before running the utility.

To obtain a record of which collections succeeded and which failed (and why), pipe output from the batch file into a log file (use the greater than symbol---">"---followed by a filename, which will be created if the file doesn't already exist; if a file of that name does exist, it will be overwritten).

The following example illustrates how to run the getconfig utility from your Netsys installation directory:

getconfig input.txt c:\newconfigs > collection.log

If the file input.txt, which specifies routers and options, is located in the same directory as the getconfig utility, and you have a directory called newconfigs on your C:\ drive, configuration files will be written into the c:\newconfigs directory and a log of error messages will be written to the file collection.log in the directory Netsys.

Collection Failures

If you use the getconfig utility to collect configurations but don't review the messages generated by the collection process, your baseline could be displaying out-of-date information.

You should generate and check an output log each time you run getconfig.bat. This will alert you to failed collections and out-of-date information.

Consider the following example: You successfully collect configurations for Routers A, B, and C at the midnight on Monday and update your baseline. At 8 a.m. Tuesday, somebody changes the password for Router A without telling you. When you collect configurations at midnight on Tuesday, you will collect new configurations for Routers B and C, but the collection for Router A will fail, because you have not updated the input file used by getconfig.bat.

The collection log will tell you that Router A did not respond to the update request.

Updating the Baseline from the Command Line

The utility program run_ngs.exe ("ngs" means Non-GUI Services) in your Netsys directory can be used to create a new baseline, update an existing baseline with configuration files collected by the getconfig utility, and generate reports and topology views in HTML and Java formats for viewing in a web browser.

To use the utility to update a baseline, you first need to collect current data using the getconfig utility described previously, then enter the following on a DOS command line in the Netsys directory:

RUN_NGS -b <baseline directory> -u <new configurations directory>

The baseline directory you specify is the directory that contains the baseline file (a file with the extension .baseline).

The new configurations directory is the location of your newly collected configurations (the target directory used the getconfig.bat utility described elsewhere in this chapter). This should not be your baseline's config directory. The run_ngs utility will write copies of the new configuration files into the baseline's config subdirectory during the updating process, but it also moves existing files to another location first. Previous versions of configuration files are needed to generate change reports.

Paths can be specified as either absolute, or relative to the Netsys directory (where run_ngs is located). If you create a baseline called test and accept the Cisco Netsys Baseliner default location for it, the file test.baseline will be located in the directory C:\Netsys\data\test (assuming your installation is in C:\Netsys).

The -b option is the only option that is required to execute the run_ngs utility. Use the run_ngs -b option by itself only if you want to generate HTML reports and Java topology views of the baseline as it currently exists. If you want to update your baseline at the same time, use the getconfig utility to write configuration files, then use run_ngs with the -u option and specify the location of the newly written configuration files.

The correct syntax for updating the baseline test using configuration files written to the C:\newconfigs directory is:

RUN_NGS -b data\test -u c:\newconfigs

(Neither run_ngs nor the Cisco Netsys Baseliner software recognizes file or directory names that contain spaces or non-alpha/numeric characters other than hyphens, periods, or the underscore character.)

Optional run_ngs parameters allow you to:

Use the -o option to specify an output directory for HTML reports. This allows you to publish your reports to a secure location under control of your web server, so that you can safely make the reports available over the internet. For more information about viewing Java and HTML output, see the chapter "Web Reports and Topologies." When you use the -o option, the run_ngs utility will not update the baseline's index.html file---the file used to display the index of reports (and their time stamps) in the browser. You will have to keep track of these reports yourself.

You can automate the entire collection/updating process by running the command-line utilities getconfig and run_ngs from a batch file that is executed automatically by a third-party scheduler or batch-file processing program.

Optional Run_ngs Parameters

You can specify any of the following options with run_ngs.exe (where two forms of a command are given, use either form---fully spelled out, or abbreviated):

Sample Run_ngs Command

The following example shows how to specify parameters for run_ngs:

RUN_NGS -b data\test -u c:\newconfigs -0 c:\reports -command_log c:\files\run_ngs.log

When run from the C:\Netsys directory, this will update the baseline named TEST, which is stored in the default location, using the configuration files that were written to the C:\files\newconfigs directory by getconfig.bat. HTML-format reports will be written to the directory C:\reports. A log of the process will be written to the file run_ngs.log in the directory C:\files.

Report Manager Utility

The utility program reportmgr.exe will delete the files and folders of web reports (whether generated by the run_ngs utility or from the Tools menu in the Cisco Netsys Baseliner software). This capability allows you to regulate the amount of disk space devoted to out-of-date reports. See the chapter "Web Reports and Topologies" for a discussion of web reports and disk space requirements.

Before you run the reportmgr utility, you need to identify the folders you want to delete. When web reports are created by either the run_ngs utility or from the Tools menu, the HTML files are stored in a subdirectory structure in your baseline's reports folder. These folders and files are kept in a folder that is numbered when created. The first time you generate web reports, they will be placed in folder 0001 (inside the reports folder); the second set of reports will be stored in the 0002 folder; and so on.

However, once you have deleted one of these folders, you can no longer count on this pattern to identify the relative age of your reports. The software will reuse numbers that have been deleted. That is, if you create reports in folders 0001, 0002, and 0003, then delete the 0001 folder, the next set of reports will be stored in a newly created 0001 folder.

In order to determine the age of a given folder, you need to check the date of creation, using the Windows NT Explorer, a DOS command, or the reports index page accessible from your web browser. (Choose the Generated Web Reports command on the Cisco Netsys Baseliner View menu, or use your web browser to open the file index.html in the reports directory. Remember, however, that this file will not show reports generated using the -o option of the run_ngs utility .)

The reportmgr utility takes two arguments:

The following sample entered at the command line from the C:\Netsys directory will delete the reports contained in the 0003 folder from a baseline located in C:\Netsys\Data\mybaseline:

reportmgr -r 0003 C:\Netsys\Data\Mybaseline\Reports\index.sdf

Automated Batch File Processing

You can automate the process of collecting configurations and publishing updated reports and topology views (to a web server, for example), by using any of several commercially available batch processing programs, such as Wilson Window Ware's WinBatch (http://www.windowware.com) or Unisyn Software's AutoMate (http://www.unisyn.com).

Microsoft's Schedule service (and the At command) would seem like a good choice for automating the data collection process. However, Cisco engineers have been unable to make this service work with the run_ngs utility, apparently because of the way Windows NT shows or hides system data according to users' logon privileges.

Regardless of whether you want to run the Cisco Netsys Baseliner utilities singly or together, you should run them from a batch file so that you can set some environment variables that each uses.

For getconfig.bat, you must set the environment variable ECSP_HOME equal to your Cisco Netsys Baseliner installation directory (C:\Netsys).

For run_ngs, you must set all of the following environment variables in the order shown:

set ECSP_HOME=C:\<Netsys installation directory>

set ECSP_DATA=%ECSP_HOME%\Data

set ECSP_TMPDIR=%ECSP_DATA%\Temp

set RES_DIR=C:/<Netsys installation directory>/resources/topology_new

set TK_LIBRARY=%ECSP_HOME%\resources\tk8.x

set TCL_LIBRARY=%ECSP_HOME%\resources\tcl8.x

Be sure to enter the commands exactly as shown---and note the direction of the slashes. All are backward slashes except those which define the RES_DIR variables. Use forward slashes in that line.

Auto_update.bat

A sample batch file, auto_update.bat, is included in your Cisco Netsys Baseliner installation directory.

This file sets your environment variables and then runs both utilities.

The Auto_update.bat file takes three arguments, in the following order:

This batch file will collect configurations into the directory specified in the third command-line argument. If you want an output log which records any collection failures, you should pipe output of auto_update.bat to a log file (or edit auto_update.bat to pipe output of getconfig.bat to an output file).

Be careful when you specify directories on the command line---auto_update.bat will delete all files in the output directory (specified by the third argument).

The batch fill will then update the baseline specified as the first argument. As written, auto_update.bat will call run_ngs.exe with the -u option to update the baseline using the configuration files just collected then use the -cd option to generate reports and compare them with reports generated during the previous run.

If you want to use different run_ngs options, you will have to edit the auto_update.bat file.

Collecting Configuration Files Using the Tools Menu

Once a baseline has been created, you may find it more convenient to use the Collect Cisco Configurations wizard, started from a Cisco Netsys Baseliner menu selection, instead of the command-line utilities.

Using the "Set Up Router Access" Wizard

Before you can update your configuration files or baseline using the Collect Cisco Configurations wizard, the routers for which you want to collect information must be added to the Router Access Database that is maintained by the Cisco Netsys Baseliner software as part of the baseline. To do so, you must use the Set Up Router Access wizard.

Adding Routers to the Router Access Database

This wizard can be used to add, edit, or delete routers from the database, and to review the information that has been added previously.

Several steps in the Set Up Router Access wizard offer branching options that will take you down different paths.

The following sequence of step-by-step instructions will focus on what needs to be done in order to add routers to the database, thereby allowing you to use the Collect Cisco Configurations wizard.

Information about other options in the Set Up Router Access wizard will be discussed in the section "Other "Set Up Router Access" Wizard Operations."

To add to or modify the Router Access Database, do the following:

Step 1 Select the Set Up Router Access command from the Tools menu in the Cisco Netsys Baseliner software's main window. After reading the information displayed in the Start step, click the Next button to proceed. (Click the Cancel button to exit the Set Up Router Access wizard without making any changes. The Back button is grayed and unavailable at this time, since this is the first step in the wizard.)

Step 2 Select the Update (Add/Edit) access parameters option.

Click the Next button to proceed.

Or, click the Back button to return to the previous step or the Cancel button to exit the wizard without taking any action.

Step 3 In the next panel of the wizard, choose the Select from routers that already have access parameters specified if you have already added a router to the database; choose Enter their names directly... to gather data from a router that is not in the baseline; or choose the Select from all routers in baseline option to update routers already in the baseline but not yet added to the Router Access Database.

Click the Next button to proceed.

Step 4 Depending on your selection in the previous step, you will be presented with one of two options: either the Select Cisco routers to update step will present a list of routers from which you can select, or the Enter Cisco routers to update step will display an editable window into which you can enter the name of the router you wish to add.


Figure 3-1: Selecting Routers from a List


If you are selecting routers from a list, highlight the routers you want to add to the database by clicking the mouse on the router name in the Possible Choices window (multiple selections can be made by combining the Control or Shift keys with the mouse click).

When you have selected a router or group of routers, click the right-arrow button (==>) in the center of the window to add the routers to the Selected list.

Or, click the All button to select all of the routers listed in the Possible Choices window.

To remove a router or group of routers from the Selected list, highlight the router names and click the Delete button at the bottom of the Selected window, or click the Clear button to de-select all routers in the Selected box. (The Delete and Clear buttons remove routers from the Selected window only, not from the baseline or Router Access Database.)

When the list in the Selected window contains all of the routers of interest, click the Next button to proceed.


Figure 3-2: Entering a Router by Name


If you are entering the name of a router, remember that you are not adding a configuration filename; you are adding the router's hostname, which will be used as a Telnet message parameter. A directory path is not valid for this field.

Step 5 If you have only added a single router to the selection list in the previous step, skip ahead to the next step.

If you have selected more than one router in the previous step, the How do you want to specify new access parameters step will present two options. You can choose to specify parameters for all selected routers in a single operation (all routers will receive the same values), or you can choose to specify parameters for each router one at a time.

When you have made your choice, click the Next button to proceed to the next step.

Step 6 The New access parameters... step shows a list of parameters that can be set.


Figure 3-3: Enter Router Parameters


Enter a value in the edit box adjacent to a parameter you wish to change. If you want to preserve whatever value the router currently assigns to that parameter, enter an asterisk (*).

When you have entered values for each parameter you wish to change, click the Next button to proceed.

If you elected to specify parameters for each router one at a time in the previous step, this step will be repeated once for each router that you are adding to the database.

Step 7 The Confirm step will remind you of the number of routers you are about to change. If you are ready to proceed, choose the OK to update button.

If you want to change any of your previous selections in the Set Up Router Access wizard before proceeding, click the Back button at the bottom of the wizard window.

Step 8 The Complete step will tell you what action was taken---it will either show you the number of entries that were completed, or, if you selected No in the previous step, it will advise you that no action was taken.

Click the Restart wizard button to begin again, or the Done button to dismiss the wizard window.

Using the "Collect Cisco Configurations" Wizard

Before you can collect data using this wizard, you must first enter the routers of interest into the Router Access Database maintained by the Cisco Netsys Baseliner software. See the section "Using the "Set Up Router Access" Wizard" elsewhere in this chapter.

Once you have added routers to the Router Access Database, you can periodically collect current configurations for the devices in your baseline without having to open a DOS command window, using the Collect Cisco Configurations wizard.

You can choose to update your baseline with the new information or just save the new configuration files without modifying the baseline.

To collect configuration data from routers that are in the Router Access Database, do the following:

Step 1 Choose the Collect Cisco Router Configurations item on the Tools menu in the Cisco Netsys Baseliner main window.

Step 2 After reading the information presented in the Start step of the Collect Cisco Configurations wizard, click the Next button to proceed. (Or, click the Cancel button to exit the wizard and return to the Cisco Netsys Baseliner software. The Back button is grayed and unavailable because this is the first step in the process.)

Step 3 The Select the routers for collection step displays all of the routers that are currently in the baseline's Router Access Database, in the Possible Choices box at the left of the wizard window.


Figure 3-4: Select Routers for Collection


Select those routers whose configurations you want to collect, by clicking on them. (Multiple selections are allowed, using the Control and Shift keys in combination with the mouse.)

When you have selected a router or group of routers, click the arrow button (==>) in the center of the window.

Or, just click the All button in the window's center to select all routers from the Possible Choices list.

If you want to remove routers from your selection list, click on their names in the Selected window and click the Delete button (this action removes the highlighted routers from the selection list only, not from the baseline or Router Access Database).

Or, click the Clear button to remove all routers from your selection list.

When you are satisfied with your selection list, click the Next button to advance to the next step.

Step 4 The Select configuration collection options step offers two checkboxes, both selected by default. If you accept these options without change, passwords will not be shown in the collected files and filenames will not be case sensitive.

When you are satisfied with your selections, click the Next button to continue.

Step 5 The Configuration filename suffix step allows you to specify a text string that will be appended to the router's configuration filename (which will be the same as the router's hostname). For example, you may want your configuration files to use a confg suffix so that they will follow the CiscoWorks convention.

Enter the suffix to be used in the edit box provided (or leave it blank), then click the Next button to continue.

Step 6 Select the appropriate button---Yes or No---in the Update baseline or save to a directory step, depending on whether your want the newly collected data to be incorporated into your baseline or written to a directory in the form of configuration files. (If you choose to update your baseline with the new configuration data, previously generated reports may be out of date, and the layout of your topology views may be changed.) Click the Next button to continue.

Step 7 If you selected Yes in the previous step, skip ahead to the next step.

If you selected No in the previous step (meaning you do not want the collected configurations incorporated into your baseline), the Output directory for configs step will be displayed.


Figure 3-5: Selecting a Directory for Configuration Files


Identify a target directory, either by entering a valid directory path in the Directory field, or by navigating to it in the large central window. (The list includes both filenames and subdirectories; subdirectories are shown with a backslash following the name. Double-click on a subdirectory to open it; or, double-click on the first entry in the list---..\ <up one directory level>---to go back up the directory tree. The Directory edit box will show your current location).

When configuration files are written, a subdirectory will be created in the directory specified in this step and configuration files written to the newly created directory. The name of that directory will be in the form of get_config_0.11_Mar_1998_10_20_46. The directory name includes a time stamp---the date of collection followed by the time (in HH_MM_SS format).

When you have located the directory into which you want the new configuration files written, click the Next button to proceed to the next step.

Step 8 A Confirm message will remind you that continuing with the process could be time consuming, and your baseline could be changed (if you selected Yes in the previous step).

Click the Yes button to begin the collection process. The Collect Cisco Router Configuration wizard will send Telnet messages to each of the routers you specified in order to gather the configuration data.

Or, click the Back button to return to the previous step. You can step back through the entire wizard using the Back button if you want to change the number of routers or select different options.

You can also click the Cancel button to exit the collection wizard without gathering new data, but you will have to make all of the selections again the next time you start the wizard. The Collect Cisco Router Configurations wizard does not retain any settings from session to session.

Collection Log

When you use the Collect Cisco Router Configurations wizard, you can use your web browser to check on the success of the process. The Collection Logs command on the View menu will open your default web browser, with the log displayed.

Use the browser to open the index.html file in the Ntlogs subdirectory in your baseline folder. The top frame of the web page will list an index of collections, with the most recent collection listed first. Results of the collection process---number of routers contacted, number of successful collections---will be summarized in the Status column. Locate the date and time of interest and click on the link in the Status column to view details of the collection process, which will be displayed in the bottom frame. For each successful Telnet communication, the log will simply note the success; if the collection fails for any router, the log will note the reason.

You can print the entire log, or the table of logs (top frame), simply by clicking the mouse in the desired frame and selecting Print from the browser's file menu, or select the frame and use the browser's Print button.


Figure 3-6: Collection Log


Other "Set Up Router Access" Wizard Operations

In addition to adding routers to the Router Access Database, you can also use the Set Up Router Access wizard to edit information about routers already listed, delete routers from the database, or review the information that is in the database.

Editing the Router Access Database

To edit information about routers already listed, do the following:

Step 1 Choose the Set Up Router Access command on the Tools menu in the Cisco Netsys Baseliner software's main window.

Review the message in the Start screen, then click the Next button to proceed.

Click the Cancel button to exit the wizard without taking any action. The Back button is grayed and disabled at this time because there are no previous steps in the wizard.

Step 2 Choose the Update (Add/Edit) entry in database option, then click the Next button to proceed.

Step 3 Choose the Select from those in Router Access Database option, then click the Next button to proceed.

Step 4 The Select Cisco routers to update step displays a list of the routers that are in the database in the Possible Choices box on the left side of the wizard window. Choose the router or routers by clicking on their names. (Multiple selections can be made by combining the Control or Shift keys with the mouse click.) When you have selected a router or group of routers, click the right-arrow button (==>) in the center of the window to add the highlighted routers to the Selected list.

Or, click the All button to add all of the routers in the Possible Choices list to the Selected list.

To remove routers from the selection list, highlight their names in the Selected window and click the Delete button, or click the Clear button to remove all routers from the list in the Selected window. (The Delete and Clear buttons remove routers from the list in the Selected window, not from the baseline.)

Step 5 If you have selected one router in the previous step, skip ahead to the following step.

If you added multiple routers to the Selected list in the previous step, The How do you want to specify new values step will present you with the option of editing all routers in a single screen, or each router individually.

When you have made your choice, click the Next button to proceed to the next step.

Step 6 If you elected to edit all routers at the same time, or if you are adding a single router, the New values... step will present a list of the parameters that you can change, with an edit box adjacent to each parameter.


Figure 3-7: Editing Router Configuration Data


Initially, each edit box will be filled with an asterisk (*), the wildcard character used to preserve the present value of the parameter. When you click the Next button and proceed to the next step, anything you enter into any of the edit boxes will be applied to all of the routers you placed on the Selected list in the previous step.

If you elected to edit routers individually, the New values... step will present a list of the parameters that you can change, with an edit box adjacent to each parameter filled with the current value set for the first router on the Selected list. Enter new values for each parameter you want to change for this router. When you click the Next button, the New values... step will be repeated for each router on the Selected list. When all routers on the list have been edited, clicking the Next button will proceed to the next step.

Step 7 The Confirm Update step will remind you of the number of routers you are about to change. If you are ready to proceed, choose the Yes option and click the Next button at the bottom of the wizard window.

If you want to change any of your previous selections in the Set Up Router Access wizard before proceeding, click the Back button at the bottom of the wizard window.

Step 8 The Complete step will tell you what action was taken---it will either show you the number of entries that were completed, or, if you selected No in the previous step, it will advise you that no action was taken.

Click the Restart wizard button to begin again, or the Done button to dismiss the wizard window.

Removing Routers from the Access Database

To remove routers from the Router Access Database, you need to clear the access parameters---which means you will not be able to collect information about them using the Collect/Import Cisco Configurations wizard until you add them again. To clear parameters, do the following:

Step 1 Choose the Set Up Router Access command on the Tools menu of the Cisco Netsys Baseliner software's main window. After reading the information displayed, click the Next button to proceed or the Cancel button to exit the wizard without taking any action. (The Back button is disabled here because there are no previous steps.)

Step 2 In the What password operation do you want to perform step, choose the Clear access parameters option and click the Next button to proceed to the next step.

Step 3 The Clear access parameters on which Cisco Routers step will display a list of routers in a Possible Choices box in the wizard window. Select one or more routers (multiple selections can be made using the Control or Shift keys in conjunction with the mouse click), then click on the right-arrow (==>) button in the center of the window.

Or, click on the All button to select all routers in the list displayed in the Possible Choices window.


Figure 3-8: Removing Access Parameters


If you want to remove a router or group of routers from the Selected list, highlight their names by clicking on them, then click the Delete button, or click the Clear button to remove all routers from the Selected window. (The Delete and Clear buttons remove routers from the list in the Selected window, not from the access list or from the baseline).

When the Selected list contains the desired routers, click on the Next button to proceed.

Step 4 The Confirm Update step will remind you of the number of routers you are about to change. If you are ready to proceed, choose the Yes option and click the Next button at the bottom of the wizard window.

If you want to change any of your previous selections in the Set Up Router Access wizard before proceeding, click the Back button at the bottom of the wizard window.

Step 5 The Complete step will tell you what action was taken---it will either show you the number of entries that were completed, or, if you selected No in the previous step, it will advise you that no action was taken.

Click the Restart wizard button to begin again or the Done button to dismiss the wizard window.

Reviewing Information in the Router Access Database

If you have already entered routers into the Router Access Database, you can use the Set Up Router Access wizard to review their configuration parameters, by doing the following:

Step 1 Select the Set Up Router Access item from the Tools menu.

After reading the information displayed in the Start step, click the Next button to proceed, or the Cancel button to exit the wizard without taking any action. (The Back button is disabled at this point because there are no previous steps.)

Step 2 Select the Display entry in database option and click the Next button.

Step 3 The Display current values step will display a list of routers that are in the baseline but not in the database, followed by a line of column headings, followed by a spreadsheet-like grid of information about the routers that are in the database. To see the complete spread of columns, either use the horizontal scrollbar at the bottom of the window or, if your monitor is large enough, resize the window by dragging its right edge (or use the maximize button in the window's title bar).


Figure 3-9: Viewing Router Access Data


When you are finished viewing the information, click the Next button to proceed to the next step, or click the Back button to select a different Set Up Router Access operation.

Step 4 The Complete step offers you the option of restarting the wizard or dismissing the wizard window.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Apr 27 11:55:04 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.