This page shows the mobility group name in the Default Mobility Group text box and lists the MAC address and IPv4/IPv6 address of each controller that is currently a member of the mobility group. The first entry is the local controller, which cannot be deleted.

• If you are adding only one controller or want to individually add multiple controllers, click New.

  OR

• If you are adding multiple controllers and want to add them in bulk, click EditAll.

1. In the Member IP Address text box, enter the management interface IPv4/IPv6 address of the controller to be added.

   Note

   If you are configuring the mobility group in a network where network address translation (NAT) is enabled, enter the IPv4/IPv6 address that is sent to the controller from the NAT device rather than the controller’s management interface IPv4/IPv6 address. Otherwise, mobility will fail among controllers in the mobility group.

2. In the Member MAC Address text box, enter the MAC address of the controller to be added.

3. In the Group Name text box, enter the name of the mobility group.

   Note	The mobility group name is case sensitive.

4. In the Hash text box, enter the hash key of the peer mobility controller, which should be a virtual controller in the same domain.

   You must configure the hash only if the peer mobility controller is a virtual controller in the same domain.

   Note	Hash is not supported for IPv6 members.

5. Click Apply to commit your changes. The new controller is added to the list of mobility group members on the Static Mobility Group Members page.

6. Click Save Configuration.

7. Repeat Step a through Step e to add all of the controllers in the mobility group.

8. Repeat this procedure on every controller to be included in the mobility group. All controllers in the mobility group must be configured with the MAC address and IPv4/IPv6 address of all other mobility group members.

The Mobility Group Members > EditAll page lists the MAC address, IPv4/IPv6 address, and mobility group name (optional) of all the controllers currently in the mobility group. The controllers are listed one per line with the local controller at the top of the list.

1. Click inside the edit box to start a new line.

2. Enter the MAC address, the management interface IPv4/IPv6 address, and the name of the mobility group for the controller to be added.

   Note	You should enter these values on one line and separate each value with one or two spaces.

   Note	The mobility group name is case sensitive.

3. Repeat Step a and Step b for each additional controller that you want to add to the mobility group.

4. Highlight and copy the complete list of entries in the edit box.

5. Click Apply to commit your changes. The new controllers are added to the list of mobility group members on the Static Mobility Group Members page.

6. Click Save Configurationto save your changes.

7. Paste the list into the text box on the Mobility Group Members > Edit All page of all the other controllers in the mobility group and click Apply and Save Configuration.

The names of all the currently configured mobility groups appear in the middle of the page.

show mobility summary

config mobility group domain domain_name

config mobility group member add mac_address ip_address

config mobility group member hash peer-ip-address key

config mobility multicast-mode {enable | disable} local_group_multicast_address

where local_group_multicast_address is the multicast group IPv4 address for the local mobility group. This address is used for multicast mobility messaging.

If you enable multicast mobility mode, the controller uses multicast mode to send Mobile Announce messages to the local group. If you disable multicast mobility mode, the controller uses unicast mode to send the Mobile Announce messages to the local group. The default value is disabled.

config mobility group multicast-address group_name IP_address

If you do not configure the multicast IPv4 address for non-local groups, the controller uses unicast mode to send mobility messages to those members.

show mobility summary

show mobility group member hash

save config

debug mobility multicast {enable | disable}

This page contains the following fields

• Global Mobility Statistics

  • Rx Errors—Generic protocol packet receive errors, such as packet too short or format incorrect.

  • Tx Errors—Generic protocol packet transmit errors, such as packet transmission fail.

  • Responses Retransmitted—Mobility protocol that uses UDP and resends requests several times if it does not receive a response. Because of network or processing delays, the responder may receive one or more retry requests after it initially responds to a request. This text box shows a count of the response resends.

  • Handoff Requests Received—Total number of handoff requests received, ignored, or responded to.

  • Handoff End Requests Received—Total number of handoff end requests received. These requests are sent by the anchor or foreign controller to notify the other about the close of a client session.

  • State Transitions Disallowed—Policy enforcement module (PEM) that has denied a client state transition, usually resulting in the handoff being terminated.

  • Resource Unavailable—Necessary resource, such as a buffer, was unavailable, resulting in the handoff being terminated.

• Mobility Initiator Statistics

  • Handoff Requests Sent—Number of clients that have associated to the controller and have been announced to the mobility group.

  • Handoff Replies Received—Number of handoff replies that have been received in response to the requests sent.

  • Handoff as Local Received—Number of handoffs in which the entire client session has been transferred.

  • Handoff as Foreign Received—Number of handoffs in which the client session was anchored elsewhere.

  • Handoff Denys Received—Number of handoffs that were denied.

  • Anchor Request Sent—Number of anchor requests that were sent for a three-party (foreign-to-foreign) handoff. The handoff was received from another foreign controller, and the new controller is requesting the anchor to move the client.

  • Anchor Deny Received—Number of anchor requests that were denied by the current anchor.

  • Anchor Grant Received—Number of anchor requests that were approved by the current anchor.

  • Anchor Transfer Received—Number of anchor requests that closed the session on the current anchor and transferred the anchor back to the requestor.

• Mobility Responder Statistics

  • Handoff Requests Ignored—Number of handoff requests or client announcements that were ignored because the controller had no knowledge of that client.

  • Ping Pong Handoff Requests Dropped—Number of handoff requests that were denied because the handoff period was too short (3 seconds).

  • Handoff Requests Dropped—Number of handoff requests that were dropped due to either an incomplete knowledge of the client or a problem with the packet.

  • Handoff Requests Denied—Number of handoff requests that were denied.

  • Client Handoff as Local—Number of handoff responses sent while the client is in the local role.

  • Client Handoff as Foreign—Number of handoff responses sent while the client is in the foreign role.

  • Anchor Requests Received—Number of anchor requests received.

  • Anchor Requests Denied—Number of anchor requests denied.

  • Anchor Requests Granted—Number of anchor requests granted.

  • Anchor Transferred—Number of anchors transferred because the client has moved from a foreign controller to a controller on the same subnet as the current anchor.

show mobility statistics

clear stats mobility