Alias – Brocade Mobility Access Point System Reference Guide (Supporting software release 5.5.0.0 and later) User Manual
Page 157
Brocade Mobility Access Point System Reference Guide
147
53-1003100-01
5
2. Select Devices.
3. Select System Profile from the options on left-hand side of the UI.
4. Expand the Network menu and select Miscellaneous.
FIGURE 54
Network - Miscellaneous screen
5. Select the Include Hostname in DHCP Request option to include a hostname in a DHCP lease
for a requesting device. This feature is enabled by default.
6. Select the DHCP Persistent Lease option to retain the lease that was last used by the access
point if the access point’s DHCP server resource were to become unavailable. This feature is
enabled by default.
7. Select the OK button located at the bottom right of the screen to save the changes. Select
Reset to revert to the last saved configuration.
Alias
With large deployments, the configuration of remote sites utilizes a set of shared attributes, of
which a small set of attributes are unique for each location. For such deployments, maintaining
separate configuration (WLANs, profiles, policies and ACLs) for each remote site is complex.
Migrating any global change to a particular configuration item to all the remote sites is a complex
and time consuming operation.
Also, this practice does not scale gracefully for quick growing deployments.
An alias enables an administrator to define a configuration item, such as a hostname, as an alias
once and use the defined alias across different configuration items such as multiple ACLs.
Once a configuration item, such as an ACL, is utilized across remote locations, the alias used in the
configuration item (ACL) is modified to meet local deployment requirement. Any other ACL or other
configuration items using the modified alias also get modified, simplifying maintenance at the
remote deployment.
Aliases have scope depending on where the Alias is defined. Alias are defined with the following
scopes: