[racktables-users] Re: Cabling Report
- From: Ingimar Alfreð Róbertsson <ingimar@xxxxx>
- To: "racktables-users@xxxxxxxxxxxxx" <racktables-users@xxxxxxxxxxxxx>
- Date: Sun, 27 Oct 2013 20:24:52 +0000
Hi.
We created a custom report for displaying a list of all cables in the system.
The highest used number is at the top so it's easy to find the next cable-id.
This is probably not the prettiest code available but it works at least for our
environment using version 0.20.5. :-)
https://github.com/iar42/rt-cable-report
Hope this helps.
Kveðja / Best regards
Ingimar Alfreð Róbertsson
Kerfisstjóri hýsingar
System Administrator - Hosting Solutions
Sími / Telephone:(+354) 570 1003
Farsími / Mobile:(+354) 895 6342
www.ok.is
Fyrirvari/Disclaimer
-----Original Message-----
From: racktables-users-bounce@xxxxxxxxxxxxx
[mailto:racktables-users-bounce@xxxxxxxxxxxxx] On Behalf Of Denis Ovsienko
Sent: 27. október 2013 15:08
To: racktables-users@xxxxxxxxxxxxx
Subject: [racktables-users] Re: Cabling Report
27.10.2013, 09:51, "Louis Kowolowski" <louisk@xxxxxxxxxxxxxxxxx>:
> On Oct 15, 2013, at 2:40 PM, Adrian Leineweber
> <adrian.leineweber@xxxxxxxxxxxxxxxx> wrote:
>
>> Hello List,
>>
>> we are using Racktables 0.20.1 to manage our 2 datacenters.
>> We are using labelled cables referrenced as "Cable ID" in a format like
>> "ADM067"
>>
>> Our problem is:
>> If we want to connect a new device and label new cables for that device we
>> don't know how to obtain the next cable id.
>>
>> Does anybody have a custom report where we can get a sorted output of all
>> used cable id's or something like that.
>>
>> How do you solve this issue in your datacenters without having duplicate
>> lists ?
This report doesn't exist in the current version. However, it is 100% doable
(and I know some users have already independently implemented that). I would
welcome anyone who can implement this as GPL code and relieve others from
reinventing the wheel.
>
> At one point, I worked for a company that used labeled cables. At first, it
> sounded like a really good idea. In practice, it took so long to find the
> matching ID at the other end of the cable that I just started going to the
> switch and asking it to tell me what port mapped to a particular mac address.
> I never went back to labeled cables.
>
The matter is, "label nothing" and "label everything" aren't the only possible
strategies. In many cases labelling 2 meters of twisted pair between a server
and a top-of-rack switch isn't worth the effort. Quite the opposite, labels are
a must for cables that span several rooms, floors and sometimes even cities.
When things go wrong, people need to tell the cables regardless of MAC
addresses, link status and physical connection with the network port. So
there's a valid use case for this.
--
Denis Ovsienko
Other related posts:
