cojacks85
Contributor
Contributor

VMWare HA issues / ESX3.5.0U4 DNS issues

Jump to solution

Hi guys,

I have the following problems with my VMWare farm.

VMWare HA:

I have setup a HA-Cluster where I wanted to add two hosts (HP DL585). One of them installs and configures the HA Agent with no problems. The other one comes up with an error message (not enough resources...). My configured failover capacity is 1 with VC saying I have 0 at the moment. Reservations are not made on single VMs. Strict admission control is turned off.

There is currently only one VM on this cluster which is a virtualized VC, so I haven't got a chance to turn it off and configure HA Smiley Wink

I've read that this was an issue some time earlier with U2, but I guess this should be fixed right now..

Another point is that I have problems with DNS. I have two service console connections at the moment, one in my backend for VMKernel iSCSI Connections with IP 10.0.0.1/8 and one for Management with 172.16.1.180/24 to the frontend. In my opinion the iSCSI SC doesn't need to have a connection to the gateway (172.16.1.1) because it's only for one iSCSI SAN in this backend and will be forever. When I try to ping my DNS servers from ESX console (172.16.1.180) it tries to ping this adress from 10.0.0.1... Do I have to bridge my separated LANs to get a connection from iSCSI SC to the gateway or what? Sounds a bit insecure..

Thanks for any hints or comments on that.

Cheers,

Timo

0 Kudos
1 Solution

Accepted Solutions
AndreTheGiant
Immortal
Immortal

In this case I simple use static hosts files on ESXs and VC with the only front-end SC.

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro

View solution in original post

0 Kudos
5 Replies
AndreTheGiant
Immortal
Immortal

I suggest to create two different network to isolate the iSCSI part.

Remember that for iSCSI (in ESX 3.x) you need also a SC.

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
cojacks85
Contributor
Contributor

Hello Andre,

sorry I think I haven't clearly expressed myself. There are two different networks with two different SCs. One in my backend and one in my frontend.

Regarding the DNS problems I have resolved the issue with deleting the SC from iSCSI network, but I know there would be one needed (besides of this, for which situation I need a SC on iSCSI network?). I could now proper nslookup my servers..

Regarding HA nothing changed..

Thanks anyways for your hint.

Cheers,

Timo

0 Kudos
AndreTheGiant
Immortal
Immortal

In this case I simple use static hosts files on ESXs and VC with the only front-end SC.

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro

View solution in original post

0 Kudos
loewenholz
Contributor
Contributor

You need SC Port and iSCSI (VMKernel Port) on the same Network because SC will authenticate against iSCSI and for scanning new LUN`s.

Check DNS/Routing under Configuration/Software

regards,

Marcus

cojacks85
Contributor
Contributor

Okay thanks for the hints, now it works fine.

All I've done is the following:

Setting static hostfiles

Setting das.AllowedNetworks for the cluster to my primary SC

Thanks for the hints leading me to this solution.

Cheers,

TImo

0 Kudos