cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
934
Views
0
Helpful
3
Replies

Cisco telemetry broker and Nexus Dashboard data broker

m1xed0s
Spotlight
Spotlight

Just heard of Cisco telemetry broker today. Have not got time to do much google search yet about it. Is there a quick comparison between Cisco telemetry broker and nexus Dashboard data broker, like the purpose, features and benefits?

3 Replies 3

Tarakesh Jetti
Cisco Employee
Cisco Employee

Hi, 

Thanks for the question.

 

Currently, all network telemetry-based analytics products require a separate connection to a telemetry exporting source. Many customers have a multitude of analytics tools forcing them to choose which to deploy. But what if customers could address this problem by creating an aggregator and translation service that ingests any network telemetry and delivers it to any analytics tool?

 

That's where The Cisco Telemetry Broker comes in!

 

Cisco Telemetry Broker (formerly known as Titan) is a solution for any organization that considers analytics critical to their success. Analytics are only as good as the telemetry sources they use. Telemetry Broker distributes telemetry from any source, to anything, from anywhere. The Cisco Telemetry Broker is software not hardware, it is programmable, and it solves the problem of any one analytics platform holding exclusivity to a telemetry stream.

 

 

Cisco Telemetry Broker provides several key functionalities that will address the growing concerns of our customers:

 

 

 Brokering Data: The ability to route and replicate telemetry data from a source location to multiple destination consumers. Quickly onboard new telemetry-based tools! 

 

Filtering Data: The ability to filter data that is being replicated to consumers for fine grain control over what consumers are able to see and analyze. Save money sending data to expensive tools! 

 

Transforming Data: The ability to transform data protocols from the exporter to the consumer’s protocol of choice. Enable tools to consume multiple data formats!

 

Key features:

  • Replicate UDP telemetry to any number of tools
  • Ingest cloud logs* and convert to IPFIX for use in tools like Secure Network Analytics
  • Easily scale deployments with Virtual Appliances
  • High Availability built in for free
  • Central management for multiple telemetry exporters

 

 

 

 

Cisco Nexus Dashboard Data Broker (NDDB) (formerly Nexus Data Broker (NDB)) with Cisco Nexus Family switches is a software-defined, programmable solution for packet brokering. Packet brokering is the aggregation of network traffic mirrored or copied using network/optical TAPs or Cisco Switched Port Analyzer (SPAN) for monitoring and visibility. In contrast to monitoring solutions based on traditional packet brokers, the Cisco NDDB packet brokering approach offers a simple, scalable, and cost-effective solution well suited for customers who need to monitor higher volume and business-critical traffic for security, compliance, and application-performance measurement. It also enables real-time traffic visibility with an event-based approach through northbound APIs.

 

Benefits of Cisco Nexus Dashboard Data Broker

Extensive visibility

Gain extensive visibility for high-density data center switches with speeds up to 100/400G and analytics for increasing traffic volumes and highly complex multipath networks.

 

Grow at scale with speed

Scale out network monitoring independent of the number of ports, switches, or taps.

 

Highly cost-effective

Reduce network monitoring expenses with simple and cost-effective standard Cisco Nexus switches.

 

Basic Salient features of the Cisco Nexus Dashboard Data Broker:

 

  • Scalable topology for TAP and SPAN port aggregation.
  • Robust Representational State Transfer (REST) API and a web-based GUI for performing all functions.
  • Ability to replicate and forward traffic to multiple monitoring tools.
  • Rules for matching monitoring traffic based on Layer 1 through Layer 4 information.
  • Time-stamping using PTP.
  • Packet Truncation beyond a specified number of bytes to discard the payload.
  • Custom filtering of packets using User Defined Fields.
  • Ability to adapt to changes in TAP/SPAN aggregate network states.
  • End-to-end visibility.
  • High Availability.
  • Load Balancing.
  • Manage multiple disjointed networks.
  • Integration with ACI devices/ APIC and NX-OS devices.
  • Real-time statistics for easy troubleshooting.
  • Application management via IPv6.
  • Security features, such as role-based access control (RBAC), and integration with an external Active Directory using RADIUS, TACACS, or LDAP for authentication, authorization, and accounting (AAA) functions.

 

 

If you find my reply solved your question or issue, kindly click the 'Accept as Solution' button and vote it as helpful.

You can also learn more about Cisco Nexus Dashboard through our live Ask the Experts (ATXs) session. Check out this ATXs Resources [https://community.cisco.com/t5/data-center-and-cloud-knowledge/cisco-aci-ask-the-experts-resources/ta-p/4394491] to view the latest schedule for upcoming sessions, as well as the useful references, e.g. online guides, FAQs.

 

Thanks and regards,

Tarakesh Jetti

Customer Success Specialist -CX

So Cisco telemetry broker is essentially the UDP Director? Is there a reason I should not use the telemetry broker with Nexus switches in DC OR I would have to use Cisco Nexus Dashboard Data Broker for compatibility reason?

 

 

Hi,

 

Please find the difference of UDP director and Cisco Telemetry broker.

 

 

 

 

 

 

 

Cisco Telemetry Broker supports sending telemetry from the following types of inputs: 

 UDP Inputs: An input that consumes UDP telemetry and sends it to our destinations. 

 VPC Flow Logs : An input that consumes Amazon Web Services (AWS) VPC Flow Logs from an s3 bucket, transforms them into IPFIX, and sends the IPFIX to your destinations. 

NSG Flow Logs: An input that consumes Azure NSG Flow Logs from an Azure Storage Account, transforms them into IPFIX, and sends the IPFIX to your destinations.

 

 

 

 

 

The Cisco Telemetry Broker Nodes Overview shows details about all of your broker nodes, including the following: 

 

 Broker node name and IP address

 Telemetry interface IP address.

 Capacity of the broker node.

 The associated cluster name.

 Received and Sent rate in bps 

Status of the broker node and the last time the manager communicated with it.

Which high availability clusters the broker node belongs to, if any 

 

By default, the Broker Nodes table is filtered by Highest Received Rate. You can also filter it by Most Recently Seen. To do this, from the Highest Received Rate drop-down list, choose Most Recently Seen.

 

Broker nodes are the devices that will ingest process and broker telemetry throughout the network. Broker nodes are deployed as virtual machines similar to the manager. Broker nodes have two network interfaces. One will reside on the management network and the other will reside on a monitoring network.

 

For more information and resources related to Cisco Telemetry broker see below link.

 

https://www.cisco.com/c/en/us/products/security/telemetry-broker/index.html

 

 

 

If you find my reply solved your question or issue, kindly click the 'Accept as Solution' button and vote it as helpful.

You can also learn more about Cisco Nexus Dashboard through our live Ask the Experts (ATXs) session. Check out this ATXs Resources [https://community.cisco.com/t5/data-center-and-cloud-knowledge/cisco-aci-ask-the-experts-resources/ta-p/4394491] to view the latest schedule for upcoming sessions, as well as the useful references, e.g. online guides, FAQs

 

 

Thanks and regards,

Tarakesh Jetti

Customer Success Specialist -CX

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: