Hi all,
We have an IBM 7013-J40 that fails to boot. We attempted to bring up in normal mode one of the first messages we receive is " NO VALID FLASH FIRMWARE ! ". It attempts but fails to find a boot device and stops at
" system unable to IPL". In SERVICE mode pretty much the same sequence of events except it will only go to the NETWORK BOOT main menu. No service menus are offered. This menu has 4 selections.
1. Select boot device
2. Select languages
3. Send test transmission ( PING)
4. Exit
Selection 1 shows default boot devices however n boot devices are listed. Hence our problem. It will also not ping any known IPXs.
A little more background: Prior to the latest issues we were not able to boot however we were able to access the MAINTENANCE MENU. While in the MAINTENANCE MENU we were not able to show or select a boot device. Our thoughts at the time was that the Firmware was corrupted and that a battery disconnect would do the trick. As stated above this did not resolve our issue but most likely compounded the issue.
Our thoughts are that we need to redo the Firmware however we are unble to locate a copy. Can anyone help??
Any thoughts are welcomed...
Dietz
We have an IBM 7013-J40 that fails to boot. We attempted to bring up in normal mode one of the first messages we receive is " NO VALID FLASH FIRMWARE ! ". It attempts but fails to find a boot device and stops at
" system unable to IPL". In SERVICE mode pretty much the same sequence of events except it will only go to the NETWORK BOOT main menu. No service menus are offered. This menu has 4 selections.
1. Select boot device
2. Select languages
3. Send test transmission ( PING)
4. Exit
Selection 1 shows default boot devices however n boot devices are listed. Hence our problem. It will also not ping any known IPXs.
A little more background: Prior to the latest issues we were not able to boot however we were able to access the MAINTENANCE MENU. While in the MAINTENANCE MENU we were not able to show or select a boot device. Our thoughts at the time was that the Firmware was corrupted and that a battery disconnect would do the trick. As stated above this did not resolve our issue but most likely compounded the issue.
Our thoughts are that we need to redo the Firmware however we are unble to locate a copy. Can anyone help??
Any thoughts are welcomed...
Dietz