[AA] if You actually still dealing with such issues in Your customer
networks, my condolences. Especially sad is the issue with management PC
- do Your customers use commodity Windows PC with freeware Solarwinds
version as NMS?
Yes, my customers (and companies at all) are not always ideal
On (2013-04-25 16:51 -0400), Phil Shafer wrote:
transfers. So the second network is rs232 _and_ fxp.
Brandon Ross wrote:
Both.
Either defend that statement or admit that it was overly broad.
Everyone seems to agree RS232 is granted. But some people feel you also
need to build FXP.
The
This should be simple but I can't get the behavior I want.
Blackhole scenario. Customer set community, I want to see that community
and set next-hop to an address I have with a discard. I've tried both a
discard interface and a basic static route. Those seem ok either way.
set routing-options
Works fine for me in the lab on MX80+JUNOS 12.3 ( I use BGP-LU though, too
busy to change to regular inet unicast:-)
[edit logical-systems MX2-RR]
aarseniev@mx80# run show route logical-system MX2-RR protocol bgp extensive
inet.0: 29 destinations, 30 routes (27 active, 0 holddown, 2 hidden)
Hello,
Use a ttl on the bgp session with the customer -
Rgds,
C.
Le 26/04/2013 16:26, Alex Arseniev a écrit :
Works fine for me in the lab on MX80+JUNOS 12.3 ( I use BGP-LU though,
too busy to change to regular inet unicast:-)
[edit logical-systems MX2-RR]
aarseniev@mx80# run show route
Hi Eric,
Works fine here, as you configured it.
Can you reply your inbound route-policy and the show route x.x.x.x/32
extensive?
Thanks.
Tim
On 26-04-13 15:36, Eric Krichbaum wrote:
This should be simple but I can't get the behavior I want.
Blackhole scenario. Customer set community, I
4550 packet buffers are not that big.
We are getting tail drops on ports that show 5-6 Gbps utilization (output of
monitor interface show command).
It's related to (micro)bursts, and there is not much to do about it. Deeper
buffers would certainly help.
If I remember correctly QFX uses a cut
Eric. eBGP single hop will not let you change the NH by default. You can
use the following knob to override this behavior:
protocols {
bgp {
log-updown;
group TRIGGER {
accept-remote-nexthop;
This can be applied @ proto group or neighbor. See
Thanks everyone. The policy straight to discard works for me, just annoyed
me. I really didn't want to apply a knob (similar to the disable connected
check on cisco) to do it. Trying to make these policies the same has proven
an interesting exercise and at least now I am aware of the knobs to
i have been told its an honor system however
someone i know bought the license and it was just a piece of paper saying
they could use it
On Thu, Apr 25, 2013 at 10:04 PM, OBrien, Will obri...@missouri.edu wrote:
My apologies, I didn't pay attention to the blade you referenced.
That blade is
Also, you can do then next-hop discard in your policy and you won't need
the static route.
On Fri, Apr 26, 2013 at 2:04 PM, Richard A Steenbergen r...@e-gerbil.netwrote:
On Fri, Apr 26, 2013 at 11:14:39AM -0500, Eric Krichbaum wrote:
Thanks everyone. The policy straight to discard works for
11 matches
Mail list logo
