Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

iSCSI Boot with NetApp

I have a question about the iSCSI boot with a NetApp.

The configuration in UCSM is like the CVD Flexpod Guide.

I had created two vNics (image01.png + image02.png).

When the blade is booting up, the connection to the NetApp will established. On the NetApp Controller i see the logged in initiator on the igroup:

    IG_ESX03 (iSCSI) (ostype: vmware):

        iqn.2013-12.ch.xxx:esxi03a (logged in on: team01-20)

        iqn.2013-12.ch.xxx:esxi03b (logged in on: team01-30)

Then on the KVM Session i see that ESXi stay at the iscsi_vmk screen (image03.png). After maybe 30 seconds, i execute the igroup show command on the NetApp:

    IG_ESX03 (iSCSI) (ostype: vmware):

        iqn.2013-12.ch.xxx:esxi03a (logged in on: team01-30, team01-20)

        iqn.2013-12.ch.xxx:esxi03b (logged in on: iscsi (awaiting reconnect))

After more 30 seconds, i saw that team01-30 is not logged in on the second iqn:

    IG_ESX03 (iSCSI) (ostype: vmware):

        iqn.2013-12.ch.xxx:esxi03a (logged in on: team01-30, team01-20)

        iqn.2013-12.ch.xxx:esxi03b (not logged in)

ESXi starts normally and looks fine. In the storage adapter configuration it looks good. Two paths on FI-A and FI-B (image04.png and image05.png).

Is that normal, that iqn.2013-12.ch.xxx:esxi03b is not logged in.

Thank you.

Best Regards

Patrick

3 REPLIES
Cisco Employee

iSCSI Boot with NetApp

Patrick,

Check the troubleshooting section of Andreas' doc :

http://www.cisco.com/en/US/products/ps10281/products_configuration_example09186a0080bfcb0a.shtml#tshoot

Or my shameless plug:

https://supportforums.cisco.com/docs/DOC-38582#Verification_

(per adapter)

At least it will let us know what's going on in UCS.

M.

New Member

iSCSI Boot with NetApp

Hi Marcin

Here is the output (the customer name is replaced with xxx):

vnic iSCSI Configuration:

----------------------------

vnic_id: 13

          link_state: Up

       Initiator Cfg:

     initiator_state: ISCSI_INITIATOR_READY

initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR

                vlan: 0

         dhcp status: false

                 IQN: iqn.2013-12.ch.xxx:esxi01a

             IP Addr: 172.20.20.101

         Subnet Mask: 255.255.255.0

             Gateway: 0.0.0.0

          Target Cfg:

          Target Idx: 0

               State: ISCSI_TARGET_READY

          Prev State: ISCSI_TARGET_DISABLED

        Target Error: ISCSI_TARGET_NO_ERROR

                 IQN: iqn.1992-08.com.netapp:xxxvfvm01

             IP Addr: 172.20.20.155

                Port: 3260

            Boot Lun: 0

          Ping Stats: Success (11.743ms)

        Session Info:

          session_id: 0

         host_number: 0

          bus_number: 0

           target_id: 0

vnic_id: 14

          link_state: Up

       Initiator Cfg:

     initiator_state: ISCSI_INITIATOR_READY

initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR

                vlan: 0

         dhcp status: false

                 IQN: iqn.2013-12.ch.xxx:esxi01b

             IP Addr: 172.20.30.101

         Subnet Mask: 255.255.255.0

             Gateway: 0.0.0.0

          Target Cfg:

          Target Idx: 0

               State: ISCSI_TARGET_READY

          Prev State: ISCSI_TARGET_DISABLED

        Target Error: ISCSI_TARGET_NO_ERROR

                 IQN: iqn.1992-08.com.netapp:xxxvfvm01

             IP Addr: 172.20.30.155

                Port: 3260

            Boot Lun: 0

          Ping Stats: Success (19.016ms)

        Session Info:

          session_id: 0

         host_number: 0

          bus_number: 0

           target_id: 0

adapter 1/1/1 (mcp):2#

Thank you.

Cisco Employee

iSCSI Boot with NetApp

Patrick,

Does the state here change with time?

If you tell me this state remains the same, it means that we retain probler reachability between UCS and iSCSI target.

IF it changes look at the state transition and error code... You can also try sniffing traffic to see if there's something that might be going wrong on network layer.

M.

354
Views
0
Helpful
3
Replies