Table Of Contents

Limitations of the Conversion Process

Limitations of the Conversion Process

---

Because of differences between the configuration settings in non-IOS APs and IOS configuration settings, the conversion process has the following limitations.

Settings	Limitations	Implications and Workarounds
AAA	Retransmission settings range from 1 to 100. If the configured setting is greater than 100, the migrated setting is 100. If the configured setting is less than 1, the migrated setting is 1. Separate EAP and non-EAP server settings are not migrated. Once a server is enabled, all the users are configured to use that server. LEAP usernames do not migrate. Following AAA server parameters do not migrate: •Port configuration settings for TACACS server •802.1X protocol version for EAP authentication •Update delay per server
Boot server and DHCP	BOOTP is not supported by IOS. Only DHCP configuration settings with a Client Identifier type of Ethernet are migrated; all other Client Identifier types are discarded. If DHCP is configured, the fall-back IP address will not be configured. Following Boot Server parameters do not migrate: •DHCP Multiple-Offer Timeout •DHCP Requested Lease Duration •DHCP Minimum Lease Duration •DHCP Client Identifier Value	Convert from BOOTP to DHCP before proceeding with the conversion.
CDP	CDP information on a per-interface basis is not migrated.
Ethernet	Following parameters do not migrate: •Optimize Network for maximum multicast packets per second •Loss of backbone connectivity timeout •Maximum multicast packets per second
FTP and TFTP	Configuration parameters do not migrate.
HTTP	Only the HTTP port and the Enable or Disable settings are migrated.
Filters	Separate filters are created for Ethertype, IP port, and IP protocol filters that have been set to non-default priority. This may create multiple filters with the same numeric identifier, but the conversion inserts a numeric index to differentiate the filters. If both port and protocol filters are applied on an interface, this setting does not migrate. Default multicast address filtering for an interface does not migrate. Ethertype filters—A maximum of 100 Ethertype filters can be created. Ethertype filters will not have associated names; instead, they will have associated numbers ranging from 200 to 299. Port filters are created in the format IP access list extended Port_PortId. Protocol filters are created in the format IP access list extended PF_ProtocolId. Ether filters are created in the format access-list Numeric_Value permit or deny Protocol-Type. MAC-based filters—Only MAC-based filter settings with SSIDs associated to a VLAN and with MAC authentication enabled are migrated.
Policy Groups	Policy groups are created in the format policy-map_policy Name Policy_ID. Policy groups without an associated VLAN are not migrated.
Port Assignments	Not migrated.	The port assignments settings are only supported in the non-IOS environment. This feature is not supported on IOS, so the settings are not converted. If you have not made any changes to the default settings in the port assignments page, there are no implications and you can ignore this setting. The purpose of the port assignments feature is to ensure that a root AP that has repeaters connected to it will always show them as neighbors using the same interface for CDP. This ensures that an application that is drawing topology maps will always show the same topology. If the repeater APs are reset (possibly due to a power outage), they may appear to be on different interfaces when they come back up if there are no port assignment settings. It is possible that some network management applications will detect this as a change in network topology. You should ignore any messages indicating topology changes from such an application because no actual change in topology has occurred.
Timeouts	The following settings do not migrate: •Rogue AP Alert Timeout •Unknown Class Timeout •Multicast Addresses Timeout •Infrastructure Hosts, Client Stations, and Repeater Timeout
VLANs	Migrated only when they are associated with an SSID, except for the native VLAN. The native VLAN is migrated even if it is not associated with an SSID.