Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

EBGP issue

Hi experts,

I am facing a issue with BGP connectivity with two remote location. I am creating EBGP neighbor ship with loopback and using two different media. After configuration the BGP was up and I am facing issue during failover scenario. Please find the details.

  • Individual L3 links between A location-B location routers.
  • Loopback interfaces on both end routers used.
  • Two static routes need to be added for B-loopback loopback on A-location router pointing to both WAN IPs.
  • Similarly on B-location router  two static routes for A-location loopback.
  • BFD needs to be configured for static routing on individual links(300ms x 3times).
  • BGP peering will be done with loopbacks on each ends.

Whenever one media fails the BGP is getting down after some time. Kindly suggest.

Configuration scripts attached for reference along with failover logs.

Regards,

Naveen

4 REPLIES

Re: EBGP issue

Naveen,

Configure BFD support for BGP as well, if you need to decrease the fail-over time...

Refer following link:

http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fs_bfd.html

HTH,

Smitesh

Please rate if helpful.

Message was edited by: smitesh kharecha

New Member

EBGP issue

Hi Smitesh,

     I have used bfd on interfaces and configured " neighbor X.X.X.X fall-over bfd "  in bgp. Please let me know anyother options are there?

Br,

Naveen

Hall of Fame Super Silver

EBGP issue

Hello Naveen,

I would try to use different names or groups for the two static routes used to reach the loopback on the other site

You currently have the following configuration:

ip route static bfd GigabitEthernet2/34 10.196.108.9

ip route static bfd GigabitEthernet3/9 10.196.108.13

ip route 10.196.108.24 255.255.255.255 10.196.108.9 name BGP_B_loc

ip route 10.196.108.24 255.255.255.255 10.196.108.13 name BGP_B_loc

ip route 10.196.108.9 255.255.255.255 GigabitEthernet2/34 10.196.108.9 name BGP_B_loc

ip route 10.196.108.13 255.255.255.255 GigabitEthernet3/9 10.196.108.13 name BGP_B_Loc

I would use different names as actually the next-hops are different and the name option refers to a next-hop name

ip route static bfd GigabitEthernet2/34 10.196.108.9

ip route static bfd GigabitEthernet3/9 10.196.108.13

ip route 10.196.108.24 255.255.255.255 10.196.108.9 name BGP_B_loc1

ip route 10.196.108.24 255.255.255.255 10.196.108.13 name BGP_B_loc2

ip route 10.196.108.9 255.255.255.255 GigabitEthernet2/34 10.196.108.9 name BGP_B_loc1

ip route 10.196.108.13 255.255.255.255 GigabitEthernet3/9 10.196.108.13 name BGP_B_Loc2

and I would do the same on the other location

see BFD configuration guide

http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_bfd/configuration/12-4t/Bidirectional_Forwarding_Detection.html#GUID-BFF5025F-AA11-4241-81BC-74890BC92C8A

Hope to help

Giuseppe

New Member

EBGP issue

Hi Giuseppe,

Both links are going to same router (A-B connectivity). And name is only used for identification of static routes, I think.

Regards,

Naveen

215
Views
0
Helpful
4
Replies
CreatePlease to create content