Notifications

1233 views

Description

Vcenter discovery does not use the Identification and Reconciliation engine to uniquely identify a CI but a function within script include VCenterESXHostsSensor is used instead.

Line 36: index: [ esxCorrelationIdIndex, ['serial_number'] ]

If the ESX servers discovered in the payload do not already exist in CMDB, 'esxCorrelationIdIndex' will not return results, which means that serial_number will then be used to uniquely identify a CI. Now, if the discovered ESX servers have duplicate serial_number in the payload, then only one ESX server CI record will be created and attributes such as name, correlation_id etc. will be overwritten with the name, correlation_id of the next ESX server with the same serial number.

This also means that Identification Engine Reconciliation rules, such as Data Source Precedence is not used by these inserts/updates.

Steps to Reproduce

  1. Run Vcenter discovery in an environment where ESX servers have duplicate serial numbers.

Workaround

This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

Modify the CI identifier in script include VCenterESXHostsSensor. For example, use correlation_id first if it can be trusted to uniquely identify a CI in your environment.

  1. Edit line 36 of "VCenterESXHostsSensor" script include 
  2. Replace index: [ esxCorrelationIdIndex, ['serial_number'] ] 
    • with index: [ esxCorrelationIdIndex, ['correlation_id'], ['name'] ], 
    • OR, with a combination like index: [ ['morid', 'correlation_id'], ['name'] ] 
  3. Click on Update 

Related Problem: PRB1323765

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - Audit Management PA Content - Madrid 2019 Q1
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - GRC Workbench - New York 2019 Q3
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Policy and Compliance PA Content - Madrid 2019 Q1
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - Risk Management PA Content - Madrid 2019 Q1
SR - IRM - SIG Assessment Legacy - Madrid 2019 Q1
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - CMDB CI Class Models - 201907
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3

Fixed In

Madrid Patch 6
New York

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-04-01 08:43:46
Published:2019-09-03