HPE EVA Storage
1826645 Members
3561 Online
109695 Solutions
New Discussion

Re: Two different EVAs conntect to one host, different versions of MPIO?

 
sam bell
Regular Advisor

Two different EVAs conntect to one host, different versions of MPIO?

Hi,

 

during the weekend I need to move an Exchange database from an EVA5000 to an 6400. In order to perform the copyjob I'll remove one of the servers FC links from the EVA5000 fabric and connect it to the 6400 fabric.

 

The host (Windows Server 2003 SP2) currently has MPIO for the EVA5000 installed. Can I just install the 6400 MPIO version before connecting host and EVA or are there any compatibility issues with two different versions of MPIO being installed at the same time?

 

Thanks!

3 REPLIES 3
Brad_Hedley
Occasional Advisor

Re: Two different EVAs conntect to one host, different versions of MPIO?

What versions are you running for the EVA5000 and what version do you want to run for the EVA6400.

I have a site that has a EVA3100, EVA4100, EVA4400, EVA6400 and I am using the same version of MPIO for all servers with no apparent issues.
Greybeard
Esteemed Contributor

Re: Two different EVAs conntect to one host, different versions of MPIO?

You only hava a single fibre to each EVA during this process? Bypass the Switch and set an EVA host port to direct attach, then no multipath so no need for MPIO :)

_________________________________________________
How to assign points on this new forum? Click the Kudos Star!
Sheldon Smith
HPE Pro

Re: Two different EVAs conntect to one host, different versions of MPIO?

You don't need to bypass the switch or fiddle with EVA host port settings. Just zone the system with one path to each array. Still no need for MPIO at this time.

After data (and fibre?) is moved, then make sure you have the latest MPIO, set your zones and go. One thing I didn't catch, are there new switches or are you using existing fabrics? If using existing fabrics, you would not need to move fibre cables.


Note: While I am an HPE Employee, all of my comments (whether noted or not), are my own and are not any official representation of the company

Accept or Kudo