VSNext and MDPS?

[Bob_Zimmerman]

One of the big reasons I use VSX is so I can handle management routing separately from through-traffic routing. Only VS 0 is able to reach our managements. With VSNext, each VS has a separate management warp which has to be able to reach that VS's management server.

Is there a way to manage the VSs through VS 0 like with older VSX?

Do we need to use MDPS or something to get this?

How would MDPS interact with VSNext, considering they are both ways of managing network namespaces?

[PhoneBoy]

Unlike legacy VSX, it's possible to have VSes managed by different management servers on the same physical gateway.
That necessitates each VS being able to reach its management directly instead of versus VS0.

At least prior to R82, MDPS and Maestro (would impact ElasticXL) were not compatible.
I don't see it listed as a limitation in R82, so maybe this will work?

[Chris_Atkinson · Accepted solution]

Unfortunately sk138672 limitations currently lists MDPS & VSnext as an unsupported combo.

See: PMTR-116515

[PhoneBoy]

However, there is something in the latest JHF that might help:

PRJ-60148, PMTR-113933

VSNext

UPDATE: Rather than using the management switch, it is now possible to choose a different management interface for each virtual system (VS).

[Bob_Zimmerman]

Unfortunately, this doesn't help any of my VSX deployments.

[Chris_Atkinson]

For those that need this routing isolation for Mgmt please raise the requirement with your local office / SE so the RFEs are documented.

[andrej_kascak3]

hello PhoneBoy, is there some SK, or admin guide reference sharing more details about this update? Thank you!

[PhoneBoy]

Unfortunately, there is no details about this.
However, given that "Management Interface" is a concept in Gaia itself and the networking details for a VS are configured via (g)clish now instead of SmartConsole, I'd say that's probably where you do it.
Might check with TAC to confirm.