Oct 18, 2013 - Path = “$FileShr Agent AMD64 MOMAgent.msi” Arguments = “USE_SETTINGS_FROM_AD=0 MANAGEMENT_GROUP=OM_Contoso. There are 2 Proliant ML Servers in our domain. G4 is the MOM Server, G2 has a MOM Agent. In Operations Manager Under Computer Groups, both show 'HP Proliant Insight Management Agents', but only G4 shows 'HP Proliant Servers' and 'HP Proliant Servers ML'. Under 'role' for G4, the computer model of G2 is shown as ML 370 G2. Under 'Computer Details' both have all the right HP Insight Agents. Why is G2 not in HP Proliant and Proliant ML computer groups? Does it matter? Perbedaan guitar rig 5 dengan efek figital. Chiavetta wind driver windows 7 0. Will all events be handled anyway? Both are Win2K3 SP1. PS I'm new to MOM, but am using it primarily for the HP agent. It doesn't look as if it matters, but some reassurance would be welcome. George, Your G2 must be in HP Proliant Servers and HP Proliant Servers ML groups as well. Since your G2 is not in these groups you will not receive MOM alerts/events related to rules from these two groups. ![]() You can manually add G2 server in these groups with MOM administrator console. But better option is to check why G2 is not in these groups. Make sure you have full PSP installed on G2. Make sure SNMP options on G2 is same as on G4 P.S. We use MOM 2005 and we have ML370 G1, ML370 G3, ML370 G4 servers. We DON'T have ML370 G2 servers. ALL our Proliant ML servers are in three groups: HP Proliant Insight Management Agents, HP Proliant Servers and HP Proliant Servers ML. But generally speaking if you use HP Insight manager you will see all alerts from 3 Proliant MOM gpoups in Insight manager as well. ![]() Igor, Thanks for answering my questions, and so quickly. PSP is 7.60 on both servers. SNMP was running on both servers. SNMP Trap was not running on either servers, so I started it on both (not sure if needed). I have added G2 to the HP Proliant computer groups manually. I had tried to do that earlier, but it hadn't worked. I'm still puzzled as to why G2 wasn't automatically included. It's an Exchange 2003 Server. Another error which has just shown up is that the agent failed to install MBSA on that server. Possible reason is that action and response account do not have right privileges. Do you know what privileges are required? 1) I think SNMP trap is not needed, but check that you have defined Read/Create private SNMP community string and Read public (at least) community string. Check option 'Accept SNMP packets from any host' as well. Do you use HP Insight manager? If yes - do you see G2 server in HPSIM? I still don't think that problem is G2 specified, but I as I wrote before we don't have G2 servers. 2) Regarding MBSA: we don't use MBSA management pack. But try post here full message and event id - and probably we can suggest something regarding MBSA. 1) Read/Create private SNMP community string and Read public community string were defined on G4 (the MOM server) but not on G2 (the MOM agent). 'Accept SNMP packets from any host' was not checked on either server. I have rectified these settings for which thanks. However, these corrections have not 'solved' the problem of G2 not being automatically included in the Proliant computer groups. I have checked again and found that manually entering G2 via the Admin Console is the only way to include it. We do not use HP Insight manager, as our attempts to do so have indicated that it uses too many resources. This is one reason for trying out MOM 2005. I agree that the problem is probably not G2 specific, but related to some settings. 2) Regarding MBSA: I can see why you don't use MBSA management pack - the weekly event log is somewhat verbose! I raised the question thinking it might be relevant to the other issue. The Event Description is: Script Error - The agent failed to install Microsoft Baseline Security Analyser. The Event Number is: 40000. The Source is: Microsoft Baseline Security Analyzer MP. The Event Id is: 9c800145-87c8-4f36-b49c-e8e617d4dd36. >>I have rectified these settings for which thanks. However, these corrections have not 'solved' the problem of G2 not being automatically included in the Proliant computer groups.
0 Comments
Leave a Reply. |