vSphere Storage Appliance

 View Only
  • 1.  iSCSI target not reconnected after boot

    Posted Aug 02, 2010 07:57 PM

    I'm using vsphere ESXi 4.0, updated to last patch as of today, and I'm having this problem.

    Any iSCSI vmfs disk is not reconnected anymore after reboot. If I perform a manual scan, all disks are mounted again with no problem, but no hope to see them before the manual scan.

    All paths are manual and fixed.

    There was no problem up to a few days ago, before installing last vsphere patches (I had to do because I needed a patch loss of vkernel connection).

    I'm scanning and rebooting continuosly... trying to see any persistence.

    Any hint?

    Thanks,

    Tonino



  • 2.  RE: iSCSI target not reconnected after boot

    Posted Aug 02, 2010 11:03 PM

    /var/log/messages contains, in the boot phase:

    Aug 2 22:34:24 iscsid: Login Failed: iqn.1986-03.com.hp.storage.msa1510i:cerere.vmfs4 if=vmk2 addr=192.168.84.81:3260 (TPGT:65536 ISID:0x1) Reason: 00080000 (Initiator Connection Failure)

    Aug 2 22:34:24 iscsid: Login Failed: iqn.1986-03.com.hp.storage.msa1510i:cerere.vmfs4 if=vmk4 addr=192.168.84.81:3260 (TPGT:65536 ISID:0x2) Reason: 00080000 (Initiator Connection Failure)

    Aug 2 22:34:24 iscsid: Login Failed: iqn.1986-03.com.hp.storage.msa1510i:cerere.vmfs4 if=vmk5 addr=192.168.84.81:3260 (TPGT:65536 ISID:0x3) Reason: 00080000 (Initiator Connection Failure)

    Aug 2 22:34:24 iscsid: Login Failed: iqn.1986-03.com.hp.storage.msa1510i:cerere.vmfs4 if=vmk6 addr=192.168.84.81:3260 (TPGT:6 ISID:0x4) Reason: 00080000 (Initiator Connection Failure)

    Unique interface working on 192.168.84.x network is vmk6 (which has 192.168.84.21).

    Why all those attempted login from other iSCSI interfaces (vmk2,vmk4,vmk5)?

    Log is full of failed attempts to connect target from any ESXi iSCSI interface.

    Is that normal?



  • 3.  RE: iSCSI target not reconnected after boot

    Posted Aug 03, 2010 10:22 AM

    Another strange log:

    Aug 3 10:07:31 Hostd: Fetch all physical NICs....

    Aug 3 10:07:31 Hostd: Fetched physical NIC: vmnic0.

    Aug 3 10:07:31 Hostd: Fetched physical NIC: vmnic1.

    Aug 3 10:07:31 Hostd: Fetched physical NIC: vmnic2.

    Aug 3 10:07:32 Hostd: Fetched physical NIC: vmnic3.

    Aug 3 10:07:32 Hostd: Fetched physical NIC: vmnic4.

    Aug 3 10:07:32 Hostd: Fetched physical NIC: vmnic5.

    Aug 3 10:07:32 Hostd: Fetched physical NIC: vmnic6.

    Aug 3 10:07:32 root: init Running sfcbd-watchdog start

    Aug 3 10:07:32 Hostd: Fetched physical NIC: vmnic7.

    Aug 3 10:07:32 Hostd: Loading DVS information

    Aug 3 10:07:32 Hostd: DvsVmkProvider::Refresh called

    Aug 3 10:07:32 Hostd: Failed to load DVS portgroup information : no element found.

    Aug 3 10:07:32 Hostd: Fetch all virtual switches....

    Aug 3 10:07:33 Hostd: Successfully fetched virtual switch: vSwitch0.

    Aug 3 10:07:33 Hostd: RefreshVmkernelNic: called

    Aug 3 10:07:33 Hostd: InstallNics: Fetch all VmKernel NICs....

    Aug 3 10:07:33 Hostd: InstallNics: Successfully fetched VmKernel NIC vmk0 on VMware-A.

    Aug 3 10:07:33 Hostd: InstallNics: Successfully fetched VmKernel NIC vmk3 on vMotion-A.

    Aug 3 10:07:33 Hostd: InstallNics: Successfully fetched VmKernel NIC vmk1 on BackupVM.

    Aug 3 10:07:33 Hostd: InstallNics: Successfully fetched VmKernel NIC vmk2 on iSCSI1-v81.

    Aug 3 10:07:33 Hostd: InstallNics: Successfully fetched VmKernel NIC vmk4 on iSCSI2-V82.

    Aug 3 10:07:33 Hostd: InstallNics: Successfully fetched VmKernel NIC vmk5 on iSCSI3-v83.

    Aug 3 10:07:33 Hostd: InstallNics: Successfully fetched VmKernel NIC vmk6 on iSCSI4-v84.

    These NIC installs appear after iSCSI inizialization... Is that normal?

    it looks like it follows these steps:

    - iSCSI init (-> failure)

    - NIC init

    - manual iSCSI rescan (ok)

    Any comment? It looks like a bug in ESXi 4.0.



  • 4.  RE: iSCSI target not reconnected after boot

    Posted Aug 03, 2010 11:17 AM

    The login failed message could be a problem with the authentication.

    Are you using a chap password?

    Have you change something on the storage side?

    Andre



  • 5.  RE: iSCSI target not reconnected after boot

    Posted Aug 03, 2010 12:23 PM

    There are no password.

    I reconfigured storage after I saw problems on vmware, but that did not help.

    I have 4 disk-sets and 4 nics on storage (4 vlans), with dual path for each disk (main and secondary path).

    On servers, I have four NICs only for iSCSI.

    NICs are in the same vswitch (a unique vswitch for the whole server), but are dedicated to iSCSI (each one has a specific vlan).

    iSCSI paths are fixed (manually typed for each server).

    In any case, boot reconnect does not work, but manual "rescan" works fine.

    After manual "rescan" I see all iSCSI disks.



  • 6.  RE: iSCSI target not reconnected after boot

    Posted Aug 03, 2010 01:05 PM

    Check on storage vendor site, to see if there are some best practice for VMware.

    Usually you do not need to register manually each paths, cause the autodiscovery will find them for you.

    Andre



  • 7.  RE: iSCSI target not reconnected after boot

    Posted Aug 03, 2010 02:21 PM

    It looks like iSCSI scripts start before NIC and network scripts.

    It that possible?



  • 8.  RE: iSCSI target not reconnected after boot

    Posted Aug 03, 2010 02:35 PM

    Hi,

    In the boot sequence once the network is up then only ISCSI targets will be scanned automatically.

    what is the ISCSI product you are using.






    Jak



  • 9.  RE: iSCSI target not reconnected after boot

    Posted Aug 03, 2010 02:52 PM

    HP Storageworks MSA1510i



  • 10.  RE: iSCSI target not reconnected after boot

    Posted Aug 06, 2010 08:51 AM

    Problem is solved, but mistery remains.

    We did a lot of loop of this kind:

    1. no iSCSI drives mounted

    2. manual rescan

    3. reboot (looping to #1)

    The first time we made two reboot, without a rescan, all iSCSI drives have been mounted normally.

    So, we tried again.

    If I do a rescan, and a reboot, I don't see iSCSI drives.

    If I make another reboot, without making a rescan, on following boot I see all iSCSI drives.

    More: if I make a "/sbin/auto-backup.sh", on following reboot iSCSI drives disappear. Only after another consecutive reboot, I see all disks again.

    Where is the problem?