Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

ADB100 (TechnicalUser)
22 May 11 8:01
I have some older Extreme switches (ExtremeWare OS) that support LLDP but not enough to get the Mitel IP Phones to discover the Voice VLAN.  No problem - I have routing between the Data (access) & Voice VLAN so I'll configure Option 125 on both the Data & Voice VLAN DHCP Scopes.
Since LLDP is preferred (and usually supported in the switches) we normally just configure Option 125 globally on the DHCP server (so it automatically applies to all Scopes) and omit the 'vlan=xxx' part.  So I reconfigured Option 125 to include this for the Data VLAN but left the global settings (without 'vlan=xxx') in there for the Voice VLAN.
On bootup the phone uses Option 125 from the Data VLAN DHCP scope and begins tagging packets with the Voice VLAN tag, it leases a Voice VLAN IP address and displays it is using Option 125, however it displays 'TFTPerr' at the point it would normally start downloading and then resets.

I solved this by adding the same 'vlan=xxx' to the Voice VLAN DHCP scope but I kind of thought this was a bit odd as the phone should just ignore this option once it is speaking with a Tag?

Not a big issue but seems a little odd to me.  The Nortel (Avaya..) phones don't do this - they do a limited DHCP request on the access vlan and simply request an IP address and Option 128 (I think?) which tells it the Voice VLAN.  It then releases the IP address and sends out a more substantial DHCP request using Tagged frames, however it doesn't need to see the option telling it the Voice VLAN at this point.

Andy
SXWizard (Vendor)
22 May 11 21:05
Option 125 on the data VLAN DHCP server only needs this entry - id:ipphone.mitel.com;vlan=X

This will give the phone the voice VLAN tag. The phone will then reboot tagged to the voice VLAN and request DHCP. The voice VLAN DHCP server needs options 3, 6 and 125. For option 125 use this example and change X to match your requirements. (call_srv & sw_tftp would be the IP address of the controller).

id:ipphone.mitel.com;call_srv=X;vlan=X;dscp=46;l2p=X;sw_tftp=X
ADB100 (TechnicalUser)
23 May 11 14:44
OK.  So it still needs the 'vlan=xxx' in the Voice VLAN DHCP scope?  It just seems a bit odd as it has already accepted the Voice VLAN Tag from the Data VLAN DHCP scope?
I'll modify Option 125 for the Data & Voice VLANs when I get back to site and test.

Thanks, Andy

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close