Network Inventory Objects with Segmentation
General |
For the assignment of objects to segments there are 3 principle ways implemented: ▪Initial Assignment Assignment Change Modes: ▪Manual Assignment Change ▪Automatic Assignment Change
|
Initial Assignment |
On creation of an object an initial assignment to segments takes place derived from the respective reference object
|
Manual Assignment Change |
The Network Segment Administrator can assign segments manually to certain objects. He can do that per individual object but also gets support by the system to apply ‘half-automatically’ segment propagation as bulk operations
|
Automatic Assignment Change |
The segment assignment of certain objects is done by the system automatically if the segment assignment of defined reference objects will change. In order to ensure data consistency the Network Segment Administrator cannot change this manually |
Object |
Single Object |
Group Object |
Initial Assignment from Reference Object |
Assignment Change Mode |
Automatic Assignment Reference Object |
|||||
Location System |
ü |
User |
Manual |
|||||||
Location |
ü |
Location System |
Manual |
|||||||
Component |
ü |
Locations |
Manual |
|||||||
Transportcontainer |
ü |
Locations |
Automatic |
Locations |
||||||
Location Group |
ü |
User |
Automatic |
Locations |
||||||
Cableline |
ü |
User |
Automatic |
Cables |
||||||
Ductline |
ü |
User |
Automatic |
Ducts |
||||||
Physical Path |
ü |
Components |
Automatic |
Components |
||||||
Project |
ü |
User |
Manual |
|||||||
Workorder |
ü |
User |
Automatic |
Content |
||||||
Electrical Circuit |
ü |
Location |
Automatic |
Content |
||||||
STM/Ethernet Ring |
ü |
User |
Automatic |
Content |
||||||
MPLS |
ü |
User |
Automatic |
Content |
||||||
VPLS |
ü |
User |
Automatic |
Content |
||||||
IP Pool |
ü |
- |
Manual |
|||||||
IP Subnet |
ü |
IP Pool |
Manual |
|||||||
VLAN Network |
ü |
- |
Manual |
|||||||
VLAN |
ü |
VLAN Network |
Manual |
|||||||
|
|
|||||||||
Single Object |
•A network object can be part of a network segment •Network objects have their own network segment assignment •Depending on the current users network segment membership, it will be visible to the user or not •They may have a property “Segmentation” of possible values Local, Distributed and External |
|||||||||
Group Object |
Group objects are collections of different single objects. They have the segmentation values of all their objects.
|
|||||||||
Initial assignment from Reference Object |
Describes the origin of the initial assignment of the object. |
|||||||||
Automatic assignment from Reference Object |
Describes the origin of the automatic assignment of the object. |
|||||||||
Objects not yet implemented for network segmentation
|
The amount of implemented functions for Network Segmentation is dependent to the requirements and priorities from the network documentation practice and is subject to future development. The implementation of Network Segmentation therefore covers the main areas of ConnectMaster® but without claiming a theoretically 100% approach of all details and special cases. The following Network-Inventory Objects / Functionality Areas are currently not part of Network Segmentation functionality. This means, that by using the listed objects and functions the segmentation cannot be checked. Therefore the visibility/editability cannot be checked by the system and therefore is possible for users of all segments.
|
|||||||||
|