Solution - Communication/Data Circuits in CMDb

[cyked]

Our Network and Telephony teams wanted a way to manage their circuits in the CMDB and be able to use them for things like Incident/Problem/Change Management.  The existing circuit table in CMDB is for power circuits (contains fields like phase, max amps, and voltage) , so I created a new table with some additional fields to meet their needs.  The new table is extended from cmdb_ci.

Below the process requirements are most specifics like field choice list detail.

Process Requirements

• Fields which are required to be populated to create a new record or update an existing record:
  • Name
  • Circuit type
  • Circuit category
  • Circuit ID
  • Terminating device
  • Support group
• Ability for members of IT Network Engineering or Telecom support groups to create new records
• Members of the set support group will have write access to the CI
  
  • Users who are not members of these groups will have read-only access and will not be able to create records
• Circuit ID field is read only unless Lifecycle status is "In build"

Technical Requirements

• There are a few required fields that are custom to Circuits that were added from the base table. Those fields are:
  • Circuit Type – Choice List with following values
    • MPLS
    • Internet
    • P2P
    • SIP
    • PRI
  • Circuit Category – Choice List with following values
    • Corporate
    • Partner
  • Circuit ID – String field (text)
  • LEC ID – String field (text)
  • Port speed – Choice List with following values
    • 10 MBPS
    • 100 MBPS
    • 1 GBPS
    • 10 GBPS
  • Circuit CIR – Choice List with following values
    • 20 Mbps
    • 30 Mbps
    • 40 Mbps
    • 50 Mbps
    • 60 Mbps
    • 70 Mbps
    • 80 Mbps
    • 90 Mbps
    • 100 Mbps
    • 200 Mbps
    • 250 Mbps
    • 300 Mbps
    • 400 Mbps
    • 500 Mbps
    • 600 Mbps
    • 700 Mbps
    • 800 Mbps
    • 900 Mbps
    • 1000 Mbps
    • 2000 Mbps
    • 5000 Mbps
    • 10000 Mbps
  • Terminating Device – Reference field to allow a Network Gear CI to be referenced on a Circuit CI record
    • Reference field is a lookup to Network Gear where the class is Router, Switch, Media Gateway, or WAN Accelerator
  • Device Interface – Reference field to allow a Network Gear CI Network Adapter CI to be referenced on a Circuit CI record
    • Reference field is a lookup to Network Adapter table. Is filtered to ONLY records related to the selected Terminating Device if one is selected
  • Circuit Provider - re-labelled company field on this table

[Anthony Fantene]

There are some OOTB features that will get you started now. 

Telecommunications Service Management (servicenow.com)

At the very least this document mentions a Network Circuit CI (cmdb_ci_network_circuit) which didn't exist 3 years ago, and would be a good place to start and preferable to a custom table.

I'm just researching this myself so not much advice yet on how to best use it.

[bboatright]

There is a "Circuit" class that might be a good candidate for the information/fields as suggested by @cyked

[Robert Campbell]

This is Power Circuits not Data and all of these requirements would need to be added to that table.  Is this still not a thing?  Do people not track data circuits or do they do so in such an unrelated way that searching won't find the expected results?

[Rick25]

hi all,

Check out the "Network circuit" table at cmdb_ci_network_circuit.

You may need to get some extra ci tables from a plugin to see it.

Regards,

Rick

[Robert Campbell]

I checked for the table but it doesn't exist.  Maybe we don't have the plugin enabled but I don't know which plugin that is.  It seems that it may be part of Telecommunication Service Management but I'm guessing that's an additional paid module?