On Fri, Sep 20, 2013 at 12:19 PM, Ben Scott <mailvor...@gmail.com> wrote: > On Fri, Sep 20, 2013 at 2:12 PM, Kurt Buff <kurt.b...@gmail.com> wrote: >> No, the configuration of the L3 switch is stupidly simple ... > > Very odd that you're getting CPU spikes, then. > > You've done a "show log -a" on the switch right after the trouble > and found nothing helpful, I presume?
On the 3400cl, 'show log' says the same as 'sho log -a' - nothing of interest. Just that the monitor port has a high collision or drop rate once in a while, and that doesn't correlate with the network interruptions.. The other switches have more interesting entries, though none that seems to fit with a layer 2 loop or anything that would cause a spike in the CPU on the 3400cl - but I'm still investigating that. > Have you checked for firmware updates? Not yet - it's a worthy thought. >> ... the backup machine's trunk is LACP ... > > Is the backup machine behaving itself? LACP reconfiguration prolly > hits the CPU. STP will hit the CPU. But I'm shooting in the dark, > here. AFAICT, the backup machine is OK - it pulls a huge amount of data around midnight from the Exchange server primarily, and then nothing during business hours. > I'd call HP support. They know what magic commands to issue to get > the switch to cough up relevant debug info. > >> No ACLs, and two routes - a DG and a static to another switch for a lab >> subnet. > > I believe routing is done on ASICs with that model anyway. I'm going to take a look at the packets I've captured first, and see what I can, but HP support might well be the answer. Kurt
