No DHCP - Vlan Issue? 1

[snootalope]

I've got a test lab setup for our 8.6 call managers running in vmware. Everythings up and working. However, I can't get any phones to pick up IP addresses from my publisher/dhcp server.

I can ping everything from all directions no problem. I'm guessing it's a vlan tagging issue, but not sure where to fix this beings I do not have a router in place here, only a cisco 3524 poe switch.

Call Managers - 172.16.1.1 (publisher) Default Gateway is 172.16.1.254
...DHCP subnet is 172.16.1.0/24
.
VMware vSwitch - no vlan tagging
.
Cisco 3524 - IP Vlan1 172.16.1.254
...The port that connects switch to vmware host...
switchport trunk encapsulation dot1q
switchport access vlan 172
switchport mode trunk
switchport vocie vlan 172
spanning-tree portfast
...The port I have a phone plugged into...
switchport trunk encapsulation dot1q
switchport mode trunk
switchport vocie vlan 172
.
.

Again, I can ping everything in and out of the switch just fine. I just can't get anything on the physical switch to pick up a dhcp address from 172.16.1.1.

 

[imbadatthis]

If Im reading this right, your DHCP is on vlan 1. (why oh why are you using vlan 1?) ...

and your voice ports are on vlan 172 ....
so no talky talky ...

put your dhcp on vlan 172 and that could work..
you may have to enable dhcp-relay ..
you May have to provide correct dhcp options for your phones depending on what they are...

cheerios.


We must go always forward, not backward
always up, not down and always twirling twirling towards infinity.

 

[VinceWhirlwind]

No, imbadatthis, you didn't read it right.

OK, what kind of phones do you have?

Your port configuration is a mess.

switchport trunk encapsulation dot1q
switchport access vlan 172
switchport mode trunk
switchport vocie vlan 172
Is truly horrible. It's either a trunk, OR it's ACCESS, not both. As it is the trunk int your VMWARE cluster, I suggest this should be a trunk, so:
switchport trunk encapsulation dot1q
switchport mode trunk

Your phone port config
switchport trunk encapsulation dot1q
switchport mode trunk
switchport vocie vlan 172
is even worse. This is probably what's confusing your phones - do a packet capture and you might find they're sending out their DHCP request on VLAN1.
If you have Cisco phones, you probably want:
switchport mode access
switchport voice vlan 172

Unless the phone can discover that is is meant to be on VLAN172 (via CDP and the "switchport voice vlan 172" config) then it will boot up in and send a DHCP request into VLAN 1.

 

[snootalope]

Thanks Vince. This is what happens when I only get to work on switches once every five years or so.

The DHCP is now working after adding the access command. Thanks again.