At 11:18 AM 1/9/02, NK Sat wrote: >Do we have any links or writeup to understand how the load 10/255 txload >and rxload are calculated in the "show interface serial " command.... > >i wanna understand what 10/255 means on a T3.
Another case of lazy programming! ;-) Instead of showing you the load as a percentage (a fraction of 100), like every other tool does, Cisco displays load (and other values) as a fraction of 255. You'll get used to it.... So, 255/255 would be a saturated link. You're using 100% of it. 10/255 means you are using about 0.04 (4%) of your T3 45 Mbps capacity. This assumes that the bandwidth command is set to correctly reflect the 45 Mbps capacity of the circuit. As is the case with most such values, Cisco makes the calculations as an exponential average over 5 minutes. The software calculates a sample every 5 seconds and provides a moving average over a 5-minute period. A moving average incorporates feedback from previous samples into the current result. The most recent sample is weighted slightly more than previous samples, but because there are so many more previous samples, they contribute heavily to the result also. The weighting decays exponentially for each previous sample, but in 5 minutes, there are 60 previous samples, so they are still significant. The goal is to avoid skewing the result too much if the 5-second sample happens to take place when someone is downloading a huge MP3 file, for example, or when nobody was doing anything on the network for whatever reason. That's probably way more than you wanted to know! ;-) Priscilla >Thanks > >_________________________________________________________________ >Send and receive Hotmail on your mobile device: http://mobile.msn.com ________________________ Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=31448&t=31400 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
