Disabling interface on VS

[_Daniel_]

Hi All,

We're aware on how to remove an interface on a VS by using the vsx_provisioning_tool; but what would be the best way to just disable a bond "sub-interface" on a VS -in a VSX cluster.

Is it by using the below commands:

On VSX member 1 (where our VS is active)

set vsx off

set interface bond2.15 state off

set vsx on

And repeat the above on VSX member 2 (where our VS is standby)

[the_rock]

That sounds logical, based on below as well

Best,

Andy

https://community.checkpoint.com/t5/Security-Gateways/Remove-interface-from-VSX-systems/td-p/65004

[JozkoMrkvicka]

You want to delete only VLAN 15 configured on bond2, or delete complete bond2 logical interface ?

[_Daniel_]

Hi Jozko,

Not delete, rather disable vlan15 on bond2, i.e. bond2.15 -we need to re-enable back in some time.

[JozkoMrkvicka]

The correct way is to delete VLAN from Topology tab within affected VS in SmartConsole. Do not forget to install policy afterwards.

Once the VLAN is needed again, just add it back.

[_Daniel_]

To get you right:
1- disable the interface from clish
2- delete it from the Topology tab for the affected VS in SmartConsole
3- push the policy

To reactivate it, just reverse the above steps

[JozkoMrkvicka]

Disable interface from CLI within VS is not needed. SmartConsole will remove it during provisioning proccess (once you click OK with deleted VLAN on VS object).

[Matlu]

Hello

Is it possible to disable an interface that is part of a VSX Cluster?

I have a lab environment, where the Eth2 interface is the SYNC interface between my VSX1 and VSX2 box

My Cluster does not “wake up”, and emphasizes that the problem is the Eth2 interface

I have done everything at VMWARE level but I still can't fix it

I want to logically shut down the Eth2 interface from each box

Is this possible?

Could you guide me with the steps to follow?

Thanks

[the_rock]

I believe generic linux command would be if eth2 down

Andy

[Lari_Luoma]

I have tested setting vsx wrp-interface down simply with ifconfig. It won't survive reboot though, but will work.