Depending on the implementation, these AS could be ignored confederation loop checking is done on sub-as number only.
If you still having an issue, you can override as loop detection with the as-loops command. Doug Marschke Principal Technologist Strategic Networks Training JNCIE-ER #3, JNCIE-M/T #41, JNCIS-FW, JNCI www.ietraining.net (415)902-5702 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Amos Rosenboim Sent: Thursday, May 29, 2008 9:56 AM To: juniper-nsp Subject: [j-nsp] BGP question Hello List, This is not Juniper specific, but I think it's an interesting case anyway. A global carrier is running an MPLS network to provide L3 and L2 vpns. Obviously this carrier doesn't have presence in every city and every country so he forms partnerships with local carriers to extend the his footprint. This is done by establishing type B inter as NNI links. The iBGP topology of this carrier is using confederations. The problem now is that one of the new partners is using a private AS, which happens to match one of the BGP confederations used inside the global carrier network. This obviously creates a problem which I'm looking to overcome. Any ideas will be appreciated. Regards Amos _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp