cancel
Showing results for 
Search instead for 
Did you mean: 

'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Didn't get far with the first command:
Quote
c:\>telnet -f events##.log 192.168.1.254
Failed to create log file.
c:\>

Did better with the telnet log on command, although if hardly needs to be said that it means very little to me (especially references to 'Jan  1') :
{admin}=>syslog msgbuf show hist=enabled
<85> Jan  1 00:00:08 FIREWALL has been enabled
<4> Jan  1 00:00:16 KERNEL Cold restart
<85> Jan  1 00:00:24 FIREWALL event (1 of 1): created rules
<85> Jan  1 00:00:24 FIREWALL event (1 of 1): modified rules
<82> Jan  1 00:00:32 UPnP framework disabled
<85> Jan  1 00:00:32 FIREWALL has been enabled
<82> Jan  1 00:00:34 UPnP framework disabled
<82> Jan  1 00:00:36 UPnP framework disabled
<82> Jan  1 00:00:43 UPnP framework enabled
<85> Jan  1 00:00:43 FIREWALL level changed to Standard.
<85> Jan  1 00:00:43 FIREWALL event (1 of 1): deleted rules
<148> Jan  1 00:00:43 DHCS server up
<173> Jan  1 00:00:54 xDSL linestate down
<3> Jan  1 00:00:58 [ANTI_SPOOFD] (err) llist_getobject_at for ENV.ANTI_SPOOFD's
value failed
<37> Jan  1 00:01:06 LOGIN User admin logged in on TELNET (192.168.1.64)
<173> Jan  1 00:01:24 xDSL linestate down
<173> Jan  1 00:01:50 xDSL linestate up (ITU-T G.992.5; downstream: 9955 kbit/s,
upstream: 1217 kbit/s; output Power Down: 20.6 dBm, Up: 12.8 dBm; line Attenuat
ion Down: 37.0 dB, Up: 16.8 dB; snr Margin Down: 9.1 dB, Up: 6.4 dB)
<38> Jan  1 00:02:03 PPP CHAP Receive challenge from rhost bras-red9.sf (Interne
t)
<38> Jan  1 00:02:04 PPP CHAP Receive challenge from rhost PTN-AG02 (Internet)
<38> Jan  1 00:02:04 PPP CHAP Receive success (Internet)
<85> Jan  1 00:02:04 FIREWALL event (1 of 19): deleted rules
<132> Jan  1 00:02:04 PPP link up (Internet) [87.113.27.154]
<85> Jan  1 00:02:04 FIREWALL event (1 of 50): created rules
<85> Jan  1 00:02:04 FIREWALL event (1 of 32): modified rules
<37> Jan  1 00:02:34 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
<132> Jan  1 00:05:02 PPP link down (Internet) [87.113.27.154]
<85> Jan  1 00:05:02 FIREWALL event (1 of 1): created rules
<85> Jan  1 00:05:02 FIREWALL event (1 of 1): modified rules
<38> Jan  1 00:05:15 PPP CHAP Receive challenge from rhost bras-red9.sf (Interne
t)
<38> Jan  1 00:05:16 PPP CHAP Receive challenge from rhost PCL-AG05 (Internet)
<38> Jan  1 00:05:16 PPP CHAP Receive success (Internet)
<85> Jan  1 00:05:16 FIREWALL event (1 of 2): deleted rules
<132> Jan  1 00:05:16 PPP link up (Internet) [87.112.132.131]
<14> Jan  1 00:05:39 CONFIGURATION saved by TR69
<99> Nov 25 14:02:20 SNTP Systemtime update: time setting 00:05:56 > new time se
tting: 14:02:20
<102> Nov 25 14:02:20 SNTP Synchronised to server: 212.159.13.50
<84> Nov 25 14:02:34 IDS scan parser : tcp port scan: 74.125.230.127 scanned at
least 10 ports at 87.112.132.131. (1 of 1) : 74.125.230.127  87.112.132.131  40
  56  TCP 443->49192 [...R..] seq 2847270670 ack 0 win 0
