Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This article details how to generate report using the RestAPI which will mirror as closely as possible the "OutputDevices" report which was available in V3 of iQSonar.
You can download the latest version of the file: OutputDevices-v1.ps1, and simply customise the $user, $pass and $sonar values and it should run in your environment

...

FieldV3 CommentRestAPI Comment
HostnameHostname of the deviceGet this from the /devices RestAPI endpoint 
FQDNFully QUalified Domain Name of the deviceGet this from the /devices/{Device_ID} RestAPI endpoint
OSOS description and service packGet this from the /devices/{Device_ID} RestAPI endpoint
OS Install DateOS description and service packGet this from the /devices/{Device_ID} RestAPI endpoint
May not always be available
LocationLocation of the deviceIn V4 this represents the target configuration set used to define the device.
Get this from the /devices RestAPI endpoint
Serial NumberThe serial number of the deviceGet this from the /devices RestAPI endpoint
PhysicalCPUCountNumber of physical CPUs or sockets in the Physical Device (which may differ from the Virtual or Logical host when a device is a virtual machine or partition)

IF the device is a physical device, this information is derived from the /devices/{Device_ID} RestAPI endpoint
IF the device is a virtual device AND we have scanned the virtualisation host, the information is also available.

Where the virtualisation host is not scanned, then this field and all the other information about the physical host will not be able to be populated.

PhysicalCoreCountSum of cores across all CPUs in the Physical Device (which may differ from the Virtual or Logical host when a device is a virtual machine or partition)Get this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalCoresPerCPUPhysical core count divided by the physical CPU countGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalCPUManufacturerManufacturer of the CPU on the Physical DeviceGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalCPUModelModel of the CPU on the Physical DeviceGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalCPUSpeedSpeed of the CPU on the Physical DeviceGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalRAMTotal amount of RAM on the Physical DeviceGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
VirtualCPUCountNumber of Virtual CPUs perceived by the device (only populated when the device is Virtual or Logical)Get this from the /devices/{Device_ID} RestAPI endpoint; Only available if device is virtual or logical
VirtualCoreCountSum of Cores perceived by the device (only populated when the device is Virtual or Logical)Get this from the /devices/{Device_ID} RestAPI endpoint; Only available if device is virtual or logical
VirtualRAMAmount of perceived RAM by the device (only populated when the device is Virtual or Logical)Get this from the /devices/{Device_ID} RestAPI endpoint; Only available if device is virtual or logical
DeviceModelModel of the deviceGet this from the /devices RestAPI endpoint for a physical device.
PhysicalModelSocketCountNumber of sockets that may be populated with physical CPUs on the Physical DeviceGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalModelCoreCountMaximum number of cores per CPU according to the model documentationGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalDeviceManufacturerManufacturer of the Physical DeviceGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalHostnameHostname of the Physical DeviceGet this from the /devices/{Device_ID} RestAPI endpoint for virtual devices; May not always be available
PhysicalFQDNFully Qualified Domain Name of the Physical DeviceGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
IP Address
  • If more than 1, will be semi-colon separated. 
  • Info such as DHCPServer from IPAddress table will not be in OutputDevices. 
  • Will only include IPv4.
V4 also exposes IP6 addresses.
PhysicalMACAddressIf more than 1, will be semi-colon separated.
VirtualMACAddressIf more than 1, will be semi-colon separated.
ClusterInformationThe virtualization cluster that the physical machine is part ofOnly available if it is part of a cluster, and the cluster has been scanned
ClusterNameName of clusterOnly available if it is part of a cluster, and the cluster has been scanned
PartitioningMethodVirtualization Method (VMware, HyperV, LPAR etc.). If this field is null it indicates the device is physical.
DerivedCPU
Not directly available via RestAPI. Must be coded in the script.
DerivedCoresPerCPU
Not directly available via RestAPI. Must be coded in the script.
BiosConcatenation of Device.BIOSName, DeviceBIOSManufacturer, Device.BIOSVersion separated by semi-colons.Get this from the /devices/{Device_ID} RestAPI endpoint.
LastScanDateLast date the device was scannedGet this from the /devices/{Device_ID} RestAPI endpoint.
DeviceIDThe unique identifier for this deviceThe Rest API gives unique identifiers in GUID format
PhysicalDeviceIDThe unique identifier of the Physical Device (where relevant) – used to map logical devices or Virtual machines back to the Physical Device which hosts them.Get this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalCPUNotesNotes that indicate CPU vs socket mismatches or CPU core values that don’t match the CPU modelThis V3 data is not directly available via RestAPI. This functionality is part of DataHub for V4, and if required must be coded in the script.
NotesNotes related to the device modelThis V3 data is not directly available via RestAPI. This functionality is part of DataHub for V4, and if required must be coded in the script.
ExternalLinkLink to model documentation from the vendorThis V3 data is not available via RestAPI.
DNSHostnameThe hostname of the device as reported from DNSGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
DNSFQDNThe fully qualified hostname of the device as reported from DNSGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalDNSHostnameThe hostname of the physical device as reported from DNSGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
PhysicalDNSFQDNThe fully qualified hostname of the physical device as reported from DNSGet this from the /devices/{Device_ID} RestAPI endpoint; May not always be available
MeasurementCommentWill contain additional info such as “Believed to be: Oracle Linux Server release 5.7” where appropriateThis V3 data is not available via RestAPI.

