ASA 5520 VPN licenses

Similar Questions

• ASA 5520 - VPN users have no internet.

  Hello

  We just migrated a Pix 515 and an ASA 5520 VPN concentrator.  The firewall part works fine, but we have some problem with our remote VPN.

  Everything inside network is accessible when you use VPN remote but there is no access to our perimeter network or the internet.  I don't know there's only something simple you need that I'm missing, and hoping someone can shed some light on what is needed to allow the VPN tunnel back outdoors and in our DMZ.

  The ASA is running 8.2 (2) 9 and ASDM 6.2 (1).

  See you soon,.

  Rob

  From the 172.16.68.0/24 you can PING 10.10.10.1 correct?

  The 10.10.10.0/24 you can PING 172.16.68.1 correct?

  I'm having a hard time find now how this tunnel is up since you have PFS
  activated on the SAA, but not on the PIX.

  Federico.

• VPN site to site & outdoor on ASA 5520 VPN client

  Hi, I'm jonathan rivero.

  I have an ASA 5520 Version 8.0 (2), I configured the site-to-site VPN and works very well, in the other device, I configured the VPN Client for remote users and works very well, but I try to cofigure 2 VPNs on ASA 5520 on the same outside interface and I have the line "outside_map interface card crypto outdoors (for VPN client). , but when I set up the "crypto map VPNL2L outside interface, it replaces the command', and so I can have only a single connection.

  the executed show.

  ASA1 (config) # sh run

  : Saved

  :

  ASA Version 8.0 (2)

  !

  hostname ASA1

  activate 7esAUjZmKQSFDCZX encrypted password

  names of

  !

  interface Ethernet0/0

  nameif inside

  security-level 100

  address 172.16.3.2 IP 255.255.255.0

  !

  interface Ethernet0/1

  nameif outside

  security-level 0

  IP 200.20.20.1 255.255.255.0

  !

  interface Ethernet0/1.1

  VLAN 1

  nameif outside1

  security-level 0

  no ip address

  !

  interface Ethernet0/2

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  interface Ethernet0/3

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  interface Ethernet0/4

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  interface Ethernet0/5

  Shutdown

  No nameif

  no level of security

  no ip address

  !

  2KFQnbNIdI.2KYOU encrypted passwd

  passive FTP mode

  object-group, net-LAN

  object-network 172.16.0.0 255.255.255.0

  object-network 172.16.1.0 255.255.255.0

  object-network 172.16.2.0 255.255.255.0

  object-network 172.16.3.0 255.255.255.0

  object-group, NET / remote

  object-network 172.16.100.0 255.255.255.0

  object-network 172.16.101.0 255.255.255.0

  object-network 172.16.102.0 255.255.255.0

  object-network 172.16.103.0 255.255.255.0

  object-group network net-poolvpn

  object-network 192.168.11.0 255.255.255.0

  access list outside nat extended permit ip net local group object all

  access-list extended sheep allowed ip local object-group net object-group net / remote

  access-list extended sheep allowed ip local object-group net net poolvpn object-group

  access-list splittun-vpngroup1 extended permitted ip local object-group net net poolvpn object-group

  pager lines 24

  Within 1500 MTU

  Outside 1500 MTU

  outside1 MTU 1500

  IP local pool ippool 192.168.11.1 - 192.168.11.100 mask 255.255.255.0

  no failover

  ICMP unreachable rate-limit 100 burst-size 10

  don't allow no asdm history

  ARP timeout 14400

  Global 1 interface (outside)

  NAT (inside) 0 access-list sheep

  NAT (inside) 1 access list outside nat

  Route outside 0.0.0.0 0.0.0.0 200.20.20.1 1

  Route inside 172.16.0.0 255.255.255.0 172.16.3.2 1

  Route inside 172.16.1.0 255.255.255.0 172.16.3.2 1

  Route inside 172.16.2.0 255.255.255.0 172.16.3.2 1

  Timeout xlate 03:00

  Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02

  Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00

  Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00

  Timeout, uauth 0:05:00 absolute

  dynamic-access-policy-registration DfltAccessPolicy

  the ssh LOCAL console AAA authentication

  No snmp server location

  No snmp Server contact

  Server enable SNMP traps snmp authentication linkup, linkdown cold start

  Crypto ipsec transform-set ESP-3DES-MD5-esp-3des esp-md5-hmac

  Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac

  86400 seconds, duration of life crypto ipsec security association

  Crypto ipsec kilobytes of life security-association 400000

  Crypto-map dynamic outside_dyn_map 20 the value transform-set ESP-3DES-SHA

  card crypto VPNL2L 1 match for sheep

  card crypto VPNL2L 1 set peer 200.30.30.1

  VPNL2L 1 transform-set ESP-3DES-MD5 crypto card game

  map outside_map 65535-isakmp ipsec crypto dynamic outside_dyn_map

  outside_map interface card crypto outside

  crypto isakmp identity address

  crypto ISAKMP allow outside

  crypto ISAKMP policy 20

  preshared authentication

  3des encryption

  md5 hash

  Group 2

  life 86400

  crypto ISAKMP policy 30

  preshared authentication

  aes-256 encryption

  sha hash

  Group 2

  life 86400

  crypto ISAKMP policy 65535

  preshared authentication

  3des encryption

  sha hash

  Group 2

  life 86400

  Telnet timeout 5

  SSH timeout 5

  Console timeout 0

  a basic threat threat detection

  Statistics-list of access threat detection

  !

  !

  internal vpngroup1 group policy

  attributes of the strategy of group vpngroup1

  banner value +++ welcome to Cisco Systems 7.0. +++

  value of 192.168.0.1 DNS server 192.168.1.1

  Split-tunnel-policy tunnelspecified

  Split-tunnel-network-list value splittun-vpngroup1

  value by default-ad domain - domain.local

  Split-dns value ad - domain.local

  the address value ippool pools

  username password asa1 VRTlLlJ48/PoDKjS encrypted privilege 15

  tunnel-group 200.30.30.1 type ipsec-l2l

  IPSec-attributes tunnel-group 200.30.30.1

  pre-shared-key *.

  type tunnel-group vpngroup1 remote access

  tunnel-group vpngroup1 General-attributes

  ippool address pool

  Group Policy - by default-vpngroup1

  vpngroup1 group of tunnel ipsec-attributes

  pre-shared-key *.

  context of prompt hostname

  Cryptochecksum:00000000000000000000000000000000

  : end

  ASA2 (config) #sh run

  Crypto ipsec transform-set ESP-3DES-MD5-esp-3des esp-md5-hmac
  86400 seconds, duration of life crypto ipsec security association
  Crypto ipsec kilobytes of life security-association 400000
  card crypto VPNL2L 1 match for sheep
  card crypto VPNL2L 1 set peer 200.30.30.1
  VPNL2L 1 transform-set ESP-3DES-MD5 crypto card game
  VPNL2L interface card crypto outside
  crypto isakmp identity address
  crypto ISAKMP allow outside
  crypto ISAKMP policy 20
  preshared authentication
  3des encryption
  md5 hash
  Group 2
  life 86400

  tunnel-group 200.30.30.1 type ipsec-l2l
  IPSec-attributes tunnel-group 200.30.30.1
  pre-shared key cisco

  my topology:

  

  I try with the following links, but did not work

  http://www.Cisco.com/en/us/products/ps6120/products_configuration_example09186a0080912cfd.shtml

  http://www.Cisco.com/en/us/products/ps6120/products_tech_note09186a00807e0aca.shtml

  Best regards...

  "" I thing both the force of the SAA with the new road outside, why is that? ".

  without the road ASA pushes traffic inward, by default.

  In any case, this must have been a learning experience.

  Hopefully, this has been no help.

  Please rate, all the helful post.

  Thank you

  Rizwan Muhammed.

