Mitel Forums - The Unofficial Source
Mitel Forums => MiVoice Office 250/Mitel 5000 => Topic started by: cgashlin01 on June 03, 2015, 03:42:05 PM
-
So I am implementing vlans and am testing currently.
I am moving my DHCP server to something else(Windows 2012).
Issue.....
Phone boots and says that option 129 is missing. even though I have it in my DHCP scope as an option that is set as IP address and have it set to my phone system.
Any idea?
-
I will add that I have it setup in my switch for DHCP helper. It works iwth a PC no problem.
-
cgashlin01,
Why don't use just use the DHCP server in the 5000? What we would be looking for those is option 125 or 43 though.
Thanks,
TE
-
If you have access to the option 125 config tool it would be helpful. What DCHP server are you using? The process the phone goes through on boot is to use lldp, if unavailable use dchp to learned vlan, priority, phone system address and dscp values.
Generally the first dhcp request is on the untagged default vlan, the dhcp sever would have the necessary info and after the phone learns where it go it releases that lease. Then sends out a new vlan tagged one.
The tool creates both an ascii and hex representation of option 125.
The phone will also respond to option 43 as well as the old Mitel 128, 129, 130, 132, 133, 134 values (I may have some wrong numbers) but this is a quick overview from memory.
The 125 hex string starts with the mitel vendor code followed by a lenght of string value the the hex representation of ipphone.mitel.com;tftp_srv;call_srv,l2p and other values. These all get done by the tool. You may be able to look in you system to see the true format.
If using 43 you don't need the vendor id or string length values.
-
I am new to this MItel system. SO I am unware of option 125 config tool.
I am using Server 2012 DHCP Server
-
cgashlin01,
Does your switches support LLDP-MED or CDP?
Thanks,
TE
-
Found this string online
"id:ipphone.mitel.com;sw_tftp=192.168.11.10;call_srv=192.168.11.1;vlan=11;l2p=1v6s6;dscp=46v46s26;"
You could modify and use for option 43 type ascii string
sw_tftp and call_srv usually is the phones sytem, vlan would the phone vlan, l2p(layer 2 priority) (default value)v(voice value)s(signalling value) same scheme for dscp
-
my vlans are untagged so it should not care about the vlan. Should this be the only option in my DHCP?
-
My switch does support LLDP
-
I tried LLDP and it still says option 129 missing.
My vlans are untagged.
-
Using option 43:43 is all it says on the phone when i use option 43 but it does not work. Just sits there.
-
LLDP-MED support?
The recommended switch configuration of wanting to use the port on the back of the phone for the data vlan would be to configure the phone ports as untagged in data and tagged in voice. dchp server port only in data untagged, phone system only invoice untagged or tagged depending on system. some type of routing between the 2 wheter is be separate interfaces where one is only one data and the other only on voice or router on a stick where both are on the same interface and the connected port would be the same as a phone port.
You then can setup the qos queues to prioritize the voice traffic.
-
Its an SG300 layer 3 switch.
-
cgashlin01,
Sorry I had to step away for a bit.
So LLDP-MED or CDP is used in order to get the phones on the right VLAN as they boot up. The command most switches use for this is the word "voice" under the Voice Vlan. This will provide the phone with the VLAN ID and its L2P [Layer 2 Priority].
As JohnP stated the ports the phones are in should be untagged for the native VLAN, which is normally data, and tagged for the voice VLAN. The port the phone system should be in should be untagged for the voice VLAN and depending on the switch No Untagged for the Data VLAN. That way no native VLAN traffic will be mistakenly sent to the 5000. So, when the phones come up they get their VLAN ID and then send out their DHCP request on the Voice VLAN and the only thing that will respond to them is the 5000. To make things better if you don't remove the flag from Client's Vendor Class ID Must Match Name for the DHCP Server Range on the 5000 then even if a PC were to send a request it would be ignored.
Thanks,
TE
-
My comment about tagged or untagged for the phone system was the 3300 can be set to operated with a tagged value
-
Johnp,
I kind of figured that was where you were going, but we can't do that on the 5000. I was knocking your answer either, I just wanted to clarify my original post as to why I asked about LLDP-MED or CDP.
Thanks,
TE
-
Kind of like why I put the LLDP-MED question, when answered it does LLDP :) Didn't think you were knocking me, just wanted to add the additional info to clarify.
It is more difficult to answered such a question when doing it from memory without anything open to referrence. Know how to do it, even figured out option 125 on a linux DHCP box years ago when they first moved to it instead of the 128 etc options.
-
Johnp,
We don't even try to setup a customers DHCP server anymore as it is always a headache. This way if their DHCP server has an issue the phone will still be ok.
Now, what we normally do is set at least one of the answer point phones to be a static IP address so that if the DHCP server on the 5000 has an issue we at least have one phone still working.
Thanks,
TE
-
So to clarify
I have my DHCP server running in VLAN 1 untagged. If I plug a comptuer into vlan 2 i get a 9.0 IP if I plug a comptuer in vlan 1 i get a 0.0 IP.
My phone system right now is in the 0.0 network
When I plug my phone into the VLAN 2 Tagged port it boots but it ignores everything and just pulls from our old DHCP server.
When I disable the old DHCP server and it is forced to pull from our new one. It tells me option 129 is missing.
If only I could get the option 129 to work.
-
May I also add that it is ignoring the option 43. It just strait up says no vlan when booting. It once said VLAN2
-
If you are using untagged switch ports then you don't want to use a vlan option for the phone otherwise it will tag the packets and hang.
If you are tagging the voice vlan on the switch then you would specify a vlan in your options if not then treat it as if there are no vlans.
Try this:
Plug the phone in and hold down the 7 key until “Config Teleworker?” appears
Press * for yes
Press # for new
Enter IP address of PBX (Using # for . if needed)
Press the volume down key to save.
Press * to save changes and reboot phone.
This will bypass Mitel specific options and use normal DHCP like a PC would.
The difficulty with option 125 and Windows Server is that it is an encapsulated option and isn't programmed directly from the gui.
Check the attached guide to get you started and use the Config Helper to get you started.
-
Does the Mitel 5000 support multiple gateways or routes?
-
cgashlin01,
What exactly are you referring to; what are you trying to do?
Thanks,
TE
-
I may just wait until a weekend to adjust all the IPs. since my mitel does not have the correct gateway in for the new VLAN I cannot connect to eh Mitel from the 9.1 network. I will have to try once I adjust the gateway on the Mitel.
-
cgashlin01,
Ah, I get what you were trying to do now. Unfortunately the 5000 allows for only one gateway. If you do change it then you will need to do a reset after performing a backup database save.
Thanks,
TE
-
Oh fun, ill have to schedule the reboot.
Hopefully my DHCP works after the reboot and can supply the phones. If not another headache will occur.
-
cgashlin01,
That is why we don't use third-party DHCP servers, too much of a headache. Not sure why you want to recreate the wheel, but we are here to help if we can.
Thanks,
TE
-
To make things really awesome. Now all of my 5320 phones are pulling weird stuff.
They are booting up and thinking they are on VLAN 2 then just sit there at DHCP: Discovery. I have no VLANS currently. I removed all of them. LLDP is disabled on everything. It is back to what it used to be.
Funny thing.....
If I plug into another switch it works.
-
Turns out LLDP is scary. it some how replicated to the POE switch and was telling it to look on VLAN2. SURPRISE!!!!
-
cgashlin01,
That is one of the issues of working on a live system. Welcome to the club!
Sorry,
TE
-
So does anyone have experience using Server DHCP?
-
cgashlin01,
We all do since the built-in DHCP server only came out at 6.0.
So, if you want to use your DHCP Server there are a few things that mess up in the process.
1. DHCP Server cannot read tagged VLAN traffic properly and won't respond correctly. Solution: put a second NIC in the server and put it on a port that is untagged for the voice VLAN.
2. Don't have LLDP or CDP running and all DHCP traffic stays on the Data Network; the DHCP server responds but issues a data VLAN address and you get the 129 error since it doesn't have option 43 or 125.
3. You get the DHCP from the Voice VLAN but you still get an error as Option 125 was setup improperly or the DHCP server can't support encapsulated options. Solution use option 43 instead.
Have you used the attached .zip file that Sarond posted to setup option 125? I know you can't load it on a newer server and get it to work, but you can load it on your PC and run it just to get the correct configuration option and manually do the rest by following the document.
Thanks,
TE
-
I am scheduled on the 20th to do the cutover at work with the VLAN I will have to test it at that point. I do have a 2nd NIC I can utilize in my ESXi box that is holding my servers.
-
cgashlin01,
That should solve your problem with the DHCP server seeing the VLAN traffic properly, but you still have to decide on whether you want to use option 43 or 125 and then set them up properly.
What is your reason for wanting to use an external DHCP server in the first place?
Thanks,
TE
-
If the DCHP server is only on the data vlan and has both scopes setup properly with the Mitel option and the voice vlan has an ip helper address that points to this server and routing works properly, then it should work IMHO.
Much easier to have the phone system handle DHCP for the phones natively and just have the options setup properly in the other DHCP server.