Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1167
  • Last Modified:

Cacti template for IP Aliases

I have a RHEL 5 server with Cacti installed. Since this server has multiple IP addresses using IP Aliasing, I need to setup a Cacti template that can monitor each of the IPs for inbound and outbound traffic. I tried using the example document I found here (http://www.roth.lu/cacti-snmp-tut.htm), but it seems to be lacking as it is not clearly written.

Has anyone else tried this type of monitoring? If so, how did you configure Cacti to monitor per IP Alias interface?
0
Michael Worsham
Asked:
Michael Worsham
  • 3
  • 3
1 Solution
 
gremwellCommented:
The page you refer to describes how to configure iptables to count number of incoming and outgoing packets per IP alias. Then the author makes this information available via SNMP. Next it use Cacti to fetch the data from SNMP.

Please specify what part you are having difficulties with.
0
 
Michael WorshamInfrastructure / Solutions ArchitectAuthor Commented:
The iptables porition isn't showing anything. It keeps showing the amount of data being '0'.

Plus, the section labeled "3B. Graph Template" is confusing in its wording. What actually needs to be modified and in what order, etc?

0
 
gremwellCommented:
The IP tables part seems to work fine for me. I have attached the scripts (iptables_traffic_rules_gen.sh is slightly modified to take care of chain creation).

abb@d820:/usr/local/sbin/snmp_ips$ sudo ./iptables_traffic_rules_gen.sh

abb@d820:/usr/local/sbin/snmp_ips$ ./iptables_traffic_iplist.sh -g
192.168.1.103
127.0.0.1
172.16.202.1
172.16.180.1
172.16.190.1
172.16.57.1
172.16.58.1
192.168.122.1

abb@d820:/usr/local/sbin/snmp_ips$ ./iptables_traffic_iplist.sh -i
1
2
3
4
5
6
7
8

abb@d820:/usr/local/sbin/snmp_ips$ sudo ./iptables_traffic_eval.sh in
13772
0
0
0
0
0
0
0

abb@d820:/usr/local/sbin/snmp_ips$ sudo ./iptables_traffic_eval.sh out
21070
0
0
0
0
0
0
0

And, after ping localhost:

abb@d820:/usr/local/sbin/snmp_ips$ sudo ./iptables_traffic_eval.sh  in
16582
672
0
0
0
0
0
0

Hope it helps a bit. Can't help you with graph templates though, I don't use cacti myself.
iptables-traffic.zip
0
A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

 
Michael WorshamInfrastructure / Solutions ArchitectAuthor Commented:
First I did the following:

iptables -N traffic_in
iptables -N traffic_out
iptables -I INPUT 1 -j traffic_in
iptables -I OUTPUT 1 -j traffic_out

Then I tried your scripts. The "iptables_traffic_eval.sh" in nor out doesn't display anything.

Below is the output when I just do 'iptables -vxnL'.


Chain INPUT (policy ACCEPT 1350998 packets, 1824050953 bytes)
    pkts      bytes target     prot opt in     out     source               destination
     244    19151 traffic_in  all  --  *      *       0.0.0.0/0            0.0.0.0/0

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
    pkts      bytes target     prot opt in     out     source               destination

Chain OUTPUT (policy ACCEPT 967645 packets, 65040517 bytes)
    pkts      bytes target     prot opt in     out     source               destination
     185    30288 traffic_out  all  --  *      *       0.0.0.0/0            0.0.0.0/0

Chain traffic_in (1 references)
    pkts      bytes target     prot opt in     out     source               destination

Chain traffic_out (1 references)
    pkts      bytes target     prot opt in     out     source               destination

Open in new window

0
 
gremwellCommented:
I'm not sure why chain traffic_in and traffic_out chains are empty in your case. Normally they should be populated by iptables_traffic_rules_gen.sh. Are you sure you have executed it? For me the end of the output you have quoted looks like following:
-------------
Chain traffic_in (1 references)
    pkts      bytes target     prot opt in     out     source               destination        
       0        0            all  --  *      !lo     0.0.0.0/0            169.254.6.228      
       0        0            all  --  *      !lo     0.0.0.0/0            127.0.0.1          
       0        0            all  --  *      !lo     0.0.0.0/0            172.16.202.1        
       0        0            all  --  *      !lo     0.0.0.0/0            172.16.180.1        
       0        0            all  --  *      !lo     0.0.0.0/0            172.16.190.1        
       0        0            all  --  *      !lo     0.0.0.0/0            172.16.57.1        
       0        0            all  --  *      !lo     0.0.0.0/0            172.16.58.1        
       0        0            all  --  *      !lo     0.0.0.0/0            192.168.122.1      
      17     2000            all  --  *      !lo     0.0.0.0/0            192.168.1.103      

Chain traffic_out (1 references)
    pkts      bytes target     prot opt in     out     source               destination        
       0        0            all  --  !lo    *       169.254.6.228        0.0.0.0/0          
       0        0            all  --  !lo    *       127.0.0.1            0.0.0.0/0          
       0        0            all  --  !lo    *       172.16.202.1         0.0.0.0/0          
       0        0            all  --  !lo    *       172.16.180.1         0.0.0.0/0          
       0        0            all  --  !lo    *       172.16.190.1         0.0.0.0/0          
       0        0            all  --  !lo    *       172.16.57.1          0.0.0.0/0          
       0        0            all  --  !lo    *       172.16.58.1          0.0.0.0/0          
       0        0            all  --  !lo    *       192.168.122.1        0.0.0.0/0          
      23     1686            all  --  !lo    *       192.168.1.103        0.0.0.0/0          
-------------

Maybe the output of the following commands will give us some clue:

sh -x ./iptables_traffic_iplist.sh -g
sh -x ./iptables_traffic_iplist.sh -i
sudo sh -x ./iptables_traffic_rules_gen.sh
0
 
Michael WorshamInfrastructure / Solutions ArchitectAuthor Commented:
The modified scripts helped out a lot. It seems I didn't run the initial iptables_traffic_rules_gen.sh script correctly, thus nothing was being produced.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now