AC:Release 5219 LSUM1WCMX40RT AP:WTU430H直通模式
现场是三层注册,同一个本体下的部分分体可以上线,部分分体无法上线,本体正常上线,故障AP都可以获取到IP地址和AC也可以PING通。
现场有两个AC,在故障分体上指定任意一个AC IP地址后都可以正常注册,option43属性正常下发:display dhcp client verbose,Boot servers: 192.168.113.10 192.168.113.26是正常的。
且所有分体使用的是同一个DHCP服务器。
- *Jan 1 00:08:54:275 2014 H3C CWC/7/SND_PKT: Sent discovery request with SeqNum 0 to AC 192.168.113.10:5246.
- *Jan 1 00:08:54:278 2014 H3C CWC/7/RCV_PKT: Received discovery response with SeqNum 0 from AC at 192.168.113.10:5246.
- *Jan 1 00:08:54:275 2014 H3C CWC/7/SND_PKT: Verbose info for discovery request sent to AC 192.168.113.10:5246, length=158.
- *Jan 1 00:08:54:276 2014 H3C CWC/7/SND_PKT: Sent discovery request with SeqNum 0 to AC 192.168.113.26:5246.
- *Jan 1 00:08:54:279 2014 H3C CWC/7/RCV_PKT: Received discovery response with SeqNum 0 from AC at 192.168.113.26:5246.
- *Jan 1 00:08:54:279 2014 H3C CWC/7/RCV_PKT: Verbose info for discovery response from AC 192.168.113.26:5246, length=128.
- *Jan 1 00:08:56:287 2014 H3C CWC/7/EVENT: AP selected AC IP 192.168.113.26 Priority 4 successfully.
- *Jan 1 00:08:56:287 2014 H3C CWC/7/FSM: Enter Join state.
- *Jan 1 00:08:56:288 2014 H3C CWC/7/EVENT: Fill join req.wtu=1.model=WTU430H.wt drv info:[219801A1ARC178000474].subslot=8.ret=0x0.
- *Jan 1 00:08:56:289 2014 H3C CWC/7/SND_PKT: Sent join request with SeqNum 1 to AC 192.168.113.26:5246.
- *Jan 1 00:08:56:289 2014 H3C CWC/7/SND_PKT: Verbose info for join request sent to AC 192.168.113.26:5246, length=257.
- *Jan 1 00:08:56:290 2014 H3C CWC/7/RCV_PKT: Received join response with SeqNum 1 from AC at 192.168.113.26:5246.
- *Jan 1 00:08:56:290 2014 H3C CWC/7/RCV_PKT: Verbose info for join response from AC 192.168.113.26:5246, length=24.
- *Jan 1 00:08:56:291 2014 H3C CWC/7/ERROR: Failed to process Join Response because Result Code was failure.uiAPID=1,uiResultCode=1.
- *Jan 1 00:08:56:292 2014 H3C CWC/7/EVENT: Close capwap client udp port:27774
- *Jan 1 00:08:56:292 2014 H3C CWC/7/FSM: [Tunnel ID: 1] Join -> Idle.
通过在AP上的debug capwap可以看到,AP同时向两个AC发起discover请求并收到回应,并且向level优先级高的AC发起了join请求,但是join失败。
此时我们发现,在备AC上本体的模板下配置了level 2,本体在主AC正常上线,但是分体在两台AC上都没有配置优先级,分体根据discover回应的信息确认备AC的AP负载小,故向备AC发起join,此时备AC查看本体拓扑关系,本体不在线,故拒绝分体上线。
终结者本体和分体存在对应关系,需要确保AC上其优先级配置一致。