Network Setup
VSA Community Forum
LeftHand VSA Forum
Home       Members    Calendar    Who's On
Welcome Guest ( Login | Register )
        



Network Setup Expand / Collapse
Author
Message
Posted Wednesday, February 20, 2008 3:00 PM
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Group: Forum Members
Last Login: Wednesday, July 09, 2008 5:59 PM
Posts: 30, Visits: 47
Adam,

Once I tried to get the sw iSCSI initiator in ESX to work I ran into problems. I ended up wiping out the VSA VM and starting over. I have the ESX network set up like the diagram in the VSAUserManual.pdf shows. If you can reference the diagram there, I have VS0 and VS1 plugged into the same hw switch. The subnet is 172.17.251.0/24. The console is .209, the VSA is .210, and the gateway is .1.

I cannot ping from the esx console to the VSA. They are on different virtual switches, but that shouldn't matter.

Virtual switch 2 is a crossover cable to a nic on one of my 2003 servers. The subnet is 192.168.254.0/24. The server can ping the esx, but not the other way. It sounds like an esx routing problem?

I would like to be able to attach to the VSA raid from esx VMs, and also from the servers on the 172.17.251.0 subnet.

Before I hosed up the config I could ping the VSA and the volume VIP. Help?


Regards, Rich

HP ML350 SATA with VSA
Post #143
Posted Wednesday, February 20, 2008 3:23 PM
Supreme Being

Supreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme BeingSupreme Being

Group: Moderators
Last Login: Yesterday @ 3:37 PM
Posts: 108, Visits: 375
It is really hard to mentally grasp what you are trying to do networking wise through text but I can help steer you a bit.

First of all being able to ping the VIP of the SAN from the ESX console is absolutely required.
From and ESX console you must be able to both ping and vmkping the SAN or you won't be able to connect volumes.
The ping / console is used for iSCSI authentication and discovery. The vmkping / vmkernel is used for actual iSCSI connectivity and IO.
Both are necessary.
Once you have those working if you want VMs to be able to connect iSCSI themselves then just give them virtual adapters on the same virtual switch that the VSA and VMkernel are on.

Hope that helps.


Adam C
Product Manager
LeftHand Networks
Post #144
Posted Wednesday, February 20, 2008 6:14 PM
Forum Member

Forum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum MemberForum Member

Group: Forum Members
Last Login: Wednesday, July 09, 2008 5:59 PM
Posts: 30, Visits: 47
I did end up getting it working. But, it was reboot several times, change things and then change them back.... strange. The iSCSI initiator works and I installed a VM from an iso image. Nice.



Regards, Rich

HP ML350 SATA with VSA
Post #145
« Prev Topic | Next Topic »


All times are GMT -6:00, Time now is 12:46am

Powered By InstantForum.NET v4.1.4 © 2008
Execution: 0.047. 11 queries. Compression Disabled.