• How many group Supportepar ASA 5520 vpn for remote access

  Hello

  Howmany vpn group is supported on asa 5520 with configuraion vpn remote access.

  Concerning

  1 if nat-control is disabled and you do not have any other order NAT in your config file, you do not have it. Try to remove the existing "NAT 0" command and "clear xlate."

  2. you must ensure that your network inside know they can go by ASA to access remote vpn client IP. You have any device layer 3 behind the ASA that does the routing. If so, please verify that this is the routing table.

• ASA 5520 - VPN using LDAP access control

  I'm setting up an ASA 5520 for VPN access.  Authorization & authentication using an LDAP server.  I have successfully configured tunnel, and I can access internal resources.  What I want to do now is to limit access to a specific ad group membership.  In the absence of this belonging to a group, a user cannot access the VPN.

  My VPN client software testing is Cisco Systems VPN Client 5.0.05.0290 Version.  The Group authentication is configured in a connection entry that identifies the Group of Tunnel. I think I wrote that correctly.

  The Version of the software on the SAA is 8.3 (1).

  My current challenge is getting the VPN to stop letting each request for access through little matter belonging to a group.  I found the thread below to be significantly useful, but there is obviously something which is not entirely mesh with my situation.

  https://supportforums.Cisco.com/message/3232649#3232649

  Thanking all in advance for everything offered thoughts and advice.

  Configuration (AAA LDAP, group policy and group of tunnel) is below.

  AAA-Server LDAP protocol ldap
  AAA-Server LDAP (inside) host x.x.y.12
  Server-port 636
  LDAP-base-dn dc = domain, dc = com
  LDAP-scope subtree
  LDAP-naming-attribute sAMAccountName
  LDAP-login-password *.
  LDAP-connection-dn cn = svcacct, or = svcac, or = users, or = svcad, dc = domain, dc = com
  enable LDAP over ssl
  microsoft server type
  LDAP-attribute-map LDAP_MAP
  AAA-Server LDAP (inside) host x.x.y.10
  Server-port 636
  LDAP-base-dn dc = domain, dc = com
  LDAP-scope subtree
  LDAP-naming-attribute sAMAccountName
  LDAP-login-password *.
  LDAP-connection-dn cn = svcacct, or = svcac, or = users, or = svcad, dc = domain, dc = com
  enable LDAP over ssl
  LDAP-attribute-map LDAP_MAP
  AAA-Server LDAP (inside) host x.x.y.11
  Server-port 636
  LDAP-base-dn dc = domain, dc = com
  LDAP-scope subtree
  LDAP-naming-attribute sAMAccountName
  LDAP-login-password *.
  LDAP-connection-dn cn = svcacct, or = svcac, or = users, or = svcad, dc = domain, dc = com
  enable LDAP over ssl
  microsoft server type
  LDAP-attribute-map LDAP_MAP

  AAA-Server LDAP (inside) host x.x.y.10
  Server-port 636
  LDAP-base-dn dc = domain, dc = com
  LDAP-scope subtree
  LDAP-naming-attribute sAMAccountName
  LDAP-login-password *.
  LDAP-connection-dn cn = svcacct, or = svcac, or = users, or = svcad, dc = domain, dc = com
  enable LDAP over ssl
  LDAP-attribute-map LDAP_MAP
  AAA-Server LDAP (inside) host x.x.y.11
  Server-port 636
  LDAP-base-dn dc = domain, dc = com
  LDAP-scope subtree
  LDAP-naming-attribute sAMAccountName
  LDAP-login-password *.
  LDAP-connection-dn cn = svcacct, or = svcac, or = users, or = svcad, dc = domain, dc = com
  enable LDAP over ssl
  microsoft server type
  LDAP-attribute-map LDAP_MAP
  !
  internal group NOACCESS strategy
  NOACCESS group policy attributes
  VPN - concurrent connections 0
  Protocol-tunnel-VPN IPSec webvpn
  address pools no
  attributes of Group Policy DfltGrpPolicy
  VPN - 10 concurrent connections
  Protocol-tunnel-VPN IPSec webvpn
  enable IPSec-udp
  vpn group policy - pro internal
  vpn - pro group policy attributes
  value x.x.y.17 x.x.y.27 WINS server
  Server DNS value x.x.y.19 x.x.y.29
  VPN - 50 simultaneous connections
  Protocol-tunnel-VPN IPSec svc
  group-lock value vpn - pro
  field default value domain.com
  value of address ip-vpn-pro pools
  WebVPN
  client of dpd-interval SVC no
  dpd-interval SVC 1800 bridge
  !

  attributes global-tunnel-group DefaultRAGroup
  LDAP authentication group-server
  LDAP authorization-server-group
  Group Policy - by default-vpn-pro
  authorization required
  type group tunnel vpn - pro remote access
  attributes global-tunnel-group-vpn - pro
  LDAP authentication group-server
  Group-server-authentication (LDAP outside)
  LDAP authorization-server-group
  Group Policy - by default-vpn-pro
  band-Kingdom
  password-management
  band-band
  authorization required
  type tunnel-group NOACCESSGROUP remote access
  attributes global-tunnel-group NOACCESSGROUP
  LDAP authentication group-server
  NOACCESS by default-group-policy

  Hello

  The configuration of what you are looking for is a feature called DAP (Dynamic Access Policy)

  The following link will explain how to set up the same.

  http://www.ciscosystems.com/en/us/products/ps6120/products_white_paper09186a00809fcf38.shtml

  I hope this helps.

  Kind regards

  Anisha

  P.S.: Please mark this thread as answered if you feel that your query is resolved. Note the useful messages.

