[racktables-users] Re: Patch panels

From: "Vater, Wolfgang" <wolfgang.vater@xxxxxxxxxxxxx>
To: "racktables-users@xxxxxxxxxxxxx" <racktables-users@xxxxxxxxxxxxx>
Date: Fri, 4 Aug 2017 10:01:47 +0000

I had this issue before.

I created two new objects for this (Configuration : Dictionary : Chapter
'ObjectType'), a PatchPanel-Frame and a PatchPanel-Insert.

Then I go to (Configuration : Object container compatibility) and create a
parent-child relationship between the PatchPanel-Frame and the PatchPanel-Insert

Then you create the PatchPanel-Frame Object. For the name I always use the
rackname and unit number where this is installed like “R03S15 H45” and position
this in this rack and unit.

Now you create the PatchPanel-Insert. I use a rather long name.
<localrack>-<rackunit>-<insert number>--<remoterack>-<rackunit>-<insert
number>.

This could look like this: R03S15-H45-1—R04S12-H45-1

This naming method allows you to have each insert to go to a different
PatchPanel-Frame and a different insert number.

On the properties page of the PatchPanel-Insert you need to select the
PatchPanel-Frame container. Now the Insert is seen as part of the frame.

Of course this is not visible in the rack layout. You will always ever see the
PatchPanel-Frame. But with my long names for the inserts this would be totally
impractical to show the name of each insert, there is simply not enough space
in the field.

I also always add a hardwired port type LC and RJ45 (LC for fiber connections,
I use LC only, and RJ45 for all patch connections) and create the required
port-compatibilities for them. In my PatchPanel-Insert I use only RJ45 or LC as
port type. Using the fantastic Link Management plugin  (available here:
<https://github.com/github138/myRT-contribs/tree/develop-0.20.x>
https://github.com/github138/myRT-contribs/tree/develop-0.20.x ;) you can now
backlink the two PatchPanel-Inserts so that you see the patching across patch
panels.

Wolfgang

Wolfgang Vater | Lead Client Architect | Enterprise Services

Unisys Deutschland GmbH | +49 162 255 9338 | wolfgang.vater@xxxxxxxxxx |
Philipp-Reis-Str. 2 | 65795 Hattersheim

<http://www.unisys.com/>

Unisys Deutschland GmbH | Geschäftsführer: Sandro Lindner & Dr. Uwe Heckert |
Sitz der Gesellschaft: Hattersheim | Amtsgericht: Frankfurt/Main HRB  7929

THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.

DIESE E-MAIL IST AUSSCHLIESSLICH FÜR DEN ADRESSATEN BESTIMMT UND KANN
VERTRAULICHE INFORMATIONEN ENTHALTEN. Sollten Sie nicht der Adressat dieser
Informationen sein, bitten wir Sie, sich mit dem Absender in Verbindung zu
setzen und die Informationen von Ihren Endgeräten zu entfernen.

<http://www.linkedin.com/company/unisys>    <http://twitter.com/unisyscorp>
<https://plus.google.com/+UnisysCorp/posts>
<http://www.youtube.com/theunisyschannel>  <http://www.facebook.com/unisyscorp>
<https://vimeo.com/unisys>  <http://blogs.unisys.com/>

From: racktables-users-bounce@xxxxxxxxxxxxx
[mailto:racktables-users-bounce@xxxxxxxxxxxxx] On Behalf Of Tim W
Sent: 3 August, 2017 18:01
To: racktables-users@xxxxxxxxxxxxx
Subject: [racktables-users] Patch panels

How are you guys doing patch panels?  I am setting up some Ortronics
multi-cassette patch panel banks, and each cassette is connected to a
structured cable run to a different rack.  How can I represent that?  Make the
mother chassis a 'network chassis' and treat the cassettes as blades?

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Follow-Ups:
- [racktables-users] Re: Patch panels
  - From: Tim W

References:
- [racktables-users] Patch panels
  - From: Tim W

[racktables-users] Re: Patch panels

Other related posts: