how to stop one particular vs in VSX cluster R77.30?

[Amit_Sharma3]

i am looking  for command to stop one virtual firewall on vsx cluster ver. R77.30. 

[Chris_Atkinson]

Hi Amit,

Some commands and tasks are recommended only to be run in consultation with TAC or under specific circumstances. 

Could you please outline the scenario that you are faced with relating to the above requirement so that we might be able to assist further?

Thanks,

Chris

[Amit_Sharma3]

we have one  VSX cluster with 10 virtual firewall , using VSLS . we want to stop 4 virtual firewalls on both side (active/standby). don't want to delete these permanently 

[PhoneBoy]

That doesn't explain WHY you want to stop them, which is the question.

I believe we plan to support this functionality in the future, but do not currently.

[RickHoppe]

I cannot answer for Amit's specific situation, but you can run into a situation where you need to change a file within the context of a single Virtual System followed by a cpstop/cpstart. In some environments it's easier to propose a change for CAB approval when you only are able to restart a single Virtual System and not the whole VSX gateway. This functionality would be very welcome in a future release.

[Sven_Glock]

As far as I know stopping one single VS is not supported

[Alin]

As far as i know :

clusterXL_admin up

clusterXL_admin down

[G_W_Albrecht]

When using VSLS, afaik stoping a VS is impossible as another instance of the VS will take over instantly. Its a feature not a bug...

[Fernando_Segura]

clusterXL_admin down switch ha to the other member, if you try it int the last active member, you get:

Setting member to administratively down state ...
Member current state is ACTIVE(!)
All the members within the cluster have problem/s and the local member was chosen to become active

the only way i'v found to acomplish this is to put all his interfaces down

- switch to vs desired:

vsenv x

- see the name of the interfaces

ifconfig -a | grep HWaddr

- put down one by one ( except the loopback)

ifconfig  <name> down

[RickHoppe · Accepted solution]

I'm not sure if it applies to R77.30 but recently I received this undocumented command for restarting a single VS on R80.10: fw vsx restart_vs <VSID>

Example for restarting VS 3: fw vsx restart_vs 3

[hugothebas]

I know this was posted down in 2020, I'm sorry to resurrect this post, but it helped me now in 2022!

Nice command!

Thanks