...
Common Properties
These are used by all Opmantek products (exception: NMIS does not use the addresses property). Only the first two, name and hostname are absolute necessary properties. The properties shown in italic are not directly interpreted by the applications and are completely optional.
| Property Name | Description |
|---|---|
| name | The internal name of the node. This is used for identifying and displaying the node, not for communication with the node! |
| hostnamehost | The DNS name, unqualified host name or main IP address for this node. Using a fully qualified DNS host name is recommended. |
| addresses | A list containing any secondary IP addresses that should also be associated with this node. |
| group | The (single) group that this node belongs to, which is used to control what nodes a user is allowed to see. |
| notes | Free-form notes for a node, which are shown on the relevant context pages. (optional) |
| comments | A list of originator- and time-tagged comments for this node. (optional, supported in opEvents 2.0 and newer) |
| location | The location of the node. (optional) |
| businessService | The service the node provides. (optional) |
...
Both opConfig (2.1 and up) and opEvents (1.2.3 and up) support per-node activation and licensing, which is controlled by the properties described below. (NMIS doesn't use any of these.)
If a node is disabled for a particular product, then it is completely ignored by this product: for opEvents that means no events are processed for this node, for opConfig no command sets would be run for the node and so on.
...
The current version of opEvents, 1.2.36, does not make use of product-specific properties.
...
NMIS Properties
When a node is refreshed or imported from NMIS, many of its properties in NMIS are also transferred. This includes certain NMIS uses further properties to control its operations, mostly things like SNMP-related identities, node active and collect flags and the like., etc. The table below describes the most important properties that NMIS interprets or understands.
Whenever a node in opConfig or opEvents is refreshed/imported from NMIS, all of NMIS' node properties are also transferred. These properties are currently not used by opConfig or opEvents, but will show up when you export a node using opnode_admin. Your opEvents and opConfig policies can make use of these properties, you can edit them with opnode_admin (and, to some extent, via the GUI if you modify the configuration variables opevents_gui_node_summary_list and/or opconfig_gui_node_summary_list).
| Property Name | Description |
|---|---|
| active | whether the node is active and handled by NMIS or should be ignored |
| collect | whether SNMP data should be collected from this node |
| ping | whether reachability statistics should be collected for this node |
| model | what type of device this is (default: "automatic") |
| version | snmpv1, snmpv2c or snmpv3; relevant only if collect is true |
| community | read-only community string for access using snmpv1 or snmpv2c |
| netType | wan or lan |
| roleType | core, access or distribution |
| username authkey authpassword authprotocol privkey privpassword privprotocol | authentication parameters for SNMP Version 3 |
| port | which port to use for SNMP access (default: 161) |
| timezone | which timezone this system is in, numeric offset |
| webserver | whether the node runs a webserver. if true, a link to the node is presented in the NMIS GUI |
| threshold | whether thresholds are to be processed for this node |
| cbqos | whether Quality of Service data should be collected for this node (if the device and model support QoS) |