Hi - does anyone have any good practices for hardware replacement where SSH is used? For example a remote engineer replaces a switch, a config file is pushed on from our NMS after some basic configuration & then all seems well - except we need to generate the SSH key with 'crypto key generate' and we can not ssh to the box to do this. We don't really want the onsite engineer to generate the key - can we do this in the config file somehow? Ideally keeping the key the same as before so we don't have a problem with NMS's saying the SSH key has changed.
Also - if the key is generated, is it stored in nvram automatically, or only if you wr mem?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...