Input queue drops are almost always indicative of process level traffic happening. You may be able to dump some of the frames utilizing the "sh buffers input-interface packet" to see what those packets are. Then you can decide on how to reduce that traffic at process level. Some platform implementations thorttle the incoming packet rate if the process level input queue is overrun.
As for the tx/rx load get a sniffer trace or try Netflow to see what the traffic is.
1) When I issue "sh buffers input-interface packet" I gen no output.
2) As I mentuned earlier this is not a case of classic production network but rather a Dev-QA testing network. This VSS aggregates 6 fully populated 7018 switches which serve hundreds of servers and storage systems. Its not that I can say them... "hmmm, your test is suffocating my switch, please stop it".
I know that they are "killing" their systems in this lab. This is the purpose of this lab.
My primary goal is to optimize anything I can in order not to disturb thier tests.
Making the hold-queue larger solved the queue drops and throttles but it didn't solved the high tx/rx load.
I'm thinking to devide this Vlan to several smaller Vlans in order make use of several tx/rx load (queues)
[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...