WAP业务失败问题案例

1、wap业务失败问题案例一. 问题描述2009年3月25 , 26日在ggsn5下所有测试点测试经常出现wap业务失败，失败率约 20%左右。二. 问题分析从ip协议分析，终端向wapgw 10.0.0.172发送wsp connect请求与网关建立连接，wapgw 10.0.0.172 一直没有响应，终端重发8次wsp connect仍无响应，连接超时中 断：17:32:3&905 17:32:42.108 17:32:47.311 17:32:52.514 17:32:57.718 17:33:02.92117:33:08.12417:33:13.32717:33:l&530

2、10.9.123.16810.9.123.16810.9.123.16810.9.123.16810.9.123.16810.9.123.16810.9.123.16810.9.123.16810.9.123.16810.0.0.17210.0.0.17210.0.0.17210.0.0.17210.0.0.17210.0.0.17210.0.0.17210.0.0.17210.0.0.172ipipipipipip1pipipv/tphvsp 1170v/tp4-wsp 1170v/tphvsp 1170v/tphvsp 1170v/tp+vysp 1170wtp+wsp 1170v/tph

3、7sp 1170wtp+wsp 1170v/tp-bwsp 11709201 9201 9201 9201 9201 9201 9201 92019201654654654654654654654654654wsp connect (0x01)vvsp connect (0x01；wsp connect (0x01)wsp connect (0x01)wsp connect (0x01)wsp connect (0x01)wsp connect (0x01)wsp connect (0x01)终端(10.9.123.168) 一直 向 10.0.0.172 发送 w5p connectir求，

4、但没有得 到响应，最后超时失17:33:24.733 20:53:45:4e:. 20:53:45:4e： ip ppp lcptermination request13:21:32.030 ps attach success 13:21:34.702 pdp activate success 13:22:21733|btm' ©tu ; 13:22:21.733|',匚匚q p13:22:23.827 ps detached具体测试记录如下：0.76s (165 frames)0.54s (117 frames)#3wapgw连接失败，导致梦 网首页登陆尖败。测试时

5、间测试点lac查资料对应 ggsn测试情况3月25日国门酒店9494ggsn5出现 2 次 wap gateway connect fail马赛国际公寓9732ggsn5出现 1 次 wap gateway connect fail数码港国际酒店9493ggsn5出现多次 wap gateway connect fail卜蜂莲花车陂店9493ggsn5出现 3 次 wap gateway connect fail3月26日华师地铁站9999ggsn5出现 2 次 wap gateway connect fail大舜晶华酒店9478ggsn6出现 4 次 wap gateway connect

6、fail广东蓄能大厦9474ggsn5出现 1 次 wap gateway connect fail林和西地铁站9999ggsn5出现 2 次 wap gateway connect fail三、gn 口抓包在gn接口查询其中一次通信过程，发现已转发终端(10.10.100.146 )向10.0.0.172发送wsp connect请求，但10.0.0.172侧没有响应，最后终端发起pdp去激活请求。no. . timesourcedestinati onprotocolgtp2 2009-03-2515:07:53221.177.76.81221.177.76.43 2009-03-2515

7、:07:54221.177.76.21221.177.76.864 2009-03-2515:0:545 2009-03-2515:07:5410.10.100.146239.255.255.250udp6 2009-03-2515:07:5410.10.100.14610.0.0.1727 2009-03-2515:07:55221.177.76.218 2009-03-2515:07:58gtpgtp10.10.100.146255.255.255.255 bootp221.177.76.8610.10.100.146255.255.255.255infocreate pop contex

8、t responset-pdumalformed packetnalforred packetsource port: cmadmin destination port: ssdp gtp <?/tp+wsp> wsp connect (0x01)239.255.255.250 udp9 2009-03-2515:07:5810.10.100.14610 2009-03-2515:08:0010.10.100.14610.0.0.17211 2009-03-2515:08:0010.10.100.146239.255.255.250 udp12 2009-03-2515:08:05

9、10.10.100.14610.0.0.17213 2009-03-2515:08:1010.10.100.14610.0.0.17214 2009-03-2515:08:1610.10.100.14610.0.0.1'?10.10.100.14610.0.0.172gtptpduh<alformed packetbootpmalformed packetsource port: cmadmin destination port: ssdp gtp <wtp+wsp> wsp connect (0x01)source port: cmadmin destination

10、 port: ssdp15 2009-03-25 15:08:21ib mbb-ibbb5 15sqhebhh10.10.100.14610.0.0.17217 2009-03-2515:08:3110.10.100.14610.0.0.17218 2009-03-2515:08:3610.10.100.14610.0.0.17219 2009-03-2515:08:42221.177.76.4221.177.76.8220 2009-03-2515:08:42221.177.76. 82 221.177.76.4connect (0x01)connect (0x01)connect (0x0

11、1) connect (0x01)(0x01) gtp <>/tp+wsp> wsp connect (0x01) gtp <?/tp+h5p> w5p connect (0x01)delete pdp context request delete pdp context responsegtp <wtp+wsp> wsp gtp v?/tp+rsp> wsp gtp v打tp+0sp> ssp gtp <?/tp+wsp> wspgtp <?rrp+wsp> wsp connectgtpgtp四. gi 口外侧抓包

12、在gi防火墙外侧对wap gateway connect fail进行抓包，发现同样已转发终端向10.0.0.172 发送 wsp connect 请求，但 10.0.0.172 侧没有响应。五. 问题定位通过抓包定位，wap gateway connect fail是在gi 口外侧至wapgw侧网段引起。六. 问题跟踪问题上报wapgw厂家，3月27日厂家对ggsn5的wapgw进行检查,发现gzwap02bnk( ggsn5的wapgw )的其中某一个设备老化出现故障。厂家处理后进行多次wapgw连接测试再无wap gateway connect fail发生。09:40:23.671 a

13、te item begin 09:40:24.905 ps attach success 09:40:27.499 pdp activate success 09:40:28.452 wap gateway connected 09:40:31.592 ps detached 09:40:33.530 ate item end 09:40:36.530 ate item begin 09:40:51.530 ate item end 09:40:54.530 ate item begin 09:40:55.889 ps attach success 09:40:58.842 pdp activate success 09:40:59.717 wap gatev/ay connected 09:41:44.139 ate item end 09:41:47.1