Release Notes-HP Networking Management Software PCM 4.0 (04.00.00.1619)

IMPORTANT INSTALLER CHANGES IN PCM 4.0 (04.00.00.1619)

HP Networking recommends you use software version PCM 4.0 (04.00.00.1619) when upgrading your product. If you've previously installed PCM 04.00.00.1609 successfully, there is no need to uninstall it and install this version. The runtime execution of both versions is identical.

Important : HP recommends that you make a backup copy of your PCM server before you upgrade to PCM 4.0. For more information on making a backup of your PCM server, see the HP PCM+ 4.0

Migration Guide on the web.

The following summarizes the installer issues resolved in this software release. For more details, please see “Fixed Issues” on page 13.

■ CR_108019: PCM 3.x and MM 3.x upgrade to PCM 4.0 can take multiple hours.

■ CR_108020: “Data Migration Failed” error during PCM 3.x to 4.0 upgrade when Windows or the Regional Setting (locale) is not English.

■ CR_108591: Mobility Manager data migration failure results in misleading “The HP Mobility Manager trial period has expired” message.

■ CR_108697: In some cases, PCM 3.x to 4.0 upgrade fails to proceed beyond Installing PCM

Local Agent Service

■ CR_108787: After upgrading to PCM 4.0 / MM 4.0, you may experience unusual symptoms when accessing the WLAN Metrics tab.

■ CR_109041: Uninstalling PCM 04.00.00.1609 removes non PCM files.

For details on installer known issues in this release, see “PCM+/PCM 4.0 (04.00.00.1619)” on page 17.

Please Note: PCM+ 4.0 Licensing and Support

Due to Hewlett-Packard corporate software policies, software products such as PCM+ are required to incorporate maintenance licenses. The effects of this on software updates and technical support can be found here:http://h17007.www1.hp.com/docs/support/warranty/HPNetworkingProductWarrantySummary.pdf

Please see “PCM+ 4.0 Licensing and Operational Considerations” on page 5 for additional informa-tion.

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)

PCM+ Version 4.0 (with Network Immunity Manager integrated)Mobility Manager Version 4.0Identity Driven Manager Version 4.0

http://h17007.www1.hp.com/docs/support/warranty/HPNetworkingProductWarrantySummary.pdf

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=12883&prodSeriesId=3961207

© Copyright 2005 - 2012 Hewlett-Packard Development Company, LP. The information contained herein is subject to change without notice.

Publication Number

5998-2560February, 2012

Applicable Products

HP PCM 4.0HP PCM+ 4.0HP Mobility Manager 4.0HP Identity Driven Manager 4.0

Trademark Credits

Microsoft, Windows, Windows XP, and Windows Vista are registered trademarks of Microsoft Corporation.

Software Credits

SSH on ProCurve Switches is based on the OpenSSH software toolkit. This product includes software developed by the OpenSSH Project for use in the OpenSSH Toolkit. For more information on OpenSSH, visit http:// www.openssh.com.

SSL on ProCurve Switches is based on the OpenSSL software toolkit. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. For more information on OpenSSL, visit http://www.openssl.org.

This product includes cryptographic software written by Eric Young ([email protected]). This product includes software written by Tim Hudson ([email protected])

Open Source Software Acknowledgement

PCM and PCM+ uses two unmodified Open Source packages. The full source code and licenses to these packages can be found on the PCM distribution DVD in the OpenSourcePackages directory. These packages are:

1) JDesktop Integration Components. http://javadesktop.org/articles/jdic/index.html

2) JRadiusClient. http://jradius-client.sourceforge.net/

The following applies to both of these packages:

This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.

This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details.

You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA

Disclaimer

The information contained in this document is subject to change without notice.

These Release Notes are applicable at the date of the ProCurve Manager Version 3.20 Release. Please check the ProCurve Technical Support Web site at:

www.hp.com/networking/supportfor recent information.

The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.

Warranty

See the Customer Support/Warranty booklet included with the product.

A copy of the specific warranty terms applicable to your Hewlett-Packard products and replacement parts can be obtained from your HP Sales and Service Office or authorized dealer.

Hewlett-Packard Company8000 Foothills Boulevard, m/s 5551Roseville, California 95747-5551www.hp.com/networking

http://www.procurve.com

http://www.openssh.com

http://www.openssl.org

http://www.hp.com/networking/support

Release Notes Contents:Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)

IMPORTANT INSTALLER CHANGES IN PCM 4.0 (04.00.00.1619) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Please Note: PCM+ 4.0 Licensing and Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

PCM+ 4.0 Licensing and Operational Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Software Updates and Maintenance Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4PCM+ 4.0 Maintenance License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Release Notes and HP Security Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

PCM+/PCM 4.0 Notes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Using Firewalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6PCM+ 4.0 for HP Network Node Manager: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Network Immunity Manager (NIM) Integration into PCM+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Mobility Manager (MM) 4.0 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Identity Driven Manager (IDM) 4.0 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

What's New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10PCM+ 4.0 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10MM 4.0 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11IDM 4.0 New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Fixed Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13PCM 4.0 (04.00.00.1619) installation only fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13PCM+ 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13MM 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14IDM 4.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17PCM+/PCM 4.0 (04.00.00.1619) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17PCM+/PCM 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21MM 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23IDM 4.0 (04.00.00.1619) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23IDM 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)PCM+ 4.0 Licensing and Operational Considerations

PCM+ 4.0 Licensing and Operational Considerations

For customers migrating to PCM+ 4.0 from PCM+ 3.0 or PCM+ 3.1 or PCM+ 3.2, there are technical support and licensing considerations that you should be aware of prior to migrating. For detailed information, see the HP PCM+ 4.0 Migration Guide.

