[j-nsp] About Juniper MX10 router performance
Morgan McLean
wrx230 at gmail.com
Mon Apr 23 14:30:50 EDT 2012
>From an MX80
inet.0: 400906 destinations, 799589 routes (400906 active, 0 holddown, 0
hidden)
Direct: 7 routes, 7 active
Local: 6 routes, 6 active
OSPF: 105 routes, 104 active
BGP: 799470 routes, 400788 active
Static: 1 routes, 1 active
root at border-a> show chassis routing-engine
Routing Engine status:
Temperature 52 degrees C / 125 degrees F
CPU temperature 64 degrees C / 147 degrees F
DRAM 2048 MB
Memory utilization 42 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 6 percent
Interrupt 0 percent
Idle 93 percent
Model RE-MX80
Start time 2011-12-04 05:07:56 UTC
Uptime 141 days, 13 hours, 34 minutes, 41
seconds
Last reboot reason Router rebooted after a normal shutdown.
Load averages: 1 minute 5 minute 15 minute
0.21 0.14 0.08
root at border-a> show chassis tfeb
TFEB status:
Slot 0 information:
State Online
Intake temperature 51 degrees C / 123 degrees F
Exhaust temperature 67 degrees C / 152 degrees F
CPU utilization 5 percent
Interrupt utilization 0 percent
Heap utilization 29 percent
Buffer utilization 13 percent
Total CPU DRAM 1024 MB
Start time: 2011-12-04 05:10:36 UTC
Uptime: 141 days, 13 hours, 32 minutes, 17
seconds
On Mon, Apr 23, 2012 at 10:00 AM, Doug Hanks <dhanks at juniper.net> wrote:
> The MX5 scaling is identical to the MX80. The only difference is that the
> MX5 restricts the physical port usage to MIC0.
>
> 3,000,000 IPv4 prefixes in the RIB.
> 1,000,000 IPv4 unicast in the FIB.
>
> Thank you,
>
> --
> Doug Hanks - JNCIE-ENT #213, JNCIE-SP #875
> Sr. Systems Engineer
> Juniper Networks
>
>
> On 4/23/12 2:44 AM, "Saku Ytti" <saku at ytti.fi> wrote:
>
> >On (2012-04-22 23:52 -0700), Md. Jahangir Hossain wrote:
> >
> >> In some of forum i found 1.6million but in juniper site i can not found
> >>this information.
> >
> >This is certainly possible and will scale further, depending of course
> >what
> >other things are populated in RLDRAM. Giving exact answer might prove
> >difficult.
> >More than likely you'll find control-plane scaling to be insufficient
> >before you'll be bothered by RDLRAM being filled.
> >
> >--
> > ++ytti
> >_______________________________________________
> >juniper-nsp mailing list juniper-nsp at puck.nether.net
> >https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list