Netflow on Juniper

Juniper routers can generate and send flow records to a management server. This allows the administrator to monitor all the traffic that is being routed and better understand the users’ behavior and needs when using the network. Besides that, it also creates a database with every connection originated or destined to your autonomous system for further consultation.

The following tutorial shows how to configure the router and how to set up a management server to receive and store the data using open source tools. In addition, it will also  show how to query the information base.

Configuring the Router

1. Define and configure an interface to export flow data, like ge-1/1/0. The flow collector must be reachable through this interface, since flow records cannot be exported if the flow collector is reachable through a management interface like fxp0.1)http://www.juniper.net/techpubs/en_US/junos13.3/topics/task/configuration/inline-flow-monitoring.html#VT5jL4VmFUHwaj4i.97

set interfaces ge-1/1/0 unit 0 family inet address 172.16.200.4/16

Continue reading “Netflow on Juniper”

References   [ + ]

1. http://www.juniper.net/techpubs/en_US/junos13.3/topics/task/configuration/inline-flow-monitoring.html#VT5jL4VmFUHwaj4i.97

RADIUS Authentication on Juniper

This article shows how to configure a Juniper router to authenticate users on a RADIUS server.

1. Configure the router with the RADIUS server information:

[edit system]
set system radius-server 10.0.12.1 port 1812
set system radius-server 10.0.12.1 secret yourpassword
set system radius-server 10.0.12.1 timeout 5
set system radius-server 10.0.12.1 retry 3
set system radius-server 10.0.12.1 source-address 192.168.120.4

In this case, the RADIUS server is with the IP address of 10.0.12.1, UDP port 1812.

Continue reading “RADIUS Authentication on Juniper”

Adding a Netflow Listener to Cacti

This article explains how to add new Netflow listeners to Cacti. By default, Cacti is not able to show Netflow reports. So, to follow the steps in this article, the Flowview plugin have to be installed on Cacti.

1. Configure Cacti server to receive and store the netflow files adding the lines shown below, one line for each router:

vi /etc/flow-tools/flow-capture.conf

-V 5 -w /var/flow/ABC-Router -n 275 -N 3 -E500M 0/0/3001
-V 5 -w /var/flow/DEF-Router -n 275 -N 3 -E500M 0/0/3002
-V 5 -w /var/flow/GHI-Router -n 275 -N 3 -E500M 0/0/3003
-V 5 -w /var/flow/JKL-Router -n 275 -N 3 -E500M 0/0/3004
-V 5 -w /var/flow/MNO-Router -n 275 -N 3 -E500M 0/0/3005
-V 5 -w /var/flow/PQR-Router -n 275 -N 3 -E500M 0/0/3006
-V 5 -w /var/flow/STU-Router -n 275 -N 3 -E500M 0/0/3007
-V 5 -w /var/flow/VWX-Router -n 275 -N 3 -E500M 0/0/3008
-V 5 -w /var/flow/XYZ-Router -n 275 -N 3 -E500M 0/0/3009

Continue reading “Adding a Netflow Listener to Cacti”

Traffic Classification and Marking on HP Switches

1. The QoS service offered by the ISP allows for control of how traffic is prioritised and bandwidth is reserved, with three queues available (multimedia – VoIP, critical data and normal data). Packets must be remarked with the following values to be classified on a each queue:

Continue reading “Traffic Classification and Marking on HP Switches”

Limiting Application Bandwidth on HP Switches

In this article we will configure the HP7510 switch to limit the bandwidth for two specific applications. The switch is placed in the company central building and is connected to the WAN router that provides access to offices in different remote locations. Continue reading “Limiting Application Bandwidth on HP Switches”

Traffic Classification and Marking on Cisco IOS

In this article I will show how to mark IP packets to prioritize multimedia and critical applications following a QoS policy that will be later enforced inside the ISP cloud.

1. The QoS service offered by the ISP allows for control of how traffic is prioritized and bandwidth is reserved, with three queues available as shown in the figure below.

Continue reading “Traffic Classification and Marking on Cisco IOS”