grohgreg
Dunno. Ask The Chief
join:2001-07-05
Dawson Springs, KY
2 edits | reply to teledatatech
Re: Lots of red X's after firmware update
I don't believe the firmware update has anything to do with this. What I see is a classic example of shared (and clearly oversold) bandwidth. In this case, the PEP server at your NOC has been overwhelmed to the point that Flow Control was enabled. Note at the bottom left corner of that statistics page - under Interval Start. During that hour, only 4 of 511 URL requests were processed in under 2 seconds, 426 of them between 2 and 4 seconds, and 78 took between 4 and 16 seconds. By comparison, only 134 of the requested URLs were already in your modems cache. But note how much faster they are retrieved from your cache, than from the PEP server at your NOC.
//greg//
--
HN7000S/98cm Prodelin/2w Osiris/ProPlus - G16/1250H/Germantown - NAT 66.82.187.152/Gateway 66.82.25.10/DNS 66.82.4.12 and 66.82.4.8 - Firefox 3 - AV/Firewalled by NIS2009 |
|
One more too
@direcway.com
| said by grohgreg  :I don't believe the firmware update has anything to do with this. What I see is a classic example of shared (and clearly oversold) bandwidth. In this case, the PEP server at your NOC has been overwhelmed to the point that Flow Control was enabled. Note at the bottom left corner of that statistics page - under Interval Start. During that hour, only 4 of 511 URL requests were processed in under 2 seconds, 426 of them between 2 and 4 seconds, and 78 took between 4 and 16 seconds. By comparison, only 134 of the requested URLs were already in your modems cache. But note how much faster they are retrieved from your cache, than from the PEP server at your NOC. //greg// Likewise. When I had my Ku system, whenever there were RTT problems, it was coincident with the flow control being on and high bandwidth demand times on the transponder. So, I too would doubt any relationship to the software update. |
|
