I’m monitoring a few AIX LPAR using both 1.5.0p16 and an old 1.2.8 cmk raw systems.
The 1.5 versions stared maybe as 1.4, not sure, but we have been upgrading it to the current 1.5.0p16 level.
Thing is, on the cmk 1.5.0p16, for a time nowwhen I go to wato, the services tab mentions them (hdisk0 and hdisk1) as “vanished”, and prompts us to remove or disable them. But, I I just leave them there, they still get performance date and I can see the performance graph for each server.
On 1.2.8, same system as client, the disks (hdisk0 and 1) are still there.
The AIX agent is the 1.5.0p16 version.
For aix_diskiod, the agent returns:
<<<aix_diskiod>>>
hdisk1 0.0 34.5 1.7 535998099 204641620
hdisk0 0.1 71.4 1.4 1454788462 78967544
<<<aix_memory>>>
Both CMK are configured to display performace data for each disk on the system.
So, why is 1.5.0p16 trying to get rid of the disks, while they are still there?
On the first two images, you see the AIX hdisks being suggested by cmk 1.5.0p18 now to be either removed or disabled since it gets them as “vanished” (even when some of those are the AIX OS boot drives). You’ll also see that on cmk raw 1.5.0p18 the aix drives still get data for performance and perf-o-meter if you just don’t “remove” or “disable” the drives. At the same time, when monitoring the same boxes from 1.2.8 (third image), the disks are just fine and not vanished.
I’m monitoring a few AIX LPAR using both 1.5.0p16 and an old 1.2.8 cmk raw systems.
The 1.5 versions stared maybe as 1.4, not sure, but we have been upgrading it to the current 1.5.0p16 level.
Thing is, on the cmk 1.5.0p16, for a time nowwhen I go to wato, the services tab mentions them (hdisk0 and hdisk1) as “vanished”, and prompts us to remove or disable them. But, I I just leave them there, they still get performance date and I can see the performance graph for each server.
On 1.2.8, same system as client, the disks (hdisk0 and 1) are still there.
The AIX agent is the 1.5.0p16 version.
For aix_diskiod, the agent returns:
<<<aix_diskiod>>>
hdisk1 0.0 34.5 1.7 535998099 204641620
hdisk0 0.1 71.4 1.4 1454788462 78967544
<<<aix_memory>>>
Both CMK are configured to display performace data for each disk on the system.
So, why is 1.5.0p16 trying to get rid of the disks, while they are still there?
I’m re-sending this to the list to see if you can help me at least on how to debug this.
Is there a recommended way to “see” what’ the aix_diskiod cmk-server-side is doing when it receives the information from the cmk agent on the aix box? I’ve see already that the cmk agent is producing that information.
So what could be good pointers to debug the server side of things, and what is the aix_diskiod doing with the info it receives, or if it is never being called or what.
I’m monitoring a few AIX LPAR using both 1.5.0p16 and an old 1.2.8 cmk raw systems.
The 1.5 versions stared maybe as 1.4, not sure, but we have been upgrading it to the current 1.5.0p16 level.
Thing is, on the cmk 1.5.0p16, for a time nowwhen I go to wato, the services tab mentions them (hdisk0 and hdisk1) as “vanished”, and prompts us to remove or disable them. But, I I just leave them there, they still get performance date and I can see the performance graph for each server.
On 1.2.8, same system as client, the disks (hdisk0 and 1) are still there.
The AIX agent is the 1.5.0p16 version.
For aix_diskiod, the agent returns:
<<<aix_diskiod>>>
hdisk1 0.0 34.5 1.7 535998099 204641620
hdisk0 0.1 71.4 1.4 1454788462 78967544
<<<aix_memory>>>
Both CMK are configured to display performace data for each disk on the system.
So, why is 1.5.0p16 trying to get rid of the disks, while they are still there?