ASA + FirePOWER 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 ASA
Configure the inside (GigabitEthernet 1/2) and wifi (GigabitEthernet 1/9) interfaces to have IP
addresses as needed within the existing environment. In this example, inside clients are on the
10.0.0.1/24 network and WIFI clients are on the 10.1.0.1/24 network.
asa(config)# interface gigabitEthernet 1/2
asa(config-if)# ip address 10.0.0.1 255.255.255.0
asa(config)# interface gigabitEthernet 1/9
asa(config-if)# ip address 10.1.0.1 255.255.255.0
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:
asa(config)# dhcpd address 10.0.0.2-10.0.0.100 inside
asa(config)# dhcpd address 10.1.0.2-10.1.0.100 wifi
Also the modification of the DHCP pools will disable the previous DHCP server on the ASA, and
