You were correct. Once I modified the Resource Pool, including only the Management Servers in the same geographic location, the Resource Pool became stable and usable.
Thanks! Sven From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Thursday, July 18, 2013 11:51 AM To: [email protected] Subject: RE: [msmom] RE: SCOM 2012 SP1 Unix/Linux Resource Pool issue We do not ever recommend management servers across geographic locations, except in specific circumstances for DR. In general, all management servers must be within 5ms latency between each other and the databases. Anything beyond this and the resource pools will start to break. For a geographic design, we generally recommend using gateways in remote locations to aggregate traffic, not management servers. I don't think I have ever seen a management server placed in a different domain than the rest of the management group... I'd have to do some research to see if that was even supported/supportable. From: [email protected] [mailto:[email protected]] On Behalf Of Sven Wells Sent: Thursday, July 18, 2013 10:40 AM To: [email protected] Subject: RE: [msmom] RE: SCOM 2012 SP1 Unix/Linux Resource Pool issue So of the 4, one is in another, trusted, domain. None of them are in the same geographical location. 3 are in the US, the 4th is in Europe. The 3 in the US are all well connected, but not on the same subnet/VLAN. But you've given me an idea. I'm going to select 4 that are in the same geographical location, connected to the same VLAN/subnet and see what happens. I'll post back when I get some results. Thanks, Sven From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Thursday, July 18, 2013 11:18 AM To: [email protected] Subject: RE: [msmom] RE: SCOM 2012 SP1 Unix/Linux Resource Pool issue I'm not necessarily recommending it... just was curious. J It can be done - via powershell, but there are issues that require workarounds if you had done it. Since you didn't - that's not relevant. So on your issue - are all of your management servers in the same physical location and connected to the same VLAN/subnet? As in well connected, and no latency between themselves or the operational database? From: [email protected] [mailto:[email protected]] On Behalf Of Sven Wells Sent: Thursday, July 18, 2013 10:09 AM To: [email protected] Subject: RE: [msmom] RE: SCOM 2012 SP1 Unix/Linux Resource Pool issue I just realized I can't remove those servers from the "All Management Servers Resource Pool", that pool is locked and the membership option is grayed out. Thanks, Sven From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Thursday, July 18, 2013 10:50 AM To: [email protected] Subject: [msmom] RE: SCOM 2012 SP1 Unix/Linux Resource Pool issue For the management servers that are members of your Unix/Linux resource pool - did you also happen to remove these from the All Management Servers Resource pool? From: [email protected] [mailto:[email protected]] On Behalf Of Sven Wells Sent: Thursday, July 18, 2013 9:44 AM To: [email protected] Subject: [msmom] SCOM 2012 SP1 Unix/Linux Resource Pool issue Hello, We've been attempting to add some Red Hat Linux servers/agents to be monitored by our SCOM 2012 SP1 environment. The environment consists of 12 Management servers, 4 of which I have configured as/for the Unix/Linux Resource pool. I have also exported/imported each server's certificate to each other server in the Resource Pool. I am seeing the following Alert: Alert: Resource Pool Heartbeat Failure Source: Unix/Linux Resource Pool Watcher Path: Not Present Last modified by: System Last modified time: 7/18/2013 8:33:03 AM Alert description: The resource pool 8d19ae3d-9aa0-458a-a002-d0343ca75d44 failed to heartbeat. Notification subscription ID generating this message: {67EB2DBA-6A6B-AF69-B131-65AF3B9B1A9E} I'm also seeing the following Event ID in the Operations Manager event log on each Management Server: Log Name: Operations Manager Source: OpsMgr Connector Date: 7/18/2013 8:33:04 AM Event ID: 20022 Task Category: Availability Level: Error Keywords: Classic User: N/A Computer: <management server name> Description: The entity "Unix/Linux Resource Pool" is not heartbeating. Entity Id: {C8936320-4BAE-9645-3F83-5336A988399C} Management Group Name: PPDI Management Group Id: {8D7AF625-4BFC-8C9F-A281-DF0EFD4EB7E6} Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event";> <System> <Provider Name="OpsMgr Connector" /> <EventID Qualifiers="32768">20022</EventID> <Level>2</Level> <Task>3</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2013-07-18T13:33:04.000000000Z" /> <EventRecordID>103216</EventRecordID> <Channel>Operations Manager</Channel> <Computer><management server name></Computer> <Security /> </System> <EventData> <Data>{C8936320-4BAE-9645-3F83-5336A988399C}</Data> <Data>Unix/Linux Resource Pool</Data> <Data>PPDI</Data> <Data>{8D7AF625-4BFC-8C9F-A281-DF0EFD4EB7E6}</Data> </EventData> </Event> I have checked the state of all Management Servers, and they are all showing green/healthy. All of them have the Data Access Service, Management service, and Management Configuration service up and running. This works perfectly fine In our Pre-Production environment, however, our Pre-Production environment only has 1 Management Server as this is more of a test environment. Ideas? Thanks! Sven Sven Wells SYSTEMS ADMINISTRATION SPECIALIST TECHNOLOGY AND LABORATORY SVCS Wilmington NC HQ PPD Phone +1 910 558 6870 [email protected] www.ppdi.com <http://www.ppdi.com/> This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner. This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner. This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner. This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner.
