Using RT values instead of VRF names

By default, VPNs are named based on the familiar VRF names. You can choose to use Route Targets instead to name VPNs.

Important:
If devices have previously been discovered with VRF naming, duplicate VPN entities might be displayed on the next discovery. For example, the same VPN entity can appear twice, once with the VRF name and once with the RT value. To avoid duplicate device entries, set the LingerTime of all devices in the topology to zero before running your next discovery. To do this, proceed as follows:
  1. Log into the OQL Service Provider using the following command:
    ncp_oql -domain NCOMS -service Model
  2. Run the following command to set the LingerTime to zero:
    update ncimCache.lingerTime set lingerTime = {LINGERTIME=0};
go

For MPLS networks, Network Manager uses Route Target (RT)-based discovery, using VRF and RT information to determine which provider edge routers are involved in a VPN. The core view consists of all MPLS-enabled devices, and VPNs resolve based on RT information.

To use RT values instead of VRF names:

  1. Exit all instances of the Discovery Configuration GUI.
  2. Go to the NCHOME/etc/precision directory.
  3. Edit the DiscoConfig.DomainName.cfg file and set the m_RTVPNResolution field to 1 in the disco.config table. The default is 2 (use VRF).
  4. Restart the ncp processes to read the configuration files again: 
    itnm_stop ncp
itnm_start ncp

    Alternatively, restart the ncp_config process.

Note: RT-based discoveries do not require label data. However, you can retrieve the label data as described in Fine-tuning label data.