[j-nsp] M20 / RE2 Full table
Can I run a full BGP table on the M20 with a RE2 with 768MB memory? Full IPv4 and IPv6 table. /Patrik ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Debug vmcore files
You could use gdb. But the likelihood of any success without source code is slim. You're better off sending them to jtac. On Tue, Mar 1, 2011 at 6:36 AM, meryem Z merye...@hotmail.com wrote: Hello community, Is there any tool to debug vmcore files generated on an m-series juniper router ? Thanks. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Debug vmcore files
You mean kgdb i guess. this tool is available on juniper routers on /var/bin. I'm wondering if anyone has tested it before ? Thank you. From: routeh...@gmail.com Date: Tue, 1 Mar 2011 07:21:58 -0500 To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Debug vmcore files You could use gdb. But the likelihood of any success without source code is slim. You're better off sending them to jtac. On Tue, Mar 1, 2011 at 6:36 AM, meryem Z merye...@hotmail.com wrote: Hello community, Is there any tool to debug vmcore files generated on an m-series juniper router ? Thanks. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Debug vmcore files
Here's an example below. You'll either need to use gdb on the box itself, or get/xcompile a powerpc-freebsd gdb. Again, without source, you're not going to get far. % tar zvxf /var/tmp/chassisd.core-tarball.4.tgz chassisd.core.4.gz juniper.conf.gz messages chassisd.info.4 juniper.conf.1.gz % gzip -d chassisd.core.4.gz % gdb /usr/sbin/chassisd chassisd.core.4 GNU gdb 6.5 [juniper_2006a_411] Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as powerpc-specifix.com-freebsd...(no debugging symbols found) Reading symbols from /usr/lib/libddl-access.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libddl-access.so.1 Reading symbols from /usr/lib/libjipc.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libjipc.so.1 Reading symbols from /usr/lib/libberkeley-db.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libberkeley-db.so.4 Reading symbols from /usr/lib/libthr.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libthr.so.2 Reading symbols from /usr/lib/libisc.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libisc.so.2 Reading symbols from /usr/lib/libkvm.so.3... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libkvm.so.3 Reading symbols from /usr/lib/libfasic.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfasic.so.1 Reading symbols from /usr/lib/libhsl2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libhsl2.so.1 Reading symbols from /usr/lib/libcmb.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcmb.so.1 Reading symbols from /usr/lib/libcnh.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcnh.so.1 Reading symbols from /usr/lib/libjpci.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libjpci.so.1 Reading symbols from /usr/lib/libm.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libm.so.4 Reading symbols from /usr/lib/libfabric2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfabric2.so.1 Reading symbols from /usr/lib/libfabric1.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfabric1.so.1 Reading symbols from /usr/lib/libprovider.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libprovider.so.1 Reading symbols from /usr/lib/libiic.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libiic.so.1 Reading symbols from /usr/lib/libcam.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcam.so.3 Reading symbols from /usr/lib/libsbuf.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libsbuf.so.3 Reading symbols from /usr/lib/libutil.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libutil.so.5 Reading symbols from /usr/lib/libgcc.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgcc.so.1 Reading symbols from /usr/lib/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libc.so.6 Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/libexec/ld-elf.so.1 Core was generated by `chassisd'. Program terminated with signal 6, Aborted. #0 0x42683428 in kill () from /usr/lib/libc.so.6 [New Thread 0x2057000 (LWP 100110)] (gdb) bt #0 0x42683428 in kill () from /usr/lib/libc.so.6 #1 0x421d8a30 in raise () from /usr/lib/libthr.so.2 #2 0x42681e88 in abort () from /usr/lib/libc.so.6 #3 0x01c00c64 in vlogging_event () #4 0x01c00af4 in vlogging () #5 0x01c00ce4 in logging () #6 0x01ab9670 in pic_clean_init () #7 0x01a16308 in mcontrol_check_backup_active () #8 0x01a16e20 in msm_exec () #9 0x01a17b2c in mcontrol_init () #10 0x019365e4 in ch_init () #11 0x01938640 in ch_a2_fru_map_set_context () #12 0x01ab3620 in allocadupx () #13 0x01ab44bc in main () (gdb) x 0x01a16308 0x1a16308 mcontrol_check_backup_active+364: 0x3d200201 On Tue, Mar 1, 2011 at 7:29 AM, meryem Z merye...@hotmail.com wrote: You mean kgdb i guess. this tool is available on juniper routers on /var/bin. I'm wondering if anyone has tested it before ? Thank you. From: routeh...@gmail.com Date: Tue, 1 Mar 2011 07:21:58 -0500 To: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] Debug vmcore files You could use gdb. But the likelihood of any success without source code is slim. You're better off sending them to jtac. On Tue, Mar 1, 2011 at 6:36 AM, meryem Z merye...@hotmail.com wrote: Hello community, Is there any tool to debug vmcore files generated on an m-series juniper
Re: [j-nsp] Debug vmcore files
Hi, You can also use the cli command : show system core-dumps core-file-info detail core-filename Regards, David David Roy Orange - IP Domestic Backbone - TAC Tel. +33(0)299876472 Mob. +33(0)685522213 Email. david@orange-ftgroup.com JNCIE-M/T #703 ; JNCIS-ENT -Message d'origine- De : juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] De la part de Scott T. Cameron Envoyé : mardi 1 mars 2011 15:02 À : juniper-nsp@puck.nether.net Objet : Re: [j-nsp] Debug vmcore files Here's an example below. You'll either need to use gdb on the box itself, or get/xcompile a powerpc-freebsd gdb. Again, without source, you're not going to get far. % tar zvxf /var/tmp/chassisd.core-tarball.4.tgz chassisd.core.4.gz juniper.conf.gz messages chassisd.info.4 juniper.conf.1.gz % gzip -d chassisd.core.4.gz % gdb /usr/sbin/chassisd chassisd.core.4 GNU gdb 6.5 [juniper_2006a_411] Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as powerpc-specifix.com-freebsd...(no debugging symbols found) Reading symbols from /usr/lib/libddl-access.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libddl-access.so.1 Reading symbols from /usr/lib/libjipc.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libjipc.so.1 Reading symbols from /usr/lib/libberkeley-db.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libberkeley-db.so.4 Reading symbols from /usr/lib/libthr.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libthr.so.2 Reading symbols from /usr/lib/libisc.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libisc.so.2 Reading symbols from /usr/lib/libkvm.so.3... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libkvm.so.3 Reading symbols from /usr/lib/libfasic.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfasic.so.1 Reading symbols from /usr/lib/libhsl2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libhsl2.so.1 Reading symbols from /usr/lib/libcmb.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcmb.so.1 Reading symbols from /usr/lib/libcnh.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcnh.so.1 Reading symbols from /usr/lib/libjpci.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libjpci.so.1 Reading symbols from /usr/lib/libm.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libm.so.4 Reading symbols from /usr/lib/libfabric2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfabric2.so.1 Reading symbols from /usr/lib/libfabric1.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfabric1.so.1 Reading symbols from /usr/lib/libprovider.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libprovider.so.1 Reading symbols from /usr/lib/libiic.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libiic.so.1 Reading symbols from /usr/lib/libcam.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcam.so.3 Reading symbols from /usr/lib/libsbuf.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libsbuf.so.3 Reading symbols from /usr/lib/libutil.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libutil.so.5 Reading symbols from /usr/lib/libgcc.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgcc.so.1 Reading symbols from /usr/lib/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libc.so.6 Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/libexec/ld-elf.so.1 Core was generated by `chassisd'. Program terminated with signal 6, Aborted. #0 0x42683428 in kill () from /usr/lib/libc.so.6 [New Thread 0x2057000 (LWP 100110)] (gdb) bt #0 0x42683428 in kill () from /usr/lib/libc.so.6 #1 0x421d8a30 in raise () from /usr/lib/libthr.so.2 #2 0x42681e88 in abort () from /usr/lib/libc.so.6 #3 0x01c00c64 in vlogging_event () #4 0x01c00af4 in vlogging () #5 0x01c00ce4 in logging () #6 0x01ab9670 in pic_clean_init () #7 0x01a16308 in mcontrol_check_backup_active () #8 0x01a16e20 in msm_exec () #9 0x01a17b2c in mcontrol_init () #10 0x019365e4 in ch_init () #11 0x01938640 in ch_a2_fru_map_set_context () #12 0x01ab3620 in allocadupx () #13 0x01ab44bc in main () (gdb) x 0x01a16308 0x1a16308 mcontrol_check_backup_active+364: 0x3d200201 On Tue, Mar 1, 2011 at 7:29 AM, meryem Z merye...@hotmail.com wrote: You mean kgdb i guess. this tool is available on
Re: [j-nsp] [c-nsp] P2MP LSPs :: TailEnd/Bud nodes behavior
I'm not sure about the MX80 but on the MX960 with a DPC you can dedicate a
PFE on one of the DPCs to be used for tunnel services, but you lose the
Ethernet interfaces. I believe on the newer MPCs you can do the same and
not lose the Ethernet interfaces. Not sure about support on the MX80
though you'd have to check with Juniper.
Phil
On 3/1/11 2:50 AM, Egor Zimin les...@gmail.com wrote:
In my case I have a deal with MX80
2011/3/1 Phil Bedard phil...@gmail.com:
In the Juniper case you can get around the double replication on the M/T
by using a tunnel services PIC and using a tunnel interface to terminate
the P2MP LSP. Just a limitation of the platforms.
Phil
On 2/28/11 10:44 AM, Egor Zimin les...@gmail.com wrote:
Hello, guys
Today I noticed very interesting difference in implementation of P2MP
LSPs by Cisco and Juniper.
The difference is related to explicit/implicit-null behavior of S2L
Sub-LSP tailend routers:
Cisco implementation:
(http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_p2mp
_p
s6922_TSD_Products_Configuration_Guide_Chapter.html)
---
The tailend routers allocate unreserved labels, which are greater than
15 and do not include implicit or explicit null labels.
---
In Juniper's implementation tailend allocates implicit/explicit null
label as a usual.
As a consequence of this, (it looks like) we can have unnecessary
replication before Bud nodes.
For example:
Let's consider this configuration:
###
label-switched-path LSP-P2MP-16--19 {
to 10.245.87.19;
p2mp TREE1;
}
label-switched-path LSP-P2MP-16--18 {
to 10.245.87.18;
p2mp TREE1;
}
label-switched-path LSP-P2MP-16--15 {
to 10.245.87.15;
p2mp TREE1;
}
label-switched-path LSP-P2MP-16--17 {
to 10.245.87.17;
p2mp TREE1;
}
###
show mpls lsp p2mp ingress
Ingress LSP: 1 sessions
P2MP name: TREE1, P2MP branch count: 4
To FromState Rt P ActivePath LSPname
10.245.87.1710.245.87.16Up 0 *
LSP-P2MP-16--17
10.245.87.1510.245.87.16Up 0 *
LSP-P2MP-16--15
10.245.87.1810.245.87.16Up 0 *
LSP-P2MP-16--18
10.245.87.1910.245.87.16Up 0 *
LSP-P2MP-16--19
Total 4 displayed, Up 4, Down 0
###
As you can see, there are four leaves. Three bottom leaves use the
same downstream interface:
###
show rsvp session p2mp detail | match PATH sentto
PATH sentto: 10.245.87.146 (xe-0/0/2.0) 4 pkts
PATH sentto: 10.245.87.149 (xe-0/0/1.0) 2 pkts
PATH sentto: 10.245.87.149 (xe-0/0/1.0) 2 pkts
PATH sentto: 10.245.87.149 (xe-0/0/1.0) 3 pkts
###
show rsvp session p2mp
Ingress RSVP: 18 sessions
P2MP name: TREE1, P2MP branch count: 4
To FromState Rt Style Labelin Labelout
LSPname
10.245.87.1710.245.87.16Up 0 1 SE -3
LSP-P2MP-16--17
10.245.87.1510.245.87.16Up 0 1 SE -3
LSP-P2MP-16--15
10.245.87.1810.245.87.16Up 0 1 SE - 309200
LSP-P2MP-16--18
10.245.87.1910.245.87.16Up 0 1 SE - 309200
LSP-P2MP-16--19
Total 4 displayed, Up 4, Down 0
###
As you can see, we have two different out labels (3 and 309200) for
the same P2MP LSP. Label 3 is allocated by node 10.245.87.15 because
of PHP.
Can anybody explain, what IETF speaks about this case ? Must tailend
routers allocate unreserved label or not ? I can't find any mention of
this case in RFCs (4875, 4461).
--
Best regards,
Egor Zimin
___
cisco-nsp mailing list cisco-...@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
--
Best regards,
Egor Zimin
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] M20 / RE2 Full table
It actually depends on other factors than just the RE. The SSB may not have enough memory depending on number of neighbors and ports. Sent from my Motorola Xoom On Mar 1, 2011 4:12 AM, Patrik Lagerman p...@connect2ip.se wrote: ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] M20 / RE2 Full table
What is max on SSB-E with 128MB mem? On Tue, 1 Mar 2011 07:46:17 -0700, Michael Loftis wrote It actually depends on other factors than just the RE. The SSB may not have enough memory depending on number of neighbors and ports. Sent from my Motorola Xoom On Mar 1, 2011 4:12 AM, Patrik Lagerman p...@connect2ip.se wrote: ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Debug vmcore files
It is a good idea. one more question plz: Is it safe to read a vmcore file of a router on another router ? since the first one crashed recently and any command with a lot of output makes him stop responding. Thanks again for your help. From: david@orange-ftgroup.com To: routeh...@gmail.com; juniper-nsp@puck.nether.net Date: Tue, 1 Mar 2011 15:18:28 +0100 Subject: Re: [j-nsp] Debug vmcore files Hi, You can also use the cli command : show system core-dumps core-file-info detail core-filename Regards, David David Roy Orange - IP Domestic Backbone - TAC Tel. +33(0)299876472 Mob. +33(0)685522213 Email. david@orange-ftgroup.com JNCIE-M/T #703 ; JNCIS-ENT -Message d'origine- De : juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] De la part de Scott T. Cameron Envoyé : mardi 1 mars 2011 15:02 À : juniper-nsp@puck.nether.net Objet : Re: [j-nsp] Debug vmcore files Here's an example below. You'll either need to use gdb on the box itself, or get/xcompile a powerpc-freebsd gdb. Again, without source, you're not going to get far. % tar zvxf /var/tmp/chassisd.core-tarball.4.tgz chassisd.core.4.gz juniper.conf.gz messages chassisd.info.4 juniper.conf.1.gz % gzip -d chassisd.core.4.gz % gdb /usr/sbin/chassisd chassisd.core.4 GNU gdb 6.5 [juniper_2006a_411] Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as powerpc-specifix.com-freebsd...(no debugging symbols found) Reading symbols from /usr/lib/libddl-access.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libddl-access.so.1 Reading symbols from /usr/lib/libjipc.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libjipc.so.1 Reading symbols from /usr/lib/libberkeley-db.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libberkeley-db.so.4 Reading symbols from /usr/lib/libthr.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libthr.so.2 Reading symbols from /usr/lib/libisc.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libisc.so.2 Reading symbols from /usr/lib/libkvm.so.3... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libkvm.so.3 Reading symbols from /usr/lib/libfasic.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfasic.so.1 Reading symbols from /usr/lib/libhsl2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libhsl2.so.1 Reading symbols from /usr/lib/libcmb.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcmb.so.1 Reading symbols from /usr/lib/libcnh.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcnh.so.1 Reading symbols from /usr/lib/libjpci.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libjpci.so.1 Reading symbols from /usr/lib/libm.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libm.so.4 Reading symbols from /usr/lib/libfabric2.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfabric2.so.1 Reading symbols from /usr/lib/libfabric1.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfabric1.so.1 Reading symbols from /usr/lib/libprovider.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libprovider.so.1 Reading symbols from /usr/lib/libiic.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libiic.so.1 Reading symbols from /usr/lib/libcam.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libcam.so.3 Reading symbols from /usr/lib/libsbuf.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libsbuf.so.3 Reading symbols from /usr/lib/libutil.so.5...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libutil.so.5 Reading symbols from /usr/lib/libgcc.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgcc.so.1 Reading symbols from /usr/lib/libc.so.6... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libc.so.6 Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/libexec/ld-elf.so.1 Core was generated by `chassisd'. Program terminated with signal 6, Aborted. #0 0x42683428 in kill () from /usr/lib/libc.so.6 [New Thread 0x2057000 (LWP 100110)] (gdb) bt #0 0x42683428 in kill () from /usr/lib/libc.so.6 #1 0x421d8a30 in raise () from /usr/lib/libthr.so.2 #2 0x42681e88 in abort () from /usr/lib/libc.so.6 #3 0x01c00c64 in vlogging_event () #4 0x01c00af4 in
Re: [j-nsp] M20 / RE2 Full table
It's possible, but there are alot of other factors, number of peers, forwarding table size, L3VPN/L2VPN or no, etc. On the surface it sounds like a bad idea though. Especially since the M20 is EOL and doesn't have the resources to support newer code versions. On Tue, Mar 1, 2011 at 5:47 AM, Patrik Lagerman p...@connect2ip.se wrote: Can I run a full BGP table on the M20 with a RE2 with 768MB memory? Full IPv4 and IPv6 table. /Patrik ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] M20 / RE2 Full table
I know of one doing this. I would not recommend it in a production environment. DRAM 768 MB Memory utilization 95 percent CPU utilization: User 2 percent Background 2 percent Kernel 5 percent Interrupt 0 percent Idle 91 percent Model RE-2.0 -Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Patrik Lagerman Sent: Tuesday, March 01, 2011 5:47 AM To: juniper-nsp@puck.nether.net Subject: [j-nsp] M20 / RE2 Full table Can I run a full BGP table on the M20 with a RE2 with 768MB memory? Full IPv4 and IPv6 table. /Patrik ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Debug vmcore files
On Tue, Mar 01, 2011 at 07:21:58AM -0500, Scott T. Cameron wrote: You could use gdb. But the likelihood of any success without source code is slim. You'd be absolutely amazed how much JTAC stupidity can be avoided by looking at the coredump backtrace yourself, without needing source access. As I understand it they use some point and click tool for automatically identifying PRs which match a coredump, and in my experience their tool is on crack a VERY high percentage of the time. Being able to say uh no, that's not even close to what I see in the backtrace, please try again can literally cut months off the time it takes for a case to be resolved. -- Richard A Steenbergen r...@e-gerbil.net http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] 10.2R4
http://www.juniper.net/alerts/viewalert.jsp?txtAlertNumber=PSN-2010-12-112actionBtn=Search Is 10.2R4 actually released? The latest I can find for download is 10.2R3.10. I must be missing something. Thanks, -b -- Bill Blackford Network Engineer Logged into reality and abusing my sudo privileges. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] 10.2R4
Hi Bill, No, it's not out yet. Aviva In message aanlktikesxjadsbwxdm-dxac0nsshdcj-+cyqkx39...@mail.gmail.comyou wr ite: http://www.juniper.net/alerts/viewalert.jsp?txtAlertNumber=PSN-2010-12-112ac tionBtn=Search Is 10.2R4 actually released? The latest I can find for download is 10.2R3.10. I must be missing something. Thanks, -b -- Bill Blackford Network Engineer Logged into reality and abusing my sudo privileges. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
