FLOWVIEW SETTING
Moderators: Developers, Moderators
-
- Cacti User
- Posts: 60
- Joined: Thu Apr 18, 2024 10:40 pm
FLOWVIEW SETTING
hello, any help me, When installing FlowView, does the switch need to add a specific script or can it automatically retrieve data for the FlowView plugin? thanks
-
- Cacti User
- Posts: 60
- Joined: Thu Apr 18, 2024 10:40 pm
Re: FLOWVIEW SETTING
I have attached the following files
- Attachments
-
- seting flowview
- Screenshot 2025-01-10 145012.png (92.69 KiB) Viewed 600 times
Re: FLOWVIEW SETTING
you need configure netflow on you switch/router.
How to use Flowview plugin is described in /path/to/cacti/plugins/flowview/README.md
How to use Flowview plugin is described in /path/to/cacti/plugins/flowview/README.md
Let the Cacti grow!
Re: FLOWVIEW SETTING
You need to run listener on your system. It is described in plugins/flowview/service/README.md
Let the Cacti grow!
-
- Cacti User
- Posts: 60
- Joined: Thu Apr 18, 2024 10:40 pm
Re: FLOWVIEW SETTING
thanks sir, do i need to add a special netflow script to the switch? or maybe there is a specific script that i need to add to the switch? i have tried to create a listener, can i please check your dm sir?
Re: FLOWVIEW SETTING
no script. Configure netflow on your switch and destination will be your cacti device.
Run listener on your cacti, I wrote about listener above
Run listener on your cacti, I wrote about listener above
Let the Cacti grow!
-
- Cacti User
- Posts: 60
- Joined: Thu Apr 18, 2024 10:40 pm
Re: FLOWVIEW SETTING
can I read the listener on this link?
https://github.com/Cacti/plugin_flowvie ... /README.md
for configure netflow settings is in the listener menu, right sir?
Re: FLOWVIEW SETTING
What brand are your switch ?
Test
Almalinux
php 8.2.14
mariadb 10.6.16
Cacti 1.2.27
Spine 1.2.27
RRD 1.7.2
thold 1.8
monitor 2.5
syslog 3.2
flowview: 3.3
weathermap 1.0 Beta
Almalinux
php 8.2.14
mariadb 10.6.16
Cacti 1.2.27
Spine 1.2.27
RRD 1.7.2
thold 1.8
monitor 2.5
syslog 3.2
flowview: 3.3
weathermap 1.0 Beta
-
- Cacti User
- Posts: 60
- Joined: Thu Apr 18, 2024 10:40 pm
Re: FLOWVIEW SETTING
So here is a sample of config you can use on your switch:
flow exporter CACTI
description Cacti-server
destination <IP of cacti>
transport udp <UDP port you define on cacti as Listener port>
flow record R1
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
match transport source-port
match transport destination-port
match ipv4 tos
match interface input
collect counter bytes
collect counter packets
collect interface output
!
flow monitor M1
record R1
exporter CACTI
cache entries 1000
Then you apply the flow function on the port you want to monitor:
interface <interface name like Te1/1/27>
ip flow monitor M1 input
it's basically the same for all model of Cisco switch
flow exporter CACTI
description Cacti-server
destination <IP of cacti>
transport udp <UDP port you define on cacti as Listener port>
flow record R1
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
match transport source-port
match transport destination-port
match ipv4 tos
match interface input
collect counter bytes
collect counter packets
collect interface output
!
flow monitor M1
record R1
exporter CACTI
cache entries 1000
Then you apply the flow function on the port you want to monitor:
interface <interface name like Te1/1/27>
ip flow monitor M1 input
it's basically the same for all model of Cisco switch
Test
Almalinux
php 8.2.14
mariadb 10.6.16
Cacti 1.2.27
Spine 1.2.27
RRD 1.7.2
thold 1.8
monitor 2.5
syslog 3.2
flowview: 3.3
weathermap 1.0 Beta
Almalinux
php 8.2.14
mariadb 10.6.16
Cacti 1.2.27
Spine 1.2.27
RRD 1.7.2
thold 1.8
monitor 2.5
syslog 3.2
flowview: 3.3
weathermap 1.0 Beta
-
- Cacti User
- Posts: 60
- Joined: Thu Apr 18, 2024 10:40 pm
Re: FLOWVIEW SETTING
Thank you sir,Rno wrote: ↑Fri Jan 10, 2025 10:28 am So here is a sample of config you can use on your switch:
flow exporter CACTI
description Cacti-server
destination <IP of cacti>
transport udp <UDP port you define on cacti as Listener port>
flow record R1
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
match transport source-port
match transport destination-port
match ipv4 tos
match interface input
collect counter bytes
collect counter packets
collect interface output
!
flow monitor M1
record R1
exporter CACTI
cache entries 1000
Then you apply the flow function on the port you want to monitor:
interface <interface name like Te1/1/27>
ip flow monitor M1 input
it's basically the same for all model of Cisco switch
In the listener settings section "allowed Host Range" is it filled with the IP Address used when remote device or what?
And for the "destination <ip of cacti>" section, is it filled with the IP of the cacti server? For example, I use the cacti server "192.168.x.x" -> "destination 192.168.x.x" is that right?
- Attachments
-
- Screenshot 2025-01-13 094112.png (36.24 KiB) Viewed 520 times
-
- Cacti User
- Posts: 60
- Joined: Thu Apr 18, 2024 10:40 pm
Re: FLOWVIEW SETTING
sorry I have tried to help with DM, please help check DM sir for details, I have tried to apply it but it still doesn't work, maybe there are suggestions, thank youRno wrote: ↑Fri Jan 10, 2025 10:28 am So here is a sample of config you can use on your switch:
flow exporter CACTI
description Cacti-server
destination <IP of cacti>
transport udp <UDP port you define on cacti as Listener port>
flow record R1
match ipv4 protocol
match ipv4 source address
match ipv4 destination address
match transport source-port
match transport destination-port
match ipv4 tos
match interface input
collect counter bytes
collect counter packets
collect interface output
!
flow monitor M1
record R1
exporter CACTI
cache entries 1000
Then you apply the flow function on the port you want to monitor:
interface <interface name like Te1/1/27>
ip flow monitor M1 input
it's basically the same for all model of Cisco switch
Re: FLOWVIEW SETTING
The "allowed host Range" can be let to 0, no filter on who is sending the traffic.
but you can also specify the IP of the device that send the netflow traffic.
And Yes <IP of cacti> mean the ip of the cacti server.
but you can also specify the IP of the device that send the netflow traffic.
And Yes <IP of cacti> mean the ip of the cacti server.
duwijakarta wrote: ↑Sun Jan 12, 2025 9:45 pm Thank you sir,
In the listener settings section "allowed Host Range" is it filled with the IP Address used when remote device or what?
And for the "destination <ip of cacti>" section, is it filled with the IP of the cacti server? For example, I use the cacti server "192.168.x.x" -> "destination 192.168.x.x" is that right?
Test
Almalinux
php 8.2.14
mariadb 10.6.16
Cacti 1.2.27
Spine 1.2.27
RRD 1.7.2
thold 1.8
monitor 2.5
syslog 3.2
flowview: 3.3
weathermap 1.0 Beta
Almalinux
php 8.2.14
mariadb 10.6.16
Cacti 1.2.27
Spine 1.2.27
RRD 1.7.2
thold 1.8
monitor 2.5
syslog 3.2
flowview: 3.3
weathermap 1.0 Beta
-
- Cacti User
- Posts: 60
- Joined: Thu Apr 18, 2024 10:40 pm
Re: FLOWVIEW SETTING
I have tried to apply it as I DMed you sir, please help me correct which part is still wrong because currently I have tried it and there is still no data that can be seen in flowviewRno wrote: ↑Mon Jan 13, 2025 2:32 am The "allowed host Range" can be let to 0, no filter on who is sending the traffic.
but you can also specify the IP of the device that send the netflow traffic.
And Yes <IP of cacti> mean the ip of the cacti server.
duwijakarta wrote: ↑Sun Jan 12, 2025 9:45 pm Thank you sir,
In the listener settings section "allowed Host Range" is it filled with the IP Address used when remote device or what?
And for the "destination <ip of cacti>" section, is it filled with the IP of the cacti server? For example, I use the cacti server "192.168.x.x" -> "destination 192.168.x.x" is that right?
Who is online
Users browsing this forum: No registered users and 3 guests