the ASA, are covered in detail in Chapter 25. The effects of using names like Dingle to identify your access lists have not been studied in depth. Use them at your own risk. In the configuration, the IP address will be translated to the configured name: ASA-5540/GAD# sho run I include Dingle access-list Dingle extended permit tcp any host FileServer eq WWW If you prefer to see the IP addresses, you can disable the names feature by negating the names command. The configuration will once again show the IP addresses: ASA-5540/GAD(config) no names ASA-5540/GAD(config)# sho run I include Dingle access-list Dingle extended permit tcp any host 10.10.10.10 eq WWW Even with names enabled, the output of the show interface command will always show the IP addresses. If you need to see all the names configured on your ASA, use the show names command: ASA-5540/GAD #sho names name 10.10.10.1 ASA-Outside name 10.10.10.10 FileServer name 192.168.1.1 ASA-Inside Thanks to the new capabilities in the OS, you can also use the sho run names command: ASA-5540/GAD #sho run names name 10.10.10.1 ASA-Outside name 10.10.10.10 FileServer name 192.168.1.1 ASA-Inside The names feature is extremely helpful in that it makes ASA configurations easier to read. With very large configurations, the number of IP addresses can be staggering, and trying to remember them all is a practical impossibility. Chapter 28: ASA Firewall Configuration Object Groups Object groups allow a group of networks, IP addresses, protocols, or services to be referenced with a single name. This is extremely helpful when you're configuring com- plex access lists. Take the situation shown in Figure 28-2. There are three web servers, each of which offers the same three protocols: SMTP (TCP port 25), HTTP (TCP port 80), and HTTPS (TCP port 443). Services on each Port 25: SMTP web server: Port 80: HTTP Web server #1 Port 443: HTTPS 192.168.1.101 Web server #2 192.168.1.201 Outside Inside Web server #3 192.168.1.228 Figure 28-2. Complex access list scenario This example shows a c