Service graph connector for Infoblox connection is failing?

Vini
Giga Guru

Hi,

 

We are trying to retrieve IP address / IP subnets from Infoblox by using "Service graph connector for Infoblox " but test connection is failing with the following error.

Error Info# Unable to make a connection with Infoblox please check the credentials.

In the logs we notice the error code 404 which mence there is no connection between ServiceNow and Infoblox.

 

- Let us know if you have the same issue / Resolution. Thank you in advance

2 ACCEPTED SOLUTIONS

Vini
Giga Guru

Hi All and @Stacey Shapiro 

 

We identified the solution.

1. we set the 'Network Flow' value in your Infoblox connector to <Client Name> at Configure Infoblox HTTP connection.
https://<instance name>.service-now.com/now/nav/ui/classic/params/target/http_connection.do%3Fsys_id%3D63a23482536011109f66ddeeff7b12a6
2. Then we updated your 2 Infoblox Data Source (Pool and IP Address) to use the connector specified. This should allow them to uptake the Network Flow change that allows them to connect successfully.
3. Then we navigated to Integrationhub ETL and configured both of the Infoblox connectors (Pool and IP Address). We left most defaults values as is, but this is where you will make changes if you have missing field values in your destination data. We did change the frequency of the import for Infoblox Pool from 'Periodically' to 'Daily' at 1:00am.
4. A test run from the Integrationhub ETL shows sample records being written to your source table and from there to the destination tables successfully. Now your Infoblox connector should run tonight.

Validated after full load now new records are added on following tables.
Allocated IP Addres# cmdb_ci_allocated_ip_address
IP Networks subnet# cmdb_ci_ip_network_subnet

 

Regards,

Vinil.

 

View solution in original post

Vini
Giga Guru

Identified the Solution for this issue.

1. we set the 'Network Flow' value in your Infoblox connector to <Client Name> at Configure Infoblox HTTP connection.
2. Then we updated your 2 Infoblox Data Source (Pool and IP Address) to use the connector specified. This should allow them to uptake the Network Flow change that allows them to connect successfully.
3. Then we navigated to Integrationhub ETL and configured both of the Infoblox connectors (Pool and IP Address). We left most defaults values as is, but this is where you will make changes if you have missing field values in your destination data. We did change the frequency of the import for Infoblox Pool from 'Periodically' to 'Daily' at 1:00am.
4. A test run from the Integrationhub ETL shows sample records being written to your source table and from there to the destination tables successfully. Now your Infoblox connector should run tonight.

Validated after full load now new records are added on following tables.
Allocated IP Addres# cmdb_ci_allocated_ip_address
IP Networks subnet# cmdb_ci_ip_network_subnet

View solution in original post

4 REPLIES 4

Stacey Shapiro
Tera Expert

I had a hard time getting this setup also but finally got it to work. I used the URL Builder. For the host, I just put the URL that I use to log into infoblox. I left port and base path blank. Under attributes, I listed the API version. This got the test connection to work. My issue now is that the data load just hangs but at least it is connecting. Hope this helps you. 

 

 

Vini
Giga Guru

Hi All and @Stacey Shapiro 

 

We identified the solution.

1. we set the 'Network Flow' value in your Infoblox connector to <Client Name> at Configure Infoblox HTTP connection.
https://<instance name>.service-now.com/now/nav/ui/classic/params/target/http_connection.do%3Fsys_id%3D63a23482536011109f66ddeeff7b12a6
2. Then we updated your 2 Infoblox Data Source (Pool and IP Address) to use the connector specified. This should allow them to uptake the Network Flow change that allows them to connect successfully.
3. Then we navigated to Integrationhub ETL and configured both of the Infoblox connectors (Pool and IP Address). We left most defaults values as is, but this is where you will make changes if you have missing field values in your destination data. We did change the frequency of the import for Infoblox Pool from 'Periodically' to 'Daily' at 1:00am.
4. A test run from the Integrationhub ETL shows sample records being written to your source table and from there to the destination tables successfully. Now your Infoblox connector should run tonight.

Validated after full load now new records are added on following tables.
Allocated IP Addres# cmdb_ci_allocated_ip_address
IP Networks subnet# cmdb_ci_ip_network_subnet

 

Regards,

Vinil.

 

Vini
Giga Guru

Identified the Solution for this issue.

1. we set the 'Network Flow' value in your Infoblox connector to <Client Name> at Configure Infoblox HTTP connection.
2. Then we updated your 2 Infoblox Data Source (Pool and IP Address) to use the connector specified. This should allow them to uptake the Network Flow change that allows them to connect successfully.
3. Then we navigated to Integrationhub ETL and configured both of the Infoblox connectors (Pool and IP Address). We left most defaults values as is, but this is where you will make changes if you have missing field values in your destination data. We did change the frequency of the import for Infoblox Pool from 'Periodically' to 'Daily' at 1:00am.
4. A test run from the Integrationhub ETL shows sample records being written to your source table and from there to the destination tables successfully. Now your Infoblox connector should run tonight.

Validated after full load now new records are added on following tables.
Allocated IP Addres# cmdb_ci_allocated_ip_address
IP Networks subnet# cmdb_ci_ip_network_subnet

Malathimal
Tera Contributor

We could not able to find Network flow value itself.. Could you please put screenshot or elaborate in this variable