Network Traffic Graph - Fedora 15
list Sam L
I've been running xymon 4.3.3 on Fedora 14 for a month or two without any issues. I recently upgraded to Fedora 15 and now my "Network Traffic" graph in trends is no longer working. They changed up something with network card naming in Fedora 15, and my NIC is no longer called eth0 (or eth<anything>). The interface is now called p33p1. Should xymon be able to figure that out on it's own or do I need to tell it to look for more than ethX? Thanks. s0a4m
list Sam L
Hey, I was just wondering if anyone had any ideas about this? Thanks!
▸
From: user-4449a49ea16f@xymon.invalid
To: xymon at xymon.com
Subject: Network Traffic Graph - Fedora 15
Date: Sat, 2 Jul 2011 14:39:34 -0400
I've been running xymon 4.3.3 on Fedora 14 for a month or two without any issues. I recently upgraded to Fedora 15 and now my "Network Traffic" graph in trends is no longer working. They changed up something with network card naming in Fedora 15, and my NIC is no longer called eth0 (or eth<anything>). The interface is now called p33p1. Should xymon be able to figure that out on it's own or do I need to tell it to look for more than ethX?
Thanks.
s0a4m
list Vernon Everett
Hi Sam
I recall about 7 years ago, give or take, when Sun released the new
T2000 line of servers, NICs changed from being eri0, hme0, qfe1and
similar to being e1000g0, e1000g1.....
You could grab the old NICs by using a regex. They were all of the
form aaaX (a=Alpha, X=Numeric)
"^[a-z][a-z][a-z][0-9]" or something like that.
It all happened inside the C code, so I plead ignorance of the details.
The new NIC IDs no longer fitted the regex, and it broke Hobbit. (Yes,
it was called Hobbit back then)
Henrik was pretty quick off the mark though, and sorted me out with a
patch within a day or three.
(I am guessing he wasn't so busy back then)
It is possible that you have encountered something similar.
Henrik? Could it be?
I would go to your sysadmin guys and get them to stop playing
silly-buggers with the NIC naming conventions.
If they refuse to be reasonable, you might have to petition Henrik for a fix.
I still owe Henrik a beer for that T2000 fix. :-)
Regards
Vernon
▸
On 13 July 2011 10:36, Sam L <user-4449a49ea16f@xymon.invalid> wrote:Hey, I was just wondering if anyone had any ideas about this? Thanks! From: user-4449a49ea16f@xymon.invalid To: xymon at xymon.com Subject: Network Traffic Graph - Fedora 15 Date: Sat, 2 Jul 2011 14:39:34 -0400 I've been running xymon 4.3.3 on Fedora 14 for a month or two without any issues. I recently upgraded to Fedora 15 and now my "Network Traffic" graph in trends is no longer working. They changed up something with network card naming in Fedora 15, and my NIC is no longer called eth0 (or eth<anything>). The interface is now called p33p1. Should xymon be able to figure that out on it's own or do I need to tell it to look for more than ethX? Thanks. s0a4m
list Colin Coe
Vernon is correct. Fedora 15 moves away from eth[0-9], at least in some circumstances. See http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming CC On Wed, Jul 13, 2011 at 2:28 PM, Vernon Everett
▸
<user-b3f8dacb72c8@xymon.invalid> wrote:Hi Sam I recall about 7 years ago, give or take, when Sun released the new T2000 line of servers, NICs changed from being eri0, hme0, qfe1and similar to being e1000g0, e1000g1..... You could grab the old NICs by using a regex. They were all of the form aaaX (a=Alpha, X=Numeric) "^[a-z][a-z][a-z][0-9]" or something like that. It all happened inside the C code, so I plead ignorance of the details. The new NIC IDs no longer fitted the regex, and it broke Hobbit. (Yes, it was called Hobbit back then) Henrik was pretty quick off the mark though, and sorted me out with a patch within a day or three. (I am guessing he wasn't so busy back then) It is possible that you have encountered something similar. Henrik? Could it be? I would go to your sysadmin guys and get them to stop playing silly-buggers with the NIC naming conventions. If they refuse to be reasonable, you might have to petition Henrik for a fix. I still owe Henrik a beer for that T2000 fix. :-) Regards Vernon On 13 July 2011 10:36, Sam L <user-4449a49ea16f@xymon.invalid> wrote:Hey, I was just wondering if anyone had any ideas about this? Thanks! From: user-4449a49ea16f@xymon.invalid To: xymon at xymon.com Subject: Network Traffic Graph - Fedora 15 Date: Sat, 2 Jul 2011 14:39:34 -0400 I've been running xymon 4.3.3 on Fedora 14 for a month or two without any issues. I recently upgraded to Fedora 15 and now my "Network Traffic" graph in trends is no longer working. They changed up something with network card naming in Fedora 15, and my NIC is no longer called eth0 (or eth<anything>). The interface is now called p33p1. Should xymon be able to figure that out on it's own or do I need to tell it to look for more than ethX? Thanks. s0a4m
--
RHCE#805007969328369
list Sam L
Yes, I am aware Fedora changed the naming convention. My question is: How can I get the xymon network traffic graph (in trends) to work again? The only network traffic graph I have still only has eth0 in it (from old data before the Fedora upgrade.) I could probably force the name back to eth0 in the OS, but that seems like a cheesy workaround, since this is how the naming is going to be going forward. How can I get xymon to become aware that my NIC is called p33p1? Thanks for any guidance.
▸
Date: Wed, 13 Jul 2011 20:19:11 +0800 Subject: Re: [Xymon] Network Traffic Graph - Fedora 15 From: user-5b250cd7a540@xymon.invalid To: user-b3f8dacb72c8@xymon.invalid CC: user-4449a49ea16f@xymon.invalid; xymon at xymon.com Vernon is correct. Fedora 15 moves away from eth[0-9], at least in some circumstances. See http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming CC On Wed, Jul 13, 2011 at 2:28 PM, Vernon Everett <user-b3f8dacb72c8@xymon.invalid> wrote:Hi Sam I recall about 7 years ago, give or take, when Sun released the new T2000 line of servers, NICs changed from being eri0, hme0, qfe1and similar to being e1000g0, e1000g1..... You could grab the old NICs by using a regex. They were all of the form aaaX (a=Alpha, X=Numeric) "^[a-z][a-z][a-z][0-9]" or something like that. It all happened inside the C code, so I plead ignorance of the details. The new NIC IDs no longer fitted the regex, and it broke Hobbit. (Yes, it was called Hobbit back then) Henrik was pretty quick off the mark though, and sorted me out with a patch within a day or three. (I am guessing he wasn't so busy back then) It is possible that you have encountered something similar. Henrik? Could it be? I would go to your sysadmin guys and get them to stop playing silly-buggers with the NIC naming conventions. If they refuse to be reasonable, you might have to petition Henrik for a fix. I still owe Henrik a beer for that T2000 fix. :-) Regards Vernon On 13 July 2011 10:36, Sam L <user-4449a49ea16f@xymon.invalid> wrote:Hey, I was just wondering if anyone had any ideas about this? Thanks! From: user-4449a49ea16f@xymon.invalid To: xymon at xymon.com Subject: Network Traffic Graph - Fedora 15 Date: Sat, 2 Jul 2011 14:39:34 -0400 I've been running xymon 4.3.3 on Fedora 14 for a month or two without any issues. I recently upgraded to Fedora 15 and now my "Network Traffic" graph in trends is no longer working. They changed up something with network card naming in Fedora 15, and my NIC is no longer called eth0 (or eth<anything>). The interface is now called p33p1. Should xymon be able to figure that out on it's own or do I need to tell it to look for more than ethX? Thanks. s0a4m-- RHCE#805007969328369
list Sam L
Also, if this changed in Fedora now, then it means it is probably coming for Red Hat Enterprise Linux soon. And I assume this issue would hit more people then.
▸
From: user-4449a49ea16f@xymon.invalid
To: xymon at xymon.com
Subject: RE: [Xymon] Network Traffic Graph - Fedora 15
Date: Wed, 13 Jul 2011 13:29:21 -0400
Yes, I am aware Fedora changed the naming convention. My question is: How can I get the xymon network traffic graph (in trends) to work again? The only network traffic graph I have still only has eth0 in it (from old data before the Fedora upgrade.) I could probably force the name back to eth0 in the OS, but that seems like a cheesy workaround, since this is how the naming is going to be going forward. How can I get xymon to become aware that my NIC is called p33p1?
Thanks for any guidance.
Date: Wed, 13 Jul 2011 20:19:11 +0800 Subject: Re: [Xymon] Network Traffic Graph - Fedora 15 From: user-5b250cd7a540@xymon.invalid To: user-b3f8dacb72c8@xymon.invalid CC: user-4449a49ea16f@xymon.invalid; xymon at xymon.com Vernon is correct. Fedora 15 moves away from eth[0-9], at least in some circumstances. See http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming CC On Wed, Jul 13, 2011 at 2:28 PM, Vernon Everett <user-b3f8dacb72c8@xymon.invalid> wrote:Hi Sam I recall about 7 years ago, give or take, when Sun released the new T2000 line of servers, NICs changed from being eri0, hme0, qfe1and similar to being e1000g0, e1000g1..... You could grab the old NICs by using a regex. They were all of the form aaaX (a=Alpha, X=Numeric) "^[a-z][a-z][a-z][0-9]" or something like that. It all happened inside the C code, so I plead ignorance of the details. The new NIC IDs no longer fitted the regex, and it broke Hobbit. (Yes, it was called Hobbit back then) Henrik was pretty quick off the mark though, and sorted me out with a patch within a day or three. (I am guessing he wasn't so busy back then) It is possible that you have encountered something similar. Henrik? Could it be? I would go to your sysadmin guys and get them to stop playing silly-buggers with the NIC naming conventions. If they refuse to be reasonable, you might have to petition Henrik for a fix. I still owe Henrik a beer for that T2000 fix. :-) Regards Vernon On 13 July 2011 10:36, Sam L <user-4449a49ea16f@xymon.invalid> wrote:Hey, I was just wondering if anyone had any ideas about this? Thanks! From: user-4449a49ea16f@xymon.invalid To: xymon at xymon.com Subject: Network Traffic Graph - Fedora 15 Date: Sat, 2 Jul 2011 14:39:34 -0400 I've been running xymon 4.3.3 on Fedora 14 for a month or two without any issues. I recently upgraded to Fedora 15 and now my "Network Traffic" graph in trends is no longer working. They changed up something with network card naming in Fedora 15, and my NIC is no longer called eth0 (or eth<anything>). The interface is now called p33p1. Should xymon be able to figure that out on it's own or do I need to tell it to look for more than ethX? Thanks. s0a4m-- RHCE#805007969328369
list Colin Coe
See http://lists.xymon.com/pipermail/xymon/2011-April/031502.html which got zero responses. CC
▸
On Thu, Jul 14, 2011 at 1:35 AM, Sam L <user-4449a49ea16f@xymon.invalid> wrote:Also, if this changed in Fedora now, then it means it is probably coming for Red Hat Enterprise Linux soon. And I assume this issue would hit more people then. From: user-4449a49ea16f@xymon.invalid To: xymon at xymon.com Subject: RE: [Xymon] Network Traffic Graph - Fedora 15 Date: Wed, 13 Jul 2011 13:29:21 -0400 Yes, I am aware Fedora changed the naming convention. My question is: How can I get the xymon network traffic graph (in trends) to work again? The only network traffic graph I have still only has eth0 in it (from old data before the Fedora upgrade.) I could probably force the name back to eth0 in the OS, but that seems like a cheesy workaround, since this is how the naming is going to be going forward. How can I get xymon to become aware that my NIC is called p33p1? Thanks for any guidance.Date: Wed, 13 Jul 2011 20:19:11 +0800 Subject: Re: [Xymon] Network Traffic Graph - Fedora 15 From: user-5b250cd7a540@xymon.invalid To: user-b3f8dacb72c8@xymon.invalid CC: user-4449a49ea16f@xymon.invalid; xymon at xymon.com Vernon is correct. Fedora 15 moves away from eth[0-9], at least in some circumstances. See http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming CC On Wed, Jul 13, 2011 at 2:28 PM, Vernon Everett <user-b3f8dacb72c8@xymon.invalid> wrote:Hi Sam I recall about 7 years ago, give or take, when Sun released the new T2000 line of servers, NICs changed from being eri0, hme0, qfe1and similar to being e1000g0, e1000g1..... You could grab the old NICs by using a regex. They were all of the form aaaX (a=Alpha, X=Numeric) "^[a-z][a-z][a-z][0-9]" or something like that. It all happened inside the C code, so I plead ignorance of the details. The new NIC IDs no longer fitted the regex, and it broke Hobbit. (Yes, it was called Hobbit back then) Henrik was pretty quick off the mark though, and sorted me out with a patch within a day or three. (I am guessing he wasn't so busy back then) It is possible that you have encountered something similar. Henrik? Could it be? I would go to your sysadmin guys and get them to stop playing silly-buggers with the NIC naming conventions. If they refuse to be reasonable, you might have to petition Henrik for a fix. I still owe Henrik a beer for that T2000 fix. :-) Regards Vernon On 13 July 2011 10:36, Sam L <user-4449a49ea16f@xymon.invalid> wrote:Hey, I was just wondering if anyone had any ideas about this? Thanks! From: user-4449a49ea16f@xymon.invalid To: xymon at xymon.com Subject: Network Traffic Graph - Fedora 15 Date: Sat, 2 Jul 2011 14:39:34 -0400 I've been running xymon 4.3.3 on Fedora 14 for a month or two without any issues. I recently upgraded to Fedora 15 and now my "Network Traffic" graph in trends is no longer working. They changed up something with network card naming in Fedora 15, and my NIC is no longer called eth0 (or eth<anything>). The interface is now called p33p1. Should xymon be able to figure that out on it's own or do I need to tell it to look for more than ethX? Thanks. s0a4m-- RHCE#805007969328369
--
RHCE#805007969328369
list Epperson
Well, probably not "soon". RHEL lags Fedora by at least a couple of years, generally. F15 "broke" a lot of other things with the moves to systemctl, Gnome3, etc, btw. Also, btw, there's been a huge amount of controversy and bikeshedding over the pro/con of ethx names, which have been somewhat arbitrarily assigned for some time.
▸
On Wed, July 13, 2011 13:35, Sam L wrote:Also, if this changed in Fedora now, then it means it is probably coming for Red Hat Enterprise Linux soon. And I assume this issue would hit more people then. From: user-4449a49ea16f@xymon.invalid To: xymon at xymon.com Subject: RE: [Xymon] Network Traffic Graph - Fedora 15 Date: Wed, 13 Jul 2011 13:29:21 -0400 Yes, I am aware Fedora changed the naming convention. My question is: How can I get the xymon network traffic graph (in trends) to work again? The only network traffic graph I have still only has eth0 in it (from old data before the Fedora upgrade.) I could probably force the name back to eth0 in the OS, but that seems like a cheesy workaround, since this is how the naming is going to be going forward. How can I get xymon to become aware that my NIC is called p33p1? Thanks for any guidance.Date: Wed, 13 Jul 2011 20:19:11 +0800 Subject: Re: [Xymon] Network Traffic Graph - Fedora 15 From: user-5b250cd7a540@xymon.invalid To: user-b3f8dacb72c8@xymon.invalid CC: user-4449a49ea16f@xymon.invalid; xymon at xymon.com Vernon is correct. Fedora 15 moves away from eth[0-9], at least in some circumstances. See http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming CC
list Xymon User in Richmond
Well, probably not "soon". RHEL lags Fedora by at least a couple of years, generally. F15 "broke" a lot of other things with the moves to systemctl, Gnome3, etc, btw. Also, btw, there's been a huge amount of controversy and bikeshedding over the pro/con of ethx names, which have been somewhat arbitrarily assigned for some time. On Wed, July 13, 2011 13:35, Sam L wrote:
Also, if this changed in Fedora now, then it means it is probably coming for Red Hat Enterprise Linux soon. And I assume this issue would hit more people then. From: user-4449a49ea16f@xymon.invalid To: xymon at xymon.com Subject: RE: [Xymon] Network Traffic Graph - Fedora 15 Date: Wed, 13 Jul 2011 13:29:21 -0400 Yes, I am aware Fedora changed the naming convention. My question is:
How can I get the xymon network traffic graph (in trends) to work again? The only network traffic graph I have still only has eth0 in it (from old data before the Fedora upgrade.) I could probably force the name back to eth0 in the OS, but that seems like a cheesy workaround, since this is how the naming is going to be going forward. How can I get xymon to become aware that my NIC is called p33p1?
Thanks for any guidance.Date: Wed, 13 Jul 2011 20:19:11 +0800 Subject: Re: [Xymon] Network Traffic Graph - Fedora 15 From: user-5b250cd7a540@xymon.invalid To: user-b3f8dacb72c8@xymon.invalid CC: user-4449a49ea16f@xymon.invalid; xymon at xymon.com Vernon is correct. Fedora 15 moves away from eth[0-9], at least in some circumstances. See http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming CC
list Buchan Milne
▸
On Wednesday, 13 July 2011 04:36:36 Sam L wrote:
Hey, I was just wondering if anyone had any ideas about this? Thanks! From: user-4449a49ea16f@xymon.invalid To: xymon at xymon.com Subject: Network Traffic Graph - Fedora 15 Date: Sat, 2 Jul 2011 14:39:34 -0400 I've been running xymon 4.3.3 on Fedora 14 for a month or two without any issues. I recently upgraded to Fedora 15 and now my "Network Traffic" graph in trends is no longer working. They changed up something with network card naming in Fedora 15, and my NIC is no longer called eth0 (or eth<anything>). The interface is now called p33p1. Should xymon be able to figure that out on it's own or do I need to tell it to look for more than ethX? Thanks. s0a4m
Could you at least provide the *actual* output of 'ifconfig' ? If only the names have changed, then most likely you just need to adjust the regex on line 22 of xymond/rrd/do_ifstat.c, which is currently: "^([a-z]+[0123456789.:]+|lo)\\s" Maybe it should just be: "^([a-z0123456789.:]+)\\s" Regards, Buchan
list Sam L
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:26007 errors:0 dropped:0 overruns:0 frame:0 TX packets:26007 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:17070895 (16.2 MiB) TX bytes:17070895 (16.2 MiB) p33p1 Link encap:Ethernet HWaddr xx:xx:xx:xx:xx:xx inet addr:x.x.x.x Bcast:x.x.x.x Mask:255.255.255.0 inet6 addr: xxxx::xxx:xxxx:xxxx:xxxx/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:9206 errors:0 dropped:16 overruns:0 frame:0 TX packets:14358 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1641677 (1.5 MiB) TX bytes:9140070 (8.7 MiB) Interrupt:42 Base address:0x2000
▸
From: user-9b139aff4dec@xymon.invalid To: xymon at xymon.com Subject: Re: [Xymon] Network Traffic Graph - Fedora 15 Date: Thu, 14 Jul 2011 16:22:10 +0200 CC: user-4449a49ea16f@xymon.invalid On Wednesday, 13 July 2011 04:36:36 Sam L wrote:Hey, I was just wondering if anyone had any ideas about this?Thanks! From: user-4449a49ea16f@xymon.invalidTo: xymon at xymon.com Subject: Network Traffic Graph - Fedora 15 Date: Sat, 2 Jul 2011 14:39:34 -0400I've been running xymon 4.3.3 on Fedora 14 for a month or two without any issues. I recently upgraded to Fedora 15 and now my "Network Traffic" graph in trends is no longer working. They changed up something with network card naming in Fedora 15, and my NIC is no longer called eth0 (or eth<anything>). The interface is now called p33p1. Should xymon be able to figure that out on it's own or do I need to tell it to look for more than ethX?Thanks.s0a4mCould you at least provide the *actual* output of 'ifconfig' ? If only the names have changed, then most likely you just need to adjust the regex on line 22 of xymond/rrd/do_ifstat.c, which is currently: "^([a-z]+[0123456789.:]+|lo)\\s" Maybe it should just be: "^([a-z0123456789.:]+)\\s" Regards, Buchan