...

Code Block
languagepowershell
themeMidnight
titlePhysical and Virtual info for VMs
else 
		{
			# This is a virtual target
			if ( ($currDevice.cpu_count -eq 0) -or (!$currDevice.cpu_count) )
			{
				# Physical CPU info not avialble
				$row | Add-Member -MemberType NoteProperty -Name "VirtualCPUCount" -Value "n/a"
				$row | Add-Member -MemberType NoteProperty -Name "VirtualCoreCount" -Value "n/a"
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalCoresPerCPU" -Value "n/a"
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalCPUManufacturer" -Value "n/a"
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalCPUModel" -Value "n/a"
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalCPUSpeed" -Value "n/a"
			}
			$row | Add-Member -MemberType NoteProperty -Name "VirtualCPUCount" -Value $currDevice.cpu_count
			$row | Add-Member -MemberType NoteProperty -Name "VirtualCoreCount" -Value $currDevice.core_count
			$row | Add-Member -MemberType NoteProperty -Name "VirtualRAM" -Value = $currDevice.total_memory_mb
			$row | Add-Member -MemberType NoteProperty -Name "DeviceModel" -Value $currDevice.model
			# Do something with MAC addresses for VMs
			
			# Now, if the VM host we're running on was scanned, we can do something with the following:
			if (!$currDevice.virtual_host.device_id)
			{
				# host not scanned, record an error by putting "n/a" in physical hostname, leave everything else blank
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalHostname" -Value "n/a"
			}
			else 
			{
				# host was scanned, so let's populate as many details as possible about the physical host
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalCPUCount" -Value $currDevice.virtual_host.cpu_count
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalCoreCount" -Value $currDevice.virtual_host.core_count
				if ( ($currDevice.virtual_host.cpu_count -ne 0) -and ($currDevice.virtual_host.core_count -ne 0))
				{
					$cpcpu = $currDevice.virtual_host.core_count / $currDevice.virtual_host.cpu_count
					$row | Add-Member -MemberType NoteProperty -Name "PhysicalCoresPerCPU" -Value $cpcpu
				}
				# In order to get the CPU Manufacturer information, you need to follow the link to 
				# $currDevice.virtual_host.self and parse the CPU info there. This is left as an exercise to the user
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalCPUModel" -Value "n/a"
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalCPUSpeed" -Value "n/a"
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalRAM" -Value $currDevice.virtual_host.total_memory_mb
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalDeviceManufacturer" -Value $currDevice.virtual_host.manufacturer
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalHostname" -Value $currDevice.virtual_host.host_name
				
				# In order to get the MAC Address for the physical host, you need to follow the link to 
				# $currDevice.virtual_host.self and parse the MAC info there. This is left as an exercise to the user
				$row | Add-Member -MemberType NoteProperty -Name "PhysicalMACAddress" -Value "n/a"
				
			}
		}

But... we want all the

...

columns in the same order as the original report

The script above works to extract the data, but if you want to feed the CSV file to a data processing application which was written for a V3 datasource, you probably want to have the columns in the "correct" order (including empty columns) so that your third party application does not need to be reconfigured or re-written. So, to force all the columns to be saved, including the columns that are always empty, and to have the columns in the correct order corresponding to the original V3 file, we use the Select-Object powershell cmdlet, and pipe the results into the Export-CSV cmdlet.

This produces a very long line of code, so we use backticks to break it up for readibility

Code Block
languagepowershell
themeMidnight
titleOrder columns in the CSV
$csv | Select-Object Hostname, FQDN, OS, OS-Install-Date, Location, Serial-Number, PhysicalCPUCount, PhysicalCoreCount, PhysicalCoresPerCPU, `
   PhysicalCPUManufacturer, PhysicalCPUModel, PhysicalCPUSpeed, PhysicalRAM, VirtualCPUCount, VirtualCoreCount, VirtualRAM,  DeviceModel, `
   PhysicalModelSocketCount, PhysicalModelCoreCount, PhysicalDeviceManufacturer, PhysicalHostname, PhysicalFQDN, IP-Address, `
   PhysicalMACAddress, VirtualMACAddress, ClusterInformation, ClusterName, PartitioningMethod, DerivedCPU, DerivedCoresPerCPU, `
   Bios, LastScanDate, DeviceID, PhysicalDeviceID, PhysicalCPUNotes, Notes, ExternalLink, DNSHostname, DNSFQDN, PhysicalDNSHostname, `
   PhysicalDNSFQDN, MeasurementComment  | Export-csv OutputDevices.csv -NoTypeInformation

...