A number of Opmantek products use a common node configuration infrastructure, which supports standard, product-specific and custom node attributes. This page describes both the core properties and outlines the product-specific ones.
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.
The internal name of the node. This is used for identifying and displaying the node, not for communication with the node!
The DNS name, unqualified host name or main IP address for this node. Using a fully qualified DNS host name is recommended.
A list containing any secondary IP addresses that should also be associated with this node.
The (single) group that this node belongs to, which is used to control what nodes a user is allowed to see.
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)|
Properties for Licensing And Activation
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.
By default nodes are enabled for all products. Nodes are disabled if and only if they are explicitely marked as disabled.
|activated.<productname>||If set to 0, the node is disabled for <productname>. |
If unset or set to any non-zero value, the node is considered active.
Note: The activation properties are within a subhash/subdocument, and the listing above used MongoDB dot-notation to indicate that (just like you would access such properties in an opEvents policy rule or an opConfig compliance rule).
opConfig requires two extra sets of properties for correct communication with a node, which are stored in the connection_info and os_info subhash/subdocuments. The os_info information is primarily used in command set definitions, and customized command sets might not use any of these properties.
The properties given in italic are optional and only relevant for specific types of devices.
The type of OS or system 'personality', which is used for determining what command sets are applicable.
Which credential set to use when authenticating to this node.
Which transport mechanism to use for connecting to this node. Valid choices are "SSH" or "Telnet".
Whether setting up paging requires privileged mode. Only relevant on Cisco PIX/ASA.
What line separator character(s) to send to the node. By default the patform's 'newline' character sequence is used.
The name of the phrasebook macro to use for line continuation.
|connection_info.connect_options||Any extra, non-standard options for the connection. See the documentation for |
Net::CLI::Interact for details. If present, this must be an Array in JSON format.
|os_info.os||The general OS type. Required to determine what command sets are applicable.|
The OS Version identifier.
The Major Release Number extracted from the OS Version.
The Train of the OS version. Relevant for Cisco devices only.
The OS Platform as extracted from the Version.
The OS Image. Relevant mainly for Cisco devices.
The enabled Feature Sets of this system. Relevant mainly for Cisco devices.
The current version of opEvents, 1.2.6, does not make use of product-specific properties.
NMIS uses further properties to control its operations, mostly things like SNMP-related identities, node active and collect flags, 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
|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|
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|
|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)