The power of the command line. I believe that you should only use the mouse when you dont know what are doing. That is why graphical interfaces exist. Secure CRT SSH2SSH1TelnetTelnetSSHReloginSerialTAPIRAW SecureCRT. Securecrt For Mac Serial' title='Securecrt For Mac Serial' />securecrt864securecrt. SecureCRT,SecureCRT WindowsUNIXVMSVCP. Securecrt5. 1securecrt5. Internet Intranet IPv6 Windows. SecureCRTSSHSSH1SSH2TelnetrloginSecureCRT. Securecrt For Mac Serial' title='Securecrt For Mac Serial' />Configure the ASA 5. W X with a Non Default IP or Multiple VLAN Configuration. Introduction. This document describes how to perform initial installation and configuration of a Cisco Adaptive Security Appliance ASA 5. W X device when the default IP addressing scheme needs to be modified to fit into an existing network or if multiple wireless VLANs are required. There are several configuration changes that are required when modifying the default IP addresses in order to access the wireless access point WAP as well as ensure that other services such as DHCP continue to function as expected. In addition, this document provides some CLI configuration examples for the integrated Wireless Access Point WAP to make it easier to complete initial configuration of the WAP. This document is intended to supplement the existing Cisco ASA 5. World Market Employee Handbook here. X Quick Start guide available on the Cisco website. Prerequisites. This document only applies to the initial configuration of a Cisco ASA5. W X device that contains a wireless access point and is only intended to address the various changes needed when you modify the existing IP addressing scheme or add additional wireless VLANs. For default configuration installations, the existing ASA 5. X Quick Start Guide must be referenced. Requirements. Cisco recommends that you have knowledge of these topics Cisco ASA 5. W X device. Client machine with a terminal emulation program such as Putty, Secure. CRT, etc. Console Cable and Serial PC Terminal Adapter DB 9 to RJ 4. Components Used. The information in this document is based on these software and hardware versions Cisco ASA 5. W X device. Client machine with a terminal emulation program such as Putty, Secure. CRT, etc. Console Cable and Serial PC Terminal Adapter DB 9 to RJ 4. ASA Fire. POWER Module. Integrated Cisco Aironet 7. Built in WAPThe information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared default configuration. If your network is live, make sure that you understand the potential impact of any command. Network Diagrams. As shown in this image, examples of the IP addressing that will be applied in two different topologies ASA Fire. POWER with an inside switch ASA Fire. POWER without an inside switch Configure. These steps must be performed in order after you power on and boot the ASA with the console cable connected to the client. Step 1. Modify Interface IP configuration on ASAConfigure the inside Gigabit. Ethernet 12 and wifi Gigabit. Ethernet 19 interfaces to have IP addresses as needed within the existing environment. In this example, inside clients are on the 1. WIFI clients are on the 1. Ethernet 12. asaconfig if ip address 1. Ethernet 19. asaconfig if ip address 1. Note You will get this warning when you change the above interface IP addresses. This is expected. Interface address is not on same subnet as DHCP pool. WARNING DHCPD bindings cleared on interface inside, address pool removed. Step 2. Modify DHCP pool settings on both inside and wifi interfaces. This step is required if the ASA is to be used as the DHCP server in the environment. If another DHCP server is used to assign IP addresses to clients then DHCP should be disabled on the ASA altogether. Since you have now changed our IP addressing scheme, you need to alter the existing IP address ranges that the ASA is providing to clients. These commands will create new pools to match the new IP address range asaconfig dhcpd address 1. Also the modification of the DHCP pools will disable the previous DHCP server on the ASA, and you will need to re enable it. If you do not change the interface IP addresses before making the DHCP changes then you will receive this error asaconfig dhcpd address 1. Address range subnet 1. Step 3. Specify DNS server to pass to inside and Wi. FI DHCP clients. When they assign IP addresses via DHCP, most clients also need to be assigned a DNS server by the DHCP server. These commands will configure the ASA to include the DNS server located at 1. You need to substitute the 1. DNS server or a DNS server provided by your ISP. Step 4. Modify HTTP access configuration on the ASA for Adaptive Security Device Manager ASDM access Since the IP addressing has been changed, HTTP access to the ASA also needs to be modified so that clients on the inside and Wi. FI networks can access ASDM to manage the ASA. Note This configuration allows any client on the inside or wifi interfaces to access the ASA via ASDM. As a security best practice, you must limit the scope of addresses to trusted clients only. Step 5. Modify Interface IP for Access Point Management in WLAN console interface BVI1 asa session wlan console. Password Cisco. apconfigure terminal. Enter configuration commands, one per line. End with CNTLZ. apconfiginterface BVI1. Step 6. Modify default gateway on WAPThis step is required so that the WAP knows where to send all traffic that is not originated on the local subnet. This is required to provide to access the WAP GUI via HTTP from a client on the ASA inside interface. Step 7. Modify the Fire. POWER Module Management IP Address OptionalIf you also plan to deploy the Cisco Fire. POWER also known as SFR module then you also need to change its IP address in order to access it from the physical Management. ASA. There are two basic deployment scenarios that determine how to configure the ASA and the SFR module A topology in which the ASA Management. A topology where an inside switch is not present. Depending on your scenario,these are the appropriate steps If the ASA Management. You can session into the module and change it from the ASA before connecting it to an inside switch. This configuration allows you to access the SFR module via IP by placing it on the same subnet as the ASA inside interface with an IP address of 1. Lines in bold are specific to this example and are required for establishing IP connectivity. Lines in italics will vary by environment. Opening console session with module sfr. Connected to module sfr. Escape character sequence is CTRL X. Cisco ASA5. 50. 6W v. Sourcefire. 3D login admin. Password Sourcefire. Output Truncated you will see a large EULA. Please enter YES or press lt ENTER to AGREE to the EULA YES. System initialization in progress. Please stand by. You must change the password for admin to continue. Enter new password. Confirm new password. You must configure the network to continue. You must configure at least one of IPv. IPv. 6. Do you want to configure IPv. Do you want to configure IPv. Configure IPv. 4 via DHCP or manuallyEnter an IPv. Enter an IPv. 4 netmask for the management interface 2. Enter the IPv. 4 default gateway for the management interface 1. Enter a fully qualified hostname for this system Sourcefire. D CiscoSFREnter a comma separated list of DNS servers or none 1. Enter a comma separated list of search domains or none example. If your networking information has changed, you will need to reconnect. For HTTP Proxy configuration, run configure network http proxyApplying Default Allow All Traffic access control policy.