Step 1 |
Choose
Controller > Mobility Management > Mobility
Configuration to enable and configure new mobility on the
controller.
Note
|
When you
enable or disable new mobility, you must save the configuration and reboot the
controller.
|
|
Step 2 |
To configure new
mobility, select or unselect the
Enable
New Mobility (Converged Access) check box.
Note
|
When you
enable new mobility, you must save the configuration and reboot the controller.
|
|
Step 3 |
To configure the
controller as Mobility Oracle, select or unselect the
Mobility
Oracle check box.
Note
|
Mobility
Oracle is optional; it maintains the client database under one complete
mobility domain.
|
|
Step 4 |
To configure
multicast mode in a mobility group, select or unselect the
Multicast Mode check box.
|
Step 5 |
In the
Multicast IP Address text box, enter the multicast
IP address of the switch peer group.
|
Step 6 |
In the
Mobility
Oracle IP Address text box, enter the IP address of the Mobility
Oracle.
You cannot
enter a value for this field if you have checked the
Mobility Oracle check box.
|
Step 7 |
In the
Mobility
Controller Public IP Address text box, enter the IP address of the
controller, if there is no network address translation (NAT).
Note
|
If the controller has NAT
configured, the public IP address will be the network address translated IP
address.
|
Note
|
New mobility does not support IPv6.
|
|
Step 8 |
In the
Mobility
Keep Alive Count text box, enter the number of times a ping request
is sent to a peer controller before the peer is considered to be unreachable.
The range is from 3 to 20. The default value is 3.
|
Step 9 |
In the
Mobility
Keep Alive Interval text box, enter the amount of time, in seconds,
between each ping request sent to an peer controller. The range is from 1 to 30
seconds. The default value is 10 seconds.
|
Step 10 |
In the
Mobility
DSCP text box, enter the DSCP value that you can set for the
mobility controller. The range is from 0 to 63. The default value is 0.
Note
|
While configuring the Mobility DSCP value, the mobility control
socket (i.e control messages exchanged between mobility peers only and not the
data) is also updated. The configured value must reflect in the IPV4 header TOS
field. This is a global configuration on the controller that is used to
communicate among configured mobility peers only.
|
|
Step 11 |
Click
Apply.
|
Step 12 |
Choose
Controller > Mobility Management > Switch Peer
Group to add or remove members to and from the switch peer group.
This page lists
all the switch peer groups and their details, such as bridge domain ID,
multicast IP address, and status of the multicast mode. Click the name of the
switch peer group to navigate to the
Edit page and update the parameters, if required.
|
Step 13 |
Choose
Controller > Mobility Management > Mobility
Controller to view all the mobility controllers and their details,
such as IP address, MAC address, client count, and link status.
|
Step 14 |
Choose
Controller > Mobility Management > Mobility
Clients to view all the mobility clients and their parameters.
|
Step 15 |
In the
Client
MAC Address and
Client
IP Address text boxes, enter the MAC address and IP address of the
mobility client, respectively.
|
Step 16 |
In the
Anchor
MC IP Address and
Anchor
MC Public IP Address text boxes, enter the IP address and public IP
address of the anchor Mobility Controller, respectively.
|
Step 17 |
In the
Foreign
MC IP Address and
Foreign
MC Public IP Address text boxes, enter the IP address and public IP
address of the foreign MC, respectively.
|
Step 18 |
In the
Client
Association Time text box, enter the time at which the mobility
client should be associated with the Mobility Controller.
|
Step 19 |
In the
Client
Entry Update Timestamp text box, enter the timestamp at which the
client entry should be updated.
|