From: Tony Schaffran (groupstudy@cconlinelabs.com)
Date: Wed Mar 22 2006 - 18:00:20 GMT-3
Victor,
There are probably about 15 ways to solve any one problem. The solutions in
the workbooks are not necessarily the best solution, but they are the
solutions they are trying to teach you. Understand what you are doing and
why, not just what you think is the better solution. Doing this will
increase your rate of success.
Tony Schaffran
Network Analyst
CCIE #11071
CCNP, CCNA, CCDA,
NNCDS, NNCSS, CNE, MCSE
www.cconlinelabs.com
Your #1 choice for online Cisco rack rentals.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Victor Cappuccio
Sent: Wednesday, March 22, 2006 11:54 AM
To: CCIE LAB
Subject: InternetworkExperts Lab 3 Vol III Task 5.4 and Task 5.5
Hola ...
I have a doubt, about the IEWB solution in Lab 3 Vol III Task 5.4 and
Task 5.5
In Task 5.4 R1 also advertise R2 Vlan 2 Route route to R5, so IMHO a
Distribute list should be applied to the outbound of R1 to R5 ??
Or it does not matter?
R1#
router bgp 100
***
neighbor 136.1.15.5 distribute-list 2 out
***
access-list 2 deny 136.1.2.0 0.0.0.255
access-list 2 permit any
Rack1R5#show ip bgp 136.1.2.0
BGP routing table entry for 136.1.2.0/24, version 5
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Advertised to non peer-group peers:
4.4.4.4 136.1.15.1 136.1.57.7
300 300 300
136.1.245.2 from 136.1.245.2 (2.2.2.2)
Origin IGP, metric 0, localpref 100, weight 100, valid, external, best
And for Task 5.5 In my crazy world I did the following
R2#
router bgp 300
***
neighbor 136.1.245.5 route-map PREPREND:AS:PATH out
****
Rack1R2#show route-map PREPREND:AS:PATH
route-map PREPREND:AS:PATH, permit, sequence 10
Match clauses:
Set clauses:
as-path prepend 300 300
Policy routing matches: 0 packets, 0 bytes
But the solution show the use of conditional Advertisement but to be
honest, right now I can not see why the network 136.1.23.0/24 is
advertised in BGP
Thanks for your invaluable input
Victor.
This archive was generated by hypermail 2.1.4 : Sat Apr 01 2006 - 10:07:39 GMT-3