Bug 676301 - Host is losing Network connectivity once a large number of FCoE LUNS are configured and the host is then rebooted.
Summary: Host is losing Network connectivity once a large number of FCoE LUNS are co...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fcoe-utils
Version: 6.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Petr Šabata
QA Contact: Storage QE
URL:
Whiteboard:
Depends On: 695941 719584 719585
Blocks: 756082
TreeView+ depends on / blocked
 
Reported: 2011-02-09 12:09 UTC by Srinivas
Modified: 2011-12-23 18:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 10:02:49 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Srinivas 2011-02-09 12:09:40 UTC 
Description of problem:
Loss of network connectivity after configuring a large number of FCOE Luns and rebootin the host. The issue is not seen with Open-FCOE.

The issue was reproduced on the following setups

1)Dell Power Edge 2950 with ServerEngines Corp host with Emulex OneConnect 10Gb FCoE Initiator (rev 02).
2)Dell Power edge R805 with Emulex Corporation Zephyr-X: LightPulse FCoE Adapter (rev 02).
3)Dell Power edge R710 with QLogic Corp. ISP2432M-based 10GbE Converge Network Adapter (CNA) (rev 03).

Array Details :CX4-480 running with Flare30 (04.30.000.5.506).

How reproducible:

The issue is reproducible very consistently.

Steps to Reproduce:
)Host is running RHEL-6 GA with CNA with 20 Odd LUNS.
2)Add around 255 Clariion LUNS with the HOST.
3)Rescan for new LUNS. All newly added LUNS are showing correctly.
4)Reboot the host.
5)After reboot Host is accessible only via Console. Pinging to the host from other host is failing .All the old and new Luns are showing correctly.

Please let us know if you need any more information.
Comment 4 Eduard Benes 2011-05-30 12:35:55 UTC 
Hello Srinivas, unfortunately we don't have the HW required for proper verification of this bug available in house. Therefore I would like to ask for partner commitment to test the bug before accepting it for inclusion in upcoming release. Thanks!
Comment 5 Eduard Benes 2011-06-20 09:23:48 UTC 
Hello, any news on this front?
Comment 6 Srinivas 2011-06-24 16:49:47 UTC 
Sorry for the late reply. We will be ready to verify the fix. Please let us know if you need any more details.
Comment 8 Petr Šabata 2011-08-11 12:51:24 UTC 
Srinivas,

I'm not really sure what the problem could be.  Is the system installed on FCoE drives?

I understand the system is fully functional, all FCoE drives are visible and accessible but you just can't access the machine via its regular management interfaces.  Is that so?  Do they fail to initialize during boot?
Note You need to log in before you can comment on or make changes to this bug.