User's Manual

604 | IP Mobility Dell Networking W-Series ArubaOS 6.4.x| User Guide
Location-related information for users, such as roaming status, AP name, ESSID, BSSID, and physical type are
consistent in both the home agent and foreign agent. The username, role, and authentication can be different
on the home agent and foreign agent, as explained by the following:
Starting from ArubaOS 6.3, L2 GRE tunnels are automatically established between controllers in mobility
domain at the time of boot up. Before ArubaOS 6.3, the tunnels were created only when a client was
associated to a controller. Whenever a client connects to a controller in a mobility domain, layer-2
authentication is performed and the station obtains the layer-2 (logon) role. When the client roams to other
networks, layer-2 authentication is performed and the client obtains the layer-2 role. If layer-3 authentication is
required, this authentication is performed on the client’s home agent only. The home agent obtains a new role
for the client after layer-3 authentication; this new role appears in the user status on the home agent only.
Even if reauthentication occurs after the station moves to a foreign agent, the display on the foreign agent still
shows the layer-2 role for the user.
Mobile Client Roaming Status
You can view the list of mobile clients and their roaming status on any controller in the mobility domain:
Viewing Mobile Client Status using the WebUI
Navigate to the Monitoring > controller > Clients page.
Viewing Mobile Client Status using the CLI
Execute the following command to view the status of the mobile client:
show ip mobile host
Roaming status can be one of the following:
Roaming
Status Type
Description
Home Switch/Home
VLAN
This controller is the home agent for a station, and the client is on the VLAN on
which it has an IP address.
Mobile IP Visitor This controller is not the home agent for a client.
Mobile IP Binding
(away)
This controller is the home agent for a client that is currently away.
Home Switch/Foreign
VLAN
This controller is the home agent for a client, but the client is currently on a
different VLAN than its home VLAN (the VLAN from which it acquired its IP address).
Stale The client does not have connectivity in the mobility domain. Either the controller
has received a disassociation message for a client, but has not received an
association or registration request for the client from another controller, or a home
agent binding for the station has expired before being refreshed by a foreign agent.
No Mobility Service The controller cannot provide mobility service to this client. The mobile client may
lose its IP address if it obtains the address via DHCP and has limited connectivity.
The mobile client may be using an IP address that cannot be served, or there may
be a roaming hole due to improper configuration.
Table 115: Client Roaming Status
Viewing User Roaming Status using the CLI
You can view the roaming status of users on any controller in the mobility domain:
show user