For customers installing PCM+ 4.0 as a new installation, see the HP PCM+ 4.0 Installation and

Getting Started Guide for licensing information.

Technical Support

If your PCM+ product was registered after 01 February 2009, the HP Technical Support included with the purchase price is for one year. To extend Technical Support for additional years, there are two options on PCM+ 3.00/3.10/3.20:

■ Purchase a Software Subscription Care Pack. NOTE: PCM Software Subscription Care Packs do not include major upgrades and you should not upgrade to PCMv4 if you are on a software subscription Care Pack for PCMv3.

■ Purchase a PCMv3 Maintenance License appropriate for your PCM v3 installation.

If you have installed PCM v3.20 and your product was registered less than a year ago, you can upgrade to PCMv4 without any additional purchases. Please see the HP PCM+ 4.0 Migration Guide.

If you are running PCM+ 4.0, Technical Support eligibility is determined by an active Maintenance License. The following information, as well as the HP PCM+ 4.0 Migration Guide, provides details about this license type.

Software Updates and Maintenance Licenses

For PCM+ 4.0, all product updates, including Auto Updates, and minor and major updates require that you have an active Maintenance License.

PCM+ 4.0 Maintenance License

For those customers that are migrating to PCM+ 4.0, please refer to the PCM+ 4.0 Migration Guide

for details about the PCM+ 4.0 Maintenance License.

For new installations, when PCM+ 4.0 is registered in the My Networking Portal, three licenses will be generated which are required to be installed on the PCM+ 4.0 Software Installation:

■ A PCM+ 4.0 platform license appropriate to your platform (e.g., 50 devices or Unlimited Devices).

■ A PCM+ 4.0 Agent License

■ A PCM+ 4.0 Maintenance License

4

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)Release Notes and HP Security Policy

The PCM+ 4.0 Maintenance License for new installation covers the first year of use and allows for Technical Support and Software Updates. After the first year is over, a new PCM+ 4.0 Maintenance License needs to be purchased and installed for Technical Support and Software updates to continue for the next year. This process would continue annually.

Release Notes and HP Security Policy

Per HP policy, a Security Bulletin must be the first published notification of a security defect. Fixes to security defects are not documented in release notes, also by HP policy. The official communica-tion for security defect fixes will always be through HP Security Bulletins. For more information on security bulletins, and information on how to subscribe to them, please see the following web site:

http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c02645131/c02645131.pdf

PCM+/PCM 4.0 Notes

Installation

■ 60-Day Free Trial – The PCM+ 4.0 installation download includes the functionality of the free-licensed product PCM 4.0. If after the 60- day trial of PCM+ 4.0, you decide that you need only the limited features of PCM 4.0, then you can go to the HP My Networking portal and acquire a free license to continue using PCM 4.0. Note that the free version supports only 25 devices and has significantly less functionality than PCM+ 4.0. After the 60 day free trial, if you have not purchased and installed licenses for PCM+ 4.0 or acquired and installed the free license for PCM 4.0, then you will no longer be able to use these HP network management tools. Installing a license prevents this from occurring.

The PCM+ 4.0 Installer also provides the option to install plug-ins PMM, IDM, and NIM. All plug-ins require PCM+ to operate. Since they are part of the trial, they too will stop operating after the 60-day trial. To continue using the plug-ins, you must purchase licenses for PCM+ and the plug-ins.

For Installation requirements and “how to” details, see the HP PCM+ 4.0 Installation and

Getting Started Guide available at the link below. (This includes the installation details for PCM, PCM+, MM, and IDM.

1. Go to http://www.hp.com/networking/support.

2. In the Auto Search field, enter the abbreviated product name, for example PCM.

3. Click the check box for any of the products that become listed.

4. Click Display selected.

5. Click on Product support information (manuals, FAQs, knowledge base).

6. On the Business Support Center page, click on Manuals.

5

http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c02645131/c02645131.pdf

http://www.hp.com/networking/support

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)PCM+/PCM 4.0 Notes

■ PC System Requirements and Supported Operating Systems – All PCM/PCM+ software and hardware installation requirements and supported PC operating system environments are listed in the HP PCM+ 4.0 Installation and Getting Started Guide.

■ PCM+ 4.0 Installation Directory – When you install PCM+ 4.0 as a new installation, the default installation directory is C:\Program Files\Hewlett-Packard\PCM. When you migrate from PCM 3.x to PCM+ 4.0, the installation directory that you used in PCM 3.x is copied to the PCM+ 4.0 system. The default installation for PCM 3.x was C:\Program Files\Hewlett-Packard\PNM. If the migration is on the same server, then the default installation directory will remain the PNM directory. If the migration is to a different server (for example from PCM 3.x on a 32-bit server to PCM+ 4.0 on a 64-bit server), then the end result of that process is that the default directory will be PCM. See the HP PCM+ 4.0 Migration Guide for more information.

Throughout the HP PCM+ 4.0 Network Administrator’s Guide, the …\PCM directory is mentioned, but the …\PNM directory is not. Please note that if your PCM+ 4.0 installation is a migration from PCM 3.x on the same server, wherever the Administrator’s Guide mentions the default directory as …\PCM, your default directory will be …\PNM instead.

You can specify a different installation directory during the installation or migration process, but once the software is installed/migrated you must not change the directory name. That would cause incorrect operation of your PCM+ 4.0 product.

Using Firewalls

If you are using firewalls in your network management environment, please note the following:

■ A firewall can exist between the PCM+ Server and the PCM+ Remote Agent, but it must be configured to allow communication between them. See “Agent Proxies” in the HP PCM+ 4.0

Installation and Getting Started Guide.

