This content has been marked as final. Show 5 replies
You don't appear to have a kernel issue.
It would seem to be a hardware issue with your storage kit.
... loose cable?
May 8 08:44:33 Port with D_ID=11400, PWWN=10000000c94b138c reappeared in fabric May 8 08:44:33 failed state=Packet Transport error, reason=No Connection May 8 08:42:38 Port with D_ID=11400, PWWN=10000000c94b138c disappeared from fabric May 8 08:36:22 Port with D_ID=11400, PWWN=10000000c94b138c reappeared in fabric May 8 08:36:22 failed state=Packet Transport error, reason=No Connection
It isn't only Solaris 10; I'm getting the same errors on 9 connected to a 6920:
Jul 3 16:47:49 ms2 fctl: [ID 517869 kern.warning] WARNING: 13704=>fp(0)::N_x Port with D_ID=620513, PWWN=293100015d033300 disappeared from fabric
Jul 3 16:47:53 ms2 fctl: [ID 517869 kern.warning] WARNING: 13737=>fp(0)::N_x Port with D_ID=620513, PWWN=293100015d033300 reappeared in fabric
Jul 3 16:47:54 ms2 fctl: [ID 517869 kern.warning] WARNING: 13752=>fp(0)::GPN_ID for D_ID=620513 failed
I've put in a ticket with Sun. We're running Sun Cluster 3.1; are you?
Emmalleres wrote:The suggested patch would be of value only if the system was installed with Solaris 10 Update 2 or older and had never been patched. Rev-17 of patch 119130 is/was from 2006, which can be seen by reading the README for it.
you need to download patch 119130-17 for Solaris 10(SPARC) or another patch for Solaris 9 and intel platform.
this will resovle the issue.
firstname.lastname@example.orgThis thread was originally posted more than two years ago. The O.P. has never returned to update the thread though they have been active in the forums since that time (click their username).
119130-19 was from May 2006
119130-16 was from Feb 2006
The only information was the excerpt provided in the initial post. It still appears to have been an issue with the storage peripheral.
The messages point to a SAN / Storage related issue. Do the switches or array report any issue?
It looks like you are using the Qlogic native cards so would need to contact your storage vendor who will be able to help narrow down the issue.
Edited by: .robv. on 06-Nov-2009 15:55