VPN Console: File Menu

When a client browser connects to any tool, the usage is logged in a usage file, which is located in the <default_repository_path>/logs, where <default_repository_path> is the complete path name to your repository.

Additionally, you can specify access permission to the Repository Management tools. This is explained in the "Access Permission to Repository Management Tools" section. You can also run dbBackup from the command line or to back up a repository using a third party backup program. These are explained in the "Backup from the Command Line" section and the "Backup from Third Party Backup Program" section, respectively.

Backu p

This section includes the following categories:

Description

This tool backs up the MPLS VPN Solution Repository, which includes all database files, collected raw datasets, generated baseline reports, logs, service blobs, and configlets, to a local directory on the MPLS VPN Solution machine. This tool can also TAR or TAR and compress the entire backup directory.

How to Backup

Implement the following steps:

Step 1 From the window, as shown in Figure 4-3, "Repository Management Tool Choices," click Backup, either in the list on the left or in the main window itself.

An example of a resulting window is shown in Figure 4-4, "Example of Database Backup Window." The top portion of the window includes information about the fields that need information in the bottom portion of the window.

Figure 4-4: Example of Database Backup Window

Step 2 The Source Directory field (required) defaults to the directory of the currently used Repository. If you choose a different Repository to back up, in this field place the full path name to the directory of the Repository that you want to back up.

Step 3 In the Destination Directory field (required), enter the full path name to the directory where you want to place the backed up Repository.

Step 4 From Choose from the following backup options, check the following box or boxes to show how you want to back up:

DEFAULT. (The backup copy of the Repository is placed in the destination directory as is.) Choose this button if you want to just back up the Repository and leave everything as is and place it in the Destination Directory.
TAR. Choose this button if you want to back up the Repository and place it in a TAR file in the Destination Directory.
TAR and COMPRESS. Choose this button if you want to back up the Repository and place it in a compressed TAR file, and place it in the Destination Directory.
SHOW DETAILS: Check this box if you want to turn on the verbose option when backing up the database. This gives you detailed progress information.

Step 5 Click the Start Backup button once you have completed the fields and buttons in this window. This initiates the backup process and provides the widow shown in Figure 4-5, "Initiating Backup."

To return to the original values when you entered Backup, click Reset.

Figure 4-5: Initiating Backup

Step 6 In the window in Figure 4-5, "Initiating Backup," click OK to start backing up the repository. A window appears, as shown in Figure 4-6, "Example of How to Retrieve Backup Status."

Otherwise, click Cancel.

Figure 4-6: Example of How to Retrieve Backup Status

Step 7 From the example window in Figure 4-6, "Example of How to Retrieve Backup Status," click Backup Status to retrieve backup status information.

R estor e

This section includes the following categories:

Description

This tool restores a backup Repository into a destination directory. This tool reconfigures MPLS VPN Solution to use the restored Repository and to restart the watchdog servers to use the new configuration.

Caution The destination directory must be empty. If you restore a Repository over an existing repository, modification of Service Requests may not work correctly.

How to Restore

Implement the following steps:

Step 1 From the window, as shown in Figure 4-20, "Exit," all running VPN Consoles must choose File > Exit to shut down the VPN Console. This prevents other processes from having access or writing to the repository during the restore.

Note To identify whether other VPN Consoles are running, in a UNIX window, execute:
ps -ef|grep vpnconsole

Step 2 From the window, as shown in Figure 4-3, "Repository Management Tool Choices," click Restore, either in the list on the left or in the main window itself.

An example of a resulting window is shown in Figure 4-7, "Example of Database Restore Window."

Figure 4-7: Example of Database Restore Window

Step 3 In the Source Directory/File field (required), enter the full path name to the directory or file of the backup Repository that you want to restore to be the default Repository.

Step 4 In the Destination Directory field (required), enter the full path name of an empty directory where you want to place the restored Repository.

Note The Source Directory and the Destination Directory must be unique directories. They cannot be the same directory.

Step 5 From Choose following restore options, check the following box or boxes depending on the options you want:

Create destination directory if needed. When you check this box, the Restore tool creates the destination directory, if it does not exist.
SHOW DETAILS. Check this box to turn on the verbose option when restoring a backup Repository to a current default Repository. This will give you detailed progress information.

Step 6 Click the Restore button once you have completed the fields and boxes in this window. This initiates the restore process and provides the widow shown in Figure 4-8, "Initiating Restore."

