configure Mitel and Admin PC on windows 2012 DHCP using a Vlan for each network

[gcuevas]

Greetings All,

i recently replace a linux server that serve as the DHCP and DNS with a Windows 2012 Server. Before it crashed, the phones and PCs will be connected to the proper vlan and IP subnet.
i have follow many forums and i have not been able to figure this out. i was wondering if anyone could help with this issue.
the DHCP is configure with the following options:
006 DNS Server
015 DNS Domain Name
066 Boot Server Host Name
067 Bootfile Name
125 Mitel
128 Mitel TFTP
129 RTC IP
130 Mitel Vendor String
132 Voice Vlan ID 172
133 Priority

066, 067, 125 were not in use on the Linux server, these were added as i found on forums

Currently this is what happes;
1- if the port on the Mitel Vlan ID 172 is tagged and the Admin Vlan ID 192 is untagged as it was with the linux DHCP, the phone will say that TFTP server was not found then it will not pass this = SET 192.168... ICP 172.17... and the PC will get an IP from the correct vlan 192 and will ping 8.8.8.8
2- if the port is untagged vlan 172 and tagged on Vlan 192 then the phone will not pass DHCP; discovery, using option 128+ and the PC will get correct IP address but will not go online, when pinging 8.8.8.8 it reply from 172.17....
3- If the port is untagged vlan 172 and no on vlan 192 then the phone will work and the PC will get ip from the mitel vlan id 172
4- if the port is tagged vlan 172 and no on vlan 192 the same as above on test 3- phone works PC wont work
5- if the port is no on both vlans then phone wont pass DHCP: discovery, main version 02.01.... and PC will get 169... ip
6- if the port is no on vlan 172 and tagged on vlan 192 the same as above on test 5-
7- if the port is no on vlan 172 and untagged on vlan 192 the same as test 2-
8- if the port is tagged on both vlans the same as test 1-
9- yes i tried untagged both but it wont keep both untagged

10- please your assistance will be so much appreciated.

thank you

[sarond]

What type of switch do you have?
Preferably the switch should use CDP/LLDP to switch the phones into the correct VLAN, this is the easiest method.
Do you have routing between the 2 networks?

I would suggest having the port as 172 tagged and 192 untagged as this is standard.
You will still need a DHCP Server in the untagged VLAN to tell the phones where to get their VLAN info from. You will also need to have helpers forward DHCP requests from your network to your DHCP Server.
Just copy the same Mitel options (128,129,130,132,133) to both scopes.
Hopefully the phones will boot into native VLAN get info and release DHCP and then renew into VLAN 172.

I have attached an extract from the Tech Handbook regarding typical network configs.

[gcuevas]

Thank you Sarond for your response,

i have attached both scopes, the correct Vlan for the phone is 299 i just use 172 to correlate the subnet
the switch models are HP 3500 Layer 3 as the core switch and the others are HP 2600 POE/Manage switches.
since this was working with the linux server i assumed the network will be ready with all configuration needed as routing and CDP/LLDP is concerned.
in regards to the DHCP ip Helper, is this required in all switches or just the core switch which does routing or the firewall?
please advise
thank you

[pmhaynes]

Possibly, on the old DHCP you have the data scope set to give out the voice vlan.

So phone would boot get a data vlan IP then be told to got voice vlan.
Phone display would read something like "DHCP releasing"
Then the phone would rebroadcast for DHCP on the voice vlan
I have used this method once along time ago.
We now use the LLDP/CDP method.

The PC's would ignore the VLAN id on the DATA DHCP scope

The switch would be untagged Data vlan. Tagged voice VLAN

hope this helps

[gcuevas]

see screen shots please for details about the CDP/LLDP

[johnp]

I would think you need to let use know how your options are defined. I remember that some of them are long interger versus text, ip address etal.

It maybe be easier to use 43 as text and copy the text from the dhcp helper tool. For certain 125 on newer MS is a fight.

I was just setting up option 125 in a cisco router the other day and found it best to use hex FWIW, also how I did in in Linux

[sarond]

Is your Mitel Controller going to providing DHCP for phones? (As this is what it looks like from your screenshot)

If this is the case then CDP/LLDP should place the phones into the correct VLAN.

