Difference between revisions of "Configure lacp or port-channel on Aruba switches (Trunk)"
m |
m |
||
| Line 1: | Line 1: | ||
[[Main Page|Home]] > [[Switch configuration notes]] > [[Configure lacp or port-channel on Aruba switches (Trunk)]] | |||
On Aruba switch lacp or port-channel is called Trunk (Normal VLAN Access / trunk is called tagged /untagged). So we can create a trunk and add members to trunk for ether-channel or lacp operations using: | On Aruba switch lacp or port-channel is called Trunk (Normal VLAN Access / trunk is called tagged /untagged). So we can create a trunk and add members to trunk for ether-channel or lacp operations using: | ||
| Line 27: | Line 26: | ||
[[Main Page|Home]] > [[Switch configuration notes]] > [[Configure lacp or port-channel on Aruba switches (Trunk)]] | |||
Latest revision as of 06:11, 19 April 2022
Home > Switch configuration notes > Configure lacp or port-channel on Aruba switches (Trunk)
On Aruba switch lacp or port-channel is called Trunk (Normal VLAN Access / trunk is called tagged /untagged). So we can create a trunk and add members to trunk for ether-channel or lacp operations using:
trunk trk1 lacp <port-no> trunk trk1 lacp <port-no>
where instead of trk1 we can use trk2, trk3, etc. for additional trunks as and when required.
Refer:
Note that this is quite different than trunk port on Cisco / Dell etc. where all / multiple VLANs traffic is sent in tagged manner. Typical trunk access configuration might look like:
vlan <id> tagged <ports-list> untagged <ports-list> ip address <ip> <netmask>
where we can have multiple VLANs configured as tagged for same interface to make it trunk for those VLANs. If a particular interface has only one VLAN untagged then that interface is similar to access VLAN for that VLAN ID.
Home > Switch configuration notes > Configure lacp or port-channel on Aruba switches (Trunk)
