This website uses cookies. By clicking OK, you consent to the use of cookies. Click Here to learn more about how we use cookies.
OK
ABOUT CHECKMATES & FAQ
Create a Post
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Help
Kaloyan_Metodie
Participant
a week ago

BGP issues after upgrade 80.10 -> 80.30

Hi all 
We are stuck into a strange issue when upgrading a cluster from 80.10 to 80.30 
Short description: 

We have two 80.10 GW appliances, facing two internet connections with BGP, advertising one /24 with equal metric via both providers. 

Both BGP sessions are Established on the primary cluster member (confirmed in HA and LS mode). 

After upgrading to 80.30 one of the BGP comes up without issues, the other stays in Active state. 

routed.log says: interface eth1 has NO IPv4 CLUSTER address

Error is logged even though cluster addresses are properly configured and the BGP won't move to Established state. 

Shutting down the working BGP (disable interface) and waiting for the other to come up did not help/ 

We tested this on 4600 appliances then did the config from scratch on a brand new 6400 - same issue. 

I would appreciate any suggestions 🙂 

 

 

0 Kudos
Reply
6 Replies
Kaloyan_Metodie
Participant
Monday
In response to PhoneBoy

Yep, and the result of cphaprob -a if is looking good. 

0 Kudos
Reply
PhoneBoy
Admin
Admin
Tuesday
In response to Kaloyan_Metodie

TAC case is probably in order then:

Reply
Kaloyan_Metodie
Participant
Tuesday
In response to PhoneBoy

We scheduled a meeting with TAC for tonight as this is impacting prod firewalls and downtime is a bit tricky. 
I was hoping that someone ran into the same issue and could help reduce the time to resolve it. 
Will share results after debug digging 
Anyways - thank you for the reply 🙂  

0 Kudos
Reply
Sundeep_Mudgal
Employee
Employee
Wednesday

BGP is not supported on non-clustered interfaces in a clustered environment. Thanks for checking routed.log. If this is a clustered environment and eth1 is not configured with cluster VIP then please configure it.  If eth1 is configured with clustered VIP then please check the output of:

 

cphaprob -a if ---> this should show whether VIP is configured and installed. 

 

show routed cluster-state detailed -------> this should show whether routing daemon has the VIP. 

Reply
Dilian_Chernev
Contributor
6 hours ago
In response to Sundeep_Mudgal

Hi, I was involved also in debugging this issue and we ran the both commands.

cphaprob -a if - shows that eth1 exists and VIP is configured and installed, also VIP was accessible from outside world.

show routed cluster-state detailed - eth1 is missing from here. Only 3 from 4 VIP interfaces were shown here.

We had a remote session with TAC and issue was resolved, but it was not very clear what was the problem a how it was resolved.
The last thing that we do before resolving, was aligning host name of the machine and object name in policy.
After rebooting the device, BGP sessions to both providers were established and working.

I am still curious what could be the reason for VIP address missing in routed configuration and how to fix it

Thanks 

 

 

0 Kudos
Reply