cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2016
Views
0
Helpful
16
Replies

Cisco MDS Vsan question

shankar85
Level 1
Level 1

Hi,

I have two Cisco 9509 mds switches, switch 1 and switch 2 interconnect via TE ports from each of the VSANs VSAN 1 and VSAN 2.

The physcial interface in the upper half of the switch 1 and switch 2 are part of VSAN 1 and bottom half is part of VSAN 2.

No IVR enabled in any of the switches.

we have host wwn cabled to switch 1 vsan 2 and storage port to switch2 vsan 2 .

I have performed the zoning between them and assigned luns to the host but host is unable to see them .

Is there a zoning issue here ?

could some one please clarify and help ?

Apologies for the repost as i'm unable to find the original one !!

Regards

16 Replies 16

Amit Singh
Cisco Employee
Cisco Employee

Please can you share the switch configs?

Do you see the initiator and target both in  " Show Flogi Database " ?

Have you activated the zoneset? What does " Show zone status " shows you?

Yes , The host is already zoned to SVC , and I'm trying to zone it with Hitchi VSP cha port.

Also the CHa port is zoned with another ESX host.

One point however I want to add here is when i go into hitachi vsp box, I'm not able to see the wwn's of this particular esx host whilst trying to create a host group

Hello

Your OP stated "we have host wwn cabled to switch 1 vsan 2 and storage port to switch2 vsan 2".  Is this the 1st host connected in that way? i.e. do you have any other hosts accessing storage across the ISL on vsan 2?

Answering Amit's questions will help here too.

Steven

Hi ,

No this is not the first host which is accessing the storage across the ISL .

The way we zone is host will access two storage ports which are connected locally to the switch and two ports from the second switch.

Yes I can find the wwn's in the Flogi database.

Please find output of the show zone status command..

Switch 1

VSAN: 1 default-zone: deny distribute: full Interop: default
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: disabled
Full Zoning Database :
    Zonesets:1  Zones:187 Aliases: 209
Active Zoning Database :
    Name: VSAN0001_ZoneSet  Zonesets:1  Zones:187
Status: Activation completed at 14:23:09 UTC Feb 10 2014

VSAN: 2 default-zone: deny distribute: full Interop: default
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: disabled
Full Zoning Database :
    Zonesets:1  Zones:180 Aliases: 210
Active Zoning Database :
    Name: VSAN0002_ZoneSet  Zonesets:1  Zones:186
Status: Activation completed at 15:52:48 UTC Feb  8 2014

Switch 2

VSAN: 1 default-zone: deny distribute: active only Interop: default
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: disabled
Full Zoning Database :
    Zonesets:1  Zones:187 Aliases: 209
Active Zoning Database :
    Name: VSAN0001_ZoneSet  Zonesets:1  Zones:187
Status: Activation completed at 14:23:09 UTC Feb 10 2014

VSAN: 2 default-zone: permit distribute: active only Interop: default
    mode: basic merge-control: allow
    session: none
    hard-zoning: enabled broadcast: disabled
Default zone:
    qos: none broadcast: disabled ronly: disabled
Full Zoning Database :
    Zonesets:1  Zones:187 Aliases: 214
Active Zoning Database :
    Name: VSAN0002_ZoneSet  Zonesets:1  Zones:187

OK it looks like you have a zone DB missmatch:

Switch 1, vsan 2:

Full Zoning Database :

    Zonesets:1  Zones:180 Aliases: 210

Active Zoning Database :

    Name: VSAN0002_ZoneSet  Zonesets:1  Zones:186

Status: Activation completed at 15:52:48 UTC Feb  8 2014

Switch 2, vsan 2:

Full Zoning Database :

    Zonesets:1  Zones:187 Aliases: 214

Active Zoning Database :

    Name: VSAN0002_ZoneSet  Zonesets:1  Zones:187

So, the zone DB's are different but most people configure full distribution.

Check that with: sh system default zone

Also, and more concerning is that the active zoneset is different.  switch 2 has one more zone.

This generally indicates an ISL problem OR a failure to sync the zoneset and then a powercut.  Either way, I'd expect to see NO ISL comms for that VSAN.

do a show int on the ISL and see if everything is up.

