Unsolved
This post is more than 5 years old
45 Posts
0
704
January 12th, 2011 23:00
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
dynamox
9 Legend
•
20.4K Posts
0
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 ?
kenn2347
542 Posts
0
January 13th, 2011 12:00
I think you will also need the full fabric license for the ISL's to work. Not sure if that comes standard on the 300's but they didnt on the 220b's.
dynamox
9 Legend
•
20.4K Posts
0
January 13th, 2011 12:00
nahh ..you only need a license if you want to trunk ISL ports.
kenn2347
542 Posts
0
January 13th, 2011 12:00
ah thats right. Thanks Dynamox for the correction.
Loudenj
45 Posts
0
January 13th, 2011 16:00
On the old switches we can free up 1 maybe two ports, the new ones have two spare each .
From: dynamox
Sent: Friday, 14 January 2011 1:07 AM
To: John Louden
Subject: New message: "ISL or Not to"
EMC Community Network
ISL or Not to
reply from dynamox in Infrastructure Connectivity - View the full discussion
dynamox
9 Legend
•
20.4K Posts
0
January 13th, 2011 20:00
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.