e up again and again in the field. Remote Access To be able to telnet or SSH to your ASA, we must specify the networks from which we will do SO. You do this with the telnet and ssh commands: -5540(config)# telnet 192.168.1.0 255.255.255.0 inside ASA-5540(config)# ssh 192.168.1.0 255.255.255.0 inside Saving Configuration Changes If you read the first edition of this book, you may remember that I complained of the PIX not accepting wri as an abbreviation for write memory. I'm happy to report that wri does work on the ASA platform. Of course, Cisco will tell you that you should use copy run start, but I'm a curmudgeonly old pain in the ass who dislikes change: ASA-5540(config)# wri Building configuration Cryptochecksum: 7401aa77 0584c65f 9ff42fa9 d5ed86ab Chapter 28: ASA Firewall Configuration 3191 bytes copied in 3.280 secs (1063 bytes/sec) The copy running startup command works, but it's ugly: SA-5540(config)# copy run startup-config Source filename [running-config]? Cryptochecksum: 7401aa77 0584c65f 9ff42fa9 d5ed86ab 3191 bytes copied in 3.280 secs (1063 bytes/sec) When you're configuring the active ASA in a failover pair, each command should be sent to the standby PIX automatically after it's been submitted. And when you're saving changes on the active ASA, the write memory command should write the configuration to the standby ASA. To force a save to the standby PIX, use the write standby command: ASA-5540#write standby Building configuration ASA-5540# Sync Started Sync Completed Notice that the preceding Sync Started entry is not a command, but rather the output of normal ASA logging when logging is enabled. You should not run write standby in active/active failover mode, as it will force all contexts to become active on the active ASA. See "Config- uring Failover-Active/Active" on page 497 for details. Logging If you have a firewall in place, you should save and periodically review the logs it gen- erates. When configured for logging, ASA firewalls create a great deal of information. Even on small networks, th