|
|
|
Forum Newbie
Group: Forum Members
Last Login: Friday, April 04, 2008 12:03 PM
Posts: 2,
Visits: 8
|
|
We may need to change the CHAP password on our NSM. I've been experimenting in our lab with 2 ESX hosts and one VSA. It seems like as long as the ESX hosts have established the initial connection to the VSA they stay connected regardless if the password is changed on the VSA. I've even gone in and re-scaned the iscsi hba and it stayed connected even though the password on the VSA changed. I was also able to change the chap password on the esx host without loosing connectivity to the iscsi volume. The only time connectivity was lost was when the host was rebooted with the wrong chap password in the config. This should be expected behavior.
Am I missing anything here? This is good news because it means no downtime for our production esx hosts but I'd like to run it by here first.
Thanks
Jack
|
|
|
|
|
Supreme Being
Group: Moderators
Last Login: Today @ 3:37 PM
Posts: 108,
Visits: 375
|
|
You have it right.
The changes you make on SAN/iQ authentication don't affect current sessions, just new sessions.
The changes you make on ESX also, only affect new sessions.
Rescans on ESX servers do not disconnect and reconnect volumes. Rescans just log into new volumes.
So if you change the ESX chap password, and the SAN/iQ chap password to match, it should not have any affect on your current connections.
Next reboot you'll get connected using the new password. Also any new volumes connected will use the new password.
Hope that helps.
Adam C
Product Manager
LeftHand Networks
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: Friday, April 04, 2008 12:03 PM
Posts: 2,
Visits: 8
|
|
|
|
|