<37> Nov 25 14:24:05 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
<102> Nov 25 15:02:20 SNTP Synchronised again to server: 212.159.13.50
<81> Nov 25 15:05:46 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 210.1
8.5.201 Dst ip: 87.112.132.131 Type: Time Exceeded Code: Time to Live exceeded i
n Transit
<81> Nov 25 15:36:45 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 212.5
8.132.42 Dst ip: 87.112.132.131 Type: Destination Unreachable Code: Host Unreach
eable
<81> Nov 25 15:48:58 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 194.4
4.136.13 Dst ip: 87.112.132.131 Type: Time Exceeded Code: Time to Live exceeded
in Transit
<81> Nov 25 15:51:28 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 79.17
4.72.66 Dst ip: 87.112.132.131 Type: Destination Unreachable Code: Port Unreache
able
<84> Nov 25 15:56:10 IDS scan parser : tcp port scan: 74.125.133.95 scanned at l
east 10 ports at 87.112.132.131. (1 of 1) : 74.125.133.95  87.112.132.131  40
  47  TCP 443->50487 [...R..] seq 1351864057 ack 0 win 0
<102> Nov 25 16:02:20 SNTP Synchronised again to server: 212.159.13.50
<81> Nov 25 16:42:45 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 41.35
.180.242 Dst ip: 87.112.132.131 Type: Destination Unreachable Code: Port Unreach
eable
<102> Nov 25 17:02:20 SNTP Synchronised again to server: 212.159.13.50
<81> Nov 25 17:31:24 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 110.2
44.3.227 Dst ip: 87.112.132.131 Type: Destination Unreachable Code: Port Unreach
eable
<102> Nov 25 18:02:20 SNTP Synchronised again to server: 212.159.13.50
<81> Nov 25 18:24:06 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 187.8
7.174.85 Dst ip: 87.112.132.131 Type: Time Exceeded Code: Time to Live exceeded
in Transit
<37> Nov 25 19:00:16 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
<102> Nov 25 19:02:20 SNTP Synchronised again to server: 212.159.13.50
<102> Nov 25 20:02:21 SNTP Synchronised again to server: 212.159.13.50
<102> Nov 25 21:02:21 SNTP Synchronised again to server: 212.159.13.50
<102> Nov 25 22:02:21 SNTP Synchronised again to server: 212.159.13.50
<37> Nov 25 22:17:06 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
<102> Nov 25 23:02:21 SNTP Synchronised again to server: 212.159.13.50
<102> Nov 26 00:02:21 SNTP Synchronised again to server: 212.159.13.50
<102> Nov 26 01:02:21 SNTP Synchronised again to server: 212.159.13.50
<102> Nov 26 02:02:21 SNTP Synchronised to server: 212.159.13.49
<173> Nov 26 02:30:08 xDSL linestate down
<85> Nov 26 02:30:08 FIREWALL event (1 of 2): created rules
<85> Nov 26 02:30:08 FIREWALL event (1 of 2): modified rules
<173> Nov 26 02:30:25 xDSL linestate down
<173> Nov 26 02:30:55 xDSL linestate down
<132> Nov 26 02:31:06 PPP link down (Internet) [87.112.132.131]
<173> Nov 26 02:31:21 xDSL linestate up (ITU-T G.992.5; downstream: 9142 kbit/s,
upstream: 1220 kbit/s; output Power Down: 20.6 dBm, Up: 12.7 dBm; line Attenuat
ion Down: 37.0 dB, Up: 16.8 dB; snr Margin Down: 9.1 dB, Up: 6.4 dB)
<38> Nov 26 02:31:25 PPP CHAP Receive challenge from rhost bras-red9.sf (Interne
t)
<38> Nov 26 02:31:26 PPP CHAP Receive challenge from rhost JUNOS (Internet)
<38> Nov 26 02:31:26 PPP CHAP Receive success (Internet)
<85> Nov 26 02:31:29 FIREWALL event (1 of 2): deleted rules
<132> Nov 26 02:31:29 PPP link up (Internet) [46.208.181.246]
<85> Nov 26 02:31:29 FIREWALL event (1 of 1): created rules
<85> Nov 26 02:31:29 FIREWALL event (1 of 1): modified rules
<14> Nov 26 02:31:39 CONFIGURATION saved by TR69
<173> Nov 26 02:36:45 xDSL linestate down
<85> Nov 26 02:36:45 FIREWALL event (1 of 1): created rules
<85> Nov 26 02:36:45 FIREWALL event (1 of 1): modified rules
<173> Nov 26 02:37:02 xDSL linestate down
<173> Nov 26 02:37:33 xDSL linestate down
<132> Nov 26 02:37:37 PPP link down (Internet) [46.208.181.246]
<173> Nov 26 02:37:59 xDSL linestate up (ITU-T G.992.5; downstream: 9187 kbit/s,
upstream: 1224 kbit/s; output Power Down: 20.6 dBm, Up: 12.8 dBm; line Attenuat
ion Down: 37.0 dB, Up: 16.8 dB; snr Margin Down: 9.1 dB, Up: 6.2 dB)
<38> Nov 26 02:38:03 PPP CHAP Receive challenge from rhost bras-red9.sf (Interne
t)
<38> Nov 26 02:38:03 PPP CHAP Receive challenge from rhost PCL-AG07 (Internet)
<38> Nov 26 02:38:03 PPP CHAP Receive success (Internet)
<85> Nov 26 02:38:04 FIREWALL event (1 of 2): deleted rules
<132> Nov 26 02:38:04 PPP link up (Internet) [31.185.250.161]
<85> Nov 26 02:38:04 FIREWALL event (1 of 1): created rules
<85> Nov 26 02:38:04 FIREWALL event (1 of 1): modified rules
<14> Nov 26 02:38:44 CONFIGURATION saved by TR69
<173> Nov 26 02:42:28 xDSL linestate down
<85> Nov 26 02:42:28 FIREWALL event (1 of 1): created rules
<85> Nov 26 02:42:28 FIREWALL event (1 of 1): modified rules
<173> Nov 26 02:42:45 xDSL linestate down
<132> Nov 26 02:43:15 PPP link down (Internet) [31.185.250.161]
<173> Nov 26 02:43:15 xDSL linestate down
<173> Nov 26 02:43:41 xDSL linestate up (ITU-T G.992.5; downstream: 9330 kbit/s,
upstream: 1216 kbit/s; output Power Down: 20.6 dBm, Up: 12.8 dBm; line Attenuat
ion Down: 37.5 dB, Up: 16.8 dB; snr Margin Down: 9.1 dB, Up: 6.5 dB)
<38> Nov 26 02:43:43 PPP CHAP Receive challenge from rhost bras-red9.sf (Interne
t)
<38> Nov 26 02:43:43 PPP CHAP Receive challenge from rhost PCL-AG07 (Internet)
<38> Nov 26 02:43:44 PPP CHAP Receive success (Internet)
<85> Nov 26 02:43:44 FIREWALL event (1 of 2): deleted rules
<132> Nov 26 02:43:44 PPP link up (Internet) [31.185.236.185]
<85> Nov 26 02:43:44 FIREWALL event (1 of 1): created rules
<85> Nov 26 02:43:44 FIREWALL event (1 of 1): modified rules
<14> Nov 26 02:44:29 CONFIGURATION saved by TR69
<102> Nov 26 03:02:21 SNTP Synchronised to server: 212.159.6.9
<173> Nov 26 03:15:04 xDSL linestate down
<85> Nov 26 03:15:04 FIREWALL event (1 of 1): created rules
<85> Nov 26 03:15:04 FIREWALL event (1 of 1): modified rules
<173> Nov 26 03:15:21 xDSL linestate down
<173> Nov 26 03:15:51 xDSL linestate down
<132> Nov 26 03:16:03 PPP link down (Internet) [31.185.236.185]
<173> Nov 26 03:16:17 xDSL linestate down
<173> Nov 26 03:16:18 xDSL linestate up (ITU-T G.992.5; downstream: 9067 kbit/s,
upstream: 1227 kbit/s; output Power Down: 20.7 dBm, Up: 12.8 dBm; line Attenuat
ion Down: 37.0 dB, Up: 16.8 dB; snr Margin Down: 9.1 dB, Up: 6.4 dB)
<38> Nov 26 03:16:19 PPP CHAP Receive challenge from rhost bras-red9.sf (Interne
t)
<38> Nov 26 03:16:20 PPP CHAP Receive challenge from rhost PTN-AG02 (Internet)
<38> Nov 26 03:16:20 PPP CHAP Receive success (Internet)
<132> Nov 26 03:16:21 PPP link up (Internet) [46.208.84.79]
<85> Nov 26 03:16:21 FIREWALL event (1 of 2): deleted rules
<85> Nov 26 03:16:21 FIREWALL event (1 of 1): created rules
<85> Nov 26 03:16:21 FIREWALL event (1 of 1): modified rules
<14> Nov 26 03:17:06 CONFIGURATION saved by TR69
<102> Nov 26 04:02:21 SNTP Synchronised to server: 212.159.6.10
<102> Nov 26 05:02:21 SNTP Synchronised to server: 212.159.6.9
<102> Nov 26 06:02:21 SNTP Synchronised to server: 212.159.6.10
<81> Nov 26 06:04:11 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 176.1
23.216.43 Dst ip: 46.208.84.79 Type: Destination Unreachable Code: Port Unreache
able
<81> Nov 26 06:33:44 FIREWALL icmp check (1 of 2): Protocol: ICMP  Src ip: 91.19
2.152.20 Dst ip: 46.208.84.79 Type: Time Exceeded Code: Time to Live exceeded in
Transit
<81> Nov 26 06:37:18 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 182.1
29.227.240 Dst ip: 46.208.84.79 Type: Destination Unreachable Code: Port Unreach
eable
<81> Nov 26 06:43:43 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 125.7
2.251.244 Dst ip: 46.208.84.79 Type: Destination Unreachable Code: Port Unreache
able
<81> Nov 26 06:55:53 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 123.2
5.39.83 Dst ip: 46.208.84.79 Type: Destination Unreachable Code: Port Unreacheab
le
<81> Nov 26 07:01:20 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 82.73
.19.204 Dst ip: 46.208.84.79 Type: Destination Unreachable Code: Port Unreacheab
le
<102> Nov 26 07:02:22 SNTP Synchronised to server: 212.159.6.9
<81> Nov 26 07:41:10 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 115.2
01.38.195 Dst ip: 46.208.84.79 Type: Destination Unreachable Code: Port Unreache
able
<102> Nov 26 08:02:22 SNTP Synchronised again to server: 212.159.6.9
<173> Nov 26 08:07:20 xDSL linestate down
<85> Nov 26 08:07:20 FIREWALL event (1 of 1): created rules
<85> Nov 26 08:07:20 FIREWALL event (1 of 1): modified rules
<173> Nov 26 08:07:38 xDSL linestate down
<173> Nov 26 08:08:08 xDSL linestate down
<132> Nov 26 08:08:18 PPP link down (Internet) [46.208.84.79]
<173> Nov 26 08:08:34 xDSL linestate up (ITU-T G.992.5; downstream: 8242 kbit/s,
upstream: 1217 kbit/s; output Power Down: 20.4 dBm, Up: 12.8 dBm; line Attenuat
ion Down: 37.0 dB, Up: 16.8 dB; snr Margin Down: 12.1 dB, Up: 6.3 dB)
<38> Nov 26 08:08:37 PPP CHAP Receive challenge from rhost bras-red9.sf (Interne
t)
<38> Nov 26 08:08:38 PPP CHAP Receive challenge from rhost PTW-AG01 (Internet)
<38> Nov 26 08:08:38 PPP CHAP Receive success (Internet)
<85> Nov 26 08:08:38 FIREWALL event (1 of 2): deleted rules
<132> Nov 26 08:08:38 PPP link up (Internet) [146.90.58.49]
<85> Nov 26 08:08:38 FIREWALL event (1 of 1): created rules
<85> Nov 26 08:08:38 FIREWALL event (1 of 1): modified rules
<14> Nov 26 08:09:23 CONFIGURATION saved by TR69
<37> Nov 26 08:12:55 LOGOUT User admin logged out on TELNET (192.168.1.64)
<37> Nov 26 08:13:16 LOGIN User admin logged in on TELNET (192.168.1.64)
<81> Nov 26 08:23:12 FIREWALL icmp check (1 of 1): Protocol: ICMP  Src ip: 123.2
05.159.146 Dst ip: 146.90.58.49 Type: Destination Unreachable Code: Port Unreach
eable
<37> Nov 26 08:32:11 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
<37> Nov 26 09:00:36 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
<102> Nov 26 09:02:22 SNTP Synchronised to server: 212.159.6.10
<37> Nov 26 09:51:43 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
<37> Nov 26 09:54:12 LOGIN User admin logged in on [HTTP] (from 192.168.1.64)
<102> Nov 26 10:02:22 SNTP Synchronised to server: 212.159.6.9
<37> Nov 26 10:51:43 LOGIN User admin tried to log in on TELNET (192.168.1.64)
<37> Nov 26 10:52:23 LOGIN User admin logged in on TELNET (192.168.1.64)
{admin}=>exit
Townman
Superuser
Superuser
Posts: 22,919
Thanks: 9,536
Fixes: 157
Registered: ‎22-08-2007

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Note if using the full version of RouterStats, it can provide direct access to the 'telnet' version of the log thereby avoiding the need for the cmd / telnet approach.

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Thank you for your input Kevin, we want to save a log for reference.
I should have mentioned that depending on your windows version you might need to enable Telnet in the first place.
The -f option is the one that creates the log file, maybe there is a permissions issue on your C:\ directory. Which windows version is it?
As far as the log itself goes the Jan 1 dates are when you have a "cold restart" - that is a power off, it doesn't know the time & date until it synchronises. So just before 2pm on the 25th (yesterday) did you have it powered off? Might you have had a power dip?
The line went down several times (not power) this morning in the early hours - the xDSL entries to look for begin <173>
It's the first xDSL linestate down that you find after an xDSL linestate up - you can ignore in between ones. Here they are
<173> Nov 26 02:30:25 xDSL linestate down
<173> Nov 26 02:31:21 xDSL linestate up (ITU-T G.992.5; downstream: 9142 kbit/s,
upstream: 1220 kbit/s; output Power Down: 20.6 dBm, Up: 12.7 dBm; line Attenuat
ion Down: 37.0 dB, Up: 16.8 dB; snr Margin Down: 9.1 dB, Up: 6.4 dB)
<173> Nov 26 02:36:45 xDSL linestate down
<173> Nov 26 02:37:59 xDSL linestate up (ITU-T G.992.5; downstream: 9187 kbit/s,
upstream: 1224 kbit/s; output Power Down: 20.6 dBm, Up: 12.8 dBm; line Attenuat
ion Down: 37.0 dB, Up: 16.8 dB; snr Margin Down: 9.1 dB, Up: 6.2 dB)
<173> Nov 26 02:42:28 xDSL linestate down
<173> Nov 26 02:43:41 xDSL linestate up (ITU-T G.992.5; downstream: 9330 kbit/s,
upstream: 1216 kbit/s; output Power Down: 20.6 dBm, Up: 12.8 dBm; line Attenuat
ion Down: 37.5 dB, Up: 16.8 dB; snr Margin Down: 9.1 dB, Up: 6.5 dB)
<173> Nov 26 03:15:04 xDSL linestate down
<173> Nov 26 03:16:18 xDSL linestate up (ITU-T G.992.5; downstream: 9067 kbit/s,
upstream: 1227 kbit/s; output Power Down: 20.7 dBm, Up: 12.8 dBm; line Attenuat
ion Down: 37.0 dB, Up: 16.8 dB; snr Margin Down: 9.1 dB, Up: 6.4 dB)
<173> Nov 26 08:07:20 xDSL linestate down
<173> Nov 26 08:08:34 xDSL linestate up (ITU-T G.992.5; downstream: 8242 kbit/s,
upstream: 1217 kbit/s; output Power Down: 20.4 dBm, Up: 12.8 dBm; line Attenuat
ion Down: 37.0 dB, Up: 16.8 dB; snr Margin Down: 12.1 dB, Up: 6.3 dB)
I can't understand why those few downs have caused the Target SNRM to go up
Unless the current error rate is high, or was at the time.
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

