ISO10164-11 Monitor Objects MIB
===============================

Short Description
=================
These classes have been minimally implemented:
  - scanner
  - monitorMetric
  - movingAverageMeanMonitor (EWMA)

You should look at the shell scripts:
  - MON+LOG.sh
  - MONCREATE.sh
  - EWMACREATE.sh
to see how a manager must mcreate these objects to watch
some Gauge/Counter attributes of anothe MO in the MIT.
These shells are examples of watching the 'nUsers' attribute
of the uxObj1 MO in the 'sma'.

You can set the GaugeThreshold values, e.g. using the 'cmisbrowser'
once your manager has mcreated the appropriate Monitor Objects.

Other Changes to 3.2+ release
=============================
In osimis/agent/gms changes to :
  - SmiAsn.py SmiAsn.h Smi2Asn.py SmiSntx.h/.cc SmiAttr.h/.cc
  - Smi3Asn.py 

Smi2Asn.py and SmiAsn.py have same ASN.1 module name "SMI",
this makes it impossible to IMPORT Smi2Asn.py definitions into SmiAsn.py.
I added Smi3Asn.py (Module name SMI3) to let me do this).  The reason
for this is I'd rather let pepsy do as much work as possible, rather
than add lots of handcoded asn.1 to SmiAsn.py.

A new attribute/syntax was also added (TimePeriod) to Smi2Asn.py.
It is used in monmet_mib/MIB.gdmo.  

Minor changes to osimis/agent/sma: Makefile, Sma.h, 

Bugs/Future Work/Comments
=========================

1) Filling in the RDN of the "observedObjectInstance" in the
   qualityofServiceAlarm notification is the only field that
   might not work ?  At least 'readevlog' prints nothing.

2) A minor simplification was made in the GDMO file.
   GaugeThresholds (builtin OSIMIS type) was used instead
   of writing a new SeverityIndicatingGaugeThreshold attribute
   type.  These are identical, except the latter has an optional
   'perceived severity' field.  We will correct this in a future
   version, but some handcoding into osimis/agent/gms/SmiAsn.py
   is needed to add this.

3) This always been tested watching integer Gauges or Counters.
   It has never been tested against watching a Real Gauge.
   
4) No Scheduling capabilities (Conditional Packages in scanner)
   have been implemented.

5) in oidtable.at I had to use type "ObjectClass" instead of "AttributeId"
   These are identical ASN.1 definitions/types.  I got 'parse' failure
   during mcreate if I used type of AttributeId.  This will be
   investigated.

Contacts
=========
Please send comments/bug fixes to icm.group@tel.vtt.fi.
James.Reilly@tel.vtt.fi implemented scanner/monitorMetric,
and Henryka.Jormakka@tel.vtt.fi implemented movingAverageMeanMonitor.


