Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Mitel VLAN issue 1

Status
Not open for further replies.

optonic

Programmer
Mar 22, 2006
27
NL
Good day to everybody.

I have some wierd issues.

We have a separate vlan for our phones (VLAN 20)
For end-users we use (VLAN 16)
For It usage we use (VLAN 26)
The switches are setup to use trunking (cisco) and tagged untagged (procurve) This normally worked perfect.
I have setup option 125 on the DHCP server.
Everything has worked but now strange things happen.

When I use the procuve switch and the vlan is set to vlan 16 untagged and vlan 20 tagged the phone boots fine. (getting a 10.131.20 address)
When I set it to vlan 26 untagged and vlan 20 tagged. The phone boots and it's getting a 10.131.26 address.....??!!??

I have now also this on the cisco switches but when the port is setup to use vlan 16 and vlan 20 the phone boots to 10.131.26. ????!!

There is an issue somewhere but I have no idea where to look at the moment.
 
The phones are made so that if they get an IP address and a VLAN ID they will not use the IP address, but reboot and reboot in the just assigned VLAN.
If your phones get an IP address from the 26 subnet it looks like the phone is not getting the VLAN ID delivered.
 
Hi,

when the phone is booting its telling "VLAN ID 20 PRIO 5" using option 125.
And then the ip 10.131.26.*
Then the phone hangs, or continues, but using the wrong ip.
 
I tried to switch back to option 128.
But the same happens. "VLAN 20 PRIO 5 USING OPTION 128+"
but then it boots again to "10.131.26.13 USING OPTION 128+" and it hangs.

 
Remember to inpput your VLAN as HEX!

Vlan 20 (Decimal) is 16 (Hex)

**********************************************
What's most important is that you realise ... There is no spoon.
 
Sorry I was coverting the wrong way.

20 (Decimal) is 14 (Hex)
16 (Decimal) is 10 (Hex)
26 (Decimal) is 1A (Hex)


**********************************************
What's most important is that you realise ... There is no spoon.
 
You using LLDP on the HP to deliver the initial VLAN info?


The single biggest problem with communications is the illusion that it has taken place.
 
When using the dhcp config tool. Do you I need to put in the hex?
 
I'm not sure when using the DHCP helper whether you should use decimal values or not. Most DHCP servers require the value in hex.

Rereading your original post, it would seem that you are getting an IP address from the untagged side (this would be normal for first DHCP discovery). Do you have option 125 enabled on the 10.131.26.X network to tell the phone it requires VLAN 20? I suspect not.

You could try statically assigning the VLAN and Priority and see what happens then.

**********************************************
What's most important is that you realise ... There is no spoon.
 
I have seen this a number of times and the cause is one of two things.
1 - DHCP relay is enabled on the Procurve switch. you can verify by going to a command line interface in config mode and entering "show dhcp-relay". you disable it by entering "no dhcp-relay" then "write memory"
2 - your data DHCP server is vlan aware and it is connected to a port that set for untagged data / tagged voice. it sees the DHCP discovery on the voice vlan and responds. the solution is to make sure that the port is untagged data / no to the voice vlan.

back in the early days we would untag data / tag voice on all ports other than the one for the ICP. then the customer would upgrade their DHCP server from win 2k to win 2k3 and then a couple of weeks later a phone would reboot and would do exactly what you describe. get a data address, release it and rebroadcast on the correct vlan and get the data address again.
 
You may also want to look at the ip helper-address for that VLAN on the HP switch.

show ip helper-address
 
To RossBC,

You did it!!! It was indeed that my DHCP server has an tagged VLAN 20 port!
Switched it to NO and now it's working fine again!

ps. I indeed put the DHCP server on the new switch a week or 2 ago.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top