Kitz Forum
Broadband Related => Broadband Technology => Topic started by: Weaver on January 19, 2009, 01:26:13 PM
-
Looking at the detailed stats of a Netgear DG834v3 (say) with telnet (using the todo=debug trick mentioned elsewhere on this site I noticed that the ShowTime Count was incremented during the session.
Is it the case that the ShowTime count gets incremented as a result of a loss-of-sync event? (Or also because the user orders the router to drop the connection and bring it back up againg using the admin UI)
-
The two sets of stats are below. There is a set of bits-per-bin data which applies to the second state (unfortunately didn't capture it before the state change)
==
DG834v3 telnet session :-
== first set of stats ===
# cat /proc/avalanche/avsar_modem_stats
AR7 DSL Modem Statistics:
--------------------------------
[DSL Modem Stats]
US Connection Rate: 608 DS Connection Rate: 1856
DS Line Attenuation: 61 DS Margin: 13
US Line Attenuation: 31 US Margin: 6
US Payload : 5332464 DS Payload: 13570464
US Superframe Cnt : 916361 DS Superframe Cnt: 916361
US Transmit Power : 0 DS Transmit Power: 0
LOS errors: 0 SEF errors: 0
Errored Seconds: 0 Severely Err Secs: 0
Frame mode: 3 Max Frame mode: 0
Trained Path: 1 US Peak Cell Rate: 1433
Trained Mode: 3 Selected Mode: 1
ATUC Vendor Code: 54535443 ATUC Revision: 2
Hybrid Selected: 3 Trellis: 1
Showtime Count: 1 DS Max Attainable Bit Rate: 1856 kbps
BitSwap: 1 US Max Attainable Bit Rate: n/a
Annex: AnxA psd_mask_qualifier: 0x0000
Power Management Status: L0 DS HLINSC: 0
US ACTPSD: -345 DS ACTPSD: -355
Total init. errors: 0 Total init. timeouts: 0
Showtime init. errors: 0 Showtime init. timeouts: 0
Last showtime init. errors: 0 Last showtime init. timeouts: 0
ATUC ghsVid: b5 00 54 53 54 43 00 00
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00
ATUR ghsVid: b5 00 54 53 54 43 00 00
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00
[Upstream (TX) Interleave path]
CRC: 28 FEC: 11424 NCD: 0
LCD: 0 HEC: 1904
[Downstream (RX) Interleave path]
CRC: 21 FEC: 4717 NCD: 0
LCD: 0 HEC: 0
[Upstream (TX) Fast path]
CRC: 0 FEC: 0 NCD: 1
LCD: 0 HEC: 0
[Downstream (RX) Fast path]
CRC: 0 FEC: 0 NCD: 0
LCD: 0 HEC: 0
[ATM Stats]
[Upstream/TX]
Good Cell Cnt: 111093
Idle Cell Cnt: 22227367
Tx Packets Dropped Count: 0
Tx Bad Packets Count: 0
[Downstream/RX)]
Good Cell Cnt: 282718
Idle Cell Cnt: 67908275
Bad Hec Cell Cnt: 54
Overflow Dropped Cell Cnt: 0
Rx Packets Dropped Count: 0
Rx Bad Packets Count: 0
[SAR AAL5 Stats]
Tx PDU's: 17918
Rx PDU's: 20394
Tx Total Bytes: 4560039
Rx Total Bytes: 12946238
Tx Total Error Counts: 0
Rx Total Error Counts: 0
[OAM Stats]
Near End F5 Loop Back Count: 0
Near End F4 Loop Back Count: 0
Far End F5 Loop Back Count: 0
Far End F4 Loop Back Count: 0
SAR OAM Ping Response Drop Count=0
#
=== second stats ===
# cat /proc/avalanche/avsar_modem_stats
AR7 DSL Modem Statistics:
--------------------------------
[DSL Modem Stats]
US Connection Rate: 448 DS Connection Rate: 1920
DS Line Attenuation: 61 DS Margin: 11
US Line Attenuation: 31 US Margin: 6
US Payload : 154992 DS Payload: 902976
US Superframe Cnt : 90443 DS Superframe Cnt: 90443
US Transmit Power : 0 DS Transmit Power: 0
LOS errors: 0 SEF errors: 0
Errored Seconds: 0 Severely Err Secs: 0
Frame mode: 3 Max Frame mode: 0
Trained Path: 1 US Peak Cell Rate: 1056
Trained Mode: 3 Selected Mode: 1
ATUC Vendor Code: 54535443 ATUC Revision: 2
Hybrid Selected: 1 Trellis: 1
Showtime Count: 2 DS Max Attainable Bit Rate: 1920 kbps
BitSwap: 1 US Max Attainable Bit Rate: n/a
Annex: AnxA psd_mask_qualifier: 0x0000
Power Management Status: L0 DS HLINSC: 0
US ACTPSD: -345 DS ACTPSD: -355
Total init. errors: 0 Total init. timeouts: 0
Showtime init. errors: 0 Showtime init. timeouts: 0
Last showtime init. errors: 0 Last showtime init. timeouts: 0
ATUC ghsVid: b5 00 54 53 54 43 00 00
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00
ATUR ghsVid: b5 00 54 53 54 43 00 00
T1413Vid: 00 00 T1413Rev: 00 VendorRev: 00
[Upstream (TX) Interleave path]
CRC: 0 FEC: 179996 NCD: 0
LCD: 0 HEC: 0
[Downstream (RX) Interleave path]
CRC: 0 FEC: 61 NCD: 0
LCD: 0 HEC: 0
[Upstream (TX) Fast path]
CRC: 0 FEC: 0 NCD: 1
LCD: 0 HEC: 0
[Downstream (RX) Fast path]
CRC: 0 FEC: 0 NCD: 0
LCD: 0 HEC: 0
[ATM Stats]
[Upstream/TX]
Good Cell Cnt: 3229
Idle Cell Cnt: 1621332
Tx Packets Dropped Count: 0
Tx Bad Packets Count: 1
[Downstream/RX)]
Good Cell Cnt: 18812
Idle Cell Cnt: 6943548
Bad Hec Cell Cnt: 0
Overflow Dropped Cell Cnt: 0
Rx Packets Dropped Count: 0
Rx Bad Packets Count: 0
[SAR AAL5 Stats]
Tx PDU's: 18958
Rx PDU's: 21644
Tx Total Bytes: 4670354
Rx Total Bytes: 13823095
Tx Total Error Counts: 0
Rx Total Error Counts: 0
[OAM Stats]
Near End F5 Loop Back Count: 0
Near End F4 Loop Back Count: 0
Far End F5 Loop Back Count: 0
Far End F4 Loop Back Count: 0
SAR OAM Ping Response Drop Count=0
#
# bits-per-bin in state 2 (us 448 ds 1920)
# cat /proc/avalanche/avsar_bit_allocation_table
AR7 DSL Modem US Bit Allocation:
00 00 00 00 00 00 00 05 05 05 05 05 05 07 07 07
07 07 07 07 07 07 07 07 07 07 07 07 07 06 04 00
AR7 DSL Modem DS Bit Allocation:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 07 08 09 09 09 09 09 09 09 09 09 08 09
09 09 09 09 09 08 08 08 08 08 08 08 08 08 08 08
00 08 08 08 08 08 07 07 07 07 07 07 07 07 07 07
07 07 07 07 07 07 07 07 07 06 06 05 05 06 06 06
06 06 05 05 05 05 05 05 05 05 05 05 05 04 04 04
04 04 04 04 04 04 04 04 04 03 03 02 02 02 02 02
02 02 02 02 02 02 02 02 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
#
== end ==
-
I could be wrong but afaik showtime is after initialisation (http://www.kitz.co.uk/adsl/adsl_technology.htm#sync) which is part of the sync process.
Theres 2 states of connection - syncing to the exchange and then PPP session, the later being out on to the internet via your ISP.
Most routers will record 2 sets of uptime. The time the router has been up for and the time its held a valid internet PPP session.
Actual uptime displayed as LAN uptime doesnt normally allow for any loss of sync, but the time the router has remained switched on for.
-
I could be wrong but afaik showtime is after initialisation (http://www.kitz.co.uk/adsl/adsl_technology.htm#sync) which is part of the sync process.
Theres 2 states of connection - syncing to the exchange and then PPP session, the later being out on to the internet via your ISP.
Most routers will record 2 sets of uptime. The time the router has been up for and the time its held a valid internet PPP session.
Actual uptime displayed as LAN uptime doesnt normally allow for any loss of sync, but the time the router has remained switched on for.
On our APtS we get "showtime" once full sync is achived but before the ATM e to e ping, and ppp session. so I would assume this is the same as the counter mentioned
-
Thanks ezzer
-
I also noticed on a DG834v2 that while the Showtime Count is 2 under modem stats, the modem training results give a showtime of 1 ... ???
# cat /proc/avalanche/avsar_modem_training
SHOWTIME
1
failTrains=9