Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Machine_Head
Advisor
Advisor
Jump to solution

VSX - Residual warp links

Hello there,

 

Having a pesky little issue with a virtual system.
The deployment of a vswitch fails due to a residual warp link in the gaia OS config. (the warp link DOESNT exist in the management VSX config)

 

SETUP:
MDM - 2 domains
VSX Cluster Pair R81.20 -JHF119

3 VS sharing an interface over a vswitch.

Issue:
New VS is added, but the Vswitch fails to join in 1 of the nodes.

The residual warp links exist because the VS was initially added on a different MDM domain, and was removed and added back onto a different domain. Somewhere along that process of doing that may have produced that leftover.

 

error when adding the VSerror when adding the VSwarp links on gaia OS in problematic nodewarp links on gaia OS in problematic nodewrpj512 on the vswitch looks like a local loopbackwrpj512 on the vswitch looks like a local loopback

1) Opening the vswitch and clicking OK pushes policy but doesnt remove the extra warps.
2) TAC not being extra helpful  ( very helpful TAC resolved the issue!) so far and we are in a hurry, suggesting reboots and VSX reconfigures for which we need a maintenance window we can't afford right now.

What i'm thinking is to bypass the VSX shell and delete those residual interfaces.
Is it safe to do that and not cause other major issues? Even at least to try something before going for a more involved solution?

Appreciate everyones thoughts.

 

 

0 Kudos
1 Solution

Accepted Solutions
Machine_Head
Advisor
Advisor

TAC helped us remove the bugged interfaces with this command:

[Expert@HostName]# dbset vsx

[Expert@HostName]# dbset :save

[Expert@HostName]# dbset wrpxxx

[Expert@HostName]# dbset vsx t

[Expert@HostName]# dbset :save

[Expert@HostName]# grep 320 /config/db/initial

 

After removing the interface issue has been resolved

View solution in original post

3 Replies
Bob_Zimmerman
MVP Gold
MVP Gold

I can't think of any way I would trust to fix this other than a reset_gw followed by a vsx_util reconfigure. Even that might not work, though, as it only causes the firewall to be rebuilt based on the configuration in the management. If the management database has somehow gotten into an inconsistent state, the firewall may be correctly doing what the management tells it to do.

0 Kudos
Machine_Head
Advisor
Advisor

TAC helped us remove the bugged interfaces with this command:

[Expert@HostName]# dbset vsx

[Expert@HostName]# dbset :save

[Expert@HostName]# dbset wrpxxx

[Expert@HostName]# dbset vsx t

[Expert@HostName]# dbset :save

[Expert@HostName]# grep 320 /config/db/initial

 

After removing the interface issue has been resolved

PhoneBoy
Admin
Admin

dbset...memories of Nokia IPSO 🙂

0 Kudos

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events