Author Topic: DHCP on MiCollab  (Read 1889 times)

Offline nowickj

  • Jr. Member
  • **
  • Posts: 61
  • Country: pl
  • Karma: +1/-0
    • View Profile
DHCP on MiCollab
« on: February 09, 2016, 09:12:54 AM »
I haved configured DHCP on MiCollab and it looks like that:
Global  3 routers  10.127.10.254   
Range: 10.127.10.35  125 Mitel [id: 1027]  id:ipphone.mitel.com;call_srv=10.127.10.32;l2p=6s3m4v6;vlan=310;dscp=46s24m34v46;sw_tftp=10.127.10.32 
10.127.10.32 - IP Address of My MiCollab server. MiCollab is based on MiVoice Business.
All phones are located in lab room and switched to Huawai l3 switch which is trunked to Cisco switch. MiCollab and MiVoice Business are instaled on Virtual Machines and are located on the phisical serwer which is switched to Cisco switch to the port which is assigned to 310 Vlan.
When I configured manualy phone with IP address it is wark, but from DHCP it does not.

Logs look like that:
2016-02-09 15:02:51.011185500 DHCPREQUEST for 10.127.10.40 (10.127.10.32) from 08:00:0f:72:21:50 via eth0
2016-02-09 15:02:51.011289500 DHCPACK on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:02:52.119426500 DHCPRELEASE of 10.127.10.40 from 08:00:0f:72:21:50 via eth0 (found)
2016-02-09 15:03:03.612932500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:03:03.613162500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:03:07.612947500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:03:07.613110500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:03:15.613185500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:03:15.613307500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:03:31.713167500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:03:31.713284500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:04:03.718195500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:04:03.718421500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:07.714266500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:08.000346500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:08.010242500 DHCPREQUEST for 10.127.10.40 (10.127.10.32) from 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:08.010344500 DHCPACK on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:09.039699500 DHCPRELEASE of 10.127.10.40 from 08:00:0f:72:21:50 via eth0 (found)
2016-02-09 15:05:14.313771500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:14.313899500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:18.413917500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:18.414040500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:26.414085500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:26.414210500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:42.414324500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:05:42.414430500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:06:14.514190500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:06:14.514349500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:18.615457500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:19.001178500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:19.011049500 DHCPREQUEST for 10.127.10.40 (10.127.10.32) from 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:19.011144500 DHCPACK on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:20.059173500 DHCPRELEASE of 10.127.10.40 from 08:00:0f:72:21:50 via eth0 (found)
2016-02-09 15:07:25.514507500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:25.514535500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:29.614345500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:29.614465500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:37.614347500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:37.614471500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:53.715111500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:07:53.715123500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:08:25.815271500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:08:25.815425500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:29.921423500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:30.000276500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:30.010302500 DHCPREQUEST for 10.127.10.40 (10.127.10.32) from 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:30.010396500 DHCPACK on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:31.079958500 DHCPRELEASE of 10.127.10.40 from 08:00:0f:72:21:50 via eth0 (found)
2016-02-09 15:09:43.315492500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:43.315642500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:47.415188500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:47.415292500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:55.415324500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:09:55.415434500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:10:11.515456500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:10:11.515577500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:10:43.616843500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:10:43.617025500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0
2016-02-09 15:11:47.621570500 DHCPDISCOVER from 08:00:0f:72:21:50 via eth0
2016-02-09 15:11:48.001019500 DHCPOFFER on 10.127.10.40 to 08:00:0f:72:21:50 via eth0



Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4100
  • Country: us
  • Karma: +133/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: DHCP on MiCollab
« Reply #1 on: February 09, 2016, 02:11:27 PM »
I's confused here... what is offering DHCP in the voice VLAN310, MiCollab? And MiCollab is at 10.32? And the 3300 is at 10.35?

If so, your option 125 is wrong... Actually I typically use Option 43 since it is an ASCII text option and easier to configure.

If your phones are already in the VLAN 310, you must not define tha VLAN tags, the phone will continue to request DHCP in the VAN specified in the DHCP offer until a DHCP offer is received with no VLAN ID specified, so it would look something like this:

 id:ipphone.mitel.com;call_srv=10.127.10.35;sw_tftp=10.127.10.35;l2p=6;dscp=46

and that's it.

How are the phones getting to VLAN 310, via LLDP, Cisco SmartPort/Auto Voice VLAN, hard coded, or via a VLAN1 DHCP server offer?
« Last Edit: February 09, 2016, 02:24:26 PM by acejavelin »

Offline nowickj

  • Jr. Member
  • **
  • Posts: 61
  • Country: pl
  • Karma: +1/-0
    • View Profile
Re: DHCP on MiCollab
« Reply #2 on: February 10, 2016, 02:45:38 AM »
Thanks You very much:) I have changed for id:ipphone.mitel.com;call_srv=10.127.10.31;sw_tftp=10.127.10.31;l2p=6;dscp=46 where 10.31 is the 3300 and now it is working :)

Offline acejavelin

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4100
  • Country: us
  • Karma: +133/-0
  • High-tech, heavy metal redneck!
    • View Profile
    • Like what I do and wanna help out? Send me a donation!
Re: DHCP on MiCollab
« Reply #3 on: February 10, 2016, 09:44:38 AM »
Thanks You very much:) I have changed for id:ipphone.mitel.com;call_srv=10.127.10.31;sw_tftp=10.127.10.31;l2p=6;dscp=46 where 10.31 is the 3300 and now it is working :)
Awesome! Glad I could help.

Offline AndyJanes

  • New Member
  • *
  • Posts: 1
  • Country: gb
  • Karma: +0/-0
    • View Profile
Re: DHCP on MiCollab
« Reply #4 on: May 19, 2016, 05:49:23 PM »
Hi,

Just wanted to take the time to express my thanks as I registered on this forum about 15 minutes ago and I've already found the solution to my problem in this post!  I have never read any documentation about the phones automatically restarting if the vlan was specified in the option 125 string!  Taken that out the appropriate dhcp scope config and now the phones boot correctly!

Great tip!  :)

Thanks



Andy


 

Sitemap 1 2 3 4 5 6 7 8 9 10