How to Get DHCP from a Windows 2012 Server for a VLAN

Hello,
    We have the following Situation:
VLAN 1 = DATA
VLAN 20 = PHONES
Windows Server 2012 - DC & DHCP - This is a VM
Cisco 3560 Switch

Basically, we need the port that the Server is plugged into to be able to process DHCP requests from both VLANS. Unfortunately, each port can only belong to one VLAN, and even if we set Voice-Vlan as 20 on the port, it does not hand out DHCP addresses. If we set it as a member of 20, we loose data connectivity. How do we go about doing this?
JesusFreak42Asked:
Who is Participating?
 
Tim PhillipsWindows Systems AdministratorCommented:
You need to do IP Helper addresses.  This is setup on your router.  The router is told where to get DHCP leases.  Do you have a Cisco router?  Then the request is correlated with your IP Scopes on the server.
0
 
Wylie BayesNetwork Technician IIICommented:
To follow up what Tim is saying about the IP Helper addresses he is correct.

It is very much possible to have more than one vlan assigned to a single port.  It's called "Trunking" , specifically 802.1q.   So by configuring a port as a Trunk you can say allow vlans 1, 2, 3, 4 and 5 to all talk on this port.
0
 
naderzCommented:
Before we begin: it is best practice to NOT use Vlan 1. Create another Vlan for Data and use that instead of 1.

Whether you use Vlan 1 or not here is the procedure:

On the switch create two virtual interfaces: one for the Data Vlan and one for the Voice Vlan. I will use your examples above:

interface vlan 1
 description Data
 ip address give-it-some IP address

interface vlan 20
 description Voice
 ip address give-it-some IP address
 ip helper-address ip-address-of-the-dhcp-server

plugin the dhcp server in an interface on the Data Vlan (in your case Vlan 1)

And, as long as your DHCP scopes are setup correctly all should work.

Please ask if any of this is not clear.
0
 
R_EdwardsCommented:
VMware recommends utilizing VLAN technology to establish dedicated subnets for ESX/ESXi management, VMotion, and iSCSI network traffic.

 Unnecessary VLAN traffic on a TRUNK port that connects to ESX can cause major performance issues.

you basically need to trunk your switchport on your switch.

•interface GigabitEthernet1/1
•description VMware ESX - Trunk A - NIC 0 – Port Description
•switchport trunk encapsulation dot1q – ESX only supports dot1q and not ISL
•switchport trunk allowed vlan 100,200 – Allowed VLANs
•switchport mode trunk – Enables Trunk
•switchport nonegotiate – ESX/ESXi does not support DTP dynamic trunking protocol. When configuring trunk port, set it to nonegotiate.
•spanning-tree portfast trunk – Enables PortFast on the interface when it is in trunk mode


on the vm vswitch side
•esxcfg-vswitch [options] [vswitch[:ports]]
•esxcfg-vswitch -v [VLANID] -p [port group name] [vswitch[:ports]]
•esxcfg-vswitch -v 200 -p "Virtual Machine Network 2" vSwitch1


here is a link:

http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1004074

-=Richard
0
 
naderzCommented:
I must have been typing when Tim was posting. sorry about that. IP Helper-Address is recommended
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.