Nagios Process Hypermap

[tmcdonald]

Did you happen to delete then re-add the localhost and its services at any point?

[lance.peterson]

Not that I'm aware of. I do know that 172.16.100.10 was the first item that was added to Nagios. After I added the other switch I switched the localhost to the correct switch. So I can't switch where the Nagios Process parents to?

[tmcdonald]

So I can't switch where the Nagios Process parents to?

That's what we are trying to figure out. There is not a config option that I know of to set this.

Not that I'm aware of. I do know that 172.16.100.10 was the first item that was added to Nagios. After I added the other switch I switched the localhost to the correct switch.

Not quite sure what you mean with the bolded portion. Do you mean you overwrote the localhost config to that of the new switch, or that you made the new switch a parent of localhost?

I am thinking this has to do with object IDs. Can you go to the CCM, Hosts section, then for each of the switches and localhost, tell us what the ID is? It will be on the far right.

[lance.peterson]

Not that I'm aware of. I do know that 172.16.100.10 was the first item that was added to Nagios. After I added the other switch I switched the localhost to the correct switch.

Not quite sure what you mean with the bolded portion. Do you mean you overwrote the localhost config to that of the new switch, or that you made the new switch a parent of localhost?

What I mean is when I first started I didn't have 172.16.100.11 in Nagios yet. Once I brought that switch online I changed the parent for "localhost" to 172.16.100.11. 172.16.100.10 was the very first item I added to Nagios.


I am thinking this has to do with object IDs. Can you go to the CCM, Hosts section, then for each of the switches and localhost, tell us what the ID is? It will be on the far right.[/quote]

Local host ID:1
172.16.100.10 ID: 5
172.16.100.11 ID: 34

[lmiltchev]

The "Nagios Process" is placed on the map for visualization purposes only. It doesn't really matter if it is directly connected to localhost or not. You can look at it as a "sudo-parent" of all hosts that don't have parents. Once you assign parents to these hosts , they become "children" and are no longer connected DIRECTLY to the "Nagios Process". That's what happened to localhost.

I would like to reiterate:

1. "Nagios Process" still monitors ALL of the hosts on the map - directly or indirectly. Again, its presence is for visualization purposes only as it shows which hosts are on the top of the tree (in the hierarchy).

2. Even though, localhost is where nagios is running, it's just another host that is monitored. It could be named "localhost" or it could be named with an IP address... It doesn't really matter. If it has no parent, it would be connected to the "Nagios Process" directly. It it has a parent, it would be connected to the "Nagios Process" indirectly (via the parent). It is still monitored by nagios either way.

The "indirect" connections are NOT displayed on the map as it would become unreadable.

I hope this makes sense.