■ Because the communication between the PCM+ Remote Client and the PCM+ Server uses dynamic port assignments, we do not recommend placing a firewall between them. If there is a firewall present between client and server, the recommendation is to set up a VPN tunnel to traverse the firewall as the preferred method of reaching the server from the remote client.

■ A firewall between the PCM+ Agent and the managed devices associated with the PCM+ Agent is not supported.

■ The PCM+ Remote Agent packages its collected data and sends it to the PCM Server on port 51111. If this port is opened on the firewall, communications should happen normally between the PCM+ Server and PCM+ Remote Agents.

■ The PCM+ Local Agent sends traffic on port 51112, but since this agent is on the same computer as the PCM+ Server, no firewall typically exists between them.

6

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)PCM+/PCM 4.0 Notes

PCM+ 4.0 for HP Network Node Manager:

PCM+ 4.0 integrates with HP Network Node Manager Integrator (NNMi, version 8.1x and version 9.0) to provide a robust solution for managing HP network products in a multi-vendor environment. PCM+ 4.0 is targeted for medium-sized enterprise networks to provide the PCM+ functionality from the NNMi interface, including HP Networking device management, network traffic monitoring, sched-uled software updates, VLAN management, and policy management. For more information on PCM+ 4.0 integration with NNMi, see the HP PCM+ 4.0 Network Administrator’s Guide, Appendix A, “Integrating PCM with NNMi”.

Network Immunity Manager (NIM) Integration into PCM+

For PCM+ 4.0, NIM is a fully integrated component. NIM is no longer a separately installed plug in. Fixed and Known issues associated with the NIM functionality are identified with a “NIM” title in those sections in this document.

7

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)Mobility Manager (MM) 4.0 Notes

Mobility Manager (MM) 4.0 Notes

■ If you are migrating from PCM+ 3.00/3.10 to PCM+ 4.0, MM data may be lost.

• Status is not persistent. When devices are rediscovered after migration, then the status will be up-to-date

• MM rediscovers the network (with PCM) and refreshes config data for all discovered devices.

• 3.0x statistics are lost during migration.

• Preferences are migrated without any issues.

■ MM 4.0 requires that PCM+ 4.0 or later is installed.

■ MM 4.0 software is installed at the same time that PCM+ 4.0 is installed. You can choose whether or not to activate the trial version of MM 4.0 during the PCM+ 4.0 installation. See the HP PCM+ 4.0 Installation and Getting Started Guide for more information.

■ Since MM 4.0 is part of the PCM+ 4.0 60-day trial, it too will stop operating at the end of that period. To continue using MM 4.0, you must purchase licenses for PCM+ 4.0 and MM 4.0.

■ If the network contains Non MSM devices that are not configured with the default CLI passwords and SNMP credentials used by PCM, the elements associated with those wireless devices (for example, radios and SSIDS) may not be discovered. You should either pre-configure the access points with the access credentials used by PCM prior to starting discovery, or wait until the access point is discovered and use the Communication Parameters in PCM window to override the global defaults. You can then use Manual Discovery to re-discover the access point and its related radios and SSIDs, or you can simply wait until the next regularly scheduled discovery cycle collects the information.

■ PCM+ 4.0 software supports MSM devices as follows:

• Full support of MSM devices at software version 5.4.2 or higher.

• Limited support of MSM devices at software version 5.3.x.

• No support of MSM devices at software version 5.4.0 and 5.4.1.

■ Considerations when using the Teaming option on MSM7xx Controllers:

• All the wireless information about the team is reported from the manager controller, even the information on the member controllers. In MM 4.0, all the controlled APs of a team are displayed under the manager controller, no matter to which controllers they are connected. All the information about the team is reported on the manager controller as well. The only information available on member controllers is their up or down status. If the manager controller goes down, the APs will go under their elected manager controller, and information will continue to be collected and displayed under the elected manager controller.

8

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)Identity Driven Manager (IDM) 4.0 Notes

• PCM+ 4.0 collects basic data on the member controllers (for example, the SW version), but Mobility Manager doesn’t. Mobility Manager does not communicate directly with member controllers. That is why you see SW version in the PCM+ device Dashboard for the controller, but not in Wireless Properties/Status. All the team functionalities are not affected, though, and they are reported by the manager controller.

• All wireless information and wireless configuration managed by MM 4.0 is communi-cated through the manager controller, and these parameters cannot be different on the member controllers.

■ To establish communication for MM 4.0 to get all radios and WLANs information from the MSM devices running software version 5.4.2 or higher (except 5.4.0 and 5.4.1), the TCP ports 7667 and 7668 must not be blocked on the computer running the PCM agent. This may be a problem if you have activated Windows firewall or are running other firewall software on that computer.

■ To avoid running out of HEAP space on your PCM management computer, if you are managing a large number of wireless devices (usually more than 800), use a text editor to make the following changes to the files Tornado.ksh and Typhoon.ksh in the directory \Program Files\Hewlett-Packard\PCM\pcm agent:

• Tornado.ksh:

Change the -Xmx value from 1024m to 2048m. The correct statement in the file is:

$JAVA -XX:MaxPermSize=256m -Xms256m –Xmx2048m -cp "$CLASSPATH" com.hp.nis.tornado.boot.TornadoBoot -out -err $@

• Typhoon.ksh:

Change the -Xmx value from 1024m to 2048m. The correct statement in the file is:

$JAVA -Djava.library.path=$LIB -Xms256m –Xmx2048m -cp "$CLASSPATH" com.hp.nis.typhoon.Typhoon -config $CONFIG/TyphoonServer.cfg -v -out -err -ipfile config/commIpAddr.txt $@

Identity Driven Manager (IDM) 4.0 Notes

