cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1675
Views
14
Helpful
5
Replies

Does vWLC support for new mobility ?

Rasika Nayanajith
VIP Mentor VIP Mentor
VIP Mentor

To test the CA mobility, I have configured mobility between vWLC (running on 7.6.100.0) & a 5760. I can see UDP 16666/16667 port communication between the two controllers (vWLC - 10.129.0.7, 5760-10.160.49.1), but still control path is down.

(vWLC) >show mobility summary

New Mobility (Converged Access).................. Enabled

Mobility Protocol Port........................... 16666

Default Mobility Domain.......................... BUN-1

Multicast Mode .................................. Disabled

DTLS Mode ....................................... Enabled

Mobility Domain ID for 802.11r................... 0xd3ca

Mobility Keepalive Interval...................... 10

Mobility Keepalive Count......................... 3

Mobility Group Members Configured................ 2

Mobility Control Message DSCP Value.............. 0

Mobility MC public IP ........................... 10.129.0.7

Mobility Oracle IP address ...................... 0.0.0.0

Controllers configured in the Mobility Group

IP Address       Public IP Address       Group Name         Multicast IP  MAC Address               Status

10.129.0.7       10.129.0.7                 BUN-1            0.0.0.0         00:50:56:b9:33:e9          Up

10.160.49.1      10.160.49.1                BUN-1            0.0.0.0         44:ad:d9:03:9d:00  Control Path Down

(vWLC) >mping 10.160.49.1

Send count=3, Receive count=3 from 10.160.49.1

5760-1#show wireless mobility summary

Mobility Controller Summary:

Mobility Role                                   : Mobility Controller

Mobility Protocol Port                          : 16666

Mobility Group Name                             : BUN-1

Mobility Oracle                                 : Disabled

Mobility Oracle IP Address                      : 0.0.0.0

DTLS Mode                                       : Enabled

Mobility Domain ID for 802.11r                  : 0xd3ca

Mobility Keepalive Interval                     : 10

Mobility Keepalive Count                        : 3

Mobility Control Message DSCP Value             : 48

Mobility Domain Member Count                    : 2

Link Status is Control Link Status : Data Link Status

Controllers configured in the Mobility Domain:

IP               Public IP        Group Name       Multicast IP     Link Status

-------------------------------------------------------------------------------

10.160.49.1      -                BUN-1            0.0.0.0          UP   : UP

10.129.0.7       10.129.0.7       BUN-1            0.0.0.0          DOWN : UP 

Switch Peer Group Name            : SPG1

Switch Peer Group Member Count    : 2

Bridge Domain ID                  : 0

Multicast IP Address              : 0.0.0.0

IP               Public IP             Link Status

--------------------------------------------------

10.161.33.22     10.161.33.22          UP   : UP                     

10.161.33.23     10.161.33.23          UP   : UP

Here is the "debug mobility keep-alive" output from the vWLC end.

(vWLC) >debug mobility keep-alive enable

(vWLC) >*mcListen: Jan 14 14:59:10.949:

                                        mcListen:MemTime 895,processTime for Timer Message(11)=5 usec,from peer 10.129.0.7

*mmMobility: Jan 14 15:25:19.086: Keepalive:VALID:CAPWAP_OP_REQ:Sent to 10.160.49.1:version=01:SeqNo=177:receiverStatusOnTransmitter=1

*mmMobility: Jan 14 15:25:19.086: Keepalive:Mobility Member 10.160.49.1 detected DOWN status 2, cleaning up client entries

*mcListen: Jan 14 15:25:19.086: Received keepalive status change message type:2 ,peer Ip 10.160.49.1

*capwapPingSocketTask: Jan 14 15:25:19.092: Received Ping packet in capwapPingRecvPkt

*capwapPingSocketTask: Jan 14 15:25:19.092: Received client count = 0 in ping packet from peer 10.160.49.1