To return to the original values when you entered Restore, click Reset.

Figure 4-8: Initiating Restore

Step 7 In the window in Figure 4-8, "Initiating Restore," click OK to start restoring the Repository. A window appears, as shown in Figure 4-9, "Example of How to Retrieve Restore Status."

Otherwise, click Cancel.

Figure 4-9: Example of How to Retrieve Restore Status

Step 8 From the example window in Figure 4-9, "Example of How to Retrieve Restore Status," click status.

The window as shown in Figure 4-10, "Restoring a Database," appears.

Figure 4-10: Restoring a Database

Step 9 In the window in Figure 4-10, "Restoring a Database," click OK to continue modifying the configuration and restart the watchdog.

Note You must manually restart vpnconsole at this time.

Otherwise, click Cancel.

Step 10 Restart vpnconsole.

Dataset Garbag e C ollection

This section includes the following categories:

Description

This tool allows you to purge all datasets that are collected within a specified time interval and are no longer needed. All the raw datasets are removed from the Repository. The Repository is compacted to eliminate holes created by dataset removal.

How to Do Dataset Garbage Collection

Implement the following steps:

Step 1 From the window, as shown in Figure 4-3, "Repository Management Tool Choices," click Dataset Garbage Collection, either in the list on the left or in the main window itself.

An example of a resulting window is shown in Figure 4-11, "Example of Dataset Garbage Collection." In the Modify Your Search area, there are many choices to make.

Figure 4-11: Example of Dataset Garbage Collection

Step 2 Click the Category drop-down menu button and select from the list of categories.

Step 3 Choose the following from the Begin row:

Year: Enter a four-digit integer to represent the year for which you want to begin garbage collection.
Month: Click the drop-down menu button and select from the list of months (January to December) for when you want to begin garbage collection.
Day: Click the drop-down menu button and select from the list of days (1 to 31) for when you want to begin garbage collection.
Hour: Click the drop-down menu button and select from the list of hours (1 to 12) for when you want to begin garbage collection.
AM or PM: Select either AM or PM for when you want to begin garbage collection.
Minute: Enter a valid minute (1 to 60) for when you want to begin garbage collection.
Second: Enter a valid second (1 to 60) for when you want to begin garbage collection.

Step 4 Choose the following from the End row:

Year: Enter a four-digit integer to represent the year for which you want to end garbage collection.
Month: Click the drop-down menu button and select from the list of months (January to December) for when you want to end garbage collection.
Day: Click the drop-down menu button and select from the list of days (1 to 31) for when you want to end garbage collection.
Hour: Click the drop-down menu button and select from the list of hours (1 to 12) for when you want to end garbage collection.
AM or PM: Select either AM or PM for when you want to end garbage collection.
Minute: Enter a valid minute (1 to 60) for when you want to end garbage collection.
Second: Enter a valid second (1 to 60) for when you want to end garbage collection.

Step 5 Click the Search button. The specified datasets from the Repository appear in the next widow. An example of the results of clicking the Search button are shown in Figure 4-12, "Example of Results of Search for Garbage Collection."

Step 6 If you want to eliminate any holes created by dataset removal, click the Crunch button.

Note When you click the Delete All button, as shown in Figure 4-12, "Example of Results of Search for Garbage Collection," holes created by dataset removal are automatically eliminated and there is no need to click the Crunch button.

Figure 4-12: Example of Results of Search for Garbage Collection

Step 7 The window shown in Figure 4-12, "Example of Results of Search for Garbage Collection," is an example of the result of clicking Search from the window shown in Figure 4-11, "Example of Dataset Garbage Collection." From this window in Figure 4-12, "Example of Results of Search for Garbage Collection," you can view information about all the datasets you chose to remove from the Repository. If after reviewing this list of datasets you decide you still want to delete them, click Delete All. Otherwise, you can click Start a New Search, which returns you to a window as shown in Figure 4-11, "Example of Dataset Garbage Collection," where you can Modify the Search again and Search again.

Dataset Se lective P urge

This section includes the following categories:

Description

This tool allows you to selectively purge datasets from the collection Repository but does not compact the Repository. Therefore, holes are created by dataset removal. These holes can be eliminated through the Dataset Garbage Collection tool.

How to Selectively Purge Datasets

Implement the following steps:

