1 of 1 people found this helpful
This is talking about the BMC Discovery model it is nothing to do with the CMDB. The default CDM mappings are described here and make no mention of disks or file systems.
The sync mappings do not push this information because you can end up with lots of nodes. Large storage devices can easily result in hundreds of thousands of nodes per device.
Thank you Andrew.
Hi Andrew Waters!
Can I sync the disk information to CMDB or Do you see any risk with this configuration that could make you do not recommend to sync this information to CMDB?
Does exist any model OOTB that I could activate to START uploading disk information to CMDB?
1 of 2 people found this helpful
You could push the information however, as mentioned about it can result in a lot of nodes especially if you are scanning storage systems. What do you tryng to gain by pushing them?
2 of 2 people found this helpful
We have plans to integrate CMDB CIs with CA Spectrum (monitoring), and the CMDB will maintain one list of local support owners of each CIs.
However, we have a particularity that, in case of Windows servers, for instance, we have normalized different support owners for different drives, as for instance the "DRIVES C" are supported by a Windows support team, and "DRIVES D" are supported by development teams (just for instance).
So, if we want to take this plan done, we'll need to sync CIs disk information to CMDB.