案例传输光衰过大导致上传速率不达标.docx
《案例传输光衰过大导致上传速率不达标.docx》由会员分享，可在线阅读，更多相关《案例传输光衰过大导致上传速率不达标.docx（7页珍藏版）》请在冰豆网上搜索。
案例传输光衰过大导致上传速率不达标
传输光衰过大导致上传速率不达标
【摘要】在日常测试单验过程中，发现一个站点上传异常，该站点下载等其他业务正常，在后台的配合分析过程中，定位为该站因传输光衰异常导致。
【关键字】上传异常传输光衰
【故障现象】：
现场对临泉鲖城站点上传下载业务测试过程中，发现下载速率正常，满调度，SINR等能达到好点要求。
在相同位置做上传业务RSRP良好，SINR良好，后台跟踪干扰检测均在-100以下，RSSI输出在加载和不加载的情况下均正常，但是调度较差，导致上传速率持续较低（基本在10MBPS以下）。
【原因分析】
现场主要进行如下几个方面的排查。
1.上传速率较低可能与服务器有关，尝试更换服务器后做上传业务，发现速率没改善，和更换前服务器前一样，上传速率较低，尝试在该站点各个扇区做上传，情况相同，上传低的情况没改善。
继续用原服务器换个另外一个站址进行上传业务能够达标，排除服务器问题。
2.异常点SINR值较高，达到30左右，可见下行无线环境较好，同时后台跟踪干扰检测、小区内用户是否接入过多、RSSI检测，检查结果为以上各项均正常。
排除基站无线设备和频率干扰等原因。
3.联系后台检查是否有告警，后台反映该站点不存在告警，排除无线硬件故障。
4.传输因素会影响上传下载业务的性能，需要对该基站进行PING大包测试（大包1500KBYTE），发现丢包现象严重，结合以往项目经验，定位于传输问题。
需要传输侧配合排查传输是否有光路不正常（如光衰过大导致）。
传输人员配合光路排障后到原站址进行上传业务，速率正常了。
【解决方法】：
出现上传异常现象，现场人员一般从服务器异常、SINR值异常、告警、小区接入用户数、调度情况等等入手处理。
后台人员可以通过PING测试，判断下该站点的传输情况。
具体执行步骤如下
1.首先查询该基站源IP和目标IP，命令为：
LSTSCTPLNK详情如下图：
2.使用MML进行PING测试（大包1500KBYTE），具体操作如下：
选取距离FY-临泉-鲖城HFBBU00-436724较近的站点FY-临泉-鲖城二站-HFTA-436733的做为ping测试，如下：
网管提取FY-临泉-鲖城二站-HFTA-436733的本端地址如下:
FY-临泉-鲖城HFBBU00-436724较近的站点FY-临泉-鲖城二站-HFTA-436733的ping测试操作
3.命令执行结果如下：
PING:
SN=7,SRCIP="7.184.19.118",DSTIP="7.184.19.90",PKTSIZE=1500,CONTPING=DISABLE,NUM=100,APPTIF=NO;
FY-临泉-鲖城HFBBU00-436724
PING7.184.19.90:
1500databytes
Replyfrom7.184.19.90:
bytes=1500Sequence=1ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=2ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=3ttl=254time=3ms
Replyfrom7.184.19.90:
bytes=1500Sequence=4ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=5ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=6ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=7ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=8ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=9ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=10ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=11ttl=254time=3ms
Replyfrom7.184.19.90:
bytes=1500Sequence=12ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=13ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=15ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=16ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=17ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=18ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=19ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=20ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=21ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=23ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=25ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=27ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=28ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=30ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=31ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=32ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=33ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=34ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=35ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=36ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=37ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=38ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=40ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=41ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=42ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=43ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=44ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=45ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=46ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=47ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=48ttl=254time=1ms
Replyfrom7.184.19.90:
bytes=1500Sequence=49ttl=254time=3ms
Replyfrom7.184.19.90:
bytes=1500Sequence=50ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=51ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=52ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=54ttl=254time=1ms
Replyfrom7.184.19.90:
bytes=1500Sequence=55ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=56ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=57ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=59ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=60ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=61ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=62ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=63ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=64ttl=254time=10ms
Replyfrom7.184.19.90:
bytes=1500Sequence=65ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=66ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=67ttl=254time=2ms
Requesttimeout
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=70ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=71ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=72ttl=254time=3ms
Replyfrom7.184.19.90:
bytes=1500Sequence=73ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=74ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=75ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=76ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=77ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=79ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=80ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=82ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=83ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=85ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=87ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=88ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=90ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=91ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=92ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=93ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=94ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=95ttl=254time=2ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=97ttl=254time=1ms
Requesttimeout
Replyfrom7.184.19.90:
bytes=1500Sequence=99ttl=254time=2ms
Replyfrom7.184.19.90:
bytes=1500Sequence=100ttl=254time=2ms
---7.184.19.90pingstatistics---
100packet（s）transmitted
83packet（s）received
Percent17.00packetlost
round-tripmin/avg/max=1/2/10ms
共有109个报告
---END
统计信息：
共收到报文包109个。
从执行结果可见，掉包还是比较多的，对上传业务有影响。
调度不满，平均上传速率仅5Mbps左右，传输光衰处理以后平均上传速率达到30Mbps以上。
PING:
SN=7,SRCIP="7.184.19.118",DSTIP="7.184.19.90",PKTSIZE=1500,CONTPING=DISABLE,NUM=100,APPTIF=NO;
FY-临泉-鲖城HFBBU00-436724
PING7.184.19.90:
1500databytes
中间正常ping过程省略
---7.184.19.90pingstatistics---
100packet（s）transmitted
100packet（s）received
Percent0.00packetlost
round-tripmin/avg/max=2/2/19ms
共有109个报告
---END
统计信息：
共收到报文包109个。
【结论与推广】
碰到上传速率异常，从服务器、站点告警、传输问题、无线环境、参数配置、现场检查等手段进行分析，逐渐排查出具体原因。
升级会员 