This post is more than 5 years old
11 Posts
0
4042
Mds 2900 to Mcdata Ds-24m2 to host issues
All,
I'm going to explain in detail what i'm trying to do and what my issue is:
Scenario:
I have a cisco emc mds 2916ia switch in datacenter 1 connecting to a MCdata Ds-24m2 san switch that connects to a host. In datacenter 2 I have a Mcdata ds-24m2 san switch connecting to a cisco emc dms 2916ia switch. These two datacenters are connected by an fcip tunnel between the two cisco switches. My goal is to be able to see the host in datacenter 1 from the san switch in datacenter 2. This is suppose to be possible from what I was told.
Datacenter 1 connections:
1.) MDS 2916i gig0/1 connects to Core switch port 1 which is connecting to datacenter 2 through fcip tunnel on datacenter 2 Mds2916i port 1.
2.) MDS 2916i port 1 (e port) goes to Mcdata ds-24m2 san switch port 1 (e port)
3.) Host (f port) connects to Mcdata ds-24m2 san switch port 2 (e port)
Datacenter 2 connections:
1.) MDS 2916i port 1 (e port) goes to Mcdata ds-24m2 san switch port 1 (e port)
2.) No host (trying to view host in datacenter 1 from san switch)
3.) MDS 2916i gig0/1 connects to core port 1 which is connecting to datacenter 1 through fcip tunnel on datacenter 1 Mds2916i port 1.
Issue:
I cannot zone (MDS 2916i port 1 (e port)/Mcdata ds-24m2 san switch port 1 (e port)) ----> to host. I get zone merge failure from the cisco switch port.
Please help. Thank you.
healyj
141 Posts
0
December 12th, 2017 07:00
Hi there,
In our efforts 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 will set it to “answered.”
Regards,
Jim
DAucar
11 Posts
0
December 20th, 2010 08:00
I'm trunk 1 vsan over the link for testing purposes.
DAucar
11 Posts
0
December 20th, 2010 08:00
On the san switches inerop mode 1.0 and on the cisco switches interoperability mode:default which i believe is the same as the san switch.
ConnectrixHelpe
259 Posts
0
December 20th, 2010 08:00
Hello,
What interop modes are you using on the switches?
Thank you.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 20th, 2010 08:00
are you trunking any VSAN across the link ?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 20th, 2010 09:00
can you describe your VSAN layout in each datacenter. Do you have Enterprise license (which includes IVR) ? Can you run "show vsan " ..what is interoperability is set to ?
Btw ..the model is 9216i ..not 2916
DAucar
11 Posts
0
December 20th, 2010 10:00
Yes sorry didn't realized I flipped 9 and 2.
Here is some output from my switch do sh vsan, I'm only trying to push over vsan 2 right now:
(This is the same on both sides on the mds 2916i).
vsan 1 information
name:Default state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down
vsan 2 information
name:EMCSAN state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down
vsan 3 information
name:EMCSAN2 state:active
interoperability mode:default
loadbalancing:src-id/dst-id/oxid
operational state:down
vsan 4094:isolated_vsan
As for the IVR I believe this license output from my switch should cover it:
VENDOR cisco
INCREMENT SAN_EXTN_OVER_IP_9216i cisco 1.0 permanent 1 \
I thought that fcip allowed trunking which carried over vsan already? Do I some how need to configure on IVR and that will allow the host to connect to?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 20th, 2010 11:00
you are correct, you are well covered.
first of all i am not sure that your MDS is talking to your McData. When you connect McData or Brocade to Cisco ..you have to set specific interop mode on the VSAN
http://www.cisco.com/en/US/prod/collateral/ps4159/ps6409/ps4358/prod_white_paper0900aecd804bbe7d.html
as far as connecting your host accross the link to the array you have two options:
1) merge two fabric across the link
2) use IVR over transit VSAN to establish connectivity.
I strongly encourage you to use option 2 as it ensures minimal impact to fabric at each datacenter in case of fcip link flopping. So you can have something like this:
DAucar
11 Posts
0
December 20th, 2010 12:00
This is helpful. I'm not sure this is my answer yet, I will continue if it does I will post here:
Side note: I was able to establish link connectivity when I wasnt' trying to zone the host port on the san switch to the mds port on the san switch. That is where i'm failing, but I think your post is going to help hopefully "fingers crossed". Thanks for your time.
DAucar
11 Posts
0
December 21st, 2010 07:00
There are four ports at the beginning, but was only working with 1 connection for the time being. 3 out of the 4 ports were linked before any zones were created on the san switch. The 1 that didn't link had a difference from the other 3, it was that this switch interop mode was Mcdata 1.0 and the rest were open fabric 1.0.
So I do get a link established and can see all the wwn across both sites on my mds switch. When I zone the (host/san) to (san/mds) connection I get a zone merge failure and the link drops. At that time I can still see all the wwn of all the hosts on the san switches from both sites.
I do not believe IVR is what I want since I am not trying to have two vsans on the same device communicate between eachother. I just want to be able to view host A in datacenter 1 from datacenter 2 san switch.
Please correct me if i'm wrong about ivr. Thanks.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 21st, 2010 07:00
can you post a visio diagram ..or draw something in Microsoft Paint ..it's hard to understand without a picture (at least for me)
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 21st, 2010 07:00
include VSAN information too (domain id, numbering ..etc)
RRR
2 Intern
2 Intern
•
5.7K Posts
0
December 21st, 2010 08:00
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 21st, 2010 10:00
can you also show output from:
show vsan 2
on each switch.
DAucar
11 Posts
0
December 21st, 2010 10:00
Visio