Does anyone know how the inside host limit could change from 50 to 10?
We've had the unit for a while now and it had been fine. However recently users have started complaining of being unable to access the internet. When we checked the ASA it is showing 10 as the inside host limit where as previously it had been 50.
I am not really sure how this could get changed, but you can update the Activation key which determines how many users may connect to the ASA at one time. You can use the activation-key command to do this, but I am not sure where you would get your original key from. On top of that even if you could find it I am not sure what it would do if you tried to enter it again, it could stop it from working all together. You best bet is to run the "show activation-key" command and copy this info. Then contact Cisco and see what it is licensed for. Depending on what answers you get from there you may have to contact your reseller and either upgrade or find out why your key is no longer supporting 50 users if you can prove that is what you bought.
If the device crashed or if you did a format of the flash, it is possible that the original activation key is lost and you are back to the base license. If you had a "show version" output before the issue happened, that will have the activation key. You can enter that to the firewall (activation-key ). If that is not possible, I would suggest you contacting Cisco TAC Licensing Team. They will be able to regenerate the license key for you once they determine that you did have the 50 host license (based on your serial number). Hope this helps.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...