Solved

VMWare ESX 5: configure multiple ISCSI (Hanccoka?)

Posted on 2012-03-12
4
3,231 Views
Last Modified: 2012-03-14
To Hanccoka: thanks for all your input on my questions! Would be great if you could give input on this question too.

Since the patch on my NAS (by Synology) solved a lot of problems, I tried again configuring my ISCSI's according your link:
http://www.experts-exchange.com/Software/VMWare/A_9250-HOW-TO-Add-an-iSCSI-Software-Adaptor-and-Create-an-iSCSI-Multipath-Network-in-VMware-vSphere-Hypervisor-ESXi-5-0.html

Now I see I have 2 things different then in your manual:
-when I want to bind the vmkernel iscsi network I also see the management vswitch (not in your screenshot)
-I added the dynamic links manually (added both ip addresses of my NAS x.x.x.x)

Furthermore I see events in my ESX (only one configured, in standby mode now):

2010-10-14T19:46:04.900Z cpu1:3755)ScsiPath: 4541: Plugin 'NMP' claimed path 'vmhba37:C2:T0:L0'
2010-10-14T19:46:04.936Z cpu1:3755)<3>ata5.01: bad CDB len=16, scsi_op=0x9e, max=12
2010-10-14T19:46:04.941Z cpu0:2653)NMP: nmp_ThrottleLogForDevice:2318: Cmd 0x1a (0x4124007b0040) to dev "mpx.vmhba1:C0:T1:
2010-10-14T19:46:04.941Z cpu0:2653)ScsiDeviceIO: 2316: Cmd(0x4124007b0040) 0x1a, CmdSN 0x110f to dev "mpx.vmhba1:C0:T1:L0"
2010-10-14T19:46:04.999Z cpu1:3755)<3>ata5.01: bad CDB len=16, scsi_op=0x9e, max=12
2010-10-14T19:46:05.154Z cpu0:3755)Vol3: 647: Couldn't read volume header from control: Invalid handle
2010-10-14T19:46:05.154Z cpu0:3755)FSS: 4333: No FS driver claimed device 'control': Not supported
2010-10-14T19:46:05.154Z cpu0:3755)<3>ata5.01: bad CDB len=16, scsi_op=0x9e, max=12
2010-10-14T19:46:05.157Z cpu1:3755)<3>ata5.01: bad CDB len=16, scsi_op=0x9e, max=12
2010-10-14T19:46:05.159Z cpu1:3755)<3>ata5.01: bad CDB len=16, scsi_op=0x9e, max=12
2010-10-14T19:46:05.161Z cpu1:3755)<3>ata5.01: bad CDB len=16, scsi_op=0x9e, max=12
2010-10-14T19:46:05.165Z cpu1:3755)FSS: 4333: No FS driver claimed device 'mpx.vmhba1:C0:T1:L0': Not supported
2010-10-14T19:46:05.412Z cpu1:3755)VC: 1449: Device rescan time 93 msec (total number of devices 9)
2010-10-14T19:46:05.412Z cpu1:3755)VC: 1452: Filesystem probe time 392 msec (devices probed 8 of 9)
2010-10-14T19:51:23.471Z cpu0:20426)WARNING: UserObj: 675: Failed to crossdup fd 8, /dev/ptyp0 type CHAR: Busy
2010-10-14T19:51:23.471Z cpu0:20426)WARNING: UserObj: 675: Failed to crossdup fd 10, /dev/ptyp0 type CHAR: Busy
2010-10-14T19:51:23.472Z cpu1:20455)WARNING: UserLinux: 1340: unsupported: (void)


Now, pracital questions:
------------------------
-please advise if you see any incosistencies in my config
-please advise if you would configure trunks (I will make vlans -new ticket I will create for migrating to vlans -bought a Sonicwall firewall-)

Note: for now (15 minutes) everything is working fine, however no vm's are running on it.

Thanks!
J.
0
Comment
Question by:janhoedt
  • 2
  • 2
4 Comments
 
LVL 120

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 500 total points
ID: 37710357
Yes, in my article, I've setup a new vSwitch.

Check the number of paths to the NAS, there should be two paths per iSCSI LUN.

also you can login to ESXi via SSH or Console, and use ESX top, and check the traffic on the NICs, this is iSCSI traffic.

logs look normal and refer to local SATA devices (maybe) or it's a CDROM - mpx.vmhba1:C0:T1:L0
0
 

Author Comment

by:janhoedt
ID: 37716782
Switches setup according your article on all my ESX hosts. No issues at all for now (1 day).
0
 
LVL 120
ID: 37716790
very good.
0
 

Author Comment

by:janhoedt
ID: 37719708
2nd day without any issues, I'l have to conclude my nas had troubles and the update solved them all (NFS as well as this issue).
0

Featured Post

Simple, centralized multimedia control

Watch and learn to see how ATEN provided an easy and effective way for three jointly-owned pubs to control the 60 televisions located across their three venues utilizing the ATEN Control System, Modular Matrix Switch and HDBaseT extenders.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

HOW TO: Connect to the VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere (HTML5 Web) Host Client 6.5, and perform a simple configuration task of adding a new VMFS 6 datastore.
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
Teach the user how to join ESXi hosts to Active Directory domains Open vSphere Client: Join ESXi host to AD domain: Verify ESXi computer account in AD: Configure permissions for domain user in ESXi: Test domain user login to ESXi host:

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question