Adding or Deleting Proxy Mobile IP AAPs
If you need to add or delete proxy Mobile IP authoritative access points, you must disable proxy Mobile
IP before changing the configuration. Follow these steps.
Browse to the Setup page.
In the Services section, click Proxy Mobile IP. The Proxy Mobile IP Setup page appears.
Click General. The Proxy Mobile IP General page appears.
Change the Enable Proxy Mobile IP setting to no.
Add or delete AAPs as necessary.
Change the Enable Proxy Mobile IP setting to yes.
Unexpected Results on Lost Ethernet
When backbone connectivity is lost on an access point running version 12.01T1, the device switches to
repeater mode. Switch to Repeater mode is the default setting for this condition. Therefore, if the access
point's role in your network is not a repeater access point, make sure you connect it to your wired
network before booting it up. If you do not connect the access point to your network, it switches to the
repeater mode when it fails to detect the presence of an Ethernet connection. When this occurs, wireless
client devices are unable to connect and you cannot correct the problem using a wireless client. The only
way you can change the configuration is through a serial connection using the access point's command
This section lists open and resolved software issues in firmware version 12.01T1.
Getting Bug Information on Cisco.com
If you are a registered Cisco user, you can use the Cisco TAC Software Bug Toolkit, which consists of
three tools (Bug Navigator, Bug Watcher, and Search by Bug ID Number) that help you identify existing
bugs (or caveats) in Cisco software products.
Access the TAC Software Bug Toolkit at http://www.cisco.com/support/bugtools/.
The following caveats have not been resolved for firmware version 12.01T1:
Release Notes for Cisco Aironet 340 and 350 Series Access Points and 350 Series Bridges Running Firmware Version 12.01T1
CSCdz04708—Early 340 series access points are incompatible with VLAN tagging.
Early versions of the 340 series access point are able to set up VLANs, but clients on non-native
VLANs will be unable to transmit and receive large packets. The reason for this is because early 340
series access points were limited to a maximum packet data length of 1500 bytes.