• 1841. ASA 5520 VPN

  I set up a VPN site-to site between a Cisco ISR 1841 and a Cisco ASA 5520, everything seems to work but I have a few questions.

  1. I must explicitly authorize all VPN traffic in the ACL on the external interface of the 1841, y at - it an equivalent of router "vpn sysopt connection permit?

  2. Although the VPN rises and pass traffic, I have the opportunity to see what follows?

  * 14:11:52.883 22 June: % CRYPTO-6-IKMP_MODE_FAILURE: fast processing mode has failed with the peer 1.1.1.1

  You can share the outputs full? Both sides at the same time?

  Bottom line, I don't think it's normal in IOS 12.4 mainline unless packages are leaking clear ;/

• How to change address on ASA 5520 VPN peer

  Environment:

  7.2 (1) running ASA 5520

  IPSEC VPN L2L established by using wizard.

  Change the IP address of the remote peer. Using ASDM, I can't change the name of the Tunnel Group (which is currently the address peer). I may change the address peer in the IPSec rule, but is that all that is necessary?

  I have to add a new group of tunnel using the new address of peers for the name? If yes how it is related to other objects that are required for a VPN?

  When you create a VPN using the wizard, it creates several objects that are difficult to track when changes are required. Is it better to remove all current VPN objects and create a new configuration using the wizard again?

  Is it's better to make the changes using the CLI? What lines must be changed for peer address when using the commands?

  Thanks in advance for any help!

  I may change the address peer in the IPSec rule, but is that all that is necessary?

  -No, tunnel group name must match the peer address.

  I have to add a new group of tunnel using the new address of peers for the name?

  -Yes.

  Is it's better to make the changes using the CLI?

  -I recommend it, but if you don't know you have no choice.

  Add new tunnel-group with group as new name address peer, same key etc. Add a new address peer settings under rule edit ipsec peer. Then you should be able to remove the old tunnel group. Hope this helps you, been a while since I made this way.

