Hide Forgot
Error_screenshot Chassis Model: BX400S1 Firmware Version: 6.75 Switch type: PY CB Eth Switch/IBP 1Gb 36/8+2(Mode:Switch) Switch FW: 6.46 Blade Model: BX2580 M1 BIOS: V5.0.0.9 R1.26.00 for D3321-A1x iRMC: 8.08F Adapter(s): OCl14102-LOM Type: SKH - LOM Revision: Skyhawk Firmware: 11.1.1.3 Device driver: NA OCM: NA Personality: NIC-Only Multichannel (vNIC): NA Steps to reproduce: 1) Flash 11.1.1.3 firmware on Skyhawk 1G LOM. 2) Add iBFT iscsi configuration attempts for generating user configurable iqn address. 3) Make sure initiator iqn can be reachable to target. 4) Register initiator iqn in target and add a LUN to it. 5) Mount RHEL 7.1 GA'ed OS and boot to CD-ROM 6) During installation pass "ip=ibft" parameter under grub and continue installation. 7) After some time installation is booting to Dracut Emergency shell. Note: Installation of RHEL7.2 and SLES12 GMC3 OS is fine with "ip=ibft" kernel parameter passed during installation. EXPECTED RESULTS: Installation should proceed fine ACTUAL RESULTS: Installation is booting to Dracut emergency shell after passing ip=ibft parameter. Attaching screenshot. IP address of ibft0 ibft0 interface created has been assigned different IP address than what is in iBFT configuration. When ibft0 is assigned the IP address in configuration, 172.168.5.200, then initiator is able to login to the target and device appears. Bring up of ibft0 from the configuration is done by boot and installer script of RHEL7. Please raise a bz for this in RedHat bugzilla.
Created attachment 1130901 [details] console logs
Created attachment 1130902 [details] screen shot
Have you tried RHEL-7.2?
(In reply to Harald Hoyer from comment #4) > Have you tried RHEL-7.2? With RHEL7.2 it is working fine. We are able to boot to SAN OS (iBFT).
or do you expect a fix of the 7.1/7.0 installation media?
We see that this issue is closed for the Current Release when the issue is still persistent on RHEL 7.1. Can we know why was this issue was closed without proper resolution comments ?
(In reply to Ramkumar from comment #7) > We see that this issue is closed for the Current Release when the issue is > still persistent on RHEL 7.1. Can we know why was this issue was closed > without proper resolution comments ? Do you expect a z-stream fix for 7.1? 7.2 is not good enough?
A quick fix for 7.1 will work. Our Automation scripts are failing on 7.1 because of this issue. We are supporting 7.1 drivers for all our OEM's.