Maestro & VSNEXT management interfaces for VSs

[Wolfgang]

I've a question regarding the management interfaces of virtual systems running VSNext.

Normally with traditional VSX everything is managed via VS0 and the magg01 (MHO ports 1-4)

How about running VSNext on Maestro?

Is the default Virtual Switch with ID 500 (attached to magg01) used to manage all virtual systems? 

Do we need a separate management IP and interface for every virtual system and this interface must be attached to the default Virtual Switch with ID 500 (attached to magg01) ?

Is it the same like with ElasticXL and VSNext  ?

[emmap]

Short answer: yes it's the same as with EXL.

Every VS needs its own connection back to the management server, policy pushes and logging etc no longer go via VS0. It doesn't have to be via the management vswitch (I think this option came in from JHF take 25) and it doesn't have to be a dedicated management interface, but it's probably easier if both of those things are done.

[Martijn]

Hi,

Created a VSNext setup on ElasticXL this week with Smart-1 Cloud management. VS0 uses a different path to the internet than VS1. I removed the magg0 interface from VS1 and configured the default gateway on another production interface and that worked fine. I assume on Maestro this is the same.

And one of the advantages of VSNext is being able to manage different VS's from different SmartCenters. The only way this makes sence if you are able to remove the magg0 interface on VS's that do not need a layer 3 connection to some part of you network.

Regards,
Martijn