Add Service Parameters to Virtual Circuit model

[sleepinggenius2]

NetBox version

v4.2.1

Feature type

Data model extension

Triage priority

N/A

Proposed functionality

Add the fields from the "Service Parameters" section of the Circuit model to the Virtual Circuit model as well. This includes the Installed, Terminates, and Commit rate (Kbps) fields. Opening this separate FR as requested in #18153.

Use case

The "Service Parameters" fields from the Circuit model are critical to be on the Virtual Circuit model, as well as the Circuit model, in order to document real world circuits. When establishing an ENNI with another operator, that would be represented as a Circuit, with associated dates and commit rate (line rate). At the same time, or at later times, OVCs could then be ordered that use that ENNI, each with their own dates and commit rate (policed), which would be represented as Virtual Circuits. A similar situation could occur with a UNI represented as a Circuit and VLAN-based EVCs (EVP-Line, EVP-LAN, EVP-Tree) represented as Virtual Circuits.

Those are probably some of the most common scenarios the majority of the NetBox customer base will encounter. In an ISP network, we also see a number of other scenarios. One is L1VCs with L1 ENNIs that could end up in the same situation, if the ODU signal is being multiplexed on the handoff. You could represent the OTU as a Circuit and the lower order ODUs as Virtual Circuits, even the higher order ODU as a Virtual Circuit, if you want. Another is SONET/TDM services that are multiplexed on a handoff, most commonly seen with M13 muxes handing off a T3/DS3 (Circuit) with multiple DS1s (Virtual Circuits) riding on it.

Database changes

Add Installed, Terminates, and Commit rate (Kbps) fields to the Virtual Circuit model, matching the existing fields from the Circuit model.

External dependencies

None