SatSig topic:

What exactly is a NonStream Error Rate?

(Read 13743 times)

Oct 13^th, 2009 at 12:50pm

Like the title says what exactly is a nonsteam error rate and what causes it?

Network Time: TUE OCT 13 11:48:00 2009
------------------------------------

Adapter Main Statistics:
------------------------
Signal Strength.............. 94 Stream Msg-Ackd/Nakd........ 101638/84
Flags............... 0x00000000 NonStream Msg-Ackd/Nakd..... 1226/547
Stream Error Rate....... 0.08% NonStream Error Rate....... 30.85%
UpTime (d:h:m:s).. 000:04:43:20 Aloha Starts................ 875
WakeUp Aloha Starts.......... 9 Ranging Starts.............. 0
Transport Alarm Bit..... 0x0000 Frames Received............. 1779130
Addresses Open............... 7 Frame Errors: CRC/Bad Key... 0/0
Carrier Info....... 007:E:11272 Miscellaneous Problems...... 403
Rate Code........ 256k 4/5 (TC) No Receive Outroute Lock.... 32
Inroute Group................ 1 No FLL Lock................. 427
Inroute...................... 9 No Network Timing Sync...... 648
IQoS ID...................... 4300 Current Modcod............... 8-PSK 8/9 (16)

Ranging Reason: Ranging Done
Inroute Group Selection: Ranged at inroute rate selected by IQoS

Receive Status: Receiver operational. (RxCode 5)
Transmit Status: Transmitter ready. (TxCode 8)

Oct 13^th, 2009 at 6:24pm

Your stream error rate at 0.08% is rather good. Greater than 1% is marginal and 5% is bad.

What is also significant is that you are using 256k 4/5 (TC) for your uplink so not stressed at all. If it was as low as rate 1/2 for long time then marginal (e.g. heavy rain).

Note that the count stats are cumulative, so repeat the record after an hour and note the changes. Large numbers of errors may be accumulated during initial acquisition immediately after power on and during occasional ranging activity.

I am not sure what non-stream errors are but I suspect that these refer to no-acknowledgement for ALOHA bursts. My, rather simplified, guess is as follows:

Your TDMA uplink is a dynamic shared system, maybe with 50 sites sharing. If you upload a large file the process up may involve one, or more if necessary, random ALOHA request bursts, which may collide and be lost, to request a time slot allocation for the file transfer, followed by 100 stream bursts in an allocated block of time slots. A moderately high no-ack rate for ALOHA bursts is normal. Very old (1970's) TDMA used only ALOHA bursts and the satellite capacity could not be increased above 25-30% efficiency due to burst collisions. Modern TDMA systems involve the hub allocating time slots on request to particular sites, when required, for the bulk of the traffic such as a file transfer, image download or VoIP phone call. Only a minority of traffic goes ALOHA since it is not sensible to preallocate time slots to all sites, otherwise the TDMA frame would be filled with mostly unused time slots.

There are endless variations on this theme with dynamic allocation of carriers, carriers varying in size, jumping into spare gaps across the transponder etc, all to try and get more used capacity out of the satellite with shared access.

Best regards, Eric.

Oct 13^th, 2009 at 8:05pm

In my experience, non-stream errors are of no concern whatsoever. To me, anyway. There aren't even any alarm triggers for non-stream errors, so I'm not sure why they're even listed. My guess is comes close to Eric's; in that they may be related to bit errors experienced when your modem requests a seat at the table, and is told to wait for the second serving.

//greg//

Oct 14^th, 2009 at 5:07am

Okay, so the nonstream error rate is nothing to worry about.

Well something is up with this thing because I have the HX Business 1000 Premium with one user right now and cant even stay connected to Yahoo Messenger. I always get web acceleration errors.

I just ran a speedtest, with one PC and the system has not been used all night.

80 kbps down
200 kbps up

Oct 14^th, 2009 at 6:45am

anyone used pingtest.net yet?

I ran a test and scored an F.

My site is not throttled, I am using one PC connected directly to the modem and this is first thing in the morning after it has not been used since 10pm the night before.

I understand satellite internet has a high latency, but whats up this this packet loss? Is that why web pages never fully load correctly?

Oct 14^th, 2009 at 8:00am

Quote:

I always get web acceleration errors.

Tell WAFA or Bentley Walker about this, so that they know about it and can investigate. Sounds to me more like a software problem rather than a satellite radio link problem.

Regarding ping tests it is best to run these yourself from a Command Prompt window (Start, All Programs, Accessories).
Try ping to an IP address e.g. ping 85.148.42.6 -t to check routing.
Try ping to a url e.g ping www.satsig.net -t to check your DNS is correct/working. Do control C to stop so you don't waste your bandwidth or mine.
tracert 85.148.42.6 might reveal where a routing failure exists in the internet.

Best regards, Eric.

Oct 14^th, 2009 at 9:49am

Quote:

Tell WAFA or Bentley Walker about this, so that they know about it and can investigate. Sounds to me more like a software problem rather than a satellite radio link problem.

Best regards, Eric.

I have told my provider (reseller)

Oct 14^th, 2009 at 11:00am

Dear Sir

Please email our support team support@BentleyWalker.com with your modem ESN number as well ..thank you

Oct 15^th, 2009 at 7:21am

Pinging www.satsig.net [85.158.42.6] with 32 bytes of data:
Reply from 85.158.42.6: bytes=32 time=826ms TTL=244
Request timed out.
Request timed out.
Reply from 85.158.42.6: bytes=32 time=820ms TTL=244
Reply from 85.158.42.6: bytes=32 time=770ms TTL=244
Reply from 85.158.42.6: bytes=32 time=849ms TTL=244
Reply from 85.158.42.6: bytes=32 time=805ms TTL=244
Reply from 85.158.42.6: bytes=32 time=1405ms TTL=244
Reply from 85.158.42.6: bytes=32 time=768ms TTL=244
Reply from 85.158.42.6: bytes=32 time=955ms TTL=244

Ping statistics for 85.158.42.6:
Packets: Sent = 10, Received = 8, Lost = 2 (20% loss),
Approximate round trip times in milli-seconds:
Minimum = 768ms, Maximum = 1405ms, Average = 899ms

Tracing route to s55942006.adsl.wanadoo.nl [85.148.32.6]
over a maximum of 30 hops:

1    *    *    *    Request timed out.

2 658 ms 818 ms 679 ms 192.168.14.131

3    * 747 ms 839 ms 192.168.5.1

4 1509 ms 758 ms 771 ms 213-209-160-252.ip.skylogicnet.com [213.209.160.252]

5 1073 ms 839 ms 719 ms ge-1-1.r03.trn.ip.skylogicnet.com [88.202.127.25]

6 797 ms 699 ms 729 ms ge-1-3-0-0.r01.trn.ip.skylogicnet.com [88.202.127.18]

7 739 ms 1298 ms    *    xe-10-0-0-301.mil-cal-score-1-re0.interoute.net[84.233.225.141]

8 1296 ms 799 ms 699 ms ae2-0.fra-006-score-1-re0.interoute.net [89.202.146.90]

9 727 ms 939 ms 809 ms ae1-0.ams-koo-score-2-re0.interoute.net [84.233.190.49]

10 847 ms 1158 ms 2090 ms ae0-0.ams-koo-score-1-re0.interoute.net [84.233.190.1]

11    * 708 ms 817 ms ams-ix.euro.net [195.69.144.70]

12    * 726 ms 979 ms PC11.cr1-asd5.nl.euro.net [194.134.161.10]

13 772 ms    *    *    PC18.dr3-asd5.nl.euro.net [194.134.161.22]

14 809 ms 917 ms 799 ms V520.ar1-Asd-Dim.nl.euro.net [194.134.152.14]

15 857 ms 959 ms 769 ms s55942006.adsl.wanadoo.nl [85.148.32.6]
Trace complete.

Oct 15^th, 2009 at 7:24am

Quote:

Dear Sir

Please email our support team support@BentleyWalker.com with your modem ESN number as well ..thank you

I sent an email.

Oct 15^th, 2009 at 8:00pm

well something happened after I posted the last few post. My system is now "red" and shows a sig of 23, receiver not locked to signal and under "system info" it now says "not commisioned"

Oct 15^th, 2009 at 8:23pm

In view of the messages above I wonder if the hub has updated the software in your modem and is rebooting your modem?.

Under 30: No signal, wrong signal or poor receive signal.

Check connectors on LNB cable (most likely), the LNB cable itself, possible movement of the antenna, vehicle parked in the beam, LNB possibly faulty (rare). The LNB contains an oscillator with may jump in frequency or stop with temperature variations.

Wrong configuration settings can cause under SQF under 30. This arises prior to initial commissioning or after "reset to factory default" (rf command).

The satellite carrier may be off due to uplink teleport fault.

If the problem persists, call your service provider to verify that the outlink is still up working. If so, the problem is at your site.

Best regards, Eric

Oct 15^th, 2009 at 9:13pm

Im sure they changed something, they replied to the trouble ticket and said they updated some stuff and it should be working fine now, well its just the opposite.

The software date is a old one now, it is Oct 08 now, yesterday it was Aug 09. I checked the cables and the antenna, nothing has changed.

Oh and look at the time of my post, it has not worked all day and still does not work.

Oct 15^th, 2009 at 9:53pm

It sounds like your modem has been "reset to factory default" (command rf) This is sometimes necessary to clear obscure software corruptions.

You will need to go to the config screen and re-enter all the configuration parameters. The receive SQF should come good again. If this does happen, don't power cycle the modem or otherwise interfere with its activities during the initial several minutes of operation while it is reloading the latest software from the hub.

Best regards, Eric.

Oct 16^th, 2009 at 5:05am

All of the info is still in the config window. How do clear it and set it back to default?

Oct 16^th, 2009 at 9:18am

I've spoken with Bentley Walker and they will try to get in contact with you.

While you have no receive (SQF =23) the hub cannot see your modem or control it.

All I can suggest for now is:

SQF under 30: No signal, wrong signal, wrong config or poor receive signal.

Since you did not change the config to cause the fault I suggest you check connectors on LNB cable (most likely), damage to the LNB cable itself, movement of the antenna, vehicle parked in the beam and LNB possibly faulty (rare).

Best regards, Eric.

Oct 16^th, 2009 at 9:22am

Sir,

The changes applied by our team initially may relate specificially to the software image the modem is running and not the modems operational configuration.

As changes were applied on some platforms yesterday I would like to confirm your configuration.

My direct email is james@bentleywalker.com, please contact me directly with your ESN serial number and I will be able to provide further clarification. Please be assured of our full attention.

Oct 16^th, 2009 at 9:34am

I sent you an email James. Thanks.

Oct 17^th, 2009 at 6:14pm

It is back up and running now after 2 days of no service. So at least it works now, I am still getting the Web Acceleration errors.