VRC uses the Discovery operation to create a new design based on the current configuration of the network elements.
Note: You must execute your first Discovery at the Administrative Domain (AD) level.
When you execute a Discovery operation from the Baseline View, a Design View session opens with the discovered dial plan displayed.
During discovery, VRC queries each device for its dial plan configuration and displays the results. Validation errors are saved in the user log and indicated on the VRC user interface to help you resolve inconsistencies.
When you execute the Discovery operation from the Baseline View, the baseline dial plan is not automatically updated. You can view the discovered dial plan in a discovery design session and make changes without affecting the baseline dial plan. To change the baseline dial plan, you must commit the dial plan design.
When a network element is Discovered by VRC, and its running configuration is not already in the directory /opt/cisco/vnm/gdpm/data/dialplan/origconfig, the element's running configuration is saved in that directory. If you need to restore an element's original configuration, you can manually retrieve it from this location.
If you begin using VRC by Discovering an existing operational network and you want to revert to the network as it was when the first VRC Discover was executed, you can execute a Rollback operation from the VRC console. This operation installs all files found in the origconfig directory as the running config on the respective elements.
Note: If you have made changes in the physical network between the time of the original VRC Discovery and the time of the Rollback, the Rollback operation can lead to dial plan inconsistencies.
Use this procedure to discover the dial plan configuration of the elements in the network. You can execute a discovery at the AD level or at the region level.
Prerequisites:
You must have AD permission to execute a Discovery.
You must be in the Baseline View to execute the Discovery operation
You cannot have an open design session for the AD.
Select the Administrative Domain.
Right-click and Choose Discover from the menu.
You are prompted for the CSR route type. If you do not choose a CSR route type, the default is None.
If you choose None, VRC disables all CSR-related dial plan features in the AD.
If you choose Carrier, VRC assumes that all CSR-related dial plan features utilized in the dial plan are carrier based.
If you choose Trunk-Label, VRC assumes that all CSR-related dial plan features utilized in the dial plan are trunk-label based.
4. Choose a Normal or Forced Discovery. Checking the box results in a forced discovery.
Normal Discovery - The VRC looks for the dial plan and if any of the following errors are encountered, the process stops and informs you of the errors.
If the element is unreachable.
If the running configuration for the element does not match the element defined in topology. Two examples of this are: The running configuration is for a gateway but the topology lists this element as a gatekeeper. There is an IP address mismatch where the running configuration does not contain the voice-enabled IP address that the element should have.
A gateways has no voice ports defined.
Forced Discovery - The VRC looks for the dial plan and the process continues regardless of any errors. The errors are listed on the VRC server in a user log.
5. Click Discover to execute.
6. Click Continue to display the dial plan in a discovery design session window.
Click Cancel to cancel the procedure.
Note: The discovery process produces a design that is comparative, but not identical, to the configuration that is generated by VRC. If you want the configuration stored on the VRC server to exactly reflect the discovered dial plan, use the Distribution process.