Documentation

User Tools

Site Tools

Trace:
extensions:teemip-cable-mgmt

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
extensions:teemip-cable-mgmt [2025/05/07 16:02] – [Cross Connect] cnaudextensions:teemip-cable-mgmt [2025/06/10 14:45] (current) – [Patch Panel] cnaud
Line 32: Line 32:
 ===== Revision History ===== ===== Revision History =====
 ^  Version  ^  Release Date  ^  Status  ^  iTop \\ Min  ^  IPAM for iTop \\ Min  ^  Comments  ^ ^  Version  ^  Release Date  ^  Status  ^  iTop \\ Min  ^  IPAM for iTop \\ Min  ^  Comments  ^
-|  1.4.0  |  2025-xx-yy  |  WIP  |  3.2.0  |  3.2.0  | - A Cable Category may be set on a Patch Panel \\ - The creation of Back End Network Cables from a Patch Panel may be limited to a given number \\ - A Cable Category may be set on a Network Socket \\ - Organization of a Network Socket is the one of its Patch Panel (if set) or its Location otherwise \\ - A Back End Network Cable may be attached to a Breakout Cable \\ - Cable names can be automatically computed from a method that may be overloaded \\ - Replace legacy CRUD methods by new CRUD events |+|  1.4.0  |  2025-xx-yy  |  WIP  |  3.2.0  |  3.2.0  | - A Cable Category may be set on a Patch Panel and on a Network Socket\\ - The creation of Back End Network Cables from a Patch Panel may be limited to a given number \\ - The organization of a Network Socket is the one of its Patch Panel (if set) or its Location otherwise \\ - A Back End Network Cable may be attached to a Breakout Cable \\ - Local and peer device and physical interface attributes have been added to Cross Connects \\ - Cables that make the path of a Cross Connect are displayed in a tab \\ - Sockets that make the Cross Connect are automatically set or reset with a pointer to the Cross Connect they belong to \\ - Once in production, all device and front end cables of a Cross Connect may be created \\ - Cable names can be automatically computed from a method that may be overloaded \\ - Replace legacy CRUD methods by new CRUD events |
 |  **1.3.1**  |  2024-10-29  |  Supported  |  3.1.2  |  3.2.0  | - Issue [[https://github.com/TeemIp/teemip-cable-mgmt/issues/6|#6]] - Can't create second direct cable connection between two devices  \\ - Breakout Cable: edit the n:n relations with PatchPanels while on display and not on edition anymore \\ - Breakout Vable: improve automation functions | |  **1.3.1**  |  2024-10-29  |  Supported  |  3.1.2  |  3.2.0  | - Issue [[https://github.com/TeemIp/teemip-cable-mgmt/issues/6|#6]] - Can't create second direct cable connection between two devices  \\ - Breakout Cable: edit the n:n relations with PatchPanels while on display and not on edition anymore \\ - Breakout Vable: improve automation functions |
 |  1.3.0  |  2024-06-26  |  Obsolete  |  3.1.1  |  3.1.4  | - A Patch Panel can be mounted in an enclosure \\ - Network Sockets can be automatically created for a given Patch Panel \\ - Back End Cables can be automatically created between the sockets of 2 Patch Panels \\ - Number of free & ready Network Sockets in Patch Panels are displayed \\ - Cross Connects and Breakout Cables are now modelized \\ - Wiring paths can be proposed to connect the 2 Patch Panels of a Cross Connect \\ - Documents can be attached to Network Cables | |  1.3.0  |  2024-06-26  |  Obsolete  |  3.1.1  |  3.1.4  | - A Patch Panel can be mounted in an enclosure \\ - Network Sockets can be automatically created for a given Patch Panel \\ - Back End Cables can be automatically created between the sockets of 2 Patch Panels \\ - Number of free & ready Network Sockets in Patch Panels are displayed \\ - Cross Connects and Breakout Cables are now modelized \\ - Wiring paths can be proposed to connect the 2 Patch Panels of a Cross Connect \\ - Documents can be attached to Network Cables |
Line 117: Line 117:
 | Ready sockets | Number of network sockets with status 'ready' | Automatically computed | | Ready sockets | Number of network sockets with status 'ready' | Automatically computed |
 | Connector | Foreign key to a(n) Interface Connector \\ Brought by the [[extensions:teemip-network-mgmt-extended|Network Management Extended]] extension | No | | Connector | Foreign key to a(n) Interface Connector \\ Brought by the [[extensions:teemip-network-mgmt-extended|Network Management Extended]] extension | No |
-| Cable category | Foreign key to a(n) Cable category | No |+| Cable type | Foreign key to a(n) Cable Type | No | 
 +| Cable category | Foreign key to a(n) Cable Category | No |
 | **Rack Information** ||| | **Rack Information** |||
 | Rack | Foreign key to a(n) Rack | Yes | | Rack | Foreign key to a(n) Rack | Yes |
Line 179: Line 180:
 | **Front End Information** ||| | **Front End Information** |||
 | Connector | Foreign key to a(n) Interface Connector | No | | Connector | Foreign key to a(n) Interface Connector | No |
-| Cable category | Foreign key to a(n) Cable Categpry | No |+| Cable type | Foreign key to a(n) Cable Type | No | 
 +| Cable category | Foreign key to a(n) Cable Category | No |
 | Device | Foreign key to a(n) Connectable CI | No | | Device | Foreign key to a(n) Connectable CI | No |
 | Physical interface | Foreign key to a(n) Physical Interface | No | | Physical interface | Foreign key to a(n) Physical Interface | No |
Line 296: Line 298:
     * The pointer to the cross connect is reset on all the network sockets along the path     * The pointer to the cross connect is reset on all the network sockets along the path
 </note> </note>
 +
 +=== Create Cables ===
 +Once the status of the Cross Connect is set to **Production**, an action available from the Other Actions menu offers to automatically create all the Device and Front End Cables that make the Cross Connect path. However, should it be required, the deletion of these cables remains a manual operation.
  
 === Finding Wiring Paths === === Finding Wiring Paths ===
Line 312: Line 317:
 </note> </note>
  
- 
-=== Create Cables === 
 ===== Physical Interface ===== ===== Physical Interface =====
 {{icons8-globe-wire.png  }}  {{icons8-globe-wire.png  }} 
Line 396: Line 399:
 | Network socket #1 - Back end | Foreign key to a(n) Network Socket | Yes | | Network socket #1 - Back end | Foreign key to a(n) Network Socket | Yes |
 | Network socket #2 - Back end | Foreign key to a(n) Network Socket | Yes |Friendly name of a network cable is automatically computed as the concatenation of the 2 network socket names. | Network socket #2 - Back end | Foreign key to a(n) Network Socket | Yes |Friendly name of a network cable is automatically computed as the concatenation of the 2 network socket names.
 +| **Membership** |||
 +| Breakout cable | Foreign key to a(n)Breakout Cable | No |
  
 === Tabs === === Tabs ===
Line 404: Line 409:
   * The friendly name of a back end network cable is automatically computed as the concatenation of the two network sockets' name.   * The friendly name of a back end network cable is automatically computed as the concatenation of the two network sockets' name.
   * Its label may be automatically computed through the method SetLabel that can be overloaded.   * Its label may be automatically computed through the method SetLabel that can be overloaded.
 +  * A back end network cable may belong to a breakout cable 
 </note> </note>
  
extensions/teemip-cable-mgmt.1746626559.txt.gz · Last modified: by cnaud

Page Tools