DishNet: "Fragmentation Reassembly Errors"

[tedb3rd]

I pulled this from the modem diagnostics page with DishNet satellite service I just had installed this past Sunday. Can anybody translate this into a possible cause/solution? Looking at the hourly history I have 'X's across ALL the times for the 'downlink' category (for 'hourly history' and 'current hour history'). When I click the individual X, it shows this:

---------------------------------------------------------------
System Level Diagnostics
---------------------------------------------------------------
Monitoring interval Wed Dec 19 00:00:01 2012 - Wed Dec 19 01:00:01 2012
Problem(s) Detected [*** - Triggering Statistic(s)] Downlink
Overall BAD
Downlink BAD
---------------------------------------------------------------
Downlink Diagnostic Statistics
---------------------------------------------------------------
Status BAD
Fragmentation Reassembly Errors 1158(1.56%) BAD ***


The weather is clear so that's not a factor. All the other categories/times are check marks (OK) except for those where LAN shows an error when my router was turned off (so that's not concern). My speed varies. A few hours ago I was getting 5MB down. Later it was down to <1MB. Now it's about 3MB. Yesterday the download speed was measuring down in the KBs. I have called and they're sending out a tech this weekend. Any thoughts on what they might say? Is this normal?


And here's something else: My router is turned off at the time this was recorded. What's the deal with that amount of download when nothing is connected to the modem?
---------------------------------------------------------------
Traffic Activity
---------------------------------------------------------------
Monitoring interval: Tue Dec 18 21:00:01 2012 - Tue Dec 18 22:00:01 2012

Interface Bytes Packets Rate Activity
LAN Rx 0.00K 0 0.00Kbps IDLE
Uplink 6.37K 123 0.01Kbps IDLE
Downlink 471.25M 733944 1.05Mbps HIGH
LAN Tx 0.00K 0 0.00Kbps IDLE

Thanks for any insight that can be provided!

 

[stardust3]

Your router would not have anything to do with these stats. In a browser type in 192.168.0.1 into the address bar. This is the homepage for modem interface. At the top of the screen click on the "system status" link. You should have all green check marks, if not reset your modem & give a few minutes. Also from the same page you can see what signal is. If that doesn't work you probably will have to call for service.

 

[grohgreg]

My Downlink red Xs point to "fragmentation reassembly errors" as well. I'm reasonably confident it's similar to packet loss - except this is on the receive side. I don't doubt your speed is suffering too, mine's pretty consistently about 2/3 of plan speed. As stardust said, it would help to know your RX signal strength. And to help define it further, it would also help to know your Rate Code (from http://192.168.0.1/install.html) and your transmission error rate. To obtain the latter,

• go to http://192.168.0.1/cgi-bin/index.cgi?Command=1# .
• Locate Stream ACK/NAK.
• Add the two numbers together.
• Divide that sum into the NAK number for your transmission error rate.
• Multiply the rate by 100 for your transmission error percentage.

//greg//

 

[tedb3rd]

Stream ACK / NAK = 964936 / 1430

When I look at the grid with the Xs and checkmarks, all the downlinks are X's and everything else is all checks. Here is the full readout of the most recent log. I had Wildblue before but it never had the ability to get into the system this much (or at least I didn't know it)... Is it normal to have all the 'bad' status results?? They're sending out a tech on Saturday to take a look. ..I'm just trying to get a little knowledge so I'll have an idea if he comes out here and says "This is normal."

