question SErviceNow Discovery issue in Community Central forum

SErviceNow Discovery issue

sadhna — Fri, 07 Jun 2024 14:07:35 GMT

Hi Guys,

I have a requirement to run discovery for SSL VPN (Ivanti) devices.
Can Anyone help me out for running Discovery of these sort of devices.
As I have received an error message that Port 161 is down but when I checked with the Network Team These have been allowed there in Firewall.
What might be the reason behind this issue and what will be the solution for it????

Re: SErviceNow Discovery issue

Shaqeel — Fri, 07 Jun 2024 14:26:26 GMT

Hi @sadhna

Verify Firewall Configuration: Even though the network team has allowed port 161 in the firewall, double-check the configuration to ensure there are no issues. Sometimes, there could be misconfigurations or other rules affecting the traffic.
Check Connectivity: Ensure that there is proper connectivity between the discovery probe and the SSL VPN devices. You can use tools like ping or traceroute to verify connectivity. Sometimes, the issue might not be with the firewall but with network routing.
Firewall Logs: Check the firewall logs to see if any traffic is being blocked or if there are any errors related to port 161. This can provide valuable insights into whether the traffic is reaching the SSL VPN devices or not.
SSL VPN Configuration: Review the SSL VPN device configuration to ensure that it is configured to respond to discovery requests. Sometimes, devices might have settings that restrict or block discovery attempts.
Network Device Configuration: Ensure that the SSL VPN devices are configured to allow SNMP traffic on port 161. Check if SNMP is enabled and configured correctly on these devices.
Alternative Discovery Methods: If SNMP discovery is not working, consider using alternative discovery methods such as SSH or WMI depending on the capabilities of the SSL VPN devices. ServiceNow Discovery supports multiple discovery protocols, so exploring alternatives might help in discovering these devices.

Regards

Shaqeel

Re: SErviceNow Discovery issue

sadhna — Tue, 11 Jun 2024 12:30:45 GMT

Ports are allowed,No errors is being triggered in the traffic logs.
But at Sevicenow end it is still showing as 161 is down

Re: SErviceNow Discovery issue

Sohail Khilji — Tue, 11 Jun 2024 13:22:15 GMT

it must be 161 UDP not TCP.

can u share discovery logs?

Re: SErviceNow Discovery issue

sadhna — Tue, 11 Jun 2024 18:43:51 GMT

Please have a glance at attached.