Cisco Voice Services Provisioning Tool User's Guide, 2.2.x - VSPT Utilities [Cisco Voice Services Provisioning Tool]

Table Of Contents

Voice Services Provisioning Tool Utilities

Perform an Integrity Check

Checking Integrity for MGC Signaling Configuration

Checking Traffic Against MGC Configuration

View Generated MML Commands

View Generated Cisco MGW Commands

Deploy a Configuration

Deploying a New Configuration

Configuring an Incremental Deployment

Perform an Audit

Back Up and Restore

Schedule a Backup or Restore

Check Status of Backup or Restore

Make a Seed File

Voice Services Provisioning Tool Utilities

VSPT 2.2 provides many utilities, including tools to accomplish the following tasks:

•Perform an Integrity Check

•View Generated MML Commands

•View Generated Cisco MGW Commands

•Deploy a Configuration

•Perform an Audit

•Back Up and Restore

Perform an Integrity Check

When provisioning is complete, you can perform an integrity check to prevent possible configuration errors. The integrity check involves:

•Checking Integrity for MGC Signaling Configuration

•Checking Traffic Against MGC Configuration

•Checking Dial Plan Results

Each integrity check is explained in more detail in the following subsections.

Checking Integrity for MGC Signaling Configuration

When you perform an integrity check for MGC signaling configuration, the VSPT does the following:

•Checks that the hostname is specified for MGC

•Checks that login/passwords are specified for MGC

•Checks that MGC ipaddrs are specified

•Checks that if MGC failover is specified, the failover IPs are specified

•Checks that MGX hostname is specified

•Checks that MGX login/password is specified

•Checks the MGX IPaddrs

•For EXTNODES where the configuration refers to an MGX, checks PeerAddrs on IPLNK to ensure that they are addresses on the specified MGX

•For IPFAS IPLNK:

–Ensures that SigSlot/SigPort is specified

–Checks SigSlot/SigPort on MGX to ensure that the values are valid as specified on the MGX

–Ensures that MGC ports and MGX ports match on the IPLNK

–Checks that all IPLNK under a single IPFASPATH map to the same port number

Note The number of IPFAS sessions utilizing a given port is displayed because some IPLNKs might use different port IDs.

Checking Traffic Against MGC Configuration

When you perform an integrity check of traffic against the MGC configuration, the VSPT does the following:

•When D-channels are defined as FAS and NFAS PRI in the trunk group/trunk section, verifies that there are corresponding IPFASPATH signaling services with corresponding IPLNKs

•Checks if there are any defined IPFASPATH signaling services defining a D-channel but no corresponding trunk group/trunk in the traffic information with a corresponding NFAS/FAS PRI.

•Checks that signaling services defined for trunk groups exist in the configuration

For information about an integrity check of dial plan results, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide.

Use the following procedure to perform an integrity check of your configuration:

Step 1 Click Tools > Integrity Check. The screen shown in Figure 3-1 appears.

Figure 3-1 Integrity Check

Step 2 Indicate the tests you want to run, and click Start.

When the tests finish, a screen similar to the one in Figure 3-2 appears showing the results of the integrity checks.

Figure 3-2 Integrity Check Results

View Generated MML Commands

The VSPT automatically generates MML commands to provision your Cisco MGC and saves these commands in a file to be executed when you deploy the configuration. To view the MML commands generated from your VSPT provisioning session, click View > MML on the VSPT menu bar. A screen displaying generated MML, similar to the one shown in Figure 3-3, appears.

Figure 3-3 First Generated MML Screen

View Generated Cisco MGW Commands

To view the Cisco MGW commands generated from your provisioning session, click View > MGW Commands on the main VSPT menu bar. A screen with generated Cisco MGW commands, similar to that shown in Figure 3-4, appears.

Figure 3-4 Example of Generated Cisco MGW Commands

Deploy a Configuration

When you finish defining a configuration, you must deploy that configuration to the Cisco MGC. You can deploy to the Cisco MGC alone, to the Cisco MGC and one or more gateways, or to gateways only.

Note A new configuration should not be deployed during times of peak load on the Cisco MGC.

A configuration created in VSPT can be deployed to a Cisco MGC as a new configuration or incrementally. Deploying incrementally allows you to more quickly deploy modifications to an existing configuration without having to redeploy the entire configuration. VSPT also allows you to visually check the incremental commands it generates before deploying those commands to the MGC.

