Public IP address of SNOW instance to establish connection between BMC Remedy and SNOW

SHA3 · ‎06-12-2013

Hi,

For Integration between SNOW and BMC Remedy we need to establish network connection as both are on different network.

Network team is asking for Public IP address and port details to establish the connection.

Can anyone help with, how to find the Public IP Address of our SNOW instance and port details.

Appriciate your response.

richard_selby · ‎07-09-2013

Rather than entering the code in John James Andersen's site (and risk having it fail), it's easier to call his checker via ServiceNow's built in REST tool. To do this, type REST in SN's navigator. Then the NEW button.
Name: Test John-James-Anderson
Description:Publicly available test server
REST endpoint:http://www.john-james-andersen.com/tools/connection.php
Then Save.
When screen reloads, you will see it has automatically created four functions (get,put,post,delete) with the same endpoint. Click on the GET function. Click Test (two thirds of the way down the screen on the left). Then screen should reload and display the output from the Test server, where your (as in your SN instance, not your client) IP is clearly visible.
The two public IP addresses I have seen from our instances are 199.91.137.12 and 37.98.232.12
My guess is the former is for instances running out of Heathrow and the latter is Amsterdam. It would be nice to know though whether more outbound IPs are possible.

View solution in original post

jason_petty · ‎06-17-2013

If you allowed port 80 and 443 you should be good.

richard_selby · ‎07-09-2013

Rather than entering the code in John James Andersen's site (and risk having it fail), it's easier to call his checker via ServiceNow's built in REST tool. To do this, type REST in SN's navigator. Then the NEW button.
Name: Test John-James-Anderson
Description:Publicly available test server
REST endpoint:http://www.john-james-andersen.com/tools/connection.php
Then Save.
When screen reloads, you will see it has automatically created four functions (get,put,post,delete) with the same endpoint. Click on the GET function. Click Test (two thirds of the way down the screen on the left). Then screen should reload and display the output from the Test server, where your (as in your SN instance, not your client) IP is clearly visible.
The two public IP addresses I have seen from our instances are 199.91.137.12 and 37.98.232.12
My guess is the former is for instances running out of Heathrow and the latter is Amsterdam. It would be nice to know though whether more outbound IPs are possible.

SHA3 · ‎07-09-2013

Hi Richard,

Thanks for the steps.

the IP i got is 37.98.232.12.

gandalf · ‎09-19-2023

Hi richard_selby

I've tried as you suggest but the response is very unclear. Are you sure that the method works?

Here below the response given by the suggested endpoint:

html style="height:100%"><head><META NAME="ROBOTS" CONTENT="NOINDEX, NOFOLLOW"><meta name="format-detection" content="telephone=no"><meta name="viewport" content="initial-scale=1.0"><meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"></head><body style="margin:0px;height:100%"><iframe id="main-iframe" src="/_Incapsula_Resource?SWUDNSAI=9&xinfo=14-45184899-0%200NNN%20RT%281695189205924%201%29%20q%280%20-1%20-1%20-1%29%20r%280%20-1%29%20B12%284%2c315%2c0%29%20U18&incident_id=1460000770079428192-245110369179407182&edet=12&cinfo=04000000&rpinfo=0&cts=yh71x1nw%2fDzkKZeVbOX4mgjRKKWRCtOIfUFlUV7XReNwyuTLjaxlcXpHbrzzbbHn&mth=GET" frameborder=0 width="100%" height="100%" marginheight="0px" marginwidth="0px">Request unsuccessful. Incapsula incident ID: 1460000770079428192-245110369179407182<iframe><body><html>

richard_selby · ‎07-09-2013

I have just heard back from ServiceNow Hi on this one. I have cut and pasted their reply (with some minor editing). Hope this helps others looking to connect webservices etc.

For Instances on LHR1 - Slough, UK (Equinix) Datacenter:
Datacenter IP range: 199.91.137.0/24
VPN Peer: 199.91.137.20
Integrations into customer network
For integrations INBOUND to the customer network (ie: LDAP, SQL, etc) when there is NO VPN tunnel involved, the source IP address will be 199.91.137.12.
For integrations INBOUND to the customer network (ie: LDAP, SQL, etc) when there IS a VPN tunnel involved, the source IP address will be 199.91.137.22.

Integrations into Service-now network
Note: This traffic will connect over the Internet and the traffic will be encrypted with SSL.
For outbound integrations or end user access to the Service-now network, the destination IP address will be 199.91.137.100 and 199.91.137.102. These are the VIPS on the load balancer.

For instances at AMS3 - Amsterdam, NL (Equinix) Datacenter
Datacenter IP range: 37.98.232.0/24
VPN Peer: 37.98.232.20

Integrations into customer network
For integrations INBOUND to the customer network (ie: LDAP, SQL, etc) when there is NO VPN tunnel involved, the source IP address will be 37.98.232.12.
For integrations INBOUND to the customer network (ie: LDAP, SQL, etc) when there IS a VPN tunnel involved, the source IP address will be 37.98.232.22.

Integrations into Service-now network
Note: This traffic will connect over the Internet and the traffic will be encrypted with SSL.
For outbound integrations or end user access to the Service-now network, the destination IP address will be 37.98.232.100 and 37.98.232.102. These are the VIPS on the load balancer.