Follow

How to connect a Flow sensor to redBorder

INDEX

Chapter 1: Create and connect the Flow sensor

This chapter describes the steps needed to create and connect a Flow sensor to redborder.

Add a Flow sensor

The Traffic module (also known as Flow), from the redBorder platform, allows the monitoring and supervision of the data traffic received from the entire business infrastructure. Thanks to the views offered by this module we can make comparisons, filters, searches and analysis.

The first thing we need is to add a flow sensor (flow exporter). To create a new flow sensor, go to
to the Sensors  option and then in the Add Sensor menu select Flow type.

 

add-sensor-menu.png

 

We will see that a modal window appears with the following fields:

 

add-flow-sensor.png
 
  • Name: Name of the sensor.
    peligro.pngThe name you put on the sensor can not have blank spaces.
 
  • Obvervation ID: optional.
  • SNMP Community: optional.
  • IP or Network: IP address or network to which the sensor belongs.
  • License (Enterprise): License that will be used to authorize the new sensor in the redBorder platform.

If these actions have been carried out correctly, we have registered our sensor and the platform will be ready to collect and visualise the data incomming from the exporter.

 

sensor-flow-anadido.png
 
 

Traffic view (flow) in redBorder

In the user interface of the redBorder platform we can find the Traffic (flow) module, which shows a view to interact with the processed data.

tip.png Denpending on the flow version and the exporter a delay may occur in appearing the data on the dashboard. Netflow exporters must send a special package with the information template. Until redBorder does not receive that template it can not display the information.
 

If the Flow sensor has been correctly configured and has also been added correctly to the network
in the redBorder platform we should see something similar to the image below.

 

traffic-module-view.png
 

This view, like the rest of the views of redBorder, includes filtering functions, different types of views, different time windows, different types of graphs, etc…​

On the other hand, if the sensor is not configured correctly we can not see anything in the graph. An example of this is the image that we show below:

 

no-data.png
 

Chapter 2: Clarifications

In this chapter we will talk about some clarifications about the Flow sensor.

When we create a flow sensor, two processes are created.

Each process has a different listening port:

  • Netflow (any of its versions): 2055
  • sFlow: 6343

The Flow sensor that connects must send traffic through the aforementioned ports and to these ports, the sensor can send netflow traffic in version 5, 9 and IPFIX (IPFIX is the same as if we are talking about version 10 of netflow).

peligro.png  Each port listens to a different traffic, that is why if we send another type of data that is not the expected one, we will not be able to see information in the dashboard.

This notice was previously stated in the section on Traffic view, but we will remind you again.

tip.png  It may be that the traffic is delayed in appearing in the dashboard. Because netflow exporters must send a special package with the information template. Until redBorder does not receive that template it can not display the information, depending on the manufacturer it may take more or less that information to appear.
 
Have more questions? Submit a request

Comments

Powered by Zendesk