Summaraisation and Advanced Summaraisation - lab 3
Monday, January 5, 2009
done with lab 3 summaraisation and advanced summaraisation
as always everything is cool and new point / concept "leak map"
Configuring leak-map option allows us to advertise a component route (one or more specific networks of a summary route) that would otherwise be
suppressed by the manual summaraisation .
Three rules :
If the leak-map is configured to reference a route-map that does not exist, only the summary route is advertised and the more specific routes are
suppressed
If the leak-map is configured to reference a route-map and the route-map is referencing an access-list that does not exist , then the summary routes and all
the specific routes are advertised
If the leakmap is configured to reference a route-map and the route-map matches and acl , all the permitted networks b the acl will be advertised along with
the summary route
for example we have
2.2.4.2
2.2.5.2
2.2.6.2
2.2.7.2
number 128 64 32 16 8 4 2 1
4 0 0 0 0 0 1 0 0
5 0 0 0 0 0 1 0 1
6 0 0 0 0 0 1 1 0
7 0 0 0 0 0 1 1 1
2.2.4.0/(8+8+6)
2.2.4.0/22
2.2.4.0 255.255.252.0
we have a summary address 2.2.4.0/22
1. int fa0/0
ip summa eigrp 100 2.2.4.0 255.255.252.0 leak-map rakesh---------------------> (rakesh is the name of the route-map which is not configured)
in this case only summary route is advertised which will be equal to the commands output "ip summa eigrp 100 2.2.4.0 255.255.252.0"
2.
route-map rakesh permit 10
match ip address 77(----------------> acl is not configured)
int fa0/0
ip summa eigrp 100 2.2.4.0 255.255.252.0 leak-map rakesh---------------------> (rakesh is the name of the route-map which has no access-list)
in this case all of the specific and summary routes are advertised i,e
2.2.4.0
2.2.4.0
2.2.5.0
2.2.6.0
2.2.7.0
3.
both acl and route-map are configured
access 66 permit 2.2.6.0 0.0.0.255
route-map rakesh permit 10
match ip address 66
int fa0/0
ip summ eigrp 100 2.2.4.0 255.255.252.0 leak rakesh
this would advertise summary address and address we wanted to permit/ deny in the acl .. look there is an implicit deny which is followed
this is what that i found interesting ...
i need more clear understanding !!! in what sense ? well iam not happy with the output .. first of all what is the use of leak-map .. next ok that is general sense of the question ... but it is behaving differently for different set of rules .. how does it allow / deny packets or how does it work ... so on ...? iam gonna post this question and will let you know
guday