We have had kind of mixed experience with this platform. Used to M7i/M10i
which seems inheritantly more stable.

A couple of log entries that really fill up the logs;

kernel: RT_PFE: NH IPC op 35 (CHANGE FLOOD NEXTHOP) failed, err 1 (Unknown)
rpd[4786]: RPD_OS_MEMHIGH: Using 2151293 KB of memory, 101 percent of
available

Oh, and
rpd[4786]: RPD_ABORT: abort rpd[4786] version 8.5R3.4 built by builder on
2008-04-24 03:46:20 UTC: Cannot allocate memorytask_page_set_brk:
brk(0x8879c000): Cannot allocate memory

which probably resulted in

routing (PID 4786) terminated by signal number 6. Core dumped!

Half an hour ago..

/BT


-----Opprinnelig melding-----
Fra: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] På vegne av [EMAIL PROTECTED]
Sendt: 8. november 2008 15:03
Til: [EMAIL PROTECTED]
Kopi: [EMAIL PROTECTED]; [email protected]
Emne: Re: [j-nsp] Why should I *not* buy an MX?

> >> Because it's expensive compared to possible alternatives outside
> >> J-Land, including, but not limited to, Force-10.
> >
> > force10's cost advantage is chipped away at by the OP's IPv6
requirement.
> 
> Yes, IPv6 and MPLS are not currently supported (and they might be or
> not, in the future) by Force-10. Pricewise that would lead to choosing
> Cisco Cat6K with or without DFCs depending on throughput requirements.

Cisco Cat6K with traditional "LAN" type cards = globally significant
VLAN IDs. That alone throws the solution right out the window for us.
There are many other features that Cisco Cat6K with LAN type cards do
not support, for instance dual tagged VLANs.

It all depends on your requirements, of course. For us, the MX looks
very attractive, both featurewise and pricewise. But again, we use it
as a router, now a switch.

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp

Reply via email to