[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1923
  • Last Modified:

Adding a new VMware ESX host into VCentre within DMZ

Hi

I need to add a new VMware ESX host in an existing VCentre but needs to be configured within a DMZ architecture:-

So:-

1) What configurations do I need to do within VCentre, i.e network switches, etc..
2) The host be configured in its own DMZ but still needs to be available on the main internal network
3) What ports need to be enabled in firewall, to able to see DMZ servers and able to connect to these clients

Thanks
0
rakkad
Asked:
rakkad
  • 7
  • 6
1 Solution
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
1. Can be done in different ways depending upon policys in your organisation, either with:-

a). a dedicated vSwitch and at least two uplinks which connect to your DMZ, and then create a Virtual Machine Portgroup with a network label of DMZ.

b) it can be done with VLANs, and you would pass that VLAN to a vSwitch, and use VLAN tags on the Virtual Machine Portgroup

2. Do you really want to put the Host in the DMZ, we do not generally put hosts in the DMZ, we put Guests in the DMZ using the above, because you've got more network configuration, more ports to open, and the "surface area" is larger, e.g. because you've put the host in the DMZ.

3. There are many, many ports you would need to open, if you vCenter Server is in the Internal LAN

see here:-

Required ports for configuring an external firewall to allow ESX/ESXi and vCenter Server traffic

TCP and UDP Ports required to access vCenter Server, ESXi/ESX hosts, and other network components

So you need to think carefully about actually putty and install the HOST in the DMZ.
0
 
rakkadAuthor Commented:
Thanks for the comment !!

Is there a preferred recommendation and can you forward any possible design configurations ?

Thanks once again
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, it's in my first post.

Do not put the Host in the DMZ, and use 1a and 1b.
0
Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
rakkadAuthor Commented:
Thanks I'll keep you posted how I get on
0
 
rakkadAuthor Commented:
Will it possible to illustrate this in a form a pictorial representation of how It may hang together ?

Thanks
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Yes, no problems, questions please ask....

ESXi Network
this assumes, placement of Host in Internal LAN, DMZ is connected to a vSwitch, and DMZ VMs will connect to this vSwitch only.

No traffic can pass between vSwitches, so is isolated in the switches in ESXi
0
 
rakkadAuthor Commented:
Hi

I have been going over this and still confused as it whether to put the host in the DMZ network (192.x.x.x) or in the internal VLAN 226 (VMware LAN) then connect to the DMZ.

If I we're to put the host in the DMZ straight, how difficult would this be for this host to connect to VCentre  ? What problems could run into ?  In your experience would organisations follow the rule to put the host in the internal LAN then connect to DMZ

Is this way, the DMZ host needs to see the VCentre, as apposed in the reverse way

Also, would you recommend DHCP or keep static IP addresses for VM guests

Thanks

I hope I am clear with the above
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
You will need to open many ports, between vCenter Server on production LAN and ESXi server in the DMZ.

Also your attack profile is higher, putting the entire HOST in the DMZ.

ALL our clients DO NOT put the Hosts in the DMZ, they connect network interfaces on the host to DMZ.

All servers, physical or virtual have Static IP Addresses.
0
 
rakkadAuthor Commented:
So to summarise, from your suggestions I put the new host in the existing Vcentre which is in the VLAN 226 - internal network, followed by Vswitches to connect to the DMZ 192.x.x.x

Thanks again for your speedy response
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Correct, that's how it's done. Reduces attack footprint of not having management Interfaces in the DMZ for the Host Server.
0
 
rakkadAuthor Commented:
I have setup the DMZ VMware setup.  Can you verify the diagram and see if I have done it correctly.

Also, I have noticed that the vmnic0 is showing 10 instead of 1000

Also, vmnic1 to 3 is showing as standby and there is no actually connection, is there any reason for this ?

Can you assist, what can I do to check the above ?

Thanks
image.jpg
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
There is a network fault with vmnic0, e.g. cable is not correct, port is not correct, it should show 1000, not 10.

I would check the port, cable, physical network port.

It looks like you have configured 3 nics, as standby, you will need to edit the vSwitch and decide what to do with these nics?

and move them up into Active or Unused.

Make sure if using 2 or 4 nics, that you have the correct teaming policy and physical switch configuration in place.
0
 
rakkadAuthor Commented:
Thanks forum help in this call your solutions helped alot
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now