We recently upgraded the WAE code from 5.5.7 to 6.2.3c, and are seeing too many slow response reported specifically accessing a file server over the WAN.
Below are some logs from the smb-errorlog folder
08/31/2017 20:07:20.014smbao(21027 0.2) NTCE (14186) intercepted new flow 29879, source 172.25.151.38:53233(fd:46), destination 172.25.7.230:445(fd:47) @smb_new_con
n_handler [AoSmbFlow.cpp:616]
08/31/2017 20:07:20.015smbao(21027 0.2) NTCE (15003) Searching for key: 172.25.7.230, list size is 0 @KeyExists [LRUCache.h:96]
08/31/2017 20:07:20.015smbao(21027 0.2) NTCE (15014) no matching key @KeyExists [LRUCache.h:102]
08/31/2017 20:07:20.015smbao(21027 0.2) NTCE (15020) Searching for key: 172.25.7.230, list size is 0 @KeyExists [LRUCache.h:96]
08/31/2017 20:07:20.015smbao(21027 0.2) NTCE (15025) no matching key @KeyExists [LRUCache.h:102]
08/31/2017 20:07:20.027smbao(21027 0.2) NTCE (27273) NG:This Flow NOT applicable for sid mapping @smb2EnableSidMapping [CHNegotiate.cpp:1261]
08/31/2017 20:07:35.402smbao(21027 0.2) NTCE (402686) (fl=29879) f:AE2 FL:setting flow[0x7fbc27303f10] state to shutdown @start_flow_shutdown [AoSmbFlow.cpp:482]
If you look at the above logs, it shows a connection established between 172.25.151.38 and 172.25.7.230 (Actual affected server with which we have performance issues).
Then the next few logs shows a key missing and a shutdown state.
Does this mean anything?
I tried to open a TAC, but the response wasnt satisfactory, as they want me to disable SMB as a workaround.
Everything starts to work fine, when WCCP is disabled. No slowness, when the WAAS is by-passed. Not sure if this is due to the software version or the SMB that was enabled at the same time.
