Cloud Managed Networks

Hello all,

I'm starting to comissioning of new project in next monday and noted that in CNX devices list shows all VSF members (device are offline at the moment but same thing in another production workspace) which led me to think about what will happen when VSF stack will meet CNX Cloud, all configuration will be overwrited and there is no possibility to configure VSF stacks there in CNX.

I heard something about this matter in webinar or trainings but cannot recall what was the message.. Can someone help me with this one (or do I leave stacks to classic central?)

Hi Jori,

When a NEW stack is onboarded in CNX configuration a basic connectivity import is done. CNX will import the VSF configuration. 

IMO this is also the most easy way to onboard VSF stack in Central. What I always recommend:

1. Built the stack first (auto-stacking)
2. Onboard stack in Central. VSF profile is auto created

In the documentation you can find more about what configuration is imported: https://arubanetworking.hpe.com/techdocs/new-central/content/get-started/onboard-cx.htm#Auto-Imp

For my self speaking. For new deployments I use New Central / CNX config. 

Hope this will answer you question.

Hello all,

I'm starting to comissioning of new project in next monday and noted that in CNX devices list shows all VSF members (device are offline at the moment but same thing in another production workspace) which led me to think about what will happen when VSF stack will meet CNX Cloud, all configuration will be overwrited and there is no possibility to configure VSF stacks there in CNX.

I heard something about this matter in webinar or trainings but cannot recall what was the message.. Can someone help me with this one (or do I leave stacks to classic central?)

Hello Willem

Great news! I have preloaded configurations already to switches for basic connection parameters and VSF stacking configs so that Classic Central can be used for onboarding but I decided to use CNX afterwards because I figure out how to roll devices from Classic to CNX without OOB/mgmt network or vlan 1 dhcp services.

One more question: While I see all members of VSF there in CNX device list, do I configure management vid only to Conductor? (I think yes but if you might know this... Site is quite large so I don't really want to test this ;) )

Hi Jori,

When a NEW stack is onboarded in CNX configuration a basic connectivity import is done. CNX will import the VSF configuration. 

IMO this is also the most easy way to onboard VSF stack in Central. What I always recommend:

1. Built the stack first (auto-stacking)
2. Onboard stack in Central. VSF profile is auto created

In the documentation you can find more about what configuration is imported: https://arubanetworking.hpe.com/techdocs/new-central/content/get-started/onboard-cx.htm#Auto-Imp

For my self speaking. For new deployments I use New Central / CNX config. 

Hope this will answer you question.

Hello all,

I'm starting to comissioning of new project in next monday and noted that in CNX devices list shows all VSF members (device are offline at the moment but same thing in another production workspace) which led me to think about what will happen when VSF stack will meet CNX Cloud, all configuration will be overwrited and there is no possibility to configure VSF stacks there in CNX.

I heard something about this matter in webinar or trainings but cannot recall what was the message.. Can someone help me with this one (or do I leave stacks to classic central?)

Hi Jori,

During stack onboarding, CNX will generate a stack ID. This is a logical ID that is being used. All members in the stack grouped together as a single device. So you will have 1 management IP per stack. Central is not changing the VSF behavior. 

Hereby a screenshot from a VSF stack management via CNX / Central.

A few tips:

• VSF profiles are created a Site level and not at device level
• When configuring interfaces, use Port Profiles. This really helps to simplifies the configuration
• On top of that, you can use interface profiles to automatically assign port profiles to interfaces during onboarding

Documentation: https://arubanetworking.hpe.com/techdocs/new-central/content/home.htm

Hello Willem

Great news! I have preloaded configurations already to switches for basic connection parameters and VSF stacking configs so that Classic Central can be used for onboarding but I decided to use CNX afterwards because I figure out how to roll devices from Classic to CNX without OOB/mgmt network or vlan 1 dhcp services.

One more question: While I see all members of VSF there in CNX device list, do I configure management vid only to Conductor? (I think yes but if you might know this... Site is quite large so I don't really want to test this ;) )

Hi Jori,

When a NEW stack is onboarded in CNX configuration a basic connectivity import is done. CNX will import the VSF configuration. 

IMO this is also the most easy way to onboard VSF stack in Central. What I always recommend:

1. Built the stack first (auto-stacking)
2. Onboard stack in Central. VSF profile is auto created

In the documentation you can find more about what configuration is imported: https://arubanetworking.hpe.com/techdocs/new-central/content/get-started/onboard-cx.htm#Auto-Imp

For my self speaking. For new deployments I use New Central / CNX config. 

Hope this will answer you question.

Hello all,

I'm starting to comissioning of new project in next monday and noted that in CNX devices list shows all VSF members (device are offline at the moment but same thing in another production workspace) which led me to think about what will happen when VSF stack will meet CNX Cloud, all configuration will be overwrited and there is no possibility to configure VSF stacks there in CNX.

I heard something about this matter in webinar or trainings but cannot recall what was the message.. Can someone help me with this one (or do I leave stacks to classic central?)