What to do if devices in the same VLAN fail to communicate with each other when connected to TP-Link switch

TL-SG2008P , TL-SG3452X , TL-SG2218P , TL-SG3452XP , TL-SG2016P , SG2210XMP-M2 , SG3428XPP-M2 , TL-SG2210P , SG6654XHP , SG2210MP , TL-SX3008F , TL-SL2428P , TL-SX3016F , SG2218 , SG3428 , TL-SG3452P , TL-SG3428X , S4500-16GP , SG3218XP-M2 , SL2428P , TL-SG3428X-M2 , SG3210X-M2 , S4500-8GHP2F , S4500-16G2F , TL-SG3428XF , TL-SG2210MP , SG3428X-M2 , SG3210 , TL-SG3428XPP-M2 , SG3452X , SG3210XHP-M2 , TL-SG3210XHP-M2 , SG2008 , TL-SG2428P , SG3428XF , SG2005P-PD , SG2428LP , SG6428XHP , SX3008F , SG3428X , SX3016F , TL-SG3428X-UPS , SX6632YF , SG2218P , SG2428P , SG2008P , SG3452XP , TL-SG3428 , TL-SG2218 , SG2210P , SG6654X , SG2016P , SG6428X , S5500-4XHPP2XF , TL-SG3428MP , TL-SG2008 , TL-SG3210 , TL-SG3452 , TL-SX3206HPP , SG3428XMP , TL-SG3428XMP , SX3206HPP , S5500-24MPP4XF
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.
Scenario:
As is shown, two PCs with static IP addresses in the VLAN 10 cannot communicate with each other. The data packets need to pass three switches to be transmitted between the two PCs.
Troubleshooting Steps:
Note: This guide takes the Web GUI of SG2210MP as an example.
Step 1: Check the port status. Go to SYSTEM > System Info > System Summary where you can check the port status. Here both the Port 1 connected to the PC and the uplink Port 9 are in Link Up status.
If the port status is unstable or the link speed is not satisfying, go to MAINTENANCE > Device Diagnostics, choose the corresponding port, and click Apply. As is shown below, four pairs of cables are all shown as Normal, indicating that the networking cables function well.
Step 2: Check the status of spanning tree and loop detection. Both spanning tree and loop detection are disabled by default in the Standalone mode, while in the Controller mode, spanning tree is disabled and loop detection is enabled by default.
If STP is enabled, go to L2 FEATURES > Spanning Tree > Port Config where you can check the port status. Here the status of the uplink Port 9 configured with STP is Forwarding without being blocked.
If loopback detection is enabled, go to L2 FEATURES > Switching > Port > Loopback Detection where you can check the loop status and block status of the corresponding port. Here the Port 1 connected to the PC with loop detection enabled is not blocked.
Method 1: Check packet discards of the port via CLI commands. As is shown below, Tx Discards and Rx Discards are 0, indicating that no network congestion or packet discards occur.
Method 2: Go to MAINTENANCE > Traffic Monitor and monitor the Octets Rx and Tx statistics of the port over a period of time (e.g. 10 seconds). These statistics can be used to see whether there is congestion on the port by deducing the average throughput over this period and comparing it with the port bandwidth.
Step 3: Check the creation of VLAN. Go to L2 FEATURES > VLAN > 802.1Q VLAN. Here VLAN 10 has been created.
Step 4: Check the VLAN configuration of the corresponding port. Go to L2 FEATURES > VLAN > 802.1Q VLAN > VLAN Config and click Edit. Here the Port 1 connected to the PC and the uplink Port 9 have been added to VLAN 10. The PC ports are usually untagged while the uplink ports are tagged in the VLAN.
Step 5: Check the PVID configuration of the corresponding port. Go to L2 FEATURES > VLAN > 802.1Q VLAN > Port Config where you can check the PVID configuration of all the ports. The PVID of the Port 1 connected to the PC should be set as 10, while that of the uplink port is kept as 1 by default.
Step 6: Check the MAC address table. Go to L2 FEATURES > Switching > MAC Address > Address Table where you can check the mappings between MAC addresses, VLAN IDs, and ports. Mapping errors can affect data forwarding, leading to devices’ failure to communicate with each other.
Step 7: Check the filtering policies (e.g. ACL, IMPB). Go to SECURITY > ACL > ACL Config. Here no ACL has been configured for VLAN 10.
Go to SECURITY > IPv4 IMPB > ARP Detection. ARP detection is disabled by default. Here the ARP detection is not enabled for VLAN 10.
Go to SECURITY > IPv4 IMPB > IPv4 Source Guard. IPv4 Source Guard is disabled by default. Here IPv4 Source Guard is not enabled for the corresponding ports.
The checking procedure for IPv6 IMPB is similar and will not be repeated here.
Czy ten poradnik FAQ był pomocny?
Twoja opinia pozwoli nam udoskonalić tę stronę.
Jakie są Twoje uwagi dotyczące tego artykułu?
- Niezadowolenie z produktu
- Zbyt skomplikowany
- Mylący tytuł
- Nie dotyczy mnie
- Zbyt ogólnikowy
- Inne
Dziękujemy
Dziękujemy za przesłanie opinii.
Kliknij tutaj, aby skontaktować się ze Wsparciem technicznym TP-Link.
z United States?
Uzyskaj produkty, wydarzenia i usługi przeznaczone dla Twojego regionu.
Ta witryna wykorzystuje tzw. pliki cookies, aby usprawnić jej przeglądanie, w celu analizy ruchu oraz do jak najlepszej optymalizacji wyświetlanych treści. W każdej chwili można wyłączyć obsługę plików cookies. Więcej informacji na ten temat dostępnych jest w Polityce prywatności
Your Privacy Choices
Ta witryna wykorzystuje tzw. pliki cookies, aby usprawnić jej przeglądanie, w celu analizy ruchu oraz do jak najlepszej optymalizacji wyświetlanych treści. W każdej chwili można wyłączyć obsługę plików cookies. Więcej informacji na ten temat dostępnych jest w Polityce prywatności
Podstawowe Cookies
Te pliki cookies niezbędne są do poprawnego działania witryny i nie moga zostać wyłączone.
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_banner, tp_privacy_base, tp_privacy_marketing, 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
Cookies dotyczące analizy i marketingu
Analiza - Te pliki Cookies są wykorzystywane w celu analizy ruchu na naszej stronie, co umożliwia poprawę i dostosowanie wyświetlanych treści.
Marketing - Te pliki Cookies mogą być wykorzystywane przez naszych partnerów reklamowych podczas tworzenia profilu Twoich zainteresowań, co pozwala na wyświetlanie odpowiednich reklam na innych stronach.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au