cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Who Me Too'd this topic

MDS to MDS ISL configuration and behaviour

Andrew C
Level 1
Level 1

Hi,

I've been Googling for days and really getting anywhere with this so I'm hoping someone here has some knowledge I can tap into!

The situation:

We have a new SAN and MDS (9148) installed and just about to start migrating VMs/physical servers to it.

There is a requirement for a SAN Copy of block data from the old SAN to the new SAN to allow the migration of some machines. Once this is done, those physical machines will then be repatched into the new MDS and zoned accordingly.

We can't connect the old SAN to the new MDS (for several reasons), nor can we connect the new SAN to the old MDS (for several reasons).

This is a 24/7 business. Downtime has been negotiated on a per application basis and to derisk the migration, it will be taking place over a 8 week period.

My conclusion is that we need an ISL between the MDS's. I've found a couple of guides on Google and YouTube for this but I'm missing something as it's not quite making sense yet.

My questions:

  • Is setting the interface mode to "E" on each side enough to make the connection an ISL? Or are other steps needed?
  • I've seen something about telling the ISL which VSAN(s) are allowed over the ISL - but not seen how to do so. Any clues would be appreciated! For info, old MDS1 and new MDS1 both have a single VSAN (10), and old MDS2 and new MDS2 both have a single VSAN (20). There is no inter VSAN routing.
  • I've seen reference to "Zone Merge Behaviour". Can someone confirm what this is please? The old MDS's have their zonesets which are appropriate for the devices connected to them. The new MDS's have their zonesets for the devices they have connected. Will creating an ISL cause these to merge into a single zoneset? If so, should I expect any downtime?
  • Finally, would anything change if the "old MDS's" were actually Nexus 5K's (-5548UP which is what is at the DR site)?

I'm happy if you tell me CLI or DCNM based methods. I should add here I can do the "basics" (aliases, zoning, zonesets, etc) in MDS, but this is not something I've come across before. There is no test MDS devices to test with, and at this stage I'm writing the change request rather than trying to get it working on the fly.

I've attached "an excellent diagram" in case that helps!

Many thanks in advance.

Andrew

Who Me Too'd this topic