■ IDM 4.0 requires that PCM+ 4.0 or later is installed.

■ IDM 4.0 software is installed at the same time that PCM+ 4.0 is installed. You can choose whether or not to activate the trial version of IDM 4.0 during the PCM+ 4.0 installation. See the HP PCM+ 4.0 Installation and Getting Started Guide for more information.

■ Since IDM 4.0 is part of the PCM+ 4.0 60-day trial, it too will stop operating at the end of that period. To continue using IDM 4.0, you must purchase licenses for PCM+ 4.0 and IDM 4.0.

9

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)What's New

What's New

PCM+ 4.0 New Features

The following new and enhanced network management features are supported in PCM+ 4.0:

■ Network Services Monitoring

Proactive monitoring and reporting on the network services which businesses rely on (HTTP, DHCP, DNS, FTP, etc.)

■ PoE Visualization and Monitoring

Real-time and historical view of network PoE availability and usage

■ Integrated Network Threat Detection

• Network-based anomaly detection and policy-based actions to mitigate network threats.

• HP Network Immunity Manager functionality delivered as part of the PCM platform.

■ Automated Network Troubleshooting and Diagnostics

• Reports to proactively identify common network mis-configurations.

• Automation to collect and report troubleshooting information to support.

■ Web User Interface

• Simplifies management from anywhere.

• Improves performance for distributed deployment.

• Primarily focused on viewing data and not active changes in this release.

• Mobile version available.

■ Licensing and Simplified Product Updates

• Subscription-based licensing enables more rapid delivery of features to customers.

• Simplified product update process allows users to update more easily and often with fewer issues.

• Device counts now centralized in the PCM+ platform for wired and wireless devices. Mobility Manager is an enablement license.

■ Discovery and Monitoring Improvements

• Enabling multiple credentials improves accuracy of network discovery and monitoring.

• Folder and Group level device status indicators make identifying faults easier and more efficient.

■ Mapping Enhancements

• MSM devices running in control-mode mapped on L2 maps.

10


• Maps for customer-defined custom groups.

• Mapping of MSM Devices and HP WESM controlled Radio ports is now supported.

■ Virtual Device Support: Logical presentation of Teamed/Grouped devices such as MSM Controller Teams, stacked switches.

■ Distributed Management Optimizations: Improved performance in a distributed deployment.

■ IPv6 Aware: Identifies devices with IPv6 capabilities and IPv6 configured on maps and inventory reports.

■ Support for International Versions of Windows OS: French, Italian, German, Spanish, and Japanese

NIM New Features and Enhancements

■ NIM is now fully integrated with PCM+. You are not required to purchase a separate license to use NIM.

■ Modified panels in the NIM dashboard and NIM configuration to reflect the integration of NIM into PCM+.

■ Client Optimization: Delayed the loading of data into NIM dashboard until PCM model initialization is complete.

■ Enhanced the NIM integration support for RF Manager (v6.0.157).

MM 4.0 New Features

The following new and enhanced features are supported in MM 4.0 (“See” references are to the HP

Mobility Manager 4.0 Network Administrator’s Guide. See that guide for more detailed informa-tion):

■ Reporting and Performance: MM v4 works faster than MM v3.

■ Simplified Licensing: MM license is no longer based on device counts; devices are only counted in the PCM+ license product(s).

■ Wireless LANs (WLAN SSID): Added performance monitoring, properties view, and security configuration.

■ Improved usability in Site View.

IDM 4.0 New Features

HP IDM 4.0 includes the following new features and enhancements:

■ Registration Server enhancements to simplify administrative load network access control

■ Simple Network Access Control (SNAC) support, including:

11


• IAS/NPS RADIUS server support

• An Admin GUI for configuration and history and SSL certificate configuration

• A SNAC-IDM communication interface

• SNAC 802.1X hybrid solution support

■ The capability to register multiple devices per user

■ An integrated PCM/IDM installer

■ IDM Support for IPv6

■ Auto-allow capabilities

■ The capability to dynamically load OUIs from a file

■ IDM GUI enhancements

■ IDM 3.20 AU1 content merge

12

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)Fixed Issues

Fixed Issues

PCM 4.0 (04.00.00.1619) installation only fixes

Note:The user cannot fix a failed upgrade by installing PCM 4.0 (04.00.00.1619) onto the failed PCM 4.0 migration. Rather, PCM 4.0 (04.00.00.1619) is intended to be a new installation or used to upgrade from PCM 3.x.

The following issues are resolved in PCM+/PCM 4.0 (04.00.00.1619):

■ CR_108019 -PCM 3.x and MM 3.x upgrade to PCM 4.0 can take multiple hours.

■ CR _108020 - If Windows or locale is not English during a PCM 3.x to 4.0 upgrade, then a Data Migration Failed error message appears, and the database becomes no longer accessible.

■ CR_108591 -After PCM 3.x and MM 3.x upgrade to PCM 4.0, The HP Mobility Manager trial

period has expired message is displayed due to a failed data store migration.

■ CR_108697- In some cases, PCM 3.x to 4.0 upgrade fails to proceed beyond Installing PCM

Local Agent Service.

■ CR_108787 - After upgrading to PCM 4.0 / MM 4.0, you may experience the following symptoms when accessing the WLAN Metrics tab:

• The Unreachable icon is displayed in the time slider, and no charts are displayed.

• You cannot access other PCM or MM tabs or screens.

• You cannot exit PCM/MM normally, you must end the (javaw.exe) process using Windows Task Manager.

