Hi Ramon,
Thanks, that actually makes sense.
I see that racktables is very customizable, more than I thought :-)
Per dc I create a virtual rack, and I have created a object type
interconnect. And I added fields to put contract name phone number and more.
For every line to my dmarc I back link. To the interconnect object
On 28 Feb 2020, at 09:35, Ramon van der Wel <realpluut@xxxxxxxxx> wrote:
Hi,
The way I do it
Per dc I create a virtual rack, and I have created a object type
interconnect. And I added fields to put contract name phone number and more.
For that object I create 1 port with the id
For every line to my dmarc I back link. To the interconnect object
This way I have a full a to z path.
Ramon
On Fri, Feb 28, 2020, 09:05 Marijn van Gool <marijn.vangool@xxxxxxxxxxx
<mailto:marijn.vangool@xxxxxxxxxxx>> wrote:
Hello,
I noticed that you can only add a cable ID (or circuit ID?) to a link when
you link two devices and their interfaces together.
Now, in a datacenter, it’s common to have many external cables from 3rd
parties coming in to your rack.
These cables or patches usually have some sort of a ID that identifies them
and separates them from other cables.
This ID is known by both us and the external third party.
Is there a way to attach a cable / circuit ID to an interface?
Marijn
