topic Re: Unable to create regular interface on VSX Virtual System in Firewall and Security Management

Unable to create regular interface on VSX Virtual System

RichUK — Mon, 10 Oct 2022 17:10:41 GMT

Hi,

We had our VSX cluster upgraded from R80.20 to R81.10 take 66 last week by a 3rd party support company. After the upgrade, both gateways in the cluster were showing 93% memory utilisation. The chap doing the upgrade said it was because each interface was configured as a virtual switch, and each switch was taking up memory, 13 in total. He also said it is worth deleting the virtual switch and adding a regular interface on the VS.

So, the virtual switch was removed from the VS, then the virtual switch was deleted and polices installed. Then on the correct VS, we added a regular interface on the correct bond and vlan..... and nothing worked.

The interface on the VS shows the 192.168.196.x address instead of the VIP.

There are 3 VS, we tried exactly the same on another VS and it worked immediately.

Now, the VS we are having issues with is showing a warning in smart console, but doesn't show anything when we open Device & License Information. We think the issue with the interfaces is related to the warning on the VS

Any ideas?

Thanks

Rich

Re: Unable to create regular interface on VSX Virtual System

PhoneBoy — Mon, 10 Oct 2022 19:14:37 GMT

When you say nothing worked, what was the precise behavior and errors shown?
Do you have the latest JHF installed?

Re: Unable to create regular interface on VSX Virtual System

RichUK — Wed, 18 Jan 2023 11:56:25 GMT

Hi, sorry for the delay in responding. We ending up raising a TAC case and even the engineer said it was an interesting case.

However, long story short, the VS showing as a warning with no visible issues, resolved itself when I accidently rebooted the management server.

As far as the interface IP address not bonding to the regular interface. The problem identified itself when a virtual switch is removed and a regular interface is added against the VS. We were able to resolve this problem by simply restarting the VS after adding the regular interface. fw vsx restart_vs [id]