|
|
|
Forum Newbie
Group: Forum Members
Last Login: Monday, March 10, 2008 1:57 PM
Posts: 4,
Visits: 8
|
|
I'm having trouble connecting my VMWare servers (HP Blade servers) to my VSA (DL320). I've done the steps provided in the VI3 field guide, but I am having no luck connecting the VMware ESX servers to the iSCSI VSA. Here's what I've done:
In LeftHand CMC:
1. Created a Authentication Group and added the Initiator Node Name (copy/paste from VMWare server).
2. Created a Volume List and added above Authentication Group to the Volume List.
3. Created Volumes and added them to the Volume List.
4. Enabled Load Balancing.
5. Verified Read/Write access to Volumes.
6. Verified all volumes fall well under the 2TB limit per volume (16-18 GBs per volume, 8 volumes).
7. Deleted everything, and started over....multiple times.
In VMWare Console:
1. Enabled iSCSI in firewall of ESX server.
2. Enabled iSCSI in iSCSI Software Adapter.
3. Separated my Service Console/VMKernal from my Virtual Machine Network.
4. Added IP address of iSCSI in Properties > Dynamic Discovery.
5. Tried Rescan, Add Storage, Reboot.....multiple times.
And after all of that, I can not see the iSCSI VSA from the console. I can ping both the VSA and ESX server and (obviously) log into each server, as well. I'm kind of at a loss here. Does anyone see where I've gone wrong in this setup? I can't figure it out....
|
|
|
|
|
Junior Member
Group: Forum Members
Last Login: Wednesday, November 12, 2008 6:14 PM
Posts: 11,
Visits: 58
|
|
Mike-
Sounds like you've got all the steps correct, a few things to check...
To ensure you have proper connectivity, try doing a vmkping from the commandline on the ESX server to the VIP of the VSA cluster.
Do you have CHAP enabled in the ESX initiator? This can prevent connection if the auth group on the SAN is not set up for it.
Sometimes double-checking initiator node name in the auth group, volume list associations etc, will reveal a simple mistake to be the root of such issues.
Have you tried rebooting the ESX box?
Write back if you're still having problems and we can did deeper.
Brad Katz
LeftHand Support
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: Monday, March 10, 2008 1:57 PM
Posts: 4,
Visits: 8
|
|
To ensure you have proper connectivity, try doing a vmkping from the commandline on the ESX server to the VIP of the VSA cluster.
This part seems to be the issue. From the shell, it first says that vmkping is an unknown command. But, if I use regular ping, it says destination host unreachable. However, I can ping both from my machine, and both are on the same subnet and have the same gateway. And I can connect to both through their respective consoles. I'll check in with VMWare to see what I'm missing on the network side.
Thanks!
|
|
|
|
|
Forum Member
Group: Forum Members
Last Login: Wednesday, July 09, 2008 5:59 PM
Posts: 30,
Visits: 47
|
|
Mike,
On the VM side, did you go to Storage Adapters and add an iSCSI volume? Once that's done, it will show up in Storage.
Regards, Rich
HP ML350 SATA with VSA
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: Monday, March 10, 2008 1:57 PM
Posts: 4,
Visits: 8
|
|
Thanks for the reply......
That can't happen until after the connection is made between the two units. Until the VSA recognizes (and vice versa) the ESX server, you can't go to the Storage Adapter and add the volumes. Definitely a network issue right now, somewhere between the port mappings on the mezzanine cards on the Blades, to the GbE2c's on the blade chassis, to the 3Com switch, to the VMware virtual adapters, to the iSCSI VSA. Whew....
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: Monday, March 10, 2008 1:57 PM
Posts: 4,
Visits: 8
|
|
Turned out to be bad cables between the switch and the blade system. Replaced the scavenged ones with good ones, rebooted and all is back to good.
Thanks for the help(s)!!
|
|
|
|