From: Peter van Oene (pvo@usermail.com)
Date: Wed Feb 26 2003 - 20:33:03 GMT-3
At 06:11 PM 2/26/2003 -0500, trust.hogo@sarcom.com wrote:
>"show ip bgp community" command does not tell you what the communities are.
>You need to know the community name to use that command otherwise it just
>gives you all routes with community attributes even though the communities
>are different. The only way I have seen the communities is doing a "debug
>ip bgp x.x.x.x updates" on the incoming updates not the outgoing updates.
Show ip bgp will show you the communities in the bgp-rib. The poster was
looking for post rib-out policy communites (ie communities applied to
routes on their way out)
Pete
>May be someone might know how to do it.
>
>-----Original Message-----
>From: Peter van Oene [mailto:pvo@usermail.com]
>Sent: Wednesday, February 26, 2003 3:54 PM
>To: ccielab@groupstudy.com
>Subject: Re: How do you show advertised BGP community information?
>
>
>At 12:14 PM 2/26/2003 -0600, Hughes, Gordon wrote:
> >Is there any way to see what community information you are sending from
> >your local bgp router to an EBGP peer without actually using the "show
> >ip bgp community" command on that remote peer?
>
>As far as I know, Cisco only shows the pre processed rib-out with the below
>command. In other words, you can see which prefixes are going out, but not
>how they look.
>
>
>
> >The "show ip bgp neighbor x.x.x.x advertised-routes" doesn't do the
> >trick. I have even tried debugging with the command "debug ip bgp
> >x.x.x.x updates". The debug data shows everything but the community
> >information.
> >
> >
> >
> >Gordon
> >
> >
> >
> >This communication is confidential and may be legally privileged. If
> >you are not the intended recipient, (i) please do not read or disclose
> >to others, (ii) please notify the sender by reply mail, and (iii)
> >please delete this communication from your system. Failure to follow
> >this process may be unlawful. Thank you for your cooperation.
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:37 GMT-3