Fibre Channel (SAN)

Reply
New Contributor
heiko.cordt
Posts: 3
Registered: ‎08-24-2011

Errors which are documented in FOS 7.x but not in FOS 6.4.x

Since we have upgraded from FOS 6.4.1b to 6.4.2a we receive errors which are related or documented in FOS 7 but not in FOS 6.4.x,  was wondering if someone knows if the Error is seen by somebodyin the errshow as follow:


2011/09/19-17:48:12, 5862, SLOT 7 | CHASSIS, WARNING, IBM_2499_384,  S11,P-1(3): Link Timeout on internal port  ftx=-125814141 tov=2000 (>1000) vc_no=3 crd(s)lost=3 complete_loss:1

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 above normal errors are observed in the hardware that may or may not impact the

data traffic.

Recommended

Action

Whenever this error is observed persistently, power cycle the faulted blade. If the problem persists,

replace the blade.

Severity WARNING

N/A
ZMan
Posts: 1
Registered: ‎06-03-2011

Re: Errors which are documented in FOS 7.x but not in FOS 6.4.x

Hi

We had the same error being displayed in one of our switches, after upgrade to 6.4.2a.

2011/10/11-18:45:25, , 1874, SLOT 6 | CHASSIS, WARNING, USPHXZDV11,  S2,P-1(42): Link Timeout on internal port  ftx=-1490127489 tov=2000 (>1000) vc_no=18 crd(s)lost=3 complete_loss:1

After opening a PMR to IBM, we received a reply to apply this command on the switch (even though we do not use bottleneck detection):

bottleneckmon --cfgcredittools -intport -recover onLrOnly

So far, seems to have worked, no more messages.

Z Man

New Contributor
unix.support1
Posts: 2
Registered: ‎01-31-2012

Re: Errors which are documented in FOS 7.x but not in FOS 6.4.x

I'm trying to shade more light on this issue.

Does anyone know what this actually real means? And why does the upgrading the Firmware causes this issue?

?

Why this command resolves the errors: bottleneckmon --cfgcredittools -intport -recover onLrOnly?

What are the implications of leaving the switches with this command on always?

Valued Contributor
felipon
Posts: 620
Registered: ‎06-11-2010

Re: Errors which are documented in FOS 7.x but not in FOS 6.4.x

Hi,

In response to your questions:

unix.support1 wrote:

I'm trying to shade more light on this issue.

Does anyone know what this actually real means? And why does the upgrading the Firmware causes this issue?

?

Why this command resolves the errors: bottleneckmon --cfgcredittools -intport -recover onLrOnly?

What are the implications of leaving the switches with this command on always?

These events mean that a frame has been discarded in the internal backend connections of the switch. If we take a look at the reported event:

2011/10/11-18:45:25, , 1874, SLOT 6 | CHASSIS, WARNING, USPHXZDV11,  S2,P-1(42): Link Timeout on internal port  ftx=-1490127489 tov=2000 (>1000) vc_no=18 crd(s)lost=3 complete_loss:1

