Release Notes: ProCurve Management Software. Release Notes Contents: IMPORTANT: PCM/PCM Plus 3.20 Licensing and Support Changes

Transcription

1 ProCurve Manager Plus Version 3.20 Mobility Manager Version 3.10 Identity Driven Manager Version 3.20 Network Immunity Manager Version 2.20 IMPORTANT: PCM/PCM Plus 3.20 Licensing and Support Changes Due to Hewlett-Packard corporate software policy changes, software products such as PCM/PCM+ and plug-ins to PCM+ will be required to incorporate maintenance licenses. These changes affect software updates and technical support, and can be found here: Please see PCM/PCM Plus 3.20 Licensing and Operation Changes from PCM 3.10 and Previous Versions on page 3 for additional information. Release Notes Contents: PCM/PCM Plus 3.20 Licensing and Operational Changes from PCM 3.10 and Previous Versions.. 3 Technical Support Software Updates and Maintenance Licenses Maintenance License Clarification PCM+ v3 Migration Scenarios Additional Migration Notes License Types Release Notes and HP Security Policy PCM/PCM Plus 3.20 Notes Installation Using Firewalls (PR_62722) PCM Plus for HP Network Node Manager Mobility Manager 3.10 Notes Identity Driven Manager 3.20 Notes Network Immunity Manager 2.20 Notes What's New PCM/PCM Plus 3.20 New Features Mobility Manager 3.10 New Features Identity Driven Management 3.20 New Feature Network Immunity Manager New Features and Enhancements Additional Information Fixed Issues

2 Copyright , 2009, 2010 Hewlett-Packard Development Company, LP. The information contained herein is subject to change without notice. Publication Number December, 2010 Applicable Products ProCurve Manager 3.20 ProCurve Manager Plus 3.20 ProCurve Mobility Manager 3.10 ProCurve Identity Driven Manager 3.20 ProCurve Network Immunity Manager 2.20 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 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 This product includes cryptographic software written by Eric Young This product includes software written by Tim Hudson 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. 2) JRadiusClient. 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 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: for 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 Company 8000 Foothills Boulevard, m/s 5551 Roseville, California

3 PCM/PCM Plus 3.20 Licensing and Operational Changes from PCM 3.10 and Previous Versions PCM/PCM Plus 3.20 Licensing and Operational Changes from PCM 3.10 and Previous Versions For customers migrating to PCM from a previous version of PCM+ v3, there are technical support and licensing changes that you should be aware of prior to migrating. 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: Purchase a Software Subscription Care Pack. Upgrade to PCM If you are running PCM+ 3.20, Technical Support eligibility is determined by an active Maintenance License. The following information as well as the HP PCM 3.20 Migration Guide provides details about this new license type. Software Updates and Maintenance Licenses Auto Updates to PCM+ v3 platforms, when and if available, do not require an Active Maintenance License. Minor updates to PCM+ v3 platforms (for example, to PCM 3.30), when and if available, do require an Active Maintenance License. Major updates to PCM+ v3 platforms (for example, to PCM 4.00), when and if available, do require an Active Maintenance License. Maintenance License Clarification What type of Maintenance License you need is solely dependent on what platform you initially registered: PCM+ 50-device license, or PCM+ unlimited device license. If you have added device licenses to supplement the 50-device platform license, you will still only need to use the 50-device Maintenance License. 3

4 PCM/PCM Plus 3.20 Licensing and Operational Changes from PCM 3.10 and Previous Versions PCM+ v3 Migration Scenarios It is very important that you familiarize yourself with the HP PCM 3.20 Migration Guide. However, this section of these Release Notes is meant to provide clarity to the Understanding PCM Licensing section on pages 2-8 through 2-14 of the Migration Guide. The following flowchart provides an overview: Are you running PCM+ or PCM (free) PCM Free PCM+ Uninstall PCM No PCM+ 3.0 or 3.10? 3.0/ PCM+ 2.3 or earlier? Earlier YES PCM+ Device License Registered on the mynetworking portal between November and November ? NO Upgrade Upgrade or Uninstall Purchase Upgrade License (J9173A or J9176A) from a reseller Upgrade to PCM+ 2.3 Uninstall PCM Go to mynetworking portal Purchase maintenance license J9630A or J9631A from reseller Install PCM 3.20 Purchase Base Software License J9174A or J9177A Go to mynetworking portal and generate a license key Under View Registration IDs, a REG-ID for the J9689A PCM v3.2 Platform Upgrade should be available Go to mynetworking portal and generate a license key (Use the Products Without Registration ID Path) Install PCM Provide License Key to PCM 3.20 Installer When Prompted DONE 4

5 PCM/PCM Plus 3.20 Licensing and Operational Changes from PCM 3.10 and Previous Versions Scenario #1: PCM registered prior to 09 November 2009 is upgrading to PCM To upgrade to PCM in this scenario, complete these steps: 1. Purchase a J9630A or J9631A Maintenance License from a reseller (the same way you would normally obtain PCM+ device licenses). 2. Go to the mynetworking portal, select My Licenses, and enter in the Registration ID from the J9630A/J9631A that you purchased: 3. Click the Next button and follow the wizard to generate a license key. 4. Enter that license key to the PCM 3.20 installer during the installation. 5

6 PCM/PCM Plus 3.20 Licensing and Operational Changes from PCM 3.10 and Previous Versions Scenario #2: PCM was registered between 09 November 2009 and 17 November To upgrade to PCM in this scenario, do the following: 1. Go to the mynetworking portal and select My Licenses, and then View available registration IDs, as shown in the next screen image. 6

7 PCM/PCM Plus 3.20 Licensing and Operational Changes from PCM 3.10 and Previous Versions 2. From the Product name field drop-down list, select the J9689A - HP PCM+ v3.2 Platform Upgrade License. 3. Follow the wizard to generate a license key. 4. Provide that license key to the PCM 3.20 installer during the installation. See the PCM Maintenance License Check screen at the end of Scenario #1 on page 5. Scenario #3: PCM 3.10 has been installed but device licenses have not yet been registered. Important: You should not attempt to register a J9174A or J9177A on a PCM v3 platform that you will eventually migrated to PCM 3.20 or a later version. If the J9174A/J9177A registration date is after the 17 November 2010, a J9689A - HP PCM+ v3.2 Platform Upgrade License will not be available and a support call will have to be initiated with HP Networking to resolve this issue. Instead, in this situation, it is recommended that you install PCM Scenario #4: The free version of PCM 3.10 has been installed. Important: As shown in the flow chart on page 4, there is no migration path from PCM 3.00/3.10 to PCM 3.20 for the free version. Uninstalling the previous version of PCM and installing PCM 3.20 is required in order to migrate to the free version of PCM The free version of PCM 3.20 requires a license key that is generated via the mynetworking portal. 1. Go to the mynetworking portal and select My Licenses, and then in the drop-down box under Products without Registration ID, select ProCurve Manager v3. 2. Click the Next button and follow the instructions to generate the license key. 7