Deploying a New Configuration

Use the following procedure to deploy a new configuration.

Note If you want to delete a component and plan to reuse the component name, first delete the component, deploy the session, and verify that the component name has been deleted before reusing the name.

Step 1 Click Tools > Deploy on the main VSPT menu bar ( see Figure 1-3). The screen shown in Figure 3-5 appears.

Figure 3-5 Deploying a Configuration

Step 2 Indicate how you want to deploy the configuration:

•To deploy to the Cisco MGC only, do one of the following:

–If you want to send the configuration to the MGC but not activate it, click the button next to Send Configuration to MGC Only.

–If you want to send the configuration to the MGC and activate it, click the button next to Send and Activate Configuration.

–If you have a continuous-service configuration with two Cisco MGC hosts, click the button next to Send, Activate and Synchronize failover. The configuration is saved on the active host and copied to the standby host. You must restart the standby server after reconfiguration to apply changes.

•To deploy to the Cisco MGC and one or more selected gateways, select one of the above three options and in Step 4 also select one or more gateways from the list in Specify media gateways for deployment.

•To deploy to selected gateways only (and not the Cisco MGC): Check the box next to Do not deploy to MGC and in Step 4 select one or more gateways from the list in Specify media gateways for deployment.

Note If you select an option other than New, the Advanced button is enabled. For information about the options this button provides, see the "Configuring an Incremental Deployment" section.

Step 3 Select a configuration in the Based on configuration drop-down list. This list displays all existing configurations on the selected MGC and the [LAST IMPORT] and [NEW] options.

•Last Import—The VSPT compares your provisioning session to the last imported configuration and deploys only changes you have made.

Note The LAST IMPORT option allows multiple users to modify an existing configuration. However, they must each be modifying a different area of the configuration for this option to work properly.

•New—Your entire provisioning session is deployed as a new configuration.

•Existing Configurations—VSPT imports the selected configuration from the Cisco MGC, compares the differences between that configuration and your current provisioning session, and deploys changes you have made.

Note Since you are deploying a new configuration, make sure to choose the New option in the Based on configuration drop-down list.

Step 4 Select the gateways you want to deploy, if applicable.

Note To select multiple gateways, you can use standard selection methods: Shift+click to select a contiguous range, Ctrl+click to select or deselect noncontiguous gateways.

Step 5 Click OK. The screen shown in Figure 3-6 appears and displays the status as the current provisioning session is deployed.

Figure 3-6 Deployment Progress

Note In a continuous-service configuration, the XECfgParm.dat file on each machine must be configured. If you experience problems, verify the integrity of the XECfgParm.dat files on both machines. Refer to Chapter 2, "Installing Cisco Media Gateway Controller Software," in the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide.

Configuring an Incremental Deployment

An incremental deployment allows you to verify each component type configuration before proceeding to the next component deployment.

Note The Cisco MGC does not support some incremental deployment processes. If you have a problem with an incremental deployment, examine the MML commands to ensure that you have properly configured the desired components. Modify the component presenting the problem, or cancel the deployment and redeploy the component as a new configuration.

Use the following procedure to configure an incremental deployment:

Step 1 Follow Step 1 and Step 2 in the "Deploying a New Configuration" section

Step 2 Click Advanced in the window shown in Figure 3-5. The screen shown in Figure 3-7 appears.

Figure 3-7 Incremental Deployment Component Selector

Step 3 Select one or more component types to deploy, and click OK.

Step 4 Go to Step 3 in the "Deploying a New Configuration" section, and complete the procedure described there. When you click OK, a screen similar to the one displayed in Figure 3-8 appears.

Figure 3-8 Confirm MML Commands

Step 5 Inspect the MML commands, modify them if desired, and click Yes to continue with the incremental deployment. Click No to reissue the deployment as a new configuration.

Perform an Audit

You can use an audit to ensure that both the Cisco MGC and a BAMS server supporting the MGC host have consistently configured signal paths. The audit involves examines signal path and bearer channel data on both servers, comparing the data, and reporting any differences.

Use the following procedure to perform an audit:

Step 1 Click Tools > Audit on the main VSPT menu. The screen shown in Figure 3-9 appears.

Figure 3-9 Perform an Audit

Step 1 Enter the MGC hostname, login, and password in the top pane of the window.

Step 2 To specify the configuration to audit, click Select, highlight the configuration to audit, and click OK.