• Routing with Cisco ASA 5520 VPN

  I have installed IPsec vpn remote users in the Cisco ASA 5520 using RADIUS in my main network. Works very well. I have a site to my Cisco ASA5520 tunnels going to other sites, some of the tunnels have Cisco ASA and some have SonicWalls. I wish that my users VPN remote IPSec to be able to navigate in these tunnels is a site to access remote subnets attached to these tunnels. Do I need to use a combination of routing and the ACL? Or can I just use ACL only? Or just use routing only?

  Thank you

  Carlos

  Hello

  The key to set up here is the two ACL of VPN L2L end points that determine the 'interesting' traffic to connect VPN L2L. You will also need to confirm that the connection of the VPN Client is configured so that traffic to the remote sites have sent to the connection of the VPN client. There are also other things that you should check on your ASA plant

  Here most of the things you usually have to confirm

  • Set up 'permit same-security-traffic intra-interface' if it is already present in your configuration
    • This setting will allow connections to form between the hosts that are connected to the same interface on the ASA. In this case, applies because the VPN client users are connected to the interface 'outside' of the ASA and also remote sites are connected to the ASA to "external". If the traffic between the remote VPN Client and VPN L2L sites will be to enter and exit the same interface
  • You will need to check how the customer if configured VPN connection. Split or full Tunnel tunnel
    • If the connection of the VPN Client is configured as Split Tunnel then you need to add all the networks from the remote to the Split Tunnel, so that the connections between the VPN Client is transmitted to the ASA and from there connections VPN L2L
    • If the connection of the VPN Client is configured as full Tunnel, then there no problem that all traffic is transferred to the Client VPN connection all its assets
  • Define the VPN pool in the ACL of VPN L2L
    • You should make sure that the pool network VPN Client is defined in the ACL that define 'interesting' traffic to connect VPN L2L. So, you need to add the pool VPN VPN L2L configurations on the sites of Central America and remote control
  • Configure NAT0 / NAT exempt for remote VPN Client to L2L VPN Site traffic at both ends of the VPN L2L
    • You must ensure that the NAT0 / exempt NAT rules exist for the VPN Client for Remote Site traffic. This will have to be configured on the SAA "outside" interface. Format of configuration varies naturally a bit on the ASA Central his software level.

  These should be the most common things to set up and confirm for traffic to flow between the VPN Client and Remote Sites

  Hope this helps please rate if yes or ask more if necessary.

  -Jouni

