- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- clusterXL failover and dynamique routing
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
clusterXL failover and dynamique routing
Hi all,
I'm doing ebgp with a cisco router and gateway clusterXL; And that works fine. It uses the clusterXL VIP of the gateway to establish the ebgp session with the cisco router.
But when i do a clusterxl failover, the eBGP session on the standby member (newly master) takes about 40sec for passing from "idle state" to "established state" while clusterxl switch was done imediately..
The problem is that this switchover makes a blackhole trafic during 40sec.
Do you know if there is a way to tune the switchover ? for exemple to synchronize clusterXL switchover with ebgp session ?
or something else ton decrease this outage time ?
Nb: I use r81 version on security gateway
Thank you for your reply.
kind regards
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes it's recommended in such scenarios.
Sets the Check Point system to maintain the forwarding state advertised by peer routers even when they restart.
This minimizes the negative effects caused by the restart of peer routers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Is graceful restart configured in this scenario? Please see sk100499.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Chris_Atkinson ,
GR is not enabled.
Does it means that if i enable it, the newly master will forward packet even if the bgp session is not yet bring up ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes it's recommended in such scenarios.
Sets the Check Point system to maintain the forwarding state advertised by peer routers even when they restart.
This minimizes the negative effects caused by the restart of peer routers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Ok. Thank you very much for your lights @Chris_Atkinson .
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Not a problem.
Also Note - In a cluster, you must select a Router ID and make sure that it is the same on all cluster members.
![](/skins/images/84DAB6BD358ECB13CE1094473F6E2961/responsive_peak/images/icon_anonymous_message.png)