[discovery] lldp-med-net-policy-vlan not working on CCR2116

RouterOS General
1

Hello, new here.

Scenario:

CCR2116 — eth4 — Yealink Phone — PC

Yealink Phone doesn’t receive tagged VLAN Voice from LLDP-MED and therefore remains on untagged VLAN without join tagged VLAN voice.

lldp-med-net-policy-vlan is correctly enabled and configured with voice VLAN.

Yealink Phone works like a charm receiving Voice VLAN with others switch vendors and LLDP-MED.

Any ideas? At the moment the workaround to put phone on correct Voice VLAN is to use DHCP Option 132.


/interface list
add name=discovery_list

/interface list member
add interface=ether4 list=discovery_list

/ip neighbor discovery-settings
set discover-interface-list=discovery_list lldp-med-net-policy-vlan=5 protocol=lldp,mndp

/interface bridge port
add bridge=bridge1 comment="IP Phone" interface=ether4 pvid=10

/interface bridge vlan
add bridge=bridge1 tagged=bridge1,ether4 vlan-ids=5

Thanks,

Gianremo

2

In the docs there is:

When used together with the bridge interface, the (R/M)STP protocol should be enabled with protocol-mode setting. 

Additionally, other neighbor discovery protocols (e.g. CDP) should be excluded using protocol setting to avoid LLDP-MED misconfiguration.
3

Hello, thanks for answer.

Yes, already tried that but with no luck.

/interface bridge
add ether-type=0x8100 fast-forward=yes frame-types=admit-all ingress-filtering=yes name=bridge1 priority=0x1 protocol-mode=rstp pvid=1 vlan-filtering=yes

/ip neighbor discovery-settings
set discover-interface-list=discovery_list lldp-med-net-policy-vlan=5 protocol=lldp
4

update from MikroTik support #[SUP-115696]

Hello,

Thank you for the report!

We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming RouterOS versions, unfortunately, I cannot provide a release date now.

If you downgrade to RouterOS 7.7, the LLDP-MED should reply with VLAN ID.

Best regards,
Edgars P.