cancel
Showing results for 
Search instead for 
Did you mean: 
Post a Question
Highlighted
Philip_W
Nickel

rename VSX cluster member

Hi Checkmates,

Our customer's wants to upgrade his environment from R77.30 to R80.20.

Problem is: he has a VSX cluster with cluster members named 'fw1' and 'fw2'. After importing the SMS database to a new R80.20 management server the Validations tab tells us that "more than one object named fw1 exists" (the other being a default service FW1).

Long story short: we have to rename VSX cluster member 'fw1' before we can consider upgrading. In my lab I experimented with vsx_util:

- vsx_util add_member to add a Dummy gateway

- vsx_util remove_member to remove fw1

but this can't be used: "A previous remove member operation did not complete for..." because there is no SIC with the Dummy gateway, which also prevents policy installs to the remaining VSX member.

TAC told us to use vsx_provisioning_tool (and to contact Professional Services 🤔), but after reading the documentation and testing some commands I don't see how that would work.

Anyone?

Ph.

0 Kudos
4 Replies

Re: rename VSX cluster member

If I remember correctly you when you turn on the following VSX debugs it skips the provisioning process and allows you to make changes without communication:

#fw debug fwm on TDERROR_ALL_VSXM_DBG_SKIP_PING=INFO
# fw debug fwm on TDERROR_ALL_VSXM_DBG_SKIP_INSTALL=INFO
#fw debug fwm on TDERROR_ALL_VSXM_DBG_SKIP_PULL_SIC=INFO

Make changes to VSX gateway

Disable debugs with #fw debug fwm off

Might try this in your lab to see if it will let you delete.

0 Kudos
Philip_W
Nickel

Re: rename VSX cluster member

Thanks Alejandro, I'll test it tomorrow!

0 Kudos
Philip_W
Nickel

Re: rename VSX cluster member

I'm afraid this didn't solve it. Still getting:

"Previous remove member operation was not completed. Run 'vsx_util remove_member' again to resume operation."

I'll dive a bit deeper still maybe removing the whole cluster & recreating it will be the only solution.

0 Kudos

Re: rename VSX cluster member

When you run the 'vsx_util remove_member' again, you can abort the previous operation. Then you can try it again.
Regards, Maarten
0 Kudos