Chassis classes in CSDM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2023 02:19 AM
Hi gurus
I found out at least 3 different tables for Chassis.
Under Hardware table is one cmdb_ci_chassis which extends cmdb_ci_diskshelf_chassis which do not have any own columns. Then under HW-Computer - Server is another one cmdb_ci_chassis_server.
What is difference between so many chassis classes and expecially between cmdb_ci_chassis and cmdb_ci_chassis_server?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2023 05:27 AM
Following is a brief overview about the difference between these CI classes:
cmdb_ci_chassis: It stores CIs that represent physical chassis or enclosures for computing or networking equipment. Examples of CIs that can be stored in this table include rack enclosures, blade enclosures, and switch enclosures. These CIs are typically used to represent the physical infrastructure of a data center.
cmdb_ci_diskshelf_chassis: This table is used to store CIs that represent disk shelves, which are storage devices that house disk drives. These CIs are typically used to manage the storage infrastructure of a data center.
cmdb_ci_chassis_server: It is used to store CIs that represent server chassis or enclosures. These CIs are typically used to manage the physical infrastructure of servers, including blade servers, rack servers, and other server hardware.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2023 11:42 PM
as a matter of fact there is even one more for Cisco.
If cmdb_ci_chassis is used for physical chassis for computing and networking then why there is another one for Cisco or server hardware - Isn't one table so cmdb_ci_chassis enought for all of those?
Why not?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2023 12:43 AM
cmdb_ci_chassis is a direct child class of cmdb_ci_hardware. So it will be suitable to store the chassis records that cannot be classified into the other chassis classes.
cmdb_ci_chassis_server comes further down the hierarchy of hardware (Hardware>Computer>Server>Server Hardware>Server Chassis). So it has many additional attributes compared to cmdb_ci_chassis. So it is definitely more suitable for anything that can be classified as a server chassis.
Cisco UCS chassis is also a direct child class of cmdb_ci_hardware. But this class is having a few attributes which are specific to it. The following URL gives the description of this table as: Physical Cisco UCS chassis hardware used to hold Cisco UCS Blade server hardware.
CMDB tables descriptions (servicenow.com)
So it is to be used only when Cisco specific chassis hardware data needs to be populated in CMDB.