timalex
Junior Member
Posts: 36
Joined: Jun 2014
|
RE: T46G LLDP-MED VLAN Issue
I did not have talked with Yealink about the problem until now. For the workaround I use for the moment you will need:
1) You have to configure your switches to act as dhcp proxy / use ip helper addresses to forward the dhcp requests from your machines to your dhcp server. We dont use Juniper, so I cannot tell you the specific commands.
2) You need to configure your dhcp server with 2 dhcp scopes for a) <ip_scope_for_vlan_data> and b) <ip_scope_for_vlan_voice>. At a) you configure option 132 = <vlan_id_voice>. At b) you probably want to configure a Vendor Class "yealink" with option 43 = <http://your_provisioning_server/yealink> or whatever else points to you Provisioning Server.
By that, all phones will first get ip addresses out of you data scope, seeing 132, move over to vlan_voice, do a second request for another ip there, see also option 43 and therefor request from your provisioning server the common and mac files.
Option 132 will be ignored by your pc's, only used by your phones.
For further information you also might take a look at "VLAN Feature on Yealink IP Phones.pdf" from Yealink (probably you already have done so).
I dont see a screenshot from you, sorry. But we use Windows dhcp too, w2k8r2.
I didn't had time to take a deeper look into our problem with LLDP, same time pressure as you. Just looking for a quick solution to get around it.
|
|
06-23-2014 05:31 PM |
|