VPN Termination on Inside Network

[snowmizer]

I am setting up a new ASA 5510 on our inside network so that we can terminate our VPN connections on this ASA. I can get the VPN to work fine however I noticed that once I turned on my VPN profiles now when I try to access the ASDM I'm getting the VPN logon page. So I decided that in order to resolve this I need a separate interface dedicated to management of my ASA.

I'm trying to come up with the best way to do this. I've got two ports on the ASA plugged into my core switch. One is on a separate VLAN from the rest of my network traffic. This is the port I want to use for management. The second will be used to route all of my VPN traffic.

So far I haven't been able to get this to work at all. My thought was that it had to do with routes, NAT and ACLs. I've been playing with them but can't get any combination to work.

Is what I'm doing possible? How have other people set this up?

Thanks.

[snowmizer]

Been thinking about this a bit more. Basically we would like to terminate our VPN on the inside network so that we can filter our VPN users via our Websense V10K. We are also going to be implementing a guest network. If I terminate my VPN on the inside network then I can set up my Internet facing ASA so that it uses virtual firewalls and thus keep separate firewall rules for each network.

What I really need to do is have the ability to configure two IPs on my inside network range (one for management and one for VPN) since using the same IP for VPN termination and management causes issues where I can never access the ASDM from this IP.

Example: Ethernet0/0

               IP 10.1.10.200

Once I set up my VPN on this interface when I enter https://10.1.10.200 I get the VPN logon page not the ASDM page.

Can this be done?

Thanks.

[snowmizer]

I think I've figured out how to get around my issues here. I'll just change the ASDM port from 443 and leave the VPN port at 443. Then I'll just figure that I will manage it from the same interface where I'm terminating my VPN and just control who has access to the ASDM and SSH.