50M/5M瞬段嚴重



贊助商連結


acion
2011-07-02, 11:33 PM
============================================================================
VDSL Training Status: Showtime
VDSL Profile: Profile 17a
Traffic Type: PTM Mode
============================================================================
VDSL Port Details Upstream Downstream
Line Rate: 5.418 Mbps 54.492 Mbps
Actual Net Data Rate: 5.375 Mbps 54.397 Mbps
Trellis Coding: ON ON
SNR Margin: 34.4 dB 257.6 dB
Actual Delay: 5 ms 7 ms
Transmit Power: - 6.6 dBm 8.9 dBm
Receive Power: -8.8 dBm 5.4 dBm
Actual INP: 17.0 symbols 26.0 symbols
Total Attenuation: 2.3 dB 3.4 dB
Attainable Net Data Rate: 63.698 Mbps 149.872 Mbps

看圖只知道下載的snr是257.6過高,有哪位知道問題所在的可能性呢

贊助商連結


a78810
2011-07-02, 11:38 PM
電話線可能有T接干擾到噢

acion
2011-07-03, 09:27 AM
電話線可能有T接干擾到噢
我也這樣想,打算晚點從電信機房開始查線,別是外包沒把線打好吧,
最近真得是被搞翻了,六天總計才異動好11路,目前為止有的還有些小問題,等異動完再來算總帳,不過千萬秋後算帳,我會死得很難看:sleep:

62chaokai
2011-07-03, 03:36 PM
最近中華電信人忙翻了,辛苦了。
樓上的也是。

spooky_mulder
2011-07-03, 04:00 PM
acion兄可否提供數據機型號與韌體版本,謝謝。

門神
2011-07-03, 06:32 PM
acion兄可否提供數據機型號與韌體版本,謝謝。

+1 ^^

acion
2011-07-03, 09:02 PM
acion兄可否提供數據機型號與韌體版本,謝謝。
要補充說明一些
8天的時間,小弟總共花了近60個小時,只升速11路,多半的時間都在跟機房溝通與報修中,但實際上都是外包在的時候處理完,只有這一路有後續的問題
實際上這兩三年,小弟每次異動幾乎都會遇到外包到了現場,機房還未完成設定,釘線釘假的???
今天去電信機房自己重打線所獲得的P874數據如下:
============================================================================
VDSL Training Status: Showtime
VDSL Profile: Profile 17a
Traffic Type: PTM Mode
============================================================================
VDSL Port Details Upstream Downstream
Line Rate: 5.418 Mbps 54.492 Mbps
Actual Net Data Rate: 5.375 Mbps 54.397 Mbps
Trellis Coding: ON ON
SNR Margin: 32.8 dB 31.7 dB
Actual Delay: 5 ms 7 ms
Transmit Power: - 6.7 dBm 8.7 dBm
Receive Power: -8.4 dBm 5.3 dBm
Actual INP: 17.0 symbols 26.0 symbols
Total Attenuation: 2.0 dB 3.4 dB
Attainable Net Data Rate: 61.379 Mbps 152.908 Mbps
============================================================================

但是上傳最高只有不到2M,我想瞬段主因應該在於上傳不足(流量一直不大)

更令人生氣的是,客服跟我說DSLAM機房今天全部休假沒人,
!!!中華電信DSLAM機房逢一般假日就全部打烊!!!

老共,你看到了嗎??這算不算是情資呢
我可以申請電信情報費嗎??

再補充一點,星期六中午報修一路升速中的線路(還未通知施工,這是第三路未通知就長時間斷線),機房處理到下班時間就說等星期一吧

奇怪,只有我這麼衰嗎??

k7system
2011-07-03, 09:54 PM
更令人生氣的是,客服跟我說DSLAM機房今天全部休假沒人,
!!!中華電信DSLAM機房逢一般假日就全部打烊!!!


假日就沒人的話,
升速作業不就停擺了。

orz....

.

acion
2011-07-03, 10:17 PM
固6 50M/5M瞬斷的慘況(遠端==>>GATEWAY==>>該線路IP,到GATEWAY正常)
Reply from 59.125.101.XXX: bytes=32 time=17ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=16ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Request timed out.
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=20ms TTL=60
Request timed out.
Reply from 59.125.101.XXX: bytes=32 time=25ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=24ms TTL=60
Request timed out.
Reply from 59.125.101.XXX: bytes=32 time=25ms TTL=60
Request timed out.
Reply from 59.125.101.XXX: bytes=32 time=13ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=15ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=26ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=16ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=16ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=13ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=17ms TTL=60
Request timed out.
Reply from 59.125.101.XXX: bytes=32 time=15ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=13ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=25ms TTL=60
Request timed out.
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=19ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=16ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Request timed out.
Reply from 59.125.101.XXX: bytes=32 time=18ms TTL=60
Request timed out.
Reply from 59.125.101.XXX: bytes=32 time=20ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=24ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=14ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=15ms TTL=60
Reply from 59.125.101.XXX: bytes=32 time=23ms TTL=60