---------------------------------------------------------------
System Level Diagnostics
---------------------------------------------------------------
Monitoring interval Thu Dec 20 01:00:02 2012 - Thu Dec 20 02:00:02 2012
Problem(s) Detected [*** - Triggering Statistic(s)] Downlink
Overall BAD
Downlink BAD
Uplink GOOD
Association GOOD
TCP Acceleration GOOD
DNS GOOD
Inroute Protection GOOD
FAP GOOD
Web Acceleration GOOD
LAN GOOD
---------------------------------------------------------------
Downlink Diagnostic Statistics
---------------------------------------------------------------
Status BAD
SQF 103 GOOD
Over-the-Air Frequency 18410000 NOT AVAILABLE
Symbol Rate 25000000 NOT AVAILABLE
LNB Frequency 17350000 NOT AVAILABLE
Tuner Frequency 1060000 NOT AVAILABLE
Outroute ID 0 NOT AVAILABLE
Beam ID 48 NOT AVAILABLE
Key Load Errors 0 GOOD
Miscellaneous Errors 8 GOOD
GSE Packets Received 24444262 NOT AVAILABLE
Supported GSE Packet Errors 34(0.00%) GOOD
Fragmentation Reassembly Success 80597 NOT AVAILABLE
Fragmentation Reassembly Errors 2063(2.56%) BAD ***
Modcod Requests Sent 0 NOT AVAILABLE
Modcod Request Failures 0(0.00%) GOOD
Outage Duration (sec) 0(0.00%) GOOD
---------------------------------------------------------------
Uplink Diagnostic Statistics
---------------------------------------------------------------
Status GOOD
Stream ACKs 34518 NOT AVAILABLE
Stream NAKs 29(0.08%) GOOD
Outage Frames 277 NOT AVAILABLE
Outage Duration (sec) 12(0.33%) GOOD
Packets Sent 3771 NOT AVAILABLE
Bytes Sent 861024 NOT AVAILABLE
Uplink State Codes:
12.3.2 [Invalid timing packet information] occurred for 2 seconds
12.3.4 [Timing adjustment needed] occurred for 1 seconds
12.4.1 [Not receiving inroute group definition packets] occurred for 5 seconds
12.6.2 [No bandwidth allocation information available] occurred for 2 seconds
---------------------------------------------------------------
Association Diagnostic Statistics
---------------------------------------------------------------
Status GOOD
Association status UP GOOD
Num CMM Timeouts 0 GOOD
Num Keep Alive Timeouts 0 GOOD
Num Association Response Timeouts 0 GOOD
Num Reassociations 0 GOOD
Num Association Rejects 0 GOOD
Association Outage Time : 0 %
---------------------------------------------------------------
TCP Acceleration Diagnostic Statistics
---------------------------------------------------------------
Status GOOD
IPGW error detected NO NOT AVAILABLE
Backbone status UP GOOD
Flow control in effect NO NOT AVAILABLE
Tx SACKs 0(0.00%) GOOD
Rx SACKs 10(0.44%) GOOD
RSTs received 0 GOOD
RSTs transmitted 0 GOOD
Zero window rcvd 0(0%) GOOD
Zero window txed 0(0%) GOOD
TCP messages retxed 35(0.00%) NOT AVAILABLE
PEP Outage Time: 0 %
---------------------------------------------------------------
RTT Diagnostic Statistics
---------------------------------------------------------------
Status GOOD
LLRTT (in msec) for bb 0 1134 GOOD
---------------------------------------------------------------
DNS Diagnostic Statistics
---------------------------------------------------------------
Status GOOD
Timedout DNS queries 0(0%) GOOD
Invalid DNS queries 0(0%) GOOD
Invalid response rcvd 0(0%) GOOD
---------------------------------------------------------------
Inroute Protection Diagnostic Statistics
---------------------------------------------------------------
Status GOOD
Suspected Virus Packets Dropped 0 GOOD
---------------------------------------------------------------
FAP Diagnostic Statistics
---------------------------------------------------------------
FAP status GOOD
FAP in effect NO NOT AVAILABLE
Aggregated Bucket Remaining 19999 NOT AVAILABLE
Cos1 Bucket Remaining 19999 NOT AVAILABLE
Cos2 Bucket Remaining 0 NOT AVAILABLE
Cos3 Bucket Remaining 9999 NOT AVAILABLE
Cos4 Bucket Remaining 9999 NOT AVAILABLE
Cos5 Bucket Remaining 0 NOT AVAILABLE
Minimum Allowance Remaining 9999 GOOD
FAP Outage Time: 0 %
---------------------------------------------------------------
Web Acceleration[N] Diagnostic Statistics
---------------------------------------------------------------
Status GOOD
Mbx Rx Err 0 GOOD
Mbx Tx Err 0 GOOD
Mbx Socket Err 0 GOOD
---------------------------------------------------------------
LAN
---------------------------------------------------------------
Status GOOD
LAN Link Status OK GOOD
LAN Q allocation errors 0 GOOD

 

[grohgreg]

Transmission error rate of 0.15% is not critical. But not ideal either. Mine typically runs 0.01-0.03%. But the SQF of 103 is low. If you're lucky, the tech may be able to resolve this with a simple repoint

//Greg//

 

[tedb3rd]

Thanks for the feedback Greg. Is SQF like signal strength on sat TV? What's an optimal/acceptable reading for it?

 

[stardust3]

Thanks for the feedback Greg. Is SQF like signal strength on sat TV? What's an optimal/acceptable reading for it?

Signal varies from beam to beam. Looks like you're on 48, my area is in beam 40 & have seen it in the 160's + on the high end.

 

[grohgreg]

Correct. SQF is an acronym invented by Hughes that stands for Signal Quality Factor. In the military/commercial world, it's referred to as RSL (received signal level) or C/Kt (carrier to noise ratio). The unit of measure is the decibel (dBm). SQF on the other hand, is quantifiable only to whoever it was at Hughes who made it up. Short version; yes, it represents the strength of your incoming HughesNet signal.

As far as what that number should be depends upon your beam assignment plus the location of your dish within beam coverage. My red Xs for example, are apparently because I can't peak SQF any higher than 90. Other subscribers have reported SQF as high as 176. I should be able to prove this if I can get Hughes to move me to an adjacent beam, where I catch a glimpse of SQF 122+. So far Hughes can't seem to grasp the situation.

//greg//