topic Re: Fibre channel problems in ProLiant Servers (ML,DL,SL)

Fibre channel problems

Ayman Altounji — Wed, 20 Dec 2000 00:00:00 GMT

On boot up the event log contains the following messages.

cpqfcalm
Event ID 11
The driver detected a controller error on \Device\Scsi\cpqfcalm1.

cpqfcalm
Event ID 9
The device, \Device\Scsi\cpqfcalm1, did not respond within the timeout period.

cpqasm
Event ID 4188
The Compaq System Management Driver has detected that the system
encountered an NT bugcheck prior to this boot. The bugcheck data was:
STOP: 0x000000D1 (0x00000004, 0x00000008, 0x00000000, 0xBFF69101).

Before crashing we were getting the messaes below.
An error was detected on device \Device\Harddisk1\DR1 during a paging
operation.

The last message was.
The device, \Device\Scsi\cpqarry21, is not ready for access yet.

Any assistance appreciated.

Regards,
Derek

Re: Fibre channel problems

Ayman Altounji — Wed, 27 Dec 2000 00:00:00 GMT

First off, what other hardware is installed on this system (other than the DL360 itself, what else is there)?

Re: Fibre channel problems

Ayman Altounji — Thu, 28 Dec 2000 00:00:00 GMT

Event ID 11 [ CPQFCALM ]
- The driver detected a controller error on \Device\ScsiPort6
Event ID 15
- Device not ready for access

TROUBLE SHOOTING:
= The Windows NT miniport driver for the Compaq Fibre Channel Host Controller Arbitrated loop is [CPQFCALM.SYS]. It is capable of generating entries to the Windows NT system event log.

All event log entries that CPQFCALM generates that relate to Fibre Channel events WILL HAVE and event ID of 11. Although the system event log may contain other event IDs (such as 9 or 15), and list [CPQFCALM] as the source, the driver does not generate these. The Windows NT SCSIPORT driver, on behalf of the [ CPQFCALM ] driver, generates them when command timeouts occur.
DECODING WINDOWS NT EVENT LOG ENTRIES:

The key value is the first 32-bit value on the row labeled 0010 (This is located under the EVENT DETAIL under the DATA box). This value is the data that needs decoding to determine the actual event that occurred.
Other important values are the third and fourth values on row 0020 and 0030. Note: If the event is associated with a particular device on the Fiber Channel Loop, theses values will contain the Windows NT SCSI address (Bus number, Target ID, and logical Unit number) of that device. If these values each contain 000000ff, the event is not associated with a particular device.

Value: (Information contained in the DATA box)

00000001 An unknown status value was received
00000004 An unexpected SCSI frame was received
00000006* A fatal error was detected (Request for memory failed)
00000007* A fatal hardware error occurred
0000000B An unknown single-frame sequence was received
0000000E An unknown multiple-frame sequence was received
00000025 A recoverable PCI bus error occurred
00000026* An unrecoverable PCI bus error occurred
00000309 Port lost synchronization with incoming data or the port is not receiving a signal from a remote node.
00000409 A laser fault was detected
00000509 A loop timeout occurred because the loop was in a particular state for too long.
00000609 A laser fault, loss of synchronization, loss of signal, or an elastic store error occurred.
00000709 Tachyon is in an offline state
00004000 the link went down during the transmission of a frame.

Re: Fibre channel problems

Ayman Altounji — Wed, 17 Jan 2001 00:00:00 GMT

Hi,

The current setup is as follows :-

DL360 with Fibre Channel 64 bit 66mhz card which connects to a SAN 16 Fibre switch, which is then connected into a dual redundant HSG80.

The main problem seems to be a time out issue.
The error below re-occurs frequently.

DISK
An error was detected on device \Device\Harddisk2\DR2 during a paging
operation.

0000: 00220004 00720001 00000000 80040033
0010: 0000012d 00000000 00000000 00000000
0020: 81935000 00000003 00000000 00000006
0030: 00000002 0000002a 00009202 00062a01
0040: c001402a 0000a8c9 0008

The two errors below, occur on startup.

CPQFCALM
The device, \Device\Scsi\cpqfcalm1, did not respond within the timeout
period.

0000: 0010000f 006a0001 00000000 c0040009
0010: 00000100 00000000 00000000 00000000
0020: 00000000 00000000 00000000 00000000
0030: 00000000 00000007

CPQARRY
The device, \Device\Scsi\cpqarry21, is not ready for access yet.

0000: 0018150f 00720001 00000000 c004000f
0010: 00000103 c00000a3 00000001 00000000
0020: 00000000 00000000 00000000 00000000
0030: 00000000 00000000 00000007 00000045

Regards,
Derek

Re: Fibre channel problems

Ayman Altounji — Tue, 06 Feb 2001 00:00:00 GMT

This issue has been resolved, the wrong card was supplied. You can't use a 64 bit card with win 2000/NT you must use the 32 bit card.

D :)

Re: Fibre channel problems

Ayman Altounji — Mon, 19 Mar 2001 00:00:00 GMT

please sendme information for this issue.
thank you very much.
dsorokins@urudata.com

Re: Fibre channel problems

Ayman Altounji — Mon, 19 Mar 2001 00:00:01 GMT

I'm also getting these same messages, could you please send me any information on not being able to use the 64bit cards and/or anything you might have on this thanks!! ms953a@sbc.com

Re: Fibre channel problems

Ayman Altounji — Tue, 24 Apr 2001 23:00:00 GMT

I also would like any future info regarding the use of 64 bit cards with 2000 / NT. -George Sweeney

Re: Fibre channel problems

Ayman Altounji — Wed, 25 Apr 2001 23:00:00 GMT

