So I was just looking at this wwn - 10000000c9800abe and its zoned to 7f:0 & 8f:0 only(checked the activ ezoneset) , not sure how the entries for 7e:0 & 8e:0 got in there .
someone must have zoned them and later removed the zone from the active zoneset ?
Once a zone is removed , does the wwn disappear from the list logins ?
Please help me understand under what scenarios this could have happened .
A symmask refresh will not clear the entries. Deleting the zone will not help either. You will need to explicitly use a symmask delete/symaccess remove to delete the entries from the login history table of the FA ports.
The only reason those entries popped up there was because someone zoned and then unzoned those FA ports from the host.
The LHT (Login history table) is not updated automatically when an initiator is unzoned from the box. The output you see above is normal as the WWN is listed as logged on to fabric however it is not logged on to the SYMM
You should update the LHT and delete the invalid logins manually using symaccess command:
In our environment we remove simply the zone from the zoneset . The zones are never deleted . When I looked through the zones I couldn't find an entry where the wwn is zoned to 7e or 8e .
I was wondering if there is any other way where the wwns got in there other than the one I mentioned ?
Also a symmask refresh wont clear these unzoned entries ?
Anonymous User
67 Posts
808
0
Posted July 3rd, 2014 06:00
A symmask refresh will not clear the entries. Deleting the zone will not help either. You will need to explicitly use a symmask delete/symaccess remove to delete the entries from the login history table of the FA ports.
The only reason those entries popped up there was because someone zoned and then unzoned those FA ports from the host.
Regards. Rohan Gupta