DHCP and routed network vapp

[thelittlemouse]

Hi

Can someone help me with the DHCP services of VMware.

I have an edge gateway providing two services

NAT: nat the internal network to the external network

DHCP: lease IPs on the internal network

NIC: configured to DHCP mode

If the internal network and the vapp network (marked CCC) is linked using direct connection everything works,

and the VM recieve DHCP leases.

The problem is that the VM does not receive the DCHP leases in the following situation:

1. uncheck the fence vapp in the network configuration

2. select non bridged connection mode for CCC

3. disable both the firewall and NAT checkboxes

                    x--------------

------------x------>| ext network x

| edge gw   |       ---------------

|  NAT      |       --------------|

|  DHCP     ------->| internal    |   CCC  ----------------  -----   ----

------------x       | org network |--------| vapp network |--|NIC|---|VM|

                    --------------x        ----------------  -----   ----

Why would I want this? to have firewall before each VM

Thanks denes

[_morpheus_]

Can you clarify whether you're trying to do DHCP using fenced vApp?

[JayhawkEric]

Your setup looks a lot like ours.

I believe if you uncheck both firewall and nat on the internal vApp network than the vApp would not be connected to the VSE which gets deployed with the vApp, and therefor it wouldn't receive DHCP.  I could be wrong though.

You might check this by manually assigning a valid IP within the VM OS and see if you can ping the VSE that gets deployed with the vApp.

[thelittlemouse]

Hi

Thanks for the help, truly I do not really know.

Here are the 3 screenshots showing the network setup

The currently connected network is kuku, which is the not

working part. If I switch to the other network connection it

works.

I hope the screen shots clarify the network setup.

Thanks,

Denes

[thelittlemouse]

Hi

I also tried to enable the firewall only and change the default policy to accept, but that did not help either

Thanks Denes

[_morpheus_]

That's absolutely not true

Eric Lee wrote:

Your setup looks a lot like ours.

I believe if you uncheck both firewall and nat on the internal vApp network than the vApp would not be connected to the VSE which gets deployed with the vApp, and therefor it wouldn't receive DHCP.  I could be wrong though.

You might check this by manually assigning a valid IP within the VM OS and see if you can ping the VSE that gets deployed with the vApp.

[JayhawkEric]

Makes sense that it's not true as then you could have some VM's internally using this network setup and have no access outside the vApp (such as app and DB VM's) and then a multi-honed web VM to this network and an external network.

That's absolutely not true

I finally had time to do some testing in my environment.  I setup the internal network and disabled NAT/Firewall and setup DHCP on the network.  When I deployed the VM the guest customization script locked up my RHEL 5.5 VM. When I reset the VM it did pull DHCP properly.

Do you still have your VM set to do guest customization?

Eric

[thelittlemouse]

Hi,

Did you enable DHCP on the internal network using the DHCP settings on the internal network, because

in this case you have two DHCP servers, and the VM got a lease from the internal DHCP server and not

form the one located on the organization network.

I think that what this netwok setup does is that the edge gateway (internal) not the one on the diagram above sits between

the org network an the vapp network and creates a OSI L3 link (routing) between the two, which prevents the

DHCP to get through even if the NAT option is disable.

I think in your case VmWare cheats and sets the IP of the VM with the VmWare tools.

Manual IP setup also does not work. Let us assume that the org network is

gw: 192.168.2.1

nm: 255.255.255.0

VM IP: 192.168.2.6

nm: 255.255.255.0

In this case probable the routing table of the internal edge sees the same network on both of it's

iterfaces preventing appropiate routing

D.

[thelittlemouse]

Hi,

I magaged to make the netwokring work (without the DHCP)

VM:  (manually set)

IP = 192.168.0.222

GW = 192.168.0.254

NM= 255.255.255.0

vapp nework:

-enable NAT

-create a mapping from VM NIC to 192.168.0.223

The only problem with this setup is that the VM will know it's IP address

192.168.0.222 and other VMs on the internal network will know this VM

as 192.168.0.223

D.