Scenario: Rolling upgrade from ArubaOS-CX 10.01 (say 10.01.0030) to 10.02 (say 10.020010).
Two doubts reading ArubaOS-CX 10.02.0010 in preparation to a scheduled upgrade:
Why the no keepalive command is needed to be executed on both VSX members as a preparatory step before booting new software version? ...is it still necessary if only VSX LAGs are used to downlink hosts/devices?
How can the ISL Keepalive be established automatically again after the upgrade (as written on ArubaOS-CX VSX Guide for 10.02: "Keepalive is restored later when the VSX configuration is applied" Step 3 page 8) if it is then requested to save configuration after the issue of no keepalive command (Step 5 page 9)? ...there isn't a following step on the described rolling upgrade procedure where the keepalive command is required to be reapplied to reestabilish the ISL Keepalive again.
Am I wrong? Am I misunderstanding listed rolling upgrade preliminary steps?
Side note: just an example, I really don't understand the "VSX LAG secondary switch" terminology used in VSX Guide...shouldn't it simply be "VSX secondary switch"?