• ControlUp Integration with IGEL

    ControlUp can monitor IGEL endpoints via the “Linux Data Collectors” feature. This exciting combination of ControlUp and IGEL gives administrators the ultimate in visibility to their environment. From the actual user to the backend, you can see it all.

    Prerequisites

    In order to enable complete integration, ControlUp requires some configuration changes to your IGEL endpoints.

    Note: If your ControlUp is unable to connect to the IGEL device, ensure that you can connect with PUTTY using the same account you have configured for ControlUp. When you connect with PUTTY, you should end at a prompt. If you get disconnected immediately, then the same will happen to ControlUp and the integration will be unsuccessful.

    • A ControlUp Monitor Cluster is highly recommended for monitoring your endpoints.
    • IGEL OS 10+ with Enterprise Management Pack.
    • In the Agent Settings > Enable "Allow users to add machines that are running unsupported Linux flavors"
      mceclip0.png

    Installation

    1. Download and extract the ControlUp Integration pack here
    2. On your IGEL UMS server, import the two ControlUp files.
    3. Create a new Profile and assign it to your IGEL endpoints.|
      1. Ensure that your Mount Point field is /custom 
        This is case sensitive.IGEL_Integegration1.png
      2. Ensure that the Initializing Action field is /custom/ControlUp/linuxInstall.sh 
        This is case sensitive.IGEL_Integegration2.png
    4. Add the IGEL endpoints to the ControlUp Console.
      1. Linux Data Collector.
        • Create a new Linux Data Collector.
        • Add the shared credentials.
        • Add the IGEL devices. This can be done via a text file with the DNS resolvable name of all the IGEL devices or via IP address or range (DNS must resolve to these devices).
      2. Devices that have already been added to a Linux Data Collector.
        • If you have added your IGEL endpoints to your ControlUp console you can watch the installation of the integration in ControlUp.

    ControlUp Management Pack for IGEL

    ControlUp has created an initial set of Management Script Actions that can be used on IGEL devices. The scripts that can be run are as follows:

    Machine Actions:

    • Get Machine Details
    • List Assigned Profiles
    • Reboot
    • Send Wake Up
    • Shadow Terminal
    • Update configuration from UMS

    Session Actions:

    • Get Machine Details

    These script actions are natively integrated into the Console when it detects an IGEL operating system. You can activate the script actions in two ways.

    1. Right-click on the name of the IGEL device and choose “Recommended Actions”.
      image3.jpg
    2. If you have “Show Recommendations for Non-Stressed Metrics” enabled in “Display”, then clicking the “image2.png” icon will reveal the Top Recommended Actions menu.
      image1.jpg

    Happy Monitoring!

  • Monitoring Your vSAN via ControlUp

    Summary

    Starting with ControlUp v7.3 you can add your vSAN infrastructure into the organization and monitor it. Each host in a vSAN cluster will be shown and these storage devices combine to create a single vSAN datastore which will be presented in details in the Real-Time Console. 

    ControlUp Console with vSAN datastore:

    2019-05-02_13-45-52.png

    Prerequisites

    • System Requirements (on data collector\default*): 
      1. PowerShell from v5 and above.
      2. PowerCLI 10.1.1.x
      3. .Net framework from version 4.5 and above.
    • vSAN Requirements for the user that you connect with to vCenter:
      1. Performance service should be enabled and turned on inside the vSAN cluster.
      2. The user needs the permission called: "storage.View"
      3. The user must set PowerShell execution policy to allow PowerShell scripts to run. Procedure: run the following command:  Set-ExecutionPolicy RemoteSigned. (usually applied to the machine that is the data collector).

    *The best practice is to have a dedicated data collector instead of the default which is the Console/Monitor. Using a dedicated data collector increases scalability & performance.

    Adding your vSAN to the organization

    To see your vSAN information, simply add a VMware hypervisor. You can use the following article that explains how to Add Hypervisor.  <-

    After connecting to vCenter, ControlUp-Console first checks for each cluster if vSAN datastore is existed and enabled.

    Finding vSAN information in the Console

     

    While focusing on a vSAN cluster, vSAN dedicated presets will be displayed in the relevant views:

    • Folder view- vSAN Cluster.
    • Datastores view - vSAN Performance.
    • Datastore On Host view - vSAN Performance.

    Also, we have dedicated columns for vSAN on those presets, if you wish to see the description of those columns, simply hover on top of the column with your cursor and a tooltip will be shown. You can also see the description via the 'Manage Columns' ribbon.

    More about the integration & troubleshooting issue in vSAN can be seen in the following video:

     

     

     

  • NVIDIA vGPU Information & Specifications

    Users demand a better experience when using graphics-intensive applications. While it might be okay for a timecard form to load slightly slowly, it’s not acceptable for a video to jitter.

    Between the options of throwing more CPU at the problem or taking the vGPU route, the answer is obvious. And that’s is why we’re seeing a rapid adoption of vGPU in VDI environments.

    With ControlUp 7.1 we have introduced vGPU metrics to the ControlUp console. Let’s take a look at what’s possible with these new additions:

    • Static VM level metrics like vGPU Model and architecturenumber of cores and driver version
    • Runtime VM level metrics like available memoryframe buffer size and amount allocatedvideo encoder and encoder usage.
    • Runtime process level metrics show how many vGPU resources each relevant process consumes.

    In Computers view, we offer a detailed preset view of the NVIDIA GPU columns. This is a detailed explanation of the columns:

    GPU Architecture

    GPU's architecture name

    GPU Available Memory NVIDIA GPU available memory in megabytes (MB)

    GPU Frame Buffer Size

    Size of memory assigned to the NVIDIA GPU

    GPU Frame Buffer Usage NVIDIA GPU Frame Buffer usage in percents
    GPU Memory Usage NVIDIA GPU memory usage in percents
    GPU Model GPU name or NVIDIA GRID GPU profile type
    GPU Number of Cores Number of NVIDIA CUDA cores
    GPU NVIDIA driver version Current version of the installed NVIDIA GPU driver
    GPU NVIDIA License Port Primary NVIDIA license server port
    GPU NVIDIA License Server Primary NVIDIA license server name
    GPU Usage NVIDIA GPU usage in percents
    GPU Video Decoder Usage NVIDIA GPU video decoder usage in percents
    GPU Video Encoder Usage NVIDIA GPU video encoder usage in percents


    Prerequisites:

    • ControlUP Agent - must be installed on the machine where the GPU is installed.
    • NVIDIA WMI v2.30 - current version for 5.0,5.1,5.2.
    • GPU OS Support: 
      • Windows 7 64bit
      • Windows 8/8.1 64bit
      • Windows 10 64bit
      • Windows Server 2008 R2 64bit
      • Windows Server 2012 R2 64bit
      • Windows 2016 64bit
    • NVIDIA GRID Windows Driver Support: 
      • 5.0 - 385.41
      • 5.1 - 385.90
      • 5.2 - 386.09
    • Supported GPUs:
      • M6
      • M10
      • M60
      • P4
      • P6
      • P40
      • P100
    • Hypervisors Support:
      • All hypervisors supported by ControlUp 7.1

    Known Issues:

    After rebooting a machine the ControlUP Agent goes up before the NVIDIA driver and then information is not being pulled properly from Nvidia's API. 

    Solution:

    • Restart the ControlUp Agent by right clicking the machine > Agent Control > Restart Remote Agent. 

    If you wish to change the Reg Keys for the number of retries to contact.

    • Registry path: HKEY_LOCAL_MACHINE\SOFTWARE\Smart-X\ControlUp\Agent\GPU (create GPU key)
    • Keys (DWORD):
      • NumberOfRetries - 5 by default
      • IntervalBetweenRetries - 60000ms by default

     Tip:

    - Full utilization of your GPU can be shown in the command "nvidia-smi" (cmd)

    nvidiasmi.jpg

    - Our blog post about Managing vGPU in VDI

     

     

  • URL Access Directly into ControlUp Monitored Resources

    ControlUp introduces a new way to locate monitored resources by leveraging the moniker functionality of Windows. The most commonly used moniker is “http:“, which tells the operating system that the resource locator that follows it should be opened using a web browser. In a similar fashion, “controlup://” tells the operating system that the trailing resource locator should be parsed by ControlUp. When ControlUp is first launched, it associates the “controlup://” moniker with the console executable, so that it is launched when a URL beginning with this moniker is clicked or otherwise invoked.

    ControlUp URLs consist of the following components:

     

    Moniker

    Pane name

    View (if applicable)

    Search string

    Example:

    controlup://

    MyOrganization/

    Machines/

    server1

    In the example above, after the user clicks controlup://MyOrganization/Machines/server1 URL or uses the Start>Run command in Windows to invoke this URL, ControlUp will be launched or brought to the foreground if already running. Then, it will switch to the Computers view in My Organization pane and populate the search box with the term “server1“. Effectively, if a computer named server1 exists in your ControlUp configuration, it will be shown in the information grid.

    The pipe ( | ) character can be used as an OR logical operator for the search box. For example to display computers named server1 and server2, the following URL can be used: controlup://MyOrganization/Machines/server1|server2

    Other views in My Organization pane can be searched by using URLs like:

    – controlup://MyOrganization/Hosts/esx55srv01

    – controlup://MyOrganization/Sessions/user50

    – controlup://MyOrganization/Processes/wuauclt.exe

    – controlup://MyOrganization/Accounts/user50

    – controlup://MyOrganization/Executables/Outlook

    Other ControlUp panes can also be used with URLs:

    controlup://RemoteDesktop/server1 Switches to the Remote Desktop pane and establishes a remote desktop connection to server1, if exists
    controlup://Controllers Switches to the Controllers pane
    controlup://Incidents/user50 Switches to the Incidents pane and searches for incidents that include user50 in any field
    controlup://Events/user50 Switches to the Events pane and searches for Windows Events that include user50 in any field
    controlup://SecurityPolicy Switches to the Security Policy pane

    The URLs above can be leveraged in several scenarios in which a resource managed by ControlUp is addressed from an external location. Here are some ideas:

    • You send your colleague an email asking to take a look at the performance metrics of a resource
    • You receive an email alert from ControlUp, in which you can click the name of the affected resource to view it in ControlUp
    • An entry is created in your support ticketing system, in which user names can be clicked to show their sessions in ControlUp