VSX with BGP in different GAIA versions

[yura_k]

We noticed that the BGP protocol configuration for virtual systems in different GAIA versions began to differ.

We have a virtual system that is peered via BGP. Peering interface settings:
GW1-VSX-81.20:1> show interface eth2.102
state on
mac-addr 00:50:56:ae:75:cd
type vlan
instance 1
ipv4-address 10.1.102.77/24

Virtual system service interface settings:
eth2.102@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
inet 192.168.196.17/28 brd 192.168.196.196.31 scope global eth2.102

In versions R80.40 and R81.10 the configuration of the peer link could look like this:
set bgp external remote-as 65001 on
set bgp external remote-as 65001 local-address 10.1.102.77 on

And in R81.20, it became impossible to bind interface address to bgp remote-as on a virtual system:

GW1-VSX-81.20:1> set bgp external remote-as 65001 local-address 10.1.102.77 on
RTGRTG0019 BGP: Address 10.1.102.77 does not belong to any interface.

and we have to use such as workaround:
set bgp external remote-as 65001 on
set bgp external remote-as 65001 local-address 192.168.196.17 on

[Wolfgang]

@yura_k with R81.20 some changes are implemented for dynamic routing protocols to be more compliant with the RFCs and recommendations. We had a problem with OSPF interfaces in the past after switch to R81.20 https://community.checkpoint.com/t5/Maestro/max-interfaces-OSPF/m-p/199829#M2337

Open a case with TAC to check your need.

[emmap]

If this is a cluster (looks like it is) then you shouldn't be configuring local address per:

https://sc1.checkpoint.com/documents/R81.20/WebAdminGuides/EN/CP_R81.20_Gaia_Advanced_Routing_AdminG...

[yura_k]

Hi Emma! The BGP speaker is a virtual system, not a VSX cluster node.

[emmap]

Yes but it's a VS on a cluster, yes? That still counts. 

[the_rock]

I dont even recall having to configure local address setting.

Andy