Cisco Cisco 526 Wireless Express Mobility Controller
6
Release Notes for Cisco 526 Wireless Express Mobility Controller and Cisco 521 Wireless Express Lightweight Access Point, 4.1.154.23
OL-13554-01
Caveats
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 cannot 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 cannot 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.
Caveats
This section lists open caveats for components of the Cisco Smart Business Communications System.
Open Caveats
These caveats are open in 526 controller software release 4.1.154.23.
•
CSCsi64422—The controller does not resend an ACK packet when TFTP times out. This issue
occurs when the controller retrieves a file from a TFTP server over a VPN link.
occurs when the controller retrieves a file from a TFTP server over a VPN link.
Workaround: None at this time.
These caveats are open in CCA release 1.0 and affect controller manageability.
•
CSCsh99313—A controller with read-only privileges can be added to a read-write community and
vice versa (a controller with read-write privileges can be added to a read-only community). This
issue occurs when you add the same username and password pair as read-only for one controller and
as read-write for another controller. As a result, the CCA discovers both controllers even though the
privilege level of one of them does not match the privilege level of the community. When you
manage the read-write community, you can configure the controller with the read-only privilege, but
the controller rejects the operation because of insufficient privilege.
vice versa (a controller with read-write privileges can be added to a read-only community). This
issue occurs when you add the same username and password pair as read-only for one controller and
as read-write for another controller. As a result, the CCA discovers both controllers even though the
privilege level of one of them does not match the privilege level of the community. When you
manage the read-write community, you can configure the controller with the read-only privilege, but
the controller rejects the operation because of insufficient privilege.
Workaround: Set the same privilege level when configuring the same username and password pair
for different controllers. Also, provide the read-write username and password pair during controller
discovery for the read-write community and provide the read-only username and password pair
during controller discovery for the read-only community.
for different controllers. Also, provide the read-write username and password pair during controller
discovery for the read-write community and provide the read-only username and password pair
during controller discovery for the read-only community.
•
CSCsi22823—The following error message may appear on the Cisco Catalyst Express 500 Series
Switches (CE500): “Fa10: Detected undersize frames generated by the connected device.” However,
there is no impact to controller functionality.
Switches (CE500): “Fa10: Detected undersize frames generated by the connected device.” However,
there is no impact to controller functionality.
Workaround: None at this time.