topic Re: MP not associating with server in Server Management - Systems Insight Manager

MP not associating with server

Don Reese_3 — Wed, 16 Nov 2005 13:00:01 GMT

I have four servers that are not showing their MP association properly. one of the MP's is showing that it is in the proper server, however the server MP icon is stills howing the ? icon. I've tried Hardware and Software Staus, Discovery, Identify, etc.

Re: MP not associating with server

Don Reese_3 — Wed, 16 Nov 2005 16:24:54 GMT

Okay, I've done some additional fiddling, found that the SNMP settings were not correct, so I fixed it by adding localhost as a trap destination/source. But now the server thinks it is in the MP!!!

Re: MP not associating with server

Ferry Steenvoorde — Thu, 17 Nov 2005 05:06:11 GMT

Localhost as trap destination? Typical. You might give it a try with the HPSIM-server as trap destination. I guess the agents cannot cope with the localhost-option for SNMP.

At the moment I am migrating a datacenter to HPSIM 5.0 and Support Pack 7.40. On older Windows 2000-systems with Support Packs below version 6.20 (even some on 5.0.7), the Management Processors are not even recognised as being part of a managed server! It's about time to upgrade them to the latest agents.

Also, the IP-addresses of the MP's must also be in the Discovery ranges. MP's are recognised by their own access to the network, not through the system in which they are installed.

Re: MP not associating with server

Don Reese_3 — Fri, 18 Nov 2005 14:41:15 GMT

The HPSIM CMS is already a trap destination. Per another thread on here I added localhost to the security tab and that seemed to fix a lot of my earlier issues. I added localhost to the trap destination tab to see if that would have any beneficial effect.
All of my MP IP's are in the same discovery range as the (supposed-to-be) associated servers. All but 4 of my systems are recognizing the association properly, three are in a remote location where I suspect a firewall issue, and the other is an older RiLOE system that needs a couple of firmware updates.
The issue where the Server thought it was in the MP worked itself out already.