Smarts ESM: ESM used to discover W4N storage topologies but w4n-post-processing.asl is giving errors : W4NInterfaceImpl::getW4NWebServiceHandle: caught exception while creating DatabaseAccessorService: Failed to access the WSDL

Products

• VMware Smart Assurance

Issue/Introduction

Symptoms:

ESM used to discover W4N storage topologies but the following errors are seen in the ESM logs:

[April 25, 2016 10:40:55 AM GMT+03:00 +272ms] t@2811213568 ProbeCompletedRunner
ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/InCharge/ESM/smarts/rules/w4n/w4n-post-processing.asl'
ASL-ERROR_ACTION-While executing action at:
ASL-CALL_STACK_RULE- RuleName: CREATE_PORT_LINK, Line: 181
ASL-CALL_STACK_RULE- RuleName: PROCESS_LINK_DETAIL_SET, Line: 119
ASL-CALL_STACK_RULE- RuleName: START, Line: 70
ASL-ERROR_INSERT-While attempting to insert into property 'Accesses' of object 'FibreChannelArrayPort::PORT-5006016C08607AEF'
MR-OBJECT_NOT_FOUND-Object class::name '::' not found; in file "/work/redcurrent/DMT-9.4.1.0/13/smarts/repos/servif/SM_RepositoryServer.c" at line 1000

[April 24, 2016 8:36:17 PM GMT+03:00 +255ms] t@2513434368 ProbeCompletedRunner
ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/InCharge/ESM/smarts/rules/w4n/w4n-post-processing.asl'
ASL-ERROR_ACTION-While executing action at:
ASL-CALL_STACK_RULE- RuleName: CREATE_PORT_LINK, Line: 181
ASL-CALL_STACK_RULE- RuleName: PROCESS_LINK_DETAIL_SET, Line: 119
ASL-CALL_STACK_RULE- RuleName: START, Line: 70
ASL-ERROR_INSERT-While attempting to insert into property 'Accesses' of object 'FibreChannelArrayPort::PORT-5006016908607AEF'
MR-OBJECT_NOT_FOUND-Object class::name '::' not found; in file "/work/redcurrent/DMT-9.4.1.0/13/smarts/repos/servif/SM_RepositoryServer.c" at line 1000

[April 24, 2016 8:36:17 PM GMT+03:00 +269ms] t@2513434368 ProbeCompletedRunner
ASL-W-ERROR_RULE_SOURCE-While executing rule set '/opt/InCharge/ESM/smarts/rules/w4n/w4n-post-processing.asl'
ASL-ERROR_ACTION-While executing action at:
ASL-CALL_STACK_RULE- RuleName: CREATE_PORT_LINK, Line: 181
ASL-CALL_STACK_RULE- RuleName: PROCESS_LINK_DETAIL_SET, Line: 119
ASL-CALL_STACK_RULE- RuleName: START, Line: 70
ASL-ERROR_INSERT-While attempting to insert into property 'Accesses' of object 'FibreChannelArrayPort::PORT-5006016608605B1F'
MR-OBJECT_NOT_FOUND-Object class::name '::' not found; in file "/work/redcurrent/DMT-9.4.1.0/13/smarts/repos/servif/SM_RepositoryServer.c" at line 1000

Then later in the logs, there are the following errors:

[April 24, 2016 8:50:24 PM GMT+03:00 +769ms] t@2240947968 PollingQueue #2
NV_MESSAGE-*-NV_GENERIC-MSG ERR : [Thread-45 MonitoringCommon]: NOT able to reach EMC M&R. Trying to reconnect


[April 25, 2016 10:40:31 AM GMT+03:00 +072ms] t@2631616256 platform
MAIN_MSG-*-STDFD_ERR-stderr: Apr 25, 2016 10:40:31 AM com.smarts.common.ESMLogger error
SEVERE: [Thread-37] W4NInterfaceImpl::getW4NWebServiceHandle: caught exception while creating DatabaseAccessorService: Failed to access the WSDL at: http://10.168.12.45:58080/APG-WS/wsapi/db?wsdl. It failed with:
Connection refused.
[April 25, 2016 10:40:31 AM GMT+03:00 +072ms] t@2631616256 platform
MAIN_MSG-*-STDFD_ERR-stderr: javax.xml.ws.WebServiceException: Failed to access the WSDL at: http://10.168.12.45:58080/APG-WS/wsapi/db?wsdl. It failed with:
 

Environment

VMware Smart Assurance - SMARTS

Cause

The ASL errors are surfacing because there is a  ScsiPath LUN end not present in the topology.

For example "srv999.emc.com/abcde3:C0:T1:L1[NMP]" does not have LUN associated with it.
However the ScsiPath instance has "abcde3:C0:T1:L1" as the value for the "Lun" attribute.

This is the information retrieved from vCenter (mn.emc.com ) and the associated hypervisor is srv999.emc.com
Now the trouble is, in the ESM topology, no ScsiLun object exists for the "abcde3:C0:T1:L1".

When the Vcenter was checked, it was found that the Lun is not available to the vCenter but the asl script cannot handle a non discovered Lun (empty Lun object).

Resolution

Attached is an asl script which has been modified to handle a non discovered LUN object. By doing so, the error will also be avoided.

To apply:

1. Please copy the script to smarts\local\rules\w4n directory.

2. During next post processing the ASL errors mentioned should not be seen