Release Notes for the CiscoWorks Wireless LAN Solution Engine, Release 2.7.1 These release notes are for use with the CiscoWorks Wireless LAN Solution Engine (WLSE) Release 2.7.1. Note The Sun Java Cryptography Extension (JCE) 1.2.1 used in this release is set to expire at midnight on July 27th, 2005. Key functionality will stop working. Refer to the following field notice, then download and install the recommended patch: http://www.cisco.
• Obtaining Additional Publications and Information, page 27 Release Notes for the CiscoWorks Wireless LAN Solution Engine, Release 2.7.
New Features New Features The WLSE Release 2.7.1 contains: • Software support for firmware release 12.2(15)XR. • Support for WLSM. • Support for Firmware conversion VxWorks version 12.04 to IOS. Product Documentation You can access the WLSE online help by clicking the Help button in the top right corner of the screen or by selecting an option and then clicking the Help button. You can access the user guide from the online help by clicking the View PDF button.
Product Documentation The following product documentation is available for WLSE: Table 1 Product Documentation Document Title Description Installation and Configuration Guide Describes how to install and configure the WLSE. Available for the 1130/1105 CiscoWorks Wireless in the following formats: LAN Solution Engine • Printed document included with the product.
Product Documentation Table 1 Product Documentation (Continued) Document Title Description Regulatory Compliance and Safety Information for the CiscoWorks 1130 Wireless LAN Solution Engine Provides regulatory compliance and safety information for the WLSE. Available in the following formats: • Printed document included with product. • PDF on the WLSE Recovery CD-ROM. • On Cisco.com: http://www.cisco.com/univercd/cc/td/doc/product/ rtrmgmt/cwparent/cw_1105/wlse/2_7/index.
Documentation Updates Table 1 Product Documentation (Continued) Document Title Description Converting Access Points to IOS, CiscoWorks Wireless LAN Solution Engine, Release 2.7.1 Describes how to convert non-IOS access points to IOS. Available in the following formats: Supported Devices Table for the CiscoWorks Wireless LAN Solution Engine • From the WLSE online help. • On Cisco.com: http://www.cisco.com/univercd/cc/td/doc/product/ rtrmgmt/cwparent/cw_1105/wlse/2_7/index.
Documentation Updates Required Software for APs with 802.11g Radios If you are using WLSE to manage APs or bridges with 802.11g radios, the APs must be running Cisco IOS version 12.2.15JA or later. WLSE is unable to push configuration templates to APs with 802.11g radios that are running previous versions. Disable Pop-Up Blocker While using WLSE, you should disable pop-up blocking software or add WLSE to the “Allow” list.
Documentation Updates Checking Redundancy Settings In the Redundancy Status Settings table, the description for the Turned Off redundancy status should be “Not configured.” The description for Minutes Between Sync should be “Synchronization interval. (Data synchronized from the active node to the standby node.
Documentation Updates Using Scanning-Only APs Step one in the “Using Scanning-Only APs” section should read: Use a template-based configuration job to configure one or more APs as scanning-only APs (see “Using IOS Templates”). Follow these guidelines when you create the template: • Keep the configuration simple. For example, do not configure VLAN/SSID for Scanning-Only APs. • Do not configure the scanning-only AP as an active/backup WDS (to serve fast roaming traffic).
Known and Resolved Problems Modifying AP Coverage Display Options An additional step should appear after step 5. The new step should read: Click Display coverage for operational radio interfaces only to display coverage for APs that are functional. If this box is checked (default), the coverage for radios that are determined to be down are not displayed. All other steps in this section are correct. Known and Resolved Problems Table 2 describes problems known to exist in this release.
Known and Resolved Problems WLSE Problems Table 2 Known Problems in the WLSE Bug ID Summary Explanation CSCeb36372 The Client Historical Association The Client Historical Association report does report does not contain a not have information about the last time a client disassociation time. associated with the AP, the time it disconnected from the AP, the duration of the association, or the association state. There is no workaround for this problem.
Known and Resolved Problems Table 2 Known Problems in the WLSE (Continued) Bug ID Summary Explanation CSCee03323 Rogue PHY type is reported as 11a when it should be 11b. On cb21ag, pi21ag, and ti21ag client adapters, when a rogue AP client is detected, the rogue report might indicate the rogue is an 11a PHY type when it is an 11b PHY type. There is no workaround for this problem.
Known and Resolved Problems Table 2 Known Problems in the WLSE (Continued) Bug ID Summary Explanation CSCee26055 ACS Login Failed Report produces error message. When you click the ACS Failed Login Report link to launch the ACS Failed Login Report, an error message appears saying a URL has not been provided for this link. There is no workaround for this problem. You can log in directly to the ACS server and look at the ACS Failed Login Report.
Known and Resolved Problems Table 2 Known Problems in the WLSE (Continued) Bug ID Summary Explanation CSCsa12358 Wireless Client Detail Report sometimes not showing correct state. Sometimes the wireless client detail report doesn't show the correct state of the client. In the reports it shows it as assocAndAuthenticated when it should show it as none.
Known and Resolved Problems Table 2 Known Problems in the WLSE (Continued) Bug ID Summary Explanation CSCsa13728 The wrong command is reported as failed when an IOS template job that has more than one command fails. If you create a template with more than one command, and one of the commands fails, the command that is reported as failed is not correct. To work around this problem, note the command previous to the one that is reported as failed; that is the one that has, in fact, failed.
Known and Resolved Problems Table 2 Known Problems in the WLSE (Continued) Bug ID Summary Explanation CSCsa13929 Version checking error occurs if template has 11g plus any 11a radio parameters. When you create a template for a dual mode IOS AP1210 that has any of the 11a interface parameters and has specific 11g parameters, the version checking fails to process and gives you an error that no valid device versions are supported.
Known and Resolved Problems Table 2 Known Problems in the WLSE (Continued) Bug ID Summary Explanation CSCsa15540 Inventory does not start for partially successful jobs. When a job is only partially successful, the inventory cycle does not start up, and the new information is not be displayed until the next regularly scheduled inventory. To work around this problem, create an on-demand inventory job for the access points that were successfully upgraded in the partially successful firmware job.
Known and Resolved Problems Table 2 Known Problems in the WLSE (Continued) Bug ID Summary Explanation CSCsa24492 WLSE cannot handle backslashes When using Microsoft Internet Explorer 6.0 on in the some fields. Windows XP, backslashes are not interpreted correctly. For example, if you select Devices > Discover > Credentials > WLCCP > Radius UserName and use a backslash in the user name, Internet Explorer does not remember the user name. There is no workaround to this problem.
Known and Resolved Problems Table 3 Resolved Problems in WLSE (Continued) Bug ID Summary Explanation CSCee39723 Location Manager coverage is displayed regardless of operational RIF status. When there is no radio measurement data (for example, before running Radio Scan, you delete Radio Monitoring or measurement data), coverage display is estimated with the default path-loss model and the transmit power configuration parameter.
Known and Resolved Problems Table 3 Resolved Problems in WLSE (Continued) Bug ID Summary Explanation CSCsa15394 WLSE 2.7 generates false WDS 0.0.0.0 faults when no WDS is configured. If an AP is not registered with any WDS, WLSE generates a fault saying the AP is registered with an unmanaged WDS (0.0.0.0) instead of generating a fault saying “AP is not registered with any WDS.” If you see a fault that says an AP is registered with an Unmanaged WDS 0.0.0.
Known and Resolved Problems Table 4 Resolved VxWorks to IOS Conversion Bugs in WLSE (Continued) Bug ID Summary Explanation CSCsa12593 Authorization and authentication are not configured in sync.
Known and Resolved Problems Table 4 Resolved VxWorks to IOS Conversion Bugs in WLSE (Continued) Bug ID Summary Explanation CSCsa20084 IP protocol faults default action cannot always be permit any. For the protocol filter, the converted configuration has permit any as the default. CSCsa20102 Cannot telnet to IOS AP after converting from VxWorks.
Known and Resolved Problems Table 4 Resolved VxWorks to IOS Conversion Bugs in WLSE (Continued) Bug ID Summary Explanation CSCsa21277 SSID is disabled after conversion if To work around this problem: Infra-SSID VLAN is not native. 1. Make sure the SSID that is mapped to the Native VLAN is set as infrastructure SSID before starting the conversion. 2.
Obtaining Documentation Obtaining Documentation Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems. Cisco.com You can access the most current Cisco documentation on the World Wide Web at this URL: http://www.cisco.com/univercd/home/home.htm You can access the Cisco website at this URL: http://www.cisco.
Documentation Feedback Documentation Feedback You can submit e-mail comments about technical documentation to bug-doc@cisco.com. You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address: Cisco Systems Attn: Customer Document Ordering 170 West Tasman Drive San Jose, CA 95134-9883 We appreciate your comments.
Obtaining Technical Assistance Opening a TAC Case Using the online TAC Case Open Tool is the fastest way to open P3 and P4 cases. (P3 and P4 cases are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using the recommended resources, your case will be assigned to a Cisco TAC engineer.
Obtaining Additional Publications and Information Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations. Obtaining Additional Publications and Information Information about Cisco products, technologies, and network solutions is available from various online and printed sources. • Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise.
Obtaining Additional Publications and Information • Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL: http://www.cisco.com/ipj • Training—Cisco offers world-class networking training. Current offerings in network training are listed at this URL: http://www.cisco.com/en/US/learning/index.
