Fibre Channel (SAN)

Reply
N/A
Posts: 1
Registered: ‎09-30-2008

Switch Panic

Currently having issues when applying zone changes running v5.3.0a when applying the changes the switches in the ibm blade centres panic with the following

2008/09/30-06:35:35, , 54071, FFDC, WARNING, brocade4Gb, kSWD: Detect

ed unexpected termination of: ''zoned:0'RfP=786,RgP=786,DfP=0,died=1,rt=17268

82524,dt=91662,to=50000,aJc=1726781024,aJp=1726747723,abiJc=2016559412,abiJp=201

6526112,aSeq=104082,kSeq=0,kJc=0,kJp=0,J=1

Does anyone have any ideas? From what ive read the firmware im running should not exibit this problem.

Thanks

External Moderator
Posts: 4,787
Registered: ‎02-23-2004

Re: Switch Panic

dinger71,

see the Message reference Guide for details.

KSWD-1003

Message <timestamp>, , <sequence-number>, FFDC, WARNING, <system-name>, kSWD:

<Warning message>.

Probable Cause Indicates a warning state within the system.

A critical application error was reported in the watchdog subsystem. Refer to the string at the end

of the error message for specific information. The switch will reboot (on single-CP switches) or

failover (on dual-CP switches).

The warning message will be any one of the following:

  • <Detected unexpected termination of: <daemon name>>

Probable Cause: One of the critical daemons ended unexpectedly.

  • <<daemon name> failed to refresh SWD*** Sending SIGABRT to pid <process id number>>

Probable Cause: One of the critical daemons is found to be nonresponsive; sending signal

abort.

Recommended

Action

SIGABRT is the signal thrown by the programs to abort the process. Run the supportSave command

to determine, if any core files were created. If a core file is found, run supportFtp to send all core

files to a secure server location.

Copy the warning message along with any core file information, and contact your switch service

provider.

Severity WARNING

TechHelp24

TechHelp24

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.