Forum Discussion
Intermittent System Outage returns.
I am creating a new topic since I marked the last one as having a solution.. My previous topic still has the same information, but I will give a new consolidated version of what is happening and the ...
Good morning folks,
Just received an update that the network adjustments to address this concern have been implemented. Please let me know if the intermittent connectivity persists for you today.
Hello Matt and ebjoew,
Just a quick heads up on this subject. Our engineers believe they have pinpointed this to one particular gateway and are currently investigating. We will provide you updates as they come through.
Thank you,
Amanda
It seems you like poking around and troubleshooting things as much as I do. But I think this issue is out of our hands! I am willing to guess that the issue may be with the Albuquerque, NM gateway, as that seems to be a common trend.
At least we have a great community here to allow us to easily do some arm waving for attention.
Thanks for the update! As always if I notice anything new which may help I will make sure to let you know.
I also see that not only are we serviced through the same gateway (Gateway ID 2 which is Albuquerque, NM) but we are both on the same beam (Beam ID 23 which covers much of Ohio where we are both located). Perhaps the issue is with Beam 23 of the satellite.
I certainly hope things pan out the way @Amanda said they are expecting. I am hanging a lot of hope on her statement. I was right on the very edge of terminating my use of HughesNet. I think their tech support people need to have their scripts updated such that when the tech support people cannot provide good resolution to a recurring problem, the issue gets reported to the upper levels of technical support much more quickly. Intermittent problems can be just as disturbing emotionally to end users as solid failures. Solid failures tend to get fixed quickly because they are much easier to diagnose but intermittent issues nag at you with little hope of being found. The tech support people don't really want to believe you it seems. It may be a cultural difference thing.
I am eagerly waiting for the all-clear update from @Amanda.
@Matt_Is_My_Name,
Of course, we have seen nothing more about any changes to the gateway that might resolve our issue and I am still having the dropouts taking place as often as ever, both short and long ones. If anything, they are getting more numerous. I expect that you are still having the dropouts as well.
Tier Level 4 Tech Support called me today. After reviewing my situation, they decided to ship me a new modem. I will report on any differences that makes when it arrives here in a few days. Based on the fact that we are both experiencing the same problem, that you have had both you radio and modem replaced without it being resolved, and I have already had my radio replaced, I am not too optimistic about a new modem taking care of my issues. Either way, it will eliminate one more piece of older equiipment and add to our information about where the issue truly lies. I will report back when I have the new modem running.
Personally, I am still rather expecting the gateway issue which @Amanda mentioned to be the true source of our issues. As I have noted before, not only are we both on the same gateway, we are both on the same beam of the satellite as well. We are both on Gateway 2 and Beam 23.
Saw something new in the event log. I have no idea what it means, but I figured I would share anyway.
05/29/2017 12:41:59 12305 4 1 Command initiated ranging: Range every rate in the trajectory table 05/29/2017 12:42:07 12802 2 1 Start Range Process Sym 512 Code 2 Process id 8 Reason NOC INITIATED Frame 376866550 Group 25 05/29/2017 12:42:13 12001 2 1 Uplink DOWN | Started on frame 376866551 | Current State Code is 12.8.2 | SQF=111 Symcod=6 IGID=25 05/29/2017 12:42:13 101 2 1 System StateCode DOWN | Started at 05/29/2017 12:42:08 | Current State Code is 12.8.2 | SQF=111 Symcod=6 05/29/2017 12:42:20 12803 2 1 Ranging Final State: Frame 376866817 Group 25 SymRate 512 Code Rate 2 MinEsNo 46 TargetEsNo 70 05/29/2017 12:42:20 12803 2 1 Ranging Final State: InitialEsNo 152 FinalEsNo 70 Final BackOff 144 Outcome SUCCESS - MET TARGET ESNO 05/29/2017 12:42:20 12504 3 1 AIS/CLPC Filter Reset due to Ranging 05/29/2017 12:42:25 12002 2 1 Uplink RECOVERED | Recovered on frame 376866835 | Outage Time 000:00:00:12 | Last State Code was 12.8.3 | SQF=111 Symcod=6 IGID=25 05/29/2017 12:42:25 102 2 1 System StateCode UP | Recovered at 05/29/2017 12:42:20 | Outage Time 000:00:00:12 | Last State Code was 12.8.2 | SQF=111 Symcod=6 05/29/2017 12:42:50 12802 2 1 Start Range Process Sym 4096 Code 2 Process id 9 Reason BASELINE RATE SET Frame 376867488 Group 26 05/29/2017 12:42:55 12001 2 1 Uplink DOWN | Started on frame 376867489 | Current State Code is 12.8.2 | SQF=112 Symcod=21 IGID=26 05/29/2017 12:42:56 101 2 1 System StateCode DOWN | Started at 05/29/2017 12:42:51 | Current State Code is 12.8.2 | SQF=111 Symcod=21 05/29/2017 12:42:59 12803 2 1 Ranging Final State: Frame 376867700 Group 26 SymRate 4096 Code Rate 2 MinEsNo 47 TargetEsNo 54 05/29/2017 12:42:59 12803 2 1 Ranging Final State: InitialEsNo 145 FinalEsNo 51 Final BackOff 85 Outcome SUCCESS - MET TARGET ESNO 05/29/2017 12:43:00 12504 3 1 AIS/CLPC Filter Reset due to Ranging 05/29/2017 12:43:05 12002 2 1 Uplink RECOVERED | Recovered on frame 376867718 | Outage Time 000:00:00:10 | Last State Code was 12.8.3 | SQF=112 Symcod=10 IGID=25 05/29/2017 12:43:06 102 2 1 System StateCode UP | Recovered at 05/29/2017 12:43:01 | Outage Time 000:00:00:10 | Last State Code was 12.8.3 | SQF=111 Symcod=10
