how-to block ads
|
|  
grohgreg
Dunno. Ask The Chief
join:2001-07-05
Dawson Springs, KY | Re: Lots of red X's after firmware update Click on one of the Xs for amplifying statistics, which will at the same time identify the specific fault that triggered that particular X
//greg// | |
| | |
grohgreg
Dunno. Ask The Chief
join:2001-07-05
Dawson Springs, KY
2 edits | 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
| Re: Lots of red X's after firmware update 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. | |
| 
Nimblewill
join:2007-08-17
Dahlonega, GA
| I'm on 91 West/1070 also. I get the red X's on RTT about the same times as you. On the Pro Plan my speeds have been great for the last couple of years. Now the speed starts dropping mid morning to about 300 - 500 all day.
If things don't improve, I will change plans hoping to get on another transponder.
Drew | |
| | | 
yolarry
join:2007-12-29
Creston, WV | Re: Lots of red X's after firmware update I dont see why you still have hughesnet when you have unlimted internet from Sprint?
I rather user Sprint cancel Hughesnet. | |
| | Brassua
join:2004-05-17
Rockwood, ME
1 edit | said by teledatatech :I will add that the modem upgrade to the HN7000S was a downgrade IMO. The DW7000 was assigned to G-17/990 and speeds were consistent at around 700 down 100 up. (Home Plan) after the "upgrade" and moved to 1070 speeds are like this: Looks like I followed you from G17/990 to G17/1070 with the somewhat same results except I came from the Pro plan to ProPlus.
--
HughesNet HN7000S ProPlus | G17/1070Mhz | .98m dish 2-watt X-mit | |
| | | | | | | Brassua
join:2004-05-17
Rockwood, ME
| Re: Lots of red X's after firmware update Yes I am getting them also, I've only been with the new HN7000S on G17/1070 since yesterday afternoon and both yesterday and today starting at 5 PM until about 9-10 PM I get red X's in the RTT category. I checked on every X there and and they all show flow control YES! 
You know I wouldn't mind as much if this didn't start until say...9 PM and ended at 2 AM.  I wonder if should complain, I mean if you are getting nowhere with them. I really hate having to call them, I remember having to years ago, it wasn't a fun call!
--
HughesNet HN7000S Pro+ | G17/1070Mhz | .98m dish 2-watt X-mit | |
| |
grohgreg
Dunno. Ask The Chief
join:2001-07-05
Dawson Springs, KY
3 edits | They're wrong. The problem is NOT at your end and there IS something they can do about it. The distinction is that it's not that they can't do anything - it's that they typically won't. I say this because getting moved to a less crowded gateway is nearly impossible - unless you're a member of the Obama administration.
Ordinarily you could tell them that your neighbor has begun an addition to his house that will soon block your line of site with G17. Repointing to another satellite automatically includes a gateway change, but even then it's a gamble - whether or not THAT gateway turns out to be just as overcrowded. Unfortunately - it's likely they've already entered this existing complaint into your account history. So the next dim bulb you try to use the line of site argument on - might get a little suspicious.
//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 | |
| | | Brassua
join:2004-05-17
Rockwood, ME
| Re: Lots of red X's after firmware update I'll be anxious to hear what they have to say, you might want to mention you are not alone and that there are others on the same Sat & Transponder with the same flow control slowdowns at roughly the same times if that helps any? 
--
HughesNet HN7000S ProPlus | G17/1070Mhz | .98m Dish w/2-watt X-mit | |
| | |
grohgreg
Dunno. Ask The Chief
join:2001-07-05
Dawson Springs, KY
1 edit | Re: Lots of red X's after firmware update said by teledatatech :Gotta love those 0 uploads Where are you testing? Cuz if those results are not from Hughes own test site, they won't be accepted as valid by tech support
//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 | |
| | SlyBoots
join:2001-12-10
La Grande, OR
1 edit | said by teledatatech :I have also been logging my speed tests just in case. These are tests from today after I got home Date/Time Down(kbps) Up(kbps) 06/17/2009 21:12:12 255 0.0 06/17/2009 21:05:21 249 0.0 Gotta love those 0 uploads looks an awful lot like mine, but unlike others in this thread, most all of my red X's were in uplink/uplink queuing with an occasional one in TCP,DNS or LAN.... 5hrs to upload a 25mb data file is just ridiculous.
Recently found out Charter HSI is now available in my area so I'll be switching to their 10Mbps service in a couple weeks...
Until these uplink issues hit; Hughes had served me well for 3 years. If I did a review I'd probably give them 3.8/5 | |
| | Xtreme2damax
join:2007-03-21
| Despite there being no change in speed, browsing seems or is dramatically slower when they pushed this new update.
Browsing itself is like a chore, taking forever to load pages and often times the pages don't fully load due to loading so slow.
Even during the free time my normal download speeds fly, but browsing is painstakingly slow as if I am browsing on a fap'd connection despite not being fap'd.
I am getting page timeouts all over the place usually rendering the generic can't connect to server error in most browsers.
I usually have to reload the page, but takes forever to load a web page.
Something in this update seems to have dramatically impacted browsing speed during all hours of the day, I've also noticed the firewall is enabled at the NOC where it wasn't enabled in the past.
--
»www.xtemu.com/forum/index.html
»www.xtemu.com/forum/portal.html
| |
| | 
wa5sox1
join:2007-07-09
Vanderwagen, NM
1 edit | Re: Lots of red X's after firmware update Exactly what I'm experiencing as well. But I started noticing this two days 'before' the update, when in System Info my 'Inroute Group' used to be 11, now toggles between Inroute Group 31 and 41, which are the ones assigned to the 512 rate code on the gateway/satellite I'm on. .. When on 31, things seem okay, but when on 41, transmit failures are high. Main adapter stats usually show a 2% or so failure rate when on 41, but within the five minute windows, they can be as high as 11%.
And, same on the timeouts. Timing applications are not functioning as they should, and lots of "Can't Connect to Server" and "Web Acceleration Client Error, Suspect Recent Satellite Outage". ... Browsing is slow, even when a speedtest says it should be okay. .. In advanced, I am noticing a 'Bad' in "Uplink Packets Received" much of the time, as well as in RTT, and never had this before. ... The Firewall appears to be truly enabled now. It used to say Enabled, but in Advanced would say "Disabled" .. now says (Under Gereral Config) "Bad fragment check: Enabled" and under "Policy Stats":
ACL Statistics
--------------
ACL is Enabled from the NOC Side
Total num of valid rules: 2
Total num Packets Received: 3001756
Total num Packets Dropped: 0
-----------------
Flow Control is usually on from 12PM - 12AM Eastern, which is much longer than it used to be on. I even saw it kick in last night at about 3AM Eastern. .. Thus far, modem has been replaced, along with tria and all cables. Tech was sent out and after witnessing what was going on said "It's not you, it's them", then commented on how strange it was to have NO transmit errors on one Inroute Group, and so many on another. ... Did your Inroute Group change as mine did? When browsing, if it seems snappy, check your Inroute Group, and when it's sluggish, check again to see if it's changed. .. Clear stats and keep an eye on the number of failed transmissions. ... If this problem is related to the Software Update, Inroute Group change(s), Firewall now being on, or whatever, they need to re-evaluate their changes and get things back to normal (which was bad enough).
Also, in Diagnostics, getting Bad or Marginal much of the time in "TCP messages retxed". Some of this may be related simply to the satellite/gateway I'm on (no ACP running, etc.), but it sure seems others are experiencing much of what I am since the "changes."
--
G25(93W)/1247H-H/SOHO/.98 2Wt/Gateway 66.82.159.144 | |
| | | | | | |
wa5sox1
join:2007-07-09
Vanderwagen, NM
3 edits | Re: Lots of red X's after firmware update said by teledatatech :said by wa5sox1 : ... Did your Inroute Group change as mine did? It does seem my group does change and when it is on a certain group, things operate better. Right now, it shows Inroute Group................ 30 Inroute..................... -1 When I see a -1 on the Inroute, it is very slow. like it has been. RTT checks are still there and started today at about 3 PM Now click on General and clear stats and keep an eye on the Ack/NAck percentage and see if you have a lot of failed transmissions. When my Inroute Group was 11, my percentage was ALWAYS 0.01% or better. .. Just replying here triggered the a red X in TCP Messages Retxd of 53(18.73%) BAD ***
Maybe it is overcrowding, but something has sure changed, and for me it changed overnight. When system is idle, all I see is "Good" for all categories in Diagnostics (with the exception of Uplink Packets Received, where is shows either a bad or marginal). ... Prior to these changes, at ALL times everything was GOOD, even when browsing with Flow Control ON. At this time, I see so many Bads and Marginals, many times not enough to trigger an asterisk..all this started for me on May 17, when system went down in the wee hours of the morning. I called and was told it was a "Scheduled Maintenance Window" .. and after it was over, the new Inroute Group(s) followed by the Software Update on the morning of May 20. .. However, noticed the increase in failed transmissions on the 17th, when the Inroute Group was changed.
I apologize, it was the Inroute Groups that changed, along with the "inroute" too. But when I'm on the 41 inroute group, LOTS of transmit failures. 31 and the system performs nicely. ... Keep an eye on your "Inroute Group" and see if it ever changes.
--
G25(93W)/1247H-H/SOHO/.98 2Wt/Gateway 66.82.159.144 | |
| | |
wa5sox1
join:2007-07-09
Vanderwagen, NM
1 edit | Re: Lots of red X's after firmware update About the same here. Though I've seen only one red in Downlink, but I don't recall what the trigger was. When you click on one of the Downlink reds, what do you see? Any signal strength change at these times?
Last night I was on Inroute Group 31, the good one, and had over 500,000 transmissions with a Stream Error Rate of 0.01. Not the case when on Inroute Group 41 though, when it can read over 2% at times. .. HughesNet will say an error rate of up to 10% is acceptable (no it's not whan conducting online business!!), but in Diagnostics (the five minute windows), even a percentage of 1% will show up as a BAD (and I've seen mine as high as 7% within those windows when on Inroute Group 41). ... Your 1.15% represents the overall average. I think that if you click on some of the five minute windows, you will find it's much higher than 1.15% at times.
Seems they threw several changes at us at one time. The Inroute Group scheme, the Firmware Update, and the Firewall Enabled (for real). Something is awry, and I hope they know it. .. When I first called about the transmission failure problem, they said it must be my transmitter. When it continued, must be the modem. EVERYTHING has been replaced here, so as the tech said, "It's not you, it's them."
--
G25(93W)/1247H-H/SOHO/.98 2Wt/Gateway 66.82.159.144 | |
| | |
wa5sox1
join:2007-07-09
Vanderwagen, NM
1 edit | Re: Lots of red X's after firmware update said by teledatatech :I sure hope they know there is a problem . Probably it's just a fluke, but it sure has seem to have went downhill after the new firmware. I used to have all green checks in the hourly diagnostic screen, but right now I have a lot in the Download. This must be the trigger Tx SACKs 153(4.09%) BAD *** -------------------------------------------------------------- Since support seems to be overwhelmed at this point, I would hope they are working on it. In the 6 or so years of Hughes service This is about the worst I've seen. Another issue I seem to have since the update is, a lot of DNS errors and pages not loading completely. Let us know when/if tech support returns your call. I sure miss the "Sea of Green" in Diagnostics, and when clicking on a Green, everything saying "Good", without all the "BAD" and "Marginals" I'm now seeing. .. Ordinarilly I would associate this with overcrowding, but this happened overnight, with the new Inroute Group change(s) and the Firmware Update.
--
G25(93W)/1247H-H/SOHO/.98 2Wt/Gateway 66.82.159.144 | |
| | Xtreme2damax
join:2007-03-21
| I am really getting sick of this crap, no use in calling worthless Indian support that is nothing more than a joke.
I'm no sure if there is a problem, or if this was an intentional move on part of Hughesnet. All I know is that these problems magically appeared after the firmware update.
If there is a problem it doesn't seem like they are acknowledging it, and are taking their sweet time to fix it.
--
»www.xtemu.com/forum/index.html
»www.xtemu.com/forum/portal.html
| |
| |
wa5sox1
join:2007-07-09
Vanderwagen, NM
| Well, was online last night when the modem reset. And, here's what it says in the reset log .. back to Version 5.6.1.35!! Hope this restores things back to normal for many who have been suffering through the new release. .. It may take a while to take care of everyone, but there has to be a reason to "pull" the new software.
____________________________________________________
Entry Number 0:
----------------------
Time of Reset : FRI JUN 26 08:03:31 2009 [GMT]
Asserted at : t=tDownload /cm_data/pessd/rem2/sdl2/filecollection.cc#240:
Reset Type : Valid Software Reset
Reset Reason : New software downloaded. (Current Image: 5.8.0.49, New Image: 5.6.1.35)
--
G25(93W)/1247H-H/SOHO/.98 2Wt/Gateway 66.82.159.144 | |
| | Xtreme2damax
join:2007-03-21 | Re: Lots of red X's after firmware update Unfortunately I still have 5.8.0.49 so I am seeing the Dns errors, page load issues with incomplete loading of pages, and extremely slow browsing.
I hope they fix this soon.  | |
| | | |
wa5sox1
join:2007-07-09
Vanderwagen, NM
| Now that they have rolled back the firmware, I believe that they need to do some further work insofar as changing the "Inroute Group". .. It was before the firmware update (the new one) that the new inroute groups changed for me..just two days before the release of the new firmware. .. I see I still have two Inroute Groups..one being 31, which yields very few transmit failures, to 41, which I have a lot of problems with. 31 averages 0.01% or less failure, whereas 41 is sometimes up to over 3%. In the five minute windows, when on 41, failure rate is sometimes as high as 9%. .. It's almost as though, prior to release of this latest firmware, they had to "plow the field" so to speak, for new inroutes to accomodate the new firmware. .. Now that they have rolled back the firmware, I sure hope they roll back the inroute group change they did. ... Prior to all this starting, my Inroute Group was always 11, with VERY few transmit failures.
--
G25(93W)/1247H-H/SOHO/.98 2Wt/Gateway 66.82.159.144 | |
| | | |
|
·
·
·
