From: Tuan Ng (tng@ofir.dk)
Date: Tue Aug 03 2004 - 04:36:17 EDT
Hi,
I got three answers from Johan Brusche, Dr Thomas Blinn and Raul Sossa Sossa.
Many thanks to you.
After reading the answers, there are 4 things I want to investigate:
1) have a talk with the SAN-guy considering zoning (new zoning recently?)
2) reboot the server (just to be sure no transient electrical problem)
3) upgrade the emx driver (to be sure that it isn't the driver which gives
problem)
The newest driver is v.2.14
(http://h30097.www3.hp.com/unix/EarlyReleasePatch-download.html), but the
server needs the PK6 installed.
Or just a driver which > 2.02; I could not find any from HP site.
(NB: according to Dr Blinn, HP does not release
these independently for older patch levels that are no longer supported, so
you can't find it on their web site)
4) upgrade to PK6
Best regards,
Tuan
**************
Answer from Johan Brusche:
>You probably have "other" operating systems using the same SAN, and
>you have NOT used zoning on the switches to separate them.
>Johan.
**************
Answer fr Dr Thomas Blinn:
>Hi, Tuan.
>
>I passed your question along to our emx driver expert, and he
>had these comments:
>
>> Hi Tom,
>>
>> The emx driver issued a request to the Name Server to get all
>> the port IDs for a particular port type. The request was rejected with
>> a reason code of "Unable to perform request" and an explanation code
>> of "No port type". I'm not sure under what context this is occurring
>> given that the error has no useful information other than the error
>> message itself. This does not feel like a driver issue but rather
>> something going on with the fabric. Is anything going on with the
>> fabric that could cause the port IDs of that the type we might be
>> requesting to be cleared at the time? I don't know there's not
>> enough info to go on.
>>
>> The error log shows the rev of the driver to be 2.02 which is
>> very old. Are they really running with a driver that old? What does the
>> boot messages say for driver and firmware revisions?
>>
>>
>> --dennis
>
>So, the message is more informational than something that might be
>a problem in the "emx" driver itself, it's a result of the driver
>asking the "name server" in the fibrechannel fabric for information
>that would normally be returned.
>
>We suspect you have an old patch kit on that system, if you have any
>patches at all. The current patch kit for V5.1A is, I believe, PK6,
>and it's available from HP's support web site. You don't need a new
>or update license of any kind to apply the patch kit, and having the
>current versions of drivers and so forth may help. However, it does
>not sound like this particular error was a problem in the driver or
>host system software, but rather a transient condition in the fibre
>fabric.
>
>Hope this information helps..
>
>Tom
**************
Answer from Raul Sossa Sossa:
>you have an issue in the path components: fca integration to the switch.
**************
-----Original Message-----
From: tru64-unix-managers-owner@ornl.gov
[mailto:tru64-unix-managers-owner@ornl.gov] On Behalf Of Tuan Ng
Sent: donderdag 29 juli 2004 08:03
To: tru64-unix-managers@ornl.gov
Subject: Fibre Channel Event error: emx_sns_get_portlist_done: GID_PT
was rejected. Rsn = 9 Expl = a
Hi managers,
We have a ES40 running 5.1A/Firmware v6.3, KGPSA-CA with the firmware
XXX. Recently I got "mx_sns_get_portlist_done: GID_PT was rejected. Rsn = 9
Expl = a".
The messages arrives each 10s, writings/readings from the disks are OK.
But the "severity=high priority" from dia worry me, do you know how can I
solve it? Does HP have something like "a note with explanation/troubleshooting
for those kind of errors"?; "man emx" doesn't help much.
Many thanks on advance, I will resume.
Best regards,
Tuan
ps: I saw the same error in january, but the
error disappear(without doing anything) less
than 1 day after!
**
from messages:
Jul 27 14:01:24 cairo vmunix: EMX DRIVER ERR: emx1:
emx_sns_get_portlist_done
- emx_sns_get_portlist_done:
GID_PT was rejected. Rsn = 9 Expl = a
***
from dia V3.3 ********************* ENTRY 291
********************************
Logging OS 2. Digital UNIX
System Architecture 2. Alpha
Event sequence number 51820.
Timestamp of occurrence 19-JUL-2004 10:32:35
Host name cairo
System type register x00000022 Systype 34. (Regatta Family)
Number of CPUs (mpnum) x00000004
CPU logging event (mperr) x00000003
Event validity 1. O/S claims event is valid
Event severity 3. High Priority
Entry type 197. Fibre Channel Event
1. - (minor class)
------- Unit Info -------
Bus Number 1.
Unit Number x0001
------- Data -------
Class x0001 Adapter - KGPSA
Subsystem x0001 Adapter - KGPSA
-- PCI Event Frame --
Slot Number 4.
Vendor ID x10DF EMULEX Corporation.
Device ID xF800 Compaq KGPSA-CA = LP8000 -
168794-B21.
Command x0007 I/O Space Accesses Response:
Enabled
Memory Space Accesses Response:
Enabled
PCI Bus Master Capability:
Enabled
Monitor for Special Cycle Ops:
DISABLED
Generate Mem Wrt/Invalidate Cmds:
DISABLED
Parity Error Detection Response:
*IGNORE*
Wait Cycle Address/Data Stepping:
DISABLED
SERR# Sys Err Driver Capability:
DISABLED
Fast Back-to-Back to Many Target:
DISABLED
Status x0280 Device is 33 Mhz Capable.
No Support for User Defineable
Features.
Fast Back-to-Back to Different
Targets,
Is Supported in Target Device.
Device Select Timing: Medium.
Revision ID x02
Class Code x00040C
Cache Line Size x10
Latency Timer xF8
Header Type x00 Single Function Device.
BIST x00
Slim Base Addr Low x01321000
Slim Base Addr High x01321000
Ctrl Reg Memory Addr Low x01322100
Ctrl Reg Memory Addr High x01322100
Ctrl Reg IO Addr Low xFC011100
Subsystem Vendor ID x0000
Subsystem ID x0000
ROM Base Addr x00000000
Interrupt Line x24
Interrupt Pin x01
Min_Gnt xFF
Max_Lat x00
- Port Interface Data -
Host Attention Reg x00000000
BIU Host Status Reg x00000000
BIU2 Host Control Reg x00000000
Firefly Attention Reg x00000000 Mailbox Interrupt Active.
BUI2 Configuration Reg x00000000 Synchronizer Contain One Stage of
Registers.
Little Endian Mode.
No Access to the PCI Config Regs.
Allow Host Access to Slim and BUI
Regs.
DMA Arbitration Style: Rotating
Priority.
BIU2 Error Status Reg x00000000
BIU Chip Type x00000002 BUI2.
BIU Chip Rev x2002506D
Protocol Firmware Rev x07233891 If the value is less than
0x07112232 for
a
LP7000 a micro code upgrade is
available.
If the value is less than
0x07233091 for
a
LP8000 a micro code upgrade is
available.
Protocol POST Revision xFF202050
Endec+ Chip Revision x00000000
KGPSA State x00002510 FC Link is Up.
Link is Configured.
Public Loop or Fabric.
Probing Link.
KGPSA Topology x00000001 Fibre Channel point to point or
fabric
connection.
KGPSA ID On Loop x00011600
Current Mail Box Reg 0 x00000000
Current Mail Box Reg 1 x00000000
Current Mail Box Reg 2 x00000000
Current Mail Box Reg 3 x00000000
Current Mail Box Reg 4 x00000000
Current Mail Box Reg 5 x00000000
Current Mail Box Reg 6 x00000000
Current Mail Box Reg 7 x00000000
Current Mail Box Reg 8 x00000000
Current Mail Box Reg 9 x00000000
Current Mail Box Reg 10 x00000000
Current Mail Box Reg 11 x00000000
Current Mail Box Reg 12 x00000000
Current Mail Box Reg 13 x00000000
Current Mail Box Reg 14 x00000000
Current Mail Box Reg 15 x00000000
Current Mail Box Reg 16 x00000000
Current Mail Box Reg 17 x00000000
Current Mail Box Reg 18 x00000000
Current Mail Box Reg 19 x00000000
Current Mail Box Reg 20 x00000000
Current Mail Box Reg 21 x00000000
Current Mail Box Reg 22 x00000000
Current Mail Box Reg 23 x00000000
Current Mail Box Reg 24 x00000000
Current Mail Box Reg 25 x00000000
Current Mail Box Reg 26 x00000000
Current Mail Box Reg 27 x00000000
Current Mail Box Reg 28 x00000000
Current Mail Box Reg 29 x00000000
Current Mail Box Reg 30 x00000000
Current Mail Box Reg 31 x00000000
Link Status MBX Reg 0 x00000000 Command Number: x00000000
Success.
Link Status MBX Reg 1 x00000000
Link Status MBX Reg 2 x00000000 Link Failure Error Count.
Link Status MBX Reg 3 x00000000 Loss of Sync Error Count.
Link Status MBX Reg 4 x00000000 Loss of Signal Error Count.
Link Status MBX Reg 5 x00000000 Loss of Sequence Error Count.
Link Status MBX Reg 6 x00000000 Invalid Transmission Word Error
Count.
Link Status MBX Reg 7 x00000000 CRC Error Count.
Link Status MBX Reg 8 x00000000 Primitive Sequence Event Timeout
Count.
Link Status MBX Reg 9 x00000000 Elastic Buffer Overrun Error Count.
Link Status MBX Reg 10 x00000000 FCAL Arbitration Timeout Count.
Read Status MBX Reg 0 x00000000 Command Number: x00000000
Success.
Read Status MBX Reg 1 x00000000
Read Status MBX Reg 2 x00000000 Active Logged Ports: x00000000
Active Exchange Count: x00000000
Read Status MBX Reg 3 x00000000 Transmit Byte Count.
Read Status MBX Reg 4 x00000000 Receive Byte Count.
Read Status MBX Reg 5 x00000000 Transmit Frame Count.
Read Status MBX Reg 6 x00000000 Receive Frame Count.
Read Status MBX Reg 7 x00000000 Transmit Sequence Count.
Read Status MBX Reg 8 x00000000 Receive Sequence Count.
Read Status MBX Reg 9 x00000000 Total Exchanges by this Adapter.
Read Status MBX Reg 10 x00000000 Total Exchanges - Adapter is
Responder.
Read Status MBX Reg 11 x00000000 Number of P_busy Response Frames.
Read Status MBX Reg 12 x00000000 Number of F_busy Response Frames.
IOCB Word 0 x00000000
IOCB Word 1 x00000000
IOCB Word 2 x00000000
IOCB Word 3 x00000000
IOCB Word 4 x00000000
IOCB Word 5 x00000000
IOCB Word 6 x00000000
IOCB Word 7 x00000000 IOCB Command Status: x00000000
IOCB Command Type: x00000000
Driver Name KGPSA-CA
Driver Revision 2.02
Module Name emx_sns_get_portlist_done
Error Message emx_sns_get_portlist_done: GID_PT
was
rejected. Rsn = 9 Expl = a
Channel Address in Loop
15--<-12 11--<-08 07--<-04 03--<-00 :Byte Order
0000: 00000000 00000000 00000000 00000000 *................*
0010: 00000000 00000000 00000000 00000000 *................*
0020: 00000000 00000000 00000000 00000000 *................*
0030: 00000000 00000000 00000000 00000000 *................*
0040: 00000000 00000000 00000000 00000000 *................*
0050: 00000000 00000000 00000000 00000000 *................*
0060: 00000000 00000000 00000000 00000000 *................*
0070: 00000000 00000000 00000000 00000000 *................*
Fibre Channel Error Code x00000000
**** V3.3 ********************* ENTRY 292
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:05 EDT