After performing the steps hereby described, your equipment will be accessib.
An example of this configuration would be : In this video you will learn how to perform a quick setup of Hirschmann devices. Keep in mind VLANs and IP Segments usually are 1:1 meaning you will need an IP Segment for every VLAN you have. If you indeed need to configure PC1 on VLAN 10 and PC2 on VLAN 20 then you should configure both ports between the Router and the Switch on trunk mode and ports 2 and 3 on the Switch as access. An example of this configuration would be this: This way the Switch would work pretty much like a "plug and play" unmanaged Switch, leaving the reset of the work to the Router to route the packets to/from the internet.
If there is not, you could just leave the Switch to its default switchport configuration, which is every port in access mode. vlan 10 packets will sent as un-tagged but vlan 11 wil sent as tagged.Is there really a need for PC1 and PC2 to be on different VLANs? If you assign a voice vlan on g1/0/1 suppose vlan 11. g1/0/1 will be sent as un-tagged because vlan 10 is native for it. Suppoes u have a vlan 10 assigned on an access port g1/0/1 in WS-C2960S-24TS-L Tagged vs Untagged Traffic. Then you are going to have to use dot 1 q encapsulation.as this is the only encapsulation type that understands the concept of an untagged vlan.the native vlan. If you mean you have disabled it by using ISL encapsulation rather than dot1q encapsulation Configure PVID on a specific port (this action is the same as configuring access port for Cisco switch) When configuring VLAN on Cisco switch, you need to: 1. I assume you hve just set your native vlan to be some obscure unused vlan. Compare VLAN between Zyxel and Cisco: When configuring VLAN on Zyxel switch (Standalone mode), you need to: 1. Thing is you have to do this on all trunk ports on all switchesīut as you have disabled it.(which you cant do on cisco devices) So the acutal command will be something like To select a specific vlan to have as native vlan Ps all traffic is tagged.apart from that of your native vlanĪnd you yourself set up which vlan you want that to be You definitely need to enable native vlan.and check it out thoughout your whole network. Īnd then this traffic gets sent out to switch 2 untagged. You dont want to set up vlan 1 as native vlan on switch 1. That is the only vlan that isnt us you must ensure that the same native vlan is used through out the network. Switchconfigdot1q-tunnel 1.1.4 switchport pvid Syntax To configure VLAN of the access-mode port, run switchport pvid vlan-id. Example The following example shows how to enable Dot1q tunnel in the global configuration mode. Untagged frames received on trunk are assumed to be part of native VLAN. by default and put the SPVLAN tag on the incoming packets. By default it is VLAN 1 but that can be changed. The native VLAN is always untagged unless you enable tagging for it.
When frames from that VLAN are sent over a trunk they get a tag added so the receiving switch knows to which VLAN the traffic belongs. When a port is set to access it means that the port is part of the VLAN forwarding wise (MAC table) but all frames are sent untagged. Could this meant that these devices must use the native VLAN on our switches (which, in our case, the native VLAN is disabled on our switches)? Currently these devices are on switchports with fairly simple configs, such as:Īccess ports don't send tagged frames as most PCs would not support 802.1Q and even if they did you would not want to tag frames unless you had the need for multiple VLANs and that would require a trunk. Devices which you want to connect to VLAN1 on switch 1 would then have to have the port they are connected to set to UNTAGGED for VLAN1 and set to NO for all other VLANs. I'm not sure how that is possible if all of our switch ports belong to VLANs. So, if port 48 on switch 1 was connected to port 48 on switch 2 then you would TAG port 48 on both switches for VLAN1 and VLAN2. The confusion came with the implementation of a new phone system, where the vendor states that certain (non-Cisco) components must not receive tagged traffic. I've always thought that traffic going through a VLAN access switchport is tagged with the VLAN ID, along with VLAN traffic going over trunk ports (when the devices are both setup for the same VLANs). Below are the screenshots from switch GUI for above example. The VLAN Port page shows how to assign the PVID for the ports. We have a network of primarily 3750 switches with several VLANs, and dot1q trunks setup between the switch stacks. Port 1.8 will enable Untagged traffic to exit this port from VLANS 20 & 30. This seems like a simple concept but I'm having a hard time grasping which traffic is tagged vs that which is not tagged.