[c-nsp] static route to null0 not visible (BGP)

[Alex Foster]

I have a couple of 3550s with already existing bgp sessions with some
upstream providers and with iBGP running between them.  Im advertising a
/24 at present and now want to advertise a /23 netblock in addition.  I
use static routes to null0 with metric of 254 for the existing /24 (on
both routers) but when I add new routes to null0 for the /23, only one
of my routers installs the route - the other learns the /23 via iBGP.
If I remove the 254 metric on the offending router (and use the default
metric), the route is installed and advertised.  When the /23 is learned
by iBGP it has a metric of 200 so does this mean it is preferred over
the static route ?? - If so why doesn't the /24 installed with a 254
metric on both routers also behave this way.  

Herewith abbreviated config for 'offending' router (router-a).

interface Loopback0
 ip address 83.245.6.241 255.255.255.255
!
!interface FastEthernet0/24
 description to router-b 
 no switchport
 ip address 83.245.6.253 255.255.255.252
 duplex full
 speed 100
!
router ospf 1
 log-adjacency-changes
 network 83.245.6.0 0.0.0.255 area 0.0.0.0
 network 88.215.60.0 0.0.1.255 area 0.0.0.0
!
router bgp 
 no synchronization
 bgp log-neighbor-changes
 network 83.245.6.0 mask 255.255.255.0
 network 88.215.60.0 mask 255.255.254.0
 timers bgp 5 15
 neighbor transit-provider peer-group
 neighbor transit-provider version 4
 neighbor transit-provider remove-private-AS
 neighbor transit-provider soft-reconfiguration inbound
 neighbor transit-provider prefix-list ISP-Ingress-In-Loose in
 neighbor transit-provider prefix-list announce-routes out
 neighbor transit-provider maximum-prefix 15000
 neighbor 83.245.6.242 remote-as 31655
 neighbor 83.245.6.242 description Router-B
 neighbor 83.245.6.242 update-source Loopback0
 neighbor 83.245.6.242 next-hop-self
 neighbor 217.163.4.33 remote-as 3356
 neighbor 217.163.4.33 peer-group transit-provider
 neighbor 217.163.4.33 password 
 neighbor 217.163.4.33 route-map Level3 in
 neighbor 217.163.4.33 maximum-prefix 18000
 no auto-summary
!
ip classless
ip route 83.245.6.0 255.255.255.0 Null0 254 ------- configured as ip
route 83.245.6.0 255.255.255.0 Null0 254 (on router-b)
ip route 88.215.60.0 255.255.254.0 Null0 ------- configured as ip route
88.215.60.0 255.255.254.0 Null0 254 (on router-b)
no ip http server
ip bgp-community new-format
ip as-path access-list 10 permit ^3356$
!
!
ip prefix-list ISP-Ingress-In-Loose seq 5 xxxxxxxxxxx
ip prefix-list ISP-Ingress-In-Loose seq 120 deny 83.245.6.0/24 le 32
ip prefix-list ISP-Ingress-In-Loose seq 130 deny 88.215.60.0/23 le 32
ip prefix-list ISP-Ingress-In-Loose seq 10200 xxxxxxxxxx
!
ip prefix-list announce-routes seq 10 permit 83.245.6.0/24
ip prefix-list announce-routes seq 15 permit 88.215.60.0/23
!
ip prefix-list default-route seq 10 permit 0.0.0.0/0
!
route-map Level3 permit 10
 match ip address prefix-list default-route
 set local-preference 110
!
route-map Level3 permit 20
 match as-path 10




The information in this e-mail and any attachments is confidential and may be subject to legal professional privilege. It is intended solely for the attention and use of the named addressee(s). If you are not the intended recipient, or person responsible for delivering this information to the intended recipient, please notify the sender immediately. Unless you are the intended recipient or his/her representative you are prohibited from, and therefore must not, read, copy, distribute, use or retain this message or any part of it. The views expressed in this e-mail may not represent those of Gamma Telecom.

This message has been scanned for viruses by MailController