VLAN being reset to none on Mitel 5224/5330 1

[dyelton]

We have Mitel 5224 and 5330 phones being tagged with VLAN 10. When the phones boot up they show VLAN 10, but after they finish downloading from the controller (starting main is displayed on the phone), VLAN None is displayed.

If I modify the config it shows being set for VLAN 10, but if I show the current config on the phone (without rebooting by holding down both volume buttons, releasing the bottom one, and dialing 234) the phone shows VLAN 0.

Why are the phones not keeping the VLAN tagging? I'm connecting to Dell Powerconnect 6248P switches.
Thanks!

 

[bobcheese]

Do the phones work? are they connecting to the controller? How are the phones getting vlan info? DHCP or LLDP?

When a phone boots up it boots to the default vlan. Once it gets it vlan info from either method it will boot up in the assigned vlan (10) and broadcast for a dhcp lease. The new lease from the dhcp server on vlan 10 should not have any vlan info in it as the phones already know what vlan they are in.

 

[dyelton]

The phones work and connect to the controller, but they don't appear to be tagged with a VLAN ID as the Voice VLAN displays as non-operational for any given port with a phone attached with VLAN 10.

Everything on the phones is set manually, including the VLAN ID.

 

[bobcheese]

Is the controller on vlan 10? If so then how are the phones connecting the controller? do you have routing between the default vlan and vlan 10?

 

[dyelton]

The controller is on VLAN 10. I have the controller port on the switch untagged and tagged for VLAN 10. I did I have to untag the controller port for VLAN 1 as well else I could only get the phones to connect 5-10% of the time. I was told by Dell that having to do that was likely due to a routing issue, but I honestly can't see any issue with the routing.

Routing is handled by a SonicWall 4060. VLAN 1 is connected to the X0 (LAN) interface and VLAN 10 is connected to a sub-interface of X0. By default, SonicWall will setup routing between trusted interfaces which both interfaces are trusted in this case.

The two need to talk to one another as attendant console and a couple of other systems on VLAN 10 need to talk to an AD server that resides on VLAN 1.

 

[mitelninja]

Check Option 125 in the Mitel and make sure it is handing off the correct VLAN information.

 

[dyelton]

Here's an interesting twist. Every once in a while when I plug a phone in, it actually gets it right. It will assign VLAN 10 and priority 7 to the phone, but if I turn around and restart the phone, 99/100 it will get assigned VLAN None Priority None, even though I have it tagged for VLAN 10.

 

[dyelton]

After playing around with this a bit more, it seems if I manually set the L2 priority (to 7), the VLAN 10 sticks.

Does this make sense?

 

[bobcheese]

No that you say this it has jogged my memeory. I had this once with a customer who was using DHCP on all sites except 1 and none of the phones would boot. We checked a DHCP phone that was working and a static that wasn't and the only difference was the L2 Priority. We added it and everything started working.

 

[dyelton]

Thanks for instilling confidence in this solution. I've been everywhere from Dell's PowerConnect tech support to Sonicwall's tech support. The phones seem to work great with the L2 priority defined. I really wish this were stated somewhere so I could have kept what little hair I had left.

 

[RossBC]

I do believe that VLAN ID and Priority HAVE to be defined together. if the priority is not defined then the VLAN ID is ignored. not sure why it worked even 1% of the time though.

 

[Mitelpassion]

it would have worked because you have routing enabled.
so phone gets non-voice IP however because there's routing available it will connect to the controller that is in the voice vlan.

if you have the phone boot in the voice vlan then you won't need routing to connect to the controller.

when defining static vlan info, you HAVE to specify vlan priority - this as of release 8

once phone is booted in vlan 10 you don't have to tell it in the dhcp that hands out voice IPs that it belongs to vlan 10 again.