Once you purchase the license there are (2) pieces to the puzzle. Hyper-V: Windows Server 2012 R2 (Not supported for ASAv50)ĪWS (c3.large, c3.xlarge, c4.large, c4.xlarge, M4)Īzure (d3, d3_v2) (including Azure Government Cloud) Stateful inspection throughput (multiprotocol) 2(TCP)Īdvanced Encryption Standard (AES) VPN throughput 3Ĭisco An圜onnect ® or clientless VPN user sessions Stateful inspection throughput (maximum) 1(UDP) For more information please visit Cisco Data Sheet including ordering part numbers. Highlited features are the ones I would pay close attention prior purchasing decision. Table below provides all the information you need for Cisco four offerings (asav5, asav10, asav30, asav50) as of April 10, 2018. Before purchasing any ASAv license its crucial to identify what are your requirements such as throughput, session ,etc.

Since everything going virtual, not having licenses tied to physical equipment provides leverage and speed in deployments.īefore hopping in into implementation piece I would like to provide an overview of different licenses that Cisco provides for their virtual ASA’s.Īs you may know the difference is going to be in the resources/features. Ability to “reuse” license if one tenant no longer needs it to the second tenant is a powerful tool. As a Private Cloud provider for example it allows you to manage licenses for your IAAS offering in one centralized location fast and easy. This comes especially helpful if you are in the Cloud sector. Personally, I think it’s a great way to manage all of your licenses. Smart Software Licensing also lets you see your license usage and needs at a glance( source).

You can easily deploy or retire ASAvs without having to manage each unit’s license key. Unlike product authorization key (PAK) licenses, smart licenses are not tied to a specific serial number. With the realease of 9.3 for ASA’s Cisco introduced Smart Licensing where it lets you purchase and manage a pool of licenses centrally.

Cisco asa activation key generator