ryanbarnes86
asked on
ShoreTel DHCP Windows Server with Cisco Switches
Hello All,
I installed a new ShoreTel system and I discovered that the ShoreTel servers do not hand out DHCP. The vendor we are working with gave info on setting up option 156 in the Windows DHCP scope. Right now, we are replacing the Cisco system and they were on a 10.10.1.x subnet and scope for the phones. Our switches and routers are all Cisco devices and have VLAN999 assigned for the phones and VLAN1 for data traffic.
We are running out of IP addresses for the internal DHCP scope so I will need to change that at some point; however, wondering if anyone can help me out? I have a dedicated DHCP server and while I did have two servers (one with about 70 percent of the addresses and then the second as a failover), I went to one because with the phone system, I don't want to make it very hard to manage, etc...
Read so much about option 156 and Cisco switches but somehow, it just isn't working. It would be nice to have the Cisco router hand out the IP's but when we had that setup, the phones get an internal IP address of 192.168.1.x, see the Option 156 and then when they are supposed to then get the 10.10.1.x address, they don't. They stay at the "Getting DHCP" screen. I then setup a Windows DHCP server with a second network card that had the IP of 10.10.1.9 on it and then the DHCP range was 10.10.1.50-200. The phones did the same thing! AHHHH!!!!
Killing me. thoughts?
I installed a new ShoreTel system and I discovered that the ShoreTel servers do not hand out DHCP. The vendor we are working with gave info on setting up option 156 in the Windows DHCP scope. Right now, we are replacing the Cisco system and they were on a 10.10.1.x subnet and scope for the phones. Our switches and routers are all Cisco devices and have VLAN999 assigned for the phones and VLAN1 for data traffic.
We are running out of IP addresses for the internal DHCP scope so I will need to change that at some point; however, wondering if anyone can help me out? I have a dedicated DHCP server and while I did have two servers (one with about 70 percent of the addresses and then the second as a failover), I went to one because with the phone system, I don't want to make it very hard to manage, etc...
Read so much about option 156 and Cisco switches but somehow, it just isn't working. It would be nice to have the Cisco router hand out the IP's but when we had that setup, the phones get an internal IP address of 192.168.1.x, see the Option 156 and then when they are supposed to then get the 10.10.1.x address, they don't. They stay at the "Getting DHCP" screen. I then setup a Windows DHCP server with a second network card that had the IP of 10.10.1.9 on it and then the DHCP range was 10.10.1.50-200. The phones did the same thing! AHHHH!!!!
Killing me. thoughts?
ASKER
Getzjd - Thanks for the info. Can you please help me out on the DATA VLAN pool? Forgive me for the stupid question. Do I need to have a Windows server with a 10.10.1.x IP/subnet and Windows handing out the IP, too? Or should I just go with the router one like you listed above and have the Option 156 in the Windows DHCP scope?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
THANKS! Will keep you updated
On the Cisco, you will need something similar. Keep in mind, this is an Adtran config v 10.03 firmware. Most of your commands in Cisco IOS are identical.
ip dhcp pool "DATA"
network 10.xx.xx.xx 255.255.248.0
domain-name "xxxxxxxxxxxxxxx""
dns-server 10.xx.x.xx 10.xx.x.xx 10.xxx.x.x
netbios-node-type h-node
default-router 10.xx.xx.xx
lease 5
ntp-server 10.xxx.x.x
option 156 ascii "ftpservers=10.xxx.x.xx, country=1, language=1, layer2tagging=1, vlanid=35"
!
ip dhcp pool "VOICE"
network 192.168.xx.x 255.255.255.0
dns-server 10.xx.xx.xx 10.xx.xx.xx 10.xx.xx.xx
netbios-node-type h-node
default-router 192.168.xx.xx
lease 7
ntp-server 10.xxx.x.x
option 156 ascii "ftpservers=10.xxx.xx.xxx,
!
After this make sure your switch ports are set to trunk and that your vlans are properly setup on the Cisco switch and that routing between vlans is in place.