Step 3 Enter the BAMS hostname, login, and password in the bottom pane of the window.

Step 4 To specify the configuration to audit, click Select, highlight the configuration to audit, and click OK.

Step 5 Click Audit. A screen similar to the one displayed in Figure 3-10 appears.

Figure 3-10 Audit Results

The left pane displays the signal path and bearer channel data configured on the MGC host, and the right pane displays the same data configured on the BAMS server.

Back Up and Restore

The VSPT backup and restore tool allows you to create, modify, and delete scheduled backups and restores hourly, daily, weekly, monthly, or on demand. You can perform back up and restore activities on any of the following devices if they have been configured for the MGC:

•MGC Host—Active configuration

•CAT5500—Configuration and image in Flash

•CAT2900XL—Running-config and image in Flash

•SLT2600—Running-config and image in Flash

•BAMS P2—Active configuration

•BAMS P3—Active configuration

The backup and restore tool also provides the status of each activity and generates user-viewable status logs.

Note This tool operates in coordination with the MGC server operating system and can be performed by one UNIX login (specified during the installation process).

Schedule a Backup or Restore

To schedule a backup or restore, use the following procedure:

Step 1 Click Tools > Backup and Restore on the main VSPT menu bar. The screen shown in Figure 3-11 appears.

Figure 3-11 Backup and Restore Utility

Step 2 Click the component for which you want to schedule a backup. In the following example, the MGC component configuration is backed up. A screen similar to the one shown in Figure 3-12 appears when you click the MGC component.

Figure 3-12 Scheduling a Backup or Restore

Note If you want to perform a restore, you must have a backup file alreadycreated and available on the MGC.

Step 3 Highlight the component you want to back up or restore in the left pane of the main backup and restore tool window, and click Add. A screen similar to the one shown in Figure 3-13 appears.

Figure 3-13 Schedule an Activity

Note The fields available on the Schedule an Activity screen vary according to the component selected.

Step 4 In the Activity field, select the action you want to perform. Choices include backup and restore.

Step 5 Enter the IP address of the Cisco MGC.

Step 6 Enter the MGC login and password.

Step 7 Enter a name for the backup file.

Step 8 Enter the IP address of the TFTP server.

Step 9 Enter the TFTP login and password.

Step 10 Specify whether or not to use verbose log mode. Verbose mode records all commands issued by the VSPT and any system responses.

Step 11 Select the schedule type. Choices include:

•Monthly

•Daily

•Hourly

•Weekly

•Now

•Later

Step 12 Select the hour and minute that the backup should begin.

Step 13 Click OK. The backup activity is scheduled, and a screen similar to the one shown in Figure 3-14 appears.

Figure 3-14 Display Activity Schedule

After the backup has been completed, the status of the activity is immediately available. The backup file with the name you specified is available for use with the VSPT.

Check Status of Backup or Restore

The VSPT generates status logs that provide information about each scheduled activity. The status log displays the following information for the activity:

•Date and time when activity began

•Success or failure

•File name on the TFTP server

•Directory of configuration files

•Image file name

If you specified verbose log mode, the status log also displays the sequence of commands issued by the VSPT and any system responses.

Use the following procedure to check the status of a backup or restore activity:

Step 1 In the left pane of the backup and restore tool window, click the device that has been backed up or restored. Click the Status tab in the right pane.

Step 2 Highlight the backup or restore for which you want information.

Step 3 Select the appropriate button for the action you want to perform. Choices are:

•Show status—Displays the log file for the activity.

•Acknowledge—Removes the text from the Status window and deletes the log file from the server.

•Clear—Removes the text from the Status window, but the log file remains on the server.

Make a Seed File

A seed file is a file created by the VSPT that contains the IP addresses of all of the devices in the Cisco MGC network, plus the relationship (hierarchy) between the devices. With this file, Cisco MNM can automatically deploy all the elements in the network that have been configured with the VSPT.

For information about deploying a seed file, refer to the Cisco MNM Release 2.1 User's Guide.

Use the following procedure to make a seed file:

Step 1 Click Tools > Make a Seed File on the main VSPT menu. The screen shown in Figure 3-15 appears:

Figure 3-15 Make a Seed File

Step 2 Enter the path and a filename, or click Select and specify a directory for the file. You can also choose the default, which is /var/opt/<basedir>/data/mgc/mistral/<configuration name>/WORKING/seed.file.

