JesusFreak42
asked on
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?
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?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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
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
I must have been typing when Tim was posting. sorry about that. IP Helper-Address is recommended
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-ser
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.