Health Monitoring
|
3/14/2006 Health monitoring uses OpenWBEM to let you view and/or monitor the health of Linux or Netware operating systems. It sounds like these services are still under development and that only data collection and analysis currently work (no system alerts or thresholds yet, etc.). Nonetheless, it is standard in NW 65. Here is the Health Monitoring Services Administration Guide. Here is the OpenWBEM Services Administration Guide. Here are the components:
There are two types of monitoring - Robust Health Monitoring, which tells you things about Memory, OS, processes, network, and CPU. The other is Simple Server Status, which simply tries to connect to a port (there are ten preconfigured ports to choose from) on a remote server and tells you if it's up or not. Robust Monitoring is only reported by a Netware or Linux server, since the owcimomd module must be running. Otherwise you can only report a Simple Server Status. You must first install OpenWBEM if it is not already. If you upgraded from NW65 SP2 or earlier, it may not be. Here is the install guide. I originally installed from the SP4 CD's, so I did not have to worry. You must also be running iManger 2.5. First you must add at least one server. I wanted to start with our actual Netware server computer (the one running all this stuff), so I logged into iManager with the Admin account, clicked Servers -> Monitor Servers from the left-hand menu, and then clicked Add. I used S3 for the Server Name and then typed in the DNS Name (it was recommended that they match, but the server name is purely descriptive), then a brief description including operating system version. I made sure Robust Health was checked, then clicked Next. For some reason, I think it thought that this was a Linux server, because I got an Authentication Failed error and it then told me about Linux User Management. Hhhmmm... I clicked on Monitor Servers again, and the servers were listed - but when I clicked on them, I got the authentication error once again! Perhaps I needed to set up the destination server first. Here is the guide for that. I went into eDirectory and checked that the proper objects were created. The CIM container was there, HMS container under that, and then ServerList1 under that. Under Properties -> Other ->lasServers, I saw everything that I had entered from the iManager screen. Hhhmmm.. I checked that the port was open by going to the Server Console and typing telnet -p 5989 localhost, and it connected (but did not say anything). I also tried the OpenWBEM unsecured port, 5988, and the connection was refused. So, the port was open.. now what was wrong?? The configuration file that specifies the location for these ServerList
Objects Health Monitoring Service Objects is SYS:/tomcat/4/webapps/nps/WEB-INF/config/lasMonitorServers.xml.
It is stored in the following format:
I checked that file on our system and it was correct. I noticed the
following error on the Logger Screen at the console:
I tried disabling authentication by modifying the openwbem conf file
(SYS:\SYSTEM\cimom\etc\openwbem\openwbem.conf) and setting
the following line:
I then restart Openwbem by typing unload owcimomd followed by openwbem. I went into iManager again to check the server stats, and voila! At least now I knew it was working. I just had to figure out how to do it without allowing anonymous access! What I ended up doing, at
least temporarily, was to turn on anonymous access again, but tell OpenWBEM
to only listen on the localhost IP (127.0.0.1). I did this by changing
the following lines and then restarting openwbem:
I checked, and I could still access the stats through iManager. However, I could no longer telnet to the OpenWBEM port from another computer. Done!
*** OpenWBEM can be configured to require secure access. Read here. |