I'm trunk 1 vsan over the link for testing purposes. 

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.

Hello,

What interop modes are you using on the switches?

Thank you.

are you trunking any VSAN across the link ?

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

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?

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:

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.

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.