I have had an issue last weekend with an upstream peer of my transit providers.
They have had a route stuck in the forwarding table for 2 weeks.
The result of this was that they were pointing one of my prefixes to a specific
one of my transits, when that transit was down they were black holing
On Tuesday, May 14, 2013 09:17:45 AM William Jackson wrote:
General opinions?
This was a common occurrence on some Cisco 7500's running a
specific version of code.
I'm not sure how wide spread the problem could be, but if it
can happen with one vendor, it certainly can happen across
the
Dear experts,
Is there any way to know what is the reply of juniper Node when we send an
OID ?
exemple OSPF OID : 1.3.6.1.2.1.14.16.2 ?
Kind regards,
Rachid DHOU
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
I'm looking for people's experience with storm control on Juniper switches. We
have a pair of EX4500 switches and I notice that storm control kicks in a lot.
I'm concerned that it might be stopping legitimate broadcast and multicast
traffic.
Before we put in these Juniper switches into the
Hi.
looks like the OID is a trap that could be sent by Juniper devices. I would
say, if one sends a trap like this towards a Juniper device, the target will
not react in any way.
This was a common occurrence on Mikrotik RouterOS too...
João Lima - Lyma
Analista de Redes e Segurança
MTCNA, MTCRE, MTCINE, JNCIA-EX, JNCIS-ER
Em 14/05/2013 06:03, Mark Tinka escreveu:
On Tuesday, May 14, 2013 09:17:45 AM William Jackson wrote:
General opinions?
This was a common
6 matches
Mail list logo