Ad Widget

Collapse

Monitoring Bonding (bond0)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • aic
    Member
    • Oct 2010
    • 50

    #1

    Monitoring Bonding (bond0)

    Hello All,

    I am monitoring NIC interfase with this configuration:

    net.if.in[eth0,bytes]


    Is it possible monitor Aggregation configuring an entry like this:

    net.if.in[bond0,bytes] or net.if.in[bond0:1,bytes]

    I did it without successfull results. Is there any other trick?

    Thanks in advance.
    aic
  • alixen
    Senior Member
    • Apr 2006
    • 474

    #2
    Hi,

    We are using :
    • net.if.in[bond0,bytes]
    • net.if.out[bond0,bytes]

    to monitor a bonded interface on several Linux servers and they work fine.

    However, I don't know if it works for an alias (bond0:1).

    Regards,
    Alixen
    http://www.alixen.fr/zabbix.html

    Comment

    • aic
      Member
      • Oct 2010
      • 50

      #3
      Thanks for your e-mail.

      I tried and I am not getting info if I set up ...[bond0:1]

      So, can I assume we will get this feature in a future release?

      Thanks!
      aic

      Comment

      • alixen
        Senior Member
        • Apr 2006
        • 474

        #4
        Hi,

        Originally posted by aic
        Thanks for your e-mail.

        I tried and I am not getting info if I set up ...[bond0:1]

        So, can I assume we will get this feature in a future release?

        Thanks!
        aic
        It is probably a limitation in Linux not Zabbix.
        I have no aliases on bonded interfaces but on an ethernet interface, ifconfig gives following results:
        Code:
        eth2      Link encap:Ethernet  HWaddr 00:11:43:34:df:81  
                  inet addr:192.168.0.11  Bcast:192.168.0.255  Mask:255.255.255.0
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                  RX packets:21773048 errors:0 dropped:0 overruns:0 frame:0
                  TX packets:19024842 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000 
                  RX bytes:2087873159 (1.9 GiB)  TX bytes:3072307430 (2.8 GiB)
        
        eth2:0    Link encap:Ethernet  HWaddr 00:11:43:34:df:81  
                  inet addr:192.168.0.16  Bcast:192.168.0.255  Mask:255.255.255.0
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        
        eth2:1    Link encap:Ethernet  HWaddr 00:11:43:34:df:81  
                  inet addr:192.168.0.18  Bcast:192.168.0.255  Mask:255.255.255.0
                  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
        As you can see, there is no statistics on aliases. All traffic is reported on main interface.

        Regards,
        Alixen
        http://www.alixen.fr/zabbix.html

        Comment

        • aic
          Member
          • Oct 2010
          • 50

          #5
          Thanks alixen!

          I guess you are correct. I re-checked and I am not gathering statistics on aliases either.

          Code:
          bond0     Link encap:Ethernet  HWaddr 00:BA:BA:BA:BA:01
                       inet addr:192.x.x.x  Bcast:192.x.x.x  Mask:255.255.255.0
                       inet6 addr: fe80::2ba:baff:feba:ba01/64 Scope:Link
                       UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
                       RX packets:53687662 errors:0 dropped:10307 overruns:0 frame:10796
                       TX packets:75857165 errors:0 dropped:0 overruns:0 carrier:0
                       collisions:0 txqueuelen:0
                       RX bytes:11248520928 (10.4 GiB)  TX bytes:78834461856 (73.4 GiB)
          
          bond0:1   Link encap:Ethernet  HWaddr 00:BA:BA:BA:BA:01
                        inet addr:192.x.x.x  Bcast:192.x.x.x  Mask:255.255.255.0
                        UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          Regards,
          aic
          Last edited by aic; 29-10-2010, 13:37.

          Comment

          Working...