8 PCM/PCM Plus 3.20 Licensing and Operational Changes from PCM 3.10 and Previous Versions Additional Migration Notes Upgrading from PCM 2.3 with PMM to PCM 3.20 (PR_47419) Under certain conditions, the PCM client will show a login screen and accept credentials, but the login screen will never close and the PCM client will not start. To avoid this scenario, when the PCM 3.20 installer is run, and if PMM had been installed as part of the PCM 2.3 installation, then you must include the PMM Plug-In during the PCM 3.20 installation, even if you are not actively using PMM. If you did not include the PMM plug-in and experienced this issue, then the solution is to re-run the PCM 3.20 installer and select the PMM Plug-in to be installed. As PCM 3.20 has already been installed, the action of running the installer again will not re-install the software, but will only install the plugin components which were not installed before. Upgrade License versus Maintenance License (PR_59361) While migrating from PCM 2.3, 3.00, or 3.10 to PCM 3.20, you will see an 'Upgrade License' screen where you an enter an upgrade license. Depending on the migration path and/or how long the PCM 3.00/3.10 has been registered, you may need to enter a maintenance license instead of an upgrade license. See the flowchart included in these release notes for details on the types of licenses you will need during migration. Migrating a large number of devices in PCM 2.3 to PCM 3.20 (PR_61958) Please back up PCM 2.3 prior to migrating. When migrating from PCM 2.3 AU13 to PCM 3.20 where PCM 2.3 is managing a large number of devices and/or running on hardware at or below the minimum recommended for PCM 3.20, upgrades to PCM 3.20 may fail with the error message Database system upgrade Failed. Please contact HPN Support if this issue is seen. 8

9 Release Notes and HP Security Policy License Types License Product Number J9173A J9176A J9174A J9175A J9177A J9630A J9631A Description Upgrade from PCM 2.30 for 50 devices and one Agent (includes a 12-month maintenance license) Upgrade from PCM 2.30 for unlimited devices and Agents (includes a 12-month maintenance license) Base software for 50 devices and one Agent (includes a 12-month maintenance license) Incremental license for an additional 100 devices and one Agent. Prerequisite: J9173A or J9174A base software Base software for unlimited devices and Agents (includes a 12-month maintenance license) 12-month maintenance license for 50 devices and one Agent Prerequisite: J9173A or J9174A base software 12-month maintenance license for unlimited devices and Agents. Prerequisite: J9176A or J9177A base software for unlimited devices and agents. 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 communication 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: PCM/PCM Plus 3.20 Notes Installation 60-Day Free Trial The installation download includes the base product PCM (free version). However at install time, the PCM+ trial version is installed, and after 60 days if not licensed, will revert to the PCM free version. Note that the free version supports only 50 devices. After the 60 day free trial, all but 50 devices will be removed from the PDM database. Installing a license prevents this from occurring. 9

