variable wrote

Model :

Hardware Version :

Firmware Version :

ISP :

Hi,
I am having trouble with my brand new SG1016. The issue lies with VLAN. I have uploaded the newest firmware available (tried with default one prior to that).
Basicaly, i have set the switch ip address to 192.168.85.78 as all of my switches are in this VLAN.
I am using port 18 as uplink and have tagged the port on 85, same config on other end (i use this switch on other end to configure all my devices so its 100% working and properly configured).
For some reason i am unable to ping the SG1016 switch. It seems like the vlan configuration is not working on the switch at all, i would like to ask if i am missing something or is the device i have malfuncioning?
I have gotten almost no response from the reseller

R1D2 wrote

The Easy Smart switch's web UI can also be reached from any other VLAN if its IP is in the same range used in this VLAN. For example, if a port is member of VLAN 85, its PVID is 85, subnet is 192.168.85.0/24 and the switch has IP 192.168.85.1 you could reach its web UI from the device connected to this port in VLAN 85 (at least it works on my SG108E/PE).

You could even reach the web UI from another port in another VLAN as long as the correct IP address is used (for example, if a ports membership/PVID is 10 and it also uses the 192.168.85.0/24 subnet, the switch's web UI can be reached from a device on that port). Although you cannot reach other clients in VLAN 85 from clients within VLAN 10, you still can reach the switch's web UI. There is no explicit management VLAN those switches are assigned to.

The PVID (Primary VLAN ID) designates the "default" VLAN for a particular port, i.e. all untagged frames are assigned to this primary (sometimes also called "native") VLAN, no matter wether it's the only VLAN this port is a member of as with "access" ports or wether this port is a member of more than one VLAN as with "trunk" ports. This is what 802.1q demands.

You could see it this way that the switch's web UI is on a trunk port which is a member of every defined VLAN and has PVID 1. All ingress traffic arrives at the web UI and every response will be forwarded to any other port b/c they are hard-coded members of the Default_VLAN 1. But since this can't be changed, I prefer to view it the way that the switch has no mgmt VLAN.

That's BTW the reason b/c in my opinion a fixed Default_VLAN 1 is not a good idea. Don't get me wrong: it's o.k. to have a System VLAN which might be designated VLAN 1 by default, but it should be not fixed/hard-coded. For example, in TL-SG2008 there is a System (management) VLAN set to 1 by default, too, but you can change it and you can remove ports from it.