To enhance overlapping IP address discovery, you enable IP Availability Manager to interoperate with the MPLS VPN-Tagging Server.
Assuming that the DisableOverlappingIP, UseVPNIP, and EnableShadowIP parameters in the tpmgr-param.conf file are set as specified in the previous section, you do so by setting the following parameter in IP Availability Manager’s discovery.conf file to TRUE:
importExternalTagsConnections TRUE
In addition, you need to enable the MPLS VPN-Tagging Server to interoperate with IP Availability Manager. You do so by adding IP Availability Manager as a source to the MPLS VPN-Tagging Server.
To enable interoperability between IP Availability Manager and the MPLS VPN-Tagging Server:
-
Consult the VMware Smart Assurance IP Manager Reference Guide and the VMware Smart Assurance IP Manager User Guide and follow the instructions to set the following parameter in the discovery.conf file to the value shown:
importExternalTagsConnections TRUE -
Consult “Configuring the MPLS VPN-Tagging Server” on page 51 and follow the instructions to add IP Availability Manager as a source to the MPLS VPN-Tagging Server.
The MPLS VPN-Tagging Server performs overlapping-IP and corresponding network-connection discovery in two vendor-specific environments: Cisco and Alcatel-Lucent. To complete the configuration of the MPLS VPN-Tagging Server, open the BASEDIR/smarts/conf/vpn-tagging/vpn-tagging.conf file and perform the following additional tasks:
-
Mandatory and for Alcatel-Lucent only: Add the Enable5620SAMDiscovery parameter with a value of TRUE to the vpn-tagging.conf file.
-
Optional and for Alcatel-Lucent only: Modify the default values of the AlcatelDiscoveryInterval parameter.
-
Optional and for Cisco only: Modify the default values of the DiscoveryFilter parameter.
These parameters are described in “Description of vpn-tagging.conf” on page 43.
Descriptions of MPLS VPN-Tagging Server discovery are given in the VMware Smart Assurance MPLS Manager Discovery Guide Supplement.
-