Hi ,

The zone DB mismatch is beacuse I have not created the zone of my host whihc is having this issue on one of the switches , hence it has one extra zone , but my understanding is that it shouldnt make any difference would it ?

Also from my past obsevation as well whilst trying to zone esx hosts with Hitachi VSP , sometimes we have to deactivate and reactivate the zone after the first time as i was told that it misses the flogi process.I have infact tried this as well and still no luck.

I have checked the comaptability guide for esx host HBa with VSP  and it shows it is compatible however not to the level of f/w, driver version though , I'm checking this in paralle with the vendor as well.

I can remove that one extra zone from the second switch if that would make any difference.

Interfaces are up

KFSW01# show int fc1/16
fc1/16 is trunking
    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
    Port WWN is 20:10:00:0d:ec:0d:bf:80
    Peer port WWN is 20:10:00:0d:ec:20:da:c0
    Admin port mode is auto, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 1
    Speed is 2 Gbps
    Transmit B2B Credit is 255
    Receive B2B Credit is 255
    Receive data field Size is 2112
    Beacon is turned off
    Trunk vsans (admin allowed and active) (1-2,30)
    Trunk vsans (up)                       (1-2,30)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             ()
    5 minutes input rate 885393648 bits/sec, 110674206 bytes/sec, 62890 frames/sec
    5 minutes output rate 701632024 bits/sec, 87704003 bytes/sec, 52179 frames/sec
      1025246443835 frames input, 1669566204487420 bytes
        0 discards, 0 errors
        0 CRC,  0 unknown class
        0 too long, 0 too short
      1018876249527 frames output, 1649070048270564 bytes
        0 discards, 0 errors
      0 input OLS, 0 LRR, 0 NOS, 0 loop inits
      0 output OLS, 0 LRR, 0 NOS, 0 loop inits
      255 receive B2B credit remaining
      255 transmit B2B credit remaining


KFSW01# show int fc7/16
fc7/16 is trunking
    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
    Port WWN is 21:90:00:0d:ec:0d:bf:80
    Peer port WWN is 21:90:00:0d:ec:20:da:c0
    Admin port mode is auto, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 2
    Speed is 2 Gbps
    Transmit B2B Credit is 255
    Receive B2B Credit is 255
    Receive data field Size is 2112
    Beacon is turned off
    Trunk vsans (admin allowed and active) (1-2,30)
    Trunk vsans (up)                       (1-2,30)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             ()
    5 minutes input rate 618134160 bits/sec, 77266770 bytes/sec, 46751 frames/sec
    5 minutes output rate 700446592 bits/sec, 87555824 bytes/sec, 52120 frames/sec
      1025988874215 frames input, 1662987713982888 bytes
        0 discards, 0 errors
        0 CRC,  0 unknown class
        0 too long, 0 too short
      1019009123607 frames output, 1649282572497460 bytes
        0 discards, 0 errors
      0 input OLS, 0 LRR, 0 NOS, 0 loop inits
      0 output OLS, 0 LRR, 0 NOS, 0 loop inits
      255 receive B2B credit remaining
      255 transmit B2B credit remaining

fc1/16 is trunking
    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
    Port WWN is 20:10:00:0d:ec:20:da:c0
    Peer port WWN is 20:10:00:0d:ec:0d:bf:80
    Admin port mode is auto, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 1
    Speed is 2 Gbps
    Transmit B2B Credit is 255
    Receive B2B Credit is 255
    Receive data field Size is 2112
    Beacon is turned off
    Trunk vsans (admin allowed and active) (1-2,30)
    Trunk vsans (up)                       (1-2,30)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             ()
    5 minutes input rate 680360504 bits/sec, 85045063 bytes/sec, 50795 frames/sec
    5 minutes output rate 909358920 bits/sec, 113669865 bytes/sec, 64173 frames/sec
      18446741314997488700 frames input, 18441939833066048856 bytes
        0 discards, 18446744073709551613 errors
        0 CRC,  0 unknown class
        0 too long, 0 too short
      18446741319935123312 frames output, 18441988913141664092 bytes
        18446744073709551533 discards, 0 errors
      18446744073709551613 input OLS, 18446744073709551611 LRR, 0 NOS, 18446744073709551598 loop inits
      18446744073709551610 output OLS, 18446744073709551613 LRR, 18446744073709551614 NOS, 18446744073709551613 loop inits
      255 receive B2B credit remaining
      254 transmit B2B credit remaining

