Command Validation Tasks form for pattern-based discovery
Summarize
Summary of Command Validation Tasks form for pattern-based discovery
The Command Validation Tasks form in ServiceNow’s pattern-based discovery enables customers to create or modify tasks that test specific discovery pattern commands. This functionality helps ensure the accuracy and success of commands used during discovery processes, particularly when troubleshooting command execution failures.
Show less
Key Features
- Automatic Task Number: Each validation task is assigned a unique number automatically by the system.
- MID Server Selection Method: Choose how to select the MID Server for testing:
- Specific MID Server: Manually specify a MID Server.
- Automatic MID Selection: Use a MID Server assigned to the IP range or network configured for Discovery.
- Try All Eligible MID Servers: Attempt with any available MID Server for the IP range or network.
- MID Server Field: Appears when “Specific MID Server” is selected, allowing direct MID Server selection.
- Validate All Pattern Commands: Option to validate all commands associated with a pattern simultaneously, simplifying comprehensive testing.
- OS Class: Defines the CI class representing target servers for validation, ensuring commands are tested against appropriate server types.
- Command Type: Select the type of command to validate, supporting Shell Command, WMI Query, SNMP Query (Tabular/Scalar), SNMP Walk, or HTTP GET (with Basic Authentication).
- IP Addresses: Specify individual IP addresses, IP ranges, or IP networks (using slash notation) where the command validation will run. Requires the ParseIPRanges script include for range/network usage.
- Commands: Select specific commands to test, typically those that failed during discovery. This is available when not validating all pattern commands.
- Pattern: Specify the discovery pattern for which command validation is performed, also available when individual commands are selected.
Practical Use and Benefits
This form empowers ServiceNow customers to systematically validate discovery commands, improving diagnostic capabilities and reducing discovery failures. By specifying MID Servers, IP targets, and command types, customers can tailor validation tests precisely to their environment. The option to validate all commands simultaneously streamlines comprehensive checks, while individual command testing aids targeted troubleshooting. Proper use of IP range/network notation enhances flexibility in large-scale environments.
Command Validation Tasks form displays the fields that you must fill when you create or modify a task for testing a pattern command.
For more information about testing pattern commands, see Validate commands used in pattern-based discovery.
| Field | Description |
|---|---|
| Number | The task number is automatically created by the system. |
| MID Server Selection Method | Select the relevant method:
|
| MID Server | The MID Server name. This field appears only if Specific MID Server is selected from MID Server Selection Method. |
| Validate All Pattern Commands | The check box for validating all commands used by a specific pattern simultaneously. |
| OS Class | The CI class that represents the servers on which you run this validation task. |
| Command Type | The command type that depends on the kind of the server:
This field is available only when Validate Al Patterns Commands isn't selected. |
| IP Addresses | Any combination of IP v4 Addresses, IP Ranges, or IP networks. For example:
Note: To use IP range or IP network, ensure you have installed the ParseIPRanges script include. For more information, refer to KB1123625: Command Validation Tool. |
| Commands | The commands for which you want to test credentials. Typically, it's a command that discovery process failed to execute. For example, /api/v1/pods?limit=50 or sudo
dmidecode. You can select only commands from the list of available commands. This field is available only when Validate All Patterns Commands isn't selected. |
| Pattern | The name of the pattern for which you want to validate the commands. This field is available only when Validate All Patterns Commands isn't selected. |