ACE module status is unknown “FSM_FT_STATE_STANDBY_COLD”,

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2015 10:02 AM - edited 03-20-2019 08:26 PM
suddenly ACE module status is unknown “FSM_FT_STATE_STANDBY_COLD”, after reloading the FT worked fine , i need to know the root cause for this ?
- Labels:
-
Cisco Bugs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-25-2015 07:15 PM
Just to close off this unanswered question, you can get into that state (FSM_FT_STATE_STANDBY_COLD) if you have an active and standby ACE and you upload a new cert and/or key and forget to import the cert and/or key to the standby ACE. Then if you save the config the active and standby don't have an identical list of certs and/or keys and it goes into COLD state.
To fix, upload the missing certs and/or keys in appropriate context on the standby ACE, change to the context that should be active (on the active ACE), and type the following and save the config:
conf t
no ft auto-sync running-config
ft auto-sync running-config
exit
wr mem
