pvs Release Notes All series

Transcription

1 pvs Release Notes All series

2 CA Nimsoft Monitor Copyright Notice This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time. This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the CA Software ). Such agreement is not modified in any way by the terms of this notice. Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy. The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed. TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE. The manufacturer of this System is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections , , and (c)(1) - (2) and DFARS Section (b)(3), as applicable, or their successors. Copyright 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Legal information on third-party and public domain software used in the Nimsoft Monitor solution is documented in Nimsoft Monitor Third-Party Licenses and Terms of Use (

3 Contact CA Contact CA Support For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At you can access the following resources: Online and telephone contact information for technical assistance and customer services Information about user communities and forums Product and documentation downloads CA Support policies and guidelines Other helpful resources appropriate for your product Providing Feedback About Product Documentation Send comments or questions about CA Technologies Nimsoft product documentation to To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at

4

5 Contents Chapter 1: General Overview 7 Chapter 2: Requirements 9 Prerequisites... 9 Hardware Requirements... 9 Software Requirements Supported Platforms for pvs Chapter 3: Considerations 11 Installation Considerations General Use Considerations Chapter 4: Known Issues and Workarounds 13 pvs Probe is Not Collecting Data Out of Memory Errors Chapter 5: Fixed Defects 15 Fixed Defects Revision History Contents 5

6

7 Chapter 1: General Overview The CA Nimsoft pvs probe monitors the health, utilization, and performance of Citrix provisioning services -based Virtual Desktop Infrastructure (VDI) environments. The pvs probe performs comprehensive monitoring and data collection for various aspects of the Citrix provisioning services VDI, providing Quality of Service (QoS) data and issuing alarms when it detects sub-optimal performance in the XenDesktop-based VDI. The probe automatically discovers virtual desktops, as well as hypervisor virtual machines that power the virtual desktops that may be using VMware vsphere, Xenserver or hyper-v virtualization technologies. The probe communicates with the provisioning services VDI environment via PowerShell commands and extracts key information for real-time monitoring. You can define alarms to be raised and propagated as CA Nimsoft alarms when specified thresholds are breached. Features Auto-discovery of the entire Citrix provisioning services VDI environment Monitoring of clustered Citrix provisioning services VDI environments Hierarchical display of provisioning services components (Farms, Sites, Device Collections, Devices, Disks, Servers, Stores) and license server Auto configuration and monitoring templates Predefined templates with selected QoS monitoring metrics and alarm thresholds Chapter 1: General Overview 7

8

9 Chapter 2: Requirements This section describes the requirements for the pvs probe. This section contains the following topics: Prerequisites (see page 9) Hardware Requirements (see page 9) Software Requirements (see page 10) Supported Platforms for pvs (see page 10) Prerequisites This section describes the prerequisites for this probe: Citrix Provisioning Services 6.1 or later Windows PowerShell command line interface on the Provisioning Services server. The latest version of PowerShell that comes with Windows Server 2008R2 or later is required. For information on configuring PowerShell for use with the pvs probe, see the pvs Guide. Windows Remote Management (WinRM) enabled on the Provisioning Services server. For instructions on enabling WinRM, see the pvs Guide. Hardware Requirements The pvs probe should be installed on a system with the following minimum resources: Memory: 2-4 GB of RAM CPU: 3 GHz dual-core processor, 32-bit or 64-bit Chapter 2: Requirements 9

10 Software Requirements Software Requirements The pvs probe requires the following software environment: Nimsoft Monitor Server or later Nimsoft Robot 5.23 or later Java Virtual Machine 1.6 or later (typically installed with NMS 5.0 and later) Infrastructure Manager 4.02 or later Microsoft.NET Framework 3.5 on the system where the Infrastructure Manager application is running Important!: On 64-bit Linux systems, the Java jre included in the pvs probe package does not install successfully when you deploy the pvs probe on a CA Nimsoft robot. You must manually install the glibc.i686 library or compatible 32-bit libraries on 64-bit Linux systems where you deploy the pvs probe. Supported Platforms for pvs The pvs probe is supported on the same set of operating systems and databases as the Nimsoft Monitor Server solution. Please refer to the: Nimsoft Compatibility Support Matrix for the latest information on supported platforms. Support Matrix for Nimsoft Probes for additional information on the pvs probe. 10 pvs Release Notes

11 Chapter 3: Considerations This section describes important information to know about the pvs probe. This section contains the following topics: Installation Considerations (see page 11) General Use Considerations (see page 11) Installation Considerations Installation follows the standard probe distribution process. General Use Considerations None. Chapter 3: Considerations 11

12

13 Chapter 4: Known Issues and Workarounds This section describes known issues and possible workarounds for this probe. These issues and workarounds apply to the latest version of the probe unless otherwise noted. Deploying the Probe on a 64-bit Linux Machine Important!: On 64-bit Linux systems, the Java jre included in the pvs probe package does not install successfully when you deploy the pvs probe on a CA Nimsoft robot. You must manually install the glibc.i686 library or compatible 32-bit libraries on 64-bit Linux systems where you deploy the pvs probe. Auto-Discovery Time for Large Provisioning Services Implementations In large Citrix Provisioning Services implementations, it may take some time for discovery to occur when you open the pvs probe configuration GUI, especially the first time you open the GUI. You may see a delay while the resource tree is populated in the navigation pane of the GUI. This section contains the following topics: pvs Probe is Not Collecting Data (see page 14) Out of Memory Errors (see page 14) Chapter 4: Known Issues and Workarounds 13

14 pvs Probe is Not Collecting Data pvs Probe is Not Collecting Data Symptom: The probe is not collecting data. Solution 1: The probe may not be able to connect to the PVS environment. There are several issues that can cause this. Solution 2: You may need to allocate more memory for the probe to execute PowerShell commands on the DDC server. We recommend setting this to 1024 MB during initial configuration for the pvs probe. However, in some cases this may need to be increased. Check the pvs.log file for the following message: Process is terminated due to StackOverflowException If you see the StackOverflowException message, on the DDC server added as a resource or alternate resource, open a command prompt and enter the following command : winrm set winrm/config/winrs '@{MaxMemoryPerShellMB="nnnn"}' where nnnn is a number greater than Solution 3: Note: This solution is only valid when Kerberos Authentication is used in the probe. In the pvs log, if you get the Kerberos error, "Clock Skew too great while getting initial ticket," there is a time difference between the PVS server and the probe machine. Verify that both the PVS server and probe machines are in the same time zone, and the time difference between the machines is not more than 5 minutes. Out of Memory Errors Symptom: Out of memory errors. Solution: In environments where the pvs probe is running close to the configuration limits, memory errors may occur. To resolve this, deactivate thepvs probe and then reactivate it. 14 pvs Release Notes

15 Chapter 5: Fixed Defects This section lists fixed defects and the revision history for the probe. This section contains the following topics: Fixed Defects (see page 15) Revision History (see page 15) Fixed Defects None. Revision History Date Description Version July 2014 Added optional Kerberos authentication 1.1 GA June 2014 First general release of the probe 1.0 GA September 2013 First release of the probe 1.00 Beta Chapter 5: Fixed Defects 15