Hirschmann switch tag vs untag setup
![hirschmann switch tag vs untag setup hirschmann switch tag vs untag setup](https://www.industrialnetworking.com/Hirschmann-RSP-Switches-LG.jpg)
This is only relevant for telephony OUI-enabled voice VLAN. It cannot be used for any special role, such as unauthenticated VLAN or voice VLAN.It is distinct, non-static/non-dynamic and all ports are untagged members by default.The default VLAN has the following characteristics: The default interface status of all ports is Trunk and all ports are configured as untagged members of the default VLAN. If it is controller based, then you usually configure port as untagged and traffic is tunneled all the way to the controller.When using factory default settings, the device automatically creates VLAN1 as the default VLAN. What type of Aruba wireless setup do you have? Is it controller based on Unified/Instant? If it is instant, then you usually configure the port as a trunk with native vlan as untagged and you configure the other vlans as tagged since the instant AP will send tagged traffic if the SSIDs are mapped to different vlans. Its an aruba wireless ap running dhcp on vlan 146." "Similarly we have vlan 146 and 149 for wireless and guest there is a port 1/9 which connects to 146 and 149 vlan as well how do i determine which port should go as tagged and untagged. If it is not configured to send a vlan then you don't need to tag the port. In your case, if whatever your are connecting, is sending a tagged vlan then you need to configure the tagged vlan on the switch port. As for vlan 113, I am not sure if you need to have tagged or untagged. Now on switch, port 1/3 is assigned to user in Support team well in this case vlan 109 should go as untagged while 113 should go as tagged" "Lets say we have 2 vlans vlan 109 for Support team and vlan 113 which is for HP-Nonstop.
Hirschmann switch tag vs untag setup series#
Please note that some HPE Switch series (Comware 5/7 OS driven) use Cisco terminology for VLAN related configurations (so access/trunk) but EtherChannels are called LAGs (Link Aggregation Groups). More or less it's enough to start your journey with HP ProCurve / HPE Aruba switches. There is a nice Aruba presentation that explains the Aruba ArubaOS-Switch (ProVision of HP ProCurve) versus Cisco IOS here. So the (logical) interface you will need to manage now on is the trk1 (forget about ports 1 and 15), at this point to apply tagging/untagging the configuration is identical to those seen above: In the end the first source of confusion (Cisco: EtherChannel -> HPE: Port Trunking = Link Aggregation) chimes in too because, often, is needed to tag/untag an aggregated interface (Trk where x is the port trunking Id).suppose to have port 1 and 15 aggregated together by using LACP.that is: It means that port 15 is "orphaned" of VLAN id 1.but to work it needs to be at least tagged or untagged member of another VLAN Id otherwise it will not be accepted (a port can't be orphaned of any VLAN, it needs to be member of a VLAN Id - tagged or untagged - at worst). The no untagged chimes in to specify that a port can be removed from being member of VLAN 1 (Default), so when you see: That way port 15 will be untagged member of VLAN 2000 and tagged member of VLAN 1000, in Cisco terms PVID = 2000 and trunk permit VLAN Ids 20.
![hirschmann switch tag vs untag setup hirschmann switch tag vs untag setup](https://techhub.hpe.com/eginfolib/networking/docs/switches/YA-YB/15-18/5998-8157_yayb_2530_atmg/content/images/figure_1-40.png)
To do that (both cases) the port need to simply be untagged/tagged as needed, example: