User Tools

Site Tools


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
Next revisionBoth sides next revision
extensions:teemip-cable-mgmt [2024/05/21 11:31] – [Network Socket] cnaudextensions:teemip-cable-mgmt [2024/05/21 11:45] – [Physical Interface] cnaud
Line 214: Line 214:
 |  All other cases  |||  set  |  Ready  | |  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:teemip-cable-mgmt#cross_connect|below]]
  
 Network sockets implements three 1:1 relations. As the datamodel doesn't provide such attributes by default, these 1:1 relations are automatically computed when objects are created, modified or deleted: when one side of the relation is changed, the other sides (new and old when appropriate) are changed. These relations are:  Network sockets implements three 1:1 relations. As the datamodel doesn't provide such attributes by default, these 1:1 relations are automatically computed when objects are created, modified or deleted: when one side of the relation is changed, the other sides (new and old when appropriate) are changed. These relations are: 
Line 291: Line 293:
  
 <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.
 </note> </note>
  
extensions/teemip-cable-mgmt.txt · Last modified: 2024/06/26 15:33 by cnaud