Fibre Channel (SAN)

Reply
New Contributor
Posts: 2
Registered: ‎01-27-2011

SilkWorm48000 Server Daemon (NSD) crash, what could be the reason for the crash??

It could be the because of duplicate WWPN entires???

Thanks'

AKKI

External Moderator
Posts: 5,029
Registered: ‎02-23-2004

Re: SilkWorm48000 Server Daemon (NSD) crash, what could be the reason for the crash??

Accordly diverse Release Notes from diverse FOS release , several DEFECT was closed by Brocade about NSD Error.

some in FICON Env, som ein Interop-Mode and much more.

You Threads not report enough Information about they environments, FOS release,... is the Director in Native or IM ? is a Open or FICON environments ?

another Qeustion is, why you have duplicated WWPN ?

TechHelp24
New Contributor
Posts: 2
Registered: ‎01-27-2011

Re: SilkWorm48000 Server Daemon (NSD) crash, what could be the reason for the crash??

Hi

Thank you for your support and below are the error logs received from the switch

" 011/08/30-02:05:13:980431, , 38775/24824, SLOT 5 | FID 128, WARNING, XXXX48K01, Duplicated WWN was detected with PID 0x11b02 and  0x11b04., ns_db.c, line: 1113, comp:nsd, ltime:2011/08/30-02:05:13:980415 (Local Time = 06:50:13) "

The server connected is a IBM Bladecenter chassis's with Qlogic Intelligent Passthru Module and the ESX 4.1 U1 is running on the Blade serrver.

The Fabric OS:  v6.4.1

Hope this will give some insight about the issue.

External Moderator
Posts: 5,029
Registered: ‎02-23-2004

Re: SilkWorm48000 Server Daemon (NSD) crash, what could be the reason for the crash??

You have a Duplicated Device, but WWN and not WWPN

procede with this one first, and try to Identify this Double WWN and remove if necessary.

NS-1006

Message

<timestamp>, , <sequence-number>,, WARNING, <system-name>, Duplicated

WWN was detected with PID <existing device PID> and <new device PID>.

Probable Cause Indicates that an existing device has the same WWN as a new device that has come online.

Recommended

Action

The switch will process the new PID and leave the existing PID intact. Subsequent switch

operations will clean up the obsolete PID. However, administrators could check and remove devices

with a duplicated WWN.

TechHelp24
New Contributor
Posts: 2
Registered: ‎09-08-2011

Re: SilkWorm48000 Server Daemon (NSD) crash, what could be the reason for the crash??

Hi

Thank you again for the help, we will work on the recommendation and update you. 

New Contributor
Posts: 2
Registered: ‎09-08-2011

Re: SilkWorm48000 Server Daemon (NSD) crash, what could be the reason for the crash??

I have one Question

Due to Duplicate FCID issue the Server Daemon (NSD) will crash and what could be the other reasons for NSD crash.

This inputs will be really helpful for me in resolving the the issue.

thanks

AKKI

Join the Community

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

vADC is now Pulse Secure
Download FREE NVMe eBook