Release Notes for Covalent SNMP.


The Covalent SNMP module needs to have a 'var' directory
as defined by the SNMPvar directive in the httpd.conf file. It also
needs read-write access to this directory.
Otherwise it cannot create a persistent file to allow restarts of the
Apache HTTP server.


The Covalent SNMP has a installation feature that starts and
stops the Apache Web server during the installation of the SNMP module.
In combination with faststart the installer checks to quickly for the
exit status of the 'start/stop' procedure. Although, an error message
is presented (message says: "An error occurred while adding the
SNMPv3 user: This may be caused by an already running webserver")
your installation  will be completed correctly.
Just make sure that indeed no other Apache processes were running.



The following MIB modules are implemented by the SNMP agent.
1) Application specific MIB modules (IETF defined)
    WWW-MIB
    -   The 'wwwServiceType' is only implemented as 'wwwServer'.
            No proxy or client.
    -   The 'wwwDocCtrlLastNLock' is implemented as read-only.
    NETWORK-SERVICES-MIB
2) Enterprise specific MIB modules
    COVALENT-GENERIC-MIB
    COVALENT-WWW-RESP-NOTIFY-MIB
    -   The 'ctNotifyEnableTable' is not implemented yet. All traps
        associated with a 4xx and 5xx response are send.
    COVALENT-APACHE-CONFIG-MIB
    -   The 'CtConfigServiceTable' is implemented as read-only.
    COVALENT-APACHE-STATUS-MIB
    -   The 'ctServerStatusClient', 'ctServerStatusRequest' and
        'ctServerStatusVirtualHost' are only meaningfull is the
        extended status is on.
        (COVALENT-APACHE-CONFIG-MIB : ctExtendedStatus == enabled)
    COVALENT-APACHE-MODULES-MIB
3) Network Management Framewrok MIB modules (IETF defined)
    SNMPv2-MIB
    SNMP-FRAMEWORK-MIB      (Used for SNMPv3)
    SNMP-MPD-MIB            (Used for SNMPv3)
    SNMP-USER-BASED-SM-MIB  (Used for SNMPv3)
    SNMP-VIEW-BASED-ACM-MIB (Used for SNMPv3)


(c) Copyrights 2001, Covalent Technologies, Inc.
