Cisco ASA 5510 - Printing out configuration?
Can anyone tell me - step by step - how to use PuTTY to connect to my Cisco ASA 5510 from the internal network and print out its configuration?
Firstly, I am a reluctant SysAdmin and it is not my primary job function. Secondly, I need help as the company that initially configured my Cisco ASA 5510's and VPN system is non-responsive in assisting me and I need to complete a PCI Compliance scan in a few days and this issue must be resolved. To put it succinctly, I need to find out exactly how our VPN is configured so that I can justify why we have remote access and prove that its secure.
Thirdly, PCI Compliance is a bitch. Grrrrrr.
Posted Aug 25, 2014, 7:52 PM UTC
Open putty, on the left go under Session - Logging, set it to All session output and enter in some file to store all output displayed. Put the IP of the ASA in and select either telnet or SSH depending on how the management access is configured. Once prompted, enter credentials/password. Once you're sitting at the console, enter show run to start printing out the config, use the space bar or Enter key to scroll through. You can also type term pag 0 before entering show run - this will cause it to print the entire config output at once instead of walking through it with the space bar.
If you can't get in via IP, try connecting a console cable to the console port on the ASA, use the Serial option in putty.
VPN config generally has lines starting with crypto, tunnel-group, etc.
Thank you! I will try this first thing in the morning! Hopefully I won't have to break out the console cable.
^This is good advice, and it's pretty much the easiest way to do it. It's also great to have on when someone is working on the equipment (like TAC or yourself) and it will record a play-by-play of all the work done.
It is great advice. I wouldn't be in this position if I'd kept closer tabs in the first place.
The only thing I'd change from your steps is to log "Printable output" instead of all session output, and instead of show run on an ASA you should use 'more system:running-config', as show run will '*' out portions of the configuration. For a PCI audit, the areas obscured are probably fine as they will be pre-shared keys and such, but it is nice to get the full configuration anyway as a backup that you can paste directly back into another ASA if you need to restore the configuration.
Great tip - yes, using more system:run will print out pre-shared keys for VPNs - you won't get use/enable passwords back, but having VPN keys is nice if you ever need to restore a config.
You won't get the passwords back in plain text, but you'll get the 'username XXX password YYY encrypted' lines back, which if pasted back into the ASA will continue working. Could be useful if you have no TACACS and a ton of local accounts on the firewall and don't want to have to reset everyone's password in case the box dies.