Step 3 Click OK. A seed file is created in the directory you specified.

	Cisco Voice Services Provisioning Tool User's Guide, 2.2.x
	VSPT Utilities
Cisco Voice Services Provisioning Tool User's Guide, 2.2.x Preface Overview Provisioning with VSPT Wizards VSPT Utilities	Download this chapter VSPT Utilities Download the complete book Book-length PDF (PDF - 1 MB) Table Of Contents Voice Services Provisioning Tool Utilities Perform an Integrity Check Checking Integrity for MGC Signaling Configuration Checking Traffic Against MGC Configuration View Generated MML Commands View Generated Cisco MGW Commands Deploy a Configuration Deploying a New Configuration Configuring an Incremental Deployment Perform an Audit Back Up and Restore Schedule a Backup or Restore Check Status of Backup or Restore Make a Seed File Voice Services Provisioning Tool Utilities VSPT 2.2 provides many utilities, including tools to accomplish the following tasks: •Perform an Integrity Check •View Generated MML Commands •View Generated Cisco MGW Commands •Deploy a Configuration •Perform an Audit •Back Up and Restore Perform an Integrity Check When provisioning is complete, you can perform an integrity check to prevent possible configuration errors. The integrity check involves: •Checking Integrity for MGC Signaling Configuration •Checking Traffic Against MGC Configuration •Checking Dial Plan Results Each integrity check is explained in more detail in the following subsections. Checking Integrity for MGC Signaling Configuration When you perform an integrity check for MGC signaling configuration, the VSPT does the following: •Checks that the hostname is specified for MGC •Checks that login/passwords are specified for MGC •Checks that MGC ipaddrs are specified •Checks that if MGC failover is specified, the failover IPs are specified •Checks that MGX hostname is specified •Checks that MGX login/password is specified •Checks the MGX IPaddrs •For EXTNODES where the configuration refers to an MGX, checks PeerAddrs on IPLNK to ensure that they are addresses on the specified MGX •For IPFAS IPLNK: –Ensures that SigSlot/SigPort is specified –Checks SigSlot/SigPort on MGX to ensure that the values are valid as specified on the MGX –Ensures that MGC ports and MGX ports match on the IPLNK –Checks that all IPLNK under a single IPFASPATH map to the same port number Note The number of IPFAS sessions utilizing a given port is displayed because some IPLNKs might use different port IDs. Checking Traffic Against MGC Configuration When you perform an integrity check of traffic against the MGC configuration, the VSPT does the following: •When D-channels are defined as FAS and NFAS PRI in the trunk group/trunk section, verifies that there are corresponding IPFASPATH signaling services with corresponding IPLNKs •Checks if there are any defined IPFASPATH signaling services defining a D-channel but no corresponding trunk group/trunk in the traffic information with a corresponding NFAS/FAS PRI. •Checks that signaling services defined for trunk groups exist in the configuration For information about an integrity check of dial plan results, refer to the Cisco Media Gateway Controller Software Release 9 Dial Plan Guide. Use the following procedure to perform an integrity check of your configuration: Step 1 Click Tools > Integrity Check. The screen shown in Figure 3-1 appears. Figure 3-1 Integrity Check Step 2 Indicate the tests you want to run, and click Start. When the tests finish, a screen similar to the one in Figure 3-2 appears showing the results of the integrity checks. Figure 3-2 Integrity Check Results View Generated MML Commands The VSPT automatically generates MML commands to provision your Cisco MGC and saves these commands in a file to be executed when you deploy the configuration. To view the MML commands generated from your VSPT provisioning session, click View > MML on the VSPT menu bar. A screen displaying generated MML, similar to the one shown in Figure 3-3, appears. Figure 3-3 First Generated MML Screen View Generated Cisco MGW Commands To view the Cisco MGW commands generated from your provisioning session, click View > MGW Commands on the main VSPT menu bar. A screen with generated Cisco MGW commands, similar to that shown in Figure 3-4, appears. Figure 3-4 Example of Generated Cisco MGW Commands Deploy a Configuration When you finish defining a configuration, you must deploy that configuration to the Cisco MGC. You can deploy to the Cisco MGC alone, to the Cisco MGC and one or more gateways, or to gateways only. Note A new configuration should not be deployed during times of peak load on the Cisco MGC. A configuration created in VSPT can be deployed to a Cisco MGC as a new configuration or incrementally. Deploying incrementally allows you to more quickly deploy modifications to an existing configuration without having to redeploy the entire configuration. VSPT also allows you to visually check the incremental commands it generates before deploying those commands to the MGC. Deploying a New Configuration Use the following procedure to deploy a new configuration. Note If you want to delete a component and plan to reuse the component name, first delete the component, deploy the session, and verify that the component name has been deleted before reusing the name. Step 1 Click Tools > Deploy on the main VSPT menu bar ( see Figure 1-3). The screen shown in Figure 3-5 appears. Figure 3-5 Deploying a Configuration Step 2 Indicate how you want to deploy the configuration: •To deploy to the Cisco MGC only, do one of the following: –If you want to send the configuration to the MGC but not activate it, click the button next to Send Configuration to MGC Only. –If you want to send the configuration to the MGC and activate it, click the button next to Send and Activate Configuration. –If you have a continuous-service configuration with two Cisco MGC hosts, click the button next to Send, Activate and Synchronize failover. The configuration is saved on the active host and copied to the standby host. You must restart the standby server after reconfiguration to apply changes. •To deploy to the Cisco MGC and one or more selected gateways, select one of the above three options and in Step 4 also select one or more gateways from the list in Specify media gateways for deployment. •To deploy to selected gateways only (and not the Cisco MGC): Check the box next to Do not deploy to MGC and in Step 4 select one or more gateways from the list in Specify media gateways for deployment. Note If you select an option other than New, the Advanced button is enabled. For information about the options this button provides, see the "Configuring an Incremental Deployment" section. Step 3 Select a configuration in the Based on configuration drop-down list. This list displays all existing configurations on the selected MGC and the [LAST IMPORT] and [NEW] options. •Last Import—The VSPT compares your provisioning session to the last imported configuration and deploys only changes you have made. Note The LAST IMPORT option allows multiple users to modify an existing configuration. However, they must each be modifying a different area of the configuration for this option to work properly. •New—Your entire provisioning session is deployed as a new configuration. •Existing Configurations—VSPT imports the selected configuration from the Cisco MGC, compares the differences between that configuration and your current provisioning session, and deploys changes you have made. Note Since you are deploying a new configuration, make sure to choose the New option in the Based on configuration drop-down list. Step 4 Select the gateways you want to deploy, if applicable. Note To select multiple gateways, you can use standard selection methods: Shift+click to select a contiguous range, Ctrl+click to select or deselect noncontiguous gateways. Step 5 Click OK. The screen shown in Figure 3-6 appears and displays the status as the current provisioning session is deployed. Figure 3-6 Deployment Progress Note In a continuous-service configuration, the XECfgParm.dat file on each machine must be configured. If you experience problems, verify the integrity of the XECfgParm.dat files on both machines. Refer to Chapter 2, "Installing Cisco Media Gateway Controller Software," in the Cisco Media Gateway Controller Software Release 9 Installation and Configuration Guide. Configuring an Incremental Deployment An incremental deployment allows you to verify each component type configuration before proceeding to the next component deployment. Note The Cisco MGC does not support some incremental deployment processes. If you have a problem with an incremental deployment, examine the MML commands to ensure that you have properly configured the desired components. Modify the component presenting the problem, or cancel the deployment and redeploy the component as a new configuration. Use the following procedure to configure an incremental deployment: Step 1 Follow Step 1 and Step 2 in the "Deploying a New Configuration" section Step 2 Click Advanced in the window shown in Figure 3-5. The screen shown in Figure 3-7 appears. Figure 3-7 Incremental Deployment Component Selector Step 3 Select one or more component types to deploy, and click OK. Step 4 Go to Step 3 in the "Deploying a New Configuration" section, and complete the procedure described there. When you click OK, a screen similar to the one displayed in Figure 3-8 appears. Figure 3-8 Confirm MML Commands Step 5 Inspect the MML commands, modify them if desired, and click Yes to continue with the incremental deployment. Click No to reissue the deployment as a new configuration. Perform an Audit You can use an audit to ensure that both the Cisco MGC and a BAMS server supporting the MGC host have consistently configured signal paths. The audit involves examines signal path and bearer channel data on both servers, comparing the data, and reporting any differences. Use the following procedure to perform an audit: Step 1 Click Tools > Audit on the main VSPT menu. The screen shown in Figure 3-9 appears. Figure 3-9 Perform an Audit Step 1 Enter the MGC hostname, login, and password in the top pane of the window. Step 2 To specify the configuration to audit, click Select, highlight the configuration to audit, and click OK. Step 3 Enter the BAMS hostname, login, and password in the bottom pane of the window. Step 4 To specify the configuration to audit, click Select, highlight the configuration to audit, and click OK. Step 5 Click Audit. A screen similar to the one displayed in Figure 3-10 appears. Figure 3-10 Audit Results The left pane displays the signal path and bearer channel data configured on the MGC host, and the right pane displays the same data configured on the BAMS server. Back Up and Restore The VSPT backup and restore tool allows you to create, modify, and delete scheduled backups and restores hourly, daily, weekly, monthly, or on demand. You can perform back up and restore activities on any of the following devices if they have been configured for the MGC: •MGC Host—Active configuration •CAT5500—Configuration and image in Flash •CAT2900XL—Running-config and image in Flash •SLT2600—Running-config and image in Flash •BAMS P2—Active configuration •BAMS P3—Active configuration The backup and restore tool also provides the status of each activity and generates user-viewable status logs. Note This tool operates in coordination with the MGC server operating system and can be performed by one UNIX login (specified during the installation process). Schedule a Backup or Restore To schedule a backup or restore, use the following procedure: Step 1 Click Tools > Backup and Restore on the main VSPT menu bar. The screen shown in Figure 3-11 appears. Figure 3-11 Backup and Restore Utility Step 2 Click the component for which you want to schedule a backup. In the following example, the MGC component configuration is backed up. A screen similar to the one shown in Figure 3-12 appears when you click the MGC component. Figure 3-12 Scheduling a Backup or Restore Note If you want to perform a restore, you must have a backup file alreadycreated and available on the MGC. Step 3 Highlight the component you want to back up or restore in the left pane of the main backup and restore tool window, and click Add. A screen similar to the one shown in Figure 3-13 appears. Figure 3-13 Schedule an Activity Note The fields available on the Schedule an Activity screen vary according to the component selected. Step 4 In the Activity field, select the action you want to perform. Choices include backup and restore. Step 5 Enter the IP address of the Cisco MGC. Step 6 Enter the MGC login and password. Step 7 Enter a name for the backup file. Step 8 Enter the IP address of the TFTP server. Step 9 Enter the TFTP login and password. Step 10 Specify whether or not to use verbose log mode. Verbose mode records all commands issued by the VSPT and any system responses. Step 11 Select the schedule type. Choices include: •Monthly •Daily •Hourly •Weekly •Now •Later Step 12 Select the hour and minute that the backup should begin. Step 13 Click OK. The backup activity is scheduled, and a screen similar to the one shown in Figure 3-14 appears. Figure 3-14 Display Activity Schedule After the backup has been completed, the status of the activity is immediately available. The backup file with the name you specified is available for use with the VSPT. Check Status of Backup or Restore The VSPT generates status logs that provide information about each scheduled activity. The status log displays the following information for the activity: •Date and time when activity began •Success or failure •File name on the TFTP server •Directory of configuration files •Image file name If you specified verbose log mode, the status log also displays the sequence of commands issued by the VSPT and any system responses. Use the following procedure to check the status of a backup or restore activity: Step 1 In the left pane of the backup and restore tool window, click the device that has been backed up or restored. Click the Status tab in the right pane. Step 2 Highlight the backup or restore for which you want information. Step 3 Select the appropriate button for the action you want to perform. Choices are: •Show status—Displays the log file for the activity. •Acknowledge—Removes the text from the Status window and deletes the log file from the server. •Clear—Removes the text from the Status window, but the log file remains on the server. Make a Seed File A seed file is a file created by the VSPT that contains the IP addresses of all of the devices in the Cisco MGC network, plus the relationship (hierarchy) between the devices. With this file, Cisco MNM can automatically deploy all the elements in the network that have been configured with the VSPT. For information about deploying a seed file, refer to the Cisco MNM Release 2.1 User's Guide. Use the following procedure to make a seed file: Step 1 Click Tools > Make a Seed File on the main VSPT menu. The screen shown in Figure 3-15 appears: Figure 3-15 Make a Seed File Step 2 Enter the path and a filename, or click Select and specify a directory for the file. You can also choose the default, which is /var/opt/<basedir>/data/mgc/mistral/<configuration name>/WORKING/seed.file. Step 3 Click OK. A seed file is created in the directory you specified.
	Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks