Link to home
Start Free TrialLog in
Avatar of Jay Thomas
Jay ThomasFlag for United Kingdom of Great Britain and Northern Ireland

asked on

vsphere 5.1 storage problem using starwind

Hi all.
I appreciate this is a long intro but hopefully the actual problem is very small. Just need to give you the background.
I have what i think is a configuration issue in my lab that im hoping will be  easy answer for an expert.
Setup:
All virtual machines running on my laptop. Installed VM workstation 11.
I have 2 ESXi 5.1 VMs on ip addresses 10.0.0.215 and 10.0.0.216
2012 Domain controller IP address 10.0.0.209
vSphere 5.1 server all configured with ESXi servers and its using 10.0.0.244
So far so good. All the above works great. They allused to have addresses in the 192.168.0.x range so that they could speak to the laptop with a 192 IP address.
I changed the virtual IP range to the 10.x range because my VMs kept looking at the virgin router for DHCP addresses. I have also deployed citrix labs with dhcp options 66/67 so i need my virtual clients to go to my virtual DHCP to get not only the IP address but the bootstrap file location (that's on a xendesktop controller).
So i just changed all virtuals to the 10.x range but here is the problem i have:
The two ESXi systems are configured via vsphere to use starwind storage which is on my laptop with a 192. address. So now the ESXi servers\ vsphere can't see the data stores. I have added a 2nd NIC to the vsphere box with a 192 address and now vsphere can ping my 192. laptop ip address but here is the question... How do i get the 2 ESXi servers to see the laptop? Do i need to add virtual NICs to them with a 192 address? Do i create a 2nd virtual network? You can see i just not sure so any pointers would be appreciated.
Many thanks
Jason
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jay Thomas

ASKER

Hi, they are all on one vnet. All was working ok till I changed up range
So all VMs have custom specific network including the 2 ESXi boxes.
I have added a 2nd NIC to vsphere with a 192 address, it now sees the laptop via ping.
I have also added another NIC to bo the ESXi boxes. All of these 2nd NICs are "bridged". Thing is, when i go into the network management on the ESXi boxes and look at network adapters I can only see one, I can't see the 2nd NIC to add a 192 address to - if that will even work?
I need to draw this network arrangement out...let me have a closer look...
Ahh a reboot perhaps Doh!
So the background.
I have several Citrix labs with various clients including PVS, Xendesktop that via DHCP need to know where the TFTP server is.
I had all virtuals on the Virgin 192 range. So for me to boot a thin client i litterally had to kil DHCP on the virgin router so that was a pain. I instead decided to switch the IP range and then of course the datastore with is on a SSD on my laptop via Starwind can no longer be accessed by anything!
My thought process is this. Add a 2nd NIC to vsphere and ESXi hosts, with a 192 address - this would work? vSphere now pings but ESXi's still couldn't see storage. I am litterally booting ESXi hosts now... Back in a minute with a report.
HI Andrew - quick update, still not had chance to get back to my lab to see if reboot fixed issue. Gte back to you as soon as I've done that.
No luck.
Can I run something past you Andrew.
Should the ESXi hosts be able to see the laptop SSD drive (starwind) the way that i have them setup? I mean, with 2 nics, one on the custom specific network and the other bridged with host. They still can't see the storage...
I gave up Andrew and put the IP range back to that of the Virgin router. I found that but powering down the virgin router once and then booting my clients they got their IP addresses with max lease time which meant subsequent reboots after the virgin router was turned back on the clients continued to use my virtual dhcp server. That was the reason for the initial change, i couldn't get my clients to use the virtual dhcp server instead of the virgin one so hence why i changed IP range.

I know you didn't offer a fix dude but you always respond and so happy to ship the points your way.