Difference between revisions of "UM:Objects"

428 bytes added ,  13:46, 2 January 2013
m (→‎Overview: links to related objecys)
Line 107: Line 107:
= Container Objects =
= Container Objects =
Container objects (or simply ''containers'') serve as building blocks for creating logical service hierarchy. Containers can have subnets, nodes, conditions, or other containers as child objects. Containers can be created in '''Infrastructure Services''' tree. Existing nodes and subnets can be added to containers by using '''Bind''' operation, and removed by using '''Unbind''' operation.
Container objects (or simply ''containers'') serve as building blocks for creating logical service hierarchy. Containers can have subnets, nodes, conditions, or other containers as child objects. Containers can be created in '''Infrastructure Services''' tree. Existing nodes and subnets can be added to containers by using '''Bind''' operation, and removed by using '''Unbind''' operation.
= Condition Objects =
Conditions may represent more complicated status checks because each condition can have a script attached. Interval for evaluation of condition status is configured in [[Server Configuration Variables]] as ConditionPollingInterval with default value 60 seconds. Input values for the condition script can be added in the Data tab. Such values are accessible via $1, $2, ... variables inside the script.


= Node Objects =
= Node Objects =
Node objects (or ''nodes'') represent computers and other network-enabled devices (such as routers and switches) in your network. They have a lot of attributes controlling all aspects of interaction between NetXMS server and managed node. For example, the attributes specify what data must be collected, how node status must be checked, which protocol versions to use etc. Node objects contain one or more interface objects. The system creates interface objects automatically during configuration polls.
Node objects (or ''nodes'') represent computers and other network-enabled devices (such as routers and switches) in your network. They have a lot of attributes controlling all aspects of interaction between NetXMS server and managed node. For example, the attributes specify what data must be collected, how node status must be checked, which protocol versions to use etc. Node objects contain one or more interface objects. The system creates interface objects automatically during configuration polls.


57

edits