■ CR_109041: If PCM 4.0 is installed on the System Drive (drive where the OS is installed), then uninstalling PCM 4.0 also deletes all files (but not subdirectories) under the root directory of the System Drive. For example, if the System Drive is C:\ and PCM 4.0 is installed under a folder in C:\, then uninstalling PCM 4.0, also deletes all files under C:\. Folders under C:\ are not deleted.

PCM+ 4.0

The following issues were resolved in PCM+/PCM 4.0:

■ CR_14119 – Alarm Trend Graph is not completely plotted.

■ CR_14771 – Policy Manager fails to Execute VT Action on the some ports if device has Mesh and Trunk Ports configured.

13


■ CR_14853 – Export subnet/devices uses agent ID in CSV output instead of the agent name.

■ CR_14924 – Print report is grayed out for agents list in the agent tab of agent groups folder.

■ CR_15003 – Inconsistencies among right-click menus and sub-menus.

■ CR_15229 – Port Assignment table: columns are not sorted correctly.

■ CR_15331 – Devices ordered inconsistently with Nav Tree.

■ CR_15464 – Historical Event Aggregation Report returns error when executed from Remote Client.

■ CR_43618 – Agent Status mismatch across different places in PCM+ Remote Client.

■ CR_43922 – “Port Access Security Configuration” report is not sorted.

■ CR_44086 – Un-check all checkboxes.

■ CR_53614 – The Historical Event Aggregation Report returns an error when executed from a Remote Client.

■ CR_55286 – PCM+ fails to find end nodes and PCs connected behind IP phones.

■ CR_55337 – Config Compare failed to perform the compare operation based on date and time.

■ CR_55490 – Annotations will disappear from the LLDP and End Host map.

■ CR_55827 – PCM+ SCP scan failure with 15.05.0002 only.

■ CR_102922 – Agent Manager and Agent Web UI should not allow a blank password for Server/Agent.

The following issues were resolved in NIM 4.0:

■ CR_006836 – It is not possible to exclude events of different categories with the same offender MAC address via the NBAD Wizard.

■ CR_043394 – MAC address is shown as NULL when an event is excluded through the NBAD exclusion wizard.

■ CR_043429 – NIM policies are not getting executed as expected when a device is behind an IP phone.

■ CR_055558 – NBAD diagnostic wizard does not show the actions once the 'show' option is selected.

MM 4.0

The following issues were resolved in MM 4.0:

14


■ RF Planner (CR_16775) – Confidence Level for Wireless Clients and Site Neighbors is always displayed as Low in the mouseover displays in the RF Planner Site View.

■ Site Planner (CR_16784) – Site planner places clients on top of each other.

■ RF Planner (CR_16791) – RF Planner: sometimes the Refreshing Site progress dialog looks like it is getting frozen when adding Stations to the canvas.

■ Scalability (CR_16812) – Client responsiveness is slow after 5 days of uninterrupted operation with 2000 devices.

■ Teaming (CR_16820) – Charts for the Manager Controller have wider time intervals than the configured values.

■ PR_54350 – Cannot open group in Wireless Site summary.

■ CR_102590 – In some Site Edit screens, distance units could be interpreted incorrectly.

■ CR_102670 – Gaps in wireless statistics charts.

■ CR_103149 – Wireless Client falsely reported in wireless status and wireless metrics tab.

IDM 4.0

The following issues were resolved in Identity Driven Manager 4.0:

■ PR_43184 – IDM cannot create a wireless based location (CR 5235).

Steps to Reproduce

1. Select the IDM Tab and navigate to IDM Home > Realms > Default Realm > Access Policy Group.

2. Select either the Default Access Policy Group or create a new Group.

3. Right-click and select Configure Identity Driven Manager.

4. Select the Locations folder.

5. Select the New Location icon.

6. Select the Wireless Devices Tab.

7. Select the Add Device button.

8. Attempt to select any Wireless device and select OK. Nothing happens.

■ CR_43994 – User Counts are inaccurate because RADIUS accounting-stop packets exceed the “integer” limit of 2.13 GB.

■ PR_63408 – User Authentications are discarded by IAS due to a session timeout (CR 6771).

15


When authentication takes longer than 15 seconds, IDM does not insert the RADIUS attributes as configured in the Policy. As a result, user authentication fails.

Steps to Reproduce

1. Create a group in Active Directory group with some international character.

2. Add some users to group.

3. Go to Identity management and enable automatic deployment to IDM agents.

■ PR_65156 – Unable to configure VLAN on HP switch 2626 using IDM deployer (CR-15251).

16

Release Notes: HP Networking Management Software, PCM 4.0 (04.00.00.1619)Known Issues

Known Issues

PCM+/PCM 4.0 (04.00.00.1619)

The following are known issues for PCM+/PCM 4.0 (04.00.00.1619) release:

■ CR _108250 - PCM 4.0 installation fails on Win2008 R2 SP1 64-bit systems when Application

Experience service is disabled. Enable and Start the service, and install the product again.

■ CR_109104: PCM GUI shows remote Agent in a down state after remote Agent upgrade from PCM 3.x to PCM 4.0.

A remote Agent upgraded from PCM 3.20 to PCM 4.0 may fail during the download of the new PCM 4.0 Agent software. After upgrading your server and rebooting (as directed), you will see that your local Agent and remote Agents are being updated to PCM 4.0. This update progress can be monitored on the Agent Groups' Agents tab. The first sign that you may have run into this failure is a remote Agent’s status being shown as red in the PCM 4.0 Agent manager, long after all other Agents have been successfully upgraded. This normally takes about 15-20 minutes.

How to determine if this failure has occurred

1. Log into the remote Agent that has failed to come up and go to the <Agent-Install-Dir>/pcm-agent/log directory.

2. Open the wrapper.log file and look for the following text:

