from r2:
[EMAIL PROTECTED]> show configuration protocols isis
lsp-lifetime 65535;
level 2 {
wide-metrics-only;
}
interface ge-0/0/0.0 {
point-to-point;
level 1 disable;
level 2 {
hello-interval 10;
}
}
--
[EMAIL PROTECTED]> show isis adj
On Fri, Mar 28, 2008 at 4:25 PM, snort bsd <[EMAIL PROTECTED]> wrote:
> On r1, r2 is in list of "show isis adjacency". with the help of
> traceoptions under "protocols isis" (r1), I can see LSPs (other routers)
> coming via the interface (connecting to r2). Obviously r2 is advertising
> LSPs via
On r1, r2 is in list of "show isis adjacency". with the help of traceoptions
under "protocols isis" (r1), I can see LSPs (other routers) coming via the
interface (connecting to r2). Obviously r2 is advertising LSPs via this link.
Yes, traffic flows between the two interfaces (connecting r1 and r
On Fri, Mar 28, 2008 at 3:08 PM, snort bsd <[EMAIL PROTECTED]> wrote:
>
> but in some cases, they are not. I have one router (say r1), it has
> adjacency with r2 (on the output of "show isis adjacency) but the r2 entry
> doesn't show up in the output of "show isis database details".
H is
Hello, all:
Shouldn't the entries in the output of "show isis adjacency" be one-to-one
relationship with the neighbor entries in "show isis database details"?
Assume r1 peers with r2, r3 and r4 in level 2 (single connection to each
neighbor)
[EMAIL PROTECTED]> show isis database level 2 r1.00-
Hi -
The inactive timer is (I presume) the OSPF dead-timer expiring. If so (and if
set to defaults) it means that e.f.g.h didn't receive an OSPF hello for 40
seconds from a.b.c.d.
a.b.c.d discovering that e.f.g.h is in one-way state probably happened
immediately after e.f.g.h decided a.b.c.d
The motivation is that currently there are a number of devices peering with
a singular router... folks are interested in introducing another router for
redundancy and configuring them in a VRRP group. They aren't interested in
configuring secondary BGP sessions on a number of devices hence it was
Hello,
I'm no BGP guru but I can put in my guess on the "motivation" part:
Cost :) Atleast that was something we considered when planning our
multi-homing solution @work and not being completely fluent in BGP
yet :)
Consider the following setup:
2 routers, 2 peerings: 1 peering to router 1
Keegan Holley
Network Managed Services Engineer I
SunGard Availability Services
Mezzanine Level MC-95
401 N. Broad St.
Philadelphia, PA 19108
215.446.1242 (office)
609.670.2149 (cell)
[EMAIL PROTECTED]
___
Keeping People and Information Connected®
http://www.
Well, I agree its not best practice, and while it made it through
tech-edits, and seemed to work fine, the example I provided in the E-BGP
chapter of the JNCIP prep book, did result in a bit of controversy.
While I recall no killer reason why this should not be
allowed/supported, the general concen
On Fri, 28 Mar 2008, Stefan Fouant wrote:
> There is some internal debate here in my office today as to whether or not
> Juniper can support a BGP implementation in conjunction with VRRP, as in,
> BGP is sourced from a VRRP VIP address.
>
> Now before everyone attempts to tear me a new one... I sh
Hi folks,
There is some internal debate here in my office today as to whether or not
Juniper can support a BGP implementation in conjunction with VRRP, as in,
BGP is sourced from a VRRP VIP address.
Now before everyone attempts to tear me a new one... I should state that
I'm pretty sure this sho
Sure, there could be many reasons such as mismatched Hello or Dead timers,
duplicate Router IDs, OSPF HELLOs not being processed due to lack of CPU
resources, underlying L2 problems preventing the Hellos from being received,
MTU mismatch, receipt of an unexpected Database Descriptor sequence
number
Thanks for all comments.
But these logs are valuable if it happens again. I am running this n/w
more than 2 yrs now. And this is first time OSPF neighbor failed
without any apparent reason.
My question is, Is there any other reasons other than media to flapped
neighbor relationship?
Thanks again
Hello Eric
The behavior you're describing is strange but it makes me thinking that
this kind of card on the M7i has 4 ports with over subscription (the
total bandwidth for the card is 1gig) so divided by 4, it gives each
port about 250M bps !
I don't know if this is the reason of your proble
You might try nanog for questions on the routing policies of the tier
I'ers. I've gotten pretty good information there from similar questions.
You may also be able to get someone from a particular ISP to contact you
off list. I have never done this personally though so YMMV.
http://www.nanog.
Yes Juniper, Narus, and Arbor platforms support flowspec... I am sure there
are others as well..
Stefan
On 3/28/08, Michael Loftis <[EMAIL PROTECTED]> wrote:
>
>
>
> --On March 27, 2008 10:17:08 PM -0400 Stefan Fouant <[EMAIL PROTECTED]>
> wrote:
>
> > Hey folks,
> >
> > This isn't specifically a
Hi Stefan,
Thanks for that, that is exactly what I was looking for, will give it a try.
Stefan Fouant wrote:
> You could always specify the sourcing interface as opposed to the
> source-address, if for example you want to use a standardized
> configuration across many devices, as in:
>
> term pe
--On March 27, 2008 10:17:08 PM -0400 Stefan Fouant <[EMAIL PROTECTED]>
wrote:
> Hey folks,
>
> This isn't specifically a Juniper question, so I do apologize for the
> improper venue... however there are some pretty knowledgeable people on
> this list so here goes...
>
> I know that Verio, AT&
Can you try login with 'root' username and EMPTY password?
On 3/28/08, Stefan Fouant <[EMAIL PROTECTED]> wrote:
>
> Hey folks,
>
> This isn't specifically a Juniper question, so I do apologize for the
> improper venue... however there are some pretty knowledgeable people on
> this list so here go
20 matches
Mail list logo
