Thanks Kevin! That makes perfect sense now. Regards, Sven
From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Wednesday, July 16, 2014 12:47 PM To: [email protected] Subject: [msmom] RE: SCOM 2012 SP1 - dual Gateways - Change Primary Management Server turns agents gray By design. When you add another GW at a location, the agents DO NOT know about it. Agents - when assigned to a gateway, get a config XML file locally that will ONLY contain that assigned GW as a possible parent. You must manually, via powershell, make those agents reporting to a GW be "aware" of the secondary gateways that they are allowed to fail over to. What you are experiencing is called "orphaning agents" because you assigne them to another healthservice, but since they don't know about that HS - they never will communicate with it and will continue to communicate with the original GW. However, since this original GW was not assigned as a failover, it rejects them, hence the HB failures and lack of communication, until at which time you assign them back, and they are no longer rejected by the original GW. When you have multiple GW's in a site for agent based failover and load balancing, you must assign the agents to their GW via PowerShell, and provide the failover GW server as a param: See: http://blogs.technet.com/b/jimmyharper/archive/2012/01/09/3346309.aspx From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sven Wells Sent: Wednesday, July 16, 2014 11:38 AM To: [email protected]<mailto:[email protected]> Subject: [msmom] SCOM 2012 SP1 - dual Gateways - Change Primary Management Server turns agents gray Hello, We have 3 data centers that are geographically remote from the SCOM 2012 SP1 database servers (and management severs). At each of these 3 data centers we built 1-Gateway Server. Each of these Gateway servers manages at least 200 agents. We decided to build a 2nd Gateway server at each of these 3 remote data centers, so that we could offload 50% of the agents onto the newly built 2nd Gateway servers. After the 2nd Gateways were built about a month ago (at least 8months after the initial Gateways), we've now started "Changing primary management server" for 50% of the agents. We started small, selecting 5-8 agents at a time, then waiting 30mins or so. Most (about 90%) of the agents we've attempted so far, go from a Green/Healthy state to a Gray/UnHealthy state within that 30mins, and never become healthy. If we move those agents back, they become Green/Healthy again. The Gateway servers and the agents they manage are all located in the same AD Domain, so everything is trusted. No DMZ/Untrusted relationships in place for this.\ Any idea why 'moving' these agents between two co-located Gateway Servers, in the same AD Domain (both agents and GWs are in the same Domain), is turning them gray? Oh, I've also attempted to "Repair" these agents, but to no avail. Thanks, Sven Sven Wells SYSTEMS ADMINISTRATION SPECIALIST Communication and Infrastructure Services TIP - Technology, Innovation and Performance PPD Wilmington NC HQ Phone +1 910 558 6870 [email protected] <mailto:[email protected]>www.ppdi.com <http://www.ppdi.com/> PPD LSS Yellow Belt [cid:[email protected]] 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.
