Sponsored Content
Operating Systems Solaris PLOGI failed state=Packet Transport error Post 302143689 by o_m_g on Friday 2nd of November 2007 03:24:38 PM
Old 11-02-2007
PLOGI failed state=Packet Transport error

Someone who can help me. the following error occur, what does it mean, and any possible solution you can give.thanks

syslog: fp: [ID 517869 kern.info] NOTICE: fp(2): PLOGI to d5900 failed state=Packet Transport error , reason=No Connection (Database)


$cat /var/adm/messages
Nov 3 05:16:21 vfaus279 fp: [ID 517869 kern.info] NOTICE: fp(2): PLOGI to d5900 failed state=Packet Transport error, reason=No Connection
Nov 3 05:16:21 vfaus279 fctl: [ID 517869 kern.warning] WARNING: 94227=>fp(2)::PLOGI to d5900 failed. state=e reason=5.
Nov 3 05:16:21 vfaus279 fp: [ID 517869 kern.info] NOTICE: fp(2): PLOGI to d6400 failed state=Packet Transport error, reason=No Connection
Nov 3 05:16:21 vfaus279 fctl: [ID 517869 kern.warning] WARNING: 94240=>fp(2)::PLOGI to d6400 failed. state=e reason=5.
 

10 More Discussions You Might Find Interesting

1. HP-UX

Error: XDMCP timed out. State=4 (CollectBroadcastQuery)

Hello, I am a new member of this forum. I am trying to solve a following problem with CDE in HPUX 11. The error is Error: XDMCP timed out. State=4 (CollectBroadcastQuery). I have uncommented the following lines from the Xaccess file - * grant service to all remote displays * ... (0 Replies)
Discussion started by: shad
0 Replies

2. Solaris

Unable to bring a disk from error to online state.

Hello experts. I am using Solaris 10(2005) on intel machine. I have installed Veritas Volume manager 5.0. I am unable to bring a disk error to online state. I would like to bring that disk to CDS format. Commands i used and output are.... #vxdisk list DEVICE TYPE ... (11 Replies)
Discussion started by: younus_syed
11 Replies

3. UNIX for Advanced & Expert Users

Transport Error

Dear Friends, I am using Solaris 10 on Sun Sparc T5120 with 4 HDD(Raid).I am getting transport error in one of my mirrored HDD c1t2d0. Below is a screen shot. I have replaced the HDD with new one but still the same. Any one can help???? c1t2d0 Soft Errors: 0 Hard Errors: 0... (1 Reply)
Discussion started by: solaris5.10
1 Replies

4. Solaris

Cygwin X Server error: xdmcp fatal error session failed session 23 failed for display

Hi, i got the following error when i tried to access the cygwin x server from a windows XP PC. "xdmcp fatal error session failed session 23 failed for display" Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Discussion started by: HarishKumarM
3 Replies

5. UNIX for Advanced & Expert Users

sftp error:- Couldn't send packet: Broken pipe

Hi, I am trying to sftp a large file(appx. 2 GB size) from solaris 10 to a Linux server. While sftping(with no options), connection is terminated after some time with broken pipe error. sftp with option -R1 or -B1500 is successful. Linux server ssh Version: OpenSSH_3.9p1, OpenSSL 0.9.7a... (3 Replies)
Discussion started by: brij123
3 Replies

6. Solaris

RED State Exception error in V250

hi all i am getting following error while starting V250 server on console we are not able to go to OBP also. RED State Exception Error enable reg: 0000.0000.0000.0000 CPU 0000.0000.0000.0001 AFSR 0030.02ae.18c0.00b7 Multiple PRIV UCU CPU WDU EDU U E CE FRC FRU (2 Replies)
Discussion started by: nikhil kasar
2 Replies

7. AIX

Open firmware state to running state

Hi Admins, I am having a whole system lpar in open firmware state on HMC. How can I bring it to running state ? Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies

8. AIX

Packet loss coming with big packet size ping

(5 Replies)
Discussion started by: Vishal_dba
5 Replies

9. Shell Programming and Scripting

Solaris ping report failed packet script

Hello, on Solaris ping command does not report failed packet as in i.e. Windows (Connection timeout) Instead it reports the sequence of the sent packet: 64 bytes from 10.80.4.120: icmp_seq=11. time=36.0 ms 64 bytes from 10.80.4.120: icmp_seq=12. time=35.9 ms 64 bytes from 10.80.4.120:... (6 Replies)
Discussion started by: drbiloukos
6 Replies

10. AIX

Error received when I was trying to check state of boot record

Hello, This is a test/lab LPAR. Recently installed and updated the SP/TL. everything seems to be working fine. (ran all post install checks) I checked the state of boot record, received the following error/failed message. Can you please explain what does this mean ? />ipl_varyon -i ... (1 Reply)
Discussion started by: dio34
1 Replies
CORE(5) 						      BSD File Formats Manual							   CORE(5)

NAME
core -- memory image file format SYNOPSIS
#include <sys/param.h> DESCRIPTION
A small number of signals which cause abnormal termination of a process also cause a record of the process's in-core state to be written to disk for later examination by one of the available debuggers. (See sigaction(2).) This memory image is written to a file named by default programname.core in the working directory; provided the terminated process had write permission in the directory, and provided the abnormal- ity did not cause a system crash. (In this event, the decision to save the core file is arbitrary, see savecore(8).) The maximum size of a core file is limited by setrlimit(2). Files which would be larger than the limit are not created. The name of the file is controlled via the sysctl(8) variable kern.corefile. The contents of this variable describes a filename to store the core image to. This filename can be absolute, or relative (which will resolve to the current working directory of the program generating it). The following format specifiers may be used in the kern.corefile sysctl to insert additional information into the resulting core file name: %H Machine hostname. %I An index starting at zero until the sysctl debug.ncores is reached. This can be useful for limiting the number of corefiles generated by a particular process. %N process name. %P processes PID. %U process UID. The name defaults to %N.core, yielding the traditional FreeBSD behaviour. By default, a process that changes user or group credentials whether real or effective will not create a corefile. This behaviour can be changed to generate a core dump by setting the sysctl(8) variable kern.sugid_coredump to 1. Corefiles can be compressed by the kernel if the following items are included in the kernel configuration file: options COMPRESS_USER_CORES devices gzio When COMPRESS_USER_CORES is included the following sysctls can control if core files will be compressed: kern.compress_user_cores_gzlevel Gzip compression level. Defaults to -1. kern.compress_user_cores Actually compress user cores. Core files will have the suffix .gz appended to them. EXAMPLES
In order to store all core images in per-user private areas under /var/coredumps, the following sysctl(8) command can be used: sysctl kern.corefile=/var/coredumps/%U/%N.core SEE ALSO
gdb(1), kgdb(1), setrlimit(2), sigaction(2), sysctl(8) HISTORY
A core file format appeared in Version 6 AT&T UNIX. BSD
November 22, 2012 BSD
All times are GMT -4. The time now is 01:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy