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:
https://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:2
318: 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.