{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30081,"path":"it-operations-management/discovery-and-service-mapping-patterns/emc-data-domain-pattern.md","title":"Dell Data Domain storage discovery using Patterns","bundle":null,"doc_type":null,"release":"australia","body":"\n# Dell Data Domain storage discovery using Patterns\n\nDiscovery and Service Mapping use the **Dell EMC Data Domain** serverless pattern to find the Data Domain storage systems registered in the Data Domain Management Center \\(DDMC\\). Discovering some of these resources might require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.\n\n## Request apps on the Store\n\nVisit 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://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).\n\nTo learn about Data Domain components and their versions that you can discover, refer to [Detailed information on products discovered by ITOM Visibility](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/itom-visibility/r_SupportedApplications.md)\n\n## Prerequisites\n\n- **Verify that the applications are up to date**\n\n Discovery and Service Mapping Patterns\n\n CMDB CI Class Models\n\n- **Verify the creation of the credential alias**\n\n role: DDMC admin.\n\n 1. Set the scope to: **Global**.\n 2. Navigate to **Connections & Credentials** > **Connection & Credential Aliases**.\n 3. Select **New**.\n 4. Fill in the fields in the form.\n\n |Field|Description|\n |-----|-----------|\n |Name|Enter a unique name for the alias. For example: `ddmc_discovery_ceredential_alias`. Make note of the alias name to use it for configuring the **Basic Auth** credentials.|\n |Type|From the list, select **Credential**.|\n |ID|The **ID** field is populated automatically when submitting the form. Make note of the alias ID to use it for configuring the parameters for the **Dell EMC Data Domain** pattern. For example: `ddmc_credential_alias_id`.|\n\n 5. Select **Submit**.\n\n- **Verify the configuration of the __Basic Auth__ credentials**\n\n role: DDMC admin.\n\n **Note:** To run discovery with Patterns, you can create only one credential per one alias.\n\n 1. Navigate to **Connections & Credentials** > **Connection & Credential Aliases**.\n 2. In the list, search for the alias unique name and open the record.\n 3. From the list, select **Basic Auth** Credentials.\n 4. Fill in the fields in the form.\n\n |Field|Description|\n |-----|-----------|\n |Name|Fill in a unique name for the credentials. For example: `ddmc_discovery_basic_auth_ceredentials`.|\n |User name|Fill in the user name that can access the DDMC. This user is created in the DDMC. The user should have minimum read-only permissions. Alternatively, fill in the REST API interface for the DDMC.|\n |Password|Fill in the password that can access the DDMC. This password is created in the DDMC.|\n |Active|Enabled by default.|\n |Credential alias|If you entered the form through the alias, you don't need to configure this field.|\n\n 5. Select **Submit**.\n\n- **Verify the configuration of a Serverless Discovery schedule**\n\n role: Discovery\\_admin.\n\n 1. Navigate to **Discovery** > **Discovery Schedules**.\n 2. Select **New**.\n 3. Fill in the fields in the form.\n\n |Field|Description|\n |-----|-----------|\n |Name|Fill in the name of your choice.|\n |Discover|In the list, select `Serverless`.|\n |MID Server|Select the search button to open the list of MID Servers and select the MID Server that has network access to the DDMC.|\n |Active|Enabled by default.|\n |Credential alias|No need to configure this field.|\n\n For more information about setting the **Max run time**, **Run**, and **Time** fields, see: [Schedule a horizontal discovery](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/t_CreateADiscoverySchedule.md)\n\n 4. Select **Submit**.\n\n- **Associate the __Dell EMC Data Domain__ pattern with the Serverless Discovery schedule**\n\n role: Discovery\\_admin.\n\n 1. Navigate to **Discovery** > **Discovery Schedules**.\n 2. Select the schedule that you configured.\n 3. Select the **Serverless Execution Patterns** tab.\n 4. Select **New**.\n 5. Fill in the fields in the form.\n\n |Field|Description|\n |-----|-----------|\n |Name|Fill in the name of your choice. For example: `dell_emc_data_domain_serverless_discovery`|\n |Pattern|Select the search button to open the list of patterns, and select the **Dell EMC Data Domain** pattern.|\n |Proxy Host|No need to configure this field.|\n |Extended Parameters|No need to configure this field.|\n\n 6. Select **Submit**.\n\n- **Configure the parameters for the __Dell EMC Data Domain__ pattern**\n\n role: Discovery\\_admin.\n\n 1. Navigate to **Discovery** > **Discovery Schedules**.\n 2. Select the schedule that you configured.\n 3. Select the **Serverless Execution Pattern** tab.\n 4. Select the record created for the **Dell EMC Data Domain** pattern.\n 5. In the **Discovery Pattern Launcher parameters** tab, set the value for the fields as follows:\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nCredential Alias\n\n\n\nFill in the alias ID configured for DDMC. You can find the alias in the **Connection & Credential Aliases** list. For example: `ddmc_credential_alias_id`.\n\n
\n\nDDMC Port\n\n\n\n\\(Optional\\) by default the pattern uses port 3009.\n\n
\n\nDDMC IP Address\n\n\n\nFill in the host name or the IP Address of the DDMC. These details can be provided by the DDMC Admin.\n\n For example: `101.10.10.101` or `ddmc.demo.local`.\n\n
6. To run the discovery, you can select **Discover now** from the **Related Links** or wait for the run time.\n\n## Data collected by Discovery during horizontal discovery\n\nDiscovery populates the data in the CMDB when running the **Dell EMC Data Domain** Patterns.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName \\[name\\]\n\n\n\nThe unique identifier of the storage server. The name is typically the Domain Name System \\(DNS\\) hostname or the computer name, which corresponds to the **host\\_name** attribute.\n\n
\n\nHost Name \\[host\\_name\\]\n\n\n\nThe DNS hostname of the Data Domain system. The host that is used to register the system with the Data Domain Management Center \\(DDMC\\).\n\n
\n\nFQDN \\[fqdn\\]\n\n\n\nThe Fully Qualified Domain Name of the Data Domain system. The complete domain name used to register the system with the DDMC.\n\n
\n\nIP Address \\[ip\\_address\\]\n\n\n\nThe IP address of the Data Domain storage server. The name is the specific IP address used to register the Data Domain system with the DDMC.\n\n
\n\nOS Version \\[os\\_version\\]\n\n\n\nThe version of the operating system running on the Data Domain system. The versions supported are from DD OS 7.3.\n\n
\n\nModel \\[model\\]\n\n\n\nThe specific model of the Data Domain \\(DD\\) system. For example, the name for the DD Virtual Edition \\(VE\\) is **DELL EMC DD VE**.\n\n
\n\nManufacturer \\[manufacturer\\]\n\n\n\nThe manufacturer is Dell EMC.\n\n
\n\nSerial Number \\[serial\\_number\\]\n\n\n\nThe unique serial number assigned to the DD system.\n\n
\n\nOperating System \\[os\\]\n\n\n\nThe Data Domain OS is: **DD OS**.\n\n
\n
\n\nField\n\n\n\nDescription\n\n
\n\nName \\[name\\]\n\n\n\nThe name of the DDMC associated with the storage cluster.\n\n
\n\nCluster ID \\[cluster\\_id\\]\n\n\n\nThe universally unique identifier \\(UUID\\) of the DDMC, which uniquely identifies the cluster.\n\n
\n\nCluster Version \\[cluster\\_version\\]\n\n\n\nThe software version of the DDMC that is currently installed on the cluster.\n\n
\n\nSerial Number \\[serial\\_number\\]\n\n\n\nThe unique serial number assigned to the Virtual Data Domain Management Center \\(VDDMC\\) system.\n\n
\n\nModel ID \\[model\\_id\\]\n\n\n\nThe specific model of the Data Domain system in use. For the DDMC, the model ID is 'DELL EMC DD Management Center'.\n\n
\n\nManufacturer \\[manufacturer\\]\n\n\n\nThe manufacturer is Dell EMC.\n\n
\n
\n\nField\n\n\n\nDescription\n\n
\n\nName \\[name\\]\n\n\n\nThe name assigned to the disk device within the storage system.\n\n
\n\nDevice ID \\[device\\_id\\]\n\n\n\nThe unique identifier for the disk device, which is the same as the device name.\n\n
\n\nModel ID \\[model\\_id\\]\n\n\n\nThe model of the disk device. For example: **VMware Virtual\\_disk**.\n\n
\n\nSize \\[size\\]\n\n\n\nThe capacity of the disk device, measured in gigabytes \\(GB\\).\n\n
The Disk Shelf Chassis database is populated only for physical DD systems that support disk expansion shelves.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nName \\[name\\]\n\n\n\nThe name of the disk expansion shelf.\n\n
\n\nSerial Number \\[serial\\_number\\]\n\n\n\nThe unique serial number of the disk expansion shelf.\n\n
\n
\n\nField\n\n\n\nDescription\n\n
\n\nSerial Number \\[serial\\_number\\]\n\n\n\nThe unique serial number of the Dell EMC Data Domain storage system, as registered in the DDMC.\n\n
\n\nSerial Number Type \\[serial\\_number\\_type\\]\n\n\n\nThe format of the serial number for the Dell EMC Data Domain storage system, indicating whether it's a system serial number or a Universally Unique Identifier \\(UUID\\).\n\n
\n\nValid \\[valid\\]\n\n\n\nThe validity of the data, with a value of **true** confirming that the serial number has been successfully verified.\n\n
\n
\n\nField\n\n\n\nDescription\n\n
\n\nName \\[name\\]\n\n\n\nThe identifier or label of the network adapter, such as **eth1**.\n\n
The DDMC REST API doesn’t provide the MAC address of network adapters. As a result, the MAC address field for network adapters remains empty.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nIP Address \\[ip\\_address\\]\n\n\n\nThe IP address that is assigned to the device.\n\n
\n\nNetmask \\[netmask\\]\n\n\n\nThe netmask associated with the IP address, defining the subnet to which the IP address belongs.\n\n
## CI relationships\n\nDiscovery and Service Mapping Patterns create these relationships to support the Data Domain discovery.\n\n\n
\n\nCI\n\n\n\nRelationship Type\n\n\n\nCI\n\n
\n\ncmdb\\_ci\\_storage\\_server\n\n\n\nManaged by::Manages\n\n\n\ncmdb\\_ci\\_storage\\_cluster\n\n
\n\ncmdb\\_ci\\_storage\\_server\n\n\n\nContains::Contained By\n\n\n\ncmdb\\_ci\\_disk\n\n
\n\ncmdb\\_ci\\_disk\\_shelf\\_chassis\n\n\n\nHosted on:: hosts\n\n\n\ncmdb\\_ci\\_storage\\_server\n\n
\n\ncmdb\\_ci\\_serial\\_number\n\n\n\nreference\n\n\n\ncmdb\\_ci\\_storage\\_server\n\n
\n\ncmdb\\_ci\\_storage\\_server\n\n\n\nOwns::Owned by\n\n\n\ncmdb\\_ci\\_network\\_adapter\n\n
\n\ncmdb\\_ci\\_storage\\_server\n\n\n\nOwns::Owned by\n\n\n\ncmdb\\_ci\\_ip \\_address\n\n
**Parent Topic:**[Available on-premise discovery patterns](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery-and-service-mapping-patterns/available-patterns.md)\n\n"}}