ASA RAM Requirements for IOS Upgrading



      While looking into NAT translation rules and upgrading here is a nice table from Cisco if you're looking at upgrading anytime and need some RAM requirements like I did.  

Cisco ASA Model

Minimum RAM Requirements (pre Cisco ASA 8.3)

Minimum RAM Requirements (post Cisco ASA 8.3)

Default Shipping RAM on New Cisco ASA Adaptive Security Appliances (as of Feb. 2010)

5505 10-User

256 MB

256 MB

512 MB

5505 50-User

256 MB

256 MB

512 MB

5505 Unlimited-User

256 MB

512 MB

512 MB

5505 Security Plus

256 MB

512 MB

512 MB

5510

256 MB

1 GB

1 GB

5510 Security Plus

256 MB

1 GB

1 GB

5520

512 MB

2 GB

2 GB

5540

1 GB

2 GB

2 GB

5550

4 GB

4 GB

4 GB

5580-20

8 GB

8 GB

8 GB

5580-40

12 GB

12 GB

12 GB

Comments

Post a Comment

Popular posts from this blog

HULC LED PROCESS - 3750 High CPU

Image
If you're looking at a switch and you see the HULC LED Process running high. The HULC LED process does some of the following tasks: 1. Check link status on every port 2. If the switch supports POE, it checks to see if there is a power device 3. Transceiver checks 4. Fan status updates 5. Set LED ports 6. Check on temperature status Overall the HULC LED Process is a monitoring process running. During looking into this I turned off all non-used ports since it checks the link status. Then I made sure the environment was good. Two Cisco Bugs: http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsi78581 http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtn42790
Read more

Cisco Tomcat High CPU Utilization 99 percent

Image
So a client was experience slow web interface usage to their calling node. As well RTMT was shooting off the alert. The alert is for Call Process CPU Node Pegging.  The culprit tomcat! Cisco Tomcat Service -  In enterprise edition this is a web server service. In the business edition (BE Servers) this uses the web server and unity utilizes the service as well. Log in to each call manager node and issue the following command: show process load cpu **OUTPUT** top - 08:55:48 up 340 days, 4:03, 1 user, load average: 4.64, 3.25, 2.98  Tasks: 142 total, 2 running, 140 sleeping, 0 stopped, 0 zombie  Cpu(s): 16.3%us, 3.4%sy, 0.0%ni, 80.1%id, 0.1%wa, 0.0%hi, 0.2%si, 0.0%st  Mem: 4016964k total, 3856400k used, 160564k free, 29904k buffers  Swap: 2064280k total, 1664k used, 2062616k free, 598124k cached  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND  8065 tomcat 25 0 2317m 1.9g 22m S 99.4 50.4 358084:37 tomcat  1 root 15 ...
Read more