《2022年wlan常见问题与解决办法 .pdf》由会员分享，可在线阅读，更多相关《2022年wlan常见问题与解决办法 .pdf（5页珍藏版）》请在taowenge.com淘文阁网|工程机械CAD图纸|机械工程制图|CAD装配图下载|SolidWorks_CaTia_CAD_UG_PROE_设计图分享下载上搜索。
1、WLAN 常见问题和解决办法常见问题之一： 用户无法通过 DHCP 获得地址，从而打不开portal页面解决办法：1 如果以前工作正常，请检查 sscc的连接是否 open wlan#show sscc info The SSC Client is connected to: 221.231.148.166:3288 The SSC Client configured servers are: Primary: 221.231.148.166:3288 Secondary: 221.231.148.169:3288 Tertiary: 0.0.0.0:0 Local Source: loopb
2、ack 0, Local Source Address: 221.231.205.181 The configured transport router is: wlan The configured retry timer is (seconds): 90 The connection state is: Open 然后检查 erx hostname与 SDX 上配的设备名字是否大小写完全一致，尤其要检查是否 erx 管理员曾经修改了ERX 的 hostname, 从而导致 sscc的连接不断被 shudown, sscc的连接状态也一直在变。同时，你可以在/opt/UMC/sae/var/
3、log/sae_error.log中发现如下类似信息：11:40:43.924 CST 29.01.2008 CopsHandler-6/0 xAC000007 JunoseJob 50 Unexpected exception while processing message Message type: 1, ClientType: 32779, Handle: Handle(C-Num=1,C-Type=1,handle=0 xAC000007) PRIs: JunoseIpInterfaceEntry junoseIpInterfacePrid = 6 : InstanceId juno
4、seIpInterfaceIpAddr = dd e7 cd e4 : InetAddress junoseIpInterfaceIpMask = 32 : InetAddressPrefixLength junoseIpInterfaceBroadcastAddr = ff ff ff ff : InetAddress junoseIpInterfaceMtu = 1500 : Integer32 junoseIpInterfaceVirtualRouterName = wlannj-gl-erx1440:77 6c 61 6e 40 6e 6a 2d 67 6c 2d 65 72 78 3
5、1 34 34 30 : DisplayString junoseIpInterfaceName = loopback0:6c 6f 6f 70 62 61 63 6b 30 : DisplayString junoseIpInterfaceIfIndex = 2931 : Unsigned32 junoseIpInterfaceLoginName = : : DisplayString junoseIpInterfaceUserIpAddr = 0 0 0 0 : InetAddress junoseIpInterfaceSpeed = 0 : Unsigned64 junoseIpInte
6、rfaceIfDesc = loopback0:6c 6f 6f 70 62 61 63 6b 30 : DisplayString junoseIpInterfaceIfAlias = : : DisplayString junoseIpInterfaceNasPortId = loopback0:6c 6f 6f 70 62 61 63 6b 30 : DisplayString junoseIpInterfaceRadiusClass = : : DisplayString junoseIpInterfaceSaeVsasVal = 1 61 63 63 74 53 65 73 73 4
7、9 64 1f 1e 73 65 72 76 69 63 65 42 75 6e 64 6c 65 1f : OctetString junoseIpInterfaceCapabilitiesVal = 4 : Bits junoseIpInterfaceNasPort = 0 : Unsigned32 junoseIpTunnelServerIpAddr = 0 0 0 0 : InetAddress junoseIpTunnelServerIpMask = 0 : InetAddressPrefixLength junoseIpTunnelId = 0 : Unsigned32 junos
8、eIpSessionId = 0 : Unsigned32 junoseIpInterfaceIfType = 1 : JunoseTargetInterfaceType , exception java.lang.IllegalArgumentException : VirtualRouterName field of interface entry differs from the device name; shutting down driver; stack trace: java.lang.IllegalArgumentException: VirtualRouterName fie
9、ld of interface entry differs from the device name at net.juniper.smgt.sae.router.junose.state.e.(JunosEIcc.java:41) at net.juniper.smgt.sae.router.junose.e.do(IpInterfaceCtx.java:547) at net.juniper.smgt.sae.router.junose.z.if(UnsolicitedMessage.java:338) at net.juniper.smgt.sae.router.junose.u.run
10、Job(JunoseJob.java:127) at net.juniper.smgt.lib.scheduler.Job.run(Job.java:38) at edu.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748) at java.lang.Thread.run(Thread.java:595) 如果是这样，那么只需在ERX 上删除原有的 SSCC和 DHCP 的配置，重新配置SSCC和 DHCP 名师资料总结 - - -精品资料欢迎下载 - - - - - - - - - -
11、- - - - - - - - 名师精心整理 - - - - - - - 第 1 页，共 5 页 - - - - - - - - - 2 检查用户所在的VLAN 子接口是否已被 SDX 管理，用 show ip int gi4/1.10010001,看看是否有 SDX 下发的策略，如果没有，那么需要让SDX 管理员将该接口加入管理E320-01:wlan#show ip int gi 16/0/0.2264003 GigabitEthernet16/0/0.2264003 line protocol VlanSub is up, ip is up Network Protocols: IP U
12、nnumbered Interface on loopback1 ( IP address 121.229.250.1 ) Operational MTU = 1500 Administrative MTU = 0 Operational speed = 1000000000 Administrative speed = 0 Discontinuity Time = 2479568161 Router advertisement = disabled Proxy Arp = enabled Network Address Translation is disabled TCP MSS Adju
13、stment = disabled Administrative debounce-time = disabled Operational debounce-time = disabled Access routing = disabled Multipath mode = hashed Auto Configure = enabled, Exclude Primary Auto Detect = disabled Inactivity Timer = disabled Warm-restart initial-sequence-preference: Operational = 0 Admi
14、nistrative = 0 In Received Packets 2046656, Bytes 921470728 Unicast Packets 2041821, Bytes 920003037 Multicast Packets 4835, Bytes 1467691 In Policed Packets 264, Bytes 31491 In Error Packets 10 In Invalid Source Address Packets 0 In Discarded Packets 738 Out Forwarded Packets 1890, Bytes 1088640 Un
15、icast Packets 1890, Bytes 1088640 Multicast Routed Packets 0, Bytes 0 Out Scheduler Dropped Packets 0, Bytes 0 Out Policed Packets 0, Bytes 0 Out Discarded Packets 4 IP policy input P134-899 classifier-group C134-1327 entry 1 12420 packets, 2322350 bytes forward IP policy output P134-900 classifier-
16、group C134-1334 entry 1 1812 packets, 1088808 bytes forward queue 0: traffic class best-effort, bound to ip GigabitEthernet16/0/0.2264003 Queue length 0 bytes Forwarded packets 0, bytes 0 Dropped committed packets 0, bytes 0 Dropped conformed packets 0, bytes 0 3 打开 erx上关于 dhcp的 debug log, 看看 ERX 是否
17、已发送 offer 给用户，同时在用户终端抓包，看看是否终端已经收到该offer interface gigabitEthernet 16/0/0.22620002 ! svlan id 2262 2 svlan ethertype 8100 ip auto-configure ip-subscriber exclude-primary ip unnumbered loopback 1 ip dhcp-capture all log sev 7 cate dhcpCapture show log data cate dhcpCapture sev 7 delta 名师资料总结 - - -精品资
18、料欢迎下载 - - - - - - - - - - - - - - - - - - 名师精心整理 - - - - - - - 第 2 页，共 5 页 - - - - - - - - - 4如果 ERX 发生 crash或其他软硬件故障后出现的无法获得IP 的故障，那么请删除 ERX 上 SSCC和 DHCP配置，重新再做一遍常见问题之二：用户获得地址无需认证直接上网解决办法：首先检查ERX 上用户接口 IPx.x.x.x 是否有 P 开头的策略，尤其要检查next-hop的那一个 classifier的流量统计是否在增加，如果有增加，那么检查隧道是否 up. (show ip static),
19、 再检查路由表，是否有到next-hop的路由。E320-01:wlan#show ip int ip121.229.250.55 ip121.229.250.55 line protocol VlanSub is up, ip is up Network Protocols: IP Layer 2 interface GigabitEthernet16/0/0.22620004 Unnumbered Interface: Corresponding Numbered Interface not specified or removed Operational MTU = 1500 Admin
20、istrative MTU = 0 Operational speed = 1000000000 Administrative speed = 0 Discontinuity Time = 3396519345 Router advertisement = disabled Proxy Arp = enabled Network Address Translation is disabled TCP MSS Adjustment = disabled Administrative debounce-time = disabled Operational debounce-time = disa
21、bled Access routing = enabled: Using 0.0.0.0 Multipath mode = hashed Auto Configure = disabled Auto Detect = disabled Inactivity Timer = disabled Warm-restart initial-sequence-preference: Operational = 0 Administrative = 0 In Received Packets 490, Bytes 57566 Unicast Packets 487, Bytes 56540 Multica
22、st Packets 3, Bytes 1026 In Policed Packets 7, Bytes 294 In Error Packets 0 In Invalid Source Address Packets 0 In Discarded Packets 0 Out Forwarded Packets 759, Bytes 639711 Unicast Packets 759, Bytes 639711 Multicast Routed Packets 0, Bytes 0 Out Scheduler Dropped Packets 0, Bytes 0 Out Policed Pa
23、ckets 0, Bytes 0 Out Discarded Packets 2 IP policy input P134-19412 classifier-group C134-2578 entry 1 4 packets, 353 bytes forward classifier-group C134-2580 entry 1 0 packets, 0 bytes forward classifier-group C134-2582 entry 1 33 packets, 12144 bytes forward classifier-group C134-2581 entry 1 412
24、packets, 52690 bytes forward classifier-group C134-2579 entry 1 0 packets, 0 bytes forward classifier-group C134-2688 entry 1 24 packets, 3105 bytes forward classifier-group C134-2577 entry 1 10 packets, 1538 bytes 名师资料总结 - - -精品资料欢迎下载 - - - - - - - - - - - - - - - - - - 名师精心整理 - - - - - - - 第 3 页，共
25、 5 页 - - - - - - - - - next-hop 221.231.148.153 classifier-group C134-1327 entry 1 7 packets, 476 bytes filter IP policy output P134-19413 classifier-group C134-2689 entry 1 325 packets, 263212 bytes forward classifier-group C134-2583 entry 1 801 packets, 813332 bytes forward queue 0: traffic class
26、best-effort, bound to ip ip121.229.250.55 Queue length 0 bytes Forwarded packets 724, bytes 638375 Dropped committed packets 0, bytes 0 Dropped conformed packets 0, bytes 0 Dropped exceeded packets 0, bytes 0 E320-01:wlan#show ip static Prefix/Length Next Hop Dst/Met Tag Intf Verify - - - - - - 221.
27、231.148.153/32 10.255.4.89 100/0 0 TUNNEL dvmrp:2 200 up 221.231.148.153/32 10.255.0.89 10/0 0 TUNNEL dvmrp:1 100 up 常见问题之三：用户无法通过认证解决办法：首先在SDXadmin 里面检查是否该用户的IP 已经发布在那个 ERX 的pool 里，如果没有，就需要用update pool去更新。大约 15-30s以后用户就能通过认证了。如果发现有该pool, 但是用户还是无法通过认证，那么有可能是一下几种情况1 检查/opt/UMC/nic/var/log/nicdebug.lo
28、g, 看看该用户的请求是不是被successfully resolved. 14:47:57.767 CST 02.02.2008 RequestProcessor-8 NicHost 10 Received request for realm ip 14:47:57.768 CST 02.02.2008 RequestProcessor-8 MetaGraph 10 Attempting to find a path for (Ip,SaeId). Constraints are IpPool 14:47:57.768 CST 02.02.2008 RequestProcessor-8 Me
29、taGraph 10 Attempting to find a path for (Ip,IpPool). Constraints are 14:47:57.768 CST 02.02.2008 RequestProcessor-8 ResolutionEngine 10 Engine received a resolution request ip 14:47:57.768 CST 02.02.2008 RequestProcessor-8 MetaGraph 10 Attempting to find a path for (Ip,SaeId). Constraints are IpPoo
30、l 14:47:57.768 CST 02.02.2008 RequestProcessor-8 MetaGraph 10 Attempting to find a path for (Ip,IpPool). Constraints are 14:47:57.769 CST 02.02.2008 RequestProcessor-8 ResolutionEngine 10 The following path was found to resolve ip:, -pick_1 14:47:57.769 CST 02.02.2008 RequestProcessor-8 ResolutionEn
31、gine 10 Servers /realms/ip/A1 were selected to resolve edge . 14:47:57.769 CST 02.02.2008 RequestProcessor-8 ResolutionEngine 10 Servers /realms/ip/B1 were selected to resolve edge 14:47:57.769 CST 02.02.2008 RequestProcessor-8 ResolutionEngine 10 Servers /realms/ip/C1 were selected to resolve edge
32、pick_1. 14:47:57.770 CST 02.02.2008 RequestProcessor-8 ResolutionEngine 10 Engine successfully resolved request ip constraints= IpPool:(0.0.0.0 0.0.0.0117.88.10.0 117.88.11.255), Vr:webNJ-HanZM-B-E320-01 steps = ip, ip, ip 14:47:57.770 CST 02.02.2008 RequestProcessor-8 NicSM 10 NicHostMIData: Total
33、Resolution Time = 688 如果不是，那么可以通过重起NIChost : /opt/UMC/nic/etc/nichost restart 名师资料总结 - - -精品资料欢迎下载 - - - - - - - - - - - - - - - - - - 名师精心整理 - - - - - - - 第 4 页，共 5 页 - - - - - - - - - 2 如果 nicdebug.log根本没有收到 NIC 请求，那么需要检查portal 程序是否运行正常3 检查 /opt/UMC/sae/var/log/sae_debug.log, 看看是否收到来自portal的认证请求（C
34、oreApi: login）,如果收到了请求，那么检查是否有radius返回的认证失败的信息，如果没有收到portal 的认证请求，请检查portal 的程序运行是否正常08:57:14.832 CST 03.02.2008 CoreApi1143:login LoginRequest 10 Authenticating via retailer retailername=default,o=Users,o=UMC 08:57:14.832 CST 03.02.2008 CoreApi1143:login EventPublisher 10 publish authorize event to
35、 flexRadiusAuth 08:57:14.832 CST 03.02.2008 AuthQueue-2 PublisherQueue 10 AuthQueue-2 executing job 08:57:14.834 CST 03.02.2008 CoreApi1143:login LoginRequest 10 Login attempt failed: net.juniper.smgt.sae.session.o:xxxxxxxxxxxx08:57:14.834 CST 03.02.2008 CoreApi1143:login SAE-AUDIT: 30 User Login De
36、nied,chinatelecom,ip61.174.118.97,VR_WLANQZ-QZ-XDL-B AS-ERX1440-1.MAN,61.174.118.97,xxxxxxxxxxxxxxx x 4 检查 portal 和 SDX 服务器是否使用同一个NTP服务器。# ntpq ntpq peers remote refid st t when poll reach delay offset disp = *202.96.216.160 202.109.93.50 2 u 161 1024 377 60.84 -3.935 10.88 +61.152.71.244 202.109.93
37、.50 2 u 720 1024 377 7.34 -30.317 11.76 如果两者之间出现时间偏差，很容易引起比较奇怪的问题常见问题之四：用户无法logout 解决办法：检查 nicdebug.log是否收到用户 IP的请求，如果没有，请检查portal 程序。如果有，看看是否正确解析（参见问题3）常见问题之五：用户能获得IP 地址，但是无法打开portal 网页解决方法：检查用户接口下是否有正常的SDX 下发的策略。如果有，检查是否到next-hop的流量统计在增加。如果没有流量在增加，则说明2层的通信有问题。如果是有些 pc可以，有些 pc 不行，（可能下层设备作了链路捆绑，把流量发到其他地方了）。名师资料总结 - - -精品资料欢迎下载 - - - - - - - - - - - - - - - - - - 名师精心整理 - - - - - - - 第 5 页，共 5 页 - - - - - - - - -