VOSS LLDP-MED with Mitel Phone
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-21-2021 02:49 PM
Trying to get this to work, but no luck so far. I have 2 separate VLANs for data and voice. On the VSP port, the data VLAN is default and untagged. I have also configured 2 commands for LLDP-MED to get the Mitel onto the voice VLAN. However, the phone is still landing on the data VLAN. The LLDP-MED commands used on the interface are:
lldp med-network-policies voice tagging tagged vlan-id 1121
lldp med-network-policies voice-signaling tagging tagged vlan-id 1121
#show lldp med-network-policies
************************************************************************************
Command Execution Time: Thu Oct 21 13:47:35 2021 CDT
************************************************************************************
==========================================================================================
LLDP-MED Network Policies
==========================================================================================
Port Application Type VlanID Tagging DSCP Priority
------------------------------------------------------------------------------------------
1/9 Voice 1121 Tagged 46 0
1/9 Voice Signaling 1121 Tagged 0 0
------------------------------------------------------------------------------------------
As a follow up question, does anyone know the difference between the policy types? That being {guest-voice | guest-voice-signaling | etc..}.
lldp med-network-policies voice tagging tagged vlan-id 1121
lldp med-network-policies voice-signaling tagging tagged vlan-id 1121
#show lldp med-network-policies
************************************************************************************
Command Execution Time: Thu Oct 21 13:47:35 2021 CDT
************************************************************************************
==========================================================================================
LLDP-MED Network Policies
==========================================================================================
Port Application Type VlanID Tagging DSCP Priority
------------------------------------------------------------------------------------------
1/9 Voice 1121 Tagged 46 0
1/9 Voice Signaling 1121 Tagged 0 0
------------------------------------------------------------------------------------------
As a follow up question, does anyone know the difference between the policy types? That being {guest-voice | guest-voice-signaling | etc..}.
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-26-2021 10:52 AM
Once you converted the auto-sense port configuration to config, you can then adjust the voice vlan to whatever you like for this particular port. Auto-sense does nothing else than dynamically configuring options with the global settings - once you convert them to config, you see them in your config file.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-26-2021 11:19 AM
It did do the conversion and I could see the commands. I was trying to determine what commands I would need for a configuration template so I tried removing 1 at at time until it broke. When I entered the global command "no auto-sense voice" and bounced the port, the phone went back to landing on the untagged data vlan.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
‎10-26-2021 11:25 AM
Added this command under the interface along with the voice network policy and now it works.
lldp tx-tlv dot3 mac-phy-config-status
lldp tx-tlv dot3 mac-phy-config-status
