Smarts IP: Domains not reconfiguring after discovery
Article ID: 332053
Updated On:
Products
VMware Smart Assurance
Issue/Introduction
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
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
Environment
VMware Smart Assurance - SMARTS
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.
Feedback
Yes
No
Powered by