this adapters working ok with server w2000 ,nt4 ,with driver version A7
and the last firmware available in the compaq web ( in the customer alert page).
my last problem in january 2001 is not this adapters , my problem is using scsi id 4 and 5 in the disk storages 4214 connected at hsg80 controller.
This configuration is not soported and i have disconnection problems with this conf.
I not using position 4 and 5 for disk drives.

Re: Fibre channel problems

Ayman Altounji — Sun, 26 Aug 2001 23:00:00 GMT

Please send me info on 32bit card versus 64bit card if it still apply. Thanks. jonabishop@hotmail.com

Re: Fibre channel problems

Dnack — Sun, 10 Nov 2002 19:12:30 GMT

Hi, i am using Proliant ML530, hp StorageWorks Fibre Channel Support for Windows 2000 and exact the same problem happen.

cpqfcalm
Event ID 9
The device, \Device\Scsi\cpqfcalm1, did not respond within the timeout period.

someone said using the driver version A7 can resolve the problem? Well i got the lastest version of driver Version 5.14.4.69 D (15 Oct 02) and the probelm still exists. Please help.
i found that this problem was posted here since Dec 2000. Compaq could have solve the problem on its newer driver.

Re: Fibre channel problems

Mark Blindman — Thu, 02 Jan 2003 20:15:18 GMT

We have encountered the CPQFCALM error 15 The device, \Device\Scsi\cpqfcalm1, is not ready for access yet.

The data in row 10 is:
0010: 03 01 00 00 a3 00 00 c0 ....??..??

rows 20 & 30 are all zeros.

Can anyone interpret the data from row 10?

Thanks,
Mark

Re: Fibre channel problems

Steve Robbins — Mon, 29 Sep 2003 13:28:14 GMT

Here is a link to Compaq/HP fix for teh issue.
http://www29.compaq.com/falco/detail.asp?FAQnum=FAQ3823

In short, Windows thinks there is a problem when there isn't. Ignore the message.

Re: Fibre channel problems

Leo O'Shaughnessy — Thu, 13 Nov 2003 10:13:29 GMT

Since rebooting the server for an unrelated change last night we are getting a CPQCALM Error 15: The device, \Device\Scsi\cpqfcalm2, is not ready for access yet.
Teh value shows that this is
0010 0309 which indicates a laser error. According to the online KB this is an error to be ignored, however we are getting one of these errors every 2 minutes and it if filling up the Event Log. The system is a DL380G3 configured in a cluster with a external RA4100 Raid array connected throught the 64bit Storage works HBA. We are running Windows 2000. Can you confirm there is an issue running this card under Win2k, or any other fixes you may be aweare of...

Re: Fibre channel problems

N_16 — Wed, 10 Nov 2004 14:07:06 GMT

Hi I am getting the similar error messages
in system event log

eventID=15

"The device, \Device\Scsi\cpqfcalm1, did not respond within the timeout period"
on following dates

Nov 9 2004
0000: 0018150f 00720001 00000000 c004000f
0010: 00000103 c00000a3 000e29fb 00000000
0020: 00000000 00000000 00000001 00000000
0030: 00000000 00000000 00000007 00000005

Oct 29 2004
0000: 0018150f 00720001 00000000 c004000f
0010: 00000103 c00000a3 00041d83 00000000
0020: 00000000 00000000 00000001 00000000
0030: 00000000 00000000 00000007 00000005

June 11 2004
0000: 0018150f 00720001 00000000 c004000f
0010: 00000103 c00000a3 00592995 00000000
0020: 00000000 00000000 00000001 00000000
0030: 00000000 00000000 00000007 00000005

Apr 7 2004
0000: 0018150f 00720001 00000000 c004000f
0010: 00000103 c00000a3 000019b1 00000000
0020: 00000000 00000000 00000001 00000000
0030: 00000000 00000000 00000007 00000005

Dec 11 2003
0000: 0018150f 00720001 00000000 c004000f
0010: 00000103 c00000a3 00006f40 00000000
0020: 00000000 00000000 00000001 00000000
0030: 00000000 00000000 00000007 00000005

Mar 13 2003
0000: 00100000 006a0001 00000000 c0040009
0010: 50000101 00000000 00000000 00000000
0020: 00000000 00000000 00000000 00000000
0030: 00000000 00000007

After this error I had to reboot the server because the server became unresponsive.

The only error in event log is this.
What would you suggest?
thank you

Re: Fibre channel problems

Steve Robbins_1 — Thu, 29 Dec 2005 09:30:17 GMT

This has been a known problem with the interaction of Windows 2000 SCSIminiport and Compaq Drivers for over 5 years, it's absolutely sad that they haven't had a fix and that the "solution" is to disregard the notice. That's fine and dandy unless you work for an IT department that requires you to have the log not set to auto-overwrite as needed and save the log for 7 days but it's not allowed to grow over a certain length and you receive one of these messages every 45 seconds, and that's not after a reboot, that's a constant thing on my servers.
would it be so difficult to path this?

Re: Fibre channel problems

Tim Yarber — Thu, 26 Oct 2006 13:16:42 GMT

I have been trying to initialize some FC Hard Disk that we got for a JBOD backup solution. The initialization fails and this event log is the only clue I have as to why it is failing. I was hoping there would be some further solution to this than just disregarding the event log. I am on a server 2003 O/S, HP Proliant ML370 with a compaq 66/64bit FC PCI contoller. When I try to inilialize the disk, it always fails.

any help is greatly appreciated please !!

Re: Fibre channel problems

sunil saxena — Mon, 14 Jan 2008 15:45:12 GMT

I am having the same problem on my servers. I have a dual node cluster using DL8500 units connected to the 4100 storage units.