UNSOLVED
ISL or Not to
Hi All,
We'll be starting our migration to our new Array ns120 from our cx3-20. The current SAN is the cx3-20 with two 220b's..standard config, each sp as a connection to each 220 and each host has a connection to each 220. The new array will ship with 300b's.
One of the main things we need to move is our ESX 3.5 (cx3) to the new Vsphere(NS120). The concept was to use vstorage motion move things like that..simple in theory. This assumes we have enough licensed ports on the new 300b's for bold new and old vmware servers, which we do not. Just wondering if it is sensible\smart to setup a ISL between a 220 and it's 300b counter part. I'm not suggest that all four become one be fabric, but two large fabrics during the migration.
Is this a support config? and should it be considered? Or is there something better
Cheers
jl
i would ISL both switches (make sure you meet all the requirements: firmware version, domain id has to be unique), present CX4 to ESX hosts and storage vmotion to new LUNs. After that you can swing host connections to new switch one HBA at a time. My only concern would be the ISL link ..not sure how much data you drive but one ISL maybe not enough.
dynamox
11 Legend
•
20419 Posts
•
87439 Points
375
0
Posted January 13th, 2011 06:00
so old ESX 3.5 servers and CX3 connected to 200s and new vSphere servers and CX4 will be connected to 300s ? Do you currently have ports available on 200s for ISLs ? How many ports are available ?