Switching

Hi all,

I tried to upgrade software on EX4200, but after I execute command

 request system software add /var/tmp/jloader-ex-3242-11.3I20110326_0802_hmerge-signed.tgz

proccess fails on fpc0 device with error:

fpc0:
tar: +CONTENTS: Cannot change ownership to uid 18520, gid 0: Invalid argument
tar: +COMMENT: Cannot change ownership to uid 18520, gid 0: Invalid argument
tar: +DESC: Cannot change ownership to uid 18520, gid 0: Invalid argument
tar: +INSTALL: Cannot change ownership to uid 18520, gid 0: Invalid argument
tar: jloader-ex-3242-11.3I20110326_0802_hmerge.tgz: Cannot change ownership to uid 18520, gid 0: Invalid argument
tar: jloader-ex-3242-11.3I20110326_0802_hmerge.tgz.md5: Cannot change ownership to uid 18520, gid 0: Invalid argument
tar: jloader-ex-3242-11.3I20110326_0802_hmerge.tgz.sha1: Cannot change ownership to uid 18520, gid 0: Invalid argument
tar: jloader-ex-3242-11.3I20110326_0802_hmerge.tgz.sig: Cannot change ownership to uid 18520, gid 0: Invalid argument
tar: certs.pem: Cannot change ownership to uid 18520, gid 0: Invalid argument
tar: Error exit delayed from previous errors

I tried upgrade from USB and HTTP - result is the same.

On fpc01 device the same files (jloader and junos) was installed without any problem.

After upgrade on fpc01 device (upgraded) all ports are down - as I understand the reason is sowftare mismatch.

Any suggestions how to upgrade fpc0?

Thanks!

It sounds like you attempted to perform the upgrade on a device which was not the master...

See if you can get member 0 (fpc0) back in sync by using the following command:

request system software  add <file> member <member_number>

HTHs.

By the way, just another tidbit of information, if you have not enabled the automatic software update feature, you have to manually install the correct software version on each prospective member switch as it is added to the Virtual Chassis.

Check out the EX documentation on Understanding Automatic Software Update on EX4200 Virtual Chassis Member Switches for more information.

HTHs.

Hi,

actually I already tried 

request system software  add <file> member <member_number>

 with the same result.

Now I have plans to destroy VC an upgrade fpc0 and then create VC back.

Thanks,

Important note:  Members with different JUNOS version cant form a VC.

You upgraded FPC1 with some different version i.e. your VC is broken now.

Post show virtual-chassis status o/p here.

You must be able to see either of FPC in LC status instead of Backup.

Now you have to break the VC and upgrade it seprately.

Hope this helps..!!!

Accept the solution if this answers your qury,KUDO would be great if you think i earned it.