On 11/Mar/15 21:18, Jared Mauch wrote:
Similarly send-community on IOS requires beyond the basic “neighbor 1.2.3.4
remote-as 5” type config.
One has the same issue in IOS XR, where BGP communities are only
signaled by default for iBGP neighbors. One needs to enable signaling of
communitie
On 11/Mar/15 22:27, Reza Motamedi wrote:
Thanks again, Mark.
So I guess the short answer is that I can't infer anything about the
location of physical connectivity having this level of information
from the control plane.
Not reliably as far as I can tell, no. Someone else can chime in here
Thanks again, Mark.
So I guess the short answer is that I can't infer anything about the
location of physical connectivity having this level of information from the
control plane. Is that a fair statement? What if the "Next Hop" is inside
the neighbor AS. I know it is a rather odd and uncommon cas
On 11/Mar/15 21:42, Reza Motamedi wrote:
What I ultimately want to determine, is the location of the AS
connection. I know for example the router is in, say LA. If hot potato
lets me to send the packet to the neighbor AS then they have an AS
connection in LA, right?
Going back to my example
What I ultimately want to determine, is the location of the AS connection.
I know for example the router is in, say LA. If hot potato lets me to send
the packet to the neighbor AS then they have an AS connection in LA, right?
Going back to my example does the fact that the entry does not have 'i'
On 11/Mar/15 21:22, Reza Motamedi wrote:
Thanks Mark for the reply. Let me try to check what I understood is
correct. Does the 'i' on the left (status code) only shows whether the
prefix belongs to this AS?
Status-code "i" just means the entry was learned by "this" router via
iBGP. It d
Thanks Mark for the reply. Let me try to check what I understood is
correct. Does the 'i' on the left (status code) only shows whether the
prefix belongs to this AS?
What I want to figure out is if this two ASes (the owner of the router and
and the first one on the AS-PATH) connect at the location
> On Mar 11, 2015, at 2:59 PM, Mark Tinka wrote:
>
>
>
> On 11/Mar/15 20:51, Jared Mauch wrote:
>>
>> NTT (2914) tags routes based on if they are a customer, peer
>> and with geographic communities based on where the route enters our
>> network. Many networks perform similar techniques
On 11/Mar/15 20:51, Jared Mauch wrote:
NTT (2914) tags routes based on if they are a customer, peer
and with geographic communities based on where the route enters our
network. Many networks perform similar techniques and you can find
details at various websites or this one:
http://w
On Wed, Mar 11, 2015 at 02:32:33PM -0400, Reza Motamedi wrote:
> Hi Nanog,
>
> For a research I want to distinguish the external AS peering from "show ip
> BGP". In other words I want to see which entry show a path that immediately
> sends packets to another AS. My understanding is that *status co
On 11/Mar/15 20:32, Reza Motamedi wrote:
Hi Nanog,
For a research I want to distinguish the external AS peering from "show ip
BGP". In other words I want to see which entry show a path that immediately
sends packets to another AS. My understanding is that *status code* shows
if the route is in
Hi Nanog,
For a research I want to distinguish the external AS peering from "show ip
BGP". In other words I want to see which entry show a path that immediately
sends packets to another AS. My understanding is that *status code* shows
if the route is internal, right? Does this mean if the *'i' *is
12 matches
Mail list logo
