VLANs - Zyxel --- Cisco

mar0001

A trunk (tagged port) means I can send more than one VLAN across. This is done in all the networks.

Unfortunately, I cannot wait any longer for a solution. It is a very expensive switch and I decided not to keep it. I am sure this is sth that will work and I am making a mistake but this is a very expensive exercise ;-)

I wish there was a clear instruction showing a lab with a basic trunk between two switches a few devices in 2-3 VLANs, even using two Zyxel switches.

PeterUK

Sure I get why you would want to trunk I have never needed to trunk my understanding of how a trunk works is

Switch A ----Switch B----Switch C

Where you have many of the same VLANs on A and C but instead of having to do all the VLANs again for B you have Switch B trunk

Zyxel_Melen

Hi @mar0001,

Please help check the MAC table on XMG1915.

In my lab, with the same VLAN configuration as yours, I connect the XMG1915 port 8 to Cisco 3750 port 8. When the Cisco's VLAN 10 line protocol is up, I can see Cisco's mac on XMG1915's MAC table. And the PC is on port 15.

I also can see XMG1915's and PC's MAC on Cisco.

My Pc also gets an IP address from Cisco.

And ping the Cisco VLAN 10 interface, which is 192.168.10.10.

However, if the VLAN 10 line protocol is down, I can't find it on XMG1915's MAC table.

Since your VLAN 10 setting on XMG1915 is correct, I think there might be a misconfiguration on your Cisco switch.

About the Cisco ping XMG1915, please correct port 8 VLAN1 from tagged to untagged since VLAN1 is usually a native VLAN for Cisco.

Xydocq

hello @mar0001

looking at this pic

Short question, what is native VLAN on Port 8-10 if all VLANs are tagged?

I could be wrong, but VID1 is default VLAN1 and also the general native VLAN1 and therefor should be untagged on all Trunk-Ports, native VLAN on Access-Port 15 is VLAN10. The only thing to tag are additional VLANs on a Trunk-Port.