Table of Contents |
---|
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 host,are absolutely necessary properties.
...
Status | ||||
---|---|---|---|---|
|
opEvents Properties
The current version of opEvents , 1.2.6, does not make use of does have a product-specific propertiesnode property: activated.opEvents
NMIS 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 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 - the three layers of the Cisco three-layer hierarchical network model | |
username | authkeyprivprotocol | privkeyauthentication and privacy parameters for SNMP Version 3 |
authkey privkey | Alternative password parameters for SNMP Version 3. Optionally, theauthkey and privkey can be used so that a plain text password does not have to be specified (see Net::SNMP). The snmpkey utility can be used to create the hexadecimal key string with the authoritativeEngineID (MAC address) for the destination device (see snmpkey). | |
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) |
Status | ||||||
---|---|---|---|---|---|---|
|