The requirement of transporting VLAN over the Trunk (as happens now on the single Uplink) is due to the fact there is a third HPE Switch (PoE) which is used only for Wireless APs access (they manage VLAN1 and VLAN 5), this third switch is connected with another single port uplink to the actual 48 ports 'edge' Switch. I'm trying to simulate BAGG and VLAN configurations in a 1920-8G 1920-8G scenario because I'm going to have a very short time window during which doing the whole re-configuration (for the sake of completeness I'm going to change the actual HPE 1920-24G that acts like a core with a brand new HPE 1920-48G so the action plan will involve re-patching, re-ordening cables, updating existing Switch's Firmware to latest release and then optimizing discussed ports settings). So I'm in serious doubt about its correctness. Here relevant parts of the config (with some screenshots) with - I hope - only BAGG1 set as Tagged Member of VLAN 5 while each GE1/0/1-GE1/0/4 port was left as Untagged Member of VLAN 5. Speaking about the point (3) I did a configuration test on a spare HPE 1920-8G (JG920A) - without connecting it - and, at first sight, I realized I didn't fully understood if I need to set VLAN 5 Tagged Membership to both BAGG1 and GE1/0/1-GE1/0/4 (BAGG member ports) or if I need to set VLAN 5 Tagged Membership only to BAGG1 leaving its member ports VLAN 5 Untagged Members: I agree with you about Trunk type (type trunk versus type hybrid)! I've got no clue why they used hybrid, other than the GUI which somehow has steered your predecessor in that direction. Make sure to use trunk instead of hybrid mode. No other port/interface specific settings are defined. What I actually see is that all ports - Uplink ports included (marked with port link-type hybrid) - were set with stp edged-port enabled and port auto-power-down. Will be helpful a reboot of both Switches once the new setup is operational (STP recalculation)? What's about BPDU/Loop Protection on all (Edge) ports but Trunk ones? What's about STP over the new Trunk and, in general, globally on the Switches (Is recommended to use MSTP or is there a way to define the 'Core' Switch as the primary?)? Is the above procedure sufficiently correct?ДЄre above steps summarized in the right order?

If all traffic (tagged/untagged) is flowing flawlessly reset the link-port type and VLANs settings set on ports initially used for the Uplink.Check the VLAN traffic passes through the new formed 4 aggregated ports' Trunk.Connect the designated 4 ports of the LAG on each side.Disconnect the actual single cable/port Uplink between Switches.

Set the VLAN tagged/untagged on the new Trunk on each side.

Define the LAG (Trunk): members and protocol (LACP Dynamic) on each side.

Initially NOT connect the 4 dedicated ports (of the new LAG).

Another physical Firewall port manages VLAN 1 (Default Gateway for the entire VLAN 1 Subnet).ДЄFAIK the STP is enabled in RSTP mode ( stp mode rstp and stp enable).ДЇor both new LAGs I'm going to use 4 ports (let me say from port 1/0/45 to port 1/0/48) on each Switch.ДЄFAIK I'm going to (please correct me if I'm wrong): VLANs were been defined yet on both Switches (VLAN 1 as default VLAN and VLAN 5 used for WiFi Guests traffic only), VLAN 5 has IP Address assigned a specific physical Firewall port connected to the 'Core' HPE 1920 Switch is dedicated to VLAN 5 traffic. What are the best practices to follow in doing such type of change? I'm going to redefine the actual inter-connection between those Switches by moving from a single port Uplink scenario (with involved interfaces actually set both with port link-type hybrid, port hybrid vlan 5 tagged and port hybrid vlan 1 untagged) to a new 4 ports LAG scenario that will use LACP (Dynamic).

The key point here is that Switches are actually connected with just one port Uplink.ДЄctually I'm not in the position to change the LAN topology as I want but I'm able to use at least more uplinks cables to enhance overall traffic throughput (since there are may Clients connecting to various Servers) and connection resiliency (against cable/port failure) between those Switches. Hello, I inherited a simple LAN (basically two identical HPE OfficeConnect 1920-48G Switches) where, topologically speaking, one Switch acts as Access for Clients (all Clients are connected to to it) and the other acts as Core for Appliances (Servers, NAS and Firewall are connected to it).

HPE Blog, Austria, Germany & Switzerland.

What is the best lag switch