Routers are NOT susceptible to the Blaster worm (or any worm for that matter). The issue with not being able to view the config was probably that the router CPU was running high due to the increased traffic loads caused by the worm.
Well, technically they are not susceptible to the Blaster virus, but they can be affected by the high network load that can be placed on your network due to the blaster virus.Several of my customer's networks were brought to a near halt due to the DoS that was a direct result of the worm.
Just thought I'd throw a non-Cisco response in there :)
I did have a customer who had non-Cisco network equipment that was in the process of an upgrade. We expedited the upgrade and the Cisco equipment had no problem dealing with the ACLs that were added to block the virus from spreading; whereas the non cisco equipment was completely locking up.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...