Cisco TAC has put together a list of router issues that are commonly perceived to be due to a hardware failure, but can normally be fixed more quickly without replacing anything. While some of these may in fact be due to hardware failures, it doesn't usually make sense to start with that assumption. Save yourself some time by checking more common causes first.
#4 A module or interface card is unrecognized. If the IOS version is too new, or the hardware is otherwise unsupported by the software, modules may not be seen. This is almost always a mismatch between the software required and the hardware installed.
In additional, failure to save the configuration after a change is also fairly common.
#6 Errors reported in show interface output. Most errors are either normal, but unusual conditions (drops, e.g.) or due to an external cause like incorrect clocking, noise, or even a marginal cable. Rule those out first.
#7 Wrong version loaded, or failure to completely boot. Again, the config-register can easily cause unexpected behavior. Check the config-register and boot system commands, and beware of relying on the system to boot the first image in flash.
I'm testing using Prime Infrastructure 3.5 to push out a new IOS to some Cat3850 switches. I have a Linux VM running SCP server acting as the intermediary. The job starts and I see the IOS file start to copy to the Linux SCP folder. Then job fails and I g...
Hi the community, I would like to have your point of view and suggestion about my problem. As you can see on the draw attached, I have static routing and dynamic routing for the same remote sites LANs.My goal is to replace the static routing by ...
We have a ISR4351-V/K9 as a voice gateway with all licensed pack included. For High Availability feature, we need another ISR4351-V/K9 router.So my question is, do we need to buy the hardware part with all license pack like existing one or just need to pu...