This post is more than 5 years old
207 Posts
0
791
New ISL - Zone Merge vs Segmented
We have to locations about 1/2 mile apart. They are Pasteur and Alton. Pastuer has 2 9506 switches - pasmds1 and pasmds2. Alton has 2 9506 switches altmds1 and altmds2. Pasmds1 has a new ISL to altmds1. Pasmds2 has a new ISL with altmds2. These are the only ISL's ie: pas1 is not connected to pas2.
For the most part the switches in Pasteur are only connected to hosts and storage in Pasteur. The switches in Alton are mostly connected to hosts and storage in Alton. We do have one small vsan101 on pasmds1 and altmds1 that has 2 hosts in alton and one DMX4 port in pasteur. We have a similar situation where vsan201 has the second hba for the 2 hosts and a different DMX4 port. The ISL between the switches allows the 2 hosts in Alton to talk to the 2 DMX4 ports in Pasteur.
When we implemented the ISLs between pasmds1 and altmds1 and the pasmds2 and altmds2 we got different results and we are not sure why. The pasmds1 and altmds1 seemed to do a fabric merge and created one large fabric where all the hosts and stroage from both locations now exist.
The pasmds2 and altmds2 ISL did not seem to create a merge but created new "segmented" vsans under a new Fabric Manager folder called "Segmented VSANs". The segmented vsan for pasteur only has pasteur stuff and the segmented vsan for alton has only alton stuff.
This is our first experience with createing an ISL between MDS switches and we are not sure what is going on. Any ideas?
For the most part the switches in Pasteur are only connected to hosts and storage in Pasteur. The switches in Alton are mostly connected to hosts and storage in Alton. We do have one small vsan101 on pasmds1 and altmds1 that has 2 hosts in alton and one DMX4 port in pasteur. We have a similar situation where vsan201 has the second hba for the 2 hosts and a different DMX4 port. The ISL between the switches allows the 2 hosts in Alton to talk to the 2 DMX4 ports in Pasteur.
When we implemented the ISLs between pasmds1 and altmds1 and the pasmds2 and altmds2 we got different results and we are not sure why. The pasmds1 and altmds1 seemed to do a fabric merge and created one large fabric where all the hosts and stroage from both locations now exist.
The pasmds2 and altmds2 ISL did not seem to create a merge but created new "segmented" vsans under a new Fabric Manager folder called "Segmented VSANs". The segmented vsan for pasteur only has pasteur stuff and the segmented vsan for alton has only alton stuff.
This is our first experience with createing an ISL between MDS switches and we are not sure what is going on. Any ideas?
healyj
141 Posts
0
November 28th, 2017 06:00
Hi there,
In our effort s to clean up the forum, we came across your question / statement.
If the question / statement is still valid, not expired and you need an update please reach out again and we try to get it answered.
As for now we set it to “answered.”
Regards,
Jim
emc_troy
142 Posts
0
March 25th, 2009 11:00
emc193070 - "Cisco: How do I create a port channel via cli"
ConnectrixHelpe
259 Posts
0
March 27th, 2009 14:00
Thank you.