The root cause is that the servers contain an unsupported EntityType, or the value is blank.
To prove this:
- Get loglevel 10 logs for the ETL
- Grep for the systemname (i.e. myserver.bmc.com) in ETL logs until you find a line that gives you the corresponding deviceid (in our example deviceid is 22181)
{"deviceId":"
22181","dnsName":
myserver.bmc.com","dispName":myserver.bmc.com","ipAddress":"172.26.1.6","deviceEntityType":"Default","deviceType":"0","parentDeviceId":"0","isMarkedForDelete":false,"tokenList":[{"tokenId":"","serverId":96,"hostId":9866}]}
- Grep for the deviceid 22181 until you find the corresponding monInstId (usually this is contained on a single line, into a very long list together with other servers). In this example monInstId is 587623
{"deviceId":"22181","monUniqName":"_PATROL__NT_OS","monInstName":"Windows Operating System","isMarkedForDelete":false,"monInstKey":{"serverId":"96","monTypeId":"501104","monInstId":"587623"}
- On the ETL logs level 10 based on the server monTypeId ad monInstId we can find if the API call is returning an EntityType value is empty or unsupported (based on the configuration of the TSOM ETL)
EXAMPLE OF EMPTY ENTYTYTYPE:
- From this first example it's clear the EntityType for moninstid 587623 is EMPTY (reported as""). This needs to be fixed at the patrol agent level with the TSIM admin. Until the EntityType is empty the affected systems with NOT get imported into TSCO. If the TSIM admin doesn't know how to fix this a Patrol agent support case can be opened, stating that EntityType is reported as empty by Patrol agent(s).
{"monUniqName":"_PATROL__NT_OS","monInstName":"Windows Operating System","monInstKey":{"serverId":"96","monTypeId":"501104","monInstId":"587623"},"attributeMap": {"CpuMhz":"","DiskCount":"","INSTANCE_NAME":"Windows Operating System","META_UNIQUE_ALIAS":"","NetInterfaceCount":"","_SystemConfig":"","PORT":"3182","CI_ID":"","OsVersion":"6.2 ","LogicalCpuCount":"","EntityType":"","DNSIP":"","CpuCount":"","hwModel":"","NetBandwidthMbps":"","hwVendor":"","MemAvailableKB":"8388608.000000","OsType":"Windows Server 2019 Standard","CI_TOKEN_ID":"","USERNAME":"admin","CpuType":"","CI_ALIAS":"","SolutionVersion":"20.05.10"}},
EXAMPLE OF UNSUPPORTED ENTYTYTYPE:
- From this second example, it's clear the EntityType for moninstid 587623 is HP.Integrity.Virtual_Machine does NOT correspond to a standalone system, so this system is not getting imported by the TSOM standalone ETL.
{"monUniqName":"_PATROL__UNIX_OS","monInstName":"UNIX OS","monInstKey":{"serverId":"2","monTypeId":"111111","monInstId":"587623"},"attributeMap":{"CpuMHz":" 2530","DOMAIN":"","META_UNIQUE_ALIAS":"","_SystemConfig":"","CI_ID":"","HostLogicalCpuCount":"","LVIRTCONFIGUREVMS":"","OsVersion":"xyzw","DNSIP":"","CpuCount":" 32","hwModel":" ia64 hp server Integrity Virtual Machine","NetBandwidthMbps":"000000","MemAvailableKB":"000000","OsType":"HP-UX","CPUDESCRIPTION":" TESTING","USERNAME":"XXXXX","CpuType":"XXXX","HOSTID":" XXXXXX","CORESPERSOCKET":"","SolutionVersion":"XXXXXX","THREADSPERCORE":"","DiskCount":"000000","INSTANCE_NAME":"UNIX OS","NetInterfaceCount":"000000","PORT":"XXXX","HOSTALIAS":"","LogicalCpuCount":"","HostMemAvailableKB":"","MTTHREADINGTYPE":"","PartitionType":"","EntityType":" HP.Integrity.Virtual_Machine","LVIRTACTIVEVMS":"","hwVendor":" HP","CI_TOKEN_ID":"","PROCESSORSOCKETS":"","CPUVENDOR":"","HostCpuCount":"","MEMAVAILABLEMB":"000000","CI_ALIAS":"","PAGESIZE":""}}
You need to contact your TrueSight Integration Manager team and request assistance to correct the EntityType of the servers (in this case to StandAlone).
VALID ENTITYTYPE VALUES:
Linux.StandAlone for a Linux machine (if it’s RedHat.KVM.Host see KA416701, agent KM needs a patch)
SunZone.Host: for a Solaris virtualization zone host
SunZone.Virtual_Machine: for a Solaris zone VM
Sun.Ldom.Primary.Host: for a Solaris virtualization LDOM host
Sun.Ldom.Primary.Virtual_Machine: for a Solaris LDOM VM
Microsoft.StandAlone: for a Windows Standalone system
HP.StandAlone: for an HP Standalone system