9. 业务故障排错方法

9.业务故障排错方法各业务troubleshooting方法介绍1、pppoe业务的troubleshooting比较常见的报错是678、718、691错误，其中678最复杂。1.1、先说678E3208512DSLAMPC以上图为列，678之所以复杂，是因为在传输的各环节中任何一点出现问题，都可能造成678.●检查思路☆先检查bas，通过bas上的检查来确定下一步检查步骤☆对链路进行检查时，必须在汇聚交换机上进行镜像抓包和隔离传输设备进行测试的方式进行●检查步骤■步骤1——配置成专线☆先把报678错误的pppoe用户配置成专线方式，做ping测试来确定物理链路是通的。☆即使物理链路不存在问题，但报678时，可能是pppoe报文在某环节丢失。troubleshooting■步骤2——在BAS上做pppoe报文分析☆如果原来是动态pppoe配置，先将故障pppoe用户做成静态vlan配置Profilepppoe-testipunnumberedloopback0pppauthenticationpappppoelogpppoeControlPacketppplogppppacketppplogpppstatemachine!interfacegigabitEthernet1/0/1.6950435svlanid695435svlanethertype8100pppoepppoeautoconfigurepppoeprofileanypppoe-test！☆然后让故障用户现场拨号，在bas进行观察E320#shpppoeinterfacegigabitEthernet1/0/1.6950435PPPoEinterfaceGigabitEthernet1/0/1.6950435isoperStatusUp(dynamic)PPPoEinterfaceGigabitEthernet1/0/1.6950435hasmaxsessions=5PPPoEinterfaceGigabitEthernet1/0/1.6950435MTU1494PPPoEinterfaceGigabitEthernet1/0/1.6950435hasnoacNamesetPPPoEinterfaceGigabitEthernet1/0/1.6950435has1activeconnections,outof1configuredsubinterfacesAttachedQoSprofile:qos-subscriber-face@ethernetGigabitEthernet1/0/1NobaselinehasbeensetPPPoEStatisticsCounters:PADIreceived1PADItransmitted0PADOreceived0-PADOtransmitted1●如果PADI为0，就说明用户pppoe请求报文没传到BAS，故障点基本就是出在下层。●前提PADI为1，PADO为0时，则说明BAS出现问题，没有回应PADI报文。troubleshootingPADRreceived1PADRtransmitted0PADSreceived0PADStransmitted1PADTreceived1PADTtransmitted0PADMreceived0PADMtransmitted0PADNreceived0PADNtransmitted0PADpacketsreceived2PADpacketstransmitted2InvalidPADPackets:InvalidVersion0InvalidPADCode0InvalidPADTags0InvalidPADTaglength0InvalidPADType0InvalidPADISession0InvalidPADRSession0InvalidPADpacketlength0InvalidPADpacketsTotalInvalidPADpackets4IngressPolicedPackets0EgressPolicedPackets0InsufficientResources0●PADT可以是用户发出，也可能是bas发出。●invalidPAD出现，则可能是客户端拨号软件设置或者网卡有问题。●Insufficient则表示可能板卡或整机资源耗尽导致troubleshooting●根据pppoe报文的分析结果，采取以下步骤☆BAS上各类PPPOE报文全为0如果在E320上没有看到上述报文，则对汇聚交换机8512与E320直连的端口进行镜像抓包分析。PPPOE协议开始，客户端广播一个发起分组(PADI)，注意PADI为广播报文。镜像示图：PCERXSWethereal被镜像口镜像输出口debugethereal镜像抓包完毕后，基本就能分析出报文丢在何处！！！troubleshooting●E320上抓到的完整pppoe-ppp报文baselinelogE320#shlogdatacategorypppoeControlPacketseverity7deDEBUG01/14/201016:11:46pppoeControlPacket(interface):PADIrxfrom00e0.4dae.22ad,length16,capturedlength68,emptyservicenameDEBUG01/14/201016:11:46pppoeControlPacket(interface):PADOtxto00e0.4dae.22ad,length60,capturedlength88,emptyservicenameDEBUG01/14/201016:11:46pppoeControlPacket(interface):PADRrxfrom00e0.4dae.22ad,length60,capturedlength88,emptyservicenameDEBUG01/14/201016:11:46pppoeControlPacket(interface):PADStxto00e0.4dae.22ad,length60,capturedlength88,connectionmadeusingsessionid14731onsubinterface1shlogdatacategoryppppacketseverity7deDEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.00,txlcpconfReq,id=229,length=18,mru=1492,authentication=pap,magicNumber=0x1e55816bDEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.00,rxlcpconfReq,id=219,length=14,mru=1492,magicNumber=0x051cfd8cDEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.00,txlcpconfAck,id=219,length=14,mru=1492,magicNumber=0x051cfd8cDEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.01,rxlcpconfAck,id=229,length=18,mru=1492,authentication=pap,magicNumber=0x1e55816bDEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.01,rxlcpechoReq,id=0,length=8,magic=0x051cfd8cDEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.01,txlcpechoResP,id=0,length=8,magic=0x1e55816bDEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.01,rxpapauthReq,id=1,length=24,peerIdlength=10,peerId='lsa5472359'6c736135343732333539,passwdlength=8,passwd='16881988'3136383831393838DEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.20,txpapauthAck,id=1,length=5,message,length=0DEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.21,rxipNcpconfReq,id=12,length=22,ipAddress=0.0.0.0,primaryDns=0.0.0.0,secondaryDns=0.0.0.0troubleshootingDEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.21,txipNcpconfNak,id[j1]=12,length=22,ipAddress=125.68.154.236,primaryDns=218.6.200.139,secondaryDns=218.89.0.116DEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.21,rxipNcpconfReq,id=13,length=22,ipAddress=125.68.154.236,primaryDns=218.6.200.139,secondaryDns=218.89.0.116DEBUG01/14/201016:11:46pppPacket(interfaceGigabitEthernet2/1.101090299.113):time:0.21,txipNcpconfAck,id=13,length=22,ipAddress=125.68.154.236,primaryDns=218.6.200.139,secondaryDns=218.89.0.116troubleshooting●镜像后，报文没发现丢失，则问题出在bas上☆我们要通过shell里面去观察动态vlan生成、pppoe报文响应信息等综合判断是板卡故障，还是软件BUG造成。1.2、718问题●718错误含义：等待远程计算机有效响应的连接超时。PPP会话已启动，但由于远程计算机在适当的时间内没有响应而中断。这可能是由于线路质量太差或是由于服务器的问题而导致的。●检查配置，查看配置是否正确和没有遗漏。●在E320上做test测试，确认与radius通信是否正常。ERX320#testaaapppncscjjf654321●bas资源不够也会造成报718错误1.3、691问题●出现691，基本与radius有关系。