ESA Product Support | ESA Guided Setup | SMA Product Support | Encryption Product Support Email Submission and Tracking Portal | Cisco Talos Reputation Center Support | CRES | Talos
Cisco: Open a Support Case | Support & Downloads | Worldwide Contacts | Bug Search | Notification Service |
ESA: | 13.5.1-277 |
SMA: | 13.6.2-023 | |
Email Plug-in (Reporting): | 1.1.0.133 | |
Email Plug-in (Encryption): | 1.2.1.151 |
Hi,
We are in the process of replacing our existing M660 running on 8.3.6-039 appliance with M680. The existing appliance has been configured with several quarantines and hosts End User Spam quarantine including safe/blocklists. In addition to that the message tracking logs and reports for last 2 years are available in the appliance that is very important and critical to us.
Would like to know any TechNote that explain step-by-step procedure for replacing the appliance.
Appreciate your guidance.
Solved! Go to Solution.
Hello Deiva,
For the SMA's you need to ensure the new M680 can be upgraded to the same version as the M660 of 8.3.6-039 Then to save the configuration of the existing SMA with passwords unmasked to your PC.
Run a backup from the failed battery error SMA to the replacement SMA
Article to do this is provided:
Then once the backup is done.
You can turn this old SMA offline.
Load the configuration backed up into the replacement SMA then put it into full production.
On the replacement SMA, re-check all connections with the ESA once configuration is loaded to scan for new hostkeys.
If there are errors, you can remove the old host-keys for a new re-scan via CLI.
CLI > logconfig > hostkeyconfig
Regards,
Matthew
Hello Deiva,
For the SMA's you need to ensure the new M680 can be upgraded to the same version as the M660 of 8.3.6-039 Then to save the configuration of the existing SMA with passwords unmasked to your PC.
Run a backup from the failed battery error SMA to the replacement SMA
Article to do this is provided:
Then once the backup is done.
You can turn this old SMA offline.
Load the configuration backed up into the replacement SMA then put it into full production.
On the replacement SMA, re-check all connections with the ESA once configuration is loaded to scan for new hostkeys.
If there are errors, you can remove the old host-keys for a new re-scan via CLI.
CLI > logconfig > hostkeyconfig
Regards,
Matthew
Thank you, Matthew. This is an excellent reference. I would be able to revert to you - how it worked in our case - in the next few weeks.
Thanks once again. Much appreciated.
Matthew, Just want to share with you that we have recently replaced the M660 appliance with M680 successfully. The above reference was really helpful. Thank you.