Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi,We recently upgraded our FWSM from version 2.3 to version 4.1, without the intermediate hop to a 3.x version first. We were advised by a Cisco representative that this intermediate upgrade to 3.x was no longer necessary.Overall, the upgrade appea...
Hi,We're about to upgrade our FWSM from software version 2.3 to 3.2, and probably straight to 4.1 to support a future project to implement VSS. We currently use Statseeker (2.8 and 3.3) to monitor all devices but the only information it seems to be ...
Hi all,Just after some opinions or, even better, experience.The web proxy server where I work currently exists within the organisations internal LAN structure (ie. traffic going to the proxy server from within the organisation does not cross the fire...
Hi all,Just upgraded a Cat3560 to IOS ver c3560-ipbasek9-mz.122-44.SE.bin and a Cat2960 to c2960-lanbasek9-mz.122-44.SE1.bin respectively. Just after upgrading I discovered there is a later release for each of these models. Now, however, I cannot g...
Hi all,Strange problem: Since last weekend I've noticed that the FWSM in our 6513 core switch is being power-cycled on an almost nightly basis at exactly the same time each time it happens (12:15am).The syslog message I receive first off is "Mar 28 0...
If the logging information you're after is typically also available via syslog you could send all of your alerts/warnings/etc to your syslog server. You could then employ a script, such as "swatch" for most *nix varieties, that will watch the log fi...
Hi KS,I'm planning to attempt the upgrade again this coming Tuesday (11-JAN-11).Given the trouble we had last time I'm somewhat hesitant to put 2.3 on the 'new' blade and rely on that as my fallback position as this could give me the exact same issue...
"I am also unsure of how you reloaded both the units.Did you copy the code onto both units.1. reloaded the secondary/standby2. once secondary came up you failed to it3. Then reloaded primaryIs this what you did or did you reload both units at the sa...
Hi KS,Unfortunately our MW was so short we didn't get an opportunity to do packet captures. The TAC were not involved in the upgrade process. Internal name resolution was working fine, but that's not saying much because the DNS servers are in the s...
We're going through the process of upgrading the proxy server hardware at the moment, but an important point that I left out is probably that we're 100Mbps to the desktop for all clients and that the speed of our internet connection is only 100Mbps a...
