ME60 BAS业务trace跟踪专题 V1.0.docVIP

ME60 BAS业务Trace跟踪专题文档密级：内部公开资料编码产品名称使用对象产品版本编写部门资料版本ME60 BAS业务Trace跟踪专题拟 制：于博日 期：2010-05-30审 核：日 期：审 核：日 期：批 准：日 期：华 为 技 术 有 限 公 司版权所有 侵权必究修订记录日期修订版本描述作者2010-05-30V1.0于博ME60 BAS业务trace 跟踪专题1.1 命令介绍trace object 命令，与debug命令类似，用于跟踪base业务用户上线过程，记录用户上线轨迹。使用该命令可以快速准确的找到故障点，是定位bas业务故障最有效的定位工具。trace object mac-address 按用户MAC进行跟踪，使用该命令可以对单个用户进行跟踪，trace object user-name 按用户名进行跟踪，跟踪对应用户名的所有用户trace object user-vlan 按vlan进行跟踪，跟踪该VLAN下的所有用户trace object qinq-vlan 按外层VLAN进行跟踪，跟踪该外层VLAN下的所有用户trace object ip-address 按IP 地址进行跟踪trace object interface 按接口进行跟踪，跟踪该接口下所有用户，该接口包括所有支持bas业务的接口。1.2 trace 跟踪记录分析1、radius 服务器不响应“Failed to authenticate because failure to send request packet to RADIUS server(UserID = 12, Code = 1254)”Radius Sent a Packet Server Template: 0 Server IP : 192.168.77.111 Vpn-Instance: - Protocol: Standard Code : Authentication request Len : 283 ID : 11 User-Name(1) 9 kkkkkk 。 。 。 -2009/11/4 15:8:34-RADIUS0023-cd8e-b541: Radius Sent a Packet Server Template: 0 Server IP : 192.168.77.111 Vpn-Instance: - Protocol: Standard Code : Authentication request Len : 283 ID : 11 User-Name(1) 9 kkkkkk 。 。 。 -2009/11/4 15:8:39-RADIUS0023-cd8e-b541: Radius Sent a Packet Server Template: 0 Server IP : 192.168.77.111 Vpn-Instance: - Protocol: Standard Code : Authentication request Len : 283 ID : 11 User-Name(1) 9 kkkkkk 。 。 。 RDS(Event): Send a message(Send Fail) 2009/11/4 15:8:44-AAA0023-cd8e-b541:Receive notify of message send fail from RADIUS successfully(UserID = 12, source message = AAA-Radius authen request) 2009/11/4 15:8:44-AAA0023-cd8e-b541:Failed to authenticate because failure to send request packet to RADIUS server(UserID = 12, Code = 1254) 如上面的trace信息所示，ME60一直在发送“Radius Sent a Packet”报文（3次），却一直收不到radius回应，导致认证失败而无法上线。这种情况一般有以下几种原因：1）、ME60与radius服务器之间链路故障。排查方法：检查ME60与radius服务器之间的链路，查看链路上的接口是否都UP，链路上的接口是否有错包，尝试ping radius服务器IP，看能否ping通。2）、Radius服务器配置问题。排查方法：检查radius服务器是否绑定了正确的ME60的IP地址，配置的端口号是否正确。3）、ME60配置问题。排查方法：检查ME60配置，是否配置了正确的“radius-server group”组，组下是否绑定了正确的radius服务器的IP地址，端口号是否正确，共享密钥是否正确。2、地址池满，无法获取IP地址“Failed to allocate IP address for CM”2009/11/4 14:56:20-CM0023-cd8e-b541:Send AM_IP_REQ to AM (userid:6 slot:0) 2009/11/4 14:56:20-AM0023-cd8e-b541:Receive IP address request from CM successfully( pool ID = 1 ) 2009/11/4 14:56:20-AM0023-cd8e-b541:Failed to allocate IP address for CM 2009/11/4 14:56:20-CM0023-cd8e-b541:Receive AM_IP_ACK from AM (userid:6 Slot:-1) 如上面的trace信息“Failed to allocate IP address for CM”。这种情况是由于地址池里的地址用完了，新用户无法获取到IP地址，导致无法上线。解决方法为，增加IP地址池即可。3、开始计费报文失败“Make user offline because Fail to start accounting(UserID = 12, Code = 2625)” Radius Sent a Packet Server Template: 0 Server IP : 192.168.70.223 Vpn-Instance: - Protocol: Standard Code : Acct req Len : 283 ID : 0 User-name(1) 9 kkkkkk 。 。 。 Radius Sent a Packet Server Template: 0 Server IP : 192.168.70.223 Vpn-Instance: - Protocol: Standard Code : Acct req Len : 283 ID : 0 User-name(1) 9 kkkkkk 2009/11/4 16:3:40-RADIUS0023-cd8e-b541: RDS(Evt): Send a msg(Send Fail) 2009/11/4 16:3:40-AAA0023-cd8e-b541:Receive notify of message send fail from RADIUS successfully(UserID = 12, soruce message = AAA-Radius acct stop request) 2009/11/4 16:3:40-AAA0023-cd8e-b541:Make user offline because Fail to start accounting(UserID = 12, Code = 2625) 如上面的trace信息，发送了多个开始计费报文给radius，但始终收不到radius回应，导致因开始计费失败而用户无法上线。这种情况有以下几种原因：1）、ME60与radius服务器之间链路故障。排查方法：检查ME60与radius服务器之间的链路，查看链路上的接口是否都UP，链路上的接口是否有错包，尝试ping radius服务器IP，看能否ping通。2）、Radius服务器配置问题。排查方法：检查radius服务器是否绑定了正确的ME60的IP地址，配置的端口号是否正确。3）、ME60配置问题。排查方法：检查ME60配置，是否配置了正确的“radius-server group”组，组下是否绑定了正确的radius服务器的IP地址，端口号是否正确。 4、bas接口配置错误“Fail to process pppoe access for VC not permit”2009/11/4 15:41:54-PPP0023-cd8e-b541:LCP negotiate successfully, start PAP/CHAP negotiate 2009/11/4 15:41:54-CM0023-cd8e-b541:Fail to process pppoe access for VC not permit 2009/11/4 15:41:54-PPP0023-cd8e-b541:Received chap authentication packet in authentication phase 2009/11/4 15:41:54-PPP0023-cd8e-b541:Received failed authentication ack message from ucm 如上trace信息，是由于bas接口配置错误导致，PPPOE用户应该配置为二层接入，检查bas接口，确认是否配置正确。5、license 限制导致无法上线“Fail to alloc cib for license or table full”-2009/11/4 15:34:5-PPP0023-cd8e-b541:LCP negotiate successfully, start PAP/CHAP negotiate -2009/11/4 15:34:5-CM0023-cd8e-b541:Fail to alloc cib for license or table full -2009/11/4 15:34:5-PPP0023-cd8e-b541:Received pap authentication packet in authentication phase -2009/11/4 15:34:5-PPP0023-cd8e-b541:Received failed authentication ack message from ucm 如上trace信息，由于license限制导致用户无法上线，这种情况是由于用户上线数量超过了license限制的规格导致，解决方法为，重新申请license，增加用户数量。6、获取不到VT模板“Fail to get Virtual-Template(User MAC Address:0023:cd8e:b541)”-2009/11/4 15:39:59-PPPOE0023-cd8e-b541:Fail to get Virtual-Template(User MAC Address:0023:cd8e:b541) -2009/11/4 15:40:4-PPPOE0023-cd8e-b541:Fail to get Virtual-Template(User MAC Address:0023:cd8e:b541)如上面的trace信息，是由于BAS接口没有捆绑VT模板导致，只有PPPOE用户需要配置VT模板。检查对应的bas接口，重新绑定VT接口就可以解决。7、域下没有配置radius服务器组“Failed to get the valid server template(UserID = 4, Code = 9184)” -2009/11/4 14:50:1-AAA0023-cd8e-b541:Receive authentication request from UCM successfully(UserID = 4) -2009/11/4 14:50:1-AAA0023-cd8e-b541:Failed to get the valid server template(UserID = 4, Code = 9184) -2009/11/4 14:50:1-AAA0023-cd8e-b541:Failed to send authentication request(UserID = 4, Code = 4112) -2009/11/4 14:50:1-AAA0023-cd8e-b541:Send authentication ack to UCM successfully(UserID = 4, Result = SRV_AUTH_FAIL) -2009/11/4 14:50:1-CM0023-cd8e-b541:Receive AAA_AUTH_ACK from AAA (userid:4 Slot:0) -2009/11/4 14:50:1-CM0023-cd8e-b541:CM StateCib:4 Event:AUTH_FAIL State From AUTH BUTT To ALLOC BUTT -2009/11/4 14:50:1-CM0023-cd8e-b541:Send PPP_AUTH_ACK to PPP (userid:4 slot:1) -2009/11/4 14:50:1-PPP0023-cd8e-b541:Received failed authentication ack message from ucm 如上面的trace信息，是由于域下没有配置radius-server group 导致因找不到radius认证服务器，用户上线失败。解决方法为，检查对应的域下配置，配置正确的radius服务器组就可以解决。8、域下没有配置地址池“No usable ip pool” -2009/11/4 14:46:58-AAA0023-cd8e-b541:Iptv shapping closed, so neednt to add physical info hash. -2009/11/4 14:46:58-AAA0023-cd8e-b541:Send authentication ack to UCM successfully(UserID = 3, Result = SRV_AUTH_PASS) -2009/11/4 14:46:58-CM0023-cd8e-b541:Receive AAA_AUTH_ACK from AAA (userid:3 Slot:0) -2009/11/4 14:46:58-CM0023-cd8e-b541:No usable ip pool -2009/11/4 14:46:58-CM0023-cd8e-b541:CM StateCib:3 Event:CONN_DOWN State From AUTH BUTT To DELETING BUTT 如上面的trace信息，是由于域下没有配置地址池导致无法获取IP地址，用户无法上线。解决方法为检查对应的域配置，绑定正确的的地址池即可。9、L2tp用户隧道密码不一致“Failed to analyze LNS packet(callid=8,reasoncode=30)” -2009/11/5 15:31:25-L2TP0023-cd8e-b541:Send SCCRQ to LNS (userid=204,callid=8,tunnelid=20) -2009/11/5 15:31:25-PPP0023-cd8e-b541:Send l2tp up message successfully -2009/11/5 15:31:25-L2TP0023-cd8e-b541:Failed to analyze LNS packet(callid=8,reasoncode=30) -2009/11/5 15:31:27-PPP0023-cd8e-b541:Received chap authentication packet in authentication phase 如上面的trace信息，是由于隧道密码不一致导致隧道无法建立，用户无法上线。解决方法为，检查LAC 和LNS两边的l2tp-group配置，把tunnel password 修改一致即可。10、L2tp用户LNS绑定的LAC名不正确“Failed to get tunnel for this user(userid=207,callid=11)”-2009/11/5 15:40:54-PPP0023-cd8e-b541:Received chap authentication packet in authentication phase -2009/11/5 15:40:56-PPP0023-cd8e-b541:Received chap authentication packet in authentication phase -2009/11/5 15:40:56-L2TP0023-cd8e-b541:Failed to get tunnel for this user(userid=207,callid=11) -2009/11/5 15:40:56-PPP0023-cd8e-b541:Received L2TP session ack message -2009/11/5 15:40:56-PPP0023-cd8e-b541:Failed to create L2TP session and notify server user down 如上面的trace信息，是由于LNS设备上l2tp-group组下绑定远端LAC设备的名字与LAC设备上L2tp-group组下，配置的tunnel name 名字不一致。解决方法为检查LNS设备，把l2tp-group组下绑定的LAC名字修改一致即可。11、没有配置static-user导致静态用户无法上线 2009/11/7 10:15:51-CM0023-cd8e-b541:Fail to process ip(arp) connect request for check ip error2009/11/7 10:15:52-CM0023-cd8e-b541:Fail to process ip(arp) connect request for check ip error2009/11/7 10:15:53-CM0023-cd8e-b541:Fail to process ip(arp) connect request for check ip error如上面的trace信息，是由于没有配置static-user，导致arp探测失败，静态用户无法上线，解决方法为重新配置正确的static-user。12、静态用户static-user配置错误“Fail to get the valid server template to use(UserID = 212, Code = 7907)” -2009/11/7 10:30:52-CM0023-cd8e-b541:Receive IP_CONN_REQ from SAM (userid:212) -2009/11/7 10:30:52-CM0023-cd8e-b541:Send AAA_AUTH_REQ to AAA (userid:212 slot:0) -2009/11/7 10:30:52-AAA0023-cd8e-b541:Receive authentication request from UCM successfully(UserID = 212) -2009/11/7 10:30:52-AAA002