We have received a couple of customer inquires regarding the use of Operations Manger 2007 in a low-bandwidth scenario. These issues deal with a situation where the Management Server in one site (Site A) is separated from its agents in another site (Site B), and Sites A and B are separated by a low-bandwidth connection.
Operations Manager was designed and built to be an enterprise-wide solution. It was understood that this product would be expected to handle thousands of agents. Therefore all data going across the network between an agent and a Management Server or gateway server is not only encrypted, but compressed as well. Our compression ratio is in the range of 4:1 to 6:1.
The impact on the network between the two sites when using the Discovery Wizard to deploy an agent can be minimized by deploying a gateway server (GW) at the distant site (Site B). When an agent is deployed through a gateway server, the gateway server itself deploys the agent, not the Root Management Server (RMS). The Root Management Server issues the command to the gateway server to deploy the agent. I performed a test measuring network traffic between the RMS and GW and between the GW and the computer to which the agent was deployed. Network traffic between the RMS and GW was about 18KB. Network traffic between the GW and the computer receiving the agent was about 7.8MB. These figures include the initial three-way handshake and all Ethernet and TCP/IP headers. Because the gateway server performs the actual agent installation, the network hit between the RMS in Site A and the GW in Site B is minimal.
To further reduce network traffic, deploy only the Management Packs you need for the distant site. Consider creating a separate Management Group containing only the Management Packs you need.
Heartbeat settings are adjustable. You can set both the heartbeat interval and the number of missed heartbeats allowed. The default setting for the heartbeat interval is 60 seconds; the default setting for number of missed heartbeats allowed is 3.