Get Mobile Phone Data to CMDB

[Suman21]

We are planning to bring the Mobile data to CMDB through Mobile Iron integration.

Wanted to understand under which table to we can update this information and also what would be the main attributes

we need to consider.  

Will IMEI number can be considered coalesce?

[Michael de Boer]

The table cmdb_ci_comm_hardware has the attributes to store IMEI, MEID, Carrier and phone number.
It has the same identification rules as the hardware table.
If you have the serial numbers, then you can use that to identify the hardware. (this is out of the box)
When you don't have it, you can add IMEI as identification.

[CMDB Whisperer]

When I last used the MobileIron integration they had created a custom CI class which extended Computer, and that was actually a good solution at the time.  Even at that point they were in the middle of a rewrite of the integration, so I'm not sure if they ended up keeping that class.  If you are an existing MobileIron customer you should be able to download all of the documentation from the MobileIron Marketplace. 

What they should be doing in the latest version is as follows:

1) Use the out of box CI classes which are now part of the CMDB CI Class Models plugin.  These are Communication Hardware (for smart phones) and Handheld Device (for tablets).  Both of these have IMEI built in, and the Asset class currently has this as well.

2) Use the Identification and Reconciliation Engine (IRE) to bring in the data.  Using the IRE there is not a single coalesce field, but rather a set of prioritized rules about what elements in the payload should be used to identify the device.  All CMDB integrations should be using the IRE, and if they don't then you should seriously consider not using those integrations!  That said, even if it is using the IRE, you should make sure to check your identification rules for these classes, because I believe by default they will just be using the default Hardware rules, which include Name, Serial Number, and some other fields which won't be helpful to you.  You will most likely want to override the identifier entries for each class, adding IMEI as an identifier entry, and removing Name, since each device likely will have the same name (i.e. the Model name, since it probably has no discoverable host name -- although this will depend on what the source data looks like and how the map is created.)

[Suman21]

Thanks for the reply... My idea is get the data into the cmdb_ci_comm table (communication Device)

Which has Type to define the Devices. Also as you said... we need to definitely set the Identification rule.

However, the cmdb_ci_comm table does not have IMEI attribute. 

[Michael de Boer]

The table is cmdb_ci_comm_hardware