Netmond V2. Object directive
The Object directive creates and describe primary monitoring target.
Object is a nodal entity in Netmond
hierarchy with personal IP address, like router, switch, host, etc.
Object may have child objects like interfaces, services.
Monitoring of the Object is made by polling methods
and by SNMP traps bound to it.
During monitoring process Object status checked (UP, DOWN, NONE)
and a number of SNMP variables values are saved to internal variables.
The Object has a number of built-in variables,
and can have custom Soft Variables
Saving methods, bound to Object,
makes reporting and data analysis.
The Object may appear in global level of Netmond
configuration file only. Directive syntax is:
- Object "name" {
- Address "address"
- [ Description "description" ]
- [ DataDir "directory" ]
- [ Polling seconds ]
- [ Timeout seconds ]
- [ Retries counter ]
- [ Saving seconds ]
- [ $Variable oid ] ...
- [ Method
( Ping | Router |
SNMP | DNS | Radius |
Tacacs | "name" ) [ "arguments" ] ] ...
- [ Trap
( Generic | "name" ) [ "arguments" ] ] ...
- [ Save
( Router | "name" ) [ "arguments" ] ] ...
- [ Service
"name" { parameters } ] ...
- [ Interface
( index | "name" ) [ { parameters } ] ] ...
- [ BGP
number [ { parameters } ] ] ...
- [ Env Temp
[ { parameters } ] ]
- }
- Declare object with IP address, define its parameters, variables,
polling methods, saving methods, bind subobjects to it.
- name
- Unique object's name.
- address
- Object's network address - IP or FQDN (Full Qualified Domain Name).
- description
- Short one-line description.
- directory
-
Alternative data saving directory in Netmond hierarchy. Default dirname is a object's "name"
- Variable oid
- New Soft Variable and its SNMP object
identifier (OID) declaration. OID must have four elements 1.3.6.1. at least,
and finish with .0, for example:
- $sysContact 1.3.6.1.2.1.1.4.0
- $sysLocation 1.3.6.1.2.1.1.6.0
- Method SNMP "community" { $sysContact $sysLocation }
Unlimited number of all kinds subobjects can be bound to Object.
Roughly, we may classify all devices connected to network as a
Router, a Switch, a Server or a Host,
depending on their functionality and mission.
Typically, network Interfaces
and controllers are monitored for a Router and for a Switch.
Netmond built-in trap processing service (activated with
Trap Generic directive) and a
special built-in polling methods
Method Router is used to do this.
Additionally, this polling method allows to control traffic flows and to accumulate
statistics for various reports and graphs.
Fat border Routers may have BGP
dynamic routing protocol up, and may have a number of BGP Peers.
Also, Cisco Router may have a number of environment monitoring
probes Env Temp.
These subobjects are monitored with Method Router
and Trap Generic too.
For Servers, it is important to monitor network and
Application services. It can be made using
Service subobject with custom polling and saving methods.
But the Service is a universal entity.
You can monitor any subsystem on a remote host - memory, disk subsystem, processes,
etc. using this abstraction.
Arbitrary network Host accessibility can be simply monitored with built-in
Method Ping
or with simple custom ICMP-echo -based polling method.
This Object may have not any additional subobject.
See also:
Method directive
Trap directive
Save directive
Remote host accessibility checking example
© 1998-2002, Rinet Software
|