Cisco Cisco AP541N Wireless Access Point Notas de publicación

2

Cisco Small Business AP541N Access Point Release Notes for Versions 1.7.2 through 2.0.4

CSP #535465—A client wireless station was continually requesting a DHCP 
address. The server sent responses, but they were not seen on the wireless 
interface. 

In the 2.0.1 release, the TX FIFO that handles multicast traffic when the AP goes off 
channel to scan for other APs was disabled. However, it is necessary to disable all 
the TX FIFOs when the AP goes off channel to scan for other access points. If the 
AP submits packets to the TX FIFOs when the AP has hopped to another channel 
to scan for beacons, the wireless chip microcode can stop outputting packets.

The AP regularly scans for access points when clustering is enabled or when 
rogue AP detection is enabled. When Clustering or Rogue AP detection is not 
used, the AP does not hop off channel to detect other Access Points. The AP541N 
does do aggressive channel scanning during the first two minutes after the AP 
boots up to quickly generate a table of potential rogue APs, but only does this at 
boot time and then does not perform another scan unless the Rogue AP or 
Clustering feature is enabled.

CSCub73520—Resolved the issue of DHCP handling between the access point 
and the DHCP server when Clustering or Rogue AP Detection is enabled.

CSCty56257—Switching firmware versions might take a long time and when 
complete, the login page might not automatically come up in certain browsers, 
such as Internet Explorer 8. 

Workaround:  Wait two minutes and refresh the screen. The login screen should 
appear. If it does not appear, power cycle the device. If you are using Internet 
Explorer 8, you can also go to Tools > Internet Options > Security > Custom and 
set Prompt for user name and password. This setting can help avoid the 
problem.