I'm troubleshooting some problems with one of our 3005 concentrators.
In looking into this, I noticed that the firmware is different between
the two, and rather old. One is running 3.1 and the other is running
3.6.7.

- What is the current version?
- How can I get a more current version? I have an account on
ftp.cisco.com, but it didn't seem to be there. Is the 3005 still a
current product?

Thanks!

[ Post a follow-up to this message ]

srp336@getcoactive.com wrote:
> I'm troubleshooting some problems with one of our 3005 concentrators.
> In looking into this, I noticed that the firmware is different
between
> the two, and rather old. One is running 3.1 and the other is running
> 3.6.7.
>
> - What is the current version?
> - How can I get a more current version? I have an account on
> ftp.cisco.com, but it didn't seem to be there. Is the 3005 still a
> current product?
>
> Thanks!

[ Post a follow-up to this message ]

4.1.7c is the latest version.  You'll need an account on Cisco's web
site to get it.

[ Post a follow-up to this message ]

mitchwell wrote:
> 4.1.7c is the latest version.  You'll need an account on Cisco's web
> site to get it.

Didn't even think of the website. I'm used to getting images from the
ftp site.

How do I verify that I have sufficient memory to upgrade the firmware?
Where is the amount of memory installed displayed?

Thanks!

[ Post a follow-up to this message ]

for IOS code, the memory requirements are usually listed when you do
the download.  I don't think there is a 3000 out there that doesn't
support the code on their web site.  They tailor the code to the type
of box, so it should be fine.

[ Post a follow-up to this message ]

on your 3005 go to Monitoring | System Status, you can check out the
memory there.
on the Cisco's website you will have special images for 3005 and you
can also check out the memory requirements before downloading the
latest code. the latest code is 4.1.7D

go to www.cisco.com -> technical support-> downloads -> security
software -> vpn software

[ Post a follow-up to this message ]