[DownloadMgr::ERROR]ERROR 1005 (HY000) at line 6: Can't create table '.\pcmagent\dbversiontable.frm' (errno: 121)

or else this text at the end of the file:

There were 10 failed launches in a row, each lasting less than 300 seconds. Giving up. There may be a configuration problem: please check the logs. <- - Wrapper Stopped

If you see either of the above text strings, the upgrade process has had a failure that requires the recovery actions below.

How to recover from the remote Agent upgrade failure

1. Reboot the remote Agent that has failed (to cleanup any hung PCM processes).

2. On the remote Agent host machine, uninstall the remote Agent application using standard operating system tools.

3. IMPORTANT: You must install the agent to the same directory of the Agent that was just uninstalled. Install the PCM 4.0 remote Agent using the standard process, as documented in “Agent-initiated Connections” the HP PCM+ 4.0 Network Administrator’s Guide.

If the install fails (usually with a file in use message), exit the installer and repeat steps two and three. It should succeed the second time.

17

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64179&taskId=101&prodTypeId=12883&prodSeriesId=3961207


After the remote Agent installation completes successfully, the PCM 4.0 server should show this Agent being updated.

Note: If it is found that the database services is not working correctly on the PCM 3.20 remote agent, it is recommended that the agent be uninstalled and reinstalled prior to upgrading the PCM server to version 4.0.

■ CR_109378: PCM 3.x to 4.0 upgrade with server database containing unsupported charac-ters will cause Unsupported Character Input messages in PCM 4.0.

Note: A new panel was added to the PCM 4.0 (04.00.00.1619) installer to warn customers not to upgrade from PCM 3.x if they think their PCM server database contains unsupported characters. Customers may choose to remove any unsupported characters before migrating to PCM 4.0 or they can remove them in response to Unsupported Character Input messages in PCM 4.0.

PCM 3.20 required characters to be English (US) but did not enforce it. With the addition of support for Internationalization in PCM 4.0, PCM 4.0 does do the enforcement. This enforcement with PCM 4.0 and not with PCM 3.x can cause garbled text to appear in the GUI after upgrading from PCM 3.x to PCM 4.0, if the database in PCM 3.x contains non-English (US) characters. You will see Unsupported Character Input messages when using PCM 4.0. You will need to change the unsupported characters to end these messages.

The following characters are supported for character input in PCM 4.0:

!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝ Þßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ

Invalid characters can be corrected from the product GUI. Here are some examples.

18


Policy Manager

When the Policy Manager is first opened, the alert with the unsupported characters in the name is shown on the left hand navigation screen. When you select that alert, you are presented with the Unsupported Characters dialog. Select OK on this dialog box, and then provide a new name/description for the alert which uses supported characters.

The updated name or description for the policy is immediately reflected in the left hand navigation tree:

19


Custom Group Names

When the Custom Groups tab is first accessed, the group names and descriptions are presented as they were configured in PCM 3.X. When you select one of these custom groups and attempt to modify it, you are presented with the dialog box for Unsupported Characters.

You must click OK on this dialog box to access the configuration screens for this custom group. When the configuration screen appears, the name and description fields will be empty. Enter a new name for the custom group at this time. You can type directly into the available fields.

20


Note: HP recommends that you update all configured custom groups to use only supported characters in their name prior to changing a group’s membership.

Unsupported characters may appear in names or descriptions as ‘?’. Replace these characters with supported characters to correct the problem.

PCM+/PCM 4.0

The following are known issues for PCM+/PCM 4.0:

■ CR_15447 – Historical PoE reports fail to show the Power/Ports value in the graph.

■ CR_43164 – I18N and certain platform specific limitations.

■ CR_43716 – PCM+ 4.0: Users able to generate reports outside their user profile.

■ CR_43908 – If a minor version exists for a major version which has not been installed, the status column shows unexpected values.

■ CR_52423 – RADIUS probe fails to work when the NPS Message Authenticator Attribute is enabled.

■ CR_52434 – Internet probe limitations.

■ CR_52573 – MSM Team not moved properly when move subnet is performed across agent.

■ CR_52574 – Team node is not displayed the subnet map.

■ CR_52753 – IP address for Radio ports is shown as 0.0.0.0 in Server Web UI.

■ CR_52859 – IPv6 Address is not shown in server web UI.

■ CR_53567 – Trap Receiver action is not working as expected.

■ CR_53655 – After transition from/to failover mode, CAPs are displayed twice in navigation tree.

■ CR_53682 – NSM Report Limitations.

■ CR_53772 – DHCP probe failed to run in DHCP enabled IP mode.

■ CR_53888 – Multiple probe selection and probe management behaviors.

■ CR_53945 – PCM online help does not come up when Chrome is the default browser.

■ CR_54171 – Changes made to the default agent after installation do not take effect on the remote agent after the agent is activated.

■ CR_54217 – NSM Dashboard limitations.

21


■ CR_54691 – Stacked device support: Individual members should be allowed to be discov-ered if each member is also configured with OOBM IP address.

■ CR_54693 – Stacked device support: PCM discovers duplicate stack when switchover happens, if stack has both VLAN IP and OOBM IP configured.

■ CR_55336 – Config Scan using SCP and its sub-options are not making correct validations.

■ CR_55878 – Test Communication Parameter produces incorrect report in certain scenarios.

■ CR_56062 – Link speed is shown as 0Mb for MSM 430, MSM 460, and MSM 466-R.

■ CR_102568 – Wireless Properties and status should be shown in the Server web UI/Mobile.

■ CR_103458 – Combination of V2 and V3 devices and Communication parameters in PCM operation failure.

■ CR_103502 – Custom group and user profiles of Team members are not handled properly after migration.

