Cisco ASA 5510 IOS upgrade

If connected via ethernet, it should only take a minute or 2, but you might have to reboot the ASA after the image is transferred.  And dont forget to write to memory after the image is transferred

Hello Freya28,

I've just upgraded one today.

I upgraded the OS on mine in less than 5 minutes. The upgrade from one OS to another requires a reboot. To add the new licenses also requires a reboot. Each reboot on mine took about 30 seconds.


Regards,

InteraX

Here's the deal...

A few weeks ago, our firewall died.  Our solutions provider brought us a loaner.  The loaner was installed & configured in 5 hours.  The config was done manually, as they were two completely different kinds of firewalls....the dead one being a Watchguard Firebox, the loaner being a Cisco Pix.

Our provider sold us a new ASA 5510, which they stated should be very easy to configure, they said they should be able to copy the config from the pix to the ASA.  When we got the bill, they billed us 9-1/2 hours for the configuration.  They are trying to tell me the IOS upgrade and the SSL licensing added significantly to the billed time...

Is it just me, or are they trying to rip us off?

Thanks,
ddachauer

So tell us how you really feel, Les...don't beat around the bush like that!

:)

Now, I must admit that I am currently working a job where I will bill the client for 12 hours for a 2 hour job. Why? Attending multiple conference calls over a period of several weeks working with other vendors + Travel time + actual work. Driving over 200 miles in a rental car, staying in a hotel overnight, spend 2 hours on the real work, take client out to lunch,  then drive 4 hours to get home. But this is non-typical, highly complex install, and I'm good at what I do. Clients willingly pay for the expertise.

Took me exactly 15 minutes to setup a ASA 5510 this morning from scratch, and that includes taking it out of the box and waiting on my laptop to boot up... I admit it didn't include any VPN or SSL stuff, but . . . .

Sounds familiar...

The travel job, that is...

Drove over 120 miles one-way last week just to run a Sniffer to prove that one machine was not taking down the whole network. Long day.....but counted exactly 5 packets - MS Browse announcement - from that machine all day. Other machines, however, did not function as anticipated and at least I proved that "our" machine was not the problem, even though it was exhibiting some apparant lockups. Lockups were user error and in no way impacted the rest of the network.