I'm trying to configure trunking on an Aruba switch, but I have limited experience with it. We currently have an old ProCurve switch that uses Trnk1, Trnk3, and Trnk6 as trunk ports, which are all set as untagged. I've set up three Link Aggregation Groups (LAGs) on the Aruba switch, with ports in each LAG mirroring the old trunks and keeping all ports untagged. Is this the correct approach, or am I missing something?
3 Answers
From my experience, the Aruba configs are pretty similar to the older ProCurve models. Are you replacing a switch or connecting another one to your setup?
I'm just swapping it out and trying to match the config.
When configuring on Aruba, make sure your LAGs reflect the old trunks. They should have the same member ports and untagged VLANs, along with any other VLANs that need to be tagged. If you only have a single VLAN for things like vmotion or iSCSI traffic, it's best to keep each LAG as an access port with just one untagged VLAN. Avoid mixing in extra tagging or LACP settings unless your setup needs it.
For your LAG ports, ensure to tag the VLANs that you'll be utilizing, but don't forget to leave your management VLAN untagged. This keeps things tidy and ensures you're not sending unnecessary traffic.
It matters whether your Aruba switch is from the older ProCurve family, like the 2930M, or from the newer CX range (like the CX6200). The command-line interface will be very different.