From: Brown, Patrick (NSOC-OCF} (PBrown4@chartercom.com)
Date: Sat Aug 16 2003 - 23:57:58 GMT-3
How are you sending the community to r4. You do not have the "neighbor
x.x.x.x send-community" command. On r4 you should be able to do the "sh ip
bgp community no-export" and see the route affected by this community. If r4
and r5 is the only routers in AS 402, you can use the "no-advertise'
community also.
ex: neighbor 130.4.45.4 send-community
HTH,
Patrick B
-----Original Message-----
From: Richard L. Pickard
To: Ccielab@Groupstudy. Com
Sent: 8/16/2003 10:16 PM
Subject: set community no-export any ideas ???
FiestaHere is my topology -
|------------BGP AS 402 ------|
R_4 s0/1 --- 130.4.45.x ---- s0/1 R_5
The lab I am working states the following -
Configure an additional Loopback with the address of 200.10.5.5/24 on
R5.
Configure R5 so that it advertises this newly created 200.10.5.5/24
Loopback
in BGP to AS 402 but it will not propagate past AS 402 (i.e. AS 401 will
not
see the 200.10.5.5/24 route)
This is what I did on R_5:
interface Loopback200
description last step in BGP lab
ip address 200.10.5.5 255.255.255.0
router bgp 65222
no synchronization
bgp router-id 130.4.5.5
bgp log-neighbor-changes
network 190.4.5.0 mask 255.255.255.0
network 200.10.5.0
neighbor 130.4.45.4 remote-as 402
neighbor 130.4.45.4 description R_4
neighbor 130.4.45.4 route-map LAB_II out
no auto-summary
!
ip classless
ip http server
ip ospf name-lookup
!
!
ip prefix-list RLP description LAB_II
ip prefix-list RLP seq 5 permit 200.10.5.0/24
route-map LAB_II permit 10
match ip address prefix-list RLP
set community no-export
I am doing something wrong, as all the routers in the lab (NOT JUST AS
402)
are picking up 200.10.5.5
[GroupStudy removed an attachment of type image/jpeg which had a name of
Fiesta Bkgrd.jpg]
This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:54:00 GMT-3