Menu déroulant pour mobile
10 February 2015 | Written by Nicolas Michel | Published in Data Center
Usually people are blogging on a certain topic because they want to share they knowledge with a certain protocol or product.
Today I ll take another approach with that fact and I will actually do the exact opposite. I have an issue with ISLB which allows load balancing for my iSCSI sessions. Today I will elaborate each steps needed to make it work. I have failed this configuration a LOT of time and I have followed the same steps over and over. I decided to make a blogpost about it to keep track of what I should do next time I want to configure it.
I did not play with VRRP yet but this can be an idea for a following blogpost.
The topology is the same as in my previous blog posts related to the MDS.
The difference here is that both MDS will have an iSCSI interface bound to their gigabit interface. (iscsi 1/1 mapped to gig 1/1).
I will start from scratch and setup the infrastructure:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 |
MDS01 ===== MDS-01(config)# vsan database MDS-01(config-vsan-db)# vsan 10 MDS-01(config-vsan-db)# vsan 10 interface fc1/5 MDS-01(config)# fcdomain domain 0x11 preferred vsan 10 MDS-01(config)# fcdomain priority 1 vsan 10 MDS-01(config)# int fc1/5 MDS-01(config-if)# switchport mode FL MDS-01(config-if)# switchport speed 2000 MDS-01(config-if)# no shut MDS-01(config)# int po10 MDS-01(config-if)# channel mode active MDS-01(config-if)# switchport rate dedicated MDS-01(config-if)# switch mode E MDS-01(config)# int fc1/1-2 MDS-01(config-if)# no shut MDS-01(config-if)# fcdomain restart disruptive vsan 10 MDS-01# show flogi database -------------------------------------------------------------------------------- INTERFACE VSAN FCID PORT NAME NODE NAME -------------------------------------------------------------------------------- fc1/5 10 0x110072 21:00:00:18:62:8d:e8:b7 20:00:00:18:62:8d:e8:b7 Total number of flogi = 1. MDS02 ===== MDS-02(config)# vsan database MDS-02(config-vsan-db)# vsan 10 MDS-02(config)# fcdomain domain 0x22 preferred vsan 10 MDS-02(config)# fcdomain priority 2 vsan 10 MDS-02(config)# interface po10 MDS-02(config-if)# channel mode active MDS-02(config-if)# switchport rate-mode dedicated MDS-02(config-if)# switch mode E MDS-02(config)# int fc1/1-2 MDS-02(config-if)# channel-group 10 force MDS-02(config-if)# no shut MDS-02(config-if)# fcdomain restart disruptive vsan 10 MDS-02(config)# show fcns database VSAN 10: -------------------------------------------------------------------------- FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE -------------------------------------------------------------------------- 0x110072 NL 21:00:00:18:62:8d:e8:b7 scsi-fcp:target Total number of entries = 1 |
The outpout above prove us that the JBOD has registered to the fabric and that VSAN 10 is running on the E port between MDS01 and MDS02. Another proof is that the FCNS commands on MDS02 has the JBOD PWWN in its database.
Now we will setup Device-alias, we will activate a test zoneset on vsan 10 because ISLB requires an already active zoneset if you want to use the auto zone feature. If you do NOT have an active zone, you will have to manually perform the zoning configuration.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 |
Device-alias configuration on MDS01 ------------------------------------ MDS-01(config)# device-alias mode enhanced MDS-01(config)# device-alias commit MDS-01(config)# device-alias database MDS-01(config-device-alias-db)# device-alias name JBOD pwwn 21:00:00:18:62:8d:e8:b7 MDS-01(config-device-alias-db)# device-alias name TEST pwwn 20:00:00:00:00:00:00:01 MDS-01(config-device-alias-db)# device-alias name TEST2 pwwn 20:00:00:00:00:00:00:02 MDS-01(config)# device-alias commit MDS-02# show device-alias database device-alias name JBOD pwwn 21:00:00:18:62:8d:e8:b7 device-alias name TEST pwwn 20:00:00:00:00:00:00:01 device-alias name TEST2 pwwn 20:00:00:00:00:00:00:02 Total number of entries = 3 Zoning Configuration for the test zoneset ----------------------------------------- MDS-01(config)# zone mode enhanced vsan 10 WARNING: This command would distribute the zoning database of this switch throughout the fabric. Do you want to continue? (y/n) [n] y Set zoning mode command initiated. Check zone status MDS-01(config)# zoneset name VSAN10 vsan 10 MDS-01(config-zoneset)# zone name TEST MDS-01(config-zoneset-zone)# member device-alias TEST MDS-01(config-zoneset-zone)# member device-alias TEST2 MDS-01(config)# zoneset activate name VSAN10 vsan 10 Enhanced zone session has been created. Please 'commit' the changes when done. MDS-01(config)# zone commit vsan 10 Commit operation initiated. Check zone status MDS-02# show zoneset active zoneset name VSAN10 vsan 10 zone name TEST vsan 10 device-alias TEST device-alias TEST2 MDS-02# sh run | sec zone zone mode enhanced vsan 10 zone broadcast enable vsan 10 zone name TEST vsan 10 member device-alias TEST member device-alias TEST2 zoneset name VSAN10 vsan 10 member TEST zoneset activate name VSAN10 vsan 10 do clear zone database vsan 10 zone name TEST vsan 10 member device-alias TEST member device-alias TEST2 zoneset name VSAN10 vsan 10 member TEST zone commit vsan 10 |
Now we can start our ISLB configuration. Again we will first configure the infrastructure and check that both iSCSI interfaces are reachable from the L2 domain.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 |
MDS01 ----- MDS-01(config)# feature iscsi MDS-01(config)# iscsi enable module 1 MDS-01(config)# int iscsi1/1 MDS-01(config-if)# no shut MDS-01(config)# int gig1/1 MDS-01(config-if)# ip address 172.16.130.51 255.255.255.0 MDS-01(config-if)# no shut MDS-01(config)# islb distribute MDS-01(config)# show islb status iSLB Distribute: Enabled iSLB CFS Session: Does not exist Number of load balanced VRRP groups: 0 Number of load-balanced initiators: 0 MDS02 ----- MDS-02(config)# feature iscsi MDS-02(config)# iscsi enable module 1 MDS-02(config)# int iscsi1/1 MDS-02(config-if)# no shut MDS-02(config-if)# int gi1/1 MDS-02(config-if)# ip add 172.16.130.52 255.255.255.0 MDS-02(config-if)# no shut MDS-02(config)# islb distribute MDS-02(config)# show islb status iSLB Distribute: Enabled iSLB CFS Session: Does not exist Number of load balanced VRRP groups: 0 Number of load-balanced initiators: 0 Servers reachability to the iSCSI MDS ------------------------------------- C:\Users\Administrator>ping 172.16.130.51 Pinging 172.16.130.51 with 32 bytes of data: Reply from 172.16.130.51: bytes=32 time<1ms TTL=255 Reply from 172.16.130.51: bytes=32 time<1ms TTL=255 Reply from 172.16.130.51: bytes=32 time<1ms TTL=255 Reply from 172.16.130.51: bytes=32 time<1ms TTL=255 Ping statistics for 172.16.130.51: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Users\Administrator>ping 172.16.130.52 Pinging 172.16.130.52 with 32 bytes of data: Reply from 172.16.130.52: bytes=32 time<1ms TTL=255 Reply from 172.16.130.52: bytes=32 time<1ms TTL=255 Reply from 172.16.130.52: bytes=32 time<1ms TTL=255 Reply from 172.16.130.52: bytes=32 time<1ms TTL=255 Ping statistics for 172.16.130.52: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms |
ISLB configuration can now start and you will see it is very brief:
We first need to check the IQN of our servers.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 |
ISLB configuration will be done on MDS01 and distributed to the fabric ====================================================================== MDS-01(config)# islb initiator name iqn.1991-05.com.microsoft:srvdc01.vpackets.local MDS-01(config-islb-init)# static nWWN system-assign MDS-01(config-islb-init)# static pWWN system-assign 2 MDS-01(config-islb-init)# target device-alias JBOD MDS-01(config-islb-init)# zonename SERVER01_TO_JBOD MDS-01(config-islb-init)# vsan 10 MDS-01(config)# islb initiator name iqn.1991-05.com.microsoft:srvwin2008.vpackets.local MDS-01(config-islb-init)# static nWWN system-assign MDS-01(config-islb-init)# static pWWN system-assign 2 MDS-01(config-islb-init)# target device-alias JBOD MDS-01(config-islb-init)# zonename SERVER02_TO_JBOD MDS-01(config-islb-init)# vsan 10 MDS-01(config)# show islb pending-diff +islb initiator name iqn.1991-05.com.microsoft:srvdc01.vpackets.local + static nWWN 21:01:00:0d:ec:71:f1:42 + static pWWN 21:02:00:0d:ec:71:f1:42 + static pWWN 21:03:00:0d:ec:71:f1:42 + vsan 10 + zonename SERVER01_TO_JBOD + target device-alias JBOD vsan 10 +islb initiator name iqn.1991-05.com.microsoft:srvwin2008.vpackets.local + static nWWN 21:04:00:0d:ec:71:f1:42 + static pWWN 21:05:00:0d:ec:71:f1:42 + static pWWN 21:06:00:0d:ec:71:f1:42 + vsan 10 + zonename SERVER02_TO_JBOD + target device-alias JBOD vsan 10 MDS-01(config)# islb commit ZONE CONFIGURATION ------------------ DS-01(config)# show zone active zone name TEST vsan 10 device-alias TEST device-alias TEST2 zone name ips_zone_SERVER01_TO_JBOD vsan 10 symbolic-nodename iqn.1991-05.com.microsoft:srvdc01.vpackets.local * fcid 0x110072 [pwwn 21:00:00:18:62:8d:e8:b7] [JBOD] zone name ips_zone_SERVER02_TO_JBOD vsan 10 symbolic-nodename iqn.1991-05.com.microsoft:srvwin2008.vpackets.local * fcid 0x110072 [pwwn 21:00:00:18:62:8d:e8:b7] [JBOD] INITIATOR CONFIGURATION ----------------------- MDS-01(config)# show islb initiator configured iSCSI Node name is iqn.1991-05.com.microsoft:srvdc01.vpackets.local Member of vsans: 10 Node WWN is 21:01:00:0d:ec:71:f1:42 No. of PWWN: 2 Port WWN is 21:02:00:0d:ec:71:f1:42 Port WWN is 21:03:00:0d:ec:71:f1:42 Configured node (iSLB) Zone Name for initiator targets: SERVER01_TO_JBOD Load Balance Metric: 1000 Number of Initiator Targets: 1 Initiator Target: iqn.1987-05.com.cisco:05.998903be49c6a394da74a656d22c52da.21000018628de8b7 Port WWN 21:00:00:18:62:8d:e8:b7 [JBOD] Primary PWWN VSAN 10 Zoning support is enabled Trespass support is disabled Revert to primary support is disabled iSCSI Node name is iqn.1991-05.com.microsoft:srvwin2008.vpackets.local Member of vsans: 10 Node WWN is 21:04:00:0d:ec:71:f1:42 No. of PWWN: 2 Port WWN is 21:05:00:0d:ec:71:f1:42 Port WWN is 21:06:00:0d:ec:71:f1:42 Configured node (iSLB) Zone Name for initiator targets: SERVER02_TO_JBOD Load Balance Metric: 1000 Number of Initiator Targets: 1 Initiator Target: iqn.1987-05.com.cisco:05.f7712ff54520690f04b3a2edacfe7586.21000018628de8b7 Port WWN 21:00:00:18:62:8d:e8:b7 [JBOD] Primary PWWN VSAN 10 Zoning support is enabled Trespass support is disabled Revert to primary support is disabled |
The configuration has been commited and MDS02 should have the ISLB configuration and the zoning configured on it:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 |
MDS-02(config)# show zone active zone name TEST vsan 10 device-alias TEST device-alias TEST2 zone name ips_zone_SERVER01_TO_JBOD vsan 10 symbolic-nodename iqn.1991-05.com.microsoft:srvdc01.vpackets.local * fcid 0x110072 [pwwn 21:00:00:18:62:8d:e8:b7] [JBOD] zone name ips_zone_SERVER02_TO_JBOD vsan 10 symbolic-nodename iqn.1991-05.com.microsoft:srvwin2008.vpackets.local * fcid 0x110072 [pwwn 21:00:00:18:62:8d:e8:b7] [JBOD] MDS-02(config)# show islb initiator configured iSCSI Node name is iqn.1991-05.com.microsoft:srvdc01.vpackets.local Member of vsans: 10 Node WWN is 21:01:00:0d:ec:71:f1:42 No. of PWWN: 2 Port WWN is 21:02:00:0d:ec:71:f1:42 Port WWN is 21:03:00:0d:ec:71:f1:42 Configured node (iSLB) Zone Name for initiator targets: SERVER01_TO_JBOD Load Balance Metric: 1000 Number of Initiator Targets: 1 Initiator Target: iqn.1987-05.com.cisco:05.998903be49c6a394da74a656d22c52da.21000018628de8b7 Port WWN 21:00:00:18:62:8d:e8:b7 [JBOD] Primary PWWN VSAN 10 Zoning support is enabled Trespass support is disabled Revert to primary support is disabled iSCSI Node name is iqn.1991-05.com.microsoft:srvwin2008.vpackets.local Member of vsans: 10 Node WWN is 21:04:00:0d:ec:71:f1:42 No. of PWWN: 2 Port WWN is 21:05:00:0d:ec:71:f1:42 Port WWN is 21:06:00:0d:ec:71:f1:42 Configured node (iSLB) Zone Name for initiator targets: SERVER02_TO_JBOD Load Balance Metric: 1000 Number of Initiator Targets: 1 Initiator Target: iqn.1987-05.com.cisco:05.f7712ff54520690f04b3a2edacfe7586.21000018628de8b7 Port WWN 21:00:00:18:62:8d:e8:b7 [JBOD] Primary PWWN VSAN 10 Zoning support is enabled Trespass support is disabled Revert to primary support is disabled |
All is all right here and none of the iSCSI initiator have yet logged in the fabric:
|
1 2 3 4 5 6 7 8 |
MDS-02(config)# show fcns database VSAN 10: -------------------------------------------------------------------------- FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE -------------------------------------------------------------------------- 0x110072 NL 21:00:00:18:62:8d:e8:b7 scsi-fcp:target [JBOD] |
Let’s now activate debugs on both switches and try to initiate a Fabric Login from the iSCSI initiators (Server 01 first then Server 02)
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 |
MDS-01(config)# 2015 Feb 9 22:51:25.827731 ips: Session Create (init-name:[iqn.1991-05.com.microsoft:srvdc01.vpackets.local] tgt-name:[] init-alias:[] ISID:[400001370000] indx:[0x02000000] init_ip:[172.16.130.10] 2015 Feb 9 22:51:25.830536 ips: Sending add vsan 10 request for port(0b000000) 2015 Feb 9 22:51:25.833420 ips: Sending flogi request for iscsi-if-index 0b000000, vsan 10 nwwn 21:02:00:0d:ec:71:f1:42 pwwn 21:02:00:0d:ec:71:f1:42 2015 Feb 9 22:51:25.850679 ips: Received NS entry change event 0, vsan_id 10, flags 0xa8e 2015 Feb 9 22:51:25.850938 ips: Registering with name server fcid 00110100 vsan 10 nwwn 21:02:00:0d:ec:71:f1:42 pwwn 21:02:00:0d:ec:71:f1:42, init_ip: 172.16.130.10 2015 Feb 9 22:51:25.866317 ips: Received NS entry change event 2, vsan_id 10, flags 0x4150 2015 Feb 9 22:51:25.867215 ips: Session Create Response: Init: node_name iqn.1991-05.com.microsoft:srvdc01.vpackets.local init_name iqn.1991-05.com.microsoft:srvdc01.vpackets.local init-nwwn 00:00:00:00:00:00:00:00 init-pwwn 00:00:00:00:00:00:00:00 init-fcid 0 isid 400001370000pgt 12288 num_auth method 2 nodeIn 2015 Feb 9 22:51:25 MDS-01 %IPS-SLOT1-5-ISCSI_CONN_UP: GigabitEthernet1/1: iSCSI session up from initiator iqn.1991-05.com.microsoft:srvdc01.vpackets.local alias ip 172.16.130.10 to target Discovery 2015 Feb 9 22:51:25 MDS-01 %IPS-SLOT1-5-ISCSI_SB_GET_TGT: iSCSI SB get 1 targets, initiator iqn.1991-05.com.microsoft:srvdc01.vpackets.local alias ip 172.16.130.10 2015 Feb 9 22:51:25.875128 ips: Session Destroy node-name:[iqn.1991-05.com.microsoft:srvdc01.vpackets.local] init-name:[iqn.1991-05.com.microsoft:srvdc01.vpackets.local] tgt-name:[]ISID:[400001370000] indx:[0x02000000] failure-code:[1] 2015 Feb 9 22:51:25.875446 ips: Session destroy response status 0 for init_name:[iqn.1991-05.com.microsoft:srvdc01.vpackets.local] target_name:[] isid:[400001370000] sent 2015 Feb 9 22:51:25 MDS-01 %IPS-SLOT1-5-ISCSI_CONN_DOWN: GigabitEthernet1/1: iSCSI session down from initiator iqn.1991-05.com.microsoft:srvdc01.vpackets.local alias ip 172.16.130.10 to target Discovery, reason: client send iscsi logout 2015 Feb 9 22:51:25.877951 ips: Session Create (init-name:[iqn.1991-05.com.microsoft:srvdc01.vpackets.local] tgt-name:[iqn.1987-05.com.cisco:05.998903be49c6a394da74a656d22c52da.21000018628de8b7] init-alias:[] ISID:[400001370000] indx:[0x02000000] init_ip:[172.16.130.10] 2015 Feb 9 22:51:25.878836 ips: Querying NS for target pwwn 21:00:00:18:62:8d:e8:b7 vsan 10 filter fcid 00110100 2015 Feb 9 22:51:25.880067 ips: NS target response vsan:[10] fcid:[00110072] for target pwwn 21:00:00:18:62:8d:e8:b7 2015 Feb 9 22:51:25.880623 ips: Session Create Response: Init: node_name iqn.1991-05.com.microsoft:srvdc01.vpackets.local init_name iqn.1991-05.com.microsoft:srvdc01.vpackets.local init-nwwn 21:00:00:18:62:8d:e8:b7 init-pwwn 21:00:00:18:62:8d:e8:b7 init-fcid 110100 isid 400001370000pgt 12288 num_auth method 2 n 2015 Feb 9 22:51:25 MDS-01 %IPS-SLOT1-5-ISCSI_CONN_UP: %$VSAN 10%$ GigabitEthernet1/1: iSCSI session up from initiator iqn.1991-05.com.microsoft:srvdc01.vpackets.local alias ip 172.16.130.10 to target iqn.1987-05.com.cisco:05.998903be49c6a394da74a656d22c52da.21000018628de8b7 MDS-01(config)# show flogi database -------------------------------------------------------------------------------- INTERFACE VSAN FCID PORT NAME NODE NAME -------------------------------------------------------------------------------- fc1/5 10 0x110072 21:00:00:18:62:8d:e8:b7 20:00:00:18:62:8d:e8:b7 [JBOD] iscsi1/1 10 0x110100 21:02:00:0d:ec:71:f1:42 21:01:00:0d:ec:71:f1:42 Total number of flogi = 2. MDS-02(config)# show fcns database VSAN 10: -------------------------------------------------------------------------- FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE -------------------------------------------------------------------------- 0x110072 NL 21:00:00:18:62:8d:e8:b7 scsi-fcp:target [JBOD] 0x110100 N 21:02:00:0d:ec:71:f1:42 (Cisco) scsi-fcp:init isc..w MDS-01(config)# show islb initiator iSCSI Node name is iqn.1991-05.com.microsoft:srvdc01.vpackets.local Initiator ip addr (s): 172.16.130.10 iSCSI alias name: Configured node (iSLB) Node WWN is 21:01:00:0d:ec:71:f1:42 (configured) Member of vsans: 10 Number of Initiator Targets: 1 Initiator Target: iqn.1987-05.com.cisco:05.998903be49c6a394da74a656d22c52da.21000018628de8b7 * Port WWN 21:00:00:18:62:8d:e8:b7 [JBOD] Primary PWWN VSAN 10 Zoning support is enabled Trespass support is disabled Revert to primary support is disabled Number of Virtual n_ports: 1 Virtual Port WWN is 21:02:00:0d:ec:71:f1:42 (configured) Interface iSCSI 1/1, Portal group tag: 0x3000 VSAN ID 10, FCID 0x110100 |
MDS01 has performed a FLOGI onto itself on the VSAN10 and it has been mapped to interface iSCSI 1/1.
We can also see that the initiator has been correctly mapped to the JBOD
Let’s now try with server 02
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 |
MDS-02(config)# 2015 Feb 9 23:01:43.102494 ips: Session Create (init-name:[iqn.1991-05.com.microsoft:srvwin2008.vpackets.local] tgt-name:[] init-alias:[] ISID:[400001370000] indx:[0x02000000] init_ip:[172.16.130.11] 2015 Feb 9 23:01:43.105270 ips: Sending add vsan 10 request for port(0b000000) 2015 Feb 9 23:01:43.108254 ips: Sending flogi request for iscsi-if-index 0b000000, vsan 10 nwwn 21:05:00:0d:ec:71:f1:42 pwwn 21:05:00:0d:ec:71:f1:42 2015 Feb 9 23:01:43.124427 ips: Received NS entry change event 0, vsan_id 10, flags 0xa8e 2015 Feb 9 23:01:43.132212 ips: Registering with name server fcid 00220000 vsan 10 nwwn 21:05:00:0d:ec:71:f1:42 pwwn 21:05:00:0d:ec:71:f1:42, init_ip: 172.16.130.11 2015 Feb 9 23:01:43.136657 ips: Received NS entry change event 2, vsan_id 10, flags 0x4150 2015 Feb 9 23:01:43.140193 ips: Session Create Response: Init: node_name iqn.1991-05.com.microsoft:srvwin2008.vpackets.local init_name iqn.1991-05.com.microsoft:srvwin2008.vpackets.local init-nwwn 00:00:00:00:00:00:00:00 init-pwwn 00:00:00:00:00:00:00:00 init-fcid 0 isid 400001370000pgt 12288 num_auth method 2 2015 Feb 9 23:01:43 MDS-02 %IPS-SLOT1-5-ISCSI_CONN_UP: GigabitEthernet1/1: iSCSI session up from initiator iqn.1991-05.com.microsoft:srvwin2008.vpackets.local alias ip 172.16.130.11 to target Discovery 2015 Feb 9 23:01:43 MDS-02 %IPS-SLOT1-5-ISCSI_SB_GET_TGT: iSCSI SB get 1 targets, initiator iqn.1991-05.com.microsoft:srvwin2008.vpackets.local alias ip 172.16.130.11 2015 Feb 9 23:01:43.161391 ips: Session Destroy node-name:[iqn.1991-05.com.microsoft:srvwin2008.vpackets.local] init-name:[iqn.1991-05.com.microsoft:srvwin2008.vpackets.local] tgt-name:[]ISID:[400001370000] indx:[0x02000000] failure-code:[1] 2015 Feb 9 23:01:43.161709 ips: Session destroy response status 0 for init_name:[iqn.1991-05.com.microsoft:srvwin2008.vpackets.local] target_name:[] isid:[400001370000] sent 2015 Feb 9 23:01:43 MDS-02 %IPS-SLOT1-5-ISCSI_CONN_DOWN: GigabitEthernet1/1: iSCSI session down from initiator iqn.1991-05.com.microsoft:srvwin2008.vpackets.local alias ip 172.16.130.11 to target Discovery, reason: client send iscsi logout 2015 Feb 9 23:01:43.165967 ips: Session Create (init-name:[iqn.1991-05.com.microsoft:srvwin2008.vpackets.local] tgt-name:[iqn.1987-05.com.cisco:05.f7712ff54520690f04b3a2edacfe7586.21000018628de8b7] init-alias:[] ISID:[400001370000] indx:[0x02000000] init_ip:[172.16.130.11] 2015 Feb 9 23:01:43.166947 ips: Querying NS for target pwwn 21:00:00:18:62:8d:e8:b7 vsan 10 filter fcid 00220000 2015 Feb 9 23:01:43.168205 ips: NS target response vsan:[10] fcid:[00110072] for target pwwn 21:00:00:18:62:8d:e8:b7 2015 Feb 9 23:01:43.168755 ips: Session Create Response: Init: node_name iqn.1991-05.com.microsoft:srvwin2008.vpackets.local init_name iqn.1991-05.com.microsoft:srvwin2008.vpackets.local init-nwwn 21:00:00:18:62:8d:e8:b7 init-pwwn 21:00:00:18:62:8d:e8:b7 init-fcid 220000 isid 400001370000pgt 12288 num_auth meth 2015 Feb 9 23:01:43 MDS-02 %IPS-SLOT1-5-ISCSI_CONN_UP: %$VSAN 10%$ GigabitEthernet1/1: iSCSI session up from initiator iqn.1991-05.com.microsoft:srvwin2008.vpackets.local alias ip 172.16.130.11 to target iqn.1987-05.com.cisco:05.f7712ff54520690f04b3a2edacfe7586.21000018628de8b7 MDS-02(config)# show flogi database -------------------------------------------------------------------------------- INTERFACE VSAN FCID PORT NAME NODE NAME -------------------------------------------------------------------------------- iscsi1/1 10 0x220000 21:05:00:0d:ec:71:f1:42 21:04:00:0d:ec:71:f1:42 Total number of flogi = 1. MDS-02(config)# show fcns database VSAN 10: -------------------------------------------------------------------------- FCID TYPE PWWN (VENDOR) FC4-TYPE:FEATURE -------------------------------------------------------------------------- 0x110072 NL 21:00:00:18:62:8d:e8:b7 scsi-fcp:target [JBOD] 0x110100 N 21:02:00:0d:ec:71:f1:42 (Cisco) scsi-fcp:init isc..w 0x220000 N 21:05:00:0d:ec:71:f1:42 (Cisco) scsi-fcp:init isc..w Total number of entries = 3 MDS-02(config)# show islb initiator iSCSI Node name is iqn.1991-05.com.microsoft:srvwin2008.vpackets.local Initiator ip addr (s): 172.16.130.11 iSCSI alias name: Configured node (iSLB) Node WWN is 21:04:00:0d:ec:71:f1:42 (configured) Member of vsans: 10 Number of Initiator Targets: 1 Initiator Target: iqn.1987-05.com.cisco:05.f7712ff54520690f04b3a2edacfe7586.21000018628de8b7 * Port WWN 21:00:00:18:62:8d:e8:b7 [JBOD] Primary PWWN VSAN 10 Zoning support is enabled Trespass support is disabled Revert to primary support is disabled Number of Virtual n_ports: 1 Virtual Port WWN is 21:05:00:0d:ec:71:f1:42 (configured) Interface iSCSI 1/1, Portal group tag: 0x3000 VSAN ID 10, FCID 0x220000 |
Note that the MDS02 will only see 1 FLOGI and that MDS01 will see both FLOGI from its local FC Disk and from its iSCSI Initiator.
Both servers are able to map the drive and everybody is happy 🙂
Nicolas
As I mentionned at the beginning of the post, I did not played with VRRP on purpose and I will relate about that in a following blogpost 🙂