circuits in CMDB... how to?

[#1]

We'd like to define WAN circuits in our CMDB. Is anyone else doing this...?
The reason we'd like to do this is so when our network monitoring systems identify a down port, we can then identify which circuit was impacted. The network alarms contain a port, not a circuit name.

Has anyone else defined WAN Circuits in their CMDB...?

My initial thought is to create a Circuit table, cmdb_ci_circuit... each Circuit can have 1 or 2 endpoints.
An endpoint will reference a router interface or switch port. Any ideerz...?

[nasa]

We have a similar requirement. Is there any solutions available to track circuits as mentioned above.

[mbourla]

We also needed to model network circuits. At the time (June 11 release) the Circuit class/table that was already there looked to be for power circuits, based on the columns on the table. I now see in Berlin that it's actually listed in the Configuration application as Power Circuit, within Data Center. Don't know if Discovery might populate Power Circuit CIs, or if anything else assumes that they're power circuits. But we decided it was a bad idea to commandeer that class/table to mean network circuits, so create a new custom class/table.

[MB26]

There currently is a class/table called "cmdb_ci_curcuit". You can use this table, add in the correct attributes. Then utilize the "CI Relations" piece to relate the circuit to CI's on either side. Depending on what you relate to the circuit, you could get the visual of a port, on "X" switch/router, which may be connected to a circuit.