Please use docs.servicenow.com for the latest documentation.
This site is for reference purposes only and may not be accurate for the latest ServiceNow version
| Note: This article applies to Fuji and earlier releases. For more current information, see Discovery Behaviors at http://docs.servicenow.com
The ServiceNow Wiki is no longer being updated. Visit http://docs.servicenow.com for the latest product documentation.
A Discovery Behavior determines what probes Shazzam launches and from which MID Servers these probes are launched. Unlike a scan in which a single MID Server that performs all protocol scans on a designated IP address range, network, or list, a behavior can assign different tasks to multiple MID Servers on the same IP address segment or on different network segments. Behaviors are available in Discovery Schedules for discoveries in which configuration items (CI) are updated in the CMDB.
Behaviors can be used in the following scenarios:
- Load balancing: A behavior enables load balancing in systems that use multiple MID Servers deployed across one or more domains.
- Multiple protocols in multiple domains: Configure one MID Server to scan for all protocols on one domain and another MID Server to perform a WMI scan on a second domain.
- Access Control Lists (ACL): Discovery can scan SNMP devices protected by an ACL if the MID Server host machine is granted access by that ACL. Use a behavior to configure a MID Server to scan devices protected by an ACL.
- Devices running two protocols: Some devices might have two protocols running at the same time. Examples of this are the SSH and SNMP protocols running concurrently on one device (most common). A behavior can control which of the two protocols is explored for certain devices. The behavior then prevents the other protocol from being explored.
Creating a Behavior
To create a behavior, navigate to Discovery Definition > Behavior' and click New. The Behavior form provides the following unique fields:
|Name||Type a unique name that describes the use for this behavior, such as Two Domains or Load Balance.|
|Discovery Functionality||Select the MID Servers to use for this behavior, the desired execution phase, and the pre-configured functionality for each MID Server (protocols to scan).|
The completed Discovery Behavior form looks like this:
Discovery Functionality defines what each MID Server in this behavior must do, specifically which protocols to detect. This form provides the following unique fields:
|Phase||A phase is an arbitrary integer used to group one or more functionalities together. All the functionalities within a phase are executed together, and all phases are executed in numerical order. All functionalities in a behavior can have the same phase. The Shazzam probe runs once for each phase in a behavior, which makes fewer phases desirable. Run multiple phases for behaviors only when devices in the network are running multiple protocols (e.g. SSH and SNMP). In this example, set one phase for the SSH scan and another phase for the SNMP scan.|
|Functionality||Select a pre-configured functionality that defines the protocol or list of protocols that each MID Server will scan. Access the Functionality Definition records through the Functionality link in the Discovery Behavior form or by navigating to Discovery Definitions > Functionality Definition.|
|MID Servers|| Select one or more MID Servers to perform this functionality for the following Discovery types:
Discovery automatically balances the load when multiple MID Servers are selected.
|Functionality Criteria|| Define criteria here for Windows MID Servers. See the following section for details.|
Functionality Criteria are required for Windows MID Servers only, and only when the behavior controls Discovery across multiple domains. When the instance launches the Shazzam probe for a Discovery in which a behavior defines multiple MID Servers to scan multiple domains, the Functionality Criteria determine which MID Server will process the results of the probe.
The form provides the following unique fields:
The name in the criteria is the variable that passes the following information:
|Value||Enter the actual name of the MID Server (mid_server) or domain (win_domain) to pass to Discovery for this criteria. This field can also have a value of mid_domain, which defines the Windows domain of the MID Server that is processing the Shazzam results.|
The completed criteria form looks like this: