[c-nsp] unsuppress-map : is this correct?

Collins, Richard (SNL US) richard.1.collins.ext at nsn.com
Sun Nov 11 12:50:47 EST 2007


It did seem to work for me in the lab.  I believe you have to use
standard
ip access lists and not prefix lists in the route-map.

 
Here is the peer router R4 without the unsuppress-map being used (shows
only aggregate).

Rack1R4#sh ip bgp 
BGP table version is 7, local router ID is 4.4.4.4
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 197.22.5.0       6.6.6.6                                0 6 5 i
*> 197.68.0.0/16    6.6.6.6                  0             0 6 5 i
*> 197.68.21.0      6.6.6.6                                0 6 5 i
Rack1R4#

After I put the unsuppress in the peer, I get back two of the three
specific networks I wanted.

Rack1R4#sh ip bgp 
BGP table version is 15, local router ID is 4.4.4.4
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 197.22.5.0       6.6.6.6                                0 6 5 i
*> 197.68.0.0/16    6.6.6.6                  0             0 6 5 i
*> 197.68.3.0       6.6.6.6                                0 6 5 i
*> 197.68.5.0       6.6.6.6    


Here is the upstream Router R6

Rack1R6#sh ip bgp 
BGP table version is 15, local router ID is 155.1.0.6
Status codes: s suppressed, d damped, h history, * valid, > best, i -
internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*> 197.22.5.0       10.10.56.5               0             0 5 i
*> 197.68.0.0/16    0.0.0.0                       100  32768 5 i
s> 197.68.3.0       10.10.56.5               0             0 5 i
s> 197.68.5.0       10.10.56.5               0             0 5 i
s> 197.68.21.0      10.10.56.5               0             0 5 I

router bgp 6
 no synchronization
 bgp log-neighbor-changes
 aggregate-address 197.68.0.0 255.255.0.0 as-set summary-only
..
 neighbor 4.4.4.4 unsuppress-map map1
 neighbor 10.10.56.5 remote-as 5
 no auto-summary
!

access-list 3 permit 197.68.3.0
access-list 5 permit 197.68.5.0 

!
route-map map1 permit 10
 match ip address 3 5


-Rich




On Sat, Nov 10, 2007 at 06:44:02PM +0200, Tassos Chatzithomaoglou wrote:
> According to:
>
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124cr/hi
rp_r/rte_bgh2.htm#wp1115114
> 
> "To selectively advertise routes previously suppressed by the
aggregate-address command, use the 
> neighbor unsuppress-map command in address family or router
configuration mode".
> 
> Which, if i understand correctly, means that whatever route-map you
use in unsuppress-map, it only 
> influences the prefixes that were suppressed by using the
"aggregate-address" command.
> 
> I have a case where i use this command and although the specific
network i define in the route-map 
> is correctly unsuppressed, all the other networks (which were not
being summarized, but were being 
> advertised) are now suppressed. Am i doing something wrong?
> 
> -- 
> Tassos


------------------------------

_______________________________________________
cisco-nsp mailing list
cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp

End of cisco-nsp Digest, Vol 60, Issue 36
*****************************************


More information about the cisco-nsp mailing list