-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
targetmaker script doesn't support 10GE interfaces #20
Comments
From [email protected] on July 14, 2011 06:45:50 i'm having problems with ifspeed always being set to 0 in targets.cfg on centos 5.6 polling stuff that i can manually snmpwalk and see the speeds are corrent trying to sort things out i see i'm working with a different version of StandardIf.pl my srpm version has a patch that looks like it's doing something similar to the above rtg2-highspeed.patch.. but it's not the same and the SVN version (last revised in 2009) shows neither the above patch or the similar patch that i see in the srpm package StandardIf.pl what's the latest version I should be working from? |
From [email protected] on July 14, 2011 07:08:47 i should add... my "ifspeed alway equals 0" problem is verified to be caused by the "high speed fix" that is in the StandardIf.pl version that comes with the srpm... taking it out lets things work for my non-highspeed interfaces. so i guess the issue is, the srpm needs to be updated... or, the spec file put into svn so patches can be submitted for it to "rpmbuild -ta" in a tarball of svn trunk |
…eed if it exists (issue cedlecomte#20)" This reverts commit 653be7d.
Fix ifspeed detection using ifhighspeed when possible, issue #20
From [email protected] on April 18, 2011 19:14:55
Targetmaker only queries ifSpeed, which returns inaccurate values for 10GE interfaces (returning 2^32-1 instead of 10000000000.
ifHighSpeed returns the speed in megabits, which can be utilized to calculate the ifSpeed.
I altered StandardIf.pl to also query IF-MIB::ifHighSpeed on all hosts, and if a value is returned, to use that * 1000000 as the actual $ifspeed value.
Is there a better way to approach this? I'm concerned about backwards compatibility.
Attachment: rtg2-highspeed.patch
Original issue: http://code.google.com/p/rtg2/issues/detail?id=20
The text was updated successfully, but these errors were encountered: