IVR virtual domain in fcdomain domain-list interop mode 2 and 3

Today I was configuring an IVR scenerio that was pretty straight forward. Here is the summary:

I establish IVR between MDS1 and MDS2
MDS1 uses VSAN50 interop 2 attached to a Brocade PID0 switch on fc1/6
MDS2 uses VSAN50 interop 1 attached to a McData switch on fc1/6

VSAN 51 is used as a transit VSAN with proper vsan-topology setup:

MDS2# show ivr vsan-topology

AFID SWITCH WWN Active Cfg. VSANS Switch-Name
-------------------------------------------------------------------------
1 20:00:00:0d:ec:0e:b2:40 yes yes 50
2 20:00:00:0d:ec:0e:b2:40 yes yes 51
2 20:00:00:0d:ec:19:c9:00 * yes yes 51
3 20:00:00:0d:ec:19:c9:00 * yes yes 50

Total: 4 entries in active and configured IVR VSAN-Topology

On MDS1 I am seeing the virtual domain in the fcdomain domain-list. This normally would not happen unless you explicitly configure the ivr virtual-fcdomain-add command.  However this is added by SAN-OS in interop modes 2 and 3. This is known as RDI Mode.

Observe the following:

MDS1# show ivr virtual-fcdomain-add-status
IVR virtual domains are added to fcdomain list in VSANS: 50
Force Option : Off

I did not configure ivr virtual-fcdomain-add vsan 50, yet it’s behaving as if I did. ¬†It is automatically added by SAN-OS.

MDS1# show fcdomain domain-list vsan 50

Number of domains: 3
Domain ID WWN
--------- -----------------------
0x62(98) 20:32:00:0d:ec:0e:b2:41 [Local]
0x63(99) 10:00:00:60:69:20:28:97 [Principal]
0x6a(106) 10:00:08:00:88:30:01:8a

You can clearly see from the above output the virtual-domain of 0x6a being added to the fcdomain domain-list on MDS1.

MDS1# show ivr virtual-dom
VSAN # Domains IVR Virtual Domains
---- --------- ----------------------------------------------
50 1 106
51 2 99,106
---- --------- ----------------------------------------------

Now take a look at MDS2, which is behaving in a regular fashion since its in interop mode 1:

MDS2# show ivr virtual-fcdomain-add-status
IVR virtual domains are not added to fcdomain list
Force Option : Off
MDS2# show fcdomain domain-list vsan 50

Number of domains: 2
Domain ID WWN
--------- -----------------------
0x64(100) 20:32:00:0d:ec:19:c9:01 [Local]
0x6a(106) 10:00:08:00:88:30:01:8a [Principal]
MDS2# show ivr virtual-dom
VSAN # Domains IVR Virtual Domains
---- --------- ----------------------------------------------
50 1 99
51 2 99,106
---- --------- ----------------------------------------------

Thanks to Cisco TAC for pointing this behavior out to me. It’s documented in the Cisco MDS9000 Interoperability Configuration Guide

This entry was posted in CCIE Storage, Interop, IVR and tagged , , , . Bookmark the permalink.

16 Responses to IVR virtual domain in fcdomain domain-list interop mode 2 and 3

  1. Deepak says:

    Hi Brian…I am planning on taking my CCIE lab three weeks from now, i had a question on IVR in the above example.Is it possibile to have the host seen with its real fcid on the other side and vice-versa? i have been trying to configure this without any luck.please let me know

    Thanks in advance

    • brian says:

      Deepak,

      So I believe what your asking is can the node be reached with its “real” FCID on one side, and then also with its “virtual” FCID from somewhere else. The answer is yes. In reality, the node is always being communicated with its real FCID, as it won’t accept frames accept those addressed to itself, there is just translation happening. So long as where you are communicating from has a route in its tables to get there, it would work. Obviously if you do not see the domain from where you are trying to communicate, you can’t get there however, so just have to make sure you have a path.

  2. Deepak says:

    Actually my question was with overlapping domain IDs across with ivr-nat enabled.For example host (with real fcid 0x123456) and storage (with real fcid 0x126543) host-mds1–Transit–mds2-storage

    Is it possible to have the host seen with fcid of 0x123456 when you do show zoneset active vsan x on MDS2 and same is the case with storage seen with fcid of 0x126543 when you do show zoneset active vsan x on MDS1

    Thanks for your time

  3. brian says:

    I don’t believe it will do what you ask. You need to zone to whatever it can see, whether thats the real or the virtual. It requires various “show” commands to follow how the virtual is being mapped to the real, which is a bit of a PITA but its something you need to get good at for lab study.

  4. Deepak says:

    Thanks for the reply Brian.i have one more question on scheduler, not sure if this is the right place but let me give a shot

    Is it possible to schedule a job now and then run every mondays, for example:

    scheduler schedule name TEST
    job name TEST
    time start now repeat 2:2

    The above command would run the job now but will repeat every 2 days 2 hrs. I want my job to run now and every mondays.Is that possible? I have been trying this without any success.Let me know your ideas

    • brian says:

      Deepak,

      You should be able to accomplish this like so:

      scheduler schedule name TEST
      job name TEST
      time start now repeat weekly Mon:05:00

      This would start the command now, and repeat every Monday. Please let me know if this does what you like. I just reviewed the Command Reference and I agree its a bit lacking in giving thorough explanations of the scheduler.

  5. Deepak says:

    Brian….i get an error message , see below, not sure what am i missing

    mds4(config-schedule)# TIME start now repeat weekly mon:05:00
    ^
    % long command detected at ‘^’ marker.

    mds4(config-schedule)#

    Thanks in advance

    • brian says:

      What if you do it like:

      TIME start now repeat weekly 2:05:00

      in this syntax, 1=Sun, 2=Mon, etc. Cannot exceed 10 chars, which yours looks like 9………could be a bug because that should work.

  6. Deepak says:

    I am running 3.2(3a).Actually i dont see weekly when i do ?

    mds2(config-schedule)# time start now repeat weekly 2:2:2
    ^
    % long command detected at ‘^’ marker.

    mds2(config-schedule)# time start now repeat ?
    Interval {[[dd:]HH:]MM} dd,HH,MM are +ve integers (Max Size – 8)
    mds2(config-schedule)# time start now repeat

  7. Deepak says:

    sorry to bother you, dont meant to be a pain

    time start now repeat 7:00:00
    the above command will run every week from now

    my question is for example, today is wednesday, want a job to be run now and then every mondays, if i use the above command it will run now but every seven days (next wednesday)

  8. SA says:

    Any luck Brian?

    MDS1(config-schedule)# time start now repeat weekly 02:05:00
    ^
    % long command detected at ‘^’ marker.

    MDS1(config-schedule)#
    MDS1(config-schedule)# time start now repeat ?
    Interval {[[dd:]HH:]MM} dd,HH,MM are +ve integers (Max Size – 8)
    MDS1(config-schedule)# time start now repeat ?
    Interval {[[dd:]HH:]MM} dd,HH,MM are +ve integers (Max Size – 8)

  9. SA says:

    MDS1(config-schedule)# time start now repeat weekly Mon:05:00
    ^
    % long command detected at ‘^’ marker.

    MDS1(config-schedule)# time start now repeat weekly 02:05:00
    ^
    % long command detected at ‘^’ marker.

    MDS1(config-schedule)#
    MDS1(config-schedule)# time start now repeat ?
    Interval {[[dd:]HH:]MM} dd,HH,MM are +ve integers (Max Size – 8)

Leave a Reply