JFYI..
http://www.juniper.net/techpubs/en_US/junos10.1/information-products/topic-collections/config-guide-policy/topic-28284.html
The nonterminating action operations carry a default accept action
//BR
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
So with 128/16 going live, Juniper may also additionally need to change their
internal addressing!
re0 show interfaces em1 terse
Interface Admin Link ProtoLocal Remote
em1 upup
em1.0 upup inet
, 2011 10:19 PM
To: Tarique A. Nalkhande - BMC; 'Daniel Roesen'; juniper-nsp@puck.nether.net
Subject: RE: [j-nsp] JUNOS and 128.0.0.0 martian (JFYI)
Pardon me for asking this...
But those routes are in private tables... does this really mean that
Juniper is going to block the traffic when it doesn't
Clarke,
If I understood your query correctly, IMHO you would also want to explore the
option of putting this FBF filter under PFE itself (forwarding-option).
--- sample output ---
MX-960 show configuration forwarding-options family inet filter
input
Markus,
The percentage of UDP traffic can vary from less than 5 percent to more than 50
percent of network traffic. After establishing a baseline, you can decide if it
is necessary to rate-limit UDP to preserve bandwidth for other protocols.
For establishing the above baseline, counters
AFAIK, RIB capacity (IPv4) for RE-850-1536 is ~6M.
Thanks Regards
Tarique Abbas Nalkhande
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Serrano Samaca,
Edinson (EXT-Other - MX/Mexico City)
Sent: 07 April, 2011
We had a similar issue after a RE reboot, basically the PFE doesn't
re-initialize clean after the reset. Try this FPC in a different slot to see if
it comes up simultaneously a spare (Working) FPC in slot 2. Based on the
outcome you can then request a RMA.
Thanks Regards
Tarique Abbas
All,
Even we faced a similar problem on our MX's running 10.2R3. Further findings
revealed memory leak bug for mib2d process.. restarting mib2d fixed it.
Juniper is probably tracking it through some internal PR, the committed release
is 10.2R3 which doesn't look likely.
Thanks Regards
Ross,
As aware, in the MX DPC there is a chip called the IChip (this is where all the
data forwarding take place). Earlier there were some cases where IChip was
dropping
the packets. To recover the chip from the 'wedge' state Juniper implemented a
self-healing mechanism as a response to PR
TCC is the way to go..
TCC is supported in CCC, draft-Kompella, and draft-Martini based VPNs to allow
for interworking between dissimilar access technologies (or differing VLAN IDs,
which are normally required to be the same at both ends of a L2 VPN).
Feel free to unicast, if you need
10 matches
Mail list logo