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 [2024/10/03 16:32] – [Revision History] cnaudextensions:teemip-cable-mgmt [2025/05/19 17:00] (current) – [Cross Connect] cnaud
Line 7: Line 7:
 level_hidden        : 1 level_hidden        : 1
 collector_hidden    : no collector_hidden    : no
-version             : 1.3.0 +version             : 1.3.1 
-release_dt          : 2024-06-26 +release_dt          : 2024-10-29 
-TeemIp              : 3.1+ +TeemIp              : 3.2+ 
-iTop                : 3.1++iTop                : 3.1.2+
 code                : teemip-cable-mgmt code                : teemip-cable-mgmt
 localization        : English, French, German localization        : English, French, German
Line 19: Line 19:
 keyword_tags        : cmdb, cable keyword_tags        : cmdb, cable
 dependencies_s      : teemip-framework, teemip-config-mgmt-adaptor dependencies_s      : teemip-framework, teemip-config-mgmt-adaptor
-download_wiki       : [[https://sourceforge.net/projects/teemip/files/teemip%20-%20extensions/Cable%20Management/1.3.0/teemip-cable-mgmt-1.3.0-125.zip/download|teemip-cable-mgmt-1.3.0-125.zip]]+download_wiki       : [[https://sourceforge.net/projects/teemip/files/teemip%20-%20extensions/Cable%20Management/1.3.1/teemip-cable-mgmt-1.3.1-126.zip/download|teemip-cable-mgmt-1.3.1-126.zip]]
 github_wiki         : [[https://github.com/TeemIp/teemip-cable-mgmt|teemip-cable-mgmt]] github_wiki         : [[https://github.com/TeemIp/teemip-cable-mgmt|teemip-cable-mgmt]]
 php-max             : 8.3 php-max             : 8.3
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.3.1  |  |  |  |  | - PR [[https://github.com/TeemIp/teemip-cable-mgmt/issues/6|#6]] - Can't create second direct cable connection between two devices. | +|  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.0**  |  2024-06-26  |  Supported  |  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.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.2.0  |  2023-12-07  |  Supported  |  3.1.1  |  3.1.4  | - A new Direct Cable class enables the connection between 2 physical interfaces together \\ - The direct connection of 2 CIs is visible in the wiring diagram \\ - Audit rules have been enhanced \\ - Data samples have been added \\ - Objects brought by the extension have their summary card \\ - Add Chinese (simplified) translation |+|  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.2.0  |  2023-12-07  |  Obsolete  |  3.1.1  |  3.1.4  | - A new Direct Cable class enables the connection between 2 physical interfaces together \\ - The direct connection of 2 CIs is visible in the wiring diagram \\ - Audit rules have been enhanced \\ - Data samples have been added \\ - Objects brought by the extension have their summary card \\ - Add Chinese (simplified) translation |
 |  1.1.0  |  2023-07-24  |  Obsolete  |  3.1.0  |  3.1.0  | - Interfaces with no connections have been removed from the wiring diagram \\ - Network cable class has been split into Backend, Frontend and Device network cable classes \\ - An audit rule identifies the cables connected to one end only \\ - Modelization of cables, sockets and interfaces have been enhanced \\ - A socket can be attached to a location or a patch panel \\ - A tab displays the list of patch panels mounted in a rack \\ - Patch panels can be handled by [[https://store.itophub.io/en_US/products/molkobain-datacenter-view-extended|Molkobain DC view extended]] | |  1.1.0  |  2023-07-24  |  Obsolete  |  3.1.0  |  3.1.0  | - Interfaces with no connections have been removed from the wiring diagram \\ - Network cable class has been split into Backend, Frontend and Device network cable classes \\ - An audit rule identifies the cables connected to one end only \\ - Modelization of cables, sockets and interfaces have been enhanced \\ - A socket can be attached to a location or a patch panel \\ - A tab displays the list of patch panels mounted in a rack \\ - Patch panels can be handled by [[https://store.itophub.io/en_US/products/molkobain-datacenter-view-extended|Molkobain DC view extended]] |
 |  1.0.0  |  2022-12-04  |  Obsolete  |  3.1.0  |  3.1.0  | - Initial revision | |  1.0.0  |  2022-12-04  |  Obsolete  |  3.1.0  |  3.1.0  | - Initial revision |
Line 41: Line 42:
 TeemIp cable management allows you to document the cable layouts of your organization. Connect physical interfaces to wall mounted network sockets, to patch panels hosted in racks or to other physical interfaces, document your patch cables and your underlying cabling layout, manage your cross connects: the extension enables a large scope of connection scenarios as the following drawing highlights: TeemIp cable management allows you to document the cable layouts of your organization. Connect physical interfaces to wall mounted network sockets, to patch panels hosted in racks or to other physical interfaces, document your patch cables and your underlying cabling layout, manage your cross connects: the extension enables a large scope of connection scenarios as the following drawing highlights:
  
-{{ cabling_scenarios.png }}+{{ cabling_scenarios.png ?nolink }}
  
 Furthermore, the extension displays the wiring that links devices, physical interfaces and network sockets together, like: Furthermore, the extension displays the wiring that links devices, physical interfaces and network sockets together, like:
  
-{{ cabling_wiring3.png }}+{{ cabling_wiring3.png ?nolink }}
  
 Note that the drawing has been manually rearranged. Note that the drawing has been manually rearranged.
Line 84: Line 85:
 Under the **Other Settings** fieldset, the **Allow cabling toward another organizations** parameter enables patch panels from a given organization to be connected to patch panels of other organizations. Under the **Other Settings** fieldset, the **Allow cabling toward another organizations** parameter enables patch panels from a given organization to be connected to patch panels of other organizations.
  
-{{ cabling_ipsettings.png }}+{{ cabling_ipsettings.png ?nolink }} 
 +===== Implementation Scenario ===== 
 +This section provides, as an example, a method that can be followed to implement TeemIp Cable Management. 
 +  
 +  - 1. Create the Racks at your different locations. 
 +  - 2. Create the [[extensions:teemip-cable-mgmt#patch_panel|Patch panels]] contained in these different racks. 
 +  - 3. On each Patch panel use the **Create network sockets** menu to automatically create as much network sockets as the Patch panel's capacity. 
 +  - 4. Still on each Patch panel, use the **Create back end network cables** menu to link its Network sockets to remote ones located in another Patch panel that you'll select, and create the associated back end network cables at the same time. 
 +    - - Note that such connections and cables may be manually created. 
 +    - - Once a back end connection exist for a Network socket, its status will become "Ready". 
 +    - - Back end cables will be listed in the **Cables** tab of the Patch panel. 
 +  - 5. Create your [[extensions:teemip-cable-mgmt#breakout_cable|Breakout cables]] and incorporate the appropriate Back end network cables in them. 
 +    - - Breakout cables will be listed as well in the **Cables** tab of the Patch panel.
 ===== Patch Panel  ===== ===== Patch Panel  =====
 {{icons8-toolbar.svg  }}  {{icons8-toolbar.svg  }} 
Line 97: Line 110:
 | Status| Possible values: Implementation, Production  | Automatically computed | | Status| Possible values: Implementation, Production  | Automatically computed |
 | Location | Foreign key to a(n) Location | Yes | | Location | Foreign key to a(n) Location | Yes |
 +| External reference | Alphanumeric string | No |
 +| Description | Multiline character string | No |
 +| **Connectivity** |||
 | Capacity | Number of network sockets that the panel can host | No | | Capacity | Number of network sockets that the panel can host | No |
 | Free sockets | Number of network sockets still available on the panel | Automatically computed | | Free sockets | Number of network sockets still available on the panel | Automatically computed |
 | 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 |
-| External reference | Alphanumeric string | No | +| Cable category | Foreign key to a(n) Cable category | No |
-| Description | Multiline character string | No |+
 | **Rack Information** ||| | **Rack Information** |||
 | Rack | Foreign key to a(n) Rack | Yes | | Rack | Foreign key to a(n) Rack | Yes |
Line 108: Line 123:
  
  
-Should the extension [[https://store.itophub.io/en_US/products/molkobain-datacenter-view-extended|Datacenter View Extended]] be installed on TeemIp, the following additional attributes will appear.+Should the extension [[https://store.itophub.io/en_US/products/molkobain-datacenter-view-extended|Datacenter View Extended]] be installed on TeemIp, the rack Informations will be completed with the following additional attribute:
 ^  Name  ^  Type  ^  Mandatory?  ^ ^  Name  ^  Type  ^  Mandatory?  ^
-| **More Information** ||| 
 | Panel | Possible values: Front, Rear | Yes | | Panel | Possible values: Front, Rear | Yes |
 | Zero-U | Possible values: Yes, No | Yes | | Zero-U | Possible values: Yes, No | Yes |
Line 127: Line 141:
 In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Patch Panel dashlet, click on it and select the item you are interested in: In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Patch Panel dashlet, click on it and select the item you are interested in:
  
-{{ classdisplay_patchpanel3x.png }}+{{ classdisplay_patchpanel3x.png ?nolink }}
  
 With the extension [[https://store.itophub.io/en_US/products/molkobain-datacenter-view-extended|Datacenter View Extended]], Patch Panel display will look like: With the extension [[https://store.itophub.io/en_US/products/molkobain-datacenter-view-extended|Datacenter View Extended]], Patch Panel display will look like:
  
-{{ classdisplay_patchpanel-dcviewext.png }}+{{ classdisplay_patchpanel-dcviewext.png ?nolink }}
  
 === Creating network sockets === === Creating network sockets ===
-If the capacity is set, to value c for instance, TeemIP will offer to automatically create c network sockets and to attach them to the patch panel. If n network sockets do already exist, with n < c, then the menu will still be displayed but only (c - n) network sockets will be created. When created, network socket will be set to inactive mode and will inherit of attributes location, rack, patch panel (obviously) and interface connector (if exists) from the patch panel.+If the capacity is set, to value c for instance, TeemIP will offer to automatically create c [[extensions:teemip-cable-mgmt#network_socket|network sockets]] and to attach them to the patch panel. If n network sockets do already exist, with n < c, then the menu will still be displayed but only (c - n) network sockets will be created. When created, network socket will be set to inactive mode and will inherit of attributes location, rack, patch panel (obviously) and interface connector (if exists) from the patch panel.
  
 === Creating back end network cables === === Creating back end network cables ===
-If some network sockets are already attached to the patch panel, TeemIP will offer to automatically connect the back end interface of these network sockets to remote sockets located in another patch panel of another Rack. This action removes to TeemIP administrator the burden of creating back end network cables for each of the network sockets attached to a patch panel.+If some network sockets are already attached to the patch panel, TeemIP will offer to automatically connect the back end interface of some of these network sockets to remote sockets located in another patch panel of another Rack. This action removes to TeemIP administrator the burden of creating back end network cables for each of the network sockets attached to a patch panel.
  
-When action is launched, TeemIP offers first to select the remote patch panel...+When action is launched, TeemIP offers first to select the number of network sockets to consider and the remote patch panel...
  
-{{ classdisplay_patchpanel_createbackendcables.png }}+{{ classdisplay_patchpanel_createbackendcables.png ?nolink }}
  
 .. before creting the links in accordance with the number of available sockets in the remote rack. .. before creting the links in accordance with the number of available sockets in the remote rack.
  
 <note tip> <note tip>
-By default, the remote patch panel must belong to the same organization as the source one. This behaviour may be changed through the parameter **Allow cabling toward another organizations** of the Global IP setting of the source organization, as described [[extensions:teemip-cable-mgmt#global_ip_settings|here]].+By default, the remote patch panel must belong to the same organization as the source one. This behaviour may be changed through the parameter **Allow cabling toward another organization** of the Global IP setting of the source organization, as described [[extensions:teemip-cable-mgmt#global_ip_settings|here]].
 </note> </note>
  ===== Network Socket =====  ===== Network Socket =====
Line 160: Line 174:
 | Rack | Foreign key to a(n) Rack | No | | Rack | Foreign key to a(n) Rack | No |
 | Patch panel | Foreign key to a(n) Patch Panel | No | | Patch panel | Foreign key to a(n) Patch Panel | No |
-| Organization | Organization that the patch panel belongs to | N/A |+| Organization | Foreign key to a(n) Organization | Yes |
 | External reference | Alphanumeric string | No | | External reference | Alphanumeric string | No |
 | Comment | Multiline character string | No | | Comment | Multiline character string | No |
 | **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 |
 | 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 171: Line 186:
 | **Back End Information** ||| | **Back End Information** |||
 | Back end network socket | Foreign key to a(n) Network Socket | No | | Back end network socket | Foreign key to a(n) Network Socket | No |
- 
-Friendly name of a network socket is automatically computed as the concatenation of the location name, rack name (if exists), patch panel name (if exists) and code of the socket. 
  
 === Tabs === === Tabs ===
Line 179: Line 192:
  
 <note tip> <note tip>
-A network socket can be installed in a patch panel or as a stand alone equipment in a room. +  * The friendly name of a network socket is automatically computed as the concatenation of the location name, rack name (if exists), patch panel name (if exists) and code of the socket. 
-  * When installed in a patch panel, attributes Location, Rack and Patch panel are mandatory. +  * The code of the network socket is computed by the method ''ComputeCode'' that can be overwriten through a datamodel extension. 
-  * When standing alone, attribute Location is mandatory but Rack and Patch panel must **NOT** be set.+  * Its organization is the one of the patch panel, if one has been selected, or the one of the location. 
 +  * A network socket can be installed in a patch panel or as a stand alone equipment in a room. 
 +    * When installed in a patch panel, attributes Location, Rack and Patch panel are mandatory. 
 +    * When standing alone, attribute Location is mandatory but Rack and Patch panel must **NOT** be set.
 </note> </note>
  
Line 187: Line 203:
 In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Network Socket dashlet, click on it and select the item you are interested in or select it directly from the Patch panel detailed display : In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Network Socket dashlet, click on it and select the item you are interested in or select it directly from the Patch panel detailed display :
  
-{{ classdisplay_networksocket3x.png }}+{{ classdisplay_networksocket3x.png ?nolink }}
  
 Network Sockets have 2 sides: Network Sockets have 2 sides:
Line 247: Line 263:
 | Primary Network socket | Foreign key to a(n) Network Socket | No | | Primary Network socket | Foreign key to a(n) Network Socket | No |
 | Secondary Network socket | Foreign key to a(n) Network Socket | No | | Secondary Network socket | Foreign key to a(n) Network Socket | No |
 +| Device | Foreign key to a(n) Connectable CI | No |
 +| Physical interface | Foreign key to a(n) Physical interface | No |
 | **Peer Unit Information** ||| | **Peer Unit Information** |||
-| Location | Foreign key to a(n) Location of Peer Organization | Yes | +| Peer location | Foreign key to a(n) Location of Peer Organization | Yes | 
-| Rack | Foreign key to a(n) Rack | Yes | +| Peer rack | Foreign key to a(n) Rack | Yes | 
-| Patch panel | Foreign key to a(n) Patch Panel  | Yes | +| Peer patch panel | Foreign key to a(n) Patch Panel  | Yes | 
-| Primary Network socket | Foreign key to a(n) Network Socket | No | +| Peer primary Network socket | Foreign key to a(n) Network Socket | No | 
-| Secondary Network socket | Foreign key to a(n) Network Socket | No | +| Peer secondary Network socket | Foreign key to a(n) Network Socket | No | 
-| **Back End Information** ||| +| Peer device | Foreign key to a(n) Connectable CI | No | 
-| Back end network socket | Foreign key to a(n) Network Socket | No |+| Peer physical interface | Foreign key to a(n) Physical interface | No |
  
 === Tabs === === Tabs ===
Line 260: Line 278:
 | Contacts | All the contacts for the Cross Connect | | Contacts | All the contacts for the Cross Connect |
 | Documents | All the documents linked to the Cross Connect | | Documents | All the documents linked to the Cross Connect |
 +| Active tickets | All the non closed tickets related to the Cross Connect |
 | Wiring | Wiring diagram | | Wiring | Wiring diagram |
 +| Cables | All the cables that make the Cross Connect |
  
  
Line 266: Line 286:
 In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Cross Connect dashlet, click on it and select the item you are interested in : In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Cross Connect dashlet, click on it and select the item you are interested in :
  
-{{ classdisplay_crossconnect.png }}+{{ classdisplay_crossconnect.png ?nolink }} 
 + 
 +<note tip> 
 +  * When the Cross Connect moves to production state: 
 +    * The cables that make the path between the local and peer end are listed in the **Cables** tab. 
 +    * All the network sockets along the path are set with a pointer to the cross connect 
 +  * When the Cross Connect exits the production state: 
 +    * The **Cables** tab is not displayed anymore. 
 +    * The pointer to the cross connect is reset on all the network sockets along the path 
 +</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 ===
 A cross connect documents a link between one or two network socket hosted in a patch panel sitting in a rack of a given organization and one or two peer network socket hosted in a peer patch panel sitting in a peer rak of a peer organization. The **Find wiring paths** action will display all the available cabling paths that may be establish to connect 2 network sockets that answer to the previous conditions. A cross connect documents a link between one or two network socket hosted in a patch panel sitting in a rack of a given organization and one or two peer network socket hosted in a peer patch panel sitting in a peer rak of a peer organization. The **Find wiring paths** action will display all the available cabling paths that may be establish to connect 2 network sockets that answer to the previous conditions.
  
-{{ classdisplay_crossconnect_find_path.png }}+{{ classdisplay_crossconnect_find_path.png ?nolink }}
  
 Network admin may select one of the offered path and manually create it within TeemIP. Network admin may select one of the offered path and manually create it within TeemIP.
Line 282: Line 314:
 These value can be overwritten through the configuration file, as described [[extensions:teemip-cable-mgmt#configuration_file|here]]. These value can be overwritten through the configuration file, as described [[extensions:teemip-cable-mgmt#configuration_file|here]].
 </note> </note>
 +
 ===== Physical Interface ===== ===== Physical Interface =====
 {{icons8-globe-wire.png  }}  {{icons8-globe-wire.png  }} 
Line 304: Line 337:
 A connection between a physical interface and a network socket will look as follows. A connection between a physical interface and a network socket will look as follows.
  
-{{ classdisplay_networksocket_to_physicalinterface.png }} +{{ classdisplay_networksocket_to_physicalinterface.png ?nolink }} 
-{{ classdisplay_physicalinterface_to_networksocket.png }}+{{ classdisplay_physicalinterface_to_networksocket.png ?nolink }}
  
  
 A connection between two physical interfaces will look as follows. A connection between two physical interfaces will look as follows.
  
-{{ classdisplay_physicalinterface_to_physicalinterface.png }}+{{ classdisplay_physicalinterface_to_physicalinterface.png ?nolink }}
  
 ===== Front End Network Cable ===== ===== Front End Network Cable =====
Line 327: Line 360:
 | Network socket #1 - Front end | Foreign key to a(n) Network Socket | Yes | | Network socket #1 - Front end | Foreign key to a(n) Network Socket | Yes |
 | Network socket #2 - Front 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 - Front 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.
- 
-Friendly name of a front end network cable is automatically computed as the concatenation of the two network sockets' name. 
  
 === Tabs === === Tabs ===
 ^  Tab  ^  Description  ^ ^  Tab  ^  Description  ^
 | Documents | All documents linked to the front end network cable | | Documents | All documents linked to the front end network cable |
 +
 +<note tip>
 +  * The friendly name of a front 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.
 +</note>
  
 <note warning> <note warning>
Line 344: Line 380:
 In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Front End Network Cable dashlet, click on it and select the item you are interested in or select it directly from the Patch Panel or Network Socket detailed displays : In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Front End Network Cable dashlet, click on it and select the item you are interested in or select it directly from the Patch Panel or Network Socket detailed displays :
  
-{{ classdisplay_frontendnetworkcable.png }}+{{ classdisplay_frontendnetworkcable.png ?nolink }}
  
 ===== Back End Network Cable ===== ===== Back End Network Cable =====
Line 361: Line 397:
 | 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** ||| 
-Friendly name of a back end network cable is automatically computed as the concatenation of the two network sockets' name.+| Breakout cable | Foreign key to a(n)Breakout Cable | No |
  
 === Tabs === === Tabs ===
 ^  Tab  ^  Description  ^ ^  Tab  ^  Description  ^
 | Documents | All documents linked to the back end network cable | | Documents | All documents linked to the back end network cable |
 +
 +<note tip>
 +  * 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.
 +  * A back end network cable may belong to a breakout cable 
 +</note>
  
 <note warning> <note warning>
Line 378: Line 420:
 In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Back End Network Cable dashlet, click on it and select the item you are interested in or select it directly from the Patch Panel or Network Socket detailed displays : In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Back End Network Cable dashlet, click on it and select the item you are interested in or select it directly from the Patch Panel or Network Socket detailed displays :
  
-{{ classdisplay_backendnetworkcable.png }}+{{ classdisplay_backendnetworkcable.png ?nolink }}
  
 ===== Device Network Cable ===== ===== Device Network Cable =====
Line 397: Line 439:
 | Physical interface | Foreign key to a(n) PhysicalInterface | No | | Physical interface | Foreign key to a(n) PhysicalInterface | No |
  
-Friendly name of a device network cable is automatically computed as the concatenation of the network socket's name and the interface's name. 
  
 === Tabs === === Tabs ===
 ^  Tab  ^  Description  ^ ^  Tab  ^  Description  ^
 | Documents | All documents linked to the device network cable | | Documents | All documents linked to the device network cable |
 +
 +<note tip>
 +  * The friendly name of a device network cable is automatically computed as the concatenation of the network socket's name and the interface's name.
 +  * Its label may be automatically computed through the method SetLabel that can be overloaded.
 +</note>
  
 <note warning> <note warning>
Line 412: Line 458:
 In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Device Network Cable dashlet, click on it and select the item you are interested in or select it directly from the Patch Panel or Network Socket detailed displays : In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Device Network Cable dashlet, click on it and select the item you are interested in or select it directly from the Patch Panel or Network Socket detailed displays :
  
-{{ classdisplay_devicenetworkcable.png }}+{{ classdisplay_devicenetworkcable.png ?nolink }}
  
 ===== Direct Network Cable ===== ===== Direct Network Cable =====
Line 431: Line 477:
 | Device #2 | Foreign key to a(n) ConnectableCI | Yes | | Device #2 | Foreign key to a(n) ConnectableCI | Yes |
 | Physical interface #2 | Foreign key to a(n) PhysicalInterface | Yes | | Physical interface #2 | Foreign key to a(n) PhysicalInterface | Yes |
- 
-Friendly name of a device network cable is automatically computed as the concatenation of the two interface's name. 
  
 === Tabs === === Tabs ===
 ^  Tab  ^  Description  ^ ^  Tab  ^  Description  ^
 | Documents | All documents linked to the direct network cable | | Documents | All documents linked to the direct network cable |
 +
 +<note tip>
 +  * The friendly name of a device network cable is automatically computed as the concatenation of the two interface's name.
 +  * Its label may be automatically computed through the method SetLabel that can be overloaded.
 +</note>
  
 <note warning> <note warning>
Line 447: Line 496:
 In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Direct Network Cable dashlet, click on it and select the item you are interested in or select it directly from the interace's display : In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Direct Network Cable dashlet, click on it and select the item you are interested in or select it directly from the interace's display :
  
-{{ classdisplay_directnetworkcable.png }}+{{ classdisplay_directnetworkcable.png ?nolink }}
  
 ===== Breakout Cable ===== ===== Breakout Cable =====
Line 467: Line 516:
 | Rack #1 | Foreign key to a(n) Rack | Yes | | Rack #1 | Foreign key to a(n) Rack | Yes |
 | Rack #2 | Foreign key to a(n) Rack | Yes | | Rack #2 | Foreign key to a(n) Rack | Yes |
- 
-Friendly name of a breakout cable is automatically computed as the concatenation of the two rack's name and the cable's label. 
  
 === Tabs === === Tabs ===
Line 478: Line 525:
  
 <note tip> <note tip>
 +  * The friendly name of a breakout cable is automatically computed as the concatenation of the two rack's name and the cable's label.
 +  * Its label may be automatically computed through the method SetLabel that can be overloaded.
 +</note>
 +
 +<note important>
   * The "Free Links" attribute is read only and automatically computed by the application.   * The "Free Links" attribute is read only and automatically computed by the application.
     * Value is computed as the capacity minus the maximum of used links with a given rack.     * Value is computed as the capacity minus the maximum of used links with a given rack.
Line 483: Line 535:
     * When a relation is created, the "Used Links" attribute is initialized with the value of the patch panel's capacity.     * When a relation is created, the "Used Links" attribute is initialized with the value of the patch panel's capacity.
 </note> </note>
 +
 <note warning> <note warning>
 Proper documentation requires that each breakout cable / patch panel relation that concerns a given  rack has a counterpart with the other rack. Proper documentation requires that each breakout cable / patch panel relation that concerns a given  rack has a counterpart with the other rack.
Line 490: Line 543:
 In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Breakout Cable dashlet, click on it and select the item you are interested in or select it directly from the interace's display : In the Network dashboard that is accessible from a submenu of the standard CMDB overview menu, find the Breakout Cable dashlet, click on it and select the item you are interested in or select it directly from the interace's display :
  
-{{ classdisplay_breakoutcable.png }}+{{ classdisplay_breakoutcable.png ?nolink }}
  
-{{ classdisplay_breakoutcable2.png }}+{{ classdisplay_breakoutcable2.png ?nolink }}
  
 ===== Wiring diagram ===== ===== Wiring diagram =====
 Once connections between Devices, Physical interfaces and Network Sockets are documented, the physical path that connects them all can be visualized through the menu "Wiring..." displayed under the "Other Actions" menu of Connectable CIs, Physical Interfaces and Network Sockets. Once connections between Devices, Physical interfaces and Network Sockets are documented, the physical path that connects them all can be visualized through the menu "Wiring..." displayed under the "Other Actions" menu of Connectable CIs, Physical Interfaces and Network Sockets.
  
-{{ classdisplay_wiring_menu.png }}+{{ classdisplay_wiring_menu.png ?nolink }}
  
 That action displays the wiring layout that connects the device it has been launch from, and all the elements that are part of the cabling path. For instance, from a backend server application : That action displays the wiring layout that connects the device it has been launch from, and all the elements that are part of the cabling path. For instance, from a backend server application :
  
-{{ cabling_wiring3.png }}+{{ cabling_wiring3.png ?nolink }}
  
 <note tip> <note tip>
Line 518: Line 571:
 The extension groups network specific typological elements in the dashlet "Network typology configuration". The extension groups network specific typological elements in the dashlet "Network typology configuration".
  
-{{ overview_group_network_typology_cable.png }}+{{ overview_group_network_typology_cable.png ?nolink }}
  
extensions/teemip-cable-mgmt.1727965951.txt.gz · Last modified: by cnaud

Page Tools