From: Alex Dean (Alex.Dean@xxxxxxxxxxxxx)
Date: Sun Aug 01 1999 - 05:41:32 GMT-3
Just had a quick look at your configs - it looks like you could try filtering o
ut the more specific routes that you don't want with your access list, and then
allowing the supernet.
An alternative you could try (no guarantees here, but I read this in an example
in the CCIE Network Design and Case Studies book under BGP and have yet to try
it)... Apparantly if you use the command:
access-list 101 permit ip 162.16.0.0 0.0.255.255 255.255.0.0 0.0.255.255
it will only allow the supernet route. I intend to try this and if it works tr
y and logic out how it works. It doesn't quite make sense to me, but if it wor
ks it would be a more elegant solution than the first one I suggetsed above.
Regards
Alex Dean
Auckland, New Zealand
(7 weeks to go)
>>> "Mohan Pokkali" <Mohan.Pokkali@USKO.com> 19/07/99 22:09:52 >>>
Hi All
Advanced IP Routing in Cisco Networks - Chapter 6 Example # 11 Complex
Redistribution Page 306
All the relevant configs and show commands are included.
On this particular example I was not able to get a clean summary address for
ospf networks (162.16.0.0) at NewYork and Moscow.
The only way I can think of getting a summary-address at NewYork and Moscow
for ospf network is by using interface configuration command :
" ip summary-address eigrp 200 162.16.0.0 255.255.0.0 " on serial interfaces
connecting to NewYork from Tokyo and London.
But then it is no more a EIGRP External ( D EX ) route . It becomes a EIGRP
route ( D ).
Any ideas ??
Thanks
Mohan
Another 50 days for the Lab.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:46 GMT-3