Netmond V2. Service directive
The Service directive creates and describe second level subobject
in a Netmond hierarchy.
This is child of Object.
It has no personal IP address. Usually, Service subobject reflects
some network service on an Object.
No predefined polling methods exist for Service.
You have to define custom Polling methods.
Custom Traps can be defined for Service
too.
The Service status is determined as integral result of
Polling methods execution. It can be UP, DOWN or NONE.
The Service can have custom Soft Variables
No predefined saving methods exist for Service.
You have to define custom Saving methods.
The
Service directive can be used only inside
Object definition block.
Directive syntax is:
- Service "name" {
- [ Description "description" ]
- [ DataDir "directory" ]
- [ $Variable oid ] ...
- [ Method
( SNMP | DNS | Radius |
Tacacs | "name" ) [ "arguments" ] ] ...
- [ Trap
"name" [ "arguments" ] ] ...
- [ Save
"name" [ "arguments" ] ] ...
- }
- Declare object's service, define its parameters, variables, methods, traps.
- name
- Unique service name.
- description
- Short one-line description.
- directory
- Alternative data saving directory in Netmond
hierarchy. Default dirname is a service "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 }
The Service is a universal entity. You can monitor any
subsystem on a remote host - memory, disk subsystem, processes, etc. using
this abstraction.
See also:
Method directive
Object directive
Simple network services checking example
© 1998-2002, Rinet Software
|