Hi Kyle!
I see absolutely no issue to start VSX configuration with one member, especially in this case when getting the second pair member is only a matter of time. I mean that you already know that the currently available switch will be VSX member and won't work as standalone device ('standalone' in this case means a switch without any plans to use VSX).
You can safely start with planning your VSX setup - which ports will be used for ISL, which ports will participate in multi-chassis LAGs etc etc. When you will get a strict plan, you can start configuring your switch as VSX member:
- assign it a hostname
- create VLANs needed
- create ISL interface (preferrably a LAG). It doesn't matter that it will stay down at this stage, better have it configured prior to receiving the second device.
- enable keepalive interface. Same story here - it will stay down so far, but it is handy to have it pre-configured.
- assign the swtich primary VSX role
- create multi-chassis LAGs and assign ports on this switch to those LAGs. While secondary device is not connected, your LAGs will work with half capacity, but still they will be LAGs. Even a single-port LAG still a LAG, e.g. it uses LACP and is fully prepared to be expanded with additionally added ports if needed. It is easier than to configure standalone port facing your server and then convert the port to a LAG when second VSX switch arrives.
- create active gateway SVI for VLANs that will be routed by this VSX pair.
In other words make the configuration to look as it is a full VSX pair, but secondary member failed, was removed from the stack and will be replaced soon. At the end of the day when (or if) one of your VSX switches will fail, you will end up in the same temporary situation - VSX config with single device. This is not very different from your current situation when you have only one VSX member thanks to logistics company :-) When your secondary switch will finally arrive, you will just configure it accordingly to join the VSX pair, set it to the rack and connect network cables. If configuration is correct, the VSX pair will be created and both switches will start operating as VSX.
------------------------------
Ivan Bondar
------------------------------
Original Message:
Sent: Oct 26, 2021 08:24 PM
From: Kyle Spooner
Subject: VSX setup, 1 member only
We ordered 4x 8325 in April (Two for core and two for a new office build) and we received 3 of them this month. The fourth got lost (screw you purolater) and the replacement has a date of February 2022
New office move in is planned for November 2021, so October was tight enough as is.
Obviously not pleased, and it's not ideal.. but if I configured VSX sync,Multichassis lags, isl, etc exactly as planned in a redundant fashion now… would be simple to plug-in once we get the second member, or would I have to essentially scrap and wipe entirely?
This is my first big engagement with Aruba so experience with the platform is still growing
------------------------------
Kyle Spooner
------------------------------