%CLS-3-CLSFAIL and %CLS-3-BOGUSOP

[rparrat666]

Hi experts,

I’m receiving the errors:

%CLS-3-CLSFAIL: CLS: Assertion failed: file "../cls/cls_entitymanager.c", line
3446
this->fCepState == kCepStateConnectReqPending -Traceback= 0x60F6DA94 0x610A909C 0x60EACE4C 0x60E
A8390 0x60EAEB20 0x61E51184 0x61E50864 0x61E50E50 0x60EAC2F8 0x60EA76F0 0x60EAEA5C 0x610DEA48 0x
61101780 0x624DFC5C 0x6110257C 0x61101724

%CLS-3-BOGUSOP: Unknown CLS verb for STATION context, DlcOpcodeT=0015 -Tracebac
k= 0x60F6DA94 0x60EA82B0 0x60EAEB0C 0x61E51184 0x61E5231C 0x61E70214 0x601430A0 0x6014BCAC 0x600
A6FA8 0x600A734C

The other info I found about the %CLS-3-CLSFAIL is:

“This message does not affect functionality.

It indicates that a race condition has occurred between DLSw and the LLC2 layers when cleaning up an LLC2 session that timed-out during the XID exchange process.”

And no info for the CLS-3-BOGUSOP error (other than that I should be screaming to the tech support for help, that’s all the error decoder or the output interpreter shows about this messages).

So I have no idea about those errors, any help?

Thanks, and by the way, do anyone knows how to check tracebacks other than opening a TAC case?

The output interpreter always shows a time error (after putting the sh ver info).

Thanks.

[schinnap · Accepted solution]

You are hitting bug CSCdm84125.This is a cosmetic bug with CLS (Cisco Link Services). DLSw+ uses the services of CLS. The traceback does not affect operation. Since it is a cosmetic issue it was not fixed in 12.0, so in order to get rid of those messages I suggest you to consider the possibility of the upgrade to 12.1(20).

Please, before the upgrade check the minimum memory requirements

Thanks,

Suresh

[rparrat666]

bugId=CSCsw98838

We weill fix it with 12.4(25b), cause the new 15 needs more RAM and FLAS.

Thanks