Hi!
Cisco and HPE (HP, HPE and Aruba) VLAN related terminology differs with regards to port aggregation (Cisco (IOS): EtherChannel, HPE (ProVision/ArubaOS-Switch): Trunk) and tagging (Cisco (IOS): Trunk(ing) an interface with VLAN ids, HPE(ProVision/ArubaOS-Switch): tagging/untagging a port with VLAN ids). The main source of confusion is a Cisco used network administrator creates Trunks (aggregated port) on HPE thinking he/she would create a tagged interface...which is not.
With regards to untagged/tagged terminology a source could be this one.
Generally Access ports/interfaces need to be configured as untagged members of a specific (only one is admitted) VLAN id. Say you have VLAN 1000 "Data" and you want to assign port 15 to it, the ArubaOS-Switch command will be:
vlan 1000 (enter the VLAN 1000 context)
untagged 15 (assign the port 15 the untagged membership for the VLAN context you're in).
Viceversa to configure a port that will carry more VLAN Ids (Cisco: Trunk) supposing its purposes will be to act as an uplink/downlink port to other switch peer or to a VLAN aware server you have basically two ways:
- set that port (a physical port or a logical one, doesn't matter) to be concurrently an:
- untagged member of a VLAN id (the PVID Port VLAN ID, AKA the native VLAN id)
- tagged member of various other VLAN ids (as needed)
- set that port (a physical port or a logical one, doesn't matter) to be concurrently a tagged member of various other VLAN ids (as needed) making it "orphaned" of its untagged membership (so traffic admitted will be ONLY the one it carries VLAN tags, traffic without VLAN tag will be dropped).
To do that (both cases) the port need to simply be untagged/tagged as needed, example:
vlan 2000
untagged port 15
exit
vlan 1000
tagged port 15
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 2000 and 1000.
The no untagged chimes in to specify that a port can be removed from being member of VLAN 1 (Default), so when you see:
vlan 1
no untagged 15
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).
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<x> where x is the port trunking Id)...suppose to have port 1 and 15 aggregated together by using LACP...that is:
trunk ethernet 1,5 trk1 lacp
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:
vlan 2000
untagged trk1
exit
vlan 1000
tagged trk1
exit
There is a nice Aruba presentation that explains the Aruba ArubaOS-Switch (ProVision of HP ProCurve) versus Cisco IOS here.
More or less it's enough to start your journey with HP ProCurve / HPE Aruba switches.
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).