Data size between agent and server
Dear All I already Implement SCOM 2007 R2 server on HQ and deploy to server on HQ. next I need to deploy to branch server. On microsoft recommand it will setup SCOM Gateway server for receive data from agent because on branch site is connect to HQ by MPLS 512k, network Team don't want there bandthwidth full. my question is 1. how many package or data size that agent send to server, and it send real time or schedule 2. how to setup SCOM GW server ( my plan is place GW server on reginal and let's agent on reginal to send data to it ) please help me to clear
August 23rd, 2011 5:40am

1. it depends on what you are monitoring/collecting and how healthy the environment is (imho 0.5kbps per agent is a nice guideline to start with; also note that a gateway can reduce traffic, it depends on how much agents will be reporting to the gw). 2. of course install it in the branch office...; think about redundancy thoughRob Korving http://jama00.wordpress.com/
Free Windows Admin Tool Kit Click here and download it now
August 23rd, 2011 6:13am

Rob is correct here. The answer to this question depends on many factors (Management Packs Imported, What is discovered on each Agent, how healthy / unhealthy the Agents are, etc). You should deploy the Gateway at the remote sites and have the Agents at that site report to the Gateway. The Gateway will compress the data before sending it across the WAN to the Management Servers. In our testing, we see around 50bytes/sec sending and 20bytes/sec recieving from each Agent. This is at steady state. If a Managmenet Server / Gateway / DB / DW goes down for som time and then comes back online, the Agents will be sending more data since they will try to send the data that was queued up when things were down. Thanks go out to my teammate Hui Wang for providing this data. Thanks Hui!!Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
August 23rd, 2011 9:14pm

For 8 servers, its probably not worth the cost. If you had closer to 20 machines, then it becomes a good idea. Generally the rule is: ~5-10 machines, not worth it (unless the link to the main office goes up and down a lot) ~10-20 machines, probably not worth it, depends on what all data you are collecting and how stabile that link is ~20-50 machines probably worth it >50 machines definitly worth it How utilized is your 2Mbps link? If its close to 100%, it might be a good idea to use the Gateway, otherwise no. How stabile are those links? If they are up and down a lot, then it might be a good idea to use the Gateway since it can cache more data than the individual Agents and when the link comes back online it will compress that data and send it up to the Management Servers at the main office. Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
Free Windows Admin Tool Kit Click here and download it now
July 5th, 2012 4:43pm

For 8 servers, its probably not worth the cost. If you had closer to 20 machines, then it becomes a good idea. Generally the rule is: ~5-10 machines, not worth it (unless the link to the main office goes up and down a lot) ~10-20 machines, probably not worth it, depends on what all data you are collecting and how stabile that link is ~20-50 machines probably worth it >50 machines definitly worth it How utilized is your 2Mbps link? If its close to 100%, it might be a good idea to use the Gateway, otherwise no. How stabile are those links? If they are up and down a lot, then it might be a good idea to use the Gateway since it can cache more data than the individual Agents and when the link comes back online it will compress that data and send it up to the Management Servers at the main office. Michael Pearson OpsMgr Performance Test Team http://blogs.technet.com/michaelpearson/ This posting is provided "AS IS" with no warranties, and confers no rights. Use of attachments are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
July 6th, 2012 6:54pm

Hello! I am planning implementing Operations Manager 2012 in my environment. I have main office and three branch offices. They are all in one domain with some sites. The channel between main office and branch offices equals approximately 2 Mb/sec each. Each branch office contains Domain Controller, Exchange Server and some Application Servers not more 8 servers. I am planning to monitor the following main roles: Windows Server, DHCP, DNS, Active Directory, Exchange Server, SQL Server, Print Server, IIS. And I would like to know should I deploy OpsMgr Gateway Servers in each branch offices to decrease load of channel or not? Thanks for your advices!
Free Windows Admin Tool Kit Click here and download it now
July 7th, 2012 4:13am

Thanks for your reply! I suppose, in my case, I will not to deploy Gateway.
August 2nd, 2012 12:52am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics