1

I have spent a lot of time researching and i have an open support ticket with vMware. I just wanted to reach out here just in case someone has done this before:

We have 3 vMware hosts, currently they are connected directly to a cybernetics SAN via SAS cables. A decision was made to upgrade the SAN controller modules to 10GB capable iscsi modules.

I decided to create tackle the vmware part first and i am creating the storage network etc. My question is, can i test the new network by connecting to iscsi (QNAP for testing iscsi connectivity) while SAS is still connected and will i run into any issues with my existing SAS connection if i add iSCSi to my environment?

I just want to make sure the vmware iscsi part is working before upgrading the SAN, that way we can avoid phone tags between vendors if something goes wrong during the upgrade.

@support-team-vmware

7 Spice ups
2

We have VMware hosts attached to local SAS and iSCSI without issue.

I am not saying you can have iSCSI and SAS to the same storage or datastore.

2 Spice ups
3

Regardless of what you read… Run an update during maintenance window :slight_smile:

1 Spice up
4

UPDATE: I successfully did this last night. It took 7 hours and here is why:

We migrated from 6GB miniSAS cables to 10GB ports on our Cybernetics SAN. We got new controller modules and replacing them was just plug and play. Easy right?

Proceeded to enable jumbo frames on the SAN, cisco switches, and in vmware vmkernel. Everything connected like it should.

We added the SAN via iSCSi to vmware and scanned everything and we saw paths and could add datastores… The catch was the SAN had snapshots and we had to re-signature the datastores.

If anyone here ever hears vmware support talk about re-signature your datastores, know that you are in for a ride. Resignaturing datastore meant re-registering every vm manually and its not a fun task for a big environment. We spent a lot of time in the vmware cli and 7 hours later, all vms were up and running.

Just in case someone runs into this and find this subreddit : Our issue was caused by the SAN snapshots, NOT Vmware snapshots

Reply