- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: EISL between MDS 9216i to MDS 9124
HPE EVA Storage
1752826
Members
3607
Online
108789
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-22-2009 10:52 PM
тАО04-22-2009 10:52 PM
Dear All,
Good Morning.
I need to create EISL link between MDS 9216i and 9124 and both are contains different firmware level.
MDS 9216i - 3.1(2)
MDS 9124 - 3.2(1a)
is it required the firmware level should be same on both the Switches or it is ok?
MDS 9216i contains VSAN1 and VSAN3.
MDS 9124 contains VSAN100
is i need to create VSAN1 and VSAN3 on MDS 9214 and to create VSAN100 on MDS 9216i so that zoneset will merge.
Please advice,
Good Morning.
I need to create EISL link between MDS 9216i and 9124 and both are contains different firmware level.
MDS 9216i - 3.1(2)
MDS 9124 - 3.2(1a)
is it required the firmware level should be same on both the Switches or it is ok?
MDS 9216i contains VSAN1 and VSAN3.
MDS 9124 contains VSAN100
is i need to create VSAN1 and VSAN3 on MDS 9214 and to create VSAN100 on MDS 9216i so that zoneset will merge.
Please advice,
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2009 07:20 AM
тАО04-23-2009 07:20 AM
Solution
The recommendation would be to run your switches at the same SAN-os versions if possible, but they should work together with minimal issues, if any at all. I would check the release notes for the later firmware to make sure it is compatible with the earlier version.
When you connect the switches, the isl ports will become a trunk port and you will be able to pass traffic accross that port across any vsans that are available on both sides.
So yes, you would need to create corrosponding vsans on both switches if you plan on having targets and/or initiators on both switches that need to talk to each other.
This does not mean that you can have stuff in VSAN1 talk to stuff in VSAN100. You would nee the IVR license on your switches in order to route between vsans (I don't know if it is even available on these lower end switches)
now...zonesets are per vsan so you would only need to have a vsan1 and/or vsan3 on the 9124 if you wanted to use ports on the 9124 in thsoe vsans... same for vsan100.
I am assuming that you are connecting these switches in order to either:
1. migrate multiple "fabrics" into a more easily managed infratstructure
or
2. connect 2 different sites in order to have some type of DR functionality
Can you give us any more details as to what the goals of the merge are?
Steven
When you connect the switches, the isl ports will become a trunk port and you will be able to pass traffic accross that port across any vsans that are available on both sides.
So yes, you would need to create corrosponding vsans on both switches if you plan on having targets and/or initiators on both switches that need to talk to each other.
This does not mean that you can have stuff in VSAN1 talk to stuff in VSAN100. You would nee the IVR license on your switches in order to route between vsans (I don't know if it is even available on these lower end switches)
now...zonesets are per vsan so you would only need to have a vsan1 and/or vsan3 on the 9124 if you wanted to use ports on the 9124 in thsoe vsans... same for vsan100.
I am assuming that you are connecting these switches in order to either:
1. migrate multiple "fabrics" into a more easily managed infratstructure
or
2. connect 2 different sites in order to have some type of DR functionality
Can you give us any more details as to what the goals of the merge are?
Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2009 11:12 AM
тАО04-23-2009 11:12 AM
Re: EISL between MDS 9216i to MDS 9124
Hi Steven,
Thanks for your reply.
basically i wants the zone and zonesets from 9216i should be available on 9124 and vise versa.
I have EMC storage and some hosts with zones are connected in 9216i. in 9124 hp storage and some hosts with zones are connected.
My requirement is as you said both the switches should form a fabric. right now both are doing as separate fabric.
Thanks for your reply.
basically i wants the zone and zonesets from 9216i should be available on 9124 and vise versa.
I have EMC storage and some hosts with zones are connected in 9216i. in 9124 hp storage and some hosts with zones are connected.
My requirement is as you said both the switches should form a fabric. right now both are doing as separate fabric.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-23-2009 11:46 AM
тАО04-23-2009 11:46 AM
Re: EISL between MDS 9216i to MDS 9124
"My requirement is as you said both the switches should form a fabric. right now both are doing as separate fabric."
On Cisco SAN Switches, technically your "VSAN" is your fabric so you have 3 separate "fabrics"
Since you don't necessarily want stuff on the 9216 to talk to stuff on the 9124, then I don't think you need to define a VSAN1 (and VSAN3) on the 9124 or a VSAN100 on the 9216. The switches should "link up" with a TE port and from your Fabric manager, you should be able to see VSAN0001, VSAN0003 and VSAN0100 so that you can edit the local zone databases from 1 interface.
Steven
On Cisco SAN Switches, technically your "VSAN" is your fabric so you have 3 separate "fabrics"
Since you don't necessarily want stuff on the 9216 to talk to stuff on the 9124, then I don't think you need to define a VSAN1 (and VSAN3) on the 9124 or a VSAN100 on the 9216. The switches should "link up" with a TE port and from your Fabric manager, you should be able to see VSAN0001, VSAN0003 and VSAN0100 so that you can edit the local zone databases from 1 interface.
Steven
Steven Clementi
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
HP Master ASE, Storage, Servers, and Clustering
MCSE (NT 4.0, W2K, W2K3)
VCP (ESX2, Vi3, vSphere4, vSphere5, vSphere 6.x)
RHCE
NPP3 (Nutanix Platform Professional)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP