From: Sam Munzani (sam@xxxxxxxxxxx)
Date: Tue Nov 07 2000 - 17:28:50 GMT-3
I tried in my lab with simple IP routing and BGP only. I didn't know
about that BGP behavior until a CCIE co-worker told me about it. No
body is perfect and nobody in group would mis guide anybody. When you
get a chance just give it a try.
Sam
----- Original Message -----
From: McNutt, Steve
To: 'Sam Munzani' ; 'ccielab@groupstudy.com'
Sent: Tuesday, November 07, 2000 2:26 PM
Subject: RE: BGP Route-maps
I haven't nuked lab 12 from my routers yet. When I get home tonight I
take at look at it and figure out what's different. I hate coming to
incorrect conclusions about things, and I dislike unintentionally
misinforming others even more. I seem to be missing the boat a lot
lately dangit.
I think the problem is that I am performing experiments on top of
complex configurations instead of doing small isolated tests. My
date is close so I've been trying to focus on doing the everything
but the kitchen sink approach to get the most bang out of my rack
time. Maybe what I need is two racks, one for doing the complicated
scenarios, and a smaller rack for quickly testing ideas and concepts
on the side. hmm..
-----Original Message-----
From: Sam Munzani [mailto:sam@munzani.com]
Sent: Tuesday, November 07, 2000 2:54 PM
To: McNutt, Steve; 'Eric Jastak'
Cc: ccielab@groupstudy.com
Subject: Re: BGP Route-maps
Not really. Here is my configs and bgp table.
First is with route-map with filters. Then I removed route-map with
filter and you will see 192.168.1.0/24 in bgp table.
Config with route-map inbound filters:
router bgp 1
no synchronization
bgp log-neighbor-changes
neighbor 132.5.5.5 remote-as 1
neighbor 132.5.5.5 update-source Loopback9
neighbor 132.5.5.5 route-map inbound in
neighbor 132.5.6.6 remote-as 1
neighbor 132.5.6.6 update-source Loopback9
neighbor 132.5.6.6 route-map inbound in
neighbor 132.5.129.2 remote-as 4
!
!
access-list 99 deny 192.168.1.0 0.0.0.255
access-list 99 permit any
route-map inbound permit 10
match ip address 99
Config without Route-map inbound filters:
router bgp 1
no synchronization
bgp log-neighbor-changes
neighbor 132.5.5.5 remote-as 1
neighbor 132.5.5.5 update-source Loopback9
neighbor 132.5.6.6 remote-as 1
neighbor 132.5.6.6 update-source Loopback9
neighbor 132.5.129.2 remote-as 4
Just do like this and you will see the results
Sam
----- Original Message -----
From: McNutt, Steve
To: 'Eric Jastak' ; 'Sam Munzani'
Cc: 'ccielab@groupstudy.com'
Sent: Tuesday, November 07, 2000 1:43 PM
Subject: RE: BGP Route-maps
I can confirm that the rule does apply to IBGP. I ran into this last
night on CCBootcamp lab 12. The rule makes sense given the goal of
IBGP is to maintain AS consistancy.
Lab 12 is cool because it gave me an idea of how confusing things can
get when working with confederations. The scoping of some rules are
changed, but some are not, and the confederation makes it harder to
tell if you are not meeting an AS wide "IBGP" type rule.
-----Original Message-----
From: Eric Jastak [mailto:ejastak@gobosh.cc]
Sent: Tuesday, November 07, 2000 2:14 PM
To: 'Sam Munzani'
Cc: 'ccielab@groupstudy.com'
Subject: RE: BGP Route-maps
I think that rule only applies to iBGP. Was the route-map applied to
an iBGP or eBGP neighbor?
- Eric
-----Original Message-----
From: Sam Munzani [mailto:sam@munzani.com]
Sent: Tuesday, November 07, 2000 10:07 AM
To: ccielab@groupstudy.com
Subject: BGP Route-maps
Hi Group,
As everybody might have read it in Halabi and bunch of other sources.
"Inbound Route-map does not work when used with matching IP address".
Today I experimented and it works inbound also. Violating the BGP (or
Halabi) rule for route-maps.
Sam
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:43 GMT-3