■ CR_103503 – Rebranding limitations.

■ CR_103506 – Unable to launch Uptime Report for the devices in 4.0 which were polled in 3.2 but not discovered in Tree.

■ CR_103772 – Sometimes a user needs to relaunch the client to see the Team members under the team node after Teams are migrated from PCM 3.x to PCM+ 4.0.

■ CR_104061 – PCM+ 4.0: The template is not added under Configuration Template tab after it is created.

■ CR_104121 – Device Registration and Portal credentials failure behavior in PCM.

■ CR_104297 – NSM Probe execution and Server-Agent time sync failure behavior.

The following are known issues for NIM:

■ CR_043149 – The Firewall wizard does not reflect the existing values for IP Reassembly when a single device is selected.

■ CR _052614 – NIM dashboard data is not displayed for the 'Top offender' panel and the 'Device Trouble Spot' panel for more than 2367 devices across the WAN Link (latency=25ms).

■ CR _104009 – The RF manager alert is duplicated in migrated set-up from PCM 3.20 to PCM+/PCM 4.0 along with NIM 2.20 auto-updates.

■ CR_104012 – The Rate-limiting option is disabled by default through NBAD diagnostic Wizard.

22


MM 4.0

The following are known issues for MM 4.0:

■ PR_53748 – MSM 460/466 supports up to 23 Rx/Tx MCS but MM displays only up to 15.

■ PR_54255 – Wrong data is displayed in VLANID field for AP530.

■ CR_102582 – The Rate Value is always displayed as “0” when the tool tip from a Wireless Client is displayed.

■ CR_102872 – Teaming: The Device Wired Throughput report does not contain data related to Slave controller (master controller during failover).

■ CR_103277 – Wireless Status: Port Status for a MSM720 in MM doesn't match the Port Status shown in the controller GUI.

■ CR_103775 – Performance: Client reacts slowly during devices discovery with 2500 wireless devices.

■ CR_104169 – Wireless Metrics: mismatch between the chart Associated Wireless Clients History and the Wireless Associations table when a new wireless client is connected

IDM 4.0 (04.00.00.1619)

The following are known issues for IDM 4.0 (04.00.00.1619) release:

■ CR _109102 - IDM server not processing Session Interim Update Information for already logged in users post migration.

Steps to Reproduce

1. Install PCM version 3.20.

2. Install IDM Agent on Linux/windows.

3. Activate IDM agent.

4. Import users.

5. Authenticate the User.

User is now authenticated successfully, and is shown as logged in IDM client. Ensure there accounting interim update or reauth is configured on the switch.

6. Migrate PCM server to version 4.0 (build 1619).

7. After successful migration do forceupdate on IDM agent to ensure IDM agent is also upgraded to Version 4.0.

8. Configure session account interim update in the switch.

9. Reauthenticate the user.

23


10. IDM now shows user as logged in to the IDM client.

11. After some time notice the session info of the user in IDM client, the following details are not updated:

– Framed IP address: (IP address of the client).

– Input octet.

– Output octet.

Workaround

It is recommended that users are logged out of the network, and then login after the migration procedure is complete.

IDM 4.0

The following are known issues for IDM 4.0:

■ CR_44253 – Enter /Tab keystrokes are not working as expected in all SNAC admin UI screens.

Steps to Reproduce

1. Install IDM 4.0 Agent.

2. Install SNAC registration server.

3. Login to SNAC server admin UI.

4. Provide Username and password and click on Enter. User is expected to login to the admin UI. But the Enter keystroke does not work.

5. Click on Tab keystroke. That does not work either. Only the mouse click works.

6. Try the same for all the options in the SNAC admin UI.

Actual Results

Enter /Tab keystrokes are not working in any of the above mentioned screens for save/cancel options. You must use the mouse to do the operations.

■ PR_45894/CR_5574 – Manual deploy is needed to send changes made to the “Only send supported device attributes to device” property.

■ CR_53933 – The IDM agent fails to connect to a new server when it is removed from one server and added to the other IDM server, in a server initiated connection.

24


Steps to Reproduce

1. Install a IDM server.

2. Install an agent with a server initiated connection and add it to this server using the agent manager which when successful, the agent is in an activated/connected state.

3. Now install one more server.

4. Deactivate and delete the agent from the first server and add it to the second server.

Actual Results

The agent remains in an activated/disconnected state and never gets connected to the server.

■ CR_54170 – Even though the IDM agent (server initiated connection) is deleted using the agent manager, it shows up in the IDM tree.

Steps to Reproduce

1. Add an IDM agent (server initiated connection).

2. Activate it. It appears in the idm tree and dashboard.

3. Delete the agent using agent manager.

4. It is not deleted from the tree, and in the dashboard agent status appears to be up.

Actual Results

The agent is not deleted from the tree and in the dashboard agent status appears to be up.

■ CR_55438 – User accountability missing when the IDM Server gone down.

Steps to Reproduce

1. Install IDM 4.0.

2. Ensure the configured user gets network access (i.e. configuration deployment is the right one).

3. Deploy the configuration on the agent and then shut down the IDM server for while.

4. Login the user and after some time logout. Also try with incorrect credentials.

5. Stop the user login process.

6. Power on the server (IDM) and open the IDM console and wait (10 mins.) to update.

Actual Results

The agent is not sending user (logged) information to the server and server is not showing the offline account information.

25


■ CR 56056 - The failed login data is incorrectly shown in Logins per hour pane of the realm dashboard.

Steps to Reproduce

1. In IDM 4.0 have 2-3 access policy groups.

2. Have some successful and some failed logins in these groups.

3. Check the dashboard.

Actual Results

