JetStream TL-SG3428X Management VLAN?

  @Kris0x0000 Yes, it does. Works great here.

1. Have you configured the VLAN at the port you are using to access the switch and set the IPs correctly?

2: Are there any ACLs configured?

  @mwo 

Thanks for your reply.

A1. I assumed that if the switch is uplinked with the trunk from the router it should "have" all VLANs (also the one used as management). Is my assumption wrong? :)

A2. No

I'll try to add some details:

My management network is 10.8.8.0/24 (vlan2) and my main network is 10.2.2.0/24 (vlan1/native). The traffic between these networks is allowed, all hosts from both sides can access each other.

I have just checked that I actually can access the switch GUI but only from this network. So the problem is I cannot access switch via 10.8.8.x/24 interface from the 10.2.2.0/24 network. I can access every other host from the 10.8.8.0/24 network though.

  @Kris0x0000 

I assume that the 3428X is not managed by Omada. In this case you have to setup all the VLANs on each port manually.

VLAN 1 is activated by default on all ports, so you have access to the switch. If you configure an additional Management VLAN, it has to be activated on all needed ports.

You can try the following:

1. Set the PVID of an unused swtich port to the Management VLAN and make this port an untagged member of the Management VLAN. Connect your PC to this port and give it a static, unused IP from the management subnet. If you can access or ping the switch, the interface works.

2. At the router trunk port, allow all needed VLANs as tagged and set the PVID to 1 or some dummy VLAN. Therefore, the router must support VLANs as well. You may now configure a router port as explained above and connect your PC there to check if the trunk is working.

Kind regards

Martin

  @mwo 

The problem is solved. It was enough to set the default route at the switch. 

Destination: 0.0.0.0

Subnet Mask: 0.0.0.0

Next Hop: ip address of the router

Distance: 1