TL-SG1016PE management website temporary not accessible,
Hello,
we have a TL-SG1016PE switch which is connected to a Dell core switch. Everything is working, but the management website is temporary not available. When I connect to the Dell switch and make a ping to the IP of the TP Link switch it is working and after that I can access the management website. Some minutes later it is not accessible again.
We have 2 other switches (Dell and Netgear) connected to the core switch, there we don't have the problem.
The uplink has VLANs enabled 16 untagged PVID, 10, 11, 12 tagged.
When I check the MAC address in the core switch it is behind the port which the TP-Link switch is connected to.
Flowcontrol is disabled. Disablind spanning tree didn't change anything. The Ports are set to auto. But that shouldn't be the problem because the log doesn't show a port state change. The port is up and working for the devices connected to the TP-Link switch.
What can I do?
Greetings
Christian
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks for posting in our business forum.
Have you checked if there is an arp issue on the core switch?
This is something we have never experienced before. If you isolate this switch from the core and other L3 switches, and connect it to a GW-SW-PC setup, will it work steadily?
- Copy Link
- Report Inappropriate Content
Hi @Clive_A ,
thanks for your reply.
Wwe have other switches conntected to the core and no problem with them, when we ping it. Currently there is only 1 accesspoint connected to the TP-Link switch. This accesspoint is 100% available when we ping it. So there is no ARP cache problem.
I've change the default VLAN for the uplink port, changed it only to 1 vlan, no change.
Greetings
Christian
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
Network_Admin wrote
Hi @Clive_A ,
thanks for your reply.
Wwe have other switches conntected to the core and no problem with them, when we ping it. Currently there is only 1 accesspoint connected to the TP-Link switch. This accesspoint is 100% available when we ping it. So there is no ARP cache problem.
I've change the default VLAN for the uplink port, changed it only to 1 vlan, no change.
Greetings
Christian
I am simply asking to test this switch and to confirm if this is a firmware issue even though it might not be.
My point is to verify if the switch is intact. Otherwise, it is the config problem. And something else should be proceeded. There is basically nothing we can do from the web GUI but Wireshark on this switch as it is an L2 switch.
- Copy Link
- Report Inappropriate Content
Hello,
sorry for the late answer, but meanwhile I have figured out where the problem is. In my eyes it's definitly a problem of the TP-Link switch.
I've testet a lot, with changing default VLAN, tagged, untagged and so on. Finally I have resettet the switch and configured it completely new. When the interface is on DHCP everything is working. When I change to static IP the problem comes back.
Greetings
Christian
- Copy Link
- Report Inappropriate Content
Network_Admin wrote
Hello,
sorry for the late answer, but meanwhile I have figured out where the problem is. In my eyes it's definitly a problem of the TP-Link switch.
I've testet a lot, with changing default VLAN, tagged, untagged and so on. Finally I have resettet the switch and configured it completely new. When the interface is on DHCP everything is working. When I change to static IP the problem comes back.
Greetings
Christian
If you say so, that's a routing issue.
Yet, the switch does not support layer 3 routing. But it does not have anything to do with the switch L3.
If you use static IP, you should definitely specify the default gateway because that's how the routing from your router comes to the switch. The default gateway should take care of it.
- Copy Link
- Report Inappropriate Content
Hi,
trust me, when I switch over to static IP I have entered the default gateway :-)
With a static IP it works for 20-30 pings and then some pings not, after that again 20-30 pings and so an.
Greetings
Christian
- Copy Link
- Report Inappropriate Content
Network_Admin wrote
Hi,
trust me, when I switch over to static IP I have entered the default gateway :-)
With a static IP it works for 20-30 pings and then some pings not, after that again 20-30 pings and so an.
Greetings
Christian
You might be right. But I don't have a comment on this as I am not on the same page as you do. I am not following you because of the information gap.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 448
Replies: 7
Voters 0
No one has voted for it yet.