- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-02-2017 02:57 PM
We are new to asset management and discovery so I may not be asking the right questions so I apologize in advance. :0)
We had outside help getting discovery set up; they helped with our mid server builds, schedules, and vlans (range sets and ranges). For the last several months we have been running discovery to discover and identify the current assets we have in our environment. We are getting ready to take the next step with Asset Management.
Our staff will be building assets and then will deliver these and put them on the network. When discovery discovers these assets we want to make sure that the correct CI stub is being updated. We want to verify that discovery is matching off the serial number. How do we verify this is set up correctly in our system?
We understand if discovery does not find a match a new asset is built. How to look for possible duplicates, incase we input the serial number wrong?
We also noticed that discovery is putting in the company instead of the manufacturer when creating the hardware model?
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-04-2017 02:50 PM
Trisha,
You can look at the discovery status log for each scan and it will show you which identifier matched on the CI. You'll see a line similar to this:
If its matching on something else you can modify the hardware identifier (discovery definition > identifiers) to suit your local needs..
Also we do use manufacturer in the company table..its working as it should.. Unless its not meeting your process.. then that's a different story..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-04-2017 02:50 PM
Trisha,
You can look at the discovery status log for each scan and it will show you which identifier matched on the CI. You'll see a line similar to this:
If its matching on something else you can modify the hardware identifier (discovery definition > identifiers) to suit your local needs..
Also we do use manufacturer in the company table..its working as it should.. Unless its not meeting your process.. then that's a different story..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-20-2020 05:26 AM
Check out this video, it will clear all your doubts and help you to understand Discovery queries in details.
Link: https://www.youtube.com/watch?v=30JbWVsusyE&t=10s&ab_channel=ServiceNowHelpdesk
It help you to understand below points.
- Discovery Overview
- Discovery prerequisite
- Understanding Discovery Phases in details
- Discovery credentials and IP Affinity
- Mid Server Management with Cluster and Load Balancer
- Schedule jobs
- Set up discovery from scratch to end
- Live implementation with real world data.
- Troubleshooting on various aspects
- Many more other issue related to mid server, CIs
- Cloud discovery
- Service Mapping
Please mark reply as Helpful/Correct, if applicable. Thanks!!