Cloud Managed Networks

 View Only
Back to discussions
Expand all | Collapse all

CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

This thread has been viewed 71 times

  • 1.  CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted Mar 24, 2026 01:17 PM

    CNX needs to change the way it applies config. Let us create all the changes needed, and then press a "Apply config" button like in AOS 8.
    At that point it should upload a new "finished" config file to the switch and enable it.

    Right now where it applies config line by line - and right after you edited a profile, you are unable to do any automatic/remote setup of switches if you want a management SVI interface in a something other than VLAN 1. That includes moving a switch from Classic central to New Central. You need physical access to console or change the uplink port during setup to finish.

    I have decided to pass on CNX for switches that does not have a dedicated management network interface connected to a different management network (not impacted by central changes).



    -------------------------------------------


  • 2.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted Mar 27, 2026 04:31 AM

    I think it's possible to change the management IP to another VLAN without console access. I have not seen that config is applied line by line, but like in batches allowing such a change.

    But with your concerns, please work with your local HPE Networking team on this to get actual information and if there really are issues or lacking functionality, they can help you further.



    ------------------------------
    Herman Robers
    ------------------------
    If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.

    In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
    ------------------------------



  • 3.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted Mar 27, 2026 08:57 AM
    Edited by US-86ba77 Mar 27, 2026 08:59 AM

    As you have to change the configuration of the VLAN (Enable L3, ...) and at the same time assign a new default route for the new SVI/subnet this will be applied in separate steps and will render the switch unreachable! As Tue mentioned we need a possibility to stop applying configuration to a device until all is defined.



    ------------------------------
    Greez,
    Uli
    ------------------------------

    Original Message


  • 4.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted Apr 02, 2026 06:03 AM

    On a very high level it is possible to achieve this workflow if there is pre configuration for the device. Multiple scenarios are being internally validated . We will publish a write up in  documentation in couple of weeks with a step by step process.  



    ------------------------------
    -Mubeesh
    ------------------------------

    Original Message


  • 5.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted Apr 02, 2026 08:39 AM
    Thanks, Mubeesh, looking forward to that!



    Original Message


  • 6.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted Jun 15, 2026 06:46 AM

    Hi @Mubeesh

    Any progress on this?

    My costumers mainly use CX 6000/6100 series switches, and they (I do to...)  insist on using a dedicated management VLAN that is NOT VLAN 1.
    This effectively renders the switches impossible to setup from scratch/ztp - or to migrate from classic Central to New Central without manual Intervention for every device.
    You will need console "Aruba-central support-mode" OR move the initial uplink port to a configured uplink port after setup (and then configure the left over initial uplink port).


    Original Message


  • 7.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 27 days ago

    Sorry this has been delayed as there were some issues that had to be fixed in this path . 

    Please find a validated method to achieve uplink VLAN change with ZTP here :

    https://arubanetworking.hpe.com/techdocs/new-central/content/cfg/get-start/conf-upl-vlan.htm



    ------------------------------
    -Mubeesh
    ------------------------------

    Original Message


  • 8.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 5 days ago

    So I'm back from vacation now, and was looking forward to check the guide.

    But unfortunately your link does not work. Has the guide been invalidated and removed, or have you just made a typo?


    Original Message


  • 9.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 5 days ago

    Not a typo, that link really is dead. It returns a proper 404, and the topic is gone from the New Central doc navigation even though the other pages in the same section are all still there, so it looks like it got pulled rather than moved.

    The good news is the procedure exists and it does cover your case. It walks through staging the new VLAN profile and port profile in Central first, disabling the default VLAN 1 profile, binding the new one as the uplink port profile, and then onboarding over VLAN 1. No console and no cable move, which is what you were after.

    I'd go back to Mubeesh for the current link rather than me guessing at one, since the page clearly moved somewhere during editing and he'll know where it landed.



    ------------------------------
    Dustin Burns

    @Worldcom Exchange, Inc.


    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


  • 10.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 4 days ago

    hi All,

    i'm browsing through this forum hoping to see some related information "which technically is" since I created a new group AOS 10 and migrating a switch from AOS 8 to the same group hoping to manage it in the CNX. I myself use a different vlan for management other than 1, however I totally lost on how to use this cnx. From the feedback here looks like I should stick with the classic central.

    ps. where can i start getting familiar with the configuration in CNX. The classic at least had something on youtube as reference.

    Thanks,


    Original Message


  • 11.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 4 days ago

    Don't read the thread that way. What's being discussed here is narrow, onboarding a switch whose management SVI isn't VLAN 1 without console access. It isn't that CNX is unfit for switches generally. If your uplink comes up on VLAN 1 with DHCP you won't hit this at all, and plenty of switches move across fine.

    For getting started, there's a TUTORIAL series posted on this same board that's the most useful material I've found: New Central configuration for tunnelled WLANs, one for mobility gateways, GreenLake SSO with Entra ID, and a device validation tool using the APIs. Search the board for TUTORIAL and they'll come up. The New Central techdocs site is the reference once you know what you're after.

    On your own migration, the uplink VLAN is the thing to sort out before you move the switch rather than after.



    ------------------------------
    Dustin Burns

    @Worldcom Exchange, Inc.


    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


  • 12.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 4 days ago

    hi Dustin where can I find it? On the forum page I can't even find a filter field search to type.

    Thank you and I appreciate you reply this quick.


    Original Message


  • 13.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 3 days ago

    The search is the magnifying glass at the very top of the page, right side of the black bar next to your profile picture, easy to miss. Type TUTORIAL in there and the series comes up.

    To save you the hunt, here's one to start with: https://airheads.hpe.com/discussion/tutorial-device-validation-tool-for-new-central-using-apis and the rest are linked from the same author's posts.



    ------------------------------
    Dustin Burns

    @Worldcom Exchange, Inc.


    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


  • 14.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 3 days ago

    A colleague found a new link for this:

    https://arubanetworking.hpe.com/techdocs/new-central-review/content/cfg/get-start/conf-upl-vlan.htm



    ------------------------------
    Greez,
    Uli
    ------------------------------

    Original Message


  • 15.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 3 days ago

    Nice find Uli, thanks for posting it. One heads up for anyone bookmarking: that URL sits on the new-central-review path, which looks like the docs review area rather than the production tree, so it may move or break when the page gets promoted. If it goes dark again, search the New Central techdocs for the VLAN uplink onboarding procedure, and ideally HPE republishes this on the main path.



    ------------------------------
    Dustin Burns

    @Worldcom Exchange, Inc.


    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


  • 16.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 2 days ago

    I had a look at this recipie, and it's quite useless as that does not address the problem. It explains how to setup profiles with static IP and routing for another VLAN and preassign that to sites, but is does nothing to resolve the real problem:

    If I have a switchport with VLAN 100 (management VLAN) untagged, and all the other needed VLANs tagged, there is no way I can do ZTP -> reconfigure for a factory new switch without moving links or changing the untagged VLAN temporarely on the switch accepting the uplink.
    Nor is there any way I can migrate an already working managed CX 6100 switch connected to that port, that has it's management IP on a VLAN 100 SVI in the switch config.
    The only two exception are:
    1: I accept management is done using VLAN 1 in the switch going forward and no VLAN 100 exists in the switch (100 is bridged to 1 on the untagged link).
    2: I reconfigure the uplink switch to start using LAG's with only one port in it for the uplink (and allow fallback). Then I need to the same on the new/migrated switch. LAGs is the only option of moving a switchport to a completely new config with only one line of change done on the switch (which is what happens when Central applies config to a switch -> one line at the time).


    Original Message


  • 17.  RE: CNX needs a new way to apply switch config - cannot migrate any switches from Classic to CNX if they are managed using a SVI

    Posted 2 days ago

    You're right, and that's a fair distinction: the doc solves pre-provisioning a new site, not converting a live uplink in place. For your case, where the port's untagged VLAN is the management VLAN and the switch being onboarded has its SVI there, there's no clean path today, because Central applies config a line at a time and there's no transactional way to swap the uplink profile and the SVI together.

    Of your two workarounds, the single-port LAG with fallback is the one I'd standardize on. It's the only construct where the whole port config swings in one commit, which is exactly the property this migration needs, and it leaves you a usable pattern for the next hundred switches rather than a one-off hack.

    Beyond that, this is squarely a product gap worth filing. Push it through your account SE as a feature ask for transactional port-profile application during onboarding. The more customers that land it formally, the faster it moves, and this thread is good evidence.



    ------------------------------
    Dustin Burns

    @Worldcom Exchange, Inc.


    If my post was useful accept solution and/or give kudos
    ------------------------------

    Original Message


Related Content