So the SCB itself is only responsible for the available bandwidth per slot
but is not and will never be a memory limitation?
Correct on all points.
- CK.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
Thank's for clearification, that helps. So the SCB itself is only
responsible for the available bandwidth per slot but is not and will
never be a memory limitation?
Best,
Jeff
Am 22.07.2015 um 23:51 schrieb Chris Kawchuk:
On 23/07/2015, at 1:30 AM, Jeff Meyers jeff.mey...@gmx.net wrote:
On 23/Jul/15 15:54, Jeff Meyers wrote:
Thank's for clearification, that helps. So the SCB itself is only
responsible for the available bandwidth per slot but is not and will
never be a memory limitation?
That's right.
The SCB provides inter-slot bandwidth. It is not impacted by FIB memory.
Hi,
I see you're running DPC cards, have you considered shifting those
links onto an MPC/Trio Card? (newer chip, more RAM, more horsepower,
yadda yadda yadda =)..) DPC was EOL a while ago, and everything has
been Trio (and now Trio-NG on the new -NG cards coming out now). As
the FIB is pushed
Hi,
The size of the firewall configuration could be concern if you use the box
for subscriber management and have tons of dynamic interface with filters
attached. Otherwise you should be safe to use that knob.
At the moment you have 11.5MB in segment 1, when you enable that know it
will go down
On 22/Jul/15 17:30, Jeff Meyers wrote:
yes, we did (at least since yesterday) although we are not really
requiring more ports or bandwidth right now. If I understand that
correctly, I need to upgrade to SCB2 as well?
Hehehehe, where have I heard that before :-)?
IPv4 BGP table havin' us
Hi,
thanks for the hint, didn't know about that option. This will certainly
safe us if we are running in to limits. We don't have too many filters,
mostly the basic stuff to protect the RE and a few filters on some vlans
with basic white- and/or blacklisting. So really nothing fance although
On 22/Jul/15 02:59, Chris Kawchuk wrote:
I know that a ton of fixes on BGP convergence time son MX80 is definitely a
reason to be 'moving up'... however as you're on RE-2000s on MX480 may not be
applicable.
I see you're running DPC cards, have you considered shifting those links onto
an
Hi,
The 'route' option on 'memory-enhanced' will give you some time before
upgrade to MPC. Actually you should be okay for quite a long time
considering the size of the table you have at the moment.
https://www.juniper.net/documentation/en_US/junos11.4/topics/task/configuration/
On 23/07/2015, at 1:30 AM, Jeff Meyers jeff.mey...@gmx.net wrote:
yes, we did (at least since yesterday) although we are not really requiring
more ports or bandwidth right now. If I understand that correctly, I need to
upgrade to SCB2 as well?
nope -- no need to go to MPC+SCB2 combo.
Over the years, we have run into a couple of issues that translated to either
exhausting FPC memory or corrupting the JTree. Currently, life is good on
13.3R6, which we run on all MX's globally. I haven't run into this specific
issue, and I am just assuming that behavior is improved.
Best
Disabling Basic-Table certainly bought you some time.
Agree that it still does not look good. I suspect that you are running into a
software issue. 11.4 is no longer a supported version, 12.3 is the minimum
supported today, with 13.3R6 as the recommended version. Is it possible for
you to
Hi,
yes, an upgrade is absolutely possible but since there are no major
issues with that release, we didn't do that yet. Are you just assuming a
newer software improves that or did Juniper really do something on that
side?
Best,
Jeff
Am 22.07.2015 um 02:45 schrieb Phil Rosenthal:
I know that a ton of fixes on BGP convergence time son MX80 is definitely a
reason to be 'moving up'... however as you're on RE-2000s on MX480 may not be
applicable.
I see you're running DPC cards, have you considered shifting those links onto
an MPC/Trio Card? (newer chip, more RAM, more
Hello list,
we seem to be running into limits with a MX480 with RE-2000 and 2x
DPCE-4XGE-R since we are seeing these new messages in the syslog:
Jul 22 00:50:36 cr0 fpc0 RSMON: Resource Category:jtree
Instance:jtree0-seg0 Type:free-dwords Available:83072 is less than LWM
limit:104857,
Can you paste the output of these commands:
show conf | display set | match rpf-check
show ver
show route sum
DPC should have enough memory for ~1M FIB. This can get divided in half if you
are using RPF. If you have multiple routing instances, this also can contribute
to the problem.
Best
Hi Phil,
sure:
{master}
jeff@cr0 show configuration | display set | match rpf-check
{master}
nico@FRA4.cr0 show version
Hostname: cr0
Model: mx480
JUNOS Base OS boot [11.4R9.4]
JUNOS Base OS Software Suite [11.4R9.4]
JUNOS Kernel Software Suite [11.4R9.4]
JUNOS Crypto Software Suite
17 matches
Mail list logo
