<h2>Errors during the vCenter discovery</h2><br/><div style="overflow-x:auto"><article><div ><h3 >Issue </h3><section><ul style="list-style-position: inside;"><li>The below errors are observed during the vCenter discovery<br /><br /> <table style="height: 61px; width: 57.6191%; border-collapse: collapse; border-style: hidden; background-color: #f0f0f0;" border="1"><tbody><tr style="height: 61px;"><td style="width: 100%; height: 61px;"> <ul style="list-style-position: inside;"><li><span style="color: #ff0000;">ICSI Export not found for targetIQN: iqn.1992-08.com.netapp:sn.xxxxxxxxxx:vs.14 lun: key-vim.host.ScsiDisk-xxxxxxxxxxxx<br /><br /></span></li><li><span style="color: #ff0000;">Controller is empty for FC Port<port id>:xxxxxxxxxxxxxxxx</span></li></ul> </td></tr></tbody></table> </li></ul></section></div><div ><h3 >Release</h3><section><ul style="list-style-position: inside;"><li>All</li></ul></section></div><div ><h3 >Resolution</h3><section><ol style="list-style-position: inside;"><li><span style="color: #ff0000;"><span style="color: #000000;">This vCenter storage warning message</span> "ICSI Export not found for targetIQN: iqn.1992-08.com.netapp:sn.xxxxxxxxxx:vs.14 lun: key-vim.host.ScsiDisk-xxxxxxxxxxxx" <span style="color: #000000;">can be ignored safely.<br /></span></span> <ul style="list-style-position: inside;"><li><span style="color: #ff0000;"><span style="color: #000000;">The source of these warnings is "<strong>VMWare - vCenter ESX Hosts Storage</strong>" probe, while the "<strong>StorageReconciler</strong>" script include tries to find storage <strong>FC</strong> and <strong>iSCSI</strong> Exports.<br /><br /></span></span></li><li><span style="color: #ff0000;"><span style="color: #000000;">These warnings are informative to mention that the discovery tried to retrieve FC/iSCSI exports and the VMware queried items are empty.<br /><br /></span></span></li><li><span style="color: #ff0000;"><span style="color: #000000;">To fix these warning messages, it is recommended that the customer has to check internally with their <strong>VMware storage administrator</strong> to fix empty FC/ISCSI exports issue with the storage devices.<br /><br /></span></span></li></ul> </li><li><span style="color: #ff0000;">"Controller is empty for FC Port<port id>:xxxxxxxxxxxxxxxx" <span style="color: #000000;">are also the warnings.<br /><br /></span></span> <ul style="list-style-position: inside;"><li><span style="color: #ff0000;"><span style="color: #000000;">In the script include '<a title="StorageReconciler" href="https://<instance_name>.service-now.com/sys_script_include_list.do?sysparm_query=nameSTARTSWITHStorageReconciler&sysparm_first_row=1&sysparm_view=&sysparm_choice_query_raw=&sysparm_list_header_search=true" rel="nofollow">StorageReconciler</a>', we have the function '_findControllers'<br /><br /></span></span> <table style="height: 486px; width: 26.3444%; border-collapse: collapse; border-style: hidden; background-color: #f0f0f0;" border="1"><tbody><tr style="height: 488px;"><td style="width: 100%; height: 488px;"> findControllers: function(targetWWPNs) {<br /> var portsGr = this.queryFcPorts(targetWWPNs);<br /> var controllerSysIds = [];<br /> var portSysIds = [];<br /><br /> // Get all port sysIds<br /> while (portsGr.next())<br /> portSysIds.push('' + portsGr.sys_id);<br /><br /><br /> // Get controllers from cmdb_rel_ci<br /> var df = new DiscoveryFunctions();<br /> var typeId = df.findCIRelationshipType("cmdb_rel_type", "Controller for::Controlled by");<br /> var rels = new GlideRecord("cmdb_rel_ci");<br /> rels.addQuery("child", portSysIds);<br /> rels.addQuery("type", typeId + '');<br /> rels.query();<br /><br /> while (rels.next()) {<br /> controllerSysIds.push('' + rels.parent);<br /> }<br /><br /> return controllerSysIds;<br /> }<br /> =========================================================<br /> The 'controllerSysIds' are passed to this call:<br /> =========================================================<br /> var controllerSysIds = this._findControllers(targetWWPNs);<br /> if (controllerSysIds.length == 0)<br /> throw 'Controller is empty for FC Port' + targetWWPNs.toString();<br /> =========================================================</td></tr></tbody></table> </li><li>This is the part which is throwing the error and it means that there is no controller connected to that FC port.<br /><br /></li><li>The message is thrown when Discovery tries to retrieve a list of controllers and if that list is empty.<br /><br /></li><li>Customer has to check this internally with their <strong>ESX hosts storage admin</strong> if Fibre Channels are used and if they are, it is likely that the fcports are not connected to a controller and also has to confirm with their <strong>vCenter storage admin</strong> if Fibre Channels are used in storage configuration of VMware environment.</li></ul> </li></ol></section></div></article></div>