Author Topic: Best Practices for DHCP server on different subnet  (Read 2887 times)

Offline iceman

  • New Member
  • *
  • Posts: 2
  • Country: us
  • Karma: +0/-0
    • View Profile
Best Practices for DHCP server on different subnet
« on: April 11, 2013, 11:09:05 AM »
We have are connecting a new segment to our network.  We have a existing Mitel system at the current location that is serving DHCP for phones.  What is the best practices for DHCP at the new location to use our mitel controller at the co.  Should I use the Mitel controller, switch at the new location or router or server??



Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2202
  • Country: us
  • Karma: +66/-0
    • View Profile
Re: Best Practices for DHCP server on different subnet
« Reply #1 on: April 11, 2013, 12:22:41 PM »
How many phones will be at the remote site?

Offline iceman

  • New Member
  • *
  • Posts: 2
  • Country: us
  • Karma: +0/-0
    • View Profile
Re: Best Practices for DHCP server on different subnet
« Reply #2 on: April 11, 2013, 12:41:19 PM »
About 10.

Offline martyn

  • Hero Member
  • *****
  • Posts: 688
  • Country: au
  • Karma: +10/-0
    • View Profile
Re: Best Practices for DHCP server on different subnet
« Reply #3 on: April 11, 2013, 06:54:51 PM »
Given that you are running voice over it, I would assume that your WAN link has low enough latency, so running DHCP off of the Mitel should be ok, but if you have DHCP infrastructure at the remote site it would probably be better off being run there.

Offline mgodinez

  • Jr. Member
  • **
  • Posts: 51
  • Karma: +0/-0
    • View Profile
Re: Best Practices for DHCP server on different subnet
« Reply #4 on: April 11, 2013, 08:20:19 PM »
Hello,

From your diagram, it seems like you have your network/sites setup to get DHCP from the mitel controller already.

Assuming you are using routers to reach your remote location - and the links b/n sites are in the same subnet...it should just work.  As long as you setup your ACLs, static routes or routing protocol(s) correctly. 

However, you can configure DHCP on your remote site router for the 'phone' network.

Regardless, I would strongly recommend you deploy QoS over the link - so the phones don't saturate it.  Although you only have 10 phones, and assuming dial tone all comes from the CO - voicemail, and other services can saturate the link under certain circumstances.

Regards,

Mike G.

Offline LoopyLou

  • Hero Member
  • *****
  • Posts: 556
  • Country: ca
  • Karma: +7/-0
    • View Profile
Re: Best Practices for DHCP server on different subnet
« Reply #5 on: April 12, 2013, 08:49:01 AM »
No real reason why you can't use the 3300 as long as you configure the DHCP helper ( DHCP relay or whatever HP calls it on the procurve ) correctly and create a subnet for the remote phones in the 3300. No reason not to use a local source if you don't want to have to setup the helper or have your DHCP go across the link between sites. 


 

Sitemap 1 2 3 4 5 6 7 8 9 10