How to configure LLDP & LLDP-MED on Omada Switches via Omada Controller

SG2005P-PD , TL-SG3452X , SG2428LP , SG3452XMPP , SG6428XHP , SG2210XMP-M2 , SX3008F , SG3428MP , SG3428X , SG3428XPP-M2 , SG3452P , SX3016F , SG3428XMPP , TL-SG3428X-UPS , SX6632YF , SG2218P , SG6654XHP , SG2428P , SG2008P , SG3452XP , SG2210MP , SG2452LP , SG2210P , SG2218 , SG3428 , SG6654X , SG2016P , SG6428X , SG3218XP-M2 , SL2428P , SG3210X-M2 , SG3428X-M2 , SG3210 , SG3452 , SX3032F , SG3210XHP-M2 , SG2008 , SG3428XMP , SX3206HPP , SG3428XF
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device, and check either the Datasheet or the firmware section for the latest improvements added to your product. Please note that product availability varies by region, and certain models may not be available in your region.
Contents
This article introduces how to configure LLDP and LLDP-MED on Omada Switches via the Omada Controller.
- Omada Software/Hardware/Cloud-Based Controller V5.0 and above
- Omada Smart/L2+/L3 Switches
Link Layer Discovery Protocol (LLDP) provides a standard link layer discovery mechanism, allowing devices from different manufacturers to discover and exchange their respective system and configuration information in the network. The LLDP-MED TLVs (Type-Length-Values) offer many advanced features for VoIP, including basic configuration, network policy configuration, address information, and directory management, meeting the requirements of different VoIP device manufacturers in terms of high return on investment, easy deployment, and easy management. It also solves the problems in deploying voice devices in Ethernet networks, providing convenience for VoIP device manufacturers, sellers, and users.
A typical application scenario for LLDP-MED is as follows. LLDP-MED allows the switch to send its Auto-VoIP information to IP phones for automatic configuration. In this example, LLDP-MED needs to be enabled on port 1/0/1 of the switch.
Here are the steps to configure LLDP-MED on the Omada switch via the Omada Controller:
- Configure a Voice VLAN.
- Create a Switch Port Profile.
- Assign the Port Profile to the switch ports where you want to enable LLDP-MED.
Note: LLDP is enabled by default and cannot be disabled on the Omada switch managed by the Omada Controller. LLDP-MED is enabled automatically when creating Switch Port Profile.
Step 1. Log in to the Omada Controller. Go to Settings > Wired Networks > LAN > Networks and click Create New LAN.
Step 2. Create a 802.1Q VLAN2 as the Voice VLAN and click Save to save the settings.
Step 3. Go to Settings > Wired Networks > LAN > Switch Profiles and click Create New Port Profile.
Step 4. Set the Voice VLAN as Tagged Networks and Voice Network. LLDP-MED is enabled by default. Click Save.
Step 5. Go to Devices, click the switch to open the Properties window, and go to the Port tab. Click the Edit icon of Port 1.
Step 6. Bind the Voice-Data-Network profile to Port 1. If LLDP-MED needs to be enabled on other ports, bind the same profile to the corresponding ports.
Step 1. Go to Tools > Terminal. Select Switch for Device Type and choose the switch with LLDP-MED enabled in the pop-up window of Sources. Click Open Terminal.
Step 2. Enter the following commands to view the LLDP neighbor. The result shows that the LLDP neighbor between the IP phone and the switch has been established.
en
show lldp neighbor-information interface gigabitEthernet 1/0/1
You have successfully configure LLDP and LLDP-MED.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Related FAQs
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.

TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au