cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1997
Views
0
Helpful
5
Replies

getting %WAAS-CIFSAO-3-131207 messages

I am runng WAAS 4.1.5f

started geting %WAAS-CIFSAO-3-131207  Error replying to client 172.16.6.167. yesterday,( about 5000 messages per hour) seems to be only on this central site server

cleared by the "no accelerator cifs enable" command the re-enabling it a few minues later. then ran ok for rest of the day, this morning started getting the same messges again.

Where do I start looking to fix this problem?..could it be a Microsoft patch on the server?

5 Replies 5

Bhavin Yadav
Cisco Employee
Cisco Employee

Hello,

Can you place some more info from following files around the same timeframe?

1. latest cifsao_errorlog log file from \local1\errorlog folder?

2. from cifs_err.log file under \local1\errorlog\cifs folder?

The logs on this file may help further to determine the issue.

Thanks.

After speaking to the server guys, the errors stopped about 12:13

I am stillinterested in what caused the problem

type-tail cifsao-errorlog.current
03/22/2011 12:14:09.387(Local)(29502) ERRO (387458) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]
03/22/2011 12:14:09.393(Local)(29502) ERRO (393974) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]
03/22/2011 12:14:09.400(Local)(29502) ERRO (400059) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]
03/22/2011 12:14:09.406(Local)(29502) ERRO (406385) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]
03/22/2011 12:14:09.692(Local)(29507) ERRO (692044) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]
03/22/2011 12:14:09.907(Local)(29507) ERRO (907618) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]
03/22/2011 12:14:09.915(Local)(29502) ERRO (915804) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]
03/22/2011 12:14:09.922(Local)(29502) ERRO (922554) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]
03/22/2011 12:14:09.928(Local)(29502) ERRO (928991) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]
03/22/2011 12:14:09.937(Local)(29513) ERRO (937389) Error replying to client 172
.16.6.167. [AoShellLog.cpp:25]

I have included the cifs-error log file for the times around the errors above

was the file attached?

Hi,

Thanks for sharing the information.

To be frank, it is tough to narrow down and pin point the problem. The best way to nail down this problem would be to open a TAC case. I suspect few defects mentioned below but not sure if you are really hiting any one of this because we need supporting logs to confirm that.

1. http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?caller=pluginredirector&method=fetchBugDetails&bugId=CSCSz31354

2. http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?caller=pluginredirector&method=fetchBugDetails&bugId=CSCsz78754

Few options if you want to try that might help you.

Option 1: 4.1.5f is getting older now. You may want to upgrade to 4.3.1. The big reason behind upgrade suggestion is - there are lot of CIFS related fixes that have gone after 4.1.5f code.

Option 2: reload WAE. This might help temporarily but issue might come back anytime.

Option 3: Apply "disk delete-data-partitions" and "reload" on WAE from CLI. This will clear all the cache that is built up and may address the issue temporarilty but again, the issue migth come back anytime.

Hope this helps.

PS: Please mark this Answered, if this answers your question.

Upgrade wont help, we have hit same issue with version 4.4.3

It seems it is unknown bug. With low traffic loads everything is fine, but adding more traffic it becomes to be unpredictable. Anyway we have raised a TAC case.

Review Cisco Networking for a $25 gift card