10 PCM/PCM Plus 3.20 Notes The PCM Installer also provides the option to install plug-ins PMM 3.10, IDM 3.20, 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 ProCurve Network Management, Installation and Getting Started Guide. (This includes the installation details for PCM, PCM+, PMM, NIM, and IDM. Incorrect links in the PCM Installer Read Me First The Read Me First, which is viewable during the installation process, has a number of incorrect links to HP Networking web pages. These links will be corrected in a subsequent update of PCM. The link to these Release Notes is correct and the latest correct information will be kept here. PC System Requirements and Supported Operating Systems All PCM/PCM Plus software and hardware installation requirements and supported PC operating system environments are listed in the HP ProCurve Network Management Installation and Getting Started Guide. For other details on configuration, see HP ProCurve Manager Network Administrator s Guide, Version 3.20, located on the same web page listed above. Using Firewalls (PR_62722): 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. 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 Devices associated with the PCM agent is not supported. The Remote Agent packages it collected data and sends it to the PCM Server on port If this port is opened on the firewall, communications should happen normally between the PCM Server and Remote Agents. The PCM Local Agent sends traffic on port 51112, but since this agent is almost always on the same computer as the PCM Server, no firewall typically exists between them. 10

11 Mobility Manager 3.10 Notes PCM Plus for HP Network Node Manager: ProCurve Manager integrates with HP Network Node Manager (NNM, version 7.5) and HP Network Node Manager Integrator (NNMi, version 8.1x and version 9.0) to provide a robust solution for managing ProCurve network products in a multi-vendor environment. ProCurve Management is targeted for medium-sized enterprise networks to provide the PCM Plus functionality from the NNM/ NNMi interface, including ProCurve device management, network traffic monitoring, scheduled software updates, VLAN management, and policy management. For more information on PCM integration with NNM and NNMi, see the HP ProCurve Manager 3.20 Network Administrator s Guide, Appendix A, Integrating PCM with NNM or NNMi. Mobility Manager 3.10 Notes Mobility Manager 3.10 requires that PCM Plus 3.20 or later is installed. If the network contains access points that are not configured with the default CLI passwords and SNMP credentials used by PCM, the elements associated with those access points (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 3.20 and PMM 3.10 software supports MSM devices as follows: Support of MSM devices at software version or higher. Limited support of MSM devices at software version 5.3.x and No support of MSM devices at software version 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 Mobility Manager, 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. 11

12 Identity Driven Manager 3.20 Notes PCM 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 Mobility Manager is communicated through the manager controller, and these parameters cannot be different on the member controllers. To establish communication between Mobility Manager and MSM devices running software version 5.4.x (except 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\PNM\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 3.20 Notes Identity Driven Manager 3.20 requires that PCM Plus 3.20 or later is installed. Network Immunity Manager 2.20 Notes Network Immunity Manager 2.20 requires that PCM Plus 3.20 or later is installed. 12

13 What's New What's New PCM/PCM Plus 3.20 New Features The following new and enhanced network management features are supported in PCM 3.20: Improved device monitoring: Detailed network device availability and network event information can be used to document network availability or troubleshoot network downtime. Rich media endpoint aware: Real-time display, location, and inventory reporting of rich media endpoints in your network, such as VoIP phones and IP cameras. HP ONE Services zl Module Management: Sim6plified deployment of network services with the discovery, monitoring, licensing, and configuration of HP ONE Services Modules. Custom Script Wizard: Enables secure, user-defined extensibility to the HP PCM Plus management platform. Added automation capability to database backup. Discovery enhancements: Support for loopback addresses Added Refresh button for topology refresh Added subnet ping sweep discovery Mobility Manager 3.10 New Features The following new and enhanced features are supported in PMM 3.10 ( See references are to the HP ProCurve Mobility Manager 3.10 Network Administrator s Guide. See that guide for more detailed information): PMM 3.10 has improved the presentation of data through a series of tabs, charts and tables, depending on what is selected in the Network Tree. In particular, PMM 3.10 has added performance monitoring of MSM-controlled APs. For example, if an MSM-controlled AP is offline, its status is displayed in the navigation tree, Site View (on the floor plan), dashboard graphs, and event logs. PMM scalability now provides near real-time support for up to 2,500 wireless devices. Wireless devices includes all APs and controllers at version or above. When the highest level of the Network Tree is selected, the Mobility Manager tab displays high-level current and historic information on network devices, clients, and events. See Mobility Manager dashboard in Chapter 2. The Wireless Metrics and Wireless Properties tabs now support controlled APs and client activity. In addition, past performance views of device and client activity is available from the Wireless Metrics tab. See Wireless Metrics tab in Chapter 2. 13

14 What's New When a wireless device or a group containing wireless devices is selected in the Navigation tree, the Radios and WLANs tabs provide detailed radio configuration and information for the selected device. The Wireless Status tab provides status of APs, wireless clients, wireless rates, local mesh, and neighborhood information in near real time. See Wireless Status tab in Chapter 2. The Wireless Address Search tool lets you easily locate the history of a client s connections. You can enter the IP address, MAC address, or User/Device name to locate log files for that client s activities, or use the tool to simply locate other information about an AP or controller. See Wireless Address Search in Chapter 2, and the online help for details. The Wireless Associations button identifies all clients associated with radios in the selected group or device at the selected time. See Wireless Associations in Chapter 2, and the online help for details. The Refresh Wireless Configuration button retrieves the current configuration for the selected device. By default, data is displayed for the previous 24 hours, but the time slider with calendars lets you see data for any period during the past five years. Support for Controller teaming provides scalability, redundancy and failover support. For details on teaming, see the HP ProCurve MSM7xx Controllers Management and Configuration Guide. 14

15 What's New You can specify the display criteria for the Mobility Manager dashboard and Wireless Metrics tab through the Tools > Preferences > Mobility > Charts and Tables option. See MM Dashboard and Wireless Metrics tab Preferences in Chapter 3. To sort data in a table, click in the column header. To select which columns to display, right-click in the header and select from the list. Click-and-drag to reorder columns within a table. Blank spaces in any column indicate the information is unavailable or not supported. For information on filtering table data, see Filtering Data in Chapter 3. For information on setting the display criteria in charts and tables, see Splitting Data in Chapter 3. 15

16 What's New Identity Driven Management 3.20 New Feature ER_ Support for multiple Domain Controller Hosts. When synchronizing users via groups in Active Directory, it is sometimes beneficial to point the IDM Server to specific domain controllers in order to synchronize changed information as fast as possible. A description of this functionality is as follows: 1. IDM will automatically discover the default domain name subscribed by the machine where the IDM Server is started. 2. The IDM administrator will be able to see the default Domain and add multiple domain controller list in space separated format. 3. The IDM administrator will be able to view the current detailed status of an ongoing directory synchronization operation by IDM with the Active Directory Domain Controller. The detailed status view can be seen by customers by pressing the Details button, being made available in the User Directory Settings panel under IDM in the Preferences dialog. This functionality can be accessed as follows: 1. Go to Preferences > Identity Management > User Directory Settings. 2. (Optional) Enter Domain Controller Host names or IP addresses. If you do not specify anything in the text area, it will connect to the default domain controller host that is reachable. 3. Add the required user groups to be synchronized from the Domain Controller by pressing the Add or Remove Groups. button. 16

17 What's New In the Add or Remove Groups dialog window, enter the names of the groups in the Groups to Synchronize field. You can see a message at the bottom of the dialog about the host that is connected for the selection of users groups to be synchronized. Press OK to select the groups to synchronize. 17

18 What's New 4. Now specify the Domain Controller host names or IP addresses separated by a space character. When the users are being synchronized using Active Directory Synchronization, pressing the Details button pops up a dialog showing details of the latest event that was received by the server. 18

19 What's New Network Immunity Manager New Features and Enhancements Several significant features/enhancements were added for managing the TMS zl module: Configuring and Managing VPN (New Feature) Configuring Global IPSec Settings Synchronize TMS Properties Managing IKE Policies Managing IPSec Proposal Managing IPSec Policies Managing GRE tunnel settings Managing Connections Refreshing VPN Connections Viewing Active IKE SA's Viewing Active IPSec VPN tunnels Viewing L2TP users Viewing Active IP Pool Sessions Configure an IPSec Client-to-Site VPN Configure an IPSec Site-to-Site VPN Configure an L2TP over IPSec VPN Configure L2TP User Authentication Manage Certificates Configuring High Availability (HA) Clusters (Enhancement) Creating an HA Cluster Adding a module/ device to an HA Cluster Modifying a HA Cluster Removing a HA Cluster Removing a module/device from an HA Cluster Synchronizing HA Configuration Managing and Configuring Firewall (Enhancements and new feature) Manage RADIUS Settings (New Feature) Manage L2TP Users (New Feature) Renaming Firewall Zones (Enhancement) Support for 256 VLANS (Enhancement) TCP MSS Configuration (Enhancement) 19

20 Additional Information Additional Information See the following Web sites for additional information: PCM Overview and Features: FAQs: Supported Devices: c pdf Download trial version: MM Information: NIM information: IDM Information: 20

21 Fixed Issues Fixed Issues PCM/PCM The following issues were resolved in ProCurve Manager 3.20: PR_55525 In Policy Manager > Policies, if you specify a partial OID value such as to match both the link up trap (.4) and the link down trap (.3), the policy will not trigger. The full trap OID must be specified before the policy will trigger (for example, for a link up). PR_55196 Policy Manager > Alerts for SNMP traps do not currently execute. PR_54843 The Port Settings: Port Enable/Disable action could hang, causing Policy Manager to not show the correct policy execution status on that policy as well as others. PR_53838 Policy Action > Send Mail does not allow multiple addresses in the To field. PR_52160 Multiple Test Communication Parameters executions against a 4000M (or other M series switches) will frequently give incorrect results when the delay between the 4000M and the PCM agent is large and no credentials are configured on the device. PR_45639 Test Communication Parameter operation is hung. PR_55354 Trap with OID is sent from an AP430 during a software upgrade is shown as an unknown trap in PCM. PR_52644 VLAN ID field is not sorted correctly in two places: In the Navigation Tree and in the associated VLAN List table. PR_61122 When a User Defined Device is created with a space in the SYSOID field and later edited, the PCM client fails to launch. PR_44334 The Deploy Wizard shows failure if the device is managed by a J9496A HP ProCurve Manager v3 Agent ONE Services zl Module and the device is not running K version of switch software. PR_55103 MyProCurve portal logins fail when PCM uses an HTTP proxy server but not a SOCKS server. PR_56115 The PCM Event Log displays Unknown V1 trap: OID= which is related to a switch software problem PR_55445: Switch sending Trap with invalid OID when 'LLDP top-change-notify' is enabled. Please refer to the switch software release notes to determine when this issue was addressed in the switch software. PR_53936 / PR_56221 PCM does not give the option to configure Virus Throttling for CX4, SFP Ports, or Mesh ports. 21

22 Fixed Issues PR_54339 PCM fails to modify GVRP port properties for the 5400, 3500, and 8200 switch models. 1. Discover an affected device in PCM. 2. Enable GVRP (GARP VLAN Registration Protocol) on the device. 3. Create dynamic VLANs on the device. 4. Rediscover the device in PCM. 5. Go to Port List > Port Assignment table. 6. In the Port assignment Table, select any port and Click on Modify GVRP port-properties and an error dialog is displayed. PR_54259 The wrong VLAN-Name is shown in the Modify VLAN Wizard when multiple VLANs are selected to be modified. 1. Right click a device in the PCM navigation tree. 2. Select VLAN Manager > Modify VLAN. 3. In the Select VLAN(s) to Modify page, select multiple VLANs to modify and click on Next. 4. In the first page, the information is shown properly for the first selected VLAN, but the next page displays the VLAN name of the first VLAN selected rather than the current VLAN being modified. PR_61952 When a device assigned a given IP Address is changed or replaced (for example, because of a hardware failure) and a new device is installed, and the same IP address is given to it, PCM will detect this and query the device with the default credentials rather than the credentials that were used by the original device at that IP address. PR_56515 Test Communication Parameters performed with correct credentials on an SNMPv3 device fails with an Authorization Failure message. 1. Discover a device with SNMPv3 enabled on it. 2. Make sure the parameters are correctly set in PCM when discovering the device. 3. After the device is successfully and completely discovered, execute Test Communication Parameters for the device. 4. The test fails with an Authorization Failure message, and the status of the device goes to unreachable. 22

23 Fixed Issues PR_55343 Device credentials are not updated on the PCM agent when incorrect SNMP credentials are changed to correct ones. 1. Discover some devices in NNM and make sure those devices are discovered in PCM after NNM integration is done. 2. Make sure the SNMP parameters test pass for all the devices mined. 3. Now change the SNMP parameters for all the devices such that Test Communication Parameters does not pass for any of the devices. 4. Wait for the status of the devices to go unreachable. 5. Set the correct SNMP communication parameters for devices in PCM so that Test Communication Parameters will pass. 6. In the PCM navigation tree, the devices never change their status to green. PR_53882 PCM does not update information about a device if the device is replaced, but re-uses same IP Address. The device must be deleted and manually discovered for the new information about the device to be collected. PR_60241 PCM discovery does not update the device serial number on rediscovery if it has changed. PR_17592 In the PCM Custom Group > Folder List, a right click on a subfolder will show device related options rather than subfolder related options. PR_57509 An additional custom group is created with the same name as that of the existed group while adding devices to the existing group. 1. Create a new group under the Custom Groups folder by right clicking on it. 2. Try to add a device to the newly created group by right clicking on the device and click Add to group option. 3. Click on the Select a Custom Group button in the Add Devices to a Group window and select an already created custom group. 4. Now, again click on the Select a Custom Group button in the Add Devices to a Group window and two groups appears with the same name in the Custom Group Selection window. PR_54185 Sometimes an unexpected Policy Already Enabled error message is displayed while creating new policy. PR_52540 Policy Progress in policy history is not being updated properly. As an example: 1. Run a policy to update software on devices. 2. Software was updated properly, but the policy progress bar in the policy history is still showing 0%. 23

24 Fixed Issues PR_59208 Event details generated for an RMON threshold violation does not provide the violating port information. PR_56602 Event Browser does not sort the Source (IP) Column correctly. Policy Manager (PR_50544) The 'Policy Manager: Send Mail' action will not accept valid address for if <domain> is more than three characters. Find Node (PR_60626) Using Find Node, an error message indicating Invalid IP address or MAC Address for device would be displayed for a mistyped DNS name or a name that was not in DNS. Find Node (PR_61117) The Find Node feature is not working for MSM Access Points and MSM Controllers. PMM 3.10 The fixed issues for PMM 3.10 have been described in previous Auto Update Release Notes for PMM. IDM 3.20 The following issues were resolved in Identity Driven Manager 3.20: PR_58246 IDM Import Wizard does not work. In the IDM Import Wizard, if you select the Active Directory option and continue, it eventually gives the following error: After providing the fix, the wizard runs successfully and imports users from the Active Directory server into the IDM Server. PR_57828 IDM and PMM Integration is required for WLAN access policy rules. PR_57623 The Linux agent is missing the DMConfig.prp file. NIM 2.20 The fixed issues for NIM 2.20 have been described in previous Auto Update Release Notes for PMM. 24

25 PCM/PCM The following are know issues for PCM/PCM+ 3.20: In the Read Me First, which is displayed during the PCM 3.20 installation, there are incorrect links to HP Networking web pages. The link to these Release Notes is correct. The other links will be corrected in subsequent updates to PCM. PR_6750 The configuration of Guaranteed Minimum Bandwidth (GMB) on ports using Port Settings Policy needs validation to check that the sum of GMB queue priorities should be 100. PR_6769 The tooltip seen when mousing over an unsecured port in the Auth Status column of the Port Access subtab, which is in turn on the Port List tab for a device, is Insecured. This term is meant to convey Unsecured or Unauthorized. PR_6964 Context-sensitive help works with IE 6 and Mozilla Firefox 1.5, but not IE 7. PR_15890 Trunk ports are not showing in the Port List (Under Device Access > Status Tab) after adding the device to a custom group. The trunk port is listed under the Port List tab only if the option Only add inter-switch ports is selected while adding the device to a Custom group. PR_17046 The time shown in the Dashboard for Top Traffic Overview is one minute ahead of the system time on the PCM Server. PR_18054 Pressing Halt when unblocking multiple hosts that were blocked as part of Virus Throttling does not halt the action. PR_18059 If the port speed of a given switch port is changed and then the switch is rediscovered through PCM, the old port speed is displayed in the Port Status tab of PCM. PR_18617 Show Violation Ports is not checked in when opened through a cloned window in the network map. 1. Open the Network map. 2. Check the Show Violation Ports button under Link View > Traffic. 3. Click on the Show this tab in a new window button to clone the window. 4. Show Violation Ports is unchecked in the new window. PR_42394 Dashboard Status for any device displays Good, Agent Unreachable in certain cases when the PCM Server service and PCM agent services are started at different times. 25

26 PR_43232 The speed of a tunnel port of a 7000 router is shown incorrectly as 79 Gb in the network map. PR_62612 PCM Server occasionally uses an old certificate for Agent-related connections. PR_62134 PCM fails to configure the IP address in VLANs for model 2520 switches. PR_44069 The Premium Licensing wizard needs multiple clicks to the Next button to go to the License confirmation page. 1. Discover any devices that have a premium license capability. 2. Launch the Config Manager > License Software wizard. Click on the Next button from the welcome page. 3. Enter the Registration ID and click on the Next button. You are not taken to the next page. The Next button in the Enter license info page will be disabled. 4. Clicking on the Back button and then clicking on the Next button will allow you to go the License Confirmation page. PR_44587 Test Communication Parameters is failing for Manager parameters also when Operator parameters are incorrect. 1. Setup the device with Operator and Manager Password. 2. Configure wrong credentials (not blank) for Operator and correct credentials for Manager in the Communication Parameter in PCM window. 3. Run Test Communication Parameters in the PCM. First time it will show Success for Manager and Failure for Operator. This is expected behavior. 4. Run Test Communication Parameters for second time and every time after that. It will indicate Failure for both the Manager and Operator. PR_45029 Intermittently, manually discovering a device using a DNS name may return Invalid IP Address. PR_47302 Unable to perform License Registration through PCM if it is installed along with all plug-ins on Windows bit. 1. Install PCM on Windows bit and select all the plug-ins for installation. 2. Launch PCM Client. 3. Click on the Preferences. 4. Select the Registration & Licensing option to enter MyProCurve credentials to register the PCM license. 26

27 5. The Device Registration option itself is not available. 6. Click on the Register button, but no action is performed. Workaround: Stop and restart all PCM Services. Release Notes: ProCurve Management Software PR_47366 Data mining does get devices from NNM when disabled and enabled within a short period of time. 1. Enable NNM integration, enter in PCM server ip address in the IP address field and enter in all the other required parameters. 2. Check for the status of integration on the dashboard. 3. Now go to Preferences > Integrations and change the IP address field pointing to the correct NNM server IP address. 4. Go to Agent Manager > Discovery > Managed Subnets and add all subnets to the managed subnets of that agent. 5. Click the database mining icon on the dashboard and check for the status of data mining and SNMP mining. Observed results: 1. When the PCM server IP address is entered in the IP address field for the first time, the connection status is displayed as not connected. 2. When the NNM server IP address is entered in the IP address field, the connection status is displayed as Connected with the last connected time. 3. Devices are not mined from NNM. 4. When the NNM is disabled and enabled again, data mining works as expected. PR_48124 LLDP Port VLAN ID is incorrectly advertised as 0 for Trunked ports. This will appear to you as a PCM problem, although the root cause is with switch software and will cause this event log message in the switch: lldp: PVID mismatch on port <n>. Switch software release notes will indicate when a new version has addressed this option. PR_50242 Event Totals by Severity graph is not seen if the events are viewed for one particular time period and grouping interval. 1. PCM receives some events. 2. Select any one of the devices and select the Reports > Network Activity > Policy Activity > Event Totals by Severity report. 3. Select Time Period > From and To values so the period is one hour. 4. Select the Group By > Interval = 1 hrs and click on the Finish button. 5. PCM will launch the Report. Observe there is no chart seen though there are some events within the selected one hour. 27

28 If the interval filter is changed to minutes instead of hours, then the graph will be seen. PR_50383 PCM is restoring the sub tabs selections for Port List tab, even after the PCM Client is re-launched. 1. Select a device in PCM navigation tree and click on the Port List tab. By default, the Port Status sub tab will be selected. 2. Select a different sub tab, for example Port-Access or Port Assignment. 3. Close the PCM client. 4. Re-launch PCM Client, and access the Port List tab of the same device selected in step 2. Expected results: Once the PCM client is re-launched, previous selections should not be retained. PR_50752 You cannot enable or disable the SNMP protocols on a Threat Management Services module from PCM. PR_50798 For some Nortel VoIP phone models, PCM does not report LLDP MED data. This will appear to you as a PCM problem, although the root cause is a problem with switch software. Switch software release notes will indicate when a new version has addressed this option. PR_52064 Client needs to be restarted to remove the non loopback IP address from the device list. 1. Configure loopback IP address on one or more devices and make sure the IP addresses are reachable from the PCM server. 2. Key in the seed ip address and make sure all the devices, even the devices configured with loopback IP address are discovered. 3. Now discover the devices using the loopback IP address manually. 4. Check the client for the IP addresses. Observed result: Once the devices are discovered using the loopback IP address, the original IP addresses are not removed from the client unless the client is restarted. Expected result: The client should be updated automatically and should not have to be restarted to reflect the changes. PR_52845 Formatting of IP addresses, DNS names, and other values may take up two lines in Reports and leads to poor readability. PR_52902 For the report wizard, the discovery wizard, the import wizard, typing the Enter or the Esc key doesn't execute any action as they are not linked to any button. 28

29 PR_53980 Changing credentials on a 7102dl device does not show correctly in the Device Access Control > Credential change history report. PR_54322 ONE Management Discovery shows the SNMPv3 Authentication protocol as SHA even when it is MD5. PR_54725 The same Agent is seen multiple times in the Authorized Managers list after performing move subnets from a local agent to a remote agent because this action does not check for duplicates in the Authorized Managers list. PR_54729 A user with Reports Only permission and a few devices assigned to them can still run a report for all the devices in the database. 1. Create a User profile with Reports permission. 2. Add only few devices to this user profile. 3. Create a user using this profile and login to the PCM server as that user. 4. As expected only the devices added in step 2 will be seen. 5. Run any report by selecting All Devices. It will show the reports for all the discovered devices in PCM. The user has access to only few devices and should only be able to see the report for these selected devices. PR_54781 In Policy Manager > Actions > Communication Parameters you are allowed to change the parameters for both SNMP v2 and v3 even though only one version is selected. PR_54811 Manually traversing the device list with the arrow keys when IDM is installed can result in the PCM Client locking up. 1. Allow PCM to discovery a number of devices. 2. Select Devices in navigation tree, then the Device List tab. 3. Using the arrow keys, navigate up and down in the list of devices shown in the Devices List tab. 4. After doing this several times, the PCM client becomes very slow and eventually locks up. PR_54857 When adding a trap receiver through Policy Manager or Move Subnets, MSM controllers report a Failure to find the chassis IP and the trap receiver is not added. PR_55447 The Event Totals by Severity Report x-axis scale is not completely readable. 29

30 PR_55459 The statistics (Smpl, Stat, and Tot) values may not appear in the Top Traffic Overview window on the Network Management Home > Dashboard. Smpl = Sampled = number of ports providing statistics in the last minute Stat= number of ports providing sample data in last minute Tot = Total = total ports in the query. PR_55752 Export Configuration action may fail to create the export directory. 1. Enable the Policy Execution from the Tools > Preferences menu item. 2. Discover devices in PCM. 3. Perform a scan on the devices. 4. Create the Export Policy by adding the Scanned devices as target. 5. Click on the Enforce button. The policy execution may fail to create the Export directory. PR_55906 Installing licenses on a device that already has licenses gives a wrong error message, indicating portal has malformed XML. PCM should prevent a user from installing another license on a device that already has that license. PR_55907 Invalid special characters seen in the License Agreement while installing premium licenses on devices. PR_56231 PCM puts ESX Servers into the McAfee security platform folder in the PCM navigation tree. PR_56275 PCM fails to do software updates for AP Discover one AP 420 device. 2. Now select the device in the PCM navigation tree, and launch the Software Update wizard for the device. 3. In Setup update time and reboot option page of the Software Update wizard, click the On Next button, which does not perform any action. PR_56473 SNMP Trap from a WESM-XL is not decoded in PCM event browser and it displays unknown trap. 30

31 PR_56625 Under Device Access, the HTTPS protocol should be grayed out for 1700 and 1800 devices since they do not support HTTPS. 1. Select a 1700/1800 device from the PCM navigation tree. 2. Select Device Access > Communication Parameters in PCM. 3. Select Web-agent settings. 4. Click Next. 5. Unclick Use PCM Defaults? 6. The HTTPS button and its Port selection field is enabled though not supported on the device. PR_56717 Re-discovery or manual discovery of a device present in the Unknown devices folder sometimes does not work. PR_56782 Enable device discovery is enabled when NNM integration is enabled, and it should not be. 1. Navigate to Preferences > Integrations > NNMi Communication Settings. 2. Enter the parameters and apply the settings. 3. Check Enable Device Discovery in Preferences > Integrations. It should not be enabled when NNMi integration is enabled. The PCM discovery mechanisms should be also be disabled. PR_56786 When all telnet sessions are occupied on a switch and you try and launch an SSH session using key authentication through PCM, it will open the SSH window and say connected, but will not allow you to login to the switch. PR_56963 When NIM is not installed on top of PCM and TMS modules are discovered in PCM, the TMS dashboard is shown with white background instead of a gray background. PR_57241 The Power required Filtering option is not working at the aggregate level view of media endpoints. 1. Discover a switch with 4 LLDP-MED (MITEL 5330 DM, MITEL 5324 IP, CP-7975G, NORTEL) IP phones connected. 2. The PoE Power Required for MITEL is configured for a value of 4.7W. 3. Entering a value of 4.7 in the Power required filtering option at the aggregate level view of media endpoints will not filter the MITEL devices, but entering a value of 47 in will filter the MITEL devices. PR_57247 The reconfigured LLDP-MED device details (for example: VLAN ID, QOS Priority, DSCP Values) for a discovered switch are updated in PCM only after the PCM Client is restarted and are not updated via a rediscovery. 31

32 PR_57249 The Window restore button in View log summary will at times not resize the window and will the window will remain at maximum. PR_57260 Whenever you mouse over on the end of the Last 24 Hours graph, the graph incorrectly shifts its position. PR_57300 In the Archive Log Files dialog, there is delayed feedback after clicking OK and during that time, the Cancel button is grayed out. PR_57453 Unauthorized user status is showing as UNKNOWN in the LLDP-MED and EndHost Map. 1. Configure a port on the switch for 802.1X. 2. Connect an unauthorized user to that port. 3. Connect a few LLDP-MED IP phones to the same switch. 4. Discover the switch using Auto Discovery. 5. In the LLDP-MED and End Host Map the status of the unauthorized user is shown as UNKNOWN. PR_57705 PCM fails to add an SNMPv3 user on a ProCurve Wireless Services module and gives the incorrect message that the SNMPv3 user is added successfully. 1. Discover a ProCurve wireless service Module. 2. Select Device Access > Communication Parameters In Device for the device. 3. On the Configure SNMP settings window, select both the SNMPv2 and SNMPv3 options. 32

33 4. Go to the V3 Credentials Configuration window. 5. Add one SNMPv3 user on the device. 6. PCM gives the message SNMP configuration successful, but the user is unable to discover the device with the newly created SNMPv3 user profile. PR_57909 Port classification is not displayed for mesh ports but the information for the device connected to the mesh ports is available via LLDP/CDP. PR_58023 In Agent Manager, SNMPv3 Auth and Priv passwords do not get cleared on deletion. 1. Open Agent Manager > Device Access > SNMP settings. 2. Configure SNMPv3 credentials. 3. Apply the settings. 4. Clear the SNMPv3 credentials. 5. Apply the settings. 6. Reopen the Agent Manager > Device Access > SNMP settings. 7. All the credentials except for the username and auth protocol still exists (grayed out) and on providing SNMPv3 username and auth protocol, previously deleted credentials will reappear. PR_58066 PCM is unable to perform Software Updates on ProCurve 6120 Blade Switches. PR_58165 Saving PCM Reports in a CSV format includes multiple entries for the header information in the CSV file (one per page of data). PR_58223 When sorting the values in the Date column (clicking the column header) in Configuration History, a pure string sort is done rather than a sort by the actual date. PR_58522 In the Network Map, when Discovery Protocol is selected for annotation, no 'Discovery Protocol' is shown for Access Points such as the AP420 or MSM devices. PR_58559 In rare cases, the PCM navigation tree may not be correctly ordered although all information is present. The workaround is to restart the PCM Client. PR_59007 The PCM Device Inventory report does not contain information for the ONE zl modules that are managed from PCM. PR_59163 When a PCM Agent is down, the agent status is unclear in some areas of PCM and may lead to misleading error messages. As a workaround, always check Agent Manager to determine the status of the agents. 33

34 PR_59170 PCM allows you to attempt CLI Wizard, Script Wizard, and Script Manager operations against unsupported devices, but then does not provide an 'unsupported' error message. PR_59361 While migrating from PCM 2.3/3.00/3.10 to PCM 3.20, you will see an 'Upgrade License' screen where you can enter an 'upgrade' license. Depending on the migration path and/or how long the PCM 3.00/3.10 has been registered, you may need to enter a maintenance license instead of an upgrade license. PR_59651 In the PCM Client Dashboard, for the Last 24hrs, the Threshold Bar and the count of all severities may not be seen. Though the screen resolution is valid, the threshold lines won't be seen. As a workaround, make some space by scrolling left the right panel. 34

35 PR_59658 The Script wizard error message box should be formatted to fit into the dialog box. 1. Create a new function and add a script by not selecting the Default Script check box. 2. In the next step select large number of device families on which the script applies. 3. Now add another script with the same function selected, and select the device families which were selected for the first script. This will result in the error message dialog which is not formatted correctly. PR_59678 If you have a device with more than six VLANS, when you access the Port Assignment Table, it is necessary to use the scroll bar on the bottom of the Port Assignment Table to scroll to the right to see all the VLANS and find they one for which you want to change the assignment. However, as you scroll to the left in the Port Assignment Table, you lose the columns that show the Port Index and Port Name. This loss makes it difficult to know which row in the table you need to modify in order to change the values for the desired port. PR_59723 The Live View tab is not shown for 3Com devices in the Device Dashboard though 3Com devices are able to show such a view via their Web UI. PR_59907 Invalid characters in the hostname, per RFC 1033, can cause CLI Test communication parameter fails for non-procurve devices with SSH capability. PR_59971 H3C S7506E image shown in PCM as an empty chassis. PR_60046 Whenever there is any event generated by Automatic Update, the source field shows an unexpected number that is not needed. PR_60047 You are not prompted to enter a password when Grant External Database Access is checked for an existing user in the Manage Users window. As a result, a user can be created without password and external database access can be granted to that user. PR_60089 When an interactive script is defined in the Script Wizard, where the input is given to the device through the script, then the device executes the command, and then returns the output in PCM, the input and output are not properly aligned/displayed in the output. PR_60099 The Ethernet ports of the 3Com PWR are not shown in Modify VLAN wizard and in VLAN Map->Port properties window. 35

36 PR_60166 License import fails if the license is transferred from the MyProCurve Portal. 1. Install PCM 3.2 on one more server. 2. Add a new license from the My ProCurve portal on server1. 3. Deactivate the license added in the above step and make a note of the uninstall key. 4. Login to the MyProCurve portal and look for the licenses added in the step Select the license and click on the Transfer license. 6. Provide the uninstall key and new server Install-ID. 7. Complete the transfer. 8. The portal will generate a file and it to you. 9. Import this file and it fails with an error. Workaround: Use the license key in the text of the generated by the portal and do not use License Bundle File when the transfer of the license is done. PR_60269 WirelessStation, WirelessStationHistory and RfDetectionHistory are unused tables that were previously used by IDM and PMM, but are obsolete in PCM

37 PR_60301 Unable to add or edit image for a User Definable Device when editing the properties for that device via the CIP utility. PR_60384 In the Configure Thresholds window for ports, the progress bar is not showing the last updated time when multiple ports are selected. PR_60809 Refreshing a Network Map with Port Name annotations will add a forward slash (/) to the port name label. PR_61040 When uninstalling PCM, any installed plug-in should automatically be uninstalled as well. PR_61041 Adding multiple User Defined Devices to a remote agent and scanning for these devices via Agent Manager will not discover the devices. As a workaround, the PCM client or the PCM server should be restarted. 37

38 PR_61047 When the shortcut link is installed other than the default Program files directory, the link Uninstall ProCurve Agent is not removed as part of the uninstall process. PR_61208 PCM fails to update the software version and the hardware serial number for WESM zl modules running version WT PR_61522 If a Loopback IP address is configured on a device, it is shown as Managed Subnet in the PCM tree. PR_61524 MSM devices have two Ports: the LAN port and the Internet Port. Either of these ports can be configured with the MSM device IP Address. The MAC address of the system however points to the Internet Port MAC address. This is the same MAC address that PCM uses to associate the neighbors during the Find Node process. Hence, while viewing the MSM controller / MSM Access point configured on its LAN port, you would notice that the Find Node operation would not be able to determine its neighbors. PR_61538 If the MyProCurve credentials entered in the Preferences > Device registration window are changed, PCM still uses the previous entered credentials while authenticating to the MyProCurve portal. PR_61590 The Create Config Template flow is not working as expected when the Back button is used on the Review IP Pools page. 1. Create two IP Pool configuration templates. 2. Create a new Config template and choose one of the pools. 3. Click the Next button. In Review IP Pools page, click Back button. 4. Do some changes in template and click Next button. 5. Try to choose the other pool from the drop down in the Review IP Pools page and click the Next button. 6. The newly selected pool is not updated. Moreover, the links for create/show IP Pools list are also not working. PR_61596 In the Script Wizard, a Script execution complete. message is shown even when the script is aborted because of an error. The errors are displayed in the Monitor The Progress dialog. PR_61600 In the Script wizard, the View Error Log dialog shows nothing and does not display all the errors that may be encountered during execution. The errors are displayed in the Monitor The Progress dialog. PR_61640 The Script Wizard help text does not indicate how to create a new function. 38

39 PR_61958 When migrating from PCM 2.3 AU13 to PCM 3.20, where PCM 2.3 is managing a large number of devices and/or running on hardware at or below the minimum recommended for PCM 3.20, upgrades to PCM 3.20 may fail with the error message Database system upgrade Failed. Please contact HPN Support if this issue is seen. PR_62024 The Add New Script in the Script Manager is not pointing to the proper online help page. 1. Click on the Script Manager tool icon from the Global tool bar. 2. Click on the Add New Script button. 3. Click on the Next button from the Welcome page. 4. There is an option to select either the existing Function name or to create a new function. 5. Click on the Help button available at the right top corner. It points to the Script Wizard help instead of the Function Name help. PR_62028 The online help contents for Edit Script Function name within the Script Manager are incorrect. PR_62122 A confusing message appears during ONE zl management. The information in the bottom status pane of a new ONE zl module reports that No records exists for this ONE zl Module, which actually means that no PCM license install, application install, or application/license uninstalls had been done via PCM as opposed to the ONE zl module not being available to communicate with PCM. PR_62124 ONE zl Management license activation status successful does not match module boot status. When the switch CLI command show services <slot-id> shows the module move from booted to initializing state, the PCM status shows the module as successfully activated. The module actually has not finished booting. PR_62136 The Help file for 'Modify VLAN 'requires more information about Managed Subnets. PR_62140 When using the 'Modify VLAN' functionality in PCM, PCM may fail to discover manual IP configuration information on some devices. PR_62282 Agent file manager online help should include 'Check for File Changes' details. 1. Click on the Agent Manager > Agent File Manager. 2. There is a new button Check for File Changes introduced in PCM 3.20 release. 3. Click on the Help button from this window. The help text does not describe the Check for File Changes button. The help text should be as follows: 39

40 The Agent File Manager is used to manually download files to Agents. Primarily, this tool is used to download CIP files (trap decoders and device OID files). These Agent files are individual files, created either directly or via some wizard, that need to be deployed to Agents. Packages deployed via the standard download protocol consist of entire archive. zip files and are usually put on the PCM Server when PCM is installed or an auto update is received. The Agent Manager keeps track of every Agent ad hoc file that needs to be downloaded to Agents. Each time an Agent connects to the PCM Server, the Agent receives this list of files and verifies that it has the same version of all files on the list. If the Agent doesn't have the file or has a different version, the file is automatically downloaded to the Agent during the initial download protocol step. The button Check for File Changes also allows this functionality to occur without having to restart the agent. (is this true?) PR_62355 You are unable to edit User Defined Devices because a popup window comes up asking to Enter the product of the device, but no entry is allowed. PR_62722 The PCM administration guide does not elaborate on firewall support. A firewall between (a) the PCM client and the PCM server and (b) between the PCM Server and a PCM Agent must be configured to allow communication between these endpoints. Note that a firewall between the PCM Agent and the Devices associated with the PCM agent is not supported. For more information, see Using Firewalls (PR_62722): on page 10. PR_62961 The help contents in the Group Script action are incorrect in regards to the file path. The content reads: When a script is invoked by a policy, the output file is created in the PNM/Server directory, unlike output files created by scripts invoked from the Script Wizard, which reside in the PNM/Client directory. Therefore, to use one location for all script output files we recommend that you always include the complete path name when specifying the script output file location. You cannot provide the complete path for the file storage. The file name option does not allow for the file path. PR_63017 PCM does not automatically check HPN FTP site for the current procurve_firmware.prp file, which details the latest software releases. In order to get the latest file from the HPN FTP site, press the Download Now button. 40

41 Note: The following PCM PRs have already been addressed in PCM 3.10 AU4 and will be re-addressed in PCM 3.2 AU1, which will be released later. PR_62344 PCM fails to decode some SYSLOG messages for H3C wireless devices. 1. Enable syslog on H3C wireless devices. 2. In the syslog tab of PCM, an example log is as follows: Warn: Replaced non-printable characters with # - Sep 15 12:51: H3C WX3008 %%10HWCM/4/TRAP(t): # configure changed: # EventIndex=11,CommandSource=2,ConfigSource=3,ConfigDestination=2 PR_62352 Invalid characters in the hostname, per RFC 1033, can cause CLI Test communication parameter fails for non-procurve devices with SSH capability. PR_62353 SNMPv3 user password is not retained for non-management users during configuration. 1. In the Device Manager >Communication Parameters window, select Device > Create an SNMPv3 User and create a new SNMPv3 user with group as manager and provide Auth and Priv passwords. 2. Do not select this SNMPv3 user as the management user. 3. Finish the configuration of this new user. 4. Open the Device Manager > Communication Parameters window again. 5. Click on Modify SNMPv3 user and notice that both Auth and Priv password fields are blank PR_62617 Logical interface appears in the Port List tab on deploying a Config Template. 1. Discover an H3C controller. 2. Create a Config Template for the device using Config Manager. 3. Modify some of the configuration in the template while creating it. 4. Deploy this template on the device. 5. On successful deployment, notice that the logical interface (the VLAN interface) appears on the Port List > Port Access, Port Assignment, and Port Status tabs windows. 41

42 6. On rediscovery of the device, the logical interface is removed however (a) the untagged information of the port is lost and (b) the Port Status page is blank and takes more than a minute to get updated. PR_62757 A length limitation in Custom Groups only allows for approximately 270 characters in the tree for custom groups, which limits the group name and any subgroups underneath it. If a group name is restricted to a length of about 30, then about 8 sub groups will be allowed. PR_63611 If online help is requested for the Monitor Progress window in the Script Wizard, the correct Help page is not displayed. PMM 3.10 The following are known issues for PMM 3.10: PR_57208 Controlled APs are not added to the Device List tab view for Custom Groups. PR_57853 Confidence level for Stations and Neighbors is always displayed as Low. PR_59527 Member controllers are not counted in the Controllers row of the Wireless Monitor Table. PR_60259 The Audit Logs function is not working. PR_60558 For non-msm HP Wireless products, 0 (zero) is always displayed as the value in the Avg. SNR (db) and Avg.Noise (dbm) columns in the Wireless Association dialog. PR_60559 For non-msm HP Wireless products, 0 (zero) is always displayed as the value in the Avg. Rate (Mbps) columns in the Wireless Association dialog. PR_61765 Multicast discovery packets continue to be sent (in error) after Auto-Discovery is disabled. PR_62177 Unsupported channels can be configured for an RP via the Radios tab. PR_62672 The Wireless Monitor table never decreases the number of RF neighbors, even those that have been removed. 42

43 PR_62946 The Wireless Properties tab reports no clients even if the AP has associated clients. PR_63243 Scalability -- The wireless status of the APs takes an excessive amount of time to update. PR_63513 The Site Access Points and Neighbors report is displaying all the neighbors -- even the trusted ones. PR_63580 The Site Planner places clients with the same signal on top of each other. PR_63588 If you click on the icon Show this tab in a new window, the new window appears with a refresh needed. If you then click on the Refresh button, the new window seems to disappear, but it is actually just hidden behind the main PMM screen. PR_63627 Scheduled reports are always generated for the same period of time. PR_63847 The Wireless Client Connection History report is displaying the Avg. Rate instead of the Avg. Throughput. PR_63929 MSM 5.3.x and devices: The Serial Number is displayed instead of System Name in several PMM areas. PR_64044 Client - After discovering a Team of controllers, the PCM Client experiences a hang and needs to be restarted. IDM 3.20 The following are known issues for IDM 3.20: PR _57709 In certain circumstances with Active Directory Synchronization, the IDM server loses its connection to a Domain Controller and does not reconnect. PR_62874 IDM 3.2- fails to override the Untagged VLAN attribute on the switch. 1. Configure the switch to perform Machine-Auth or Web-Auth authentication. Apply an access policy group that implements Untagged VLAN Access Attribute, Tagged VNAL, QOS, Ingress and egress rate limits. Authenticate via Machine-Auth or Web-Auth on a supplicant workstation. 2. Log out the authenticated user. 3. Change the Access Policy configuration by un-checking the Untagged VLAN Access Attributes and rest of access attributes inside the Identity Management Configuration window. 4. Log in the authenticated user. 5. Check on switch for port-access authentication or web-based client detail. Expected Results: The authenticated user resets its Untagged VLAN to the Default VLAN 1. Actual Results: The authenticated user get into the last configured Untagged VLAN. 43

44 PR_63083 User Session Status and the last login attempt may not be up to date in the IDM server when checked against NPS server. PR_63220 After moving users from one Access Policy Group (APG) to another APG, the user session status shows entry for both APGs rather than the current APG. PR_63221 User session status info does not show user's IP address even though the IP address is configured on the supplicant PR_63224 In the case of a successful MAC authentication, the 'session-started' event is generated and results in the user session displaying as active. If the switch port or supplicant NIC is subsequently disabled, there is no ending event to receive and the user session is still displayed as active. PR_63265 In an access rule, if Endpoint Integrity is set to PASS or FAIL or INFECTED, the user does not get authenticated. Ideally, if endpoint integrity fails, passes, or is found infected, the user should get authenticated and the respective access profile should get applied. The user is getting authenticated only if the Endpoint integrity is configured as ANY or UNKNOWN. PR_63272 While authenticating a NAP-capable supplicant on an NPS server with NAP policy with default SHV configuration, the End Point integrity status in Session information always shows as Unknown. PR_63276 In a nested Group environment, if the parent group is synchronized, IDM is not listing any users present in the child group. IDM is unable to assign some policies to wireless devices using SAW wizard. IDM is not supported on Windows 2008 R2 release. NIM 2.20 The following are known issues for NIM 2.20: PR_58131 In the Manage L2TP Address and Manage User' wizards, the Synchronize HA Participant option is not enabled for devices that are part of an HA cluster when launched using the right click option. When the same wizard is launched using the tool buttons, the Synchronize HA Participant option is present. PR_50441 The PCM Configuration tab should show hardware and software configuration for the selected TMS zl Module. PR_59898 After deactivating a NIM License, the TMS zl device dashboard should not show Alert rate, Action rate, TMS operating mode, TMS HA cluster operating Scheme, or TMS events. PR_60619 PCM appends the VLAN-ID twice when performing a policy manager action with quarantine VLAN configuration enabled. PCM performs the action on the switch by using VLAN -<id><id> as the VLAN name which is not correct. 44

45 PR_61757 TMS Firewall > Settings > Connection Allocations status remains pending. 1. Left click a TMS zl Module in the PCM navigation tree and click on the tabs TMS - Firewall > Settings > Connections Allocations. 2. Select the Connection Allocation > Reservation Property > Add action, and click Next. 3. From the device list, select one TMS device and click Next. 4. Select Add connection details and click Next. 5. Select Save configuration and click Next. Note that the status remains pending. PR_61697 Status Summary information is blank for the Name Objects Wizard if no service group member is added. PR_61474 The Create Cluster function allows the entry of duplicate HA IP addresses, which results in creating two cluster Masters. PR_61597 NIM only allows two RADIUS servers to be configured on a TMS for the same domain when up to three should be configurable. PR_61287 After successfully deploying an IPsec Remote Access VPN through the wizard, the wizard should show Summary and Close as the buttons in the final screen, but instead shows Summary and Cancel. PR_60290 Device display names for TMS zl Modules are different when compared between the PCM Navigation Tree and the NIM displays. In the View Details screen, the Device IP Address field title is somewhat inaccurate since the display is IPAddr (IPAddr) and the PCM navigation tree shows System Name (IPAddr). PR_60366 (Related to TMS PR_61199) - Care must be taken when changing the Master's HA IP Address /Subnet Mask when compared to the Participant's HA IP Address / Subnet Mask. If the Master HA new IP/mask can reach the Participant's HA original IP/Mask AND the Participant HA original IP/mask can NOT reach the Master's new HA IP/Mask, some period of time will pass before either can be reached over the network. An example: The administrator logs into the management IP address of the Master. This management IP address is synchronized between the Participant and Master. The administrator changes the HA IP address of the master: Original Master IP/mask: /30 gets changed to new IP/mask: /24 Then the administrator reboots the Master. The Participant detects that the Master has disappeared and assumes the Master role and takes on the Management IP address. The administrator logs into the Master in order to change its HA IP address: 45

46 Original Participant IP/mask (now Master): /30 gets changed to new IP/mask: /24 Unfortunately, when the previous master is in the middle of shutting down itself, it issues erroneous Gratuitous ARP requests for the previous management IP address which updates the ARP cache on machines local to that subnet. This update has the affect of directing the management IP communication to a device that cannot handle the communication. Workarounds: 1. Using the CLI, you can issue a ping to a router or unknown local address from the Master which will update the ARP cache 2. Delete the ARP cache entry from the machine or router that is being used to access the TMS 3. Wait for the ARP cache to timeout. PR_57171 If PCM/NIM discovers a TMS zl module operating in routing mode and that TMS zl module is changed to operate in Monitor Mode, NIM will display inconsistencies by showing a monitor mode TMS module with some Routing Mode features. PR_57313 The Manage L2TP Address > Applying Settings window shows TMS devices where no RADIUS Domain(s) were modified. 1. Launch the Manage L2TP Address Wizard. In the Select Devices window, select two TMS zl devices and for example. Click the Next button. 2. In the Manage L2TP Addresses window, modify a RADIUS Domain in the TMS zl device. Click the Next button. 3. The Summary of Changes window will be displayed. It shows the RADIUS Domain in which is modified. Verify that is not shown in this page. Click the Next button. 4. The Applying Settings window is displayed. Here both the devices, and , are displayed under the Device column which shows Completed successfully. Since we did not modify any RADIUS Domain for the TMS zl, it should not be shown. PR_56706 A 'License Out of Compliance' error message dialog is not shown when the NIM license is deactivated for some NIM Features. 46

47 PR_57645 Several fields in NIM are not being displayed correctly: 1. In the TMS - VPN > Certificates > SCEP subtab view, the Filtering by SCEP IP Address/Domain Name, CGI-Path, and Unique CA Identifier fields are not correct. 2. In the TMS - VPN > Certificates > CA Certificates subtab view for the ProCurve TMS zl Device Group Folder and for a single TMS zl Device, the Filtering by Subject Name, Issuer Name, and Expiry Time fields are not correct. PR_58127 In the Manage IPSec wizard and Deploy IPsec Remote-Access VPN wizard IPsec Remote Access Servers page, the IP address range field is not validated properly it will accept IP addresses that end with 0 and 255. PR_56085 The Security Activity tab view for MSM760 devices always shows Alert Count = 0, even though there are NIM Events present. PR_56088 For MSM760 devices, in the Network Map > Device View > Security State, the annotations Security Alerts by Type and Security Alerts by Severity do not show anything. PR_61281 While modifying the existing RADIUS configuration, the modify RADIUS configuration wizard does not acknowledge changing the Strip Domain from user in RADIUS request. 1. From the PCM navigation tree, right click the TMS zl module on which to configure RADIUS. 2. Select TMS-Firewall > Firewall Properties Wizard, and select RADIUS Configuration. 3. While configuring RADIUS, uncheck the Strip Domain from user in RADIUS request. 4. Deploy the configuration on the device. 5. Rerun the Firewall Properties Wizard and select RADIUS Configuration again. 6. Select the same device. 7. Now check the box Strip Domain from user in RADIUS request. 8. Wizard show that any changes have been made. 47

48 PR_62067 For an IPS configuration, you are not able to configure the Custom Inspection Depth at the Device Group level because the dialog box cannot be resized. PR_57390 Filtering is not working properly in the L2TP IP Addresses tab view. When a search is made with respect to IP address, some blank rows are displayed along with the searched data. 48