{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":29722,"path":"it-operations-management/discovery/r_MultiprobesIncludedWithDiscovery.md","title":"Discovery multiprobes and multisensors","bundle":null,"doc_type":null,"release":"australia","body":"\n# Discovery multiprobes and multisensors\n\nMultiprobes contain one or more simple probes configured to extract specific information from manageable devices by executing multiple queries with a single authentication.\n\nYou can schedule multiprobes to run any time in the discovery process to make exploration more efficient. One common use for multiprobes is as [identity probes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/c_HowDiscoveryIdentifiersWork.md). Identity probes ask a device for information such as its name and serial number. The results of those queries update existing CIs in the CMDB.\n\nTo process the data returned from a multiprobe, you must create multisensors, which run scripts that process the data returned by the multiprobes. Multisensors typically use the same name as their corresponding multiprobes.\n\n**Note:** The corresponding multisensors have the same names as the multiprobes.\n\nThe following multiprobes are included with the base system.\n\n\n
\n\nMultiprobe\n\n\n\nIncludes These Probes\n\n
\n\nAIX - ADM\n\n\n\n- AIX - Active Processes: Gets active running processes.\n- Unix - Active Connections: Gets active connections information.\n\n
\n\nAIX - Identity\n\n\n\n- AIX - Network: Determines network interfaces, IPs, and MACs.\n- AIX - Serial Number: Gets AIX serial numbers.\n\n
\n\nCIM - Identity\n\n\n\nCIM - Computer System: Gets CIM Computer Systems per SMI-S.\n\n
\n\nCIM - Identity - WBEM Service\n\n\n\nCIM - CIMOM: Probes for the WBEM Service, CIMOM.\n\n
\n\nHP-UX - ADM\n\n\n\n- HP-UX - Active Processes: Gets active running processes.\n- Unix - Active Connections: Gets active connections information.\n\n
\n\nHP-UX - Identity\n\n\n\n- HP-UX - Hardware Serial Number: Gets HP-UX serial numbers.\n- HP-UX - Network: Determines network interfaces, IPs, and MACs.\n\n
\n\nLinux - Identity\n\n\n\n- Linux - Hardware Information: Gets DMI \\(BIOS\\) information.\n- Linux - Network: Determines network interfaces, IPs, and MACs.\n\n
\n\nMac OS X - Identity\n\n\n\n- Mac OS X - Network: Determines network interfaces, IPs, and MACs.\n- Mac OS X - CPU/Memory: Gets CPU and memory information.\n\n
\n\nSNMP - A10 - Identity\n\n\n\n- SNMP - A10 - Identity - Serial: Part of the SNMP - Load Balancer - Identity multiprobe that is used to identify the A10 load balancer.\n- SNMP - Identity Info: Identifies an SNMP device.\n\n
\n\nSNMP - ACE - Identity\n\n\n\n- SNMP - Identity Info: Identifies an SNMP device.\n- SNMP - ACE - Identity - Serial: Part of the SNMP - Load Balancer - Identity multiprobe, that is used to identify the ACE load balancer\n\n
\n\nSNMP - Alteon - Identity\n\n\n\n- SNMP - Alteon - Identity - Serial: Part of the SNMP - Load Balancer - Identity multiprobe, that is used to identify the Alteon load balancer.\n- SNMP - Identity Info: Identifies an SNMP device.\n\n
\n\nSNMP - AppDirector - Identity\n\n\n\n- SNMP - AppDirector - Identity - Serial: Part of the SNMP - Load Balancer - Identity multiprobe, that is used to identify the AppDirector load balancer.\n- SNMP - Identity Info: Identifies an SNMP device.\n\n
\n\nSNMP - F5 BIG-IP - Identity\n\n\n\n- SNMP - F5 BIG-IP - Identity - Serial: Retrieves the BIG-IP chassis serial number, which is globally unique for this vendor.\n- SNMP - Identity Info: Identifies an SNMP device.\n\n
\n\nSNMP - Identity\n\n\n\nSNMP - Identity Info: Identifies printer CIs\n\n
\n\nSNMP - Load Balancer - Identity\n\n\n\n- SNMP - F5 BIG-IP - Identity - Serial: Gets BIG-IP chassis serial numbers, which are globally unique for this vendor\n- SNMP - Identity Info: Identifies SNMP devices\n\n
\n\nSNMP - Netscaler - Identity\n\n\n\n- SNMP - Netscaler - Identity - Serial: Retrieves the Netscaler chassis serial number, which is globally unique for this vendor.\n- SNMP - Identity Info: Identifies SNMP devices\n\n
\n\nSolaris - ADM\n\n\n\n- Solaris - Active Processes: Gets active running processes\n- Unix - Active Connections: Gets active connections information\n\n
\n\nSolaris - Identity\n\n\n\n- Solaris - Network: Determines network interfaces, IPs, and MACs\n- Solaris - Serial Number: Gets serial numbers for Solaris devices †\n\n
\n\nUnix - ADM\n\n\n\n- Unix - Active Processes: Gets active running processes\n- Unix - Active Connections: Gets active connections information\n\n
\n\nUNIX - Classify\n\n\n\n- ESX - OS: Identifies ESX machines\n- UNIX - OS: Runs after the ESX - OS probe to determine the operating system for SSH devices not identified as ESX\n\n
\n\nWindows - ADM\n\n\n\n- Windows - Active Processes: Gets active running processes\n- Windows - Active Connections: Retrieves active connections information\n\n
\n\nWindows - Identity\n\n\n\n- Windows - Network: Determines network interfaces, IPs, and MACs\n- Windows - OS/Hardware Information: Probes a Windows machine for WMI information\n\n
\n\nWindows - Storage 2008\n\n\n\n- Windows - Storage 2008 - PS: Retrieves disk and file system information for Windows 2008 and earlier.\n- Windows - Storage 2008 - WMI: Retrieves disk and file system information for Windows 2008 and earlier.\n\n
\n\nWindows - Storage 2012\n\n\n\n- Windows - Storage 2012 - WMI: Retrieves disk and file system information for Windows 2012 and later.\n- Windows - Storage 2012 - PS: Retrieves disk and file system information for Windows 2012 and later.\n\n
**Note:** † This probe requires the installation of a command line tool from Oracle called SNEEP. To download and install this tool, log in to the [Oracle website](https://docs.oracle.com/cd/E35557_01/doc.81/e35226/ch3_sneep.htm). After this tool is installed, the **Solaris - Serial Number** probe runs automatically when Discovery detects a Solaris device. For Fujitsu PRIMEPOWER devices, you must run this probe with root credentials.\n\n**Parent Topic:**[Discovery probes and sensors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/c_DiscoveryProbesAndSensors.md)\n\n## Add a simple probe to a multiprobe\n\nYou can add simple probes to your multiprobe in the Includes Probes related list.\n\n### Before you begin\n\nRole required: admin\n\n### About this task\n\nYou can add simple probes of any type to a multiprobe and mix probe types if necessary.\n\n**Warning:** Do not add a multiprobe to the Includes Probes related list.\n\n### Procedure\n\n1. Navigate to **All** > **Discovery Definitions** > **Probes**.\n\n2. Open a multiprobe from the list.\n\n You can see the MultiProbe designation in the **ECC queue topic** column.\n\n \\[Omitted image \"LinuxMultiProbe.png\"\\] Alt text: Linux identity multiprobe form\n\n3. In the MultiProbe record, click **New** in the **Includes probes** related list.\n\n4. Select a simple probe from the collection list in the left column and move it into the included list..\n\n \\[Omitted image \"AddSimpleProbe.png\"\\] Alt text: Adding a simple probe to a multiprobe\n\n5. Click **Save**.\n\n\n## Create a Discovery multiprobe\n\nYou can use the default multiprobes and multisensors provided in the platform or create your own.\n\n### Before you begin\n\nRole required: admin\n\n### Procedure\n\n1. Navigate to **All** > **Discovery** > **Discovery Definition** > **Probes**.\n\n2. Click **New**.\n\n3. Complete the [form](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/r_Probes.md) using the following settings:\n\n - Probe type: Multiprobe.\n - ECC queue topic: MultiProbe.\n4. In the Includes probes related list, [add the probes](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/r_MultiprobesIncludedWithDiscovery.md) you want to include in the multiprobe.\n\n5. Click **Save**.\n\n\n## Create a Discovery multisensor\n\nCreate a multiensor to process data returned from a multiprobe.\n\n### Before you begin\n\nRole required: admin\n\n### About this task\n\n\\[Omitted image \"DiscoveryMultisensorAndScript.png\"\\] Alt text: Discovery Multisensor and Script\n\n### Procedure\n\n1. Navigate to **All** > **Discovery** > **Discovery Definition** > **Sensors**.\n\n2. Click **New**.\n\n3. Complete the form using the following settings:\n\n - Sensor type: MultiSensor.\n - ECC queue topic: MultiSensor.\n - Reacts to probe: Select the probe whose payload this sensor must process.\n - Sensor type: Select one of these options.\n - Javascript: Returned data from the probe is processed in the sensor itself, outside the application, and is visible to the user. This is the most common sensor type.\n - XML: The XML data from the probe is broken into pieces. Some pieces can be used to launch other probes that the original sensor needs to complete all the necessary information about a device.\n4. Right-click the form header, and click **Save**.\n\n5. In the Responds to Probes related list, click **New**.\n\n6. Complete the form using the following settings:\n\n - Reacts to probe: Select the probe within the multiprobe that this sensor reacts to. The sensor must be linked to the probe by function, such as network identification or serial number.\n - Script: Enter a script to run before the script in the multisensor. This script defines how the data returned from each probe should be processed.\n7. Click **Save**.\n\n\n"}}