need to populate ip address and serial number in server class via integration

[chaitali shah]

Hi Folks,

When doing discovery via integration i can see ip address and serial number is not populating in server class.

can somebody suggest me how to populate IP address, Serial number Fields from multiple tools integration into server class.

[Ashok Sasidhara]

Is this for any specific integration? The best practice is to use 'Service graph connectors' for any 3rd party integrations if that integration is supported by Service Graph Connector.  

If the 'IP address' and 'Serial number' is available in the source data from the integrated tool, you need to simply update the transform map to make sure that they are populated to the 'Server' table. If these 2 attributes not available in the data imported from the tool, you need to connect with the team supporting that tool and find out if the data for these 2 attributes are present in that tool.  If they are available, then you need to look at the feasibility of updating the data import query to bring in these 2 attributes to ServiceNow (Typically such important attributes like Serial Number and IP Address might have to be available in the OOB data import & transform map if the integration is through Service Graph Connectors)

[chaitali shah]

Currently we are using ServiceNow integration via third party which includes active  directory,infoblox,nagios,qualys.

Could you please provide me exact procedure in ServiceNow  so I can populate different fields in server table.

[Ashok Sasidhara]

The following URLs might be helpful for qualys and infoblox integrations:

https://www.qualys.com/docs/qualys-asset-inventory-cmdb-sync-ire.pdf

https://docs.servicenow.com/en-US/bundle/vancouver-servicenow-platform/page/product/configuration-ma...

[Harish Bainsla · Accepted solution]

When performing discovery via integration, such as integrating with multiple tools to populate IP addresses and serial numbers into the server class in a configuration management database (CMDB), there are several steps and considerations you need to take into account. Here's a general guide to help you achieve this:

1. Integration Setup:

   • Ensure that you have proper integrations set up with the relevant tools and data sources.
   • Verify that the integrations are providing accurate and reliable IP address and serial number information.

2. CMDB Configuration:

   • In your CMDB, create or identify the appropriate CI (Configuration Item) class that represents the servers. Let's assume the class is called "Server."

3. Mapping Fields:

   • Ensure that the "Server" class in your CMDB has fields to store IP address and serial number information. If these fields are not present, you may need to add them.

4. Discovery Jobs:

   • Configure discovery jobs to run against the integrated data sources to retrieve IP address and serial number information.
   • Discovery jobs might involve running probes or scripts to collect information from devices and systems.

5. Data Transformation and Enrichment:

   • After retrieving the IP address and serial number information, you'll likely need to transform and enrich the data to match the format and structure of the "Server" class in your CMDB.
   • You might need to normalize IP addresses to a specific format (IPv4 or IPv6), handle duplicates, and ensure data consistency.

6. Data Import and Synchronization:

   • Implement a process to import the transformed and enriched data into the CMDB.
   • Schedule regular synchronization jobs to keep the IP address and serial number information up to date.

7. Error Handling and Data Quality:

   • Implement error handling mechanisms to capture any issues encountered during the integration and import process.
   • Monitor data quality and address any discrepancies or anomalies that arise.

8. Testing and Validation:

   • Thoroughly test the integration and data import process in a controlled environment before deploying to production.
   • Validate that the IP address and serial number information is accurately populated into the "Server" class.

9. Documentation and Monitoring:

   • Document the entire integration process, including configurations, mappings, transformation logic, and scheduled jobs.
   • Implement monitoring and logging to track the success of the integration and to troubleshoot any issues that arise.

10. Continuous Improvement:

    • Continuously monitor the integration's performance and accuracy.
    • Regularly review and update the integration process based on changes in data sources, tools, or requirements.