Bug 613086 - Use ip instead of ifconfig for IPoIB interfaces:
Summary: Use ip instead of ifconfig for IPoIB interfaces:
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rdma
Version: 6.0
Hardware: All
OS: Linux
Target Milestone: rc
: ---
Assignee: Doug Ledford
QA Contact: Gurhan Ozen
Depends On:
Blocks: 621266
TreeView+ depends on / blocked
Reported: 2010-07-09 16:34 UTC by Gurhan Ozen
Modified: 2013-11-04 02:00 UTC (History)
2 users (show)

Clone Of:
: 621266 (view as bug list)
Last Closed: 2010-11-10 21:28:24 UTC

Attachments (Terms of Use)

Description Gurhan Ozen 2010-07-09 16:34:56 UTC
Description of problem:
Rdma init script is utilizing ifconfig utility to control IPoIB interfaces which is producing lotsa of warning messages such as:

"Ifconfig uses the ioctl access method to get the full address information, which limits hardware addresses to 8 bytes.
Because Infiniband address has 20 bytes, only the first 8 bytes are displayed correctly.
Ifconfig is obsolete! For replacement check ip.

Probably ip should be used in favor of ifconfig. 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 2 Doug Ledford 2010-08-03 06:51:35 UTC
Changes made, will be tested tomorrow and checked in after successful tests.

Comment 3 Doug Ledford 2010-08-04 15:53:53 UTC
Note: I changed all usage of ifconfig to ip in the files owned by the rdma package.  However, ifup-aliases from initscripts still uses ifconfig and on IPoIB interfaces it is still noisy.  We would need to clone this bug against initscripts and get ifup-aliases modified in order to fully resolve the issue.

Comment 5 Gurhan Ozen 2010-08-12 18:17:12 UTC
Verifying this bug, but as comment #3 mentioned ifup- aliases still utilize ifconfig , so if someone's to do say, ifup ib0, s/he would still get the noise.

Comment 6 releng-rhel@redhat.com 2010-11-10 21:28:24 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.

Note You need to log in before you can comment on or make changes to this bug.