On Thu, Mar 5, 2020 at 7:05 AM Marijn van Gool <marijn.vangool@xxxxxxxxxxx>
You have a point there: really do not know what would happen after an
Yes, definitely staying away from this.
What I'm doing on my own (until this feature is available) is to generate
a code on the cable-id, where each field is separated by a ":".
I've defined a syntax such as "field1 : field2 : field3" where each field
represents something you might need ...
Not the best idea, but so far is working for us …
I’m trying something like this as well.
With inter datacenter backbone cables there’s usually:
- circuit ID location A;
- circuit ID location B;
- reference number of the actual backbone circuit, defined by the carrier.
Some options I can think of:
- [option A] cable ID —> circuit_ID_A : circuit_ID_B :
- [option B] visible label —> interface description + circuit_ID_A / B *and
*cable ID —> reference_number_carrier
Both not optimal, but both sort of do the job.
What do you think?