• Need help - ASA 5520 VPN issues

  Trying to simulate our in-lab recovery facility. I have 2 ASA 5520 who have a site - tunnel site between them.

  That works fine

  But I also have a requirement for remote access in one of the ASA, which formerly connected needs to route through

  the site - tunnel site to another server on the other side.

  So far the Remoting piece connects very well, I can access all networks connected locally but I can't seem to get the traffic

  to move through the site - site of the tunnel on the other side.

  Is this feasible? If so, if there are suggestions that would be appreciated.

  See you soon

  Dave

  The command is not applied to a specific interface.

  The command activate the feature on the ASA to receive traffic from VPN clients on the external interface and send him outside through the same apart from the interface through the tunnel L2L (and vice versa).

  Federico.

• Issue of ASA 5505 VPN licenses

  I have three places that I want to connect via vpn site-to-site deployed on three ASA 5505. How is the term 'Peers' in the text of license, affecting my script? Each peer ASA in a solution from site to site, or each transmission of user data in the established tunnel also counted?

  Users, passing through the tunnel of site to another are not counted. Only the peers themselves.

• ASA 5520 VPN

  Hello

  Ask for help if it is possible to have both SSL & ipsec site to site vpn configured on a 5520. If so, would there be no degradation of performance or any limitation of no.. users are allowed.

  Any other things I need to know in this respect.

  Appreciate your help,

  Thank you.

  Yes, you can have the SSL VPN, IPSec Site to site, but also remote access IPSec VPN configured and running simultaneously.

  Here's what ASA5520 can support:

  -IPSec 750 (Inc. VPN Site-to-Site and remote access)

  -750 SSL VPN

  http://www.Cisco.com/en/us/products/ps6120/prod_models_comparison.html

  Please note that for SSL VPN, it only comes with license 2 by default, and you must purchase the SSL license if you want to run more than 2 SSL VPN sessions simultaneously.

  Hope that helps.

• ISPS double and two redundant ASA 5520 VPN tunnels

  Hi all

  I have a requirement that looks like this:

  -with two ISPs (of course public IP of different subnets), I have two firewalls that we have to do 2 l2l VPN tunnels.

  Virtual private networks will be redundant to each other and in the case where one of the links is congested, traffic should pass through the other tunnel.

  Did someone do something like that?

  Thank you

  Vlad

  Hi Vlad,

  To have redundant connections, I suggest the following link:

  ASA/PIX 7.x: example of redundant Configuration or backup ISP links

  To find out when the link is congested? I don't think it could be possible at all on the SAA, with a UDP IP SLA jitter, but I think that it is supported only on IOS routers.

  Analysis of IP Service levels using the UDP IP SLA jitter operation

  Thank you.

  Portu.

  Please note all messages that will be useful.

• ASA 5520 - SSL VPN (Anyconnect) licenses

  Hello

  Can someone clarify for me the SSL VPN/AnyConnect for the ASA 5520 license?  Specifically, the differences between the AnyConnect Essentials and AnyConnect Premium.  Our current license looks like this:

  The devices allowed for this platform:
  The maximum physical Interfaces: unlimited
  VLAN maximum: 150
  Internal hosts: unlimited
  Failover: Active/active
  VPN - A: enabled
  VPN-3DES-AES: enabled
  Security contexts: 2
  GTP/GPRS: disabled
  SSL VPN peers: 2
  Total of the VPN peers: 750
  Sharing license: disabled
  AnyConnect for Mobile: disabled
  AnyConnect Cisco VPN phone: disabled
  AnyConnect Essentials: disabled
  Assessment of Advanced endpoint: disabled
  Proxy sessions for the UC phone: 2
  Total number of Sessions of Proxy UC: 2
  Botnet traffic filter: disabled

  This platform includes an ASA 5520 VPN Plus license.

  I guess that means that we have just the 2 'free trial' SSL VPN licenses and nothing else.

  I would like to add 25 or maybe 50 SSL VPN licenses and be able to use a combination of full free client, thin client and groups client AnyConnect.  The 'ASA5500-SSL-25' (or 50) would be the correct license I need to buy?

  Thank you

  Rob

  Hello

  The essentials license is per device and does not allow full-tunnel.

  If you need other features like Secure Desktop, without client SSL and other optional features such as shared licenses, you must go to the Premium license.

  http://www.Cisco.com/en/us/prod/collateral/vpndevc/ps6032/ps6094/ps6120/data_sheet_c78-527494_ps10884_Products_Data_Sheet.html

  Federico.

