Cisco Cisco Aironet 1200 Access Point 릴리즈 노트
10
Release Notes for Cisco Aironet Access Points for Cisco IOS Release 12.3(7)JA3
OL-10095-01
Important Notes
Important Notes
This section describes important information about the access point.
Change to Default IP Address Behavior
Cisco IOS Releases 12.3(2)JA and later change the default behavior of access points requesting an IP
address from a DHCP server:
address from a DHCP server:
•
When you connect a 350, 1130AG, 1200, 1230AG, or 1240AG series access point with a default
configuration to your LAN, the access point requests an IP address from your DHCP server and, if
it does not receive an address, continues to send requests indefinitely.
configuration to your LAN, the access point requests an IP address from your DHCP server and, if
it does not receive an address, continues to send requests indefinitely.
•
When you connect an 1100 series access point with a default configuration to your LAN, the 1100
series access point makes several attempts to get an IP address from the DHCP server. If it does not
receive an address, it assigns itself the IP address 10.0.0.1 for five minutes. During this five-minute
window, you can browse to the default IP address and configure a static address. If after five minutes
the access point is not reconfigured, it discards the 10.0.0.1 address and reverts to requesting an
address from the DHCP server. If it does not receive an address, it sends requests indefinitely. If you
miss the five-minute window for browsing to the access point at 10.0.0.1, you can power-cycle the
access point to repeat the process.
series access point makes several attempts to get an IP address from the DHCP server. If it does not
receive an address, it assigns itself the IP address 10.0.0.1 for five minutes. During this five-minute
window, you can browse to the default IP address and configure a static address. If after five minutes
the access point is not reconfigured, it discards the 10.0.0.1 address and reverts to requesting an
address from the DHCP server. If it does not receive an address, it sends requests indefinitely. If you
miss the five-minute window for browsing to the access point at 10.0.0.1, you can power-cycle the
access point to repeat the process.
Save Interface Level Configuration Before Upgrading to Release 12.3(7)JA3
If the access points have SSIDs configured at the interface level (rather than at the global level), before
upgrading to Cisco IOS Release 12.3(7)JA3 and above, upgrade to Cisco IOS Release 12.3(4)JA, save
the configurations and then upgrade to Release 12.3(7)JA3. This procedure must be followed to make
sure that the SSID configurations are converted from the interface level to global level.
upgrading to Cisco IOS Release 12.3(7)JA3 and above, upgrade to Cisco IOS Release 12.3(4)JA, save
the configurations and then upgrade to Release 12.3(7)JA3. This procedure must be followed to make
sure that the SSID configurations are converted from the interface level to global level.
Changes to the Default Configuration—Radios Disabled and No Default SSID
In this release, the radio or radios are disabled by default, and there is no default SSID. You must create
an SSID and enable the radio or radios before the access point will allow wireless associations from other
devices. These changes to the default configuration improve the security of newly installed access
points.
an SSID and enable the radio or radios before the access point will allow wireless associations from other
devices. These changes to the default configuration improve the security of newly installed access
points.
Clients Using WPA/WPA2 and Power Save May Fail to Authenticate
Certain clients using WPA/WPA2 key management and power save may take many attempts to
authenticate or, in some cases, fail to authenticate. Any SSID defined to use authentication
key-management wpa, coupled with clients using power save mode and authenticating using
WPA/WPA2 may experience this problem.
authenticate or, in some cases, fail to authenticate. Any SSID defined to use authentication
key-management wpa, coupled with clients using power save mode and authenticating using
WPA/WPA2 may experience this problem.
A hidden configure level command, dot11 wpa handshake timeout, can be used to increase the timeout
between sending the WPA key packets from the default value (100 ms) to a value between 101 and 200
ms. The command stores its value in the configuration across device reloads.
between sending the WPA key packets from the default value (100 ms) to a value between 101 and 200
ms. The command stores its value in the configuration across device reloads.