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: ATM link is not discovered between two network elements (359280)

Last Updated: 3/22/2024Categories: TroubleshootingTotal Views: 3111Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Smarts IP does not discover an ATM link between two network elements.

Cause

Smarts is designed to form a WAN network connection when the following conditions are met:

The IP network is only connected to two IP addresses and the two IP addresses are on different Routers.

One of the following conditions matches the interface type:

Inthe  tpmgr-param.conf file, the WAN link description exists in the WANLINK_interfacetype pattern

IP netmask is 255.255.255.252 that is /30 subnet

Interface type is of FRAMERELAY / HSSI / ATM /AAL5/ AFLAN / SONET / POINTTOPOINT

If one of these conditions is not met, the connection will not be made. If the above conditions are met, and if one IP address in the IP network is that of a router while the other IP address in the same IP network is that of either a router or a Layer 3 switch, then Smarts will create a network connection between them.

Resolution

In Smarts, a Layer 3 switch is identified by its sysObjId entry and stored in the tpmgr-param.conf file using the Layer3SwitchPattern variable. If the entry is not there for the Layer 3 switch in the tpmgr-param.conf file, do the following:

Add the Layer3SwitchPattern entry (sysObjId) in the tpmgr-param.conf file found here:

$SM_HOME/local/conf/discovery/tpmgr-param.conf

Execute the following command or restart the Smarts server:

./sm_tpmgr.exe -s <ServerName> --load-conf=tpmgr-param.conf -b <IP>:<PORT>

Execute the following commands:

./dmctl -s -b : put ICF_TopologyManager::ICF-TopologyManager::LogDiscoveryProgress true
./dmctl -s -b : put ICF_TopologyManager::ICF-TopologyManager::DebugEnabled true

Rediscover the two devices.

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