Re: Lots of red X's after firmware update

Author	All Replies
teledatatech Premium join:2001-11-23 Bucyrus, OH clubs: ·Embarq ·HughesNet Satellit.. ·Sprint Mobile Broa..	reply to teledatatech Re: Lots of red X's after firmware update --------------------------------------------------------------- System Level Diagnostics --------------------------------------------------------------- Monitoring interval THU JUN 11 17:15:07 2009 - THU JUN 11 18:15:08 2009 Problem(s) Detected [* - Triggering Statistic(s)] RTT Overall BAD Transport MARGINAL PEP BAD --------------------------------------------------------------- Transport Layer Diagnostic Statistics --------------------------------------------------------------- Outroute Type: DVB-S2-ACM Outroute Symbol Rate: 30(MSps) Outroute ACM enabled: Enabled Inroute AIS enabled: Enabled Status MARGINAL Current SQF 68 GOOD No frame info 4444(5.61%) MARGINAL SMA Reset Error 1 INFO ACM MODCOD Mismatch (Higher) 33 INFO ACM MODCOD Mismatch (Lower) 4 INFO TX CODES: None --------------------------------------------------------------- Inroute Statistics --------------------------------------------------------------- Group ID Stream Ack Stream NAK Stream Error Rate NonStream Ack NonStream NAK NonStream Error Rate Active Time (s) Allocated Bytes Allocated Bitrate (bps) Bandwidth Allocation 30 2980 0 0.04 % 37 6 0.20 % 865 378920 3504 17.14 % 60 2755 0 0.03 % 85 5 0.01 % 972 348044 2864 14.47 % --------------------------------------------------------------- PEP Diagnostic Statistics --------------------------------------------------------------- Status BAD LLRTT (in msec) for bb 2 2465 BAD * Flow control in effect YES BAD --------------------------------------------------------------- Traffic Activity --------------------------------------------------------------- Interface Bytes Packets Rate Activity LAN Rx 774.56K 6599 1.72Kbps TYPICAL Uplink 113.42K 1900 0.25Kbps IDLE Downlink 8.62M 27984 19.16Kbps TYPICAL LAN Tx 6.04M 7237 13.42Kbps IDLE --------------------------------------------------------------- Web Traffic Response Time Statistics --------------------------------------------------------------- Monitoring interval THU JUN 11 17:15:07 2009 - THU JUN 11 18:15:08 2009 --------------------------------------------------------------- Response received from TPS \|Response received from prefetch cache \|Response received from bypass proxy (interactive) \|Response received from bypass proxy (bulk) \|Response received from web/proxy server (interactive) \|Response received from web/proxy server (bulk) \|Response received from other \| URLs: 511 \|URLs: 134 \|URLs: 0 \|URLs: 2 \|URLs: 0 \|URLs: 0 \|URLs: 0 \| Interval Start(ms) Interval End(ms) URLs(%) \|Interval Start(ms) Interval End(ms) URLs(%) \|Interval Start(ms) Interval End(ms) URLs(%) \|Interval Start(ms) Interval End(ms) URLs(%) \|Interval Start(ms) Interval End(ms) URLs(%) \|Interval Start(ms) Interval End(ms) URLs(%) \|Interval Start(ms) Interval End(ms) URLs(%) \| 0 2000 4(0.78%) \|0 100 128(95.52%) \|0 1000 0(0.00%) \|0 5000 0(0.00%) \|0 1000 0(0.00%) \|0 5000 0(0.00%) \|0 1000 0(0.00%) \| 2000 4000 426(83.37%) \|100 200 2(1.49%) \|1000 2000 0(0.00%) \|5000 10000 2(100.00%) \|1000 2000 0(0.00%) \|5000 10000 0(0.00%) \|1000 2000 0(0.00%) \| 4000 6000 51(9.98%) \|200 300 0(0.00%) \|2000 3000 0(0.00%) \|10000 15000 0(0.00%) \|2000 3000 0(0.00%) \|10000 15000 0(0.00%) \|2000 3000 0(0.00%) \| 6000 8000 18(3.52%) \|300 400 0(0.00%) \|3000 4000 0(0.00%) \|15000 20000 0(0.00%) \|3000 4000 0(0.00%) \|15000 20000 0(0.00%) \|3000 4000 0(0.00%) \| 8000 10000 5(0.98%) \|400 500 1(0.75%) \|4000 5000 0(0.00%) \|20000 25000 0(0.00%) \|4000 5000 0(0.00%) \|20000 25000 0(0.00%) \|4000 5000 0(0.00%) \| 10000 12000 1(0.20%) \|500 600 0(0.00%) \|5000 6000 0(0.00%) \|25000 30000 0(0.00%) \|5000 6000 0(0.00%) \|25000 30000 0(0.00%) \|5000 6000 0(0.00%) \| 12000 14000 1(0.20%) \|600 700 0(0.00%) \|6000 7000 0(0.00%) \|30000 35000 0(0.00%) \|6000 7000 0(0.00%) \|30000 35000 0(0.00%) \|6000 7000 0(0.00%) \| 14000 16000 2(0.39%) \|700 800 0(0.00%) \|7000 8000 0(0.00%) \|35000 40000 0(0.00%) \|7000 8000 0(0.00%) \|35000 40000 0(0.00%) \|7000 8000 0(0.00%) \| 16000 18000 0(0.00%) \|800 900 0(0.00%) \|8000 9000 0(0.00%) \|40000 45000 0(0.00%) \|8000 9000 0(0.00%) \|40000 45000 0(0.00%) \|8000 9000 0(0.00%) \| 18000 4294967295 3(0.59%) \|900 4294967295 3(2.24%) \|9000 4294967295 0(0.00%) \|45000 4294967295 0(0.00%) \|9000 4294967295 0(0.00%) \|45000 4294967295 0(0.00%) \|9000 4294967295 0(0.00%) \| -- Hughesnet G-17/1070 With Backup Sprint Service
	to forum · permalink · · 2009-06-12 06:17:16 ·
grohgreg Dunno. Ask The Chief join:2001-07-05 Dawson Springs, KY 2 edits	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
	to forum · permalink · · 2009-06-12 08:44:24 ·
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.
One more too @direcway.com	to forum · permalink · 2009-06-12 11:29:35 ·


Friday, 04-Dec 02:22:47	Terms of Use \| Privacy Policy \| Hosting by www.nac.net - DSL,Hosting & Co-lo \| feedback \| contact over 10 years online! © 1999-2009 dslreports.com. republican-creole page compression OFF