Dell PowerConnect W-Airwave W-Airwave 7.2 Configuration Guide - Page 147

Advanced Services, Overview of IP Mobility Domains

Page 147 highlights

Advanced Services This document section describes the contents, parameters, and default settings for all Advanced Services components in Dell PowerConnect W Configuration. Dell PowerConnect W Configuration in AWMS 6.3 supports advanced services such as IP Mobility and VPN services. Future AWMS versions will support additional advanced services. For additional information about IP Mobility domains, VPN services, and additional architecture or concepts, refer to your version of the ArubaOS User Guide. Overview of IP Mobility Domains Dell PowerConnect W's layer-3 mobility solution is based on the Mobile IP protocol standard, as described in RFC 3344, "IP Mobility Support for IPv4". This standard addresses users who need both network connectivity and mobility within the work environment. Unlike other layer-3 mobility solutions, an Dell PowerConnect W mobility solution does not require that you install mobility software or perform additional configuration on wireless clients. The Dell PowerConnect W controllers perform all functions that enable clients to roam within the mobility domain. In a mobility domain, a mobile client is a wireless client that can change its point of attachment from one network to another within the domain. A mobile client receives an IP address (a home address) on a home network. A mobile client can detach at any time from its home network and reconnect to a foreign network (any network other than the mobile client's home network) within the mobility domain. When a mobile client is connected to a foreign network, it is bound to a care-of address that reflects its current point of attachment. A care-of address is the IP address of the Dell PowerConnect W controller in the foreign network with which the mobile client is associated. The home agent for the client is the controller where the client appears for the first time when it joins the mobility domain. The home agent is the single point of contact for the client when the client roams. The foreign agent for the client is the controller which handles all Mobile IP communication with the home agent on behalf of the client. Traffic sent to a client's home address is intercepted by the home agent and tunneled for delivery to the client on the foreign network. On the foreign network, the foreign agent delivers the tunneled data to the mobile client. A mobility domain is a group of Dell PowerConnect W controllers among which a wireless user can roam without losing their IP address. Mobility domains are not tied with the master controller, thus it is possible for a user to roam between controllers managed by different master controllers as long as all of the controllers belong to the same mobility domain. You enable and configure mobility domains only on Dell PowerConnect W controllers. No additional software or configuration is required on wireless clients to allow roaming within the domain. Before configuring a mobility domain, you should determine the user VLAN(s) for which mobility is required. For example, you may want to allow employees to be able to roam from one subnetwork to another. All controllers that support the VLANs into which employee users can be placed should be part of the same mobility domain. A controller can be part of multiple mobility domains, although Dell PowerConnect W recommends that a controller belong to only one domain. The controllers in a mobility domain do not need to be managed by the same master controller. You configure a mobility domain on a master controller; the mobility domain information is pushed to all local controllers that are managed by the same master controller. On each controller, you must specify the active domain (the domain to which the controller belongs). If you do not specify the active domain, the controller will be assigned to a predefined "default" domain. Although you configure a mobility domain on a master controller, the master controller does not need to be a member of the mobility domain. For example, you could set up a mobility domain that contains only local controllers; you still need to configure the mobility domain on the master controller that manages the local Dell PowerConnect W AirWave 7.2 | Configuration Guide Dell PowerConnect W Configuration Reference | 147

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160

Dell PowerConnect W AirWave 7.2
| Configuration Guide
Dell PowerConnect W Configuration Reference
|
147
Advanced Services
This document section describes the contents, parameters, and default settings for all
Advanced Services
components in
Dell PowerConnect W Configuration
. Dell PowerConnect W Configuration in AWMS 6.3
supports advanced services such as IP Mobility and VPN services. Future AWMS versions will support additional
advanced services.
For additional information about IP Mobility domains, VPN services, and additional architecture or concepts,
refer to your version of the
ArubaOS User Guide
.
Overview of IP Mobility Domains
Dell PowerConnect W’s layer-3 mobility solution is based on the Mobile IP protocol standard, as described in
RFC 3344, “IP Mobility Support for IPv4”. This standard addresses users who need both network connectivity
and mobility within the work environment.
Unlike other layer-3 mobility solutions, an Dell PowerConnect W mobility solution does not require that you
install mobility software or perform additional configuration on wireless clients. The Dell PowerConnect W
controllers perform all functions that enable clients to roam within the mobility domain.
In a mobility domain, a mobile client is a wireless client that can change its point of attachment from one
network to another within the domain. A mobile client receives an IP address (a home address) on a home
network. A mobile client can detach at any time from its home network and reconnect to a foreign network (any
network other than the mobile client’s home network) within the mobility domain. When a mobile client is
connected to a foreign network, it is bound to a care-of address that reflects its current point of attachment. A
care-of address is the IP address of the Dell PowerConnect W controller in the foreign network with which the
mobile client is associated.
The
home agent
for the client is the controller where the client appears for the first time when it joins the mobility
domain. The home agent is the single point of contact for the client when the client roams. The
foreign agent
for
the client is the controller which handles all Mobile IP communication with the home agent on behalf of the
client. Traffic sent to a client’s home address is intercepted by the home agent and tunneled for delivery to the
client on the foreign network. On the foreign network, the foreign agent delivers the tunneled data to the mobile
client.
A mobility domain is a group of Dell PowerConnect W controllers among which a wireless user can roam without
losing their IP address. Mobility domains are not tied with the master controller, thus it is possible for a user to
roam between controllers managed by different master controllers as long as all of the controllers belong to the
same mobility domain.
You enable and configure mobility domains only on Dell PowerConnect W controllers. No additional software or
configuration is required on wireless clients to allow roaming within the domain.
Before configuring a mobility domain, you should determine the user VLAN(s) for which mobility is required. For
example, you may want to allow employees to be able to roam from one subnetwork to another. All controllers
that support the VLANs into which employee users can be placed should be part of the same mobility domain.
A controller can be part of multiple mobility domains, although Dell PowerConnect W recommends that a
controller belong to only one domain. The controllers in a mobility domain do not need to be managed by the
same master controller.
You configure a mobility domain on a master controller; the mobility domain information is pushed to all local
controllers that are managed by the same master controller. On each controller, you must specify the active
domain (the domain to which the controller belongs). If you do not specify the active domain, the controller will
be assigned to a predefined “default” domain.
Although you configure a mobility domain on a master controller, the master controller does not need to be a
member of the mobility domain. For example, you could set up a mobility domain that contains only local
controllers; you still need to configure the mobility domain on the master controller that manages the local