Author Topic: MiVB 7.2 and BlueCat DHCP Server  (Read 1453 times)

Offline BarryNI86

  • Contributer
  • *
  • Posts: 7
  • Karma: +1/-0
    • View Profile
MiVB 7.2 and BlueCat DHCP Server
« on: December 21, 2016, 06:19:31 PM »
Hi All,

This is my first post so please bare with me.

I have been working with a customer of ours and we are having issues with DHCP. It appears they are having issues with their BlueCat DHCP server. This is a centralised DHCPserver for them. The only way I have been able to get DHCP working is to advise them to include the old options 128-133 as firstly they cannot use Option 125 because it simply won't work and option 43 is already in use by Cisco CCM. I have checked the string they are using and it appears fine:

ipphone.mitel.com;sw_tftp=10.114.x.x;call_srv=10.114.x.x;vlan=900;l2p=6v6s6;dscp=46v46s26

I have upgraded their system tonight and the phones just got stuck on 'Contacting Server'. To prove that DHCP was the issue, I have statically assigned phones to get them back in service. The phones are a mix of 5312/5330/5304.

I have no experience with BlueCat DHCP servers so I am basing all the advice I am giving their IT on Windows. Anyone any experience with BlueCat?

Any help would be great.

Thanks


Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2202
  • Country: us
  • Karma: +66/-0
    • View Profile
Re: MiVB 7.2 and BlueCat DHCP Server
« Reply #1 on: December 21, 2016, 07:10:31 PM »
Don't know BlueCat, but on a linux box I had 125 set as hex and used the tool to generate the string. I did have to enter some colons though

Offline iboyd

  • Jr. Member
  • **
  • Posts: 61
  • Country: us
  • Karma: +1/-0
    • View Profile
Re: MiVB 7.2 and BlueCat DHCP Server
« Reply #2 on: December 21, 2016, 07:32:45 PM »
The server type should not be an issue as DHCP is a defined protocol, not a private one.

As such try the following string:
....Tid:ipphone.mitel.com;sw_tftp=(CALL SERVER);call_srv=(CALL SERVER);vlan=900;l2p=6v6s6( could just try it as 6); dscp=46v46s26 (or try v46s46).

Also convert it to hex, making sure the .... is converted as NULL hex instead of 2E 2E.  NULL should be 00 00 04 03.  If that doesn't work i will run it thru the Option 125 converter and see if that makes a difference. 

Also you only need to define Opt 43 and Opt 125 for the phones, it's the paging adapter that really needs all the fluff (stupid paging adapter).

Another thought is to flip DHCP to the 3300 and then you can definitely point the figure at the DHCP server being mis-configured.

-Ian

Offline BarryNI86

  • Contributer
  • *
  • Posts: 7
  • Karma: +1/-0
    • View Profile
Re: MiVB 7.2 and BlueCat DHCP Server
« Reply #3 on: December 22, 2016, 05:09:38 AM »
Thanks Ian and John. I have forwarded the suggestion onto the customer.

I will let you know the outcome.

Sent from my SM-N9005 using Tapatalk


Offline BarryNI86

  • Contributer
  • *
  • Posts: 7
  • Karma: +1/-0
    • View Profile
Re: MiVB 7.2 and BlueCat DHCP Server
« Reply #4 on: February 26, 2017, 01:44:34 AM »
Hi All, a long time coming but the issue was on the BlueCat server.

Sent from my SM-N9005 using Tapatalk



 

Sitemap 1 2 3 4 5 6 7 8 9 10