I have one cat6513, its supervisor engine (720) crashed few times in last 6 years. and few months before it crashed, you can feel network slowness in related network, but, no any eventance related to the box, no error log, no perfermence by show cpu/mem, no packet drop/overload in interface.
at the crashing time, you still have no error messages on box, only crash dumping file, cisco tac checked crash dumping, and most time, the file comments as software caused.
at the crashing time, there is no traffic in/out, perfermence is very low, but, if you run "show tech" it take very long time ( more than 45 minutes), I have no chance to finish the "show tech" before reload.
I have all rest cat6500s with no any problem similar like this one.
We had replaced supervisor modules, but the problem comes back, not frequetely, but, properly a year later.
Is any possible there is not supervisor module has problem, but, the other part? such as chasis?
Is any possible I can monitor this issue than just feel it and guess it may have problem soon?
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...