Hi all, I'm a bit new to the world of smart switches, so this is likely something very simple I'm overlooking.
I have a SG200-50 switch. When I assign it a management IP of 192.168.0.2, I can access it just fine for a certain amount of time. But if I go back later and try to access the web-based config screens, I suddenly can't. I can't even ping it.
I suspect the problem is that I haven't set up any VLANs on the switch, and so none of the switch ports are configured to be part of the management VLAN. But the default behavior is for every port to be an untagged trunk on VLAN 1 - correct?
So, why can't I access the switch?
Thanks for helping...as I said, I'm sure it's something really basic.
I agree with what has been posted here already. It sounds like you don't have a route to the management subnet via your VPN connection. Check your advertised and allowed routes when connecting to the VPN to verify. As for not being able to manage the switch via the web interface, I would ensure the vlan interface is up/up, and connected nodes are passing traffic. If that is not the issue, it could potentially be a bug. Hope you are able to resolve the issue.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...