Pau Lo
asked on
CMDB relationships for hardware assets
I am looking at the structure of a CMDB. I am told it is best practice to establish relationships between CI (configuration items), which I presume is to assist risk assessments, e.g. if you apply an update to a server, and that server has a relationship to a business critical application, obviously having that degree of knowledge about the infrastructure helps in risk assessment/timing.
But I was not sure what sort of relationships you would define with hardware CI's, or at least server level. The link of business software to hardware makes sense, but why would you define a relationship between 2 hardware items, and can you provide some examples and the benefits in doing so?
But I was not sure what sort of relationships you would define with hardware CI's, or at least server level. The link of business software to hardware makes sense, but why would you define a relationship between 2 hardware items, and can you provide some examples and the benefits in doing so?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Who is responsible for that loss (customer provided relationship about servers but someone somewhere in the chain decided to ignore it, or customer did not provided information)?