Cisco Telemetry Broker Requirements Data Sheet
Available Languages
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.
The following lists the prerequisites for deploying Cisco® Telemetry Broker to your network:
|
|
Distributed |
|
|
|
Management Server |
Brokering Node |
| CPU |
4 CPUs |
1 Gbit/s: 2 CPUs 10 Gbit/s: 5 CPUs Transformation Capable: 8 GB |
| Memory |
8 GB |
1 Gbit/s: 4 GB 10 Gbit/s: 8 GB Transformation Capable: 12 GB |
| Storage |
80 GB |
70 GB |
To deploy a manager to a hypervisor, you must download the OVA file from http://software.cisco.com. The Cisco Telemetry Broker Virtual Machine will synchronize its system time with the hypervisor. To ensure that features like TLS work correctly, hypervisor time needs to be accurate. To learn how to run NTP on the ESXI hypervisor, please refer to this VMWare knowledgebase article.
The node virtual appliance requires deployment on a vSphere ESXi hypervisor version 6.7.
Cisco Telemetry Broker allows you to ingest network telemetry from many sources, replicate it, and broker that data to multiple sources. For example, you can ingest any of the following:
● On-premises network telemetry, including NetFlow, syslog, and IPFIX
● Cloud-based telemetry sources, including AWS
And consume that telemetry with a variety of tools like Cisco Secure Network Analytics and Splunk.
Cisco Telemetry Broker has the ability to detect protocols on ingress. These protocols include
● IPFIX
● NetFlow (all versions)
● sFlow
● Syslog
● SNMP
All this functionality will come standard with the Cisco Telemetry Broker base license. The license allows you to deploy as many nodes as you want. We charge for capacity, so you can pay as you grow! See our ordering guide for details.
Cisco Telemetry Broker supports the following browsers (as tested on Windows and Linux platforms with minimum resolution of 1024 x 768 px):
● Google Chrome (latest rapid release)
● Mozilla Firefox (latest rapid release)
● Microsoft Edge (latest rapid release)
| Client |
Server |
Port |
Description |
| Users |
Nodes and Manager |
22/TCP |
SSH access to the console |
| Manager |
External Internet |
443/TCP |
HTTPS for secure external communications such as Smart Licensing and Software Update |
| Manager |
Each Node |
443/TCP |
HTTPS for secure management connections |
| Each Node |
Manager |
443/TCP |
HTTPS for secure management connections |
| Each Node |
External Internet |
443/TCP |
HTTPS for telemetry retrieved of HTTPS, such as accessing an AWS S3 bucket to retrieve stored AWS VPC flow logs |
| Users |
Manager |
443/TCP |
HTTPS for secure web interface |
Additionally, you must open ports based on the telemetry type that a source sends to a node, and based on the telemetry type that a node sends to a destination. The following table details common ports for various telemetry types:
| Port |
Description |
| 443/UDP |
HTTPS, for any telemetry retrieved over HTTPS, Such as: Accessing an AWS S3 bucket to retrieve stored AWS VPC flow logs |
| 514/UDP |
rsyslog, syslog, syslog-ng |
| 2055/UDP |
NetFlow v5, NetFlow v9 |
| 4739/UDP |
IPFIX |
| 6343/UDP |
sFlow |
