Cisco Cisco 526 Wireless Express Mobility Controller Release Notes
7
Release Notes for Cisco 526 Wireless Express Mobility Controller and Cisco 521 Wireless Express Lightweight Access Point, 4.2.61.8
OL-15616-01
Important Notes
Note
Configuring the controller using the controller GUI requires someone familiar with the 526 controller
GUI and the controller functions.
GUI and the controller functions.
Note
The controller GUI requires the following operating system and web browser: Windows XP SP1 or
higher or Windows 2000 SP4 or higher and Internet Explorer 6.0 SP1 or higher, respectively.
higher or Windows 2000 SP4 or higher and Internet Explorer 6.0 SP1 or higher, respectively.
Establishing Wireless Connectivity
Follow these guidelines to ensure that the 526 controller and 521 access point can establish wireless
connectivity.
connectivity.
•
When a 526 controller and 521 access point are connected to a Cisco Catalyst Express 500 Series
Switch or Cisco Unified Communications 500 Series Switch managed by the CCA and you use the
CCA’s Configure tab to select Smartports, you can have the CCA suggest a role for the ports to
which the controller and access point are connected. The recommended role for the controller and
access point is the Access Point Smartport Role. The CCA also suggests a default VLAN of 1. If
you apply the suggested Smartport role, the native VLAN should be set to 1 on all ports connecting
to the controller and access point.
Switch or Cisco Unified Communications 500 Series Switch managed by the CCA and you use the
CCA’s Configure tab to select Smartports, you can have the CCA suggest a role for the ports to
which the controller and access point are connected. The recommended role for the controller and
access point is the Access Point Smartport Role. The CCA also suggests a default VLAN of 1. If
you apply the suggested Smartport role, the native VLAN should be set to 1 on all ports connecting
to the controller and access point.
•
The 526 controller’s management and ap-manager interfaces are set by default to the untagged
VLAN (or VLAN 0) and it is recommended that VLAN 0 not be changed. The IP addresses for these
two interfaces must belong to the subnet associated with this untagged VLAN, and the default SSID
created from the controller configuration wizard is associated to this untagged VLAN. You can
create dynamic interfaces using any other VLAN (from 2 to 1000) and associate this VLAN to the
new SSID, but this VLAN should be different from the native VLAN on the connected port. For
example, if you create a dynamic interface using VLAN 25, then you can associate this VLAN to
the new SSID.
VLAN (or VLAN 0) and it is recommended that VLAN 0 not be changed. The IP addresses for these
two interfaces must belong to the subnet associated with this untagged VLAN, and the default SSID
created from the controller configuration wizard is associated to this untagged VLAN. You can
create dynamic interfaces using any other VLAN (from 2 to 1000) and associate this VLAN to the
new SSID, but this VLAN should be different from the native VLAN on the connected port. For
example, if you create a dynamic interface using VLAN 25, then you can associate this VLAN to
the new SSID.
Converting an Autonomous AP521 Using the CCA
When an autonomous AP521 access point is converted to controller-mode operation using the CCA, the
access point properties screen continues to indicate that the access point is an AIR-AP521G-A-K9 after
the conversion. This is in agreement with the product label on the access point. However, the CCA
displays a small triangle icon next to the converted access point to indicate that the access point is now
operating as a controller-mode access point.
access point properties screen continues to indicate that the access point is an AIR-AP521G-A-K9 after
the conversion. This is in agreement with the product label on the access point. However, the CCA
displays a small triangle icon next to the converted access point to indicate that the access point is now
operating as a controller-mode access point.
Note
The CCA conversion process is one-way. Once the conversion takes place, you cannot restore the access
point to autonomous operation.
point to autonomous operation.