BGP metric for Backup MPLS circuit

[Brian Smith]

We have a 10 location fully-meshed MPLS network.  All CPE routers use the same AS number.  Two of the locations have backup MPLS circuit with the same ISP as the primary MPLS Circuit.  I've decided to use a basic route map to set the metric value of the backup circuit to a value of 10 . 

One of the locations this configuration worked fine, but the other location i'm having problems.

Here is the configuation of the problem location

route-map Backup permit 10
set metric 10

router bgp 1
no synchronization
bgp log-neighbor-changes
network 172.20.114.0 mask 255.255.255.0
network 192.168.114.0
neighbor 1.1.1.1 remote-as 55000
neighbor 2.2.2.2 remote-as 55000
neighbor 2.2.2.2 route-map Backup in
neighbor 2.2.2.2 route-map Backup out
no auto-summary

When I do a "sh bgp"  the backup circuit isn't added in my remote network (which are ibgp), but it's added in the ISP router..

*> 192.168.107.0    1.1.1.1                         0 55000 55000 i                Remote Location Router
*> 192.168.109.0    1.1.1.1                         0 55000 55000 i                Remote Location Router
*  140.25.2.92/30            ISP Network                                                              
                    2.2.2.2           10             0 55000 ?                             
*>                  1.1.1.1                         0 55000 ?
*  132.11.15.220/30        ISP Network
                    2.2.2.2           10             0 55000 ?
*>                  1.1.1.1                         0 55000 ?

From all the Routers, I can ping the backup circuit IP address that my ISP provided me (2.2.2.1 and 2.2.2.2).

When I bring down the primary circuit, I can't ping to any of my remote networks or ibgp networks.  Hopefully this makes a little since, I don't know much about BGP.

[Brian Smith]

I thought since all my routers are in the same AS number

that it's using iBGP.

below is the output of sh ip bgp sum

BGP router identifier 10.0.8.2, local AS number 1
BGP table version is 877, main routing table version 877
117 network entries using 15444 bytes of memory
144 path entries using 7488 bytes of memory
8/7 BGP path/bestpath attribute entries using 1184 bytes of memory
4 BGP AS-PATH entries using 96 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
Bitfield cache entries: current 1 (at peak 2) using 32 bytes of memory
BGP using 24244 total bytes of memory
BGP activity 1083/966 prefixes, 2138/1994 paths, scan interval 60 secs

Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
12.1.8.21  4 65000   34022   37238      877    0    0 4d23h         112
19.211.41.5   4 65000    6606    7251      877    0    0 4d23h          27

[Brian Smith]

added the following to the bgp config

timers bgp 10 30

The converence time is pretty good when I tested it.

CPU utilization is around 37%

[Chetan Kumar Ress]

Hi Brian

As in previous post i told you to have a word with you SP & Now your convergence issue resolved as told to manipulate  keepalive & holdtimer.

In your below output you can see that you are receving 112 prefix from 12.1.8.21 (State/PfxRcd) & 27 prefix from 19.211.41.5.

Sh ip sh ip bgp table you can see the prefix that you are receving from both MPLS Circuit. As per your network if you think that you should receive all route from bith MPLS circuit then you should have a word with you SP that why you r not getting all prefix from both circuit.

Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down  State/PfxRcd
12.1.8.21  4 65000   34022   37238      877    0    0 4d23h         112
19.211.41.5   4 65000    6606    7251      877    0    0 4d23h         27

Regards

Chetan Kumar