Modeling Ethernet Virtual Private Lines

[iunderwood]

I am looking for some ideas on how to model some circuits which make up my WAN. These are EVPL circuits from CrownCastle.

I have two diverse headends and about a dozen remote sites. Each remote site has two VLANs, one to each headend. The VLANs are unique to the sites themselves. For instance, Site 1 has VLAN 901 and 902. 901 goes to the primary headend and 902 goes to the secondary headend. They are configured as point-to-point circuits for all intents and purposes.

However, there are 3 IDs that I want to track. The first is a 6-digit service number which identifies the endpoint circuit / NID and those kinds of things coming in. These are pretty straightforward. The others are a CID for each of the P2P VLANs that go from the site to the headends.

In a standard case, I'd place the VLANs on a set of virtual interfaces and track that to the parent, which would track a circuit to the CC network. However, since I want to track the per-VLAN IDs, it seems like I need to make the interfaces independently and connect them directly.

What would be fantastic would be if there was a way to related a connection to a parent link. For instance, I could track a subinterface from a remote site to the headend subinterface over their parent circuits. Supporting the nesting required would be a challenge.

How have others in the community approached this?