Solved

Setting up a DMZ using ESX 3.5

Posted on 2008-11-01
2
1,459 Views
Last Modified: 2012-05-05
I ma trying to get a DMZ up and running using ESX 3.5. No matter what I try the VM can not ping the gateway. I have 8 NIC's per ESX host. 2 are being used for Service Console 1, 4 are dedicated the VM network that has 3 VM Networks (internal / DMZ / Public) and 2 for Service Consoe 2 / VMkernal. I added a VlanID of 225 to the DMZ virtual network and followed a guide on setting up the port on the switch that connects to the DMZ interface of the ASA. I creaded a vlan for this port on the physical switch 225 and enabled trunking dot1q and connected the vlan to the port.

I also enabled in the inside interface of the ASA to the switch to use trunking dot1q and assigned it vlan 201. Once that happed I lost all communication, as I thought the trunking would allow other vlan to pass thru from the switch. I am at a total loss, any guiedence would be greatly appreciated.

0
Comment
Question by:viperhost
2 Comments
 
LVL 23

Assisted Solution

by:bhanukir7
bhanukir7 earned 500 total points
ID: 22856283
Hi viper,

A good place to start with would be this step by step on mikes blog

http://www.mikechammock.com/2008/06/setting-up-dmz-in-esx-35.html

bhanu
0
 

Accepted Solution

by:
viperhost earned 0 total points
ID: 22857594
Excellet link, thank you very much!
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If we need to check who deleted a Virtual Machine from our vCenter. Looking this task in logs can be painful and spend lot of time, so the best way to check this is in the vCenter DB. Just connect to vCenter DB(default DB should be VCDB and using…
When rebooting a vCenters 6.0 and try to connect using vSphere Client we get this issue "Invalid URL: The hostname could not parsed." When we get this error we need to do some changes in the vCenter advanced settings to fix the issue.
Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…
Teach the user how to install and configure the vCenter Orchestrator virtual appliance Open vSphere Web Client: Deploy vCenter Orchestrator virtual appliance OVA file: Verify vCenter Orchestrator virtual appliance boots successfully: Connect to the …

805 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question