Cabling - Revision history

Andriyanov at 20:11, 5 November 2013

2013-11-05T20:11:39Z

Andriyanov at 20:04, 5 November 2013

2013-11-05T20:04:55Z

Andriyanov at 19:54, 5 November 2013

2013-11-05T19:54:38Z

Andriyanov at 19:43, 5 November 2013

2013-11-05T19:43:31Z

Andriyanov: Created page with "This page is for thoughts about documenting of cables, patch-panels, splices and cross-connects in RT. ==Object types=="

2013-11-05T19:31:28Z

Created page with "This page is for thoughts about documenting of cables, patch-panels, splices and cross-connects in RT. ==Object types=="

New page

This page is for thoughts about documenting of cables, patch-panels, splices and cross-connects in RT.

==Object types==

@@ Line 7: / Line 7: @@
 While Cross is much like a traditional object, Cable is a fundamentally new type. It has:
-  * physical medium type (SM fiber, twisted pair, etc)
+* physical medium type (SM fiber, twisted pair, etc)
-  * a model
+* a model
-  * named fibers. Actually Cable is a group of crossable cables (fibers)
+* named fibers. Actually Cable is a group of crossable cables (fibers)
-  * a set of Crosses which a Cable belongs to
+* a set of Crosses which a Cable belongs to
-  * length and shape which could be represented visually on a map
+* length and shape which could be represented visually on a map
 ==Connection types==
