HPE EVA Storage
1827072 Members
3501 Online
109713 Solutions
New Discussion

Re: Cascading SAN Switches with 2 EVAs

 

Cascading SAN Switches with 2 EVAs

Good Morning.

I have some issues when i try to cascade 2 SAN Switches, SW_A (SW SAN 4/16) and SW_C (SW SAN 4/8), the licences of each one are different.

I read some messages and i take notes to make it right:

I've disabled the zone configs in 2nd Switch (SAN sw 4/8). ("cfgdisable")

I've changed the Domain ID in each switch

The ports for the cascade are E_Port,

The SFP are in both switches are 4 GB/s

The Firmware versions are different, ive planning to ugrade the both switches to 5.3.0 or v6.0.0b. (¿the version 6 is necesary?)

The 1st Switch (4/16) has full licenses, but the 2nd (4/8) has only 2 Licences.

I´ve attached the logs of the 2 switches, i think that the 2nd switch has the probelm because that not have the licenses to make the cascade, i hope to be right on this.

I need some recomendations to put this switches to work togheter. The fisrt Switch are in producction with a EVA4000 and 12 Integritys.

Q1: The version of the FW must be identical in both switches.

Q2: When i disable de zone config in the 2nd switch, what can i do for configure aliases and zones in the new switch?

Q3: i have to make more configurations in the switch for de cascade?

Thanks a lot.

P.D: Sorry about the errors in the language.
4 REPLIES 4
Uwe Zessin
Honored Contributor

Re: Cascading SAN Switches with 2 EVAs

> Q1: The version of the FW must be identical in both switches.

Technically, there is _some_ compatibility (as one must be able to do rolling upgrades in a Fabric), but it is a good idea to run the same version everywhere if it is possible.

> Q2: When i disable de zone config in the 2nd switch, what can i do for configure aliases and zones in the new switch?

The switches _should_ merge existing zones if there are no conflicting names / member lists.

> Q3: i have to make more configurations in the switch for de cascade?

On first look, no, but I have not checked _every_ switch parameter.


The biggest problem, however, is that SW_C is missing a Fabric license as can be seen in the "switchShow" output:
: 5 5 id N4 Online E-Port segmented,(No Fabric License)

Without that license, no merge will happen.
.

Re: Cascading SAN Switches with 2 EVAs

Thanks.
in that case, i´ll find the fabric licence.

i´ll have another Questions:

Q4: I´ll have to disable the zone config "cfgdisable" in the 2nd switch to the merge works?, i dont know if this visible from the logs that i´ve posted.

Q5: The administration of the all ports of both switches its managed from the 1st switch (Primary), or i´ll have to enter in each switch to configure them, Ej: Aliases, Zones, Configs.

Q6: I need to add another EVA4100 in the SAN eviroment when the merge in switches has completed. in that case, there will be 2 EVAS. They can be managed with one Storage Server right?


Thanks
Uwe Zessin
Honored Contributor

Re: Cascading SAN Switches with 2 EVAs

A4: yes, but it might still not work if there are conflicting definitions -e.g. two zones with the same name, but different members.

A5: Administration should be done from a switch with the most current firmware - all changes will be sent to the other switches in the fabric.

A6: Yes, no problem. You can have a second server as a 'warm standby', but I feel it is easier to manage and monitor both systems from one interface.
.

Re: Cascading SAN Switches with 2 EVAs

All right. i will make this changes, and let you know about the results...

Thanks for the help.