Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Smarts IP: Use of Shadow IP addresses for compatibility with OI, NPM and MPLS domains (519440)

Last Updated: 12/17/2018Categories: TroubleshootingTotal Views: 4441Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

With IP Tagging, the IP domain will associate a device IP with a tag at the end.   For example a device with IP 172.123.120.24 with after getting an IP tag will show as 172.123.120.24/<Tag>  This IP Tag will also be synced with OI, NPM and MPLS domains.  However these domain types are not fully compatible with an IP/tag format.

Without a shadow IP address, the SNMP traps are will be dropped by the OI trap receiver.  The IP address of the trap is still the source IP and not the tagged IP address.  So you will receive the message that the IP address is not matched by the trap processor

One can have the option to enable shadow IP (EnableShadowIP) to true.  However, devices that also have Virtual IP addresses will not get shadow IP addresses.

Cause

When DisableOverlappingIP flag is set to FALSE it enables IP-tagging probes. These probes identifies certain IP addresses as VPN IP addresses. The shadow IP address creation has checks to exclude the VPN IP addresses.

Resolution

In Version 9.4.2 Patch 26, and 9.5.1 a new parameter was introduced, EnableShadowIPForVPNIP.   For this and newer version of Smarts customers to be able to use IP Tagging along with creating a shadow IP address for compatability with OI and NPM and MPLS will need to do the following:

Add new flag "EnableShadowIPForVPNIP TRUE" - ~/local/conf/discovery/tpmgr-param.conf file

Disable flag "DisableOverlappingIP FALSE" - ~/local/conf/discovery/tpmgr-param.conf file

See notes for a more detail explanation to introduce IP tagging

Related Information

1. To enable IP tagging you need to mark flag "DisableOverlappingIP FALSE" in tpmgr-param.conf this is must.
//Description:
# DisableOverlappingIP(Enable/Disable Overlapping IP Feature).
# Controls whether the IP Manager discovers MPLS-related VPN routing and forwarding (VRF) IP
# addresses and performs IP tagging:
#            A value of TRUE indicates that the IP Manager does not discover VRF IP addresses and thus does not
#              perform IP tagging.
#            A value of FALSE indicates that the IP Manager discover s VRF IP addresses and performs IP
#         tagging.
#            When DisableOverlappingIP = FALSE, all discovered VRF IP objects are subject to IP tagging.

2. Now above flag only enables IP tagging feature but to make that tagged IP available to satellite domains like OI, MPLS we need to create SHADOW IP. To process a trap, OI domain looks for this shadow IP(without "[SHADOW]" keyword) and entertain the traps. Hence to make shadow IP available for satellite domains we need to enable flag "EnableShadowIP TRUE" in tpmgr-param.conf
//Description:
# This flag is used to create Shadow IP objects whenever the User uses
# Tagging to tag IP objects. This is used for Backwards Compatibility
# so that the current IP product would work with the satellite servers(NPM etc)
# without change of code in them
#            A value of TRUE indicates that shadow objects are created.
#            A value of FALSE indicates that shadow objects are not created.
#
# Default Value = TRUE

3. Now comes the last flag EnableShadowIPForVPNIP, this flag is recently introduced. When this flag is set shadow IP is created for all the IPs. This flag basically skips the IP objects creation logic that is there in VPN IP creation rule and creates the IP in the normal flow which is the intended. The normal flow should create the shadow IP.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant