Cisco Cisco Aironet 1200 Access Point Notas de publicación
10
Release Notes for Cisco Aironet 1200 Series Access Points Running VxWorks Firmware Version 12.05
OL-6434-01
Important Notes
The “Reliable multicast messages from the access point to workgroup bridges” setting limits reliable
delivery of multicast messages to approximately 20 Cisco Aironet Workgroup Bridges that are
associated to the access point. The default setting, disabled, reduces the reliability of multicast delivery
to allow more workgroup bridges to associate to the access point.
delivery of multicast messages to approximately 20 Cisco Aironet Workgroup Bridges that are
associated to the access point. The default setting, disabled, reduces the reliability of multicast delivery
to allow more workgroup bridges to associate to the access point.
Access points and bridges normally treat workgroup bridges not as client devices but as infrastructure
devices, like access points or bridges. Treating a workgroup bridge as an infrastructure device means that
the access point reliably delivers multicast packets, including Address Resolution Protocol (ARP)
packets, to the workgroup bridge.
devices, like access points or bridges. Treating a workgroup bridge as an infrastructure device means that
the access point reliably delivers multicast packets, including Address Resolution Protocol (ARP)
packets, to the workgroup bridge.
The performance cost of reliable multicast delivery—duplication of each multicast packet sent to each
workgroup bridge—limits the number of infrastructure devices, including workgroup bridges, that can
associate to the access point. To increase beyond 20 the number of workgroup bridges that can maintain
a radio link to the access point, the access point must reduce the delivery reliability of multicast packets
to workgroup bridges. With reduced reliability, the access point cannot confirm whether multicast
packets reach the intended workgroup bridge, so workgroup bridges at the edge of the access point's
coverage area might lose IP connectivity. When you treat workgroup bridges as client devices, you
increase performance but reduce reliability.
workgroup bridge—limits the number of infrastructure devices, including workgroup bridges, that can
associate to the access point. To increase beyond 20 the number of workgroup bridges that can maintain
a radio link to the access point, the access point must reduce the delivery reliability of multicast packets
to workgroup bridges. With reduced reliability, the access point cannot confirm whether multicast
packets reach the intended workgroup bridge, so workgroup bridges at the edge of the access point's
coverage area might lose IP connectivity. When you treat workgroup bridges as client devices, you
increase performance but reduce reliability.
Cisco Discovery Protocol Re-Enabled for Individual Interfaces on Reboot
The Cisco Discovery Protocol (CDP) feature is enabled by default, and CDP is enabled for each of the
access point’s relevant interfaces by default. However, if you disable CDP for one of the individual
interfaces, the access point re-enables CDP for that interface when it reboots. If you disable CDP
completely, the access point does not re-enable CDP on reboot.
access point’s relevant interfaces by default. However, if you disable CDP for one of the individual
interfaces, the access point re-enables CDP for that interface when it reboots. If you disable CDP
completely, the access point does not re-enable CDP on reboot.
Symbol IP Phone Issues
When a Symbol IP phone is associated to a VoIP VLAN (Symbol extensions enabled), the phone
associates to the access point and is authenticated approximately every 2 seconds. the Symbol phone
shows a “No Network” error every 1 to 2 minutes. It also appears that Symbol phones do not work well
when using a non-primary SSID. It is possible that the phone does not perform an active probe and
therefore does not detect information about the SSID it associated with in the beacon, causing it to
reassociate and authenticate.
associates to the access point and is authenticated approximately every 2 seconds. the Symbol phone
shows a “No Network” error every 1 to 2 minutes. It also appears that Symbol phones do not work well
when using a non-primary SSID. It is possible that the phone does not perform an active probe and
therefore does not detect information about the SSID it associated with in the beacon, causing it to
reassociate and authenticate.
Symbol phones may disconnect and be unable to roam between subnets when the access point passes
multicast or FTP traffic. If there are no FTP or multicast sessions in progress the Symbol phone operates
normally and is able to roam between subnets. To work around this issue, limit multicast and FTP traffic
if you are using Symbol IP phones in a proxy Mobile IP environment.
multicast or FTP traffic. If there are no FTP or multicast sessions in progress the Symbol phone operates
normally and is able to roam between subnets. To work around this issue, limit multicast and FTP traffic
if you are using Symbol IP phones in a proxy Mobile IP environment.