Refer to the following primus solutions -  emc101566 - > symmask list logins returns incorrect fabric login for Emulex hba's.  * This can be cleared by resetting the port.  If that does not clear the login status contact Tech Support.  emc192707 - > The login history table is historical and the entries remain even after the HBAs have logged out of it.   * Enginuity version 5671 and above has the ability to delete the entries and hence clean up the login history table.  The CLI syntax to remove the entries is as below:  SYMMASK -sid -wwn | -awwn | -iscsi | -aiscsi delete [-dir all -p all | -dir # -p #] [-login]  Specifically the -login deletes the entries in the login history table and the entries in the masking database.
Hello,  I have unzoned all of the hosts from our DMX-2000. The array is set for data erasure in a few days. I checked to make sure all zones are removed by checking in fabric manager as well as displaying the active zone set for each vsan on the core switches. All looks fine there, however, when I check using symmask, two of the hosts still show an HBA logged in as yes, in fabric yes, even after I have removed the zones. I checked each zone to make sure that the zone name was not incorrect and that the host was still zoned to the array and compared it to the active zone set. There is no active zone for those two hosts, and there is no storage shown still attached using syminq.  The command I use is symmask -sid XX list logins. I listed the output of one of the hosts below. The rest are all No No I am perplexed.  Thanks! - Admingirl  [IMAGE]
symmask showing hbas still logged in after unzoned