Device not reachable through Discovery (but accessible via MID server)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2016 10:57 AM
Hi,
Has anyone ever had a scenario where a device is reachable if you login to MID server and try to access the device BUT seems to be dead when you try to discover it? What are the possivble causes? And how should we go about debugging and resolving those access issues?
Thanks.
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2016 11:17 AM
Can you provide more detail how you are accessing it through the MID server?
What error messages are being returned from Discovery?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2016 01:19 PM
Hi ctomasi,
Thanks for your response. We are able to ping as well as access (direct) web console of that device. However, shazzam probe returns nothing - not even alive flag as true.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2016 01:36 PM
What protocol/port are you trying to reach this with when you use Discovery? The typical three are WMI (Windows), SSH (Unix/Linux), and SNMP (most network devices, PDUs, etc.) Does your device speak one of these?
This may help get you started...
Discovery Troubleshooting - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-10-2016 06:27 PM
Sounds like there's a very effective firewall or ACL preventing the port scan to seeing any of our classification ports in a state of open. As you mention its not even alive (responsive in some sort). So yes I would look to your well applauded security team to see what it will take to get the midserver "closer" to those devices..
