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.
hello, looking for a low latency switch from Cisco for high-frequency trading network environment. But noticed the Nexus 3500 is End-of-Sale, any other series could be the candidate? Btw, currently, we are using Arista 7150S which latency is ~35...
Hi, Model is : WS-C3560X-24T-SLicence is :Index 1 Feature: ipservicesPeriod left: 8 weeks 4 daysLicense Type: EvaluationLicense State: Active, Not in Use, EULA not acceptedLicense Priority: NoneLicense Count: Non-CountedIndex 2 Feature: ipbasePe...
hello when asked for DMVPN configuration(phase 3):Ensure spokes establish OSPF adjacency through a tunnel , and without attempting to elect any DR ,does it mean Network type should be point-2-Multipoint ?and if Yes ? Why? thanks and regar...