To clear out 'old' WWNs from the SAS version of the MD32xx, you indeed have to powercycle the whole unit. I've run into this before myself where I couldn't identify which VMware server was using which WWN. There are 2 main options: - reboot 1 server, go into the SAS6E HBA firmware interface and note down the WWN (if you have just 2 servers, through process of elimination you know who is who) - disconnect 1 server and powercycle the MD array
Hello to all! I am new to this forum and have allready posted my question in another forum, but i think this is the correct place :emotion-1:. I have a - don´t know if a big - problem:We have to Dell Servers running VSphere connected to a DEll MD Storage with SAS connections.After one host lost both SAS connections (the connection control LEDs where also off) to the Storage, i tried a reboot.The connection was up again, but datatransfer was impossible, so we changed the SAS controller of the host.The new controller has new sas identifiers and i missed delete the old ones at this moment.So after the change we have 6 sas identfieres listed on the MD but only 4 could be in use (2 hosts with each one SAS Cards with 2 connectors.So i wanted to delete the old IDs afterwards but when i deleted one of the IDs and controlled in the "not Assigend IDs" Window of the MD (its called "nicht zugewiesene HOst Port Kennungen" in German, i hope my translation is not that bad) the deleted ID shows up there.We have double checked (with the Dell support) that this ID is one of the old card, but i don´t understand why the MD still shows it as if it where still connected to the storage.On this weekend i will remove the second ID, hoping that the first deleted will not show up longer when i have deleted the second one, when both still show up i will try a reboot of the storage, but than i have no further idea what i can to get rid of old card IDs. :emotion-6:Sorry for my english, its not my mother tounge...:-)Hope, somebody can help me.....Regards,Maximilian
Vsphere and Md3220