KFSW02# show int fc7/16
fc7/16 is trunking
    Hardware is Fibre Channel, SFP is short wave laser w/o OFC (SN)
    Port WWN is 21:90:00:0d:ec:20:da:c0
    Peer port WWN is 21:90:00:0d:ec:0d:bf:80
    Admin port mode is auto, trunk mode is on
    snmp link state traps are enabled
    Port mode is TE
    Port vsan is 2
    Speed is 2 Gbps
    Transmit B2B Credit is 255
    Receive B2B Credit is 255
    Receive data field Size is 2112
    Beacon is turned off
    Trunk vsans (admin allowed and active) (1-2,30)
    Trunk vsans (up)                       (1-2,30)
    Trunk vsans (isolated)                 ()
    Trunk vsans (initializing)             ()
    5 minutes input rate 693032224 bits/sec, 86629028 bytes/sec, 51656 frames/sec
    5 minutes output rate 621006912 bits/sec, 77625864 bytes/sec, 46975 frames/sec
      18446738277510559587 frames input, 18437009382560591856 bytes
        0 discards, 18446744073709551601 errors
        0 CRC,  0 unknown class
        0 too long, 0 too short
      18446738182041962307 frames output, 18436662913929808892 bytes
        18446744073709551319 discards, 0 errors
      0 input OLS, 18446744073709551612 LRR, 0 NOS, 18446744073709551608 loop inits
      18446744073709551613 output OLS, 18446744073709551614 LRR, 0 NOS, 18446744073709551614 loop inits
      255 receive B2B credit remaining
      252 transmit B2B credit remaining

Hi

The zone DB mismatch is not because of that.  Every conncted switch participating in a particular VSAN should have EXACTLY the same active zone DB,  If they don't there is a synchronisation problem.

As for deactivating/activating the zone, is this so it will appear on the storage array?  I if so, this is normal.  When the host performs a flogi and a scan, if there is no zone in place then the array will never see it scanning.  Normally an FC rescan or reboot of the host is all thats needed.

What was the output of "sh system default zone"?  If that is saying full distribution, then the full zone database should also be the same.

Hi ,

Below is the output of the command you had requested.

system default zone default-zone deny

system default zone distribute active only

Betwn , I got in touch with vendor yesterday and they werent able to comment much abou this as they say nothing exaclty is happening with regards to this inside of the VSP, in terms of compatability all they were able to confirm is HBA is compatible.

Thanks

Shankar

Hello

OK,  I think you need to log a call with you support provider.  This is getting a bit too complex for this method of support

Full zone distribution should really be enabled, but you have your 2 vsans on switch 2 set to active only, when the ones on switch 1 are full - they should be the same.

Get that sorted out and then the full & active zone databses will be the same on poth switches.  This will probably fix your issue.

Sorry , I should have been more clear , but the i checked both the switches and both are the same in terms of the following command.

Switch 1 & 2.

system default zone default-zone deny

system default zone distribute active only

Thanks

In addition to which , VSAN 1 will be part of switch 1 and 2 and VSAN 2 will be part of Switch 1 & 2 as we have defined the Physical interfaces in that manner which is top half in switch 1 & 2 as VSAN 1 and bottom half is VSAN 2.

So say if I were to do zoning for host connected in VSAN 1 switch 1 with a storage port in VSAN 2 switch 2 I'd be selecting VSAN switch 1 zoneset to create the necessary zoning and activate the same.

Thanks

Shankar

it would be nice if you could post a diagram of your configuration. Remember devices needs to be in the same VSAN to talk to each other, if they are not, you will have to use IVR (which requires additional license)

@dynamoxxx

@dynamoxxx

PFA diagramdiagram.JPG

based on that diagram, they way things are right now you would have to use IVR.  If VSAN 2 is trunked between both switches, you could also move Host to VSAN 2 (unless it's already using resources in VSAN 1)

@dynamoxxx

@dynamoxxx
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: