UNSOLVED
R
RashidMahamood
1 Rookie
•
18 Posts
0
7040
January 28th, 2015 06:00
Inter VSAN Routing- IVR
Dear Team,
I am going to configure the IVR. My Environment is mentioned below. So please let me know how to create the IVR between primary and DR site by using below inputs.
Production Site Fabric 1
- MDS 9710 and MDS 9222i ( FC ISL is created between two switch)
- Only two VSAN is created per switch VSAN 100 and VSAN 102
- VSAN 100 is used for production zoneset
- VSAN 102 is used for FCIP interface
- FCIP communication is working fine between two sites
Production Site Fabric 2
- MDS 9710 and MDS 9222i ( FC ISL is created between two switch)
- Only two VSAN is created per switch VSAN 200 and 202
- VSN 200 is used for production zoneset
- VSAN 202 is used for FCIP interface
- FCIP communication is working fine between two sites
DR site Fabric 1
- MDS 9710 and MDS 9222i ( FC ISL is created between two switch)
- Only two VSAN is created per switch VSAN 101 and VSAN 102
- VSAN 101 is used for production zoneset
- VSAN 102 is used for FCIP interface
- FCIP communication is working fine between two sites
DR Site FABRIC 2
- MDS 9710 and MDS 9222i ( FC ISL is created between two switch)
- Only two VSAN is created per switch VSAN 100 and VSAN 102
- VSAN 201 is used for production zoneset
- VSAN 202 is used for FCIP interface
- FCIP communication is working fine between two sites
All servers and hosts are connected to MDS 9710 series switch in both sites. MDS 9222i switch is used to create only for FCIP and IVR. So please let me know where i have to enable the IVR and what will be the IVR VSAN topology.
I wanted to configure IVR without NAT and IVR without auto config.
Do i need to enable the IVR feature in MDS9710 and MDS 9222i ? OR only i need to enable the IVR feature in MDS 9222i ?
Do i need to add all four switches from all FABRIC-1 to single IVR topology database. ?? OR only i need to add the MDS 9222i Switch WWN to IVR topology database ???
1913
0
Posted January 28th, 2015 06:00
================================================================
Configuration Command that i have created for Fabric-1
================================================================
ivr enable
ivr distribute
ivr vsan-topology database
autonomous-fabric-id 1 switch-wwn 20:00:00:2a:6a:db:53:00 vsan-ranges 100,102 --------->PR - MDS9710 switch wwn
autonomous-fabric-id 1 switch-wwn 20:00:00:2a:6a:ae:df:00 vsan-ranges 100,102 ---------->PR - MDS 9222i switch wwn
autonomous-fabric-id 1 switch-wwn 20:00:00:2a:6a:db:50:80 vsan-ranges 101-102 ----------->DR - MDS9710 switch wwn
autonomous-fabric-id 1 switch-wwn 20:00:00:2a:6a:ae:e2:c0 vsan-ranges 101-102 -----------> DR MDS9222i switch wwn
ivr commit
ivr vsan-topology activate
ivr commit
Do i need to configure more than above configuration ?? Do i need to run this configuration in all switches in same fabric at both production and DR (PRMDS9710 MDS 9222i AND DR MDS9710, MDS 9222i) ??
1913
0
Posted January 28th, 2015 06:00
1) NX-OS version ?
2) You can't create IVR without NAT anymore
3) VSANs that exist on 9710 also exist on 9222i ?
1913
0
Posted January 28th, 2015 06:00
MDS 9710 and MDS 9222i is running with 6.2.5.
VSAN exist on 9710 is also exist on 9222i.
1913
0
Posted January 28th, 2015 07:00
1913
0
Posted January 28th, 2015 07:00
The VSAN 102 in Fabric-1 and VSAN 202 in Fabric is used as Transit VSAN
1913
0
Posted January 28th, 2015 07:00
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.
1913
0
Posted January 28th, 2015 21:00
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
1914
0
Posted January 28th, 2015 21:00
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"
1848
0
Posted January 28th, 2015 22:00
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
dynamox
11 Legend
•
20419 Posts
•
87439 Points
1913
0
Posted January 28th, 2015 06:00
you need to use a transit VSAN, you don't want to merge fabrics between Prod and DR.