This post is more than 5 years old
5 Posts
0
23316
January 30th, 2014 02:00
Vsphere and Md3220
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
Dev Mgr
4 Operator
•
9.3K Posts
0
February 1st, 2014 17:00
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
DELL-Sam L
Moderator
•
7.7K Posts
0
January 30th, 2014 10:00
Hello maximilianp,
Here is a link to the administrator guide and if you look on page 60 Step 10 it explains how to remove the Host Port Identifiers. ftp://ftp.dell.com/Manuals/Common/powervault-md3200_Administrator%20Guide_en-us.pdf I would check with how it is stated there and confirm that you are doing the steps correctly.
Please let us know if you have any other questions.
maximilianp
5 Posts
0
January 30th, 2014 11:00
Hallo Sam!
Thank you for your fast reply!
I thought, that when i remove the host port identifier and the device with the identifier no longer exists, than the ID shold not longer be shown in the "Known unassociated host port identifiers" window.
But after removing it from Host port identifier information area., it appears there!
I thougt the listet ID in this window are the ones the storage detects automatically? or isn´t this correct?
So the only way to get rid of unwanted ids is to replace it?
I have red the page 60, it was exact the way i tried it.
Or maybe as long the second port of the removed controller ist associated with one host, it is shown?
I fear to remove both, because i fear to cut the connection to a working host, although it seems impossible to me....:-(
Maximilian
DELL-Sam L
Moderator
•
7.7K Posts
0
January 30th, 2014 13:00
Hello maximilianp,
As long as you have the replacement HBA assigned to the host you should be good to remove the second connection. What I would do is if you have a window where you can stop the IO to the MD or a time when IO is low then I would do it then just in case there is any issues with the host losing access for a few seconds.
Please let us know if you have any other questions.
maximilianp
5 Posts
0
January 31st, 2014 15:00
I´ll give a try on sunday!
Thank you for your inputs!
Maximilian
maximilianp
5 Posts
0
February 1st, 2014 11:00
Hello Sam!
have have removed the connections from the removed HBA, no problems at all, i have removed the 2 correct IDs. But the ids still show up in the "Known unassociated host port identifiers" window.
Then i tried following:
I removed one the Ids of the new active HBA, made a new host with one the ids from the old removed HBA and tried to replace this ID with the one of the active HBA. But still no luck: Both old ids are again in the "Known unassociated host port identifiers" window - as if the old HBA still exists and is connected to the storage.
My last chance: reboot the storage. But i don´t think, that this will solve the problem.
Maybe you have another idea?
Regards, Maxi
maximilianp
5 Posts
0
February 3rd, 2014 03:00
Thanks for your answer!
I am a little bit relieved!
The support from Dell used following command to find out the installed hba:
Login via SSH
The this command:
esxcfg-scsidevs -a
in the answer of this command we found the first Id of the installed hbas
regards