07-06-2010 05:24 AM
Hi ,
My ACE module has been rebooted with unknown reason and this is what I see the reason for the same.
Software
system: Version A2(2.3) [build 3.0(0)A2(2.3)]
system image file: [LCP] disk0:c6ace-t1k9-mz.A2_2_3.bin
installed license: no feature license is installed
last boot reason: NP 1 Failed : NP ME Hung
configuration register: 0x1
IXP CAUSE = NP ME Hung
does anyone tell me is this an hardware issue or software?
Thanks in advance. Any help would be highly appriciated.
REgards
Alex.
07-07-2010 12:14 AM
You will need to do a 'dir core:' and extract all the files you see there.
You then need to send them to the TAC for analysis...they are meaningless without the appropriate decoder.
Gilles.
09-11-2012 08:57 AM
In case this helps anyone in the future. I had this error message today. I am running Version 12.2[125 [build 3.0(0)A4(2.2)].
I appear to have caused it by inadvertantly reintroducing "alias" and "peer" statements into my context THEN shortly thereafter trying to delete the context (in order to recreate via a context restore to test a modified version of another server's configuration). The "no context ABC" caused the hang when it could not talk to this context's failover: nothing was configured on the other end! So the command line hung for 1-2 minutes before it spontaneously rebooted, resulting in the same message you listed.
Regards,
David
09-11-2012 08:13 PM
Hello,
Here you have a link how you can take a look of the recent core dumps files and how you can get them out of the box for further analysis.
Please get a # show tech-support as well.
It is important to collect this data to determine the root cause of the crash, have you had this issue before?
Jorge
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide