They do not have a route at all through the other provider., that I would like preferred.
I'm going to contact my carrier again to ask specifically what community might work, as they know what is accepted upstream - I have no way of knowing what ASN's are in between, however they should know though. Thank you all -----Original Message----- From: Wycliffe Bahati [mailto:[email protected]] Sent: 03 November 2015 14:39 To: Mark Tinka Cc: Nick Cutting; [email protected] Subject: Re: [c-nsp] BGP peering visibility Local preference should only affect there internal routing but not what you see in the looking glass ./swami Sent from my iPhone > On 3 Nov 2015, at 17:31, Mark Tinka <[email protected]> wrote: > > > >> On 3/Nov/15 16:15, Nick Cutting wrote: >> >> >> >> However the Other carrier's looking glass - which is what the other 40 >> percent of clients use, is using the inbound route with multiple prepends >> and the last resort community. > > Assuming you are announcing consistently, the other provider could be > overriding your desires with LOCAL_PREF on their side. > > Best to confirm with them, as you are doing. > >> >> >> I imagine many people on this list have decent visibility as you probably >> have multiple peerings. >> What tools are out there that may help me with my limited visibility? >> I want to see the how the carriers that my clients are using are connected >> to my own upstream ISP's - I'm not sure how to go about this. > > A simple way to view this is with an example below: > > http://bgp.he.net/AS174 > > Replace with ASN of interest. > > Mark. > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
