EX4500 : chassis-manager is thrashing, not restarted

[emil_katzarski]

I have a brand new EX4500 and I am trying to install the recommended JUNOS version 10.2R1.8.

Upgrade goes OK and after rebooting I get this:

Dec 8 11:32:44 init: chassis-manager (PID 1056) started
Dec 8 11:32:45 init: software-forwarding (PID 875) terminated by signal number 6. Core dumped!
Dec 8 11:32:45 init: software-forwarding (PID 1063) started

root@:LC:0% cli
{linecard:0}
root> show chassis hardware
error: the chassis-control subsystem is not running

{linecard:0}

Then I try to reactivate the device (as on EX4200) in the same state:

{linecard:0}
root> request virtual-chassis reactivate
error: command is not valid on the ex4500-40f

{linecard:0}

No success.

Any ideas?

[lteguh]

what was the previous image running in that chassis?

thanks.

[schandra]

Please open a jtac case with the appropriate details

pls include 'request system information' and all the files from /var/log and /var/tmp  and someone will help out.

in the meantime you can try and restart the chassisd process

 restart chassis-control immediately

thx S.C.

[JulioCassettez]

I ran into the same issue.  It turns out, the EX4500's that were shipped were CEE (converged enhanced ethernet) capable which requires a newer JunOS version for the box to fully boot.

http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/reference/specifications/swit... 

Juniper has updated their recommended software site.

https://www.juniper.net/customers/csc/software/junos_software_versions.jsp

How to tell what kind of EX4500 you have (ie. you'll see a -C at the end of the part number....EX4500-40F-FB-C):

http://www.juniper.net/techpubs/en_US/release-independent/junos/topics/task/verification/chassis-ex4...