Difference between revisions of "Configure stacking on Aruba 2930F switches"
From Notes_Wiki
(Created page with "<yambe:breadcrumb self="Configure stacking on Aruba 2930F switches">Switch configuration notes|Switch configuration notes</yambe:breadcrumb> =Configure stacking on Aruba 2930F...") |
m |
||
Line 1: | Line 1: | ||
[[Main Page|Home]] > [[Switch configuration notes]] > [[Configure stacking on Aruba 2930F switches]] | |||
To configure stacking on Aruba 2930F switches use following steps: | To configure stacking on Aruba 2930F switches use following steps: | ||
Line 63: | Line 62: | ||
[[Main Page|Home]] > [[Switch configuration notes]] > [[Configure stacking on Aruba 2930F switches]] |
Latest revision as of 06:11, 19 April 2022
Home > Switch configuration notes > Configure stacking on Aruba 2930F switches
To configure stacking on Aruba 2930F switches use following steps:
- Connect to switch that should become master (commander) and enable vsf using:
- vsf enable domain 1001
- After this switch would reboot and would become first member of vsf. Choose a different domain ID 1-65k+ for every different vsf within organization.
- Then set priority of this switch higher than reset and configure the vsf links. A single vsf link can have up to eight interfaces and connects two specific physical switches. Thus, if you are creating ring topology and connecting switch 2 with both switch 1 and switch 3, then switch 2 will have two links configured, one with ports connected to switch1 and other with ports connected to switch2.
- vsf member 1 priority 160
- vsf member 1 link 1 1/51
- vsf member 1 link 2 1/52
- Note that now that we have enabled vsf domain the ports are 1/51 and 1/52 and not 51, 52. We can see the vsf configuration or port numbering using:
- show vsf
- show interface brief
-
- Here against current switch a * would be shown in "show vsf" output.
- After enabling vsf on first switch connect the links as specified in above ports (port 51 to previous switch and port 52 to next switch) and power on second switch.
- On second swith use:
- vsf member 2 link 1 51
- vsf member 2 link 2 52
- vsf member 2 priority 150
- vsf enable domain 1001
- Assuming port 51 of second switch is connected to port 52 of first switch. Note that we have reduced priority for second switch so that it becomes standby.
- For any additional member switches use:
- vsf member <member-id> link 1 51
- vsf member <member-id> link 2 52
- vsf member <member-id> priority 140
- vsf enable domain 1001
- After every single switch joining the stack keep looking at 'show vsf' output to ensure things are going as per plan.
Removing stack
To remove a switch from stack use:
vsf disable
This might require removing vsf link ('no vsf member <id> link 1 <port>'') before disabling vsf.
Testing stack
We can test stack by powering off a single switch or removing a single connecting cable. However, restoring the component might still leave stack with lot of amber alerts. To remove those amber alerts rebooting the current commander seems to solve the problem:
reload
Note that this means downtime for all hosts / switches connected to master.
Refer:
- https://community.arubanetworks.com/community-home/digestviewer/viewthread?MID=23423
- https://support.hpe.com/hpsc/doc/public/display?docId=a00050273en_us (See VSF - Page 697 - Chapter 30)
Home > Switch configuration notes > Configure stacking on Aruba 2930F switches