[j-nsp] Image compatibility

Evan Williams evangellick at btinternet.com
Sat Aug 4 09:57:14 EDT 2007


fpga code, IOS, let's face it the blue box archetecture has past its sell by 
date. These are word I can only read in the morning.
With Juniper, The hardware will only call the software/firmware it requires. 
Consider the Junos Image to be a wardrobe and the hardware picks the clothes 
that fit or are up to date. It is only taking up disk space that would 
otherwise be used by logs.
routng engine redundancy, graceful switchover, not to forget graceful 
restart (when other vendors can agree on a standard) why concern yourself 
with the size of the JUNOS image, the platform should give 5x9s availability



----- Original Message ----- 
From: "Hyunseog Ryu" <r.hyunseog at ieee.org>
To: "Richard A Steenbergen" <ras at e-gerbil.net>
Cc: "juniper-nsp" <juniper-nsp at puck.nether.net>
Sent: Friday, August 03, 2007 11:37 PM
Subject: Re: [j-nsp] Image compatibility


> The reason why Cisco 7600 series router image is so large is because it
> contains all FPCGA firmware images for line card, and during the boot,
> it checks hardware firmware version, and if it's not compatable with
> current IOS version, it will automatically download the FPCGA firmware
> to line card.
> So sometimes it may take up to 15~20 min for booting because of this
> activity.
>
>
>
>
> Richard A Steenbergen wrote:
>> On Thu, Aug 02, 2007 at 06:09:06PM -0500, Hyunseog Ryu wrote:
>>
>>> I think IOS for Cisco 7600 router is about that size already. :-)
>>>
>>
>> 110MB for current advipservices, and growing.
>>
>> -rw-r--r--  1 code  code  110884868 Jun  4 18:05 
>> c7600s72033-advipservicesk9-mz.122-33.SRB1.bin
>>
>> They actually suffer from the exact same problem. If you crack open the
>> IOS image you'll see that the majority of size is actually speciality hw
>> images (SIP/SPA, OSM, etc) and the like that most people don't use (and
>> could easily install a second image for if they did). With Cisco the
>> situation is much worse though, it actually has to read that entire image
>> from flash with every boot (at the blistering speed of 1MB/s from ATA),
>> then unzip it (yes it actually uses zip :P), then TFTP the subimages to
>> MSFC and cards and boot them. If you ever wondered why it takes 5+ 
>> minutes
>> to boot a 6500, a good 3 minutes of it is wasted on preparation due to
>> poor image management... Of course these are the same people who have 
>> been
>> shipping SUP720s for years with internal flash drives which are too small
>> to hold any even slightly moderm images, then charging an extra $2k for a
>> $20 commodity compact flash with a Cisco label on it. :)
>>
>> So yeah, Juniper is certainly better about the entire thing than Cisco in
>> pretty much all respects, but thats hardly saying much.
>>
>>
>
> _______________________________________________
> 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