Warranty Autodiscovery

Discover Warranty Details with Device42

Device42 supports auto-discovery of hardware warranties, making tracking within Device42 a breeze.

The Device42 warranty autodiscovery and management tools will find and help you keep track of your hardware warranties from Dell, Lenovo, HP Inc., Meraki, and IBM. The functionality originally started as a standalone script, which still functions, and is now integrated into the main UI (see Discovery –> Warranty Sync).

Warranty Sync menu

To configure automatic warranty discovery, you’ll need to simply request API keys from the vendors that require them (currently Dell, HP, and Meraki – links below), and once you’ve provided Device42 with your API access keys, simply let Device42 loose! As long as your device CIs have a model and serial number present so Device42 knows what vendor to ask, and the ID of the machine, warranty autodiscovery does the rest, automatically discovering and populating your hardware’s service contract information.

Detailed Warranty AutoDiscover Setup Instructions

Supported Vendors:

  • Dell
  • IBM
  • Meraki
  • HP (Hewlett Packard)
  • Lenovo

API Keys, Configuration and Prerequisites:

    1. For the script to successfully retrieve warranty information for a given device, the device’s model and serial # fields must be correctly filled out (entered or discovered). If you have more than one Vendor entry for a given vendor, the best option is to merge them prior to discovery. For example to merge all lexical variations of “Dell” into a single vendor, head to DataCenter -> Vendors and check the boxes next to all variations of ‘dell’:
      Merge dell vendor items
    2. The Device42 Model field must be set to one of the following: Dell, HP, IBM, Meraki, or Lenovo – hardware with different vendor name variations will not return a warranty. You can easily add the proper Alias to each vendor if your vendors are named differently. On the vendor edit screen, simply add dell to the Dell vendor entry, hp to your Hewlett Packard vendor entry, ibm for IBM, meraki for Meraki, and finally lenovo to the Lenovo vendor entry:
      Add Dell vendor alias
    3. Get your API keys (Dell, HP, & Meraki):

Dell API key: Instructions for obtaining a Dell API key are available (this moved to TechDirect, now requires a valid Dell login) from here: TechDirect APIs.

HP API key: Instructions to obtain HP API key – http://developers.hp.com (correct as of 11/2018). These instructions from HP offer details around their process for obtaining their API key.

Meraki API Keys: A Meraki API key must be obtained to enable Device42 to retrieve warranty information. Instructions to obtain Meraki API key: https://developer.cisco.com/meraki/api/#/rest/getting-started. These instructions from Meraki offer details around their process for obtaining their API key.

Note: If using the standalone warranty script (instructions in  the STANDALONE section below), Python 2.7 must be installed along with the python library requests.

Secure Communication Details

Both the UI and the warranty script transmit the same information (relevant serial number(s) to the appropriate vendor via port 443 SSL, including the API key entered into Device42 for this purpose only if required by the vendor (Dell/HP/Meraki). Payload looks as follows:

payload = {'id': inline_serials, 'apikey': self.api_key, 'accept': 'Application/json'}

Warranty lookup queries the APIs at the following URLs:

Dell - sandbox.api.dell.com https port 443
Lenovo/IBM - support.lenovo.com https port 443
HP - css.api.hp.com https port 443
Meraki - api.meraki.com https port 443

Configuring a Job / API Key Example

  1. Select Discovery > Warranty Sync from the main menu, then click Add Warranty Check and name your job.
  2. Select a vendor. If you select Dell, HP, or Meraki, be sure to enter your matching API key (see API Keys section above for details on obtaining a Dell/HP/Meraki API key).
    If you select Dell, be sure to select the API Version from the drop-down list (current default is Version 5).
  3. You can add your API key right from this screen. Click the magnifying glass on the Access Key field, and in the upper right of the window that opens, click Add Password and add your key as shown below. Repeat these steps for the Secret Key if necessary.
  4. Choose your Order Number Generation and Debug Level options, set a schedule if desired, and save the job.
  5. Go ahead and run the job!

As long as your API key is active, and devices have a valid model, vendor, and serial information the sync will gather warranty information. On each Device in the “LifeCycle” tab or Datacenter > Purchases, you will find past and present warranty information. This includes O/home/device42/d42/docs/media/images/autodiscovery/warranty-discovery-management/rder details, contract/service types, and dates.

If you are using the STANDALONE warranty script:

  1. Create a working directory. Copy the files from Device42’s GitHub warranty_check Repo
  2. Copy the file warranty.cfg.example to warranty.cfg
  3. Set the required parameters in warranty.cfg [D42 instance info & API keys]:
    warranty.cfg settings example
  4. Run the script! $ python starter.py

Obtaining the standalone script (note: may be deprecated in the future)

As noted above, this functionality is now built into the main UI:

The latest version of the standalone script can be downloaded from GitHub

HPE warranty lookup info

HP Enterprise (“HPE”) hardware warranties cannot currently be retrieved automatically as HPE simply does not offer an API endpoint that makes this data externally available.
HPE Customers can check Hewlett Packard Enterprise Warranty Status at The Hewlett Packard Enterprise Support Center: https://support.hpe.com/hpsc/wc/public/home.

This is a limitation of Hewlett Packard Enterprise, and in no way related to any sort of Device42 limitation. HP recently executed a split it began back in 2014 where Hewlett Packard restructured itself into two separate businesses: Hewlett Packard (“HP”) and Hewlett Packard Enterprise (“HPE”).