How to find out if a device/software/service is discovered by DiscoveryIssue Discovery probes devices using popular and standard management interfaces and so most devices can be Discovered. If your are not sure if a specific device can be discovered, then please use these steps. What you need to know about your device: Manufacturer (e.g. Cisco)Product family and sub-family (e.g. Nexus 2000, Cisco Nexus 2200 Platform with Cisco FET, for Cisco Nexus 5000, 6000, or 7000 Series Switch)Model Name/Number (e.g. N2K-C2248TF-E)Know what type of device this is (e.g. Fabric Extender unit for a Stacked IP Network Switch)Know which management interfaces the device has (e.g. SNMP and a SSH based CLI via the main Switch unit) Don't waste your time testing on an old version. You should try to be on the latest instance major version and patch if possible, and definitely upgrade the following out-of-band applications to the current version because most device-specific discovery code and enhancements are now in these additional apps rather than the main plugins. Most latest app version will also install on N-1 or N-2 instance versions: Discovery and Service Mapping PatternsVisibility ContentCMDB CI Class ModelsExpanded Model and Asset Classes If using ACC: Agent Client Collector for VisibilityAgent Client Collector for Visibility Content And while you are updating apps anyway... Pattern Designer Enhancements Certificate Inventory and Management CMDB and CSDM Data Foundations DashboardsFirewall Audits and ReportingDiscovery Admin WorkspaceService Operations Workspace ITOM AppsCloud Discovery WorkspaceConfiguration Management For Scoped Apps (CMDB) You can list all store apps, filtered by ITOM, Discovery etc. on the ServiceNow Store.ReleaseCurrentResolution Table of Contents Discover the Device IPSearch public ServiceNow sites for the specific manufacturer, family, sub-family, name or part numberNavigate the documentation for the general device type Computer and server discoveryNetwork device discoveryStorage discoverySoftware discovery and Database discoveryCloud discovery Tech Support Case Discover the Device IP Try it and see. Add the correct credentials for accessing the device to the instance, and then run a Quick Discovery of the IP address. Does the Shazzam probe see ports open for any of the standard management interfaces?Does a Classify probe get launched?Does an Identity probe or Pattern then get launched, and cause a Discovery Device History record to be created?Does a CI get created, linked from the Discovery Device History record? If the device does not appear to be active to the Shazzam port probes, with no ports open, then the Device may not be discover-able. However the device may not be set up correctly for remote management, or may be blocked by a firewall, which you'd need to resolve. Assuming there are no authentication errors, and the device is active, but the device is not Classified, then it probably is not supported. If the device is classified, and classified correctly for the table that this type of device should be saved in, then it is probably supported at least for basic attributes. Any errors during Identification may be due to credentials or configuration issues. If a CI gets created, does it contain all the attributes you were expecting? Search public ServiceNow sites for the specific manufacturer, family, sub-family, name or part number Support for a particular manufacturer/vendor is is likely cover a whole family of similar products, so don't expect specific part numbers to be found. Search for the product vendor and family/series names. HI Portal - Knowledge Base - The Support and Troubleshooting knowledge base has a lot of device-specific information, for supported and unsupported devices, and known challenges with discovering them.Community Posts - Will include discussions on device support, problems with specific devices, and possible customizations to add support yourself.Idea Portal - This will confirm things that are not yet supported.App Store - New Discovery support is tending to be added as Store Apps now, meaning additional devices can be added between releases, and to older releases. Navigate the documentation for the general device type Summary page of what is discovered (not necessarily up to date - check specific pages for more accurate info on versions etc.):Detailed information on products discovered by ITOM Visibility Https://docs.servicenow.com/bundle/rome-it-operations-management/page/product/service-mapping/reference/r_SupportedApplications.html If you can't find anything specific to your device model, then it is probably still supported. Discovery uses industry standard remote management protocols for most discovery, and those tend to be implemented in a similar way for each device type, regardless of the vendor. The landing pages in the documentation for Discovery are: ITOM Visibility - Discovery, and for what is discovered see Data collected by Discovery. The List of Discovery Probes and Available discovery patterns list the probes and patterns that exist for general types, and some specific vendors. Within those pages you have links to specific to types of device/software/service. Click the headers below for those pages: Computer and server discovery The manufacturer and Model are not particularly relevant for PC based hardware, as they are now very standardized. Focus on the Operating System and version when checking if a server will be supported. Linux is just the kernel and it is the specific Operating System/Distribution which adds all the other commands and daemons that Discovery needs to use, and so if your particular Linux distribution and version is not listed, then you can check the lists of SSH commands for Discovery to be sure they are present. Assume any documentation applies only to Intel x86 (32 and 64 bit) CPU architecture, unless specifically stated. Don't assume IA64, ARM, MIPS, Sparc, AS/400, Power etc. are supported. Embedded devices, running real-time or embedded versions of Windows/Linux operating systems should not be thought of as Computers. Those don't tend to include the normal server management technologies, and which particular embedded RTOS was used in the design is irrelevant. Network device discovery From your device documentation, confirm that SNMP is implemented, and see which standard MIBs are included, and if there are any special Vendor MIBs or special REST APIs or Command Line Interfaces (CLI). Any data in Vendor MIBs will need vendor specific code in the probes/patterns and that should be documented. The standard probes/patterns will usually be able to discovery enough attributes for identification and classification, even if the vendor MIBs are not supported. Devices that don't support SNMP can usually be discovered if you create an HTTP Classifier, but we don't include many of those out-of-box due to the performance impact this has on Shazzam. Doug's community post is a good place to start:Community: Create a simple SNMP Classifier. The patterns edition Storage discovery You need to know what SMI-S/CIM Servers you have running in your environment. These are vendor-specific for a particular interop namespace, and are usually installed on separate Servers due to the ports conflicting, but are still standards based. Discovery of Storage is done by querying those SMI-S servers, not directly to the devices, so as long as you are discovering the IP of the server running the SMI-S server, and that server is tracking the Storage systems you want to discover, then it should be discover-able. Software discovery and Database discovery Process Classification is the normal way to discover Software services, which requires that the software is running at the time. Applicative Credentials are usually required, in addition to the credential used for Host discovery. If a Process Classifier exists for a particular piece of software, then a CI will be created. If a probe or pattern exists for that, to discover further information on it, then that will be in the documentation as well. If you don't see your specific software mentioned in the documentation, then although an application CI can easily be discovered by Creating a Discovery Process Classification, there will probably be no additional code for attributes specific to that software unless you write a probe or pattern yourself. Most of the Available discovery patterns are for specific software. Application Clusters may not be supported even if the standalone application is. If we do support this it will be documented. Cloud discovery If the Cloud provider is not listed, then discovery of the cloud resources is not currently supported. Tech Support Case Once you have done the above, and the device still isn't getting fully discovered, then you might consider opening a Support Case. Free technical support does cover break/fix situations with our out-of-box code, and if you have reason to believe the existing documented probes/patterns should work with your device, then we'll be happy to help. Support would require the usual details, instance access, test examples and results, in order to investigate why the device is not discovered. Please do not open Cases with support with lists, asking for us to research the devices for you. That would be considered part of the planning of a discovery implementation, and help with that would usually be provided by professional services, or an implementation partner. We are interested in feedback related to device support, and the place to do that is up-voting and commenting on existing enhancement requests in the Ideas Portal, or create a new Idea for the device you want adding.