Tivoli Endpoint Manager (TEM) is designed to be a real time (seconds and minutes) system capable of workng in extremely limited bandwidth environments. Properly configured, The TEM platform can effectively and quickly deploy files that are hundreds of MBs large to tens of thousands of computers without significantly affecting general network performance. Because of the speed and prevalence of the TEM platform in the network, however, it is very important that network engineers understand the different types of traffic that the TEM Servers, Relays, Clients, and Consoles can generate.
The following information describes the different types of network traffic and explains the purpose of the traffic as well as information about how to handle "Possible Worst Case Traffic".
Note: The "possible worst case traffic" are definitely not expected; however, in the interest of preparing for the worst case scenario, example situations are given as well mechanisms to recover from the situation. This information is intended to educate network engineers and provide the basis of a disaster recovery procedure related to the Tivoli Endpoint Manager infrastructure.
Please refer to the following diagram in the network discussions below: