I have two sites, one in England, one in Houston. The site in England has a 4404
(10.160.104.187), running against an anchor controller in Houston (10.32.210.251), that
provides internet access for guest users, running 4.2.112.0. Up until the last few days,
it worked without issue. Now, the control channel will not come up, although the data
channel is fine.
From the Houston 4404:
(uscy1wc-air011) >mping 10.160.104.187
Send count=3, Receive count=0 from 10.160.104.187
(uscy1wc-air011) >show msglog
Message Log Severity Level ...................... VERBOSE
00:0b:7d:0f:38:75 Ignoring Announce, client record for
not found
Wed Sep 17 15:54:57 2008: Mobility packet received from:
Wed Sep 17 15:54:57 2008: 10.160.104.185, port 16666
Wed Sep 17 15:54:57 2008: type: 3(MobileAnnounce) subtype: 0 version: 1 xid
: 13224 seq: 17332 len 116 flags 0
Wed Sep 17 15:54:57 2008: group id: aa7a4fec 6bf5225c d25d6e98 b17ac701
Wed Sep 17 15:54:57 2008: mobile MAC: 00:0b:7d:0f:38:75, IP: 0.0.0.0, instance
: 0
Wed Sep 17 15:54:57 2008: VLAN IP: 10.160.191.242, netmask: 255.255.255.0
Wed Sep 17 15:54:57 2008: Switch IP: 10.160.104.185
Wed Sep 17 15:54:57 2008: 00:0b:7d:0f:38:75 Ignoring Announce, client record for
not found
(uscy1wc-air011) show>mobility sum
Symmetric Mobility Tunneling (current) .......... Enabled
Symmetric Mobility Tunneling (after reboot) ..... Enabled
Mobility Protocol Port........................... 16666
Mobility Security Mode........................... Disabled
Default Mobility Domain.......................... BG
Mobility Keepalive interval...................... 10
Mobility Keepalive count......................... 3
Mobility Group members configured................ 3
Controllers configured in the Mobility Group
MAC Address IP Address Group Name Status
00:18:ba:49:ab:40 10.160.104.187 BG Control Path Down
00:1c:58:8a:b4:a0 10.160.104.185 BG Control Path Down
00:1e:be:7a:b8:c0 10.32.210.251 BG Up
(uscy1wc-air011) show>mobility stat
Global Mobility Statistics
Rx Errors .................................... 0
Tx Errors .................................... 0
Responses Retransmitted ...................... 0
Handoff Requests Received .................... 388
Handoff End Requests Received ................ 0
State Transitions Disallowed.................. 0
Resource Unavailable.......................... 0
Mobility Initiator Statistics
Handoff Requests Sent ........................ 0
Handoff Replies Received ..................... 0
Handoff as Local Received .................... 0
Handoff as Foreign Received .................. 0
Handoff Denys Received ....................... 0
Anchor Request Sent .......................... 0
Anchor Deny Received ......................... 0
Anchor Grant Received ........................ 0
Anchor Transfer Received ..................... 0
Mobility Responder Statistics
Handoff Requests Ignored ..................... 388
Ping Pong Handoff Requests Dropped ........... 0
--More-- or (q)uit
Handoff Requests Dropped ..................... 0
Handoff Requests Denied ...................... 0
Client Handoff as Local ...................... 0
Client Handoff as Foreign ................... 0
Client Handoff Inter-Group .................. 0
Anchor Requests Received ..................... 0
Anchor Requests Denied ....................... 0
Anchor Requests Granted ...................... 0
Anchor Transferred ........................... 0
(uscy1wc-air011) show>
Given what I see, I think that the anchor control is rejecting the requests for some
reason.
