vaibhavbhatnaga
ServiceNow Employee

Service Graph Connector for Infoblox

 

Overview

 

Service Graph Connector for Infoblox will import Subnet and IP Address from Infoblox to the ServiceNow CMDB quickly, seamlessly, and securely. It is built Infoblox IPAM module. This integration is part of ServiceNow-developed Service Graph Connectors. The Plug-and-play Service Graph Connectors simplify setup and facilitate quick integration. 

 

Uses cases

  • IP address visibility  
    • Understand what IP addresses are allocated vs what various tools are reporting IP addresses
    • Understand how public IP address is routed to private IP address/s  
    • Enable being able to track – network, domain, and IP pool to a particular set of Application Service  
  • Feed the IP address range that Discovery should scan

 

What is IPAM?

 

IP Address Management is a means of planning, tracking, and managing the Internet Protocol address space used in a network​.

 

Requirement for Setup

 

  • Basic credentials to connect Infoblox instance

 

vaibhavbhatnaga_0-1673365497253.png

 

  • Infoblox Instance

vaibhavbhatnaga_0-1673365739593.png

 

  • Network Views for which data to be imported

 

vaibhavbhatnaga_2-1673365373007.png

 

Configure IPAM task user group

 

Users can configure the task when the subnet is deleted or added. The task can assign to the user group

 

Check/Uncheck create a task when networks are deleted​

Check/Uncheck create a task when networks are added​

 

vaibhavbhatnaga_3-1673365373016.png

 

Assign task user group

 

User group is assigned to a connection from where data is imported

 

vaibhavbhatnaga_4-1673365373023.png

 

 

Data Sources

 

  • SG-Infoblox Synchronize Network : This data source requests current set of IPAM CIs from Infoblox and finds and deletes any unreported CIs from SN instance.​
  • SG-Infoblox IP Pool : This data source imports IP pool.​ IP Pool doesn’t have any IP addresses. It is top level subnet
  • SG-Infoblox IP Address : Data source imports Network subnets and allocated IP address.

 

Import Schedules

 

There are 3 import schedules –

 

  • SG-Infoblox Synchronize Network : This scheduled data import parent for SG-Infoblox IP Pool and SG-Infoblox IP Address. .​
  • SG-Infoblox IP Pool : This scheduled data import invokes data source SG-Infoblox IP Pool.​
  • SG-Infoblox IP Address : This scheduled data import invokes data source SG-Infoblox IP Address.

 

Tables

A New CDBM Model is added for this connector.

 

Configuration Item 

Table 

Description 

Network Subnet 

cmdb_ci_ip_network_subnet 

Represents subnet 

Allocated IP Address 

cmdb_ci_allocated_ip_address 

Represents allocated (used) IP address. 

IP Pool  

cmdb_ci_ip_pool 

Represents a sequential range of IP addresses within a certain network 

Managed Network 

cmdb_ci_managed_network 

Network identifier 

 

 

Note:  Service Graph connector for Infoblox is in the innovation lab. Please raise a request in the store to install it in non-prod instance.

11 Comments
FYL
Mega Sage

@vaibhavbhatnaga 

Can you please advise, how can we identify the Subnet/Network name? 
We want to see if we can make use of it to identify the location for Discovery schedules.
Thanks.

What is the difference between Network Subnet & Managed Network table ? They both appear the same number of records and details based on what we pulled from Infoblox. 

Thanks
Vini
Giga Guru

@vaibhavbhatnaga 

 

Thank you for the blog, We installed Infoblox recently and trying to fetch the data from it to ServiceNow. Test connection was failed initially then we updated property "Property for Service Graph connector for Infoblox application" value from Default. then Test load of 20 records is loding for long time and it was not successful.

 

can you advise on this issue?

FYL
Mega Sage

@Vini 

Try Load All instead, this may take some time depending on the network views you have specified.

Malathi Vinoth
Tera Contributor

While testing the connection with Infoblox it is showing as below error,

Unable to make a connection to Infoblox API call,Please check your credentials again.

 

Is there any additional settings to be done to connect from Public url to private url?

malathiddha
Tera Contributor

How these subnets are onboarded to discovery schedule, as there are huge range will that be manually added or any integration setup to be completed?

Jim41
Tera Expert

We would like to use this for discovery too!  Any plans in the work to add this feature?

 

RE:

@vaibhavbhatnaga 

Can you please advise, how can we identify the Subnet/Network name? 
We want to see if we can make use of it to identify the location for Discovery schedules.
Thanks.

What is the difference between Network Subnet & Managed Network table ? They both appear the same number of records and details based on what we pulled from Infoblox. 

Thanks



Stefan_Garcia
Tera Contributor

Is it possible to pull in Infoblox extended attributes via the Service Graph connector? How would that be accomplished?

Teddy Sincire2
Tera Expert

@Malathi Vinoth 

Make sure to include https:// in the URL and use a mid server that isn't part of a cluster.

 

Stacey Pevec
Tera Expert

Hello community 🙂 I installed the Infoblox ServiceGraph connector and have a few questions. 
1. Trying to get an understanding of how people are using this service graph connector to drive discovery schedules. So far I dont see how to do this.

2. I also do not see the relationships created between the allocated ip adress and the ip address. I opened a HI ticket for that because that is a relationship rule in the class manager for the class.

3. Lastly, how would you use this tool to see how the public IP routes to the private IP? 

 

Thank you!

MikeLerch
Tera Contributor

Hello, everyone!  We've installed the InfoBlox connector, but some of the API calls fail on the InfoBlox side with the following error:

{ "Error": "AdmConProtoError: Result set too large (> 1000)",
  "code": "Client.Ibap.Proto",
  "text": "Result set too large (> 1000)"
}

Speaking with our network team, and browsing through the InfoBlox API documentation that the Guided Setup provides, and it seems clear that the API calls should be using paging but are not.

Is there some configuration parameter we can specify so that paging is used instead of ServiceNow trying to pull all the records all at once?