activeX1
1 Copper

SRDF and mirrorview over FCIP

Jump to solution

I have to configure SRDF and Mirrorview over FCIP on Cisco MDS 9513 with Cisco 18/4 FCIP module. I would like to understand do we need to move FA on VMAX or SP Front end port  on Clariion to FC port on FCIP blade. Is it possible to just create create an IVR zone between source FA on blade other than FCIP and target FA on NON-FCIP blade as well. Basically, is it mandatory to have RDF FA/SP Port on FCIP module. Please respond ASAP. Also Can I share SP port on Clariion for host allocation as well as for Mirrorview.

0 Kudos
1 Solution

Accepted Solutions
RRR
5 Osmium

Re: SRDF and mirrorview over FCIP

Jump to solution

I'd advise not to use host based storage access over the same links as the MirrorView or SRDF. Keep them separated from host access (use different VSANs).

Furthermore: don't create 1 large VSAN which stretches over the long ip line. If ip goes down, you will end up with 2 separated VSANs that can't see eachother. When the link comes abck up, you'll have a fabric merge, which can cause some delays (RSCN = Registered State Change Notifications). If now the link goes up-down-up-down-up-down-up, the RSCN process is interrupted each time the link goes down.

If you'd use a transit VSAN, no massive amounts of RSCNs will be triggered on the VSANs on either end, just of the ports that make up the link to the transit VSAN.

0 Kudos
9 Replies
dynamox
6 Thallium

Re: SRDF and mirrorview over FCIP

Jump to solution

FCIP service is fabric based so any port that is part of a VSAN that you configured in ivr topology can be zoned to remote switch over FCIP link. Best practise is not to use Mirrorview ports for host access.

0 Kudos
RRR
5 Osmium

Re: SRDF and mirrorview over FCIP

Jump to solution

Storage ports remain FC only. You need to create the FCIP config on both switches which will use the ip ports on your 18/4 blade (4, because you have 2 fabrics) and zone the storage ports you'd like to "see" eachother.

Example:

fcip enable

vsan database

vsan 500 name "VSAN0500_SRDF"

fcip profile 10

ip address 80.12.34.57

tcp max-bandwidth-mbps 800 min-available-bandwidth-mbps 800 round-trip-time-ms 1

tcp max-jitter 1

no in-order-guarantee vsan 500

fcdomain fcid persistent vsan 1

fcdomain priority 32 vsan 500

fcdomain domain 100 static vsan 500

fcdomain fcid persistent vsan 500

interface fcip10

use-profile 10

peer-info ipaddr 80.12.34.58

write-accelerator

ip-compression mode1

switchport trunk allowed vsan 500

zoneset distribute full vsan 500

zone name Z_001_002_FA13DA vsan 500

member pwwn 50:06:05:8e:52:b5:1a:dc

member pwwn 50:06:05:8e:52:b5:1b:dc

zone name Z_001_002_FA10DA vsan 500

member pwwn 50:06:05:8e:52:b5:1c:dc

member pwwn 50:06:05:8e:52:b5:1d:dc

zoneset name VFAB0201_SRDF vsan 500

member Z_001_002_FA13DA

member Z_001_002_FA10DA

zoneset activate name VFAB_500_SRDF vsan 500

interface mgmt0

switchport speed 100

ip address 192.168.1.221 255.255.255.0

interface GigabitEthernet1/1

ip address 80.12.34.57 255.255.255.240

0 Kudos
Highlighted
RRR
5 Osmium

Re: SRDF and mirrorview over FCIP

Jump to solution

Oh yeah, I forgot: best practice is not to use MV ports for anything else than MV, but you are free to override that advise and do it.

With SRDF on Symm you can't use these ports for anything else.

activeX1
1 Copper

Re: SRDF and mirrorview over FCIP

Jump to solution

Thanks RRR and dynamox for your replies. One more query is we have VSAN-100 and VSAN-200 at Site-A and VSAN-100/200 on Site-B switches as well which we'll be connecting through FCIP. once we have IVR enabled and FCIP connectivity would these two VSAN's merge in one VSAN like VSAN100 on SiteA and SiteB will be just one VSAN? I woule prefer to keep them saperate so that easier to manage. Is it going to be disruptive or non-disruptive. 

0 Kudos
dynamox
6 Thallium

Re: SRDF and mirrorview over FCIP

Jump to solution

i agree that since you have IVR functionality it's best to keep them separate and not let fabrics merge. If FCIP starts flopping, it would impact hosts/storage at both sites. So i would recommend that you create a transit VSAN at each site, that will be the only VSAN that's allowed to be trunk over your FCIP link. For systems that need to talk to each other over the link (SRDF/MirrorView /ports) you will be using IVR zoning. Take a look at VSAN 100/200 at each site and document their domain id:

sh fcdomain vsan 100

look for line that says "Current domain ID: 0xXXXX

make sure that vsan 100 and both sites have unique domain ids, that will allow you to use regular IVR ..otherwise you will have to use IVR-NAT which is more complicated. Let us know if you need help with configuring IVR topology ...RRR talks Cisco as his second language and i can help out as well

0 Kudos
Symmetrix_
2 Iron

Re: SRDF and mirrorview over FCIP

Jump to solution

Hello Dynamox,

Could you please clarify your statement “If FCIP starts flopping, it would impact hosts/storage at both sites” How?

Thanks,

0 Kudos
RRR
5 Osmium

Re: SRDF and mirrorview over FCIP

Jump to solution

2nd language ? Who, me ? Well, I had a little help from a working config I saved somewhere And this one worked just fine !

0 Kudos
RRR
5 Osmium

Re: SRDF and mirrorview over FCIP

Jump to solution

I'd advise not to use host based storage access over the same links as the MirrorView or SRDF. Keep them separated from host access (use different VSANs).

Furthermore: don't create 1 large VSAN which stretches over the long ip line. If ip goes down, you will end up with 2 separated VSANs that can't see eachother. When the link comes abck up, you'll have a fabric merge, which can cause some delays (RSCN = Registered State Change Notifications). If now the link goes up-down-up-down-up-down-up, the RSCN process is interrupted each time the link goes down.

If you'd use a transit VSAN, no massive amounts of RSCNs will be triggered on the VSANs on either end, just of the ports that make up the link to the transit VSAN.

0 Kudos
dynamox
6 Thallium

Re: SRDF and mirrorview over FCIP

Jump to solution

Symmetrix_ wrote:

Hello Dynamox,

Could you please clarify your statement “If FCIP starts flopping, it would impact hosts/storage at both sites” How?

Thanks,

what RRR said

0 Kudos