[j-nsp] M10 routing engine memory upgrade

Josef Buchsteiner josefb at juniper.net
Sat Feb 26 03:17:45 EST 2005


Eric,Richard,
             there was an issue on RE2.0 if we had less then 768Memory
             installed and the stick was in slot 3 and the other slots
             are  not  enabled  we  will  not run ECC. Resolutions are
             either  move  the  DIMM into another Slot except 3 or you
             contact  support and ask for a bios upgrade which will be
             then  BIOS  1.4.  This  can  be  checked as well with the
             command 'show chassis routing-engine bios'

             hope this clears why you have seen non ECC with Juniper
             DIMM's and or the change after the upgrade.

             thanks
             Josef

Friday, February 25, 2005, 9:41:14 PM, you wrote:

EVT> Our M5s, prior to upgrading RAM, were Non-ECC.  After the RAM upgrades,
EVT> they were ECC.  This is using Juniper memory.  Sample from config diffs:

EVT>  # router> show chassis routing-engine
EVT>  # Routing Engine status:
EVT> -#     DRAM                       256 MB
EVT> +#     DRAM                       768 MB
EVT>  #     Serial ID                      e3000000ba492b01
EVT>  # 
EVT>  # router> show chassis scb
EVT> @@ -91,7 +91,7 @@
EVT>  # DEVFS: ready for devices
EVT>  # Pentium Pro MTRR support enabled
EVT>  # md0: Malloc disk
EVT> -# DRAM Data Integrity Mode: Non-ECC
EVT> +# DRAM Data Integrity Mode: ECC Mode with h/w scrubbing
EVT>  # npx0: <math processor> on motherboard
EVT>  # npx0: INT 16 interface
EVT>  # pcib0: <Intel 82443BX host to PCI bridge (AGP disabled)> on
EVT> motherboard

EVT> -evt

EVT> -----Original Message-----
EVT> From: juniper-nsp-bounces at puck.nether.net
EVT> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Richard A
EVT> Steenbergen
EVT> Sent: Friday, February 25, 2005 3:23 PM
EVT> To: Pedro Roque Marques
EVT> Cc: John Kristoff; juniper-nsp at puck.nether.net
EVT> Subject: Re: [j-nsp] M10 routing engine memory upgrade

EVT> On Fri, Feb 25, 2005 at 12:08:49PM -0800, Pedro Roque Marques wrote:
>> Brian W Gemberling writes:
>> 
>> > John,
>> 
>> >     Those should work just fine.  They work for me.
>> 
>> Just make really sure that when the box boots up you see a line
EVT> saying:
>>   "DRAM Data Integrity Mode: ECC Mode with h/w scrubbing"
>> 
>> non-ECC memory will cause your system to crash due to memory
>> corruption. It is only a question of time... for a system that is on
>> 24x7 the interval of time for the propabability to be close to 1 is
>> not that high.
>> 
>> We do see that kind of problems in practice.

EVT> Interestingly, I've run across a pile of M5s with RE-333's shipped
EVT> w/256MB 
EVT> that don't have ECC (or at least the kernel doesnt detect it). I wasn't
EVT> able to find any feedback from anyone who had seen Juniper shipping
EVT> non-ECC, but I've now seen about 5 of these, so I'm really starting to
EVT> wonder. :)


 


More information about the juniper-nsp mailing list