Capturing Regional Information in the CMDB

[Stacy1]

Hello,

So we have an infrastructure of regions that we call POD's.   These POD's have a group of offices in them that are supported by a particular infrastructure of switches, routers, servers, etc.   We want to be able to name these POD's in the CMDB and reference all the underlying items that support it.

Has anyone done anything like this before and if so what Configuration Class did you use?

Thank you,

Stacy

[AJ63]

it is may be in "Facility" class. I mean should be. PODs and RPP and all etc are belongs to Facility class. Either can be created or can be mapped to Hardware class. whats say?

[A Westervelt]

Assuming all of your offices are different Location (cmn_location) records, I would create a new POD Location as a parent record to the offices.

In the CMDB, you can build a Group CI that has a location of the new POD records. The Group can then be related to each piece of hardware that supports to the POD. Out-of-the-box relationship "Members::Member of" might be a good fit.

[phanindra1]

Hi Stacy, We had a similar requirement to represent branch offices. We used 'Buildings' class for this purpose, and then related them to hardware and network devices using 'Uses:Used by' relationship type..Let me know if it meets your requirement.

[brukasmj]

This topic is very interesting because we had issues to setup the relationship between buildings/locations and discovered/imported ci's when using another cmdb product. Simply was not working flexible, properly.

So the question is if this is working much more easily in SNOW ? If yes how is it working ?

Is it working based on an integration point ? Synchronised or Asynchronised

Can we fill a building table and related the buildings to the corresponding devices in that building.

How is that relationship built ? Based on ip subnets ? Is there a grouping mechanism ?

thanks in advance for helping

John