Hi Christian, a quick test says its the negotiated speed, which is what you would expect.
The exact mechanism its worked out with tho is a bit of voodoo. Firstly I know they use a 1 or 2 second average which means it catches spikes that your interface counter will never see and that arent probably harmful. Heres what I get, see if you can figure how they work that % out :) FastEthernet0/1 is up, line protocol is up (connected) MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, reliability 255/255, txload 18/255, rxload 18/255 Half-duplex, 10Mb/s 30 second input rate 722000 bits/sec, 91 packets/sec 30 second output rate 723000 bits/sec, 94 packets/sec Interface Filter State Trap State Upper Lower Current Traps Sent --------- ------------- ------------- ------- ------- ------- ---------- Fa0/1 Forwarding inactive 15.00% 5.00% 9.21% 0 On Thu, Aug 02, 2007 at 10:30:53AM -0700, Christian MacNevin wrote: > Hello, > In 12.2SX, is storm control (as a percentage) definitely linked to the > negotiated speed/duplex of the port? Or is it based on the > hardware capability of the port? ie: will 15% on a gig port limit to 150Mb > regardless of negotiated speed? Or will it adjust to 15Mb > for 100meg negotiated host? > Cheers > Christian. > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/