This is working as per design. You can try adding keep-all under the ibgp peer group. You may need to soft clear the sessions to perform route refresh, but I believe after that you will see all route in the bgp.l3vpn.
Regards > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Tuesday, June 24, 2008 8:52 AM > To: [email protected] > Subject: [j-nsp] MBGP automatic filtering? > > A (hopefully) simple question for someone on here. > > When connecting a PE router to a route reflector, there seems > to be some form of automatic filtering going on with the > bgp.l3vpn.0 table. > > On the RR I see the following for a 'show bgp neighbor <pe-address>': > ... > Table bgp.l3vpn.0 Bit: 20017 > RIB State: BGP restart is complete > RIB State: VPN restart is complete > Send state: in sync > Active prefixes: 9 > Received prefixes: 9 > Suppressed due to damping: 0 > Advertised prefixes: 1156 > ... > > While on the PE, for a 'show bgp neighbor <rr-address>' I get: > ... > Table bgp.l3vpn.0 > RIB State: BGP restart is complete > RIB State: VPN restart is complete > Send state: not advertising > Active prefixes: 9 > Received prefixes: 9 > Suppressed due to damping: 0 > ... > > The PE seems to be doing some form of automatic filtering on > the received prefixes from the RR, to only include those that > are required for routing-instances it has configured. > > Is there any command that can override this, and show the > full list of prefixes received from the RR? > > Thanks > > Michael > > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