• Terminology VPN licenses makes me crazy

  Sorry if this question has been postponed, probably several times, but I simply can't have my head wrapped around the SSL VPN license thing. The documentation uses terminology that does match the output of the SHOW VERSION, at least not that I can see.

  So, I have an ASA 5520. We ordered it added 100 SSLVPN licenses. Here is the output appropriate to see THE VERSION

  The devices allowed for this platform:

  The maximum physical Interfaces: unlimited

  VLAN maximum: 150

  Internal hosts: unlimited

  Failover: Active/active

  VPN - A: enabled

  VPN-3DES-AES: enabled

  Security contexts: 2

  GTP/GPRS: disabled

  VPN SSL counterparts: 100

  Total of the VPN peers: 750

  Sharing license: disabled

  AnyConnect for Mobile: disabled

  AnyConnect Cisco VPN phone: disabled

  AnyConnect Essentials: disabled

  Assessment of Advanced endpoint: disabled

  Proxy sessions for the UC phone: 2

  Total number of Sessions of Proxy UC: 2

  Botnet traffic filter: disabled

  This platform includes an ASA 5520 VPN Plus license

  So should what license I, exactly? AnyConnect Essentials is disabled, so it leads me to believe that I have a form any of premium Anyconect (it does not SAY that, he said only: 'VPN PLUS'). Cisco.com looking for part number ASA5520-VPN-PL =, which is the ASA 5520 with the VPN Plus license (without the user SSL 100 Add in) gets me squat. If I do not have a form of "premium anyconnect", why is it SAID that somewhere, instead of saying "this isn't anyconnect essentials, and you do not have these other advanced features?

  I'll try to find a copy of our original order, which will show me all the part numbers, we bought, but I'm afraid that won't do me much good because it doesn't seem to be a comparative table of the licenses and features that maps the old method of doing things for example WEBVPN) to the new method ("ANYCONNECT").

  Is the answer poking me in the eyes and I'm simply not noticing?

  Any help appreciated!

  Jim

  The worm out pre 8.4 code HS has been confusing for many.  You currently have an AnyConnect Premium license that gives you full access to all features SSL AnyConnect VPN, clientless WebVPN, Cisco Secure Desktop, etc.  Your current license will allow 100 concurrent sessions or WebVPN clientless SSL VPN AnyConnect.  With 8.4, the worm out sh was changed to give you a more realistic licensing real you have enabled.  Here is an example of output from one of my ASAs lab for your reference.

  The devices allowed for this platform:

  The maximum physical Interfaces: 8 perpetual

  VLAN: 3 restricted DMZ

  Double ISP: Disabled perpetual

  Junction VIRTUAL LAN ports: perpetual 0

  The hosts on the inside: 10 perpetual

  Failover: Disabled perpetual

  VPN - A: enabled perpetual

  VPN-3DES-AES: activated perpetual

  AnyConnect Premium peers: 2 perpetual

  AnyConnect Essentials: Disabled perpetual

  Counterparts in other VPNS: 10 perpetual

  Total VPN counterparts: 25 perpetual

  Shared license: disabled perpetual

  AnyConnect for Mobile: disabled perpetual

  AnyConnect Cisco VPN phone: disabled perpetual

  Assessment of Advanced endpoint: disabled perpetual

  Proxy UC phone sessions: 2 perpetual

  Proxy total UC sessions: 2 perpetual

  Botnet traffic filter: disabled perpetual

  Intercompany Media Engine: Disabled perpetual

  This platform includes a basic license.

• DHCP relay for users (ASA) SSL VPN

  I have ASA 5520 vpn endpoint. Before asa, there are firewalls which translates the public ip address to the private sector and to pass SSL traffic to ASA. I have configured DHCP relay to get the IP address for the DHCP in Windows Server users:

  dhcprelay Server 10.100.2.101 on the inside

  dhcprelay activate vpn

  dhcprelay setroute vpn

  and it does not work. with the local pool, it works fine. Should I do something else? When I turn on debugging it has not any activity.

  You try to assign the IP address to the SSL vpn client using the DHCP server?

  If so, you don't need these commands contained in your message.

  Basically, you need to set dhcp server in tunnel-group and dhcp-network-scope in group policy.

  Here is an example of Ipsec client. Setup must be the same.

  http://www.Cisco.com/en/us/partner/products/ps6120/products_configuration_example09186a0080a66bc6.shtml