[Bug 755486] New: Netapp CQ# - 263659 - Bladecenter - SANboot from alternate controller fails on software initiated iSCSI using onboard 1GB NIC (BCM5708S & BCM5709S) - SLES 11.2
https://bugzilla.novell.com/show_bug.cgi?id=755486 https://bugzilla.novell.com/show_bug.cgi?id=755486#c0 Summary: Netapp CQ# - 263659 - Bladecenter - SANboot from alternate controller fails on software initiated iSCSI using onboard 1GB NIC (BCM5708S & BCM5709S) - SLES 11.2 Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jaci@netapp.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=484643) --> (http://bugzilla.novell.com/attachment.cgi?id=484643) Screenshot of issue User-Agent: Mozilla/5.0 (Windows NT 5.2; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Details of the problem: An 50 GB LUN is mapped as LUN 0 to one of the hosts in the configuration. The 1GB onboard Broadcomm NIC is configured to boot from the SANboot LUN using the IBM iSCSI Configuration Manager flash utility (2 attempts are configured using the IBM flash utility -- one for each port on the 1GB NIC). SuSE Linux Enterprise Server (SLES) 11.2 is installed and boots just fine from the preferred path, but when the preferred path is failed and the host is configured to boot from the alternate path, the boot will fail. It seems that the host can still see the SANboot LUN initially, however, the boot fails when the iSCSI session fails to log in during boot up (screenshot provided) Saw this on both HS22 and HS21 blades: HS21 - Broadcom NetXtreme II BCM5708S bnx2 - 2.1.11 bnx2i - 2.7.03 HS22 - Broadcom NetXtreme II BCM5709S bnx2 - 2.1.11 bnx2i - 2.7.03 Reproducible: Always Steps to Reproduce: 1. Create 50 GB LUN. 2. Map the LUN to host . 3. Configure IBM iSCSI configuration manager utility for 2 attempts, one from each port on the NIC 4. Host installs fine on preferred path 5. After install, failover on host is configured (both MPP and DMMP attempted), iSCSI session also created for alternate path 6. After failover is configured, host is shutdown. Preferred controller is failed and ownership of SANboot volume is changed to alternate controller. 7. Attempt to boot from alternate path. Actual Results: The host seems to see the boot LUN, but will not boot into OS after it fails to log into alternate path iSCSI session during boot up. The host logs into the controller twice which allows for the partial boot, however, will not login the last time in order to complete the boot (controller log while host boots up is included) Expected Results: The host boots from the alternate path and the SLES 11.2 install boots without issue Troubleshooting: -iSCSI boot firmware table (iBFT) is configured during install, but only allows for one host port to be configured. Looked for a way to configure both paths in the iBFT during install but failed to find this information -Noticed that the install path (configured in iBFT during install) was tied to root filesystem so attempted to do same with other path, still ran into same issue at boot -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com