Troubleshooting of Layer 2 Multicast Failure
TL-SG2008P , TL-SG3452X , SG3452XMPP , TL-SG2218P , TL-SG3452XP , TL-SG2016P , SG2210XMP-M2 , SG3428XPP-M2 , SG3428XMPP , TL-SG2210P , SG6654XHP , SG2210MP , TL-SX3008F , TL-SL2428P , TL-SX3016F , SG2218 , SG3428 , TL-SG3452P , TL-SG3428X , SG3218XP-M2 , SL2428P , TL-SG3428X-M2 , SG3210X-M2 , TL-SG3428XF , TL-SG2210MP , SG3428X-M2 , SG3210 , SG3452 , TL-SG3428XPP-M2 , SX3032F , SG3452X , SG3210XHP-M2 , SG2008 , TL-SG2428P , SG3428XF , SG2005P-PD , SG2428LP , SG6428XHP , SX3008F , SG3428MP , SG3428X , SG3452P , SX3016F , TL-SG3428X-UPS , SX6632YF , SG2218P , SG2008P , SG3452XP , SG2452LP , TL-SG3428 , TL-SG2218 , SG2210P , SG6654X , SG2016P , SG6428X , TL-SG3428MP , TL-SG3210 , TL-SG3452 , TL-SX3206HPP , SG3428XMP , TL-SG3428XMP , SX3206HPP
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.
Contents
This article describes the troubleshooting steps for resolving issues with layer 2 multicast on switches, helping you quickly identify problems and address network faults.
- Omada Smart / L2+ / L3 switches
- Omada Controller (Software Controller / Hardware Controller / Cloud-Based Controller, V5.9 and above)
Multicast is commonly used in scenarios such as video conferencing and live streaming, allowing data packets to be received by multiple recipients simultaneously without the need to send individual packets to each receiver. Layer 2 multicast issues may be caused by various factors, and resolving these problems usually requires detailed diagnosis and configuration checks. This article introduces the general steps to troubleshoot multicast connectivity issues.
Step 1. Check the state of the physical port and STP. Go to Devices, select the target switch to open the Properties window, and check if the port is linked up normally and if the port is in the STP Blocking state.
1. If the port is not linked up, change the network cable and try again, or try another available port on the switch.
2. If the port is in the STP Blocking state, eliminate network loops first.
Step 2. Check the state of multicast member ports. Go to Tools > Terminal, select Switch for Device Type, choose the target switch in the pop-up window of Sources and click Confirm. Click Open Terminal.
First enter enable in the Terminal, and then enter show ip igmp snooping groups vlan vlan-id to check if the Switch ports in the multicast group correspond to the user-side ports.
1. If the Switch ports correspond to the user-side ports, it indicates that the switch has received the IGMP Report requests from the user-side devices.
2. If the Switch ports do not correspond to the user-side ports correctly, the following are the possible causes, which may require packet capture for further diagnosis.
- The switch does not receive the Report message from the user or the message format does not meet the device’s requirements.
- The IGMP messages received by the switch do not conform to the IGMP standards. The destination MAC or IP address is not a multicast address.
- The version of the IGMP messages received by the switch is not compatible with the version configured on the device.
Step 3. Check the router port.
Enter show ip igmp snooping vlan vlan-id to check if the router port exists.
1. If the router port exists, it indicates that the uplink port has received the IGMP Query messages from the upstream querier, or that the static router port has sent the Query messages.
2. If the router port does not exist, it means that no static router port has been configured, and that the switch has not received any IGMP Query messages from the upstream layer 3 device. In this case, you need to debug and troubleshoot the upstream device.
Step 4. Check the multicast packets.
Enter show ip igmp snooping interface packet-stat to check the multicast packets received by the switch.
1. Check if the switch is receiving any Error messages. If so, you need to capture the packets on the corresponding port for further analysis.
2. Check the IGMP Report message counters on the member ports. If the Report message counters do not increase after a member port receives an IGMP Report request, it indicates that the port is not receiving the Report messages.
3. Check the IGMP Query message counters on the router port. If the Query message counters do not increase, it indicates that the port is not receiving the IGMP Query messages from the upstream device or the static router port.
Step 5. Collect information and seek technical support.
If the previous steps have not been able to resolve the issue, please collect the relevant information from the previous steps, and then seek technical support.
By taking the troubleshooting steps above, you now know how to fix the Layer 2 multicast failure.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Questa faq è utile?
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
We'd love to get your feedback, please let us know how we can improve this content.
Grazie
We appreciate your feedback.
Click here to contact TP-Link technical support.
Questo sito utilizza i cookies per migliorare l'esperienza di navigazione, analizzare le attività online e offrire agli utenti una migliore user experience. Puoi disattivare o rifiutare il loro utilizzo in qualunque momento. Per maggiori informazioni consulta la nostra privacy policy .
Questo sito utilizza i cookies per migliorare l'esperienza di navigazione, analizzare le attività online e offrire agli utenti una migliore user experience. Puoi disattivare o rifiutare il loro utilizzo in qualunque momento. Per maggiori informazioni consulta la nostra privacy policy .
Basic Cookies
Questi cookies sono necessari per il corretto funzionamento del sito e non possono essere disattivati nel tuo sistema.
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
Analytics e Marketing Cookies
I cookies analitici ci permettono di analizzare le tue attività sul nostro sito allo scopo di migliorarne le funzionalità.
I marketing cookies possono essere impostati sul nostro sito dai nostri partner pubblicitari allo scopo di creare un profilo di tuo interesse e proporti contenuti pubblicitari rilevanti su altri siti.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au