Step 1 From the window, as shown in Figure 4-3, "Repository Management Tool Choices," click Dataset Selective Purge, either in the list on the left or in the main window itself.

An example of a resulting window is shown in Figure 4-13, "Example of Choosing Datasets to Purge."

Figure 4-13: Example of Choosing Datasets to Purge

The data pane is divided into two columns.

Step 2 From the left column, you can choose datasets to purge by Select Devices. Make selections from the left column as follows:

Dataset Type Selection Drop-down List: This field is required if making selections from this column. Click the drop-down menu button and select the dataset type that you want to purge.
Boxes next to rows of information:

: Check the box next to each row to indicate the device or devices you want to select.

Show Catalogs: Click this button to list all the datasets that correspond to the dataset type shown in the drop-down menu and the boxes checked to specify devices. An example of the resulting window is shown in Figure 4-14, "Example of Selective Dataset Purge."

Step 3 From the right column, you can choose datasets to purge by Select Networks/Aggregations. Make selections from the right column as follows:

Dataset Type Selection Drop-down: This field is required if making selections from this column. Click the drop-down menu button and select the dataset type that you want to purge.
Boxes next to rows of information:

: Check the box next to each row to select the network or aggregation.

Show Catalogs: Click this button to list all the datasets that correspond to the dataset type shown in the drop-down menu and the boxes checked to specify devices. An example of the resulting window is shown in Figure 4-14, "Example of Selective Dataset Purge."

Figure 4-14: Example of Selective Dataset Purge

Step 4 Check the box for each dataset that you want to purge and then click Purge Selected Datasets.

The result is a window as appears in the example, Figure 4-15, "Example of Selective Dataset Purge Status."

Figure 4-15: Example of Selective Dataset Purge Status

Set Dataset Lim it

This section includes the following categories:

Description

This tool allows you to set a limit for the number of datasets, based on the type of data and device, network, or aggregation type, stored in the Repository. When newer datasets are collected from the devices, only the most recent datasets (up to the limit) are kept in the Repository. The older datasets are automatically purged.

How to Set Dataset Limit

From the window, as shown in Figure 4-3, "Repository Management Tool Choices," implement the following steps to set a limit for the number of datasets:

Step 1 Click Set Dataset Limit, either in the list on the left or in the main window itself.

An example of a resulting window is shown in Figure 4-16, "Example of Setting Dataset Limit."

Figure 4-16: Example of Setting Dataset Limit

This window includes rows of information. Each row of information gives the Current Limit of the number of datasets in the Repository for the dataset with the specified Dataset Type and Catalog Type. When this limit is reached, the oldest dataset is removed and a new one is added until all the new datasets are in the Repository.

Step 2 In each row designating a unique Dataset Type, you can override the default of Unlimited by entering an integer in the New Limit column for the maximum number of datasets for that type. Enter 0 when you want the limit set to Unlimited.

Note It is strongly recommended that you override the Unlimited default, because large numbers of datasets can impact the usability. The limit to set varies dependent on the size of your network and your host configuration.

In the csm.properties file, there is a tool that can help you monitor your disk usage for setting the dataset limits. If you specify an e-mail address for netsys.watchdog.email.disk, you will receive an error message when the free disk space rises above the level set in netsys.watchdog.disks.high in megabytes or as a percentage (default: 20%) or when the free disk space falls below the level set in netsys.watchdog.disks.low in megabytes or as a percentage (default: 10%).

Step 3 Click the Set New Dataset Limit button to activate the setting of all newly entered limits.

The resulting window shows the new limit, as shown in Figure 4-17, "Example of Results of Setting New Dataset Limit."

Figure 4-17: Example of Results of Setting New Dataset Limit

Watch Dog

You can see the window that results from executing the wdgui command by implementing this step:

Step 1 From the VPN Console window, choose File > Watch Dog (as shown in Figure 4-18, "Watch Dog").

Figure 4-18: Watch Dog

An example of the next window to appear is shown in Figure 4-19, "Watch Dog Results." It is the window that results from executing the wdgui command, explained in detail in Chapter 2, "WatchDog Commands."

Figure 4-19: Watch Dog Results

Exit

You can exit from the VPN Console by implementing this step:

Step 1 From the VPN Console window, choose File > Exit (as shown in Figure 4-20, "Exit").

Figure 4-20: Exit

Table of Contents

VPN Console: File Menu