@@ Line 17: / Line 17: @@
 A Cross contains connections between fibers of its Cables and its ports (backlinks). All these connections are inside the Cross (none of them does not occupy a port connector on Cross'es front). These connections could be of types:
-  * loops (two ports of Cross connected)
+* loops (two ports of Cross connected)
-  * terms (one of the fibers connected to one of the ports)
+* terms (one of the fibers connected to one of the ports)
-  * xconnect (two fibers connected)
+* xconnect (two fibers connected)
 Each of such connection could have a type (i.e. splice, glued, mates, soldering, jointing)
@@ Line 27: / Line 27: @@
 ==Basic functionality==
-  * fiber path tracing (view the full path of the joined link by clicking the fiber in Cable, Cross or port);
+* fiber path tracing (view the full path of the joined link by clicking the fiber in Cable, Cross or port);
-  * auto-establishing an L2-link if the joined L1 link traces to another empty L2 port;
+* auto-establishing an L2-link if the joined L1 link traces to another empty L2 port;
-  * highlighting of ports where L1 = L2, !L1 && L2, L1 != L2;
+* highlighting of ports where L1 = L2, !L1 && L2, L1 != L2;
-  * ability to mark cuts and damages of fibers in a Cable;
+* ability to mark cuts and damages of fibers in a Cable;
-  * ability to document spare lengths of Cables in (near) Crosses;
+* ability to document spare lengths of Cables in (near) Crosses;
-  * ability to split and join Cables in Crosses;
+* ability to split and join Cables in Crosses;
-  * mass connecting or terminating of Cable's fibers in Crosses;
+* mass connecting or terminating of Cable's fibers in Crosses;
-  * displaying of Cross map in a table view. Incoming fibers are grouped by their cables, each has a text describing how it is connected, different cables should be placed in front of each other, if possible;
+* displaying of Cross map in a table view. Incoming fibers are grouped by their cables, each has a text describing how it is connected, different cables should be placed in front of each other, if possible;
-  * displaying of Cables, links, Crosses on the map (different GIS compatibility would be nice);
+* displaying of Cables, links, Crosses on the map (different GIS compatibility would be nice);
-  * adding Cables and Crossed by drawing them on the map (using GIS API) would be nice;
+* adding Cables and Crossed by drawing them on the map (using GIS API) would be nice;
 ==Questions==
-  * Should we bind cables to the Crosses' coordinates or not? (yes). Move cables with Crosses or not (ask, if not - unbind);
+* Should we bind cables to the Crosses' coordinates or not? (yes). Move cables with Crosses or not (ask, if not - unbind);
-  * Shared media types (electrical power jacks, wireless, POTS and so on);
+* Shared media types (electrical power jacks, wireless, POTS and so on);
 ==DB schema==
-CREATE TABLE `CrossLoops` (
+  CREATE TABLE `CrossConnects` (
-  `node_id` int,
+    `node_id` int,
-  `port_a` int,
+    `cable_a` int,
-  `port_b` int,
+    `cable_b` int,
-  `type` int
+    `port_a` int,
-);
+    `port_b` int,
-CREATE TABLE `CrossTerms` (
+  CREATE TABLE `CrossLoops` (
-  `node_id` int,
+    `node_id` int,
-  `node_port` int,
+    `port_a` int,
-  `cable_id` int,
+    `port_b` int,
-  `cable_port` int,
+    `type` int
-  `type` int
+  );
 );

← Older revision		Revision as of 20:04, 5 November 2013
Line 25:		Line 25:

	Basic principle is: L2 port could not be linked with more than one L2 ports. Generally, any port could not be linked more than 2 times (L1 and L2), but there is an exception: multi-fiber transmitters in one physical port. Here is the proposal: mark each side of a link with unique text mark (like RX, TX) and forbid having multiple L1 links for single port with equal or missing marks. So, the rule is: each port could not have more than one L2 link, and each of its L1 links must have a unique mark.		Basic principle is: L2 port could not be linked with more than one L2 ports. Generally, any port could not be linked more than 2 times (L1 and L2), but there is an exception: multi-fiber transmitters in one physical port. Here is the proposal: mark each side of a link with unique text mark (like RX, TX) and forbid having multiple L1 links for single port with equal or missing marks. So, the rule is: each port could not have more than one L2 link, and each of its L1 links must have a unique mark.
		+
		+	==Basic functionality==
		+	* fiber path tracing (view the full path of the joined link by clicking the fiber in Cable, Cross or port);
		+	* auto-establishing an L2-link if the joined L1 link traces to another empty L2 port;
		+	* highlighting of ports where L1 = L2, !L1 && L2, L1 != L2;
		+	* ability to mark cuts and damages of fibers in a Cable;
		+	* ability to document spare lengths of Cables in (near) Crosses;
		+	* ability to split and join Cables in Crosses;
		+	* mass connecting or terminating of Cable's fibers in Crosses;
		+	* displaying of Cross map in a table view. Incoming fibers are grouped by their cables, each has a text describing how it is connected, different cables should be placed in front of each other, if possible;
		+	* displaying of Cables, links, Crosses on the map (different GIS compatibility would be nice);
		+	* adding Cables and Crossed by drawing them on the map (using GIS API) would be nice;
		+
		+	==Questions==
		+	* Should we bind cables to the Crosses' coordinates or not? (yes). Move cables with Crosses or not (ask, if not - unbind);
		+	* Shared media types (electrical power jacks, wireless, POTS and so on);
		+
		+	==DB schema==
		+	CREATE TABLE `CrossConnects` (
		+	`node_id` int,
		+	`cable_a` int,
		+	`cable_b` int,
		+	`port_a` int,
		+	`port_b` int,
		+	`type` int
		+	);
		+
		+	CREATE TABLE `CrossLoops` (
		+	`node_id` int,
		+	`port_a` int,
		+	`port_b` int,
		+	`type` int
		+	);
		+
		+	CREATE TABLE `CrossTerms` (
		+	`node_id` int,
		+	`node_port` int,
		+	`cable_id` int,
		+	`cable_port` int,
		+	`type` int
		+	);

@@ Line 13: / Line 13: @@
    * length and shape which could be represented visually on a map
-A Cross contains connections between fibers of its Cables and its ports. All these connections are inside the Cross (none of them does not occupy a port connector on Cross'es front). These connections could be of types:
+==Connection types==
    * loops (two ports of Cross connected)
    * terms (one of the fibers connected to one of the ports)
    * xconnect (two fibers connected)
 Each of such connection could have a type (i.e. splice, glued, mates, soldering, jointing)

← Older revision		Revision as of 19:43, 5 November 2013
Line 2:		Line 2:

	==Object types==		==Object types==
		+	2 new object types: Cross and Cable.
		+
		+	Cable is a solid cable connecting two or more Crosses. It could be cut and terminated/connected by some of its fibers in any of its Crosses.
		+
		+	While Cross is much like a traditional object, Cable is a fundamentally new type. It has:
		+	* physical medium type (SM fiber, twisted pair, etc)
		+	* a model
		+	* named fibers. Actually Cable is a group of crossable cables (fibers)
		+	* a set of Crosses which a Cable belongs to
		+	* length and shape which could be represented visually on a map
		+
		+	A Cross contains connections between fibers of its Cables and its ports. All these connections are inside the Cross (none of them does not occupy a port connector on Cross'es front). These connections could be of types:
		+	* loops (two ports of Cross connected)
		+	* terms (one of the fibers connected to one of the ports)
		+	* xconnect (two fibers connected)
		+	Each of such connection could have a type (i.e. splice, glued, mates, soldering, jointing)