Cloud Managed Networks

 View Only
  • 1.  Creating a VSX via New Central?

    Posted Oct 13, 2026 08:44 AM

    Hi, i am currently trying to set up a pair of CX 8360 as a VSX couple and got them to central via ZTP.

    but i dont find any profiles that seem to relate to VSX in new central, nor do i have that option when creating LAG profiles.

    also both of the help documents the search bar is listing when searching for VSX are dead links.

    is this one of the things that still need to be done in old central or am i looking in the wrong place?



  • 2.  RE: Creating a VSX via New Central?

    Posted Oct 13, 2026 08:49 AM

    You're in the right Central, just on the wrong card. New Central does VSX for the 8360 as its own profile, not as a LAG option.

    In the configuration view pick the Site (a VSX pair has to be built at site level, not in the Library), choose the switch Device Function, and on the High Availability card click VSX, then Create VSX.

    That's where Peer 1 and Peer 2, roles, system MAC, the ISL and keepalive live. The ISL LAG can be built from inside that profile's ISL Link drop-down, which is why a plain LAG profile never shows a VSX choice. The VSX Profile page lists the prerequisites, both switches on the site with a device function and showing Synchronized, plus a site level VLAN profile: https://arubanetworking.hpe.com/techdocs/hpe-central/content/get-started-with-hpe-aruba-networking-central/vsx-profile.html

    Going back to Classic wouldn't help. It never had a VSX UI, only templates with a vsx_role variable, per the Classic templates page: https://arubanetworking.hpe.com/techdocs/central/2.5.8/content/nms/aos-cx/get-started/conf-vsx-templt-cx.htm



    ------------------------------
    Dustin Burns
    @Worldcom Exchange, Inc.
    www.wei.com

    - - -
    The comments I post here are my own, and not my employers
    If my post was useful accept solution and/or give kudos
    Personal Blog: www.networkfieldnotes.com
    - - -
    ------------------------------



  • 3.  RE: Creating a VSX via New Central?

    Posted Oct 13, 2026 05:32 PM

    This is our official, recommended procedure at this time. Doe sit cover your use case? We would appreciate your feedback.
    https://community.networking.hpe.com/discussion/how-to-configure-vsx-in-aruba-central-1




  • 4.  RE: Creating a VSX via New Central?

    Posted Oct 14, 2026 08:39 AM

    Thank you and Dustin, the VSX is standing now.
    for the requested feedback on the document, it works as written, but from thr requirements: the switches dont seem to be synced already, since i configured some things with the letters ü and ä in them which did not sync, setting both of those to an "out of sync" state, that i only saw after doing the VSX config. syncing everything at once turned out fine. also, the guide mentions that it only can be done at site level, but i have done so via Device group and not site, and it works out.

    now that leads me to a different question though about asigining port profiles to the now stacked core, i can apply regular ports and LAG ports as i want, but MClag port profiles are unuseable. i assume this is because they need to be applied to all VSX units at once, which isnt an option because i can only edit one switche's interfaces at a time.




  • 5.  RE: Creating a VSX via New Central?

    Posted Oct 14, 2026 09:49 AM

    Glad it's standing, and the device group result is useful feedback, since the VSX Profile page and that how-to both still say site scope only.

    On the MC-LAG: it doesn't need both peers edited at once. New Central builds an MC-LAG one switch at a time. The Configuration FAQ says LAGs must currently be configured at the device level, and that assigning the same port profile to several ports generates a LAG with the specified ID: https://arubanetworking.hpe.com/techdocs/hpe-central/content/frequently-asked-questions-faq/configuration-faq.html So you apply the MCLAG profile to the member ports on Peer 1 at device scope, then the same profile to Peer 2's ports, and the pair matches the two halves by LAG ID. The thing that breaks that is Auto-generate LAG ID: give the profile a fixed ID (say 10), LAG Type MCLAG, LACP ticked, trunk with your VLANs, as on the port profile page: https://arubanetworking.hpe.com/techdocs/hpe-central/content/get-started-with-hpe-aruba-networking-central/creating-a-port-profile-for-switches.html

    If it's greyed out rather than failing on save, paste the exact wording and where you're applying it from. That tells us whether it's scope or the profile.



    ------------------------------
    Dustin Burns
    @Worldcom Exchange, Inc.
    www.wei.com

    - - -
    The comments I post here are my own, and not my employers
    If my post was useful accept solution and/or give kudos
    Personal Blog: www.networkfieldnotes.com
    - - -
    ------------------------------



  • 6.  RE: Creating a VSX via New Central?

    Posted Oct 14, 2026 02:34 PM

    Thanks for the feedback and for validating the procedure.

    Regarding scope, VSX can be configured from both Site and Device Group scope today, although our recommended best practice remains Site scope.

    For MC-LAGs, the current workflow requires a dedicated port profile per MC-LAG ID. After creating the port profiles, you can simplify deployment by using an Interface Profile to apply them across the VSX pair.

    I also appreciate the note regarding synchronization status and the Device Group workflow. I'll create/update some documentation around these topics and post an update in this thread.




  • 7.  RE: Creating a VSX via New Central?

    Posted Oct 15, 2026 06:04 AM

    Thanks, that helps. will we get an option someday to esentially copy-paste Port profile settings? setting up 20 different Port profiles where the only difference is the name and the LAG ID is a hassle, but for right now necessary.




  • 8.  RE: Creating a VSX via New Central?

    Posted Oct 16, 2026 10:40 AM

    Ack! This is being looked into.