Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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: Domains not reconfiguring after discovery (500679)

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

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Case has a topology split manager setup to discover and split devices into multiple domains.
Normally, when the topology split manager (TSM) finish the discovery, it splits the list of discovered devices into the AMPM domains.  The list of devices would show up in the pending list waiting for the discovery to occur.  Once the discovery completes, reconfigure will run to build instrumentation objects.

However, when the above reconfiguration does not occur, the following error was seen in the TSM domain log:

May 18, 2017 2:30:48 PM GMT+00:00 +270ms 151561463 2554324736 ALWAYS SM_ProtocolEngine-5269 10886 Perl-Client-10886-8 AD_MSG-TMG2_STATUS_DISCOVERY_START Last discovery started at May 18, 2017 2:30:48 PM GMT+00:00

May 18, 2017 2:55:39 PM GMT+00:00 +233ms 152887729 932099840 WARN ProbeCompletedRunner ASL_ERROR_STRING_AS_DOUBLE ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/EMC/IP/smarts/rules/icf-r/iprm-reconfigure.asl' ASL-ERROR_ACTION-While executing action at: ASL-CALL_STACK_RULE- RuleName: DISCOVERY_DONE, Line: 77 ASL-CALL_STACK_RULE- RuleName: INIT, Line: 38 ASL-ERROR_STRING_AS_DOUBLE-The string '<null>' cannot be converted to a numeric value

May 18, 2017 2:55:39 PM GMT+00:00 +234ms 152887732 932099840 ALWAYS ProbeCompletedRunner AD_MSG-TMG2_STATUS_DISCOVERY_COMPLETE Last discovery completed at May 18, 2017 2:55:39 PM GMT+00:00

Cause

User had replaced the tpmgr-param.conf file from an older version of the application to the 9.4.2 version.

Resolution

Replace the correct version of the tpmgr-param.conf file into location.

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