Discovery multiprobes and multisensors

Multiprobes contain one or more simple probes configured to extract specific information from manageable devices by executing multiple queries with a single authentication.

You 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. Identity probes ask a device for information such as its name and serial number, and then use the results of those queries to update existing CIs in the CMDB.

To 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.

Remarque :

The corresponding multisensors have the same names as the multiprobes.

The following multiprobes are included with the base system.

Multiprobe	Includes These Probes
AIX - ADM	AIX - Active Processes: Gets active running processes. Unix - Active Connections: Gets active connections information.
AIX - Identity	AIX - Network: Determines network interfaces, IPs, and MACs. AIX - Serial Number: Gets AIX serial numbers.
CIM - Identity	CIM - Computer System: Gets CIM Computer Systems per SMI-S.
CIM - Identity - WBEM Service	CIM - CIMOM: Probes for the WBEM Service, CIMOM.
HP-UX - ADM	HP-UX - Active Processes: Gets active running processes. Unix - Active Connections: Gets active connections information.
HP-UX - Identity	HP-UX - Hardware Serial Number: Gets HP-UX serial numbers. HP-UX - Network: Determines network interfaces, IPs, and MACs.
Linux - Identity	Linux - Hardware Information: Gets DMI (BIOS) information. Linux - Network: Determines network interfaces, IPs, and MACs.
Mac OS X - Identity	Mac OS X - Network: Determines network interfaces, IPs, and MACs. Mac OS X - CPU/Memory: Gets CPU and memory information.
SNMP - A10 - Identity	SNMP - A10 - Identity - Serial: Part of the SNMP - Load Balancer - Identity multiprobe that is used to identify the A10 load balancer. SNMP - Identity Info: Identifies an SNMP device.
SNMP - ACE - Identity	SNMP - Identity Info: Identifies an SNMP device. SNMP - ACE - Identity - Serial: Part of the SNMP - Load Balancer - Identity multiprobe, that is used to identify the ACE load balancer
SNMP - Alteon - Identity	SNMP - Alteon - Identity - Serial: Part of the SNMP - Load Balancer - Identity multiprobe, that is used to identify the Alteon load balancer. SNMP - Identity Info: Identifies an SNMP device.
SNMP - AppDirector - Identity	SNMP - AppDirector - Identity - Serial: Part of the SNMP - Load Balancer - Identity multiprobe, that is used to identify the AppDirector load balancer. SNMP - Identity Info: Identifies an SNMP device.
SNMP - F5 BIG-IP - Identity	SNMP - F5 BIG-IP - Identity - Serial: Retrieves the BIG-IP chassis serial number, which is globally unique for this vendor. SNMP - Identity Info: Identifies an SNMP device.
SNMP - Identity	SNMP - Identity Info: Identifies printer CIs
SNMP - Load Balancer - Identity	SNMP - F5 BIG-IP - Identity - Serial: Gets BIG-IP chassis serial numbers, which are globally unique for this vendor SNMP - Identity Info: Identifies SNMP devices
SNMP - Netscaler - Identity	SNMP - Netscaler - Identity - Serial: Retrieves the Netscaler chassis serial number, which is globally unique for this vendor. SNMP - Identity Info: Identifies SNMP devices
Solaris - ADM	Solaris - Active Processes: Gets active running processes Unix - Active Connections: Gets active connections information
Solaris - Identity	Solaris - Network: Determines network interfaces, IPs, and MACs Solaris - Serial Number: Gets serial numbers for Solaris devices †
Unix - ADM	Unix - Active Processes: Gets active running processes Unix - Active Connections: Gets active connections information
UNIX - Classify	ESX - OS: Identifies ESX machines UNIX - OS: Runs after the ESX - OS probe to determine the operating system for SSH devices not identified as ESX
Windows - ADM	Windows - Active Processes: Gets active running processes Windows - Active Connections: Retrieves active connections information
Windows - Identity	Windows - Network: Determines network interfaces, IPs, and MACs Windows - OS/Hardware Information: Probes a Windows machine for WMI information
Windows - Storage 2008	Windows - Storage 2008 - PS: Retrieves disk and file system information for Windows 2008 and earlier. Windows - Storage 2008 - WMI: Retrieves disk and file system information for Windows 2008 and earlier.
Windows - Storage 2012	Windows - Storage 2012 - WMI: Retrieves disk and file system information for Windows 2012 and later. Windows - Storage 2012 - PS: Retrieves disk and file system information for Windows 2012 and later.

Remarque :

† 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. 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.

Add a simple probe to a multiprobe

You can add simple probes to your multiprobe in the Includes Probes related list.

Avant de commencer

Role required: admin

Pourquoi et quand exécuter cette tâche

You can add simple probes of any type to a multiprobe and mix probe types if necessary.

Avertissement :

Do not add a multiprobe to the Includes Probes related list.

Procédure

1. Navigate to All > Discovery Definitions > Probes.
2. Open a multiprobe from the list.
   You can see the MultiProbe designation in the ECC queue topic column.

   Figure 1. Linux identity multiprobe

   

3. In the MultiProbe record, click New in the Includes probes related list.
4. Select a simple probe from the collection list in the left column and move it into the included list..

   Figure 2. Adding a simple probe to a multiprobe

   

5. Click Save.

Create a Discovery multiprobe

You can use the default multiprobes and multisensors provided in the platform or create your own.

Avant de commencer

Role required: admin

Procédure

1. Navigate to All > Discovery > Discovery Definition > Probes.
2. Click New.
3. Complete the form using the following settings:
   • Probe type: Multiprobe.
   • ECC queue topic: MultiProbe.
4. In the Includes probes related list, add the probes you want to include in the multiprobe.
5. Click Save.

Create a Discovery multisensor

Create a multiensor to process data returned from a multiprobe.

Avant de commencer

Role required: admin

Pourquoi et quand exécuter cette tâche

Figure 3. Discovery Multisensor and Script

Procédure

1. Navigate to All > Discovery > Discovery Definition > Sensors.
2. Click New.
3. Complete the form using the following settings:
   • Sensor type: MultiSensor.
   • ECC queue topic: MultiSensor.
   • Reacts to probe: Select the probe whose payload this sensor must process.
   • Sensor type: Select one of these options.
     • 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.
     • 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.
4. Right-click the form header, and click Save.
5. In the Responds to Probes related list, click New.
6. Complete the form using the following settings:
   • 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.
   • 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.
7. Click Save.