topic Re: VSNext Bond configuration and connection with Cisco VPCs in Firewall and Security Management

VSNext Bond configuration and connection with Cisco VPCs

T_Sonnberger — Mon, 16 Feb 2026 15:03:04 GMT

Dear CheckMates,

we are currently setting up a VSNext Cluster and ran into some issues with the bond configuration/ the connection with the Cisco VPCs connected to our cluster.

This is our physical setup:

It's a two site active/standby setup.

bond2 - consisting or eth1-01 and eth1-02

In total we have 4 virtual systems - each having a VLAN on bond2

vs1 - bond2.1095

vs2 - bond2.1096

vs3 - bond2.1097

vs4 - bond2.1098

The Problem is:

I see that the bond only shows on VS1 and VS4, claiming no Bond is configured on VS2 and VS3

I can ping the HSRP Interfaces in each VLAN so I think the VLAN config etc. should be fine but in cphaprob -a if the bond does not show up as synced interface on vs2 and vs3....

Does anyone of you have some experince with a similar setup or at least have some ideas (troubleshoot commands) how to get some more information on this or what else could be checked?

Thanks in advance and BR,

Thomas

Re: VSNext Bond configuration and connection with Cisco VPCs

Wolfgang — Mon, 16 Feb 2026 15:20:35 GMT

@T_Sonnberger how did you create your bond and VLANs ?

create your Bond-interface and the VLANs in VS0 and then add the VLANs (only the VLAN interfaces, not the bond) to your virtual systems as needed.

Re: VSNext Bond configuration and connection with Cisco VPCs

Lari_Luoma — Mon, 16 Feb 2026 19:42:16 GMT

Step 1: Make sure you have the recommended JHF installed.
Step 2: Created bond interface and VLANs in VS0
Step 3: Assign VLANs to VSs you want.

Re: VSNext Bond configuration and connection with Cisco VPCs

emmap — Tue, 17 Feb 2026 02:56:01 GMT

The interfaces are not showing up as monitored interfaces, but they are there in the interface list so they have been configured correctly. They are not being monitored because the cluster is only monitoring the lowest and highest VLANs on the bond, with the idea being that if those two VLANs are working then the rest of them probably are too.

If you want to monitor all VLANs (and hence, mark the interface down for all VSs if one VLAN has an issue) then you can enable that option. The procedure in this SK should work. https://support.checkpoint.com/results/sk/sk92826

Re: VSNext Bond configuration and connection with Cisco VPCs

T_Sonnberger — Tue, 17 Feb 2026 05:38:54 GMT

Thank you so much - this is it!

I have just removed bond2.1098 on vs4 and now see bond2.1097 on vs2...

I was so confused that it said "no bond configured" that I never took into consideration that it's just about VLAN monitoring.

BR,

Thomas

Re: VSNext Bond configuration and connection with Cisco VPCs

T_Sonnberger — Tue, 17 Feb 2026 05:40:23 GMT

Thanks for the reply - that's how I have done it. Assigned bond2 to VS0, then added the VLANs in VS0 context and moved them to the specific VS.

BR,

Thomas