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 do not migrate.
|
Once a server is enabled, all 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.
|
You should convert from BOOTP to DHCP before proceeding with the AP conversion.
|
Following Boot Server parameters do not migrate:
•DHCP Multiple-Offer Timeout
•DHCP Requested Lease Duration
•DHCP Minimum Lease Duration
•DHCP Client Identifier Value
|
|
Only DHCP configuration settings with a Client Identifier type of Ethernet migrate; all other Client Identifier types are discarded.
|
|
If DHCP is configured, the fall-back IP address will not be configured.
|
|
CDP
|
CDP information on a per-interface basis does not migrate.
|
|
Ethernet
|
Following parameters do not migrate:
•Optimize Network for maximum multicast packets per second
•Loss of backbone connectivity timeout
•Maximum multicast packets per second
|
|
Filters
|
Default multicast address filtering for an interface does not migrate.
|
|
Separate filters are created for Ethertype filters, IP port filters, and IP protocol filters that have been set to non-default priority.
|
Conversion 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.
|
|
IP port filters—Will be created in the format IP access list extended Port_PortId.
|
|
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.
|
|
Protocol filters—Will be created in the format IP access list extended PF_ProtocolId.
|
|
Ether filters —Will be created in one of the following formats:
•access-list Numeric_Value permit
•deny Protocol-Type
|
|
MAC-based filters—Only MAC-based filter settings with the following will migrate:
•SSIDs associated to a VLAN
•MAC authentication enabled
|
|
FTP and TFTP
|
Configuration parameters do not migrate.
|
|
HTTP
|
Only the HTTP port and the Enable or Disable settings will migrate.
|
|
Policy Groups
|
Policy groups are created in the format policy-map_policy Name Policy_ID.
|
|
Policy groups without an associated VLAN do not migrate.
|
|
Port Assignments
|
Port assignment settings are supported only in the non-IOS environment; therefore, these settings do not migrate.
The purpose of the port assignments feature is to ensure that a root AP that has repeaters connected to it will always show the repeaters as neighbors using the same interface for CDP. Thus, an application that is drawing topology maps will always show the same topology.
|
If you have not made any changes to the default settings in the port assignments page, you can ignore this setting.
If repeater APs are reset (possibly due to a power outage), they may appear to be on different interfaces when they come back. Some network management applications might detect this as a change in network topology. You should ignore any messages indicating topology changes from such applications 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
|
VLANs migrate only when they are associated with an SSID, except for the native VLAN. The native VLAN will migrate even if it is not associated with an SSID.
|
|
