There is no compelling reason not to mix that I am aware of, in small numbers.
The concern is - that Unix/Linux is monitored agentlessly (as the workflows run on the management server or gateway proxy watcher) and communicate to the provider agent on the Unix/Linux machine. This causes significant processor utilization of a management server or GW. This is why there is a scalability limit of how many of these workflows a single healthservice can handle. The management server healthservice can handle more, because it will write directly to the databases. A GW has to queue the data, send to an upstream management server, for insertion into the DB. This is why management servers as a general rule will always handle agentless tasks better, such as network, url, or unix/linux. The agent traffic will be handled by the healthservice on the GW as well, and be processed via the same queue. The load of 60ish windows server agents through a gateway is almost negligible. As long as your gateway can adequately handle the load of the unix/linux, then the windows agents reporting to the same healthservice should be insignificant. From: [email protected] [mailto:[email protected]] On Behalf Of Pete Hakesley Sent: Thursday, July 11, 2013 10:09 AM To: 'msmom ([email protected])' Subject: [msmom] Linux and Windows on a single Gateway All, We have customer who for internal reasons wants only to use a single gateway for 49 Linux Red Hat 4/5 and 60ish Windows 2003/2008 Servers. All documentation says 100 Linux per dedicated GW etc. but is there a compelling reason technical or otherwise to never mix Linux and Windows on a single gateway in fairly small numbers. Note: SCOM 2007 R2 CU4 GW Spec 2 x CPU (vCP) 6GB RAM and 40GB C: Drive 1GB Ethernet. Peter Hakesley PJH2711-RIPE, CDCT, MBCS SCC Services Data Centre Operations - Service Implementation - Enterprise Systems Engineer SCC Cole Valley 1, 20 Westwood Avenue, Tyseley, BIRMINGHAM B11 3RZ Tel: +44 (0)845 351 0680 xtn 4006 eMail: [email protected]<mailto:[email protected]> Web : www.scc.com<http://www.scc.com/> [Description: Description: BCS_Logo]
<<inline: image001.jpg>>
