Trending too many interfaces
list Colin Coe
Hi all I've several Linux (RHEV) virtualisation servers. In the trends screen for these servers, I see a list of interfaces similar to the below: --- DMZ Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 GreenZone Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 Mgmt Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond0 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:0E bond1 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond1.641 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond1.642 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond1.644 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond2 Link encap:Ethernet HWaddr 00:1B:21:0D:CC:1A eth0 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:0E eth1 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:0E eth2 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 eth3 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 eth4 Link encap:Ethernet HWaddr 00:1B:21:0D:CC:1A eth5 Link encap:Ethernet HWaddr 00:1B:21:0D:CC:1A lo Link encap:Local Loopback rhevm Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:0E virtio_10_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:0C virtio_11_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:04 virtio_12_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:06 virtio_13_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:07 virtio_15_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:02 virtio_16_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:0B --- Only two of these have IP addresses, how can I limit Xymon to just showing the ones with IPs? Thanks CC -- RHCE#805007969328369
list Colin Coe
Anyone have any thoughts on this? The only interfaces I want graphed are "rhevm" and "bond2". TIA CC
▸
On Thu, Apr 21, 2011 at 3:30 PM, Colin Coe <user-5b250cd7a540@xymon.invalid> wrote:Hi all I've several Linux (RHEV) virtualisation servers. In the trends screen for these servers, I see a list of interfaces similar to the below: --- DMZ Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 GreenZone Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 Mgmt Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond0 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:0E bond1 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond1.641 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond1.642 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond1.644 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 bond2 Link encap:Ethernet HWaddr 00:1B:21:0D:CC:1A eth0 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:0E eth1 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:0E eth2 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 eth3 Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:12 eth4 Link encap:Ethernet HWaddr 00:1B:21:0D:CC:1A eth5 Link encap:Ethernet HWaddr 00:1B:21:0D:CC:1A lo Link encap:Local Loopback rhevm Link encap:Ethernet HWaddr 3C:4A:92:6E:FD:0E virtio_10_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:0C virtio_11_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:04 virtio_12_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:06 virtio_13_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:07 virtio_15_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:02 virtio_16_1 Link encap:Ethernet HWaddr FE:1A:4A:16:66:0B --- Only two of these have IP addresses, how can I limit Xymon to just showing the ones with IPs? Thanks CC -- RHCE#805007969328369
--
RHCE#805007969328369
list Tim McCloskey
This is a crazy guess, you don't mention which version of xymon so this may be way off. It may be way off anyway :)
If you are talking about the trends/"Network Traffic" graph it seems to be getting that data from the 'ifstat' var.
Some details follow.
1. what we graph for ifstat
hobbitgraph.cfg: FNPATTERN ifstat.(.+).rrd
See data/rrd/$hostname/ifstat.*
2. where ifstat originates
client/hobbitclient-linux.sh:
echo "[ifstat]"
/sbin/ifconfig
3. what happens to ifstat
hobbitd/client/linux.c: ifstatstr = getdata("ifstat");
hobbitd/client/linux.c: unix_ifstat_report(hostname, clienttype, os, hinfo, fromline, timestr, ifstatstr); <--- ifstatstr
You should be able to modify the client shell script to report other than ifconfig -a (which seems to be what is currently captured). Of course, there must be a better way.
Regards,
Tim
▸
From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid]
Sent: Tuesday, April 26, 2011 7:02 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Trending too many interfaces
Anyone have any thoughts on this?
The only interfaces I want graphed are "rhevm" and "bond2".
list Colin Coe
Hi Vernon and Tim I'm working in a new dev/test environment using Xymon 4.3.2. I'd wanted to avoid hacking the client-side script but if that's whats required, I'll have a look. TIA CC
▸
On Wed, Apr 27, 2011 at 11:01 AM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:This is a crazy guess, you don't mention which version of xymon so this may be way off. It may be way off anyway :)
If you are talking about the trends/"Network Traffic" graph it seems to be getting that data from the 'ifstat' var.
Some details follow.
1. what we graph for ifstat
hobbitgraph.cfg: FNPATTERN ifstat.(.+).rrd
See data/rrd/$hostname/ifstat.*
2. where ifstat originates
client/hobbitclient-linux.sh:
echo "[ifstat]"
/sbin/ifconfig
3. what happens to ifstat
hobbitd/client/linux.c: ifstatstr = getdata("ifstat");
hobbitd/client/linux.c: unix_ifstat_report(hostname, clienttype, os, hinfo, fromline, timestr, ifstatstr); <--- ifstatstr
You should be able to modify the client shell script to report other than ifconfig -a (which seems to be what is currently captured). Of course, there must be a better way.
Regards,
Tim
From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid]
Sent: Tuesday, April 26, 2011 7:02 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Trending too many interfaces
Anyone have any thoughts on this?
The only interfaces I want graphed are "rhevm" and "bond2".
--
RHCE#805007969328369
list Tim McCloskey
Colin, I have not installed any of the newer xymon versions, this is from 4.2.0. On a system with eth0->eth3 plumbed up I set the client shell script (client/bin/hobbitclient-linux.sh) to: echo "[ifstat]" /sbin/ifconfig eth0 /sbin/ifconfig eth2 Verified the data sent from one of the 'Client data available' data sets. Removed the rrd files for ifstat from the server for that client. (stopped/started the client). On the trends page I see eth0 and eth2 only, no eth1 or eth3. Yeah, it's a hack but it's fairly minor and should be easy enough to manage. Just my 3 cents.
▸
Tim
From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid]
Sent: Tuesday, April 26, 2011 8:19 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Trending too many interfaces
Hi Vernon and Tim
I'm working in a new dev/test environment using Xymon 4.3.2.
I'd wanted to avoid hacking the client-side script but if that's whats
required, I'll have a look.
TIA
CC
On Wed, Apr 27, 2011 at 11:01 AM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:This is a crazy guess, you don't mention which version of xymon so this may be way off. It may be way off anyway :)
If you are talking about the trends/"Network Traffic" graph it seems to be getting that data from the 'ifstat' var.
Some details follow.
1. what we graph for ifstat
hobbitgraph.cfg: FNPATTERN ifstat.(.+).rrd
See data/rrd/$hostname/ifstat.*
2. where ifstat originates
client/hobbitclient-linux.sh:
echo "[ifstat]"
/sbin/ifconfig
3. what happens to ifstat
hobbitd/client/linux.c: ifstatstr = getdata("ifstat");
hobbitd/client/linux.c: unix_ifstat_report(hostname, clienttype, os, hinfo, fromline, timestr, ifstatstr); <--- ifstatstr
You should be able to modify the client shell script to report other than ifconfig -a (which seems to be what is currently captured). Of course, there must be a better way.
Regards,
Tim
From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid]
Sent: Tuesday, April 26, 2011 7:02 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Trending too many interfaces
Anyone have any thoughts on this?
The only interfaces I want graphed are "rhevm" and "bond2".
-- RHCE#805007969328369
list Colin Coe
Yeah, that's pretty much what I did, except I now notice that the bridge interfaces are not listed on the trending page. One of these bridge interfaces has an IP address and I'd like to trend it. I've done a few quick greps through the source but can't see where these bridges a re being stripped out. CC
▸
On Thu, Apr 28, 2011 at 12:14 AM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:Colin, I have not installed any of the newer xymon versions, this is from 4.2.0. On a system with eth0->eth3 plumbed up I set the client shell script (client/bin/hobbitclient-linux.sh) to: echo "[ifstat]" /sbin/ifconfig eth0 /sbin/ifconfig eth2 Verified the data sent from one of the 'Client data available' data sets. Removed the rrd files for ifstat from the server for that client. (stopped/started the client). On the trends page I see eth0 and eth2 only, no eth1 or eth3. Yeah, it's a hack but it's fairly minor and should be easy enough to manage. Just my 3 cents. Tim From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid] Sent: Tuesday, April 26, 2011 8:19 PM To: xymon at xymon.com Subject: Re: [Xymon] Trending too many interfaces Hi Vernon and Tim I'm working in a new dev/test environment using Xymon 4.3.2. I'd wanted to avoid hacking the client-side script but if that's whats required, I'll have a look. TIA CC On Wed, Apr 27, 2011 at 11:01 AM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:This is a crazy guess, you don't mention which version of xymon so this may be way off. It may be way off anyway :) If you are talking about the trends/"Network Traffic" graph it seems to be getting that data from the 'ifstat' var. Some details follow. 1. what we graph for ifstat hobbitgraph.cfg: FNPATTERN ifstat.(.+).rrd See data/rrd/$hostname/ifstat.* 2. where ifstat originates client/hobbitclient-linux.sh: echo "[ifstat]" /sbin/ifconfig 3. what happens to ifstat hobbitd/client/linux.c: ifstatstr = getdata("ifstat"); hobbitd/client/linux.c: unix_ifstat_report(hostname, clienttype, os, hinfo, fromline, timestr, ifstatstr); <--- ifstatstr You should be able to modify the client shell script to report other than ifconfig -a (which seems to be what is currently captured). Of course, there must be a better way. Regards, Tim From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid] Sent: Tuesday, April 26, 2011 7:02 PM To: xymon at xymon.com Subject: Re: [Xymon] Trending too many interfaces Anyone have any thoughts on this? The only interfaces I want graphed are "rhevm" and "bond2".-- RHCE#805007969328369
--
RHCE#805007969328369
list Tim McCloskey
What shows up under 'Client data available' for the [ifconfig] and [ifstat] details? [ifconfig] should list all of the interfaces. [ifstat] should only show what you defined.
The only interfaces I want graphed are "rhevm" and "bond2".
That would be: echo "[ifstat]" /sbin/ifconfig rhevm /sbin/ifconfig bond2 [ifstat] should show the output from the above commands, which should then be on the trends page under Network Traffic. I'll be taking a look at 4.3.2 sometime in the near future, maybe it's different there.
▸
Tim
From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid]
Sent: Wednesday, April 27, 2011 4:02 PM
To: xymon at xymon.com
Subject: Re: [Xymon] Trending too many interfaces
Yeah, that's pretty much what I did, except I now notice that the
bridge interfaces are not listed on the trending page. One of these
bridge interfaces has an IP address and I'd like to trend it.
I've done a few quick greps through the source but can't see where
these bridges a re being stripped out.
CC
On Thu, Apr 28, 2011 at 12:14 AM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:Colin, I have not installed any of the newer xymon versions, this is from 4.2.0. On a system with eth0->eth3 plumbed up I set the client shell script (client/bin/hobbitclient-linux.sh) to: echo "[ifstat]" /sbin/ifconfig eth0 /sbin/ifconfig eth2 Verified the data sent from one of the 'Client data available' data sets. Removed the rrd files for ifstat from the server for that client. (stopped/started the client). On the trends page I see eth0 and eth2 only, no eth1 or eth3. Yeah, it's a hack but it's fairly minor and should be easy enough to manage. Just my 3 cents. Tim From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid] Sent: Tuesday, April 26, 2011 8:19 PM To: xymon at xymon.com Subject: Re: [Xymon] Trending too many interfaces Hi Vernon and Tim I'm working in a new dev/test environment using Xymon 4.3.2. I'd wanted to avoid hacking the client-side script but if that's whats required, I'll have a look. TIA CC On Wed, Apr 27, 2011 at 11:01 AM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:This is a crazy guess, you don't mention which version of xymon so this may be way off. It may be way off anyway :) If you are talking about the trends/"Network Traffic" graph it seems to be getting that data from the 'ifstat' var. Some details follow. 1. what we graph for ifstat hobbitgraph.cfg: FNPATTERN ifstat.(.+).rrd See data/rrd/$hostname/ifstat.* 2. where ifstat originates client/hobbitclient-linux.sh: echo "[ifstat]" /sbin/ifconfig 3. what happens to ifstat hobbitd/client/linux.c: ifstatstr = getdata("ifstat"); hobbitd/client/linux.c: unix_ifstat_report(hostname, clienttype, os, hinfo, fromline, timestr, ifstatstr); <--- ifstatstr You should be able to modify the client shell script to report other than ifconfig -a (which seems to be what is currently captured). Of course, there must be a better way. Regards, Tim From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid] Sent: Tuesday, April 26, 2011 7:02 PM To: xymon at xymon.com Subject: Re: [Xymon] Trending too many interfaces Anyone have any thoughts on this? The only interfaces I want graphed are "rhevm" and "bond2".-- RHCE#805007969328369
-- RHCE#805007969328369
list Colin Coe
Yep, in /usr/lib/xymon/client/bin/xymonclient-linux.sh I have: --- # Bug in RedHat's netstat spews annoying error messages. netstat -ant 2>/dev/null echo "[ifstat]" /sbin/ifconfig lo /sbin/ifconfig bond2 /sbin/ifconfig rhevm # Report mdstat data if it exists --- However there is no rhevm interface listed on the trending page.
▸
CC
On Thu, Apr 28, 2011 at 7:32 AM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:What shows up under 'Client data available' for the [ifconfig] and [ifstat] details? [ifconfig] should list all of the interfaces. [ifstat] should only show what you defined.The only interfaces I want graphed are "rhevm" and "bond2".That would be: echo "[ifstat]" /sbin/ifconfig rhevm /sbin/ifconfig bond2 [ifstat] should show the output from the above commands, which should then be on the trends page under Network Traffic. I'll be taking a look at 4.3.2 sometime in the near future, maybe it's different there. Tim From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid] Sent: Wednesday, April 27, 2011 4:02 PM To: xymon at xymon.com Subject: Re: [Xymon] Trending too many interfaces Yeah, that's pretty much what I did, except I now notice that the bridge interfaces are not listed on the trending page. One of these bridge interfaces has an IP address and I'd like to trend it. I've done a few quick greps through the source but can't see where these bridges a re being stripped out. CC On Thu, Apr 28, 2011 at 12:14 AM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:Colin, I have not installed any of the newer xymon versions, this is from 4.2.0. On a system with eth0->eth3 plumbed up I set the client shell script (client/bin/hobbitclient-linux.sh) to: echo "[ifstat]" /sbin/ifconfig eth0 /sbin/ifconfig eth2 Verified the data sent from one of the 'Client data available' data sets. Removed the rrd files for ifstat from the server for that client. (stopped/started the client). On the trends page I see eth0 and eth2 only, no eth1 or eth3. Yeah, it's a hack but it's fairly minor and should be easy enough to manage. Just my 3 cents. Tim From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid] Sent: Tuesday, April 26, 2011 8:19 PM To: xymon at xymon.com Subject: Re: [Xymon] Trending too many interfaces Hi Vernon and Tim I'm working in a new dev/test environment using Xymon 4.3.2. I'd wanted to avoid hacking the client-side script but if that's whats required, I'll have a look. TIA CC On Wed, Apr 27, 2011 at 11:01 AM, Tim McCloskey <user-440820cc07d6@xymon.invalid> wrote:This is a crazy guess, you don't mention which version of xymon so this may be way off. It may be way off anyway :) If you are talking about the trends/"Network Traffic" graph it seems to be getting that data from the 'ifstat' var. Some details follow. 1. what we graph for ifstat hobbitgraph.cfg: FNPATTERN ifstat.(.+).rrd See data/rrd/$hostname/ifstat.* 2. where ifstat originates client/hobbitclient-linux.sh: echo "[ifstat]" /sbin/ifconfig 3. what happens to ifstat hobbitd/client/linux.c: ifstatstr = getdata("ifstat"); hobbitd/client/linux.c: unix_ifstat_report(hostname, clienttype, os, hinfo, fromline, timestr, ifstatstr); <--- ifstatstr You should be able to modify the client shell script to report other than ifconfig -a (which seems to be what is currently captured). Of course, there must be a better way. Regards, Tim From: xymon-bounces at xymon.com [xymon-bounces at xymon.com] On Behalf Of Colin Coe [user-5b250cd7a540@xymon.invalid] Sent: Tuesday, April 26, 2011 7:02 PM To: xymon at xymon.com Subject: Re: [Xymon] Trending too many interfaces Anyone have any thoughts on this? The only interfaces I want graphed are "rhevm" and "bond2".-- RHCE#805007969328369-- RHCE#805007969328369
--
RHCE#805007969328369