At 04:00 PM 3/28/01 -0800, Josh Richards wrote:
>> router bgp 65000
>> no synchronization
>> network 10.2.27.0 mask 255.255.255.224
>> aggregate-address 10.2.27.0 255.255.255.224 summary-only
>> neighbor 10.1.130.85 remote-as 65001
>> neighbor 10.1.130.85 next-hop-self
>> neighbor 10.1.130.85 route-map US-OUT out
> ^^^^^^^^^^^^^^^^^^^^
> Try changing this to:
> prefix-list upstream_ip_out out
> (you can then remove or just ignore the US-OUT
> route-map)
Unfortunately, I fat-fingered myself out of access and will have to drive
out to the location for a power cycle before I can try that. Doh.
> What does a "show ip bgp neigh 10.1.130.85 adv" look like? It'll give an
> idea of whether the problem is in something with the filters/route-maps
> or whether the route isn't even making it to the BGP process (which if it
> isn't, I have no idea).
It's not appearing there at all, which is why I posted the non-"adv" version,
Outbound path policy configured
Outgoing update AS path filter list is 166
Route map for outgoing advertisements is US-OUT
to show that the process at least *thinks* it should have the route.
This is so bizarre. But thanks for at least the sanity check. :-)
...
Other responses:
> Is int e1 up? Just checking...
> Do you have a route for the /27 in your local table?
Yes, as posted, interface up and nailed up route even if it weren't:
#sh ip rou
C 10.2.27.0/27 is directly connected, Ethernet1
ip route 10.2.27.0 255.255.255.224 Null0 200
> that's very strange. I wonder if "ip classless" would help.
Already there.
-wfs
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:34 EDT