b) Show proc cpu history :---Check since how long is the CPU been affected.
2- Check if there is any interface drops are been seen:
show interface | include line|drops ( Check if any vlan/interface are having input drops)
3- check if there are any STP issue:
show spanning tree detail
show spann det | in ieee|from|occur|is exec
show spann det | in executing | changes
show interface | include line|drops
show cef drop
show ip traffic >> Check the traffic utilization.
4- There are some internal debugging which would help to find out which packets ( from Src,dst) is hitting the CPU:
debug netdr capture rx <<<<( DEBUG OF NETDR IS VERY USEFULL TO CHECK WHAT PACKETSS ARE COMING TO CPU)
show netdr capture-packet >> This will give you the captured outputs were you can see the Src and dst . Then you can take the action with those src ip address guys to check why they are punting the traffic.
[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...