Bug 799606 - linux can not detect the eth2 failure
linux can not detect the eth2 failure
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: iprutils (Show other bugs)
4.1
x86_64 Linux
unspecified Severity high
: rc
: ---
Assigned To: Lukáš Nykrýn
Release Test Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-03-03 08:46 EST by yijunzhu
Modified: 2012-06-20 12:03 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-20 12:03:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description yijunzhu 2012-03-03 08:46:36 EST
Description of problem:

When one network port eth2's cable is plug-out, the linux can not detect the port state change, it continue think the port is ok, then wanna send the data from the port eth2 plugout!! even other port is ok, linux will not choose other port as the ping package source port!!
(Assume:all the ports are from same network division/segment)

i can use "Ping -I eth3 gateway" ... but that is another case/senario

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

gcc version 4.1.2 20080704 (Red Hat 4.1.2-44)

How reproducible:
everytime you try

Steps to Reproduce:
1.plugout eth2
2.ping gateway address

  
Actual results:
"ping gateway" failed for the reason that all the package is send out by eth2

Expected results:
"ping gateway" successfully for the reason that ping package is from other ports that linux detected except the failure port eth2

Additional info:
nough saying
Comment 1 yijunzhu 2012-03-03 19:09:58 EST
eth2 is the first port of certain network segment;
EG:
eth0 belong to net1
eth1 belong to net3
eth2,eth3.....eth20 are from the net3

hope the eth number is not the root cause, but the first port of certain network division maybe the the source of the issue!
Comment 2 Jiri Pallich 2012-06-20 12:03:07 EDT
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See https://access.redhat.com/support/policy/updates/errata/

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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