quintin.hassell Mon, 03/07/2011 - 11:59

I have the same engine version as you do. I have a TAC case open.

They had me reboot my module. Didn't fix it. I'll let you know if they come up with a solution for me.

benreynolds Thu, 03/10/2011 - 04:29

We are getting the same issue accross the board with our AIP-SSM cards.

Looks like restoring default sig values then manually updating works.  Bit of a pain as we have over 35 units to complete this on.....

Just hope it's not a regular thing .

quintin.hassell Thu, 03/10/2011 - 06:12

Saving your current config and defaulting the sigs, then restoring will work. Also I was advised to try defaulting sig 23899/0 and then trying the update. I'm going to try that tonight to see if it works.

Aibek197938 Tue, 04/10/2012 - 03:43

Signature update S567 has the permanent fix for the issue. Update to S567 (or later) to correct the issue. Reset 23899.0 to its default settings prior to updating.


Change signature 23899.0 to the default settings, for example:

# conf t

(config)# service signature-definition sig0

(config-sig)# default signatures 23899 0

(config-sig)# exit

(config)# exit


This Discussion