Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Network Performance Monitor (NPM) > Hardware field values in NPM Node Details

Hardware field values in NPM Node Details

Table of contents
Created by Kevin Twomey, last modified by MindTouch on Jun 23, 2016

Views: 346 Votes: 2 Revisions: 5

Overview

This article explains how the Hardware field in the Node Details page is populated in NPM.

Environment

All NPM versions

Detail

The Hardware field is populated from the SWIS field called Nodes.EntityType.

This value depends on if the node is recognized as a virtual machine. It either has an entry in the VIM_VirtualMachines table, meaning it is monitored by VIM, or one of its network cards MAC address starts with one of the following VMware vendor prefixes:

  • 0003FF%
  • 000C29%
  • 005056%
  • 000569%
  • 001C14%

The following are possible values for the Hardware field:

  • Physical – The node is a physical machine.
  • Virtual, host unknown – The node has an entry in the VIM_VirtualMachines table (but ESX host which is running this VM is not managed) or the MAC address vendor prefix belongs to VMware.
  • Virtual hosted by <someNodeCaption> - The node has an entry in the VIM_VirtualMachines table and the ESX host which is running this VM is managed by Orion and IVIM.

Physical nodes are normally set to Orion.Nodes in the Nodes.EntityType field in the Nodes table .

The DB columns in the dbo.Nodes table are populated when:

  • These fields are also set if the existing Orion node is discovered as ESX during vCenter polling.
  • When a node is added to Orion (using Add node wizard or discovery) and is recognized as ESX/vCenter.
    Examples:
  • EntityType          = "Orion.VIM.Hosts" / "Orion.VIM.VCenters"
  • Vendor                = "VMware Inc."
  • MachineType    = (according to VMwareProductName property)

For any issues displaying the wrong information in the Hardware field, check the VIM_VirtualMachines Table, the MAC Address and check for duplicate nodes.

 

Last modified
22:24, 22 Jun 2016

Tags

Classifications

Public