As Kevin mentioned you can open the 'telnet' version of the log via the RouterStats interface if you fire it up. You can 'select all' (right click) and copy and then paste to a file of your choice. I suppose I like to do it the other way because I don't always want RS running and I might want to do other CLI commands whilst I'm logged into the TG582n.
I'll post up this setup info for you in just a moment.
Townman
Superuser
Superuser
Posts: 22,919
Thanks: 9,536
Fixes: 157
Registered: ‎22-08-2007

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Anotherone,
You beat me to it - you can indeed copy and paste to notepad or what ever from the RS log.  Also for what it's worth IIRC you can poke 'telnet' commands at the router via RouterStats full - see the icon on the extreme right.
As for Telnet on post windows XP platforms it is all too easy for those of us who 'fixed' this years ago to remember that for new users it needs 'fixing' and how to do it.  I recall you asking me how not so long ago!  Wink  From vista onwards telnet is not enabled by default, one has to change "windows installed features" via the control panel installed software options.
Kevin

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Quote from: Anotherone
Thank you for your input Kevin, we want to save a log for reference.
I should have mentioned that depending on your windows version you might need to enable Telnet in the first place.
The -f option is the one that creates the log file, maybe there is a permissions issue on your C:\ directory. Which windows version is it?

Win7, telnet client enabled, creating log file appears to work if I use command from my 'user' directory rather than root (I say appears to - I've not gone looking for it yet but no error message as before.)

Quote
As far as the log itself goes the Jan 1 dates are when you have a "cold restart" - that is a power off, it doesn't know the time & date until it synchronises. So just before 2pm on the 25th (yesterday) did you have it powered off? Might you have had a power dip?

Ah, understood - the resync yesterday was almost certainly me me trying to get the best possible sync speed from what was by then a 9dB target SNRM!
Quote
I can't understand why those few downs have caused the Target SNRM to go up
Unless the current error rate is high, or was at the time.

With the PC asleep at the time, that will remain a secret unfortunately, at the moment, after 4 hours since the last resync, the error figures are:
Loss of Framing (Local/Remote): 44 / 0   
Loss of Signal (Local/Remote): 5 / 0   
Loss of Power (Local/Remote): 0 / 0   
Loss of Link (Remote): -   
Error Seconds (Local/Remote): 202 / 0 
FEC Errors (Up/Down): 218 / 5,046 
CRC Errors (Up/Down): 24 / 43   
HEC Errors (Up/Down): 30 / 214
To my inexperienced eye they don't look dreadful compared with those posted 3 hours earlier.  Undecided
Thanks to both of you (have either of you got a crystal ball and/or magic wand?)
Townman
Superuser
Superuser
Posts: 22,919
Thanks: 9,536
Fixes: 157
Registered: ‎22-08-2007

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Hi,
Anotherone will comment with greater authority, but I suggest the loF / LoS / ES counts are of some concern.  I suggest posting the full set of stats please when doing so.  Right now I think stability and monitoring are called for.
Anotherone is running with this ball, but if this was my line, I would not be doing manual resynchs in an attempt to force the best synch speed.  If necessary, I'd synch circa 9pm and then leave RouterStats for a few days monitoring the SNRM variation 24x7 to see if there are any patterns beyond the night time am/MW radio interference.
Going forwards, SNRM & synch plots (where it changes) will be quite useful.
Kevin

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Wish we did have a magic wand.
Don't agree with Kevin's suggestion about resyncs at all. I'll comment more on that later.
The errors Kevin mentioned were all accumulated when you lost sync so aren't of immediate concern - they are expected. It's the change since last time that's of more interest.
As you say the errors don't look dreadful now, quite reasonable, but always post the uptime as well (no need right now).
If you see any change in LOS -  Loss of Signal (Local/Remote): 5 / 0  or sync speed/Target SNRM then post stats etc. Another reason for sticking with the TG582n is it does give better diagnostic info. Why all those drops last night, it's difficult to say, but as you've mentioned if Fibre work is going on it could be things at the exchange (might even be the Cab, but if it was, pity the poor sods out there doing it in this weather).
If you are finding Routerstats running OK where you have it installed (which is where incidentally) then fine. Did you need to set it to run as Admin?
As regards saving graphs, have a think about a suitable directory/folder to save graphs and logs. A sub-folder of Documents may be best. I use a Shared one so I can look at them from anywhere on my network.
Set up guidelines to follow.
JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Yesterday's manual resync was probably the result of a fit of pique having seen the SNRM ramp up and connection speed fall away during the week, not something I've been making a habit of (it does it perfectly well on its own!  :()
Routerstats installed in C:\, I ticked login, entered username and password when setting up.
A few tips about what and how often to capture would come in handy - will turn off sleep mode on PC for the next few days.
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

OK this may some minor errors in it, as it needs updating and I've only done it in bits so far. But I'm going to go through it all again shortly as several people have been in need lately, so I may post back some corrections and I'll edit this post as well.
Suggested RouterStats settings for the Technicolor TG582n
Go to the Graphs tab.
There is some tabs down the LHS,
Select the Y-axis Limit & Colours tab on the LHS - make sure there is a tick in all the 'Adjust axis automatically' boxes for now, and also 'Remember Tx Noise & Tx Sync y-axis limits when RouterStats closes'. Click Apply & Save.
On the Common Settings tab - In the RH box, 'Use dots for grid', set the 'Points per page' at 720, (ignore the sample rate for the moment), put a tick in 'Pause graphs when router doesn't respond', in User defined graphs select Ramp mode, and a tick in 'Show gaps in timeline longer than 5 minutes' on the right. Click Apply & Save.
On the Capture Properties tab -
In the Capture graphs box make sure the 'Rx Noise', 'Tx Noise' and 'Rx Sync Speed' boxes are ticked. No point in capturing the others at this time.
In the folder box to the right, I suggest you define a folder for all the RouterStats stuff separate from anything else, I use a sub-folder in Shared Documents so I can view from anywhere on my network. Select 'Use Windows date/time' which should show as -yyyymmmdd-hhnn in the box. In the schedule box tick 'Always' and tick 'Capture additional graphs when RouterStats closes', and tick 'Unless there are less than 50 points plotted'.  In the Overlay box, tick the last 3, 'Overlay current Rx Sync Speed', 'Overlay current Rx Noise Margin' and 'Overlay Rx & Tx Attenuation'
Click Apply and Save.
Select the Extras tab on the LHS and tick 'Plot average Rx Noise Margin value of the previous 50 samples', 'Capture image size 100%', 'Applies to Captured Images' and 'Capture format' jpg or png whichever you prefer.  Click Apply & Save.
That's all on the Graphs tab, now select the System tab, my recommendation is tick the following only, on the LHS - 'Minimise to system tray', 'Show Rx Noise value on icons', 'Prompt before closing', and select 'Normal priority'. On the RHS - 'Correct results for known router errors', 'Show Alarms tab on main window', 'Show system messages tab on main window', 'Show StatusBar uptime as d,hr:min:sec' and 'Show WAN connection type on StatusBar'.   Click Apply & Save.
Now go to the Log tab - this has 2 tabs - on File Format, at the top - 'Enable Log' should be ticked, pick a file name like 'RSlog.txt' and just type it into the box, I suggest the folder should be the same as the one for the graphs, so click on the Browse button and go there. Tick 'Start new log each day with this format yyyy-mm-dd' (default format),   tick 'Begin each new log with a header', it makes life a bit easier if at some point later you want to import the log file(s) into a spread sheet to manipulate, and select 'Comma separated values', leave the 'Date/Time format of Log entries' as Default ddd dd mmm yyyy  hh:nn:ss .  Finally tick 'Append data automatically without confirmation'.  Click Apply and Save.
On the Log tab - Schedule & Options tab -  Select Log every sample (10 seconds). tick 'Log WAN Uptime (if available)', but I suggest UNtick 'Log IP address', you don't really want your IP address in there in case you need to post an extract. There's not much point in logging anything else it only makes the file bigger.  Click Apply & Save.
We don't need anything on the E-mail tab at this time. Close the Configuration window.
Right, some more on the Main screen tabs goto the Bitloading tab (5th tab). There are 4 sub-tabs, go to the Options tab. Tick 'Refresh bitloading graphs & summary every' and change the value to 10 seconds. Tick 'Restore default telnet timeout when RouterStats is closed'. 'Telnet port 23' and Telnet timeout 2000 msec'
Now go to the Bits/Tone tab and at the bottom RHS 'Plot tones' select 0-512 (for ADSL2+). If you are on ADSL1/2 select 0-255.
Now the Alarm tab. You can ignore the sub-tabs Alarm Timers & Limits tab and the Alarm Configuration tab for now, because we aren't affected by the default settings as we won't be rebooting or emailing or specifically logging an alarm event - at this time, you can see there was an issue from the data and plots.
Goto the Alarm Actions tab and make sure there is NO tick in the top box 'Reboot router' - we don't want any uncontrolled reboots!
Tick the 'Audible alarm' box and click Test Audio (you could come back and untick it later if it makes you jump too much!).
In the box 'SysTray &TaskBar icons turn red when...' tick both.  Nothing else on this tab.
Just the Alarm Setpoints tab - now the dB and Kbps values will depend on your current connection, we'll address those separately and you may need to adjust these a little as you see what your line is doing, but for the time being I'll suggest the following settings can be made in the 'seconds' boxes - with No ticks for now
Rx Noise Margin is above dB for more than 11 seconds
Rx Noise Margin is below dB for more than 21 seconds
Rx Sync Speed is above Kbps for more than 1 seconds
Rx Sync Speed is below Kbps for more than 1 seconds
No tick at present in the two Rx Noise Margin "has increased" and "has decreased" boxes and leave the default limits & no other boxes ticked.
At last we can go to the graphs themselves.
Go through each of the tabs, Noise Margin, Sync Speed and User-Defined both Downstream & Upstream, and make sure there is a tick in the box in the bottom LH corner - this is 'Check to plot graph'. There should also be a little Green Camerra Icon just above that box on the graphs selected to be Captured.
Also note, if you right click on any graph, you will see a number of useful drop down choices. The ticks on these generally match the settings you have already made.
The ones to specifically check are 'Include in log' is ticked for all graphs, you can deselect any you don't want later when you know more about your connection, the other is 'Scheduled Capture [Always]' on the ones you want  (Green camera icon already mentioned).
Note, the user defined graphs can only be setup once RouterStats is running, see 'Help' - the RH button on the top menu bar, select 'Configuring RouterStats >Technicolor TG582 and see Step 2. When you do so, initially I suggest choosing DS & US Attenuations as the ones to monitor initially.
OK, should be ready to run, click the Start Button (green arrow on the top menu bar).
JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

A Routerstats tickbox-fest has just taken place as per your excellent instructions.  Wink
Current stats 6 hours after this morning's unforced resync:
Uptime: 0 days, 6:03:18

DSL Type: ITU-T G.992.5

Bandwidth (Up/Down) [kbps/kbps]: 1,217 / 8,242

Data Transferred (Sent/Received) [MB/MB]: 38.56 / 659.51

Output Power (Up/Down) [dBm]: 12.8 / 0.0

Line Attenuation (Up/Down) [dB]: 16.8 / 37.0

SN Margin (Up/Down) [dB]: 6.0 / 13.2

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

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

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

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

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

Loss of Link (Remote): -

Error Seconds (Local/Remote): 209 / 0

FEC Errors (Up/Down): 475 / 6,832

CRC Errors (Up/Down): 87 / 54

HEC Errors (Up/Down): 127 / 254
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Only 7 ES errors since last stats & 11 CRC - fine. No problem.
If you right click when on the SNRM graph you can get it to plot the Speed on the same graph.
JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

With a SNRM of 12dB they bloomin' well ought to be good (also, it's still daylight, or what passes for it today.  8))
Must have understood at least some of the RS instructions because I'd already got the two-axis SNRM graph set up and running.  Wink
Can't decide whether I'd rather this turned out to be an actual fault (potentially aggravating to put right but at least I'd know) or something caused by 'works and persons unknown' (doubly aggravating, especially for someone from the home of PlusNet Towers!)
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

Well I must have written something clearly then  Grin
Quote from: JayG
.......also, it's still daylight, or what passes for it today.....
Can't decide whether I'd rather this turned out to be an actual fault (potentially aggravating to put right but at least I'd know) or something caused by 'works and persons unknown' (doubly aggravating, especially for someone from the home of PlusNet Towers!)

Weather is rubbish today, permanent low cloud/fog.
This type of intermittent problem is a pain. I don't know about aggravating to anyone at PN Towers  Shocked
JayG
Pro
Posts: 1,145
Thanks: 143
Fixes: 6
Registered: ‎30-10-2011

Re: 'Normal' evening SNRM drop/flat twisted pair RJ11 cable.

I meant that I live in Sheffield, so might have had the reckless idea that PN would have a better idea of what BTOR were up to out in the field round these parts rather than elsewhere.  Undecided