Fibre Channel (SAN)

Reply
Contributor
Posts: 44
Registered: ‎02-05-2013

Error from DCX San Director

Hi Folk's,

Please help me to understand the following error from DCX San Director.From errdump could see the following error.

2013/10/13-05:25:11, , 841, SLOT 5 | CHASSIS, WARNING, Brocade_DCX4S,  S3,P-1(0): Link Timeout on internal port  ftx=1645622944 tov=2000 (>1000) vc_no=26 crd(s)lost=3 complete_loss:1.


Regards

Seenivasan P

Valued Contributor
Posts: 761
Registered: ‎06-11-2010

Re: Error from DCX San Director

Hi,

Take a look at thread: http://community.brocade.com/message/22707

Cheers,

Felipon

Valued Contributor
Posts: 931
Registered: ‎12-30-2009

Re: Error from DCX San Director

Ha Felipon beat me to it

the c2-1012 is explained here http://www.brocade.com/downloads/documents/product_manuals/B_SAN/FOS_MessageRef_v710.pdf

Might come in handy to understand future messages.

C2-1012

Message

Message <timestamp>, , <sequence-number>,, WARNING, <system-name>, S<slot number>,P<port number>(<blade port number>): Link Timeout on internal port  ftx=<frame transmitted> tov=<real timeout value> (><expected timeout value>) vc_no=<vc number> crd(s)lost=<Credit(s) lost> complete_loss:<complete credit loss>.

Probable Cause

Indicates that one or more credits have been lost on a back-end port, and there is no traffic on that port for two seconds.

Recommended Action

Turn on the back-end credit recovery to reset the link and recover the lost credits. If credit recovery has already been turned on, the link will be reset to recover the credits and no action is required.

Severity

WARNING

So basically you lost 3 credits on a blade backend port 1 in slot 3 if I interpret it correctly

Contributor
Posts: 44
Registered: ‎02-05-2013

Re: Error from DCX San Director

Hi ,

Here is slot 3  core blade. This core blade used to configure only ICL. Here how P-1(0) come. P-1 (Port 1) ,0 is pointing as blade poty no?

If am wrong please correct me.

slotshow -m       :

Slot   Blade Type     ID    Model Name     Status

--------------------------------------------------

  1     SW BLADE     51     FC8-48         ENABLED

  2     SW BLADE     51     FC8-48         ENABLED

  3     CORE BLADE   46     CR4S-8         ENABLED

  4     CP BLADE     50     CP8            ENABLED

  5     CP BLADE     50     CP8            ENABLED

  6     CORE BLADE   46     CR4S-8         ENABLED

  7     SW BLADE     51     FC8-48         ENABLED

  8     UNKNOWN                            VACANT

Regards

Seenivasan P

Valued Contributor
Posts: 931
Registered: ‎12-30-2009

Re: Error from DCX San Director

The CR blade is responsible for inter blade connectivity and the ICL's (if any).

The port it is referring to is an internal backend portnumber, ate least that's how I understand it.

Here how P-1(0) come. P-1 (Port 1) ,0 is pointing as blade poty no?

Don't know what you mean with ^^

Contributor
Posts: 44
Registered: ‎02-05-2013

Re: Error from DCX San Director

S<slot number>,P<port number>(<blade port number>)-------->S3,P-1(0):

Here S3 is Slot 3

P-1 is Port number 1

(0) is Blade port number

As much i know that  in current configuration slot 3 as core blade. P-1(0).............Pointing to where and which blade and port

Valued Contributor
Posts: 761
Registered: ‎06-11-2010

Re: Error from DCX San Director

nope, there are some mistakes there:

The error is reported on Slo3 Back-end port 0 (S3,P-1(0))

CTL BPt  UPt  SPt  MPt  CPt  IFi  GPt  M#   C#   Sw#    G#   ChID    PBPt:ISL

=======================================================================

ENB 0    -1   -1   0    0    2    0    0    0    -1   265  CONDOR2 1/9:

That back-end port in CR in slot 3 is connected to Port blade 1 back-end port 9. (S1,P-1(9))

As per this info, ICLs have nothing to do with the error.

Now, I recommend you to:

- take a look at 's initial post with the recommented documentation.

- then take a look at the thread in my first post and see if you can make the error disappear.

If not, come back with the result and we'll try to give you a hand.

rgds

Valued Contributor
Posts: 931
Registered: ‎12-30-2009

Re: Error from DCX San Director

  >> The port it is referring to is an internal backend portnumber

Contributor
Posts: 44
Registered: ‎02-05-2013

Re: Error from DCX San Director

Thanks,

Also please help the following commands how help me for the current situation.

Note: if possible Please explain the each command or if any docs please share with me.

bottleneckmon --showcredittools

bottleneckmon --cfgcredittools -intport -recover onLrOnly

bottleneckmon –-howcredittools

Valued Contributor
Posts: 931
Registered: ‎12-30-2009

Re: Error from DCX San Director

Felipon's link to another thread gave a hint already > the FOS command reference guide

But you could try help bottleneckmon as well

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