This means that the backend port 42 in slot 2 has discarded a frame (A supportsave would be required in order to check which other backend port this one it's connected to).

Upgrading the FOS did not cause the issue; I bet that the issue was there before, but with 6.4.2a these events are now reported in errdump while before were reported in RASlog instead.

The mission of command bottleneckmon --cfgcredittools -intport -recover onLrOnly is to reset the backend ports that is reporting these events (a better description is available in Brocade documentation).

Leaving this command active is harmless, otherwise if there is a backend port stuck and discarding frames, could lead to a performance degradation. And to make these events disappear the port blade (or CP/CR) would have to be reset.


Rgds

New Contributor
unix.support1
Posts: 2
Registered: ‎01-31-2012

Re: Errors which are documented in FOS 7.x but not in FOS 6.4.x

So here is the message i'm getting:

2012/01/25-19:01:48, , 1644, SLOT 5 | CHASSIS, WARNING, SilkWorm48000,  S5,P-1(45): Link Timeout on internal port  ftx=-1424786428 tov=2000 (>1000) vc_no=14 crd(s)lost=5 complete_loss:1.

2012/01/25-19:01:48, , 1645, SLOT 5 | CHASSIS, WARNING, SilkWorm48000,  S6,P-1(49): Link Timeout on internal port  ftx=1462891676 tov=2000 (>1000) vc_no=10 crd(s)lost=5 complete_loss:1.

But the problem is that the SLOT 5 and Slot 6 is a CP. So how can port 45 or 49 on Slot 5 discarded a frame? The switch is connected to same type of switch on the other end. Both got there firmware upgrade at the same time and the errors are happning on both switches?

Thank you for your help!

Valued Contributor
felipon
Posts: 620
Registered: ‎06-11-2010

Re: Errors which are documented in FOS 7.x but not in FOS 6.4.x

unix.support1 wrote:

So here is the message i'm getting:

2012/01/25-19:01:48, , 1644, SLOT 5 | CHASSIS, WARNING, SilkWorm48000,  S5,P-1(45): Link Timeout on internal port  ftx=-1424786428 tov=2000 (>1000) vc_no=14 crd(s)lost=5 complete_loss:1.

2012/01/25-19:01:48, , 1645, SLOT 5 | CHASSIS, WARNING, SilkWorm48000,  S6,P-1(49): Link Timeout on internal port  ftx=1462891676 tov=2000 (>1000) vc_no=10 crd(s)lost=5 complete_loss:1.

But the problem is that the SLOT 5 and Slot 6 is a CP. So how can port 45 or 49 on Slot 5 discarded a frame? The switch is connected to same type of switch on the other end. Both got there firmware upgrade at the same time and the errors are happning on both switches?

Thank you for your help!

You're right that slots 5 and 6 are CPs, but you have to bear in mind that we're talking about backend ports, which are the connections between the CPs and the port blades.

In your case, this silkworm48000 has a stuck path between CP in slot 5 backend port 45 that connects to a backend port in one of the port blades.

The same happens with the other CP in slot 6. The procedure to get rid of this behavior is by physically resetting the affected CP (and if this doesn't work, then the affected port blade). That is why, bottleneckmon command is useful, because instead of resetting the whole blade, just resets the affected backend port.

Frequent Contributor
SKT
Posts: 90
Registered: ‎12-26-2010

Re: Errors which are documented in FOS 7.x but not in FOS 6.4.x

can you post `slotshow` ?

Occasional Contributor
sriram.iyer
Posts: 5
Registered: ‎10-30-2012

Re: Errors which are documented in FOS 7.x but not in FOS 6.4.x

Hi all

I also faced an issue where link timeout error was coming continuously in errdump.

the command bottleneckmon --cfgcredittools -intport -recover onLrOnly has solved my problem.

After enabling credit recovery, link timeout error occurred once and immediately bottleneckmon reset the link to internal port.

Post that i have not observed any error.

Contributor
sebastian.thaele
Posts: 62
Registered: ‎05-26-2009

Re: Errors which are documented in FOS 7.x but not in FOS 6.4.x

Many customer had these messages (and will have them when they update). So I wrote a blog article about that to explain what they mean: Stuck VCs or why my switch began to nag? (seb's sanblog)

In addition because I read you wonder why the errors are not documented in the v6.4 manuals: When these manuals were published the Stuck VC check was not in the code. It was introduced later (in the v6.4 code stream it came with v6.4.2 I think). I hope the blog helps to understand.

Occasional Contributor
felix.benadis
Posts: 13
Registered: ‎07-08-2011

Re: Errors which are documented in FOS 7.x but not in FOS 6.4.x

Hello ,

           Solution has been provided by Z Man .

Error message C2-1012 is documented in FOS v6.4.3 & v6.4.3b Release notes.

Join the Community

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