Configure Operating System Instances

Use the Configuration tab to establish Windows (WMI) and Linux (SSH) credential sets for specified hosts. Credential information is supplied by the customer. The credentials needed for VirtualWisdom can be read-only, and do not require admin privileges and root access. In many cases, customers are already using management tools with established credentials, and these can often be leveraged for use with Operating System Integration.

About This Task

There are specific permission/administrator requirements for using the OS Data Collector.

  • For Linux systems, a non-root account can be used. The only minor effect of a non-root account is that the “hypervisor type” property is not populated for ESX VMs.

  • For Windows 2016 and Windows 2012R2A, a non-administrator account can be used.

    • A non-administrator account can also be used for Windows 2008 R2 Standard, but network and disk entities cannot be discovered from it.

    • When a non-administrator account is used, the account must be in the "Performance Monitor Users Group," and "User Account Control" must be disabled. See https://docs.microsoft.com for a description of the "User Account Control"feature's relationship to WMI.

Known Issues

Description

Workaround

On some versions of Linux, the speed of a network interface cannot be obtained from the operating system.

None.

You cannot create a report when the %Network Received Utilization and %Network Transmit Utilization metrics are used with the Application filter.

You can see data for these metrics with the Network Interface filter. Manually add appropriate Network Interface entities to your application.

Upon upgrade to VW 6.1 or later, any existing Logical Volume entities are archived and Logical Volumes re-discovered.

None.

Metrics collected prior to VW 6.1 for preexisting Logical Volumes can be accessed by requesting reports on the archived Logical Volumes.

Prerequisites

If you have enabled VMware vSphere Integration or IBM PowerVM Integration, you should have run at least one discovery on those integrations before doing an Operating System Integration discovery. Otherwise, you might see duplicate compute entities in the UI.

  1. Click Settings, then Integrations in the Probes and Integrations section, and then the View button for Operating System.

    The Operating System page displays, consisting of two tabs:

    • Configuration

    • Subscribe to OS Instances

      R8qFM4oOYbVG6EZwvpoARg.png
  2. On the Configuration tab, click Add to add a credential set.

    The New Credential Set dialog box displays.

    There are two variations of the New Credential Set dialog box, depending on whether you are adding Linux (SSH) or Windows (WMI) credentials.

    You can use a private key for SSH credentials, but it requires a key file. Passphrase is optional.

    If the host password is changed, the credential set must also be changed. All passwords stored in VirtualWisdom are encrypted.

    For Windows OS monitoring, CIFS Security Mode NTLMv1 and NTLMv2 are both supported.

    Discovery Time and Frequency is, unlike other scheduled discovery processes, bounded by a specified duration in hours. After that amount of time, discovery is paused and bookmarked, and the next scheduled discovery starts at that bookmark.

    These settings apply to discovery for both application discovery and OS monitoring.

    _y4g6uPMEJMumG72itx3VA.jpg

 

Related Topics

Import File Format