*capwapPingSocketTask: Jan 14 15:25:19.092: Received Ping packet in processCapwapRecvdPkt

*capwapPingSocketTask: Jan 14 15:25:19.092: Keepalive:VALID:CAPWAP_OP_REPLY:Received from 10.160.49.1:version=01:SeqNo=177:receiverStatusOnTransmitter=0

*capwapPingSocketTask: Jan 14 15:25:19.092: Updated client count to 0 for peer 10.160.49.1

*mcListen: Jan 14 15:25:19.094: MC :Received capability payload from 10.160.49.1 arch 1  dtls 2 tunnel 2

*mmMobility: Jan 14 15:25:29.087: Keepalive:VALID:CAPWAP_OP_REQ:Sent to 10.160.49.1:version=01:SeqNo=178:receiverStatusOnTransmitter=1

*mmMobility: Jan 14 15:25:29.087: Keepalive:Mobility Member 10.160.49.1 detected DOWN status 2, cleaning up client entries

*mcListen: Jan 14 15:25:29.087: Received keepalive status change message type:2 ,peer Ip 10.160.49.1

*capwapPingSocketTask: Jan 14 15:25:29.093: Received Ping packet in capwapPingRecvPkt

*capwapPingSocketTask: Jan 14 15:25:29.093: Received client count = 0 in ping packet from peer 10.160.49.1

*capwapPingSocketTask: Jan 14 15:25:29.093: Received Ping packet in processCapwapRecvdPkt

*capwapPingSocketTask: Jan 14 15:25:29.093: Keepalive:VALID:CAPWAP_OP_REPLY:Received from 10.160.49.1:version=01:SeqNo=178:receiverStatusOnTransmitter=0

*capwapPingSocketTask: Jan 14 15:25:29.093: Updated client count to 0 for peer 10.160.49.1

*mmMobility: Jan 14 15:25:39.087: Keepalive:VALID:CAPWAP_OP_REQ:Sent to 10.160.49.1:version=01:SeqNo=179:receiverStatusOnTransmitter=1

*mmMobility: Jan 14 15:25:39.087: Keepalive:Mobility Member 10.160.49.1 detected DOWN status 2, cleaning up client entrie

*mcListen: Jan 14 15:25:39.087: Received keepalive status change message type:2 ,peer Ip 10.160.49.1

Does vWLC supported what I am trying to do ? Appreciate someone's help on this

Regards

Rasika

1 Accepted Solution

Accepted Solutions

sandeep is correct about the Release note.

currently, new mobility is supported on 2500, 5500 and wism2 only. even if it works on other wlc, that is not cisco supported. check new mobility section under mobility group on config guide.

on enabling new mobility in legacy WLCs, eping will disappear and cping will emerge.

View solution in original post

5 Replies 5

Sandeep Choudhary
VIP Mentor VIP Mentor
VIP Mentor

HI Rasika,

First of all congrats for becoming Cisco designated VIP 2014.

I am not sure is this right answer of ur question ....

I think u must have seen this :

Features Not Supported on Cisco Virtual WLCs with 7.6 Relase.

• Internal DHCP server

• TrustSec SXP

• Access points in local mode

Mobility/Guest Anchor

• Multicast

• IPv6

• High Availability

• PMIPv6

• WGB

• VideoStream

• Outdoor mesh access points

Check on Page 23.

http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn76.pdf

Regards

Thanks Sandeep,

I think that says vWLC cannot be a Mobility Anchor for guest termination.

I just simply want to see how this new mobility configured controller communicate back to 5760. Since I do not have test 5508 I have configured it on vWLC,but could not get it working.

Regards

Rasika

sandeep is correct about the Release note.

currently, new mobility is supported on 2500, 5500 and wism2 only. even if it works on other wlc, that is not cisco supported. check new mobility section under mobility group on config guide.

on enabling new mobility in legacy WLCs, eping will disappear and cping will emerge.