案例传输光衰过大导致上传速率不达标.docx

1、案例传输光衰过大导致上传速率不达标传输光衰过大导致上传速率不达标【摘 要】在日常测试单验过程中，发现一个站点上传异常，该站点下载等其他业务正常，在后台的配合分析过程中，定位为该站因传输光衰异常导致。【关键字】上传异常 传输光衰【故障现象】：现场对临泉鲖城站点上传下载业务测试过程中，发现下载速率正常，满调度，SINR等能达到好点要求。在相同位置做上传业务RSRP良好，SINR良好，后台跟踪干扰检测均在-100以下，RSSI输出在加载和不加载的情况下均正常，但是调度较差，导致上传速率持续较低（基本在10MBPS以下）。【原因分析】现场主要进行如下几个方面的排查。1.上传速率较低可能与服务器有关，尝

2、试更换服务器后做上传业务，发现速率没改善，和更换前服务器前一样，上传速率较低，尝试在该站点各个扇区做上传，情况相同，上传低的情况没改善。继续用原服务器换个另外一个站址进行上传业务能够达标，排除服务器问题。2.异常点SINR值较高，达到30左右，可见下行无线环境较好，同时后台跟踪干扰检测、小区内用户是否接入过多、RSSI检测，检查结果为以上各项均正常。排除基站无线设备和频率干扰等原因。3.联系后台检查是否有告警，后台反映该站点不存在告警，排除无线硬件故障。4.传输因素会影响上传下载业务的性能，需要对该基站进行PING大包测试（大包1500KBYTE），发现丢包现象严重，结合以往项目经验，定位于传

3、输问题。需要传输侧配合排查传输是否有光路不正常（如光衰过大导致）。传输人员配合光路排障后到原站址进行上传业务，速率正常了。【解决方法】：出现上传异常现象，现场人员一般从服务器异常、SINR值异常、告警、小区接入用户数、调度情况等等入手处理。后台人员可以通过PING测试，判断下该站点的传输情况。具体执行步骤如下1.首先查询该基站源IP和目标IP，命令为：LST SCTPLNK详情如下图：2.使用MML进行PING测试（大包1500KBYTE），具体操作如下：选取距离FY-临泉-鲖城HFBBU00-436724较近的站点FY-临泉-鲖城二站-HFTA-436733的做为ping测试，如下：网管提取

4、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 PING 7.184.19.90: 1500 data bytes Reply from 7.184.19.90: bytes=1500 Sequence=1 ttl

5、=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=2 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=3 ttl=254 time=3 ms Reply from 7.184.19.90: bytes=1500 Sequence=4 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=5 ttl=254 time=2 ms Reply from 7.184.19.90: bytes

6、=1500 Sequence=6 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=7 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=8 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=9 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=10 ttl=254 time=2 ms Reply fr

7、om 7.184.19.90: bytes=1500 Sequence=11 ttl=254 time=3 ms Reply from 7.184.19.90: bytes=1500 Sequence=12 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=13 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=15 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1

8、500 Sequence=16 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=17 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=18 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=19 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=20 ttl=254 time=2 ms Reply

9、from 7.184.19.90: bytes=1500 Sequence=21 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=23 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=25 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=27 ttl=254 time=

10、2 ms Reply from 7.184.19.90: bytes=1500 Sequence=28 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=30 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=31 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=32 ttl=254 time=2 ms Reply from 7.184.1

11、9.90: bytes=1500 Sequence=33 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=34 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=35 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=36 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=37 ttl=254 tim

12、e=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=38 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=40 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=41 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=42 ttl=254 time=2 ms Reply from 7.184

13、.19.90: bytes=1500 Sequence=43 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=44 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=45 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=46 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=47 ttl=254 t

14、ime=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=48 ttl=254 time=1 ms Reply from 7.184.19.90: bytes=1500 Sequence=49 ttl=254 time=3 ms Reply from 7.184.19.90: bytes=1500 Sequence=50 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=51 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1

15、500 Sequence=52 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=54 ttl=254 time=1 ms Reply from 7.184.19.90: bytes=1500 Sequence=55 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=56 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=57 ttl=254

16、 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=59 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=60 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=61 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=62 ttl=254 time=2 ms Reply from 7

17、.184.19.90: bytes=1500 Sequence=63 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=64 ttl=254 time=10 ms Reply from 7.184.19.90: bytes=1500 Sequence=65 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=66 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=67 ttl=

18、254 time=2 ms Request time out Request time out Reply from 7.184.19.90: bytes=1500 Sequence=70 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=71 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=72 ttl=254 time=3 ms Reply from 7.184.19.90: bytes=1500 Sequence=73 ttl=254 ti

19、me=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=74 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=75 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=76 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=77 ttl=254 time=2 ms Request time out Reply from 7.18

20、4.19.90: bytes=1500 Sequence=79 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=80 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=82 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=83 ttl=254 time=2 ms Request time out Reply from 7.184.19.9

21、0: bytes=1500 Sequence=85 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=87 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=88 ttl=254 time=2 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=90 ttl=254 time=2 ms Reply from 7.184.19.90: byt

22、es=1500 Sequence=91 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=92 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=93 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=94 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=95 ttl=254 time=2 ms Re

23、quest time out Reply from 7.184.19.90: bytes=1500 Sequence=97 ttl=254 time=1 ms Request time out Reply from 7.184.19.90: bytes=1500 Sequence=99 ttl=254 time=2 ms Reply from 7.184.19.90: bytes=1500 Sequence=100 ttl=254 time=2 ms - 7.184.19.90 ping statistics - 100 packet(s) transmitted 83 packet(s) r

24、eceived Percent 17.00 packet lostround-trip min/avg/max = 1/2/10 ms共有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 PING 7.184.19.90: 1500 data bytes中间正常ping过程省略 - 7.184.19.90 ping statistics - 100 packet(s) transmitted 100 packet(s) received Percent 0.00 packet lostround-trip min/avg/max = 2/2/19 ms共有109个报告- END统计信息：共收到报文包 109 个。【结论与推广】碰到上传速率异常，从服务器、站点告警、传输问题、无线环境、参数配置、现场检查等手段进行分析，逐渐排查出具体原因。