The IDM home dashboard shows successful and failed login properly. Each access policy group dashboard shows the logins per hour data properly as well. However in the realm dashboard the logins per hour pane shows successful logins properly but the number of failed logins is not cumulative of all failed logins found in the access policy groups of that realm. Instead it takes only one realm into consideration.

■ CR_102824 – dot1x authenticated user name is not shown in Dash board (Edir as well as openldap setup).

Steps to Reproduce

Try to authenticate 802.1x user in eDirectory setup and verify the user status using “Users Tab”.

Actual Results

dot1x authenticated user name is not shown in Dash board (Edir as well as openldap setup).

■ CR_102981 – MAC address does not get prepopulated on Android running 2.2 version and below.

In MAFR scenario, if we use any device running Android 2.2 version, upon successful MAFR redirection, the SNAC registration get devices page does not get pre-populated with device MAC address. Just to note, the URL did have the MAC address of the device.

Steps to Reproduce

1. Have any Android device running 2.2 version undergo MAFR successfully

2. We will see that get device page does not have the MAC address prepopulated even if the MAC address was present in the URL

■ CR_103052 – If a 127.0.0.1 address is given as a server IP for an agent initiated connection for a single server setup, deploy config fails.

Steps to Reproduce

1. Install PCM 4.0.

26


2. Install IDM agent on the same machine with an agent initiated connection.

3. During installation when asked for server IP provide 127.0.0.1.

4. Installation is successful, however deploy current policy to the domain fails.

5. After installation if you change the IP to the IP address of the machine two instances of the agent get added; one as 127.0.0.1 and the other as the IP of machine.

Actual Results

1. Installation is successful, however deploy current policy to the domain fails.

2. After installation if you change the IP to the IP address of the machine two instances of the agent get added; one as 127.0.0.1 and the other as the ip of machine.

■ CR_103610 – Switch not sending RADIUS accounting start and stop request for web-auth and mac-auth in some cases (i.e., after access-accept, the IDM attribute, like VLANs, is not present in the switch) when the access-accept carries ACL and VLANs information to the switch. If the VLAN is not present, the switch should terminate the user and immediately initiate the accounting -start and stop.

■ CR_103675 – Status window not shown while upgrading agent from Remote PCM client.

1. Try migrating IDM 3.x to IDM 4.0.

2. After migration try to update the Agent from PCM remote client.

Even though the status window is not shown, the process goes through.

■ CR_103799 – IDM GUI performance becomes extremely sluggish during continuous hours of operation testing.

Steps to Reproduce

Install SNAC registration server as part of IDM installation. Leave the server running without performing any registrations for more than 5 days.

Actual Results

Logs roll over with PongException.

■ CR_103835 – SNAC Administrator password characters allowed inconsistent between PCM installer and SNAC Admin UI.

Steps to Reproduce

Try to configure a SNAC Administrator password including the “@” special character.

27


Actual Results

You receive an “Invalid character” error message.

■ CR_103836 – PCM installer password characters allowed for PCM Administrator and SNAC Administrator inconsistent.

Steps to Reproduce

Enter a password containing “!?” for both PCM and SNAC Administrator.

Actual Results

Password described above succeeds for PCM Administrator and fails for SNAC Administrator.

■ CR_104080 – While changing https port, changing password should not be made mandatory.

Steps to Reproduce

1. Change the default password for SNAC admin UI from blank to some other password using SNAC admin UI.

2. Save the settings.

3. Login to SNAC admin UI with the new password and try to change the https port and save the settings.

4. It shows an error message about the wrong old password.

This is the case for changing any fields; for example, changing the username/Login page banner text should not require the password to be changed.

■ CR_104954 – Auto-allow OUI does not work for 802.1x/web-auth users.

Steps to Reproduce

1. Perform AD sync to synchronize a group, say facultyGroup (containing the user facul-tymember) from AD.

2. Configure an auto-allow OUI under another group, namely auto-grp.

3. Use a device (laptop/iPad) whose MAC address matches that of the configured OUI to perform 802.1x authentication by supplying domain credentials of facultymember.

4. The user, facultymember, gets moved from facultyGroup to auto-grp.

5. Get another laptop/iPad whose MAC address is different and does not match the configured OUI.

6. Perform 802.1x authentication with this device using the same domain credentials of facultymember.

7. This device is not assigned to facultyGroup but put into Default Access Policy Group.

28


Actual Results

The user is moved into default access policy group instead of facultyGroup.

Expected Results

The user should be assigned facultyGroup.

■ CR_105310 – SNAC registration service startup can be slow - up to a few minutes.

■ Find user does not work. Find user dialog works only based on Mac-Address field. If the value provided for the “Username” field matches that of “Auth ID” in the tab view and there is session history available for that user entry, then find user will provide those details.

■ Known issues in switch software:

CR_77338 – HTTP Redirect attempt using MAC Authentication Failure Redirect (MAFR) to resolve a fully qualified domain name fails in the 3800 (K.15.03.3004) release.

CR_102585 – Enhance MAFR to handle URLs with IP addresses.

CR_103285 – A device using a port on an IP Phone does not re-authenticate in SNAC if the device authenticates before the IP phone. In short, the device authenticates, then the IP phone authen-ticates, and then the device needs to re-authenticate at some later point but the switch will not recognize that re-authentication.

CR_103557 – A switch running K.15.06.0006 does not redirect client browser MAC Authentica-tion Failure Redirect (MAFR). The switch behavior is different depending on the order of configuration. If web-ssl is configured, then MAFR, then the redirect simply doesn’t happen. If MAFR is configured, then web-ssl, the switch will take a software exception.

29

Documents

Release Notes-HP Networking Management Software PCM 4.0 (04.00.00.1619)