Rf domain alias configuration – Brocade Mobility Access Point System Reference Guide (Supporting software release 5.5.0.0 and later) User Manual
Page 69
Brocade Mobility Access Point System Reference Guide
59
53-1003100-01
5
6. Provide the numerical (non DNS) IP Address of each server used as a WIPS sensor server by
the RF Domain.
7. Use the spinner control to specify the Port of each WIPS server. The default port is 443.
8. Select OK to save the changes to the AirDefense WIPS configuration, or select Reset to revert
to the last saved configuration.
RF Domain Alias Configuration
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:
•
Global aliases are defined from the Configuration > Network > Alias screen. Global aliases are
available for use globally across all devices, profiles and RF Domains in the system.
•
Profiles aliases are defined from Configuration > Devices > System Profile > Network > Alias
screen. These aliases are available for use to a specific group of wireless controllers or access
points. Alias values defined in this profile override alias values defined within global aliases.
•
RF Domain aliases are defined from Configuration > Devices > RF Domain > Alias screen.
These aliases are available for use for a site as a RF Domain is site specific. RF Domain alias
values override alias values defined in a global alias or a profile alias configuration.
•
Device aliases are defined from Configuration > Devices > Device Overrides > Network > Alias
screen. Device alias are utilized by a single device only. Device alias values override alias
values defined in a global alias, profiles alias or RF Domain alias configuration.
Using an alias, configuration changes made at a remote location override any updates at the
management center. For example, if an Network Alias defines a network range as
192.168.10.0/24 for the entire network, and at a remote deployment location, the local network
range is 172.16.10.0/24, the network alias can be overridden at the deployment location to suit
the local requirement. For the remote deployment location, the network alias works with the
172.16.10.0/24 network. Existing ACLs using this network alias need not be modified and will work
with the local network for the deployment location. This simplifies ACL definition and management
while taking care of specific local deployment requirements.
Alias can be classified as:
•
•