How much bandwidth does TMS use to manage a system?

Available Languages

Updated:April 23, 2015
Document ID:112585

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This article relates to Cisco TelePresence Management Suite.

Q. How much bandwidth does TMS use to manage a system?

A. TMS does not maintain constant connections with systems and therefore is not consuming bandwidth for systems at all times. TMS is event triggered, meaning that connections are established as needed based on some event or trigger happening—such as connecting a call.

The bandwidth used per system is therefore completely dependent on how active each system is or how often it is managed. The connections are generally text only and very lightweight, except for software upgrades. A basic call on an MXP endpoint, for example, generates less than 140kb of total management traffic. Bandwidth usage at the system end for management is generally considered neglible. Bandwidth consumption at the TMS end will depend on how many systems are being managed and how active they are. Bandwidth consumption for management is normally not a cause for any network changes.

Related Information

Revision History

Revision Publish Date Comments
1.0
23-Apr-2015
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products