Router Stats

[#1]

Hi, I just had a look at our router stats and noticed the output power up is 12.8 but is 0.00 down. When we was on o2 we had output power up of about 20. Is this normal for PN.
Also we get a lot of error seconds. In a week we can get well over 2000 and we dont use the internet very much, where as on o2 we used to get hardly any (2 or 3 a week at most). Should we ignore this as we are not getting problems as regards speed and stability, although we have lost about 2Meg since switching to PN, but we are not bothered about this as we still get over 10Meg
Thanks

[#2]

Hi there,
There is the odd drop on your line, as far as we can see:
<img src="http://community.plus.net/visualradius/generated/image13799411329527.png"/>
But they're not happening particularly often and if everything is working for you it's probably best to follow the old adage "If it ain't broke, don't fix it".
Of course if things do get worse or you change your mind please let us know (or even better submit a fault at http://faults.plus.net) and we'll get it looked into for you.

[#3]

Quote

output power is 0.00 down

AFAIK that indicates the equipment at the exchange is in energy saving mode. Not all exchanges have this feature.

Quote

Also we get a lot of error seconds

Which router were you using at O2? When O2 first started supplying the same routers as plusnet now use, theTG582n, a lot of people in the O2 forum noticed a big increase in the number of error seconds reported by this router. Don't know if this has been improved with firmware upgrades but I would treat the number of error seconds reported with some skepticism.
You could post your full stats to see what people here think.
I would also look in the routes log to check the number of resyncs.

[#4]

o2 router was a box2, never got offered a new one, even after 5 years!!!!!
As per previous post probably best to leave alone as its causing no problems.
Stats are as follows as you  suggested,
DSL Connection 
Link Information
   

Uptime: 0 days, 23:34:47

DSL Type: ITU-T G.992.5

Bandwidth (Up/Down) [kbps/kbps]: 1.255 / 13.107

Data Transferred (Sent/Received) [MB/MB]: 18,59 / 89,88

Output Power (Up/Down) [dBm]: 12,8 / 0,0

Line Attenuation (Up/Down) [dB]: 19,8 / 35,0

SN Margin (Up/Down) [dB]: 5,8 / 5,7

System Vendor ID (Local/Remote): TMMB / ----

Chipset Vendor ID (Local/Remote): BDCM / IFTN

Loss of Framing (Local/Remote): 0 / 0

Loss of Signal (Local/Remote): 0 / 0

Loss of Power (Local/Remote): 0 / 0

Loss of Link (Remote): -

Error Seconds (Local/Remote): 883 / 0

FEC Errors (Up/Down): 0 / 0

CRC Errors (Up/Down): 72 / 1.084

HEC Errors (Up/Down): 42 / 7.343


Thanks for the replys

[#5]

Quote

Loss of Framing (Local/Remote): 0 / 0 Loss of Signal (Local/Remote): 0 / 0 Loss of Power (Local/Remote): 0 / 0 Loss of Link (Remote): -

With all the above being zero I would ignore the error seconds figure.

[#6]

I think the output power reported as 0 is just it not being reported correctly.
As for the Errored Second count, 1 errored second = 1 second with 1 or more CRC errors (amongst other things). The number of CRC errors compared with the number of errored seconds looks reasonable, suggesting the CRC errors tend to crop up 1 or 2 at a time.

[#7]

If Thomson, I think ejs is right, but IIRC it cab be found by a telnet command. Unfortunately zee little grey cells are turning white, and the forgettery improves every day.