check_idm_sync (Visit this link)
from 0 votesCheck Novell Identity Manager synchronization between eDirectory trees using ldap.
+++ What is this check program for ?
This check program is used to monitor the idm (Nocell Identity Manager) synchronization process between edirectory trees. It uses several user objects and their attributes as well as passwords to check the data flow between them. So you can realize a end to end monitoring for the edirectory drivers using the power of Nagios.
This script uses ldap to do all user object modifications and is written as a bash script.
+++ Description
Please see the PNG drawing below, I tried to put all there in.
For eDirectory Objects please refer to the comments in the check program itself.
+++ Usage
check_idm_sync.sh [-]
Driverside: This defines the side of the driver you ware and would like to check. Please see the drawing for informations.
If you would like to invert the check results put a - in front of the Driverside. This is useful if you have a one way synchronization and want to check that nothing comes back. So Nagios would normally show this as an error and with that inverted result you get the OK message. When something is received it will change to an ERROR.
Timedelay is set by default to 65 seconds. At the beginning set it to Nagios check interval (in seconds) + 5 seconds tolerance. We do the check every minute, so we set it to 65 seconds.
+++ Things to take care of
* time has to be synchronized between the edirectory trees and the nagios server
* idm drivers should allow data flow for users and the specified attributes
* test user has to be created as well as a Nagios account that can write to those user objects
* check programs are written to run on each idm server itself. We do have on every server a local Nagios installation. Small changes were necessary if they run on a central Nagios server
* The ldap statements inside the check program use the local ldap server
+++ Changelog
# v 1.0 - initial version
# v 1.1 - I modified the ldap attributes to use single value attributes. Before street and postOfficeBox were multi value attributes and made sometimes problems when the edirectory or server was restarted. I changed it to use the single value attributes location (l) and the department (ou). Else I added the edir user that is modified to be listed in the service output. If you have problems with multiple drivers that makes it easier to find the user that is not correctly synchronized.
+++ Enhancements
* Please put some feedback below what you would like to see
This check program is used to monitor the idm (Nocell Identity Manager) synchronization process between edirectory trees. It uses several user objects and their attributes as well as passwords to check the data flow between them. So you can realize a end to end monitoring for the edirectory drivers using the power of Nagios.
This script uses ldap to do all user object modifications and is written as a bash script.
+++ Description
Please see the PNG drawing below, I tried to put all there in.
For eDirectory Objects please refer to the comments in the check program itself.
+++ Usage
check_idm_sync.sh [-]
Driverside: This defines the side of the driver you ware and would like to check. Please see the drawing for informations.
If you would like to invert the check results put a - in front of the Driverside. This is useful if you have a one way synchronization and want to check that nothing comes back. So Nagios would normally show this as an error and with that inverted result you get the OK message. When something is received it will change to an ERROR.
Timedelay is set by default to 65 seconds. At the beginning set it to Nagios check interval (in seconds) + 5 seconds tolerance. We do the check every minute, so we set it to 65 seconds.
+++ Things to take care of
* time has to be synchronized between the edirectory trees and the nagios server
* idm drivers should allow data flow for users and the specified attributes
* test user has to be created as well as a Nagios account that can write to those user objects
* check programs are written to run on each idm server itself. We do have on every server a local Nagios installation. Small changes were necessary if they run on a central Nagios server
* The ldap statements inside the check program use the local ldap server
+++ Changelog
# v 1.0 - initial version
# v 1.1 - I modified the ldap attributes to use single value attributes. Before street and postOfficeBox were multi value attributes and made sometimes problems when the edirectory or server was restarted. I changed it to use the single value attributes location (l) and the department (ou). Else I added the edir user that is modified to be listed in the service output. If you have problems with multiple drivers that makes it easier to find the user that is not correctly synchronized.
+++ Enhancements
* Please put some feedback below what you would like to see
Submitted by: RainerBrunold
Hits: 497
Overall downloads: 51
Added: 2007-07-31 00:00:00
Last Modified: 2009-12-11 15:33:49
| Filename | Preview | Size | Description | DL |
|---|---|---|---|---|
| check_idm_sync.png |  |
153 kb | check_idm_sync Overview | 518 |
| check_idm_sync.sh |  |
6 kb | check_idm_sync.sh Version 1.1 | 342 |
Comments
Be the first to comment this project.
Leave a reply
If you just want to rate the project leave the other field empty.
Even though it would be nice if you would drop a line.
-
check_dxml_drvstate
from 0 votesNovell DirXML 1.1 and Identity Manager 2.x/3.x driver state detector plugin for Nagios -
check oes linux nss volume usage
1.5 from 3 votesThis check programs allows you to check the volume usage of nss volumes running on OES linux systems and monitor several other parameters. -
Check eDirectory LDAP Statistics
from 0 votesCheck the number of different searches and errors from your LDAP server. -
Groupwise Checks
from 0 votesSome scripts we use to monitor our groupwise integrations. All written in php, yet the logic may be interesting for some. -
GroupWise
from 0 votesCheck the status of the POA, MTA, GWIA and GWWEB agents by SNMP.
-
Plugin/Agent for Netware 5.0 - 6.5
from 0 votesNWNAGMON is an NLM plugin for Netware 5.0 .. 6.5 checks some basic server props and sends them directly to a nagios server (nsca v3 packets) -
check_ndslogin
from 0 votescheck_ndslogin can used by Nagios to check every configured Server for eDirectory Login -
Novell OES2 (Linux) check NSS directory quota usage
from 0 votesNovell OES2 (Linux) nss directory quota check -
check_zlm_zen_queue
from 0 votesThis program is used to check the zen_queue of the Novell Zenworks Linux Management (ZLM) solution. -
check_nwstat with Performancedata
from 0 votespatched Version of check_nwstat ( codebase of check_nwstat.c from Nagios Plugins 1.4.2 ) Published in Nagios-Plugins CVS and so in the next release of Nagios Plugins.