I have a situation where I am replacing a SonicWall FW with an ASA 5510. I have a several Public IP's assigned to several systems in the DMZ.
For example, the outside interface address is 188.8.131.52
I have OWA (443) on 184.108.40.206 > 10.10.20.3
Sharepoint (443) on 220.127.116.11 > 10.10.20.4
Company WebSite (80) 18.104.22.168 > 10.10.20.5
Public IP's are just examples
Not sure how the SonicWall did it, but we are able to get to all our resources as described above.
Is it possible for the ASA to handle this?
Your ISP provided you the public addresses. It is their responsibility to bring the traffic destined to the ASA's outside address as well as other addresses that we added in the static commands to the outside interface of the ASA. Once the traffic arrives on the ASA the ASA will take care of sending the traffic to the appropriate servers on the DMZ.
Piece of cake !!
static (DMZ,outside) 22.214.171.124 10.10.20.3
static (DMZ,outside) 126.96.36.199 10.10.20.4
static (DMZ,outside) 188.8.131.52 10.10.20.5
static (DMZ,outside) tcp 184.108.40.206 443 10.10.20.3 443 net 255.255.255.255
static (DMZ,outside) tcp 220.127.116.11 443 10.10.20.4 443 net 255.255.255.255
static (DMZ,outside) 18.104.22.168 80 10.10.20.5 80 net 255.255.255.255
You also have to allow permission in the acl applied on the outside interface to allow tcp 443 and tcp 80 to these public IP addresses from any source on the internet.
access-list outside-acl permit tcp any host 22.214.171.124 eq 443
access-list outside-acl permit tcp any host 126.96.36.199 eq 443
access-list outside-acl permit tcp any host 188.8.131.52 eq 80
access-g outside-acl in int outside