NetRAID 4M Netserver LC2000

[Kevin Perkins]

We have a netserver with novell 5.1 sp6 and the unit frequently displays that the NET4M-2.60-0 ID(0:05:0) receives an invalid comand operation code. also it displays the following error codes: 2685075456 requestors sequence number does not match. This issue causes the server to bog down and CPU utilization is at 100% for short periods of time. We updated the BIOS to 4.06.30 PV and Firmware for the Netraid to 4632 but no change in condition. Novell has no information on the error codes. Could the raid adapter be failing?? or is it something else? Could use some ideas on this

[Alicia White]

Well, I don't know Novell, but if I decipher that message correctly, "ID(0:05:0)," it means there is a issue on Channel 0, ID5, LUN 0. LUN0 isn't significant, but ID5 is.

On HP NetServers with drive cages (such as the LC2000 or the LH3), ID 5 is the SAF-TE processor for the drive cage. Most likely, the firmware on the drive cage needs to be updated.

You can go to the LC2000 download page to download the firmware update utility for the drive cage:

http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?pnameOID=19399&locale=en_US&taskId=135&prodSeriesId=50440&prodTypeId=15351&swEnvOID=54

In addition, I would make sure the drivers you are using are the latest for the NetRAID 4m. The tricky thing about the 4m is that the versions for the driver, firmware and utility must all be from the same build. You can download the latest versions here:

http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?pnameOID=62483&locale=en_US&taskId=135&prodSeriesId=51934&prodTypeId=329290&swEnvOID=1011

To confirm build versions, check the RELEASE NOTES for each download to make sure they all match. Mismatched firmware, driver & utility versions can cause some strange issues. So, it is possible that it might be part of the problem.

In Windows, it is best to upgrade the 4m in this order:

1. Uninstall the 4m utility
2. update the driver in the NOS
3. boot to Firmware update floppy
4. once firmware is updated, boot up to NOS & install compatible version of the 4M utility

Again, that is what is advised with Windows (NT in particular); I don't know if the same can be said for NW.

Good luck.

Alicia

[amhakassa]

Hi Kevin,

In addition to the excellent resolution recommendation by Alicia, I presumed u haven't cleared the CMOS after the BIOS update. So It will be a good start to clear the CMOS as follows

To clear the system configuration on the System Board:

1. Turn off power of the netServer, and unplug the power cord.
2. Remove the front bezel and left side cover (or top cover).
3. Move the configuration memory switch, switch 5 on the system board, to the "ON = Clear Config" position.
4. Plug in the power cord, and turn on power of the NetServer.

The following message will be displayed:
"Configuration has been cleared, set Clear Config switch to the OFF position before rebooting"

5. Turn off power of the NetServer, and unplug the power cord.
6. Return switch 5 on the system board to the OFF position.
7. Replace the left side cover (or top cover), and the front bezel, and plug in the power cord.
8. Turn on power to the HP NetServer and the following error message may be displayed.
"0012-34 : Incorrect System Configuration"
9. Press [F2] to run the Setup Utility when appears.
10. Make any configuration changes, if any, required, Press F10 to save and Exit.


If you read this article you will get more explanation on what the possible causes of the problem on the backplane

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=tis12720

To download the hot swap backplane PCA firmware update, here is the link which directly take u to the file you have to download

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?locale=en_US〈=English&pnameOID=19399&prodSeriesId=50440&prodTypeId=15351&basePartNum=ns1546&locBasepartNum=ns1546en&os=Cross+OS&tech=Firmware

I hope this will help
Good Luck
Amha Kassa

[kamal_9]

hi
Try using the updated driver .and you load the module conlog just by typing load conlog and enter .by this we can able to find out which module or which process is creating problem we can get the output in sys/etc/conloglog file go through this file for getting the full idea about the problem,
if problem is there pls forward the conlog.log to me