--- title: "SAN Jobs" slug: "san-jobs" status: "update" updated: 2026-11-13T10:10:11Z published: 2026-11-13T10:10:11Z canonical: "help.symphonysummitai.com/san-jobs" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # SAN Jobs Storage / SAN discovery identifies storage infrastructure through SNMP. It covers storage area network (SAN) arrays, network-attached storage (NAS) filers, and Fibre Channel (FC) fabric switches. The vendors shown include NetApp, Pure, Dell EMC, HPE, IBM, and Brocade. The information available depends on the device’s SNMP support and configuration. Use this job type to include storage infrastructure in your discovery inventory. **Example:** A storage administrator creates a Storage / SAN discovery job for approved storage arrays and Fibre Channel switches, using credentials that permit SNMP access. To create a new job for Storage Area Network (SAN) devices, perform the following steps: 1. Click **Workspace > ITAM > Asset > Discovery > Discovery Jobs**. The Discovery Jobs list page is displayed. 2. Click **New Job**. 3. On New Job, select the job type that matches your discovery source. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/discovery_jobs-image-1d9biwvy.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=KnhwIo9fBxhbnxCTyXK5OQVOoMHZJa483DRW2uIrWOQ%3D) Figure: New Job | **Job type** | **Purpose shown on the selection screen** | | --- | --- | | Network | Discover Windows through WMI, Linux through SSH, and network devices through SNMP. | | Cloud | Enumerate virtual machines and resources across AWS, Azure, GCP, and Oracle Cloud. | | Container | Discover Docker containers and Kubernetes resources. | | Hypervisor | Discover guest VMs through virtualization platforms. | | Database | Connect to database engines to discover instances and inventory. | | Directory | Discover Active Directory information without an agent. | | Storage / SAN | Discover storage systems through supported platform interfaces. | 4. Select Storage/SAN on the new job. 5. On **Identity**, select the tenant and enter a descriptive job name. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-JW6NR97D.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=u7Qu17JyiTqOIydQWUKxzCxdUBVHhioZPCD0UpDJY1Y%3D) Figure: Identity | **Field name** | **Description** | | --- | --- | | Tenant * | Tenant context associated with the job. The demonstration displays Information Technology. | | Job Name * | Name used to identify the job in the jobs list and run details. Example: HQ Windows Inventory. | | Status | Activation state selected for the job. The demonstration shows Active. | | Description (optional) | Purpose, scope notes, ownership, or other context for the team. | | Next | Continues to the next wizard stage. | | Cancel | Leaves the wizard. Confirm any save or discard behavior presented by the application. | 6. Click **Next** to open Scope. 7. On Scope & Exclusions, choose the scope type. 8. Enter the corresponding addresses. For a subnet scan, enter its CIDR block. 9. Add addresses, ranges, CIDRs, or hosts to exclude, one entry per line where the control is available. 10. Review the target boundaries and click **Next**. For a branch subnet, select CIDR Subnet and enter 192.168.50.0/24. Exclude any management or sensitive targets that the network team has removed from the approved scan list. First test the worker and credentials against one representative host. 1. Configure an address range. 1. Select IP Range (start - end). 2. Enter Start IP and End IP, for example 192.168.50.10 and 192.168.50.40. 3. Review any exclusions, and continue to Type. 2. Configure a host list. 1. Select IP List (multiple). 2. Enter the approved addresses or hostnames, one per line or separated by commas. 3. Check spelling, DNS resolution where applicable, and the completeness of the list. 4. Click **Next**. Use a single host during initial validation. Expand to a list, range, or subnet only after checking that the selected worker can collect the expected data. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-FXQHQMRF.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=D59fGdsGz3yPrD7SlD6TbXBoBjmpRg7sAtXYJ7CWbV0%3D) Figure: Scope and exclusions | **Field name** | **Description** | | --- | --- | | Scope Type | Selects Single Host / IP, IP Range (start - end), CIDR Subnet, or IP List (multiple). | | CIDR Block * | Subnet address and prefix for CIDR Subnet. Example: 192.168.50.0/24. Confirm the resulting range before scanning. | | Start IP * / End IP * | Beginning and ending addresses for IP Range (start - end). | | Exclude IPs / ranges / CIDRs / hosts (one per line) | Targets to skip within the scan scope. The UI states that excluded targets are never probed, even when they fall inside the scope. | 11. The **Type & Credentials** step lets you select the discovery method and associate credentials with the Storage / SAN discovery job. 1. For each selected method, add a stored credential. Use quick creation if a suitable credential is not yet available. 2. Use the up and down controls to arrange the displayed execution order. 3. Review the methods and selected credentials, then click **Next**. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-EZ4NZ98S.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=II1UZsMX7P1CuLkHC%2BUC0kh4u1EkUNA%2Be75AnnV8GSU%3D) Figure: SNMP Credentials | **Field or control** | **Description** | | --- | --- | | SNMP | Select Simple Network Management Protocol (SNMP) to discover storage devices within the configured scope. | | Execution Order & Credentials | Displays the selected discovery methods in execution order and the credentials associated with each method. | | Execution order number (1) | Indicates the sequence in which the discovery method runs. The method numbered **1** runs first. | | Add SNMP credential | Select an available SNMP credential for the discovery job. Credentials must belong to the same tenant as the job. | | Move up / Move down | Change the execution order when multiple discovery methods are configured. | | Remove (×) | Remove the discovery method from the job configuration. | | Quick-create SNMP credential | Create an SNMP credential to use with the discovery job. | | Manage credentials | Open credential management to add or maintain credentials for the selected tenant. | | Previous | Return to the **Scope** step. | | Next | Continue to the **Settings** step. | | Cancel | Cancel the discovery job configuration. | 12. Create SNMP Credential 1. Enter the credential name, SNMP version, and port. 2. Click **Create & Add**. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-JU2TM1WP.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=hoLIBLxA4T1p6IXUcRtk6o5ngoBKhTwamw56YGz3KdA%3D) Figure: Create Nutanix credential | **Field Name** | **Description** | | --- | --- | | Credential Name * | Enter a descriptive name to identify the credential. For example, **Storage SAN SNMP Credential**. | | SNMP Version | Select the SNMP version configured on the target devices. | | Port* | Enter the SNMP port used to communicate with the target devices. The default value shown is **161**. | | Community String | Enter the community string configured on the target device to allow SNMPv1 or SNMPv2c access during discovery. The value is case-sensitive and must match the device configuration. | | Create & Add * | Create the credential and add it to the discovery job. | | Cancel | Close the dialog without creating the credential. | 13. Credential Selection Guidance 1. Select an SNMP credential that matches the version and authentication settings configured on the target storage devices. If no matching credential is available, use **Quick-create SNMP credential** or **Manage credentials** to add one for the same tenant. 14. The **Settings** step lets you control how long Discovery Jobs run and how SNMP requests are handled. Configure per-host and overall job time limits, SNMP response timeouts, retry attempts, and version preference to suit your environment. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-OLQWM2U4.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=CJtYunoT1o831q%2Bd%2FR1RI7RYtbLgfHePclqjBjF%2F%2BdA%3D) Figure: Settings | Collection depth | Field Name | **Description** | | --- | --- | | Timeout per host(s) | Enter the maximum time, in seconds, allowed to discover each host. The default is **180 seconds**. Set to **0** for no per-host time limit. The overall job timeout still applies. | | Job Timeout (hours) | Sets the overall execution limit for the discovery workflow. The displayed value is **24 hours**, which the screen identifies as the minimum. | | SNMP Timeout | Enter how long to wait, in seconds, for a response to each SNMP request. This value overrides the timeout configured in the credential. The value shown is **5 seconds**, and the maximum is **60 seconds**. | | SNMP Retries | Enter the number of retry attempts for an SNMP request that does not receive a response. Set to **0** to disable retries. The value shown is **1**. | | Version Preference | Select which SNMP version to try first during discovery. The current selection is **Auto-detect**. | 15. **Knocking**: Performs an initial ping or TCP check before attempting detailed discovery through WMI, SSH, or SNMP. The controls for this section are not fully visible in the screenshot. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-7DDJ1PB6.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=Cq2D%2BTdEf%2FR%2BBb1FPr%2BJRcGOb9Of9tGTeYHp5xc4ch4%3D) Figure: Configure Knocking settings | Field Name | Description | | --- | --- | | Pre-flight Ping | Enable to check host reachability before detailed discovery. Hosts that do not respond to the selected ping protocol are skipped. | | Ping Only | Enable to check host reachability without collecting device information through discovery protocols. | | Ping Protocol | Select the protocol used for reachability checks: ICMP, TCP, or UDP. The default is **ICMP**. | | Knock concurrency | Enter the number of reachability checks to run simultaneously. Set to **0** for automatic concurrency (**500** checks). The maximum is **2,000**. | | Rate limit (req/s) | Enter the maximum number of SNMP/WMI requests allowed per second to control the request load on managed devices. Set to **0** for unlimited requests. | | Pre-scan Port Detection | Enable to probe TCP port **135** for WMI, TCP port **22** for SSH, and UDP port **161** for SNMP before attempting discovery. Protocols whose ports are detected as closed are skipped. | | Coverage Score | Enable to calculate a score for each device that indicates which parameters were collected and why others were not collected. | | CVE Corelation | Enable to match discovered software against Common Vulnerabilities and Exposures (CVE) records in the National Vulnerability Database (NVD). Requires an **NVD API key**. | | Capture Engine Logs | Enable to save detailed discovery engine logs for each run to support troubleshooting. This increases storage usage. | | Capture Per-Host Result | Enable to save detailed results for each host by IP address. Disable to reduce storage usage. | | Next | Click Next to configure the Schedule of the Job. | 16. Click **Next**. 17. Execution and Scheduling: The **Schedule** step lets you define when the discovery job starts, how often it repeats, and when the recurring schedule ends. 1. Select the effective task queue and if you want to schedule it, enable the **Enable Schedule Runs** toggle button. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-J071E7PE.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=uKdAV2sr%2FgpnwClGkDi2eMUgHJsaXupfXYop84YA05U%3D) Figure: Scheduling and Execution | Field Name | Description | | --- | --- | | Effective task queue | Displays the selected worker’s task queue used to execute scheduled runs and **Run Now** requests. | | Enable scheduled runs | Enable to run the discovery job automatically according to the configured schedule. | | Repeat Job | Select to repeat the discovery job at the specified interval. | | Recurrence Type | Select how frequently the job repeats. The selection shown is **Daily**. | | Recurs Every | Enter the interval between recurring runs. For example, **1** with **Daily** runs the job every day. | | End Condition | Select when the recurring schedule ends. Select **No end** to continue recurring runs without an end date. | | Start Date* | Specify the date and time when the schedule begins. The value is displayed in your time zone and stored in Coordinated Universal Time (UTC). | | Previous | Return to the **Settings** step. | | Cancel | Cancel the discovery job configuration. | | Create Job | Create the discovery job using the configured scope, credentials, settings, and schedule. | 18. Once you click **Scan and Run Now**, you will get a message mentioning Job started. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-CCY8BAYC.png?sv=2026-02-06&spr=https&st=2026-11-20T22%3A17%3A58Z&se=2026-11-20T23%3A17%3A58Z&sr=b&sp=r&sig=elHLWtvYKt9UpjS%2BSgY%2B1Z3Pgvq%2FD6XFbCKbmqFKhH8%3D) Figure: Job saved successfully