To validate the NAT scenario, a Ubuntu server VM was created called cape-may. This is just the CRM standard Ubuntu build, with IP forwarding and IP Tables configured.
One NIC card on cape-may is connected to the internal LAN while a 2nd NIC was placed on the dvs-Production distributed switch (Gig-e). Client devices that need access to the LAN and internet can be placed on dvs-Production with a gateway address of cape-may on gig-e and a DNS setting of the LAN switch.
Some preliminary testing using the Win2k VM win2kmove validated the config quickly. Both ping access and web browser internet is functioning. It is important to add the DNS entry on the client, since that is how internet names are resolved. This will become more complicated once AD is moved (more on this later).
In the equipment closet configuration, the LAN card will probably be a USB wireless network adapter.
The next step is to configure VMware Tools on cape-may to get better throughput by loading the Tools' NIC drivers. This will happen in the next week or so.
The other item that needs testing is the ingress access which is required to get to the vCenter and ESX servers. This might require additional configuration on the NAT server.
No comments:
Post a Comment