[gcuevas]

thank you all for your response,
I still have the same issue where mitel phone and pc do not connect simultaneously.
to answer the last question;  yes mitel controller provides IP address for the phones and windows 2012 DHCP for the admin PCs. i have also used server 2003 and get the same results.
i will provide the booting sequence below

waiting for 802.1x authentication
waiting for LLDP
Main Ver 02.01.00.32 Boot Ver 02.00.00.31
waiting for DHCP Main Ver 02.01.00.32
Vlan 299 Pri 6 _ Main Ver 02.01.00.32
DHCP: Discovery Main Ver 02.01.00.32
DHCP: Discovery Using Option 128+
Vlan 299 Pri 6 _ Using Option 128+
192.168.93.86
TFTP svr unavailable continuing bootup
192.168.93.86 continuing bootup
TFTP svr unavailable continuing bootup
L2&Boot download err continuing bootup
TFTP svr unavailable continuing bootup
Starting Minet.... Main Ver 02.01.00.32
Set 192.168.93.86 ICP 172.17.13.220

windows DHCP is configure as follow:
003      192.168.93.254
006      192.168.93.2 and .22
043      ascii id:ipphone.mitel.com;sw_tftp=172.17.93.220;call_srv=172.17.93.220;vlan=299;l2p=6v6s6;dscp=46v46s26
066      172.17.93.220
067      /sysro/E2T8260
125      ascii id:ipphone.mitel.com;sw_tftp=172.17.93.220;call_srv=172.17.93.220;vlan=299;l2p=6v6s6;dscp=46v46s26
128      172.17.93.220
129      172.17.93.220
130      Mitel IP Phone
132      0x12b
133      0x6

Mitel DHCP

see attache image

[johnp]

is the port your Windows DHCP server only on the pc vlan?

[sarond]

What is the address range supposed to be in the voice vlan? is it 192.168.x.x or 172.17.x.x

There are a few things that I would try. All tests would be with the switch port programmed as tagged voice, untagged data.

• Use default network parameters on phone (Hold down # while phone is booting and configure)
• Set static VLAN ID only on the phone (Hold down # while phone is booting and configure)
• If there is routing between the voice and data networks set the phone into Teleworker mode, after defaulting network parameters again. (Hold down 7 while the phone boots and enter new teleworker address = System IP)

[johnp]

Vlan 299 Pri 6 _ Using Option 128+
192.168.93.86
TFTP svr unavailable continuing bootup
192.168.93.86 continuing bootup
TFTP svr unavailable continuing bootup
L2&Boot download err continuing bootup
TFTP svr unavailable continuing bootup

That has me thinking that the Windows DHCP Server port isn't configured correctly.

Should see a release from the default and get a new value from the MCD. Doesn't look like he has things setup per Mitel's documentation on how vlan ports should be set as. IMHO

[sarond]

Vlan 299 Pri 6 _ Using Option 128+
192.168.93.86
TFTP svr unavailable continuing bootup
192.168.93.86 continuing bootup
TFTP svr unavailable continuing bootup
L2&Boot download err continuing bootup
TFTP svr unavailable continuing bootup

That has me thinking that the Windows DHCP Server port isn't configured correctly.

Should see a release from the default and get a new value from the MCD. Doesn't look like he has things setup per Mitel's documentation on how vlan ports should be set as. IMHO

My thinking as well. Although I would think CDP/LLDP should get it into the correct VLAN

[johnp]

Agree, but the same DHCP server would still fubar the connection, if not restricted. IMHO

[pmhaynes]

I have scanned through the posts so please forgive me if i repeat someone else post

From memory if you are using LLDP/CDP nothing is needed in the default vlan dhcp.
also in the 3300 dhcp vlan is not needed either. phone is already on correct vlan

i would just have 128 129 130 in the 3300 nothing in the windows dhcp

if not using LLDP/CDP

just have vlan in windows dhcp server (might need 130 also)
phone will get ip then relase ip (might say "rel" or rej"
then it will send another request on the vlan u jst gave it

again in the 3300 vlan is not needed.

what vlan do you have programmed in the 3300 ip section. i always left this at default of 1

Im not saying your method is wrong just not the method i have seen used


hope this helps