Inter VSAN Routing- IVR

you need to use a transit VSAN, you don't want to merge fabrics between Prod and DR.

1) NX-OS version ?

2) You can't create IVR without NAT anymore

3) VSANs that exist on 9710 also exist on 9222i ?

MDS 9710 and MDS 9222i  is running with  6.2.5.

VSAN exist on 9710 is  also exist on 9222i.

The VSAN 102  in Fabric-1  and VSAN 202 in Fabric is used as Transit VSAN

thank you for the picture, i am a visual person

so you only need to enable IVR on 9222i(s) as they are the ones doing the "routing".

vsan topology will look like this

autonomous-fabric-id 1 switch-wwn 20:00:00:0d:ec:f0:17:00 vsan-ranges 100,102

autonomous-fabric-id 1 switch-wwn 20:00:00:0d:ec:f0:19:00 vsan-ranges 101,102

the only VSAN that needs to be trunked on your FCIP links is VSAN 102.

So from your comments, i can believe that, i don't need  to create the VSAN 102 in MDS 9710.  

while creating VSAN topology  i just need to mention

autonomous-fabric-id 1 switch-wwn ProductionMDS9222iwwn  vsan-ranges 100,102

autonomous-fabric-id 1 switch-wwn DRMDS9222iWWN vsan-ranges 101,102

if i activated the above IVR topology and if i created the Required IVR zoneset ,Storage array connected to Production Site MDS9710 will be able  to replicate Storage array connected to DR Site MDS 9710 .. am i right ??

And you have mentioned that, IVR NAT only possible. So do i need to configure something additional to work the IVR NAT ???

Thank you for your valid inputs 

RashidABC wrote: So from your comments, i can believe that, i don't need  to create the VSAN 102 in MDS 9710.

correct, no need to create transit VSAN on 9710.

RashidABC wrote: while creating VSAN topology  i just need to mention autonomous-fabric-id 1 switch-wwn ProductionMDS9222iwwn  vsan-ranges 100,102 autonomous-fabric-id 1 switch-wwn DRMDS9222iWWN vsan-ranges 101,102

correct, so these are our steps (actual commands in bold):

1) ivr enable (run it both both 9222i)

2) ivr distribute (run it on both 9222i)

3) create ivr topology, command below (run it on one 9222i)

autonomous-fabric-id 1 switch-wwn ProductionMDS9222iwwn  vsan-ranges 100,102

autonomous-fabric-id 1 switch-wwn DRMDS9222iWWN vsan-ranges 101,102

4) ivr vsan-topology activate (run it on one 9222i)

5) ivr commit (run it on one switch)

At this point you can run show ivr vsan-topology on both 9222i and you should see the same thing.

RashidABC wrote: if i activated the above IVR topology and if i created the Required IVR zoneset ,Storage array connected to Production Site MDS9710 will be able  to replicate Storage array connected to DR Site MDS 9710 .. am i right ??

yes, at this point you can create IVR zones that will allow WWN in VSAN 100 talk to WWN in VSAN 101.

At the version you are running on IVR-NAT should be enabled by default, you can verify

sh running-config | grep -i NAT

This command should return "ivr nat"

i don't know how to thank you ... thank you so much.

Dear Dynamox is it your real name ??

i will keep updated, if there is any problem,   Can you please verify the FCIP link i created ?

Once FCIP is configured .. i  am able to ping between FCIP interfaces PR and DR

=================================================================

PR SIDE FCIP CONFIGURATION

=================================================================

config t

feature fcip

interface GigabitEthernet1/1

ip address 172.30.66.31 255.255.255.0

no shut

fcip profile 10

ip address 172.30.66.31

exit

interface fcip 10

use-profile 10

peer-info ipaddr 172.29.66.31

no shutdown

ip route 172.29.66.0 255.255.255.0 172.30.66.254

ip route 172.29.66.0 255.255.255.0 172.30.66.254 interface GigabitEthernet1/1

show interface fcip 10

show ips stats tcp interface gigabitethernet 1/1

show run interface fcip10

config t

vsan database

vsan 102

vsan 102 interface fcip10

copy running-configuration startup-configuration

===============================================================

DR SIDE FCIP CONFIGURATION

===============================================================

config t

feature fcip

interface GigabitEthernet1/1

ip address 172.29.66.31 255.255.255.0

no shut

fcip profile 10

ip address 172.29.66.31

exit

interface fcip 10

use-profile 10

peer-info ipaddr 172.30.66.31

no shutdown

ip route 172.30.66.0 255.255.255.0 172.29.66.254

ip route 172.30.66.0 255.255.255.0 172.29.66.254 interface GigabitEthernet1/1

show interface fcip 10

show ips stats tcp interface gigabitethernet 1/1

show run interface fcip10

config t

vsan database

vsan 102

vsan 102 interface fcip10

exit

copy running-configuration startup-configuration

=====================================================

Just verify and provide your valid inputs

i don't have hands on experience with FCIP but if you can ping DR datacenter interface you are good.

do i need to enable IVR on all  MDS 9710 series switches ??

Note : All hosts and storage arrays are connected to MDS 9710

Do i need to add MDS 9710 series switches to ivr vsan-topology database ?

in which switch i have to create the IVR zones and IVR Zoneset ?

Sorry.

Tomorrow i will post the complete configuration output to here.. i hope you can verify it

==============================================================================

Initially i did as below. Fabric-1  PR MDS 9222i

==============================================================================

ivr enable

ivr distribute

ivr vsan-topology database

autonomous-fabric-id 1 switch-wwn 20:00:00:2a:6a:ae:df:00 vsan-ranges 100,102 ----> PR MDS 9222i (Here 102 is transit VSAN and VSAN 100 is production VSAN that exist on MDS 9710 and MDS 9222i)

autonomous-fabric-id 1 switch-wwn 20:00:00:2a:6a:ae:e2:c0 vsan-ranges 101-102  ----> DR MDS 9222i (Here 102 is transit VSAN and VSAN 101 is production VSAN that exist on MDS 9710 and MDS 9222i)

ivr vsan-topology activate

ivr commit

============================================================================

in the above scenario, where i have to add ivr zone and ivr zoneset ???

what exactly was not working ?

i don't use auto for topology, i like to be very specific which switches/VSANs participate in IVR topology.

today  i tried the method you said. And it was not working.

Once i enable IVR feature in all MDS 9710 series it was working.

Today what i did is

PR and DR MDS 9710 switch

• feature ivr
• ivr enable
• ivr distribute

PR and DR MDS 9222 i

• feature ivr
• ivr enable
• ivr distribute

PR MDS 9222i

• ivr enable
• ivr vsan-topology auto
• ivr commit
• show ivr vsan topology active   ----> result was show vsan topoloy is active in all switches including MDS 9710

============================================

if  ivr vsan-topology create using auto option "   ivr vsan-topology auto " , do i need to configure some extra configuration ??