extensions:teemip-cable-mgmt
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| extensions:teemip-cable-mgmt [2024/05/14 13:04] – [Patch Panel] cnaud | extensions:teemip-cable-mgmt [2024/11/08 09:40] (current) – [Cable Management] cnaud | ||
|---|---|---|---|
| Line 7: | Line 7: | ||
| level_hidden | level_hidden | ||
| collector_hidden | collector_hidden | ||
| - | version | + | version |
| - | release_dt | + | release_dt |
| - | TeemIp | + | TeemIp |
| - | iTop : 3.1+ | + | iTop : 3.1.2+ |
| code : teemip-cable-mgmt | code : teemip-cable-mgmt | ||
| localization | localization | ||
| Line 19: | Line 19: | ||
| keyword_tags | keyword_tags | ||
| dependencies_s | dependencies_s | ||
| - | download_wiki | + | download_wiki |
| github_wiki | github_wiki | ||
| - | php-max | + | php-max |
| ---- | ---- | ||
| Line 27: | Line 27: | ||
| This extension brings to TeemIp objects from the cabling world that will allow you to document the physical connections between CIs. | This extension brings to TeemIp objects from the cabling world that will allow you to document the physical connections between CIs. | ||
| - | < | + | < |
| </ | </ | ||
| ===== Revision History ===== | ===== Revision History ===== | ||
| ^ Version | ^ Version | ||
| - | | 1.3.0 | 2024-0x-xx | + | | **1.3.1** |
| - | | | + | | 1.3.0 | 2024-06-26 |
| + | | 1.2.0 | 2023-12-07 | ||
| | 1.1.0 | 2023-07-24 | | 1.1.0 | 2023-07-24 | ||
| | 1.0.0 | 2022-12-04 | | 1.0.0 | 2022-12-04 | ||
| ===== Features ===== | ===== Features ===== | ||
| - | 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: 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 }} | ||
| Line 81: | Line 82: | ||
| ==== Global IP Settings ==== | ==== Global IP Settings ==== | ||
| - | Under the **Other Settings** fieldset, the **Allow cabling toward another organizations** | + | Under the **Other Settings** fieldset, the **Allow cabling toward another organizations** |
| {{ cabling_ipsettings.png }} | {{ cabling_ipsettings.png }} | ||
| Line 94: | Line 95: | ||
| | Name | Alphanumeric string | Yes | | | Name | Alphanumeric string | Yes | | ||
| | Organization | Foreign key to a(n) Organization | Yes | | | Organization | Foreign key to a(n) Organization | Yes | | ||
| - | | Status| Possible values: Implementation, | + | | Status| Possible values: Implementation, |
| | Location | Foreign key to a(n) Location | Yes | | | Location | Foreign key to a(n) Location | Yes | | ||
| | 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 | | ||
| + | | Ready sockets | Number of network sockets with status ' | ||
| | Connector | Foreign key to a(n) Interface Connector \\ Brought by the [[extensions: | | Connector | Foreign key to a(n) Interface Connector \\ Brought by the [[extensions: | ||
| | External reference | Alphanumeric string | No | | | External reference | Alphanumeric string | No | | ||
| Line 131: | Line 134: | ||
| === 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 | + | 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 |
| === Creating back end network cables === | === Creating back end network cables === | ||
| Line 145: | Line 148: | ||
| 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, | 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, | ||
| </ | </ | ||
| - | ===== Network Socket ===== | + | ===== Network Socket ===== |
| {{icons8-wired-network.png | {{icons8-wired-network.png | ||
| A network socket is the passive physical piece of hardware where you plug a network cable to establish a link between different network devices. | A network socket is the passive physical piece of hardware where you plug a network cable to establish a link between different network devices. | ||
| Line 165: | Line 168: | ||
| | Physical interface | Foreign key to a(n) Physical Interface | No | | | Physical interface | Foreign key to a(n) Physical Interface | No | | ||
| | Network socket | Foreign key to a(n) Network Socket | No | | | Network socket | Foreign key to a(n) Network Socket | No | | ||
| + | | Cross Connect | Foreign key to a(n) Cross Connect | Automatically computed | | ||
| | **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 | | ||
| Line 179: | Line 183: | ||
| * When standing alone, attribute Location is mandatory but Rack and Patch panel must **NOT** be set. | * When standing alone, attribute Location is mandatory but Rack and Patch panel must **NOT** be set. | ||
| </ | </ | ||
| + | |||
| + | === Displaying a Network Socket === | ||
| + | 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 }} | ||
| Network Sockets have 2 sides: | Network Sockets have 2 sides: | ||
| Line 186: | Line 195: | ||
| <note warning> | <note warning> | ||
| A few rules are enforced at front and back ends' levels. | A few rules are enforced at front and back ends' levels. | ||
| - | * On the front end side, a network socket cannot be connected to both a remote network socket and a connectable CI. | + | * On the front end side, |
| + | * A network socket cannot be connected to both a remote network socket and a connectable CI. | ||
| + | * A network socket may belong to a Cross Connect and may be connected to a remote network socket at the same time. | ||
| * The front end network socket and the back end one cannot be the same. | * The front end network socket and the back end one cannot be the same. | ||
| </ | </ | ||
| - | Attribute Status is read only and automatically computed: | + | Attribute |
| * If no back end network socket is set, status is set to **Inactive**, | * If no back end network socket is set, status is set to **Inactive**, | ||
| * If a back end network socket is set but if no physical interface nor network socket is set, status is set to **Ready**, | * If a back end network socket is set but if no physical interface nor network socket is set, status is set to **Ready**, | ||
| - | * If a back end network socket is set and if a physical interface or a network socket is set, status is set to **Active**. | + | |
| + | | ||
| + | In other words: | ||
| + | ^ Front End Information | ||
| + | ^ Physical interface | ||
| + | | * | * | * | unset | Inactive | ||
| + | | unset | * | set and active | ||
| + | | unset | set | * | set | Active | ||
| + | | set | unset | unset | set | Active | ||
| + | | All other cases ||| set | Ready | | ||
| + | |||
| + | |||
| + | Attribute **Cross Connect**, is set or unset from the Cross Connect objet, at the time where the Network Socket is attached to the Cross Connect, as part of the local or peer unit information. See [[extensions: | ||
| Network sockets implements three 1:1 relations. As the datamodel doesn' | Network sockets implements three 1:1 relations. As the datamodel doesn' | ||
| Line 200: | Line 223: | ||
| * 1:1 relation between the network socket and a back end one. | * 1:1 relation between the network socket and a back end one. | ||
| - | === Displaying a Network Socket === | ||
| - | 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 }} | ||
| ===== Cross Connect ===== | ===== Cross Connect ===== | ||
| Line 275: | Line 294: | ||
| <note warning> | <note warning> | ||
| - | A physical interface cannot be connected to both a network socket and another physical interface | + | A physical interface cannot be connected to both a network socket and another physical interface. |
| </ | </ | ||
extensions/teemip-cable-mgmt.1715684682.txt.gz · Last modified: 2024/05/14 13:04 by cnaud