Cloud Managed Networks

I always strongly recommend you don't start configuring the switch outside of Central. Adopt your switches into Central and use the UI Group configuration mode. Only use Template mode when you require settings that are unavailable via UI Groups or you have a specific need that means Template Groups provide you the best functionality (always UI Groups unless you can't for some reason, is my rule of thumb).

For switches that are to be stacked follow the ZTP process for stacking. Read the documentation on how that works here: https://www.arubanetworks.com/techdocs/central/2.5.8/content/nms/aos-cx/sw-stk-cx/sw-stk-cx-ui.htm

Hi @Ronin101

By my opinion UI groups for CX switches are really convenient. You can use MultiEdit for any feature not available in UI. Template groups do have their strong points. If you have many switches with same overall configuration that differs in minor things like number of ports etc... template groups can be beneficial.  If you have more diverse configuration MultiEdit will be easier to use.

Best, Gorazd

Hi @Ronin101

By my opinion UI groups for CX switches are really convenient. You can use MultiEdit for any feature not available in UI. Template groups do have their strong points. If you have many switches with same overall configuration that differs in minor things like number of ports etc... template groups can be beneficial.  If you have more diverse configuration MultiEdit will be easier to use.

Best, Gorazd

I always strongly recommend you don't start configuring the switch outside of Central. Adopt your switches into Central and use the UI Group configuration mode. Only use Template mode when you require settings that are unavailable via UI Groups or you have a specific need that means Template Groups provide you the best functionality (always UI Groups unless you can't for some reason, is my rule of thumb).

For switches that are to be stacked follow the ZTP process for stacking. Read the documentation on how that works here: https://www.arubanetworks.com/techdocs/central/2.5.8/content/nms/aos-cx/sw-stk-cx/sw-stk-cx-ui.htm

Hi @Ronin101

By my opinion UI groups for CX switches are really convenient. You can use MultiEdit for any feature not available in UI. Template groups do have their strong points. If you have many switches with same overall configuration that differs in minor things like number of ports etc... template groups can be beneficial.  If you have more diverse configuration MultiEdit will be easier to use.

Best, Gorazd

I always strongly recommend you don't start configuring the switch outside of Central. Adopt your switches into Central and use the UI Group configuration mode. Only use Template mode when you require settings that are unavailable via UI Groups or you have a specific need that means Template Groups provide you the best functionality (always UI Groups unless you can't for some reason, is my rule of thumb).

For switches that are to be stacked follow the ZTP process for stacking. Read the documentation on how that works here: https://www.arubanetworks.com/techdocs/central/2.5.8/content/nms/aos-cx/sw-stk-cx/sw-stk-cx-ui.htm

Hi @Ronin101

By my opinion UI groups for CX switches are really convenient. You can use MultiEdit for any feature not available in UI. Template groups do have their strong points. If you have many switches with same overall configuration that differs in minor things like number of ports etc... template groups can be beneficial.  If you have more diverse configuration MultiEdit will be easier to use.

Best, Gorazd

I always strongly recommend you don't start configuring the switch outside of Central. Adopt your switches into Central and use the UI Group configuration mode. Only use Template mode when you require settings that are unavailable via UI Groups or you have a specific need that means Template Groups provide you the best functionality (always UI Groups unless you can't for some reason, is my rule of thumb).

For switches that are to be stacked follow the ZTP process for stacking. Read the documentation on how that works here: https://www.arubanetworks.com/techdocs/central/2.5.8/content/nms/aos-cx/sw-stk-cx/sw-stk-cx-ui.htm

Hi @Ronin101.

MultiEdit is equivalent to UI configuration. It will allow you to configure any feature (active by your subscription tier) on the CX switch(es). 

It's not limited to show commands as it is CLI when you have switch managed by Central. 

MultiEdit will show you current switch(es) configuration and will allow you to edit (add, modify, delete config lines) it for one or more switches. 

Here you have lab guides for CX switches. Look for NetEdit labs.

NetEdit Series
AOS-CX Simulator Lab - NetEdit 2.1 Part 1
AOS-CX Simulator Lab - NetEdit 2.1 Part 2
AOS-CX Simulator Lab - NetEdit 2.1 Part 3
AOS-CX Simulator Lab - NetEdit 2.1 Part 4

Best, Gorazd

Hi @Ronin101

By my opinion UI groups for CX switches are really convenient. You can use MultiEdit for any feature not available in UI. Template groups do have their strong points. If you have many switches with same overall configuration that differs in minor things like number of ports etc... template groups can be beneficial.  If you have more diverse configuration MultiEdit will be easier to use.

Best, Gorazd

I always strongly recommend you don't start configuring the switch outside of Central. Adopt your switches into Central and use the UI Group configuration mode. Only use Template mode when you require settings that are unavailable via UI Groups or you have a specific need that means Template Groups provide you the best functionality (always UI Groups unless you can't for some reason, is my rule of thumb).

For switches that are to be stacked follow the ZTP process for stacking. Read the documentation on how that works here: https://www.arubanetworks.com/techdocs/central/2.5.8/content/nms/aos-cx/sw-stk-cx/sw-stk-cx-ui.htm