[c-nsp] RR Client in different AS?

[Mack McBride]

If the next-hop is not accessible from the 'new' network, the routes will not be learned.

Mack McBride | Network Architect | ViaWest, Inc.
O: 720.891.2502 | mack.mcbride at viawest.com | www.viawest.com | LinkedIn | Twitter | YouTube


-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of CiscoNSP List
Sent: Tuesday, March 31, 2015 5:19 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] RR Client in different AS?

Hi Everyone,

Quick question (I hope!) - A customer has an RR that successfully peers/distributes routes to RR-clients in the same AS...they have added another "network", running a different AS, and have successfully peered to the RR(So added the new networks router as an RR-client, but with a different AS)....the RR is advertising all learned routes from the "original" network to the "new" network(sh ip bgp nei x.x.x.x advertised-routes), but the "new" network(With the different AS) is only accepting the default route? (There are no inbound policies on the new networks RR-client router).

Is this expected behaviour? (I've googled, but havent found anything definitive)

Cheers.







_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
This message contains information that may be confidential, privileged or otherwise protected by law from disclosure. It is intended for the exclusive use of the addressee(s). Unless you are the addressee or authorized agent of the addressee, you may not review, copy, distribute or disclose to anyone the message or any information contained within. If you have received this message in error, please contact the sender by electronic reply and immediately delete all copies of the message.