---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management
Release :
- australia
ft:locale :
- de-DE
ft:publication_title :
- Australia IT Operations Management
ft:clusterId :
- itom
bundleId :
- itom
workflow :
- Technology
---
# NetApp SolidFire storage system
# NetApp SolidFire storage system discovery {#ariaid-title1}
* Freigeben Version: Australia
*
* Aktualisiert 12. März 2026
*
*  3 Minuten Lesedauer
ServiceNow
Discovery uses the NetApp SolidFire storage system discovery pattern to find clusters and nodes on the SolidFire storage system. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.
## Request apps on the Store {#solidfire-storage-pattern__section_sv2_vw5_5mb}
Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://docs.servicenow.com/bundle/store-release-notes/page/release-notes/store/sn-store-release-notes.html).{#solidfire-storage-pattern__inline-send-to-store}
## Prerequisites {#solidfire-storage-pattern__section_ggd_n4p_54b}
Discovery and Service Mapping Patterns store app
: Verify the Discovery and Service Mapping Patterns store app (version 1.0.74) is
installed.
Basic Auth permissions
: Ensure Basic Auth credentials are configured for authenticating the Element API
calls. Save the following SolidFire Cluster Admin credentials as Basic Auth
credentials to ensure proper access:
* read
* clusterAdmins
* reporting
* drives
{#solidfire-storage-pattern__ul_fhr_gzs_k4b}
MID server
: Ensure the MID server can access the target device.
Discovery credentials
: Ensure you have the credentials for running Discovery on the host
machine running the SolidFire storage system.
Create a serverless discovery schedule
: Create a discovery schedule to perform targeted discovery of SolidFire clusters and
nodes.
1. Navigate to DiscoveryDiscovery Schedules.
2. Click New and then fill in the form.
{#solidfire-storage-pattern__table_tt1_3z5_54b__entry__2}
| Field | Description |
|-|-|
| Name | Name for the Discovery schedule. For example, Discover SolidFire. |
| Discover | Discover type. Select Serverless. |
| MID Server | Name of the MID Server. |
| Active | Option for enabling this schedule for discovery. Select this check box to enable discovery. |
[Tabelle : 1. Discovery Schedule form]
{#solidfire-storage-pattern__table_tt1_3z5_54b}
3. Right-click the header of the Discovery Schedule form and select Save.
4. Click the Serverless Execution Patterns tab, click New, and then fill in the form.
{#solidfire-storage-pattern__table_vt1_3z5_54b__entry__2}
| Field | Description |
|-|-|
| Name | Name for this Serverless Execution Pattern. For example, SolidFire Storage Pattern. |
| Pattern | Name of the pattern to run: NetApp SolidFire Storage System. |
| Proxy Host | Fully qualified domain name of the machine on which you are installing the proxy server. Specify Global. |
| Active | Option for enabling this schedule for discovery. Select this check box to enable discovery. |
[Tabelle : 2. Serverless Execution Pattern form]
{#solidfire-storage-pattern__table_vt1_3z5_54b}
5. Under Discovery Pattern Launcher Parameters, configure the launch parameters with the relevant values. Ensure the Management IP of the cluster and Credentials Alias are defined.
{#solidfire-storage-pattern__ol_st1_3z5_54b}
## Data collected by Discovery during horizontal discovery {#solidfire-storage-pattern__section_sfd_j1v_54b}
The discovered SolidFire configuration data includes the following tables and fields.{#solidfire-storage-pattern__table_w2j_l53_2nb__entry__2}
| Table and field | Description |
|-|-|
| Main Configuration Item \[cmdb_ci_storage_server\] ||
| name | The name of the CI. |
| serial_number | The serial number associated with the CI. |
| firmware_version | The firmware version of the CI. |
| ip_address | The IP address of the CI. |
| short_description | A short textual description of the CI. |
| manufacturer | The device manufacturer. |
| model_id | The device model ID. |
| os_version | The version of the OS running on the CI. |
| os | The OS running on the CI. |
| Storage cluster \[cmdb_ci_storage_cluster\] ||
| ip_address | The IP address of the storage cluster. |
| manufacturer | The device manufacturer. |
| short_description | A short textual description of the CI. |
| cluster_version | Element OS API version running on the cluster. |
| name | The name of the CI. |
| Storage cluster node \[cmdb_ci_storage_cluster_node\] ||
| name | The name of the CI. |
| operational_status | Indicates if the device is in active state. |
| cluster | Reference for the cluster CI. |
| Storage node element \[cmdb_ci_storage_node_element\] ||
| short_description | A short textual description of the CI. |
| manufacturer | The device manufacturer. |
| serial_number | The serial number associated with the CI. |
| model_id | The device model ID. |
| chassis_type | The type of chassis that contains the server. |
| ram | The memory size of the CI. |
| cpu_type | The CPU type. |
| cpu_manufacturer | The CPU manufacturer. |
| Storage disk \[cmdb_ci_disk\] ||
| name | The name of the CI. |
| device_id | The ID of the device. |
| serial_number | The serial number associated with the CI. |
| storage_type | The storage type. |
| size_bytes | The available storage size in bytes. |
| manufacturer | The device manufacturer. |
| model_id | The device model ID. |
| computer | Reference for the storage server. |
| Network adapter \[cmdb_ci_network_adapter\] ||
| name | The name of the CI. |
| ip_address | The IP address of the CI. |
| netmask | The netmask of the server hosting the network adapter. |
| mac_address | The MAC address of the network adapter. |
| IP address \[cmdb_ci_ip_address\] ||
| ip_address | The IP address of the CI. |
| netmask | The netmask of the server hosting the CI. |
[ ]
{#solidfire-storage-pattern__table_w2j_l53_2nb}
The Dependency Views map shows all discovered SolidFire storage system clusters and nodes in your organization and the relationships between them.
## CI relationships {#solidfire-storage-pattern__section_rwc_sjx_54b}
{#solidfire-storage-pattern__table_jtg_dtm_pu832__entry__3}
| CI | Relationship/Reference | CI |
|-|-|-|
| Storage cluster | Cluster Of::Cluster | Storage cluster node |
| Storage cluster node | Hosted On::Hosts | Storage node element |
| Storage node element | Managed By::Manages | Storage cluster |
| Storage server (main CI) | Allocated To::Allocated From | Storage node element |
| Storage server (main CI) | Runs On::Runs | Storage cluster |
| Storage server (main CI) | Contains::Contained By | Disk |
[ ]
{#solidfire-storage-pattern__table_jtg_dtm_pu832}