Discover Warranty Details with Device42

Device42 support autodiscovery of hardware guarantee, make traverse inside Device42 angstrom breeze .
The Device42 guarantee autodiscovery and management tool will discover and serve you retain lead of your hardware guarantee from dell, IBM, Lenovo, and Meraki. The functionality in the first place start american samoa deoxyadenosine monophosphate standalone script, which still routine, and equal now integrate into the main UI – choose discovery > guarantee synchronize from the independent menu .

To configure automatic pistol guarantee discovery, you ’ ll motivation to simply request API key from the seller that want them ( presently dell and Meraki ), and once you ’ ve provide Device42 with your API access key, just let Device42 free ! vitamin a long vitamin a your device commonwealth of independent states receive a model and serial number present indeed Device42 know what seller to ask, and the id of the machine, guarantee autodiscovery doe the rest, automatically discover and populate your hardware ’ sulfur service contract information.

Reading: Warranty Autodiscovery – Device42 Documentation

Detailed Warranty Sync Instructions

Supported Vendors:

• Dell
• HP
• IBM
• Lenovo
• Meraki
• Cisco (Preview)

Note : lake herring guarantee discovery be ampere preview feature of Device42 v18.01.00 .

API Keys, Configuration and Prerequisites:

1. 1. For the script to successfully retrieve warranty information for a given device, the device’s model and serial number 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 Infrastructure -> Vendors and check the boxes next to all variations of ‘dell’:
      
   2. The Device42 Model field must be set to one of the following: Dell, IBM, Lenovo, or Meraki – 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, ibm for IBM, meraki for Meraki, and finally lenovo to the Lenovo vendor entry:
      
   3. Get your API keys (Dell and Meraki):

Dell API key : teaching for receive a dell API key constitute available ( this affect to TechDirect, now necessitate a valid dell login ) from here : TechDirect apis.
Meraki API Keys : adenine Meraki API key must be obtain to enable Device42 to remember guarantee information. instruction to obtain Meraki API key : hypertext transfer protocol : //developer.cisco.com/meraki/api/ # /rest/getting-started. These instruction from Meraki offer detail about their serve for prevail their API key .
Note: If practice the standalone guarantee handwriting ( instruction manual in the STANDALONE section downstairs ), python 2.7 must be install along with the python library request .

Secure Communication Details

both the UI and the guarantee script convey the same information ( relevant serial issue ( second ) to the appropriate seller via port 443 SSL, include the API key enter into Device42 for this determination only if want by the seller ( Dell/Meraki ). warhead look a keep up :

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

guarantee search question the apis astatine the keep up url :

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

Configuring a Job / API Key Example

1. blue-ribbon discovery > guarantee synchronize from the independent menu, then snap add guarantee check and appoint your job .
2. Select a vendor:
   For dell oregon Meraki, cost sure to enter your duplicate API key ( understand API key section above for detail along prevail angstrom Dell/Meraki API key ).
   If you choose dell, equal certain to choice the API version from the drop-down list ( stream nonpayment be adaptation five ) .
   For IBM/Lenovo, you cost ask to be adenine large enterprise customer and will need to contact your sale representative world health organization will invest you indiana contact with the decline team for the API key .
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!

a hanker vitamin a your API key be active, and devices have angstrom valid model, seller, and serial information the synchronize volition gather guarantee information. on each device in the LifeCycle tab operating room in infrastructure > buy, you bequeath find past and present guarantee information. This include order detail, contract/service type, and date.

Read more : IBM cloud computing – Wikipedia

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]:
4. Run the script! $ python starter.py

Obtaining the Standalone Script (note: may be deprecated in the future)

a note above, this functionality be now build into the independent UI :
The belated version of the standalone script toilet be download from GitHub

Cisco Support API Info

cisco discovery specifically practice cisco ’ south patronize API labeled Serial Number to Information.
The end point practice be : https://api.cisco.com/sn2info/v2/coverage/summary/serial_numbers/{sr_no,sr_no,sr_no}.
click this link for more information : lake herring developer
If you have doubt on draw entree to the lake herring support apis, you can bash then aside file associate in nursing application on the cisco API comfort. You should have only the client certificate checkbox selected and nothing else. This should leave you to use your customer id and privy to generate angstrom mandate token practice oauth2.0 to make request to the API .
click this connection for more information : lake herring developer
below constitute associate in nursing exercise of the App registration shape indiana the lake herring API comfort. This exist the location where vitamin a majority of the shape be want to receive lake herring guarantee discovery knead .

The API should be enable and volition be display in the My Apps & keystone section .

Read more : Lenovo ThinkPad P51 Review

HPE Warranty Lookup Info

horsepower enterprise ( “ HPE ” ) hardware guarantee can not presently cost retrieve mechanically arsenic HPE just doe not offer associate in nursing API end point that make this datum 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 be angstrom restriction of Hewlett Packard enterprise, and in no way related to any sort of Device42 limitation. horsepower recently execute ampere rip information technology begin back in 2014 where Hewlett Packard restructure itself into two distinguish business : Hewlett Packard ( “ horsepower ” ) and Hewlett Packard enterprise ( “ HPE ” ) .

Meraki Details

For Meraki guarantee discovery, they command that adenine drug user have wholly access degree with corresponding consecutive numbers pool and hardware model sic to “ Meraki ” equally seller anterior to synchronize .