ich hatte bei einem Kunden heute einen hängenden Call im VCM. Gut dachte ich, startest den Router neu (do o/b) und dann passt es wieder. Passte es aber nicht. Das VDSL-Modem kam nämlich nicht wieder hoch. Was könnte die Ursache dafür sein?
Code: Alles auswählen
root@XYZ:/
> ls -r st/vdsl
Advanced MENU:
Modem MENU:
Connection-history TABINFO: 100 x [Index,Sync-time,..]
Attainable-Data-Rate-Downstream-kbps INFO: 0
Attainable-Data-Rate-Upstream-kbps INFO: 0
Attenuation-Downstream-dB INFO: 0.0
Attenuation-Upstream-dB INFO: 0.0
Connection-count INFO: 0
Connection-duration INFO:
DSLAM-Chipset-Manufacturer INFO:
DSLAM-Manufacturer INFO:
DSLAM-Serial-Number INFO:
DSLAM-Version INFO:
Data-Rate-Downstream-kbps INFO: 0
Data-Rate-Upstream-kbps INFO: 0
INP-Downstream-Symbols INFO: 0.0
INP-Upstream-Symbols INFO: 0.0
Interleave-Downstream-ms INFO: 0.00
Interleave-Upstream-ms INFO: 0.00
Line-State INFO: UNKNOWN
Line-Type INFO: over-ISDN
Modem-Type INFO: VDSL2
SNR-Downstream-dB INFO: 0.0
SNR-Upstream-dB INFO: 0.0
Standard INFO: Unknown
VDSL-Profile INFO: Unknown
Vectoring INFO: No
Vectoring-Support INFO: No
Retrain ACTION:
[rek] Connection-history:
Index Sync-time Disconnect-time Standard VDSL-Profile Reason DS-datarate US-datarate DS-SNR US-SNR DS-attenuation US-attenuation Linecode Vectoring
============-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
1 03/19/2018 12:15:05 03/22/2018 22:39:58 VDSL2 17a Protocol 100872 41999 13.7 9.3 12.9 12.1 5.7.9.9.0.7 Yes
2 03/22/2018 22:45:42 03/23/2018 02:34:19 VDSL2 17a Protocol 100872 41341 12.6 9.1 12.9 12.1 5.7.9.9.0.7 Yes
3 03/23/2018 02:37:24 03/27/2018 20:03:36 VDSL2 17a Protocol 100872 41249 12.3 9.2 12.9 12.1 5.7.9.9.0.7 Yes
[rek] Advanced:
DS-Bit-Loading TABINFO: 0 x [BIN-Number,x0,x1,x2,x3,x4,x5,..]
DS-SNR-per-Sub-Carrier TABINFO: 0 x [Sub-Carrier,x0,x1,x2,x3,x4,..]
US-Bit-Loading TABINFO: 0 x [BIN-Number,x0,x1,x2,x3,x4,x5,..]
Connection-count INFO: 0
Connection-duration INFO:
DS-ATM-Cells INFO: 0
DS-ATM-HEC-Errors INFO: 0
DS-ATM-Idle-Bit-Errors INFO: 0
DS-Attainable-data-rate-kbps INFO: 0
DS-CRC-Errors INFO: 0
DS-Data-Path-CRCnp-Errors INFO: 0
DS-Data-Path-CRCp-Errors INFO: 0
DS-Data-Path-CVnp-Errors INFO: 0
DS-Data-Path-CVp-Errors INFO: 0
DS-Data-Rate-kbps INFO: 0
DS-FEC-Errors INFO: 0
DS-INP-Symbols INFO: 0.0
DS-Interleave-ms INFO: 0.00
DS-Line-Attenuation-dB INFO: 0.0
DS-Line-Options INFO:
DS-SNR-Margin-dB INFO: 0.0
DSLAM-Chipset-Manufacturer INFO:
DSLAM-Chipset-Manufacturer-dump INFO: 0000000000000000
DSLAM-Manufacturer INFO:
DSLAM-Manufacturer-dump INFO: 0000000000000000
DSLAM-Serial-Number INFO:
DSLAM-Version INFO:
Line-State INFO: UNKNOWN
Rx-Packet-count INFO: 0
Standard INFO: Unknown
Transmitted-ATM-Cells INFO: 0
Tx-Packet-count INFO: 0
US-ATM-Cells INFO: 0
US-ATM-HEC-Errors INFO: 0
US-ATM-Idle-Bit-Errors INFO: 0
US-Attainable-data-rate-kbps INFO: 0
US-CRC-Errors INFO: 0
US-Data-Path-CRCnp-Errors INFO: 0
US-Data-Path-CRCp-Errors INFO: 0
US-Data-Path-CVnp-Errors INFO: 0
US-Data-Path-CVp-Errors INFO: 0
US-Data-Rate-kbps INFO: 0
US-FEC-Errors INFO: 0
US-INP-Symbols INFO: 0.0
US-Interleave-ms INFO: 0.00
US-Line-Attenuation-dB INFO: 0.0
US-Line-Options INFO:
US-SNR-Margin-dB INFO: 0.0
VDSL-Profile INFO: Unknown
Vectoring INFO: No
Vectoring-Support INFO: No
WAN-Rx-Overruns INFO: 0
WAN-Rx-Packet-bytes INFO: 0
WAN-Rx-Packet-count INFO: 0
WAN-Rx-Packet-drops INFO: 0
WAN-Rx-Packet-errors INFO: 0
WAN-Tx-Overruns INFO: 0
WAN-Tx-Packet-bytes INFO: 0
WAN-Tx-Packet-count INFO: 0
WAN-Tx-Packet-drops INFO: 0
WAN-Tx-Packet-errors INFO: 0
Retrain ACTION:
[rek] Advanced/DS-Bit-Loading:
BIN-Number x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 Graph
============-------------------------------------------------------
[rek] Advanced/DS-SNR-per-Sub-Carrier:
Sub-Carrier x0 x1 x2 x3 x4 x5 x6 x7 x8 x9
=============------------------------------------------------
[rek] Advanced/US-Bit-Loading:
BIN-Number x0 x1 x2 x3 x4 x5 x6 x7 x8 x9 Graph
============-------------------------------------------------------
[rek] Modem:
Boot-Count INFO: 108
Chipset-Type INFO:
DSL-API-Version INFO:
DSP-Firmware-Version INFO:
Driver-Version INFO:
Hardware-Version INFO:
Hybrid INFO: B/J
ISDN-Firmware INFO: /flash/system/lcos/lcos-1/xcpe_579907_574402
Last-Error INFO: Quick memtest timeout
Link INFO: 0
Load INFO: 0
Load-Idle INFO: 0
Load-System INFO: 0
Load-User INFO: 0
Memory-test INFO: Timeout
Modem-State INFO: Uploading-Bootstrap
Options INFO: 3
POTS-Firmware INFO: /flash/system/lcos/lcos-1/xcpe_57B507_575401
Temperature[degC] INFO: 0.0
WAN-Acceleration INFO: No
Reboot-Modem ACTION:
INFO: Options
INFO: Quick-Memory-test
und
INFO: Uploading-Bootstrap
Ein VDSL-Status-Trace liefert:
Code: Alles auswählen
[VDSL-Status] 2018/03/27 20:30:12,329
[1] Booting modem: Quick memtest timeout
[VDSL-Status] 2018/03/27 20:30:24,042
[1] Booting modem: Quick memtest timeout
[VDSL-Status] 2018/03/27 20:30:35,755
[1] Booting modem: Quick memtest timeout
[VDSL-Status] 2018/03/27 20:30:47,467
[1] Booting modem: Quick memtest timeout
[VDSL-Status] 2018/03/27 20:30:59,180
[1] Booting modem: Quick memtest timeout
[VDSL-Status] 2018/03/27 20:31:10,893
[1] Booting modem: Quick memtest timeout
[VDSL-Status] 2018/03/27 20:31:22,606
[1] Booting modem: Quick memtest timeout
[VDSL-Status] 2018/03/27 20:31:34,319
[1] Booting modem: Quick memtest timeout
Des Weiteren benötigt das Modem 3 Min. zum synchronisieren. Ist das nicht etwas lange?
Firmware ist 10.12-RU6.
Vielen Dank und viele Grüße,
Jirka