cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2189
Views
0
Helpful
3
Replies
Highlighted

last boot reason: NP 1 Failed : NP Control Store Parity Error

Hi.

I have a pair of ACE modules in an active/active HA configuration

I currently have two contexts running on ACE1 and Admin context on ACE2.

ACE1 reloaded due to the error:

last boot reason:  NP 1 Failed : NP Control Store Parity Error

This had happened only once, however since then, one of the contexts isn't responding to ICMP requests (well, it does but intermittently and in no set pattern.  The other context on ACE1 is responding fine. 

Software

  loader:    Version 12.2[123]

  system:    Version A2(3.4) [build 3.0(0)A2(3.4)]

  system image file: [LCP] disk0:c6ace-t1k9-mz.A2_3_4.bin

Any suggestions of commands I could use to try and get to the bottom of this?  I'd like to try and see the problem if I can without reloading it and issue going away.

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Cisco Employee

Hi Mick

I encourage you to open a TAC case along with the show tech from ACE1 admin context

Rgds

View solution in original post

3 REPLIES 3
Highlighted
Cisco Employee

Hi Mick

I encourage you to open a TAC case along with the show tech from ACE1 admin context

Rgds

View solution in original post

Highlighted
Beginner

Hi Mick,

I faced the same issue "COUPLE OF TIMES" and every time i raised a tac case , they replaced the hardware through RMA.

1) Upgraded the software to the latest version

2) Replace it through RMA if step 1 does not resolve the issue.

regards,

Parvees

Highlighted

It turned out to be a one off.  Strange how it affected the vlan interface after it rebooted, but a failover of the context and reload of the module and a fail back did the trick.

Content for Community-Ad
This widget could not be displayed.