Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

WAE and filer latency

Hello, I can see some logs into our WAE (WAE-612-K9) but I cannot find any useful information to fix it:

Host X.X.X.X:445 was not discovered, bypass period: 60 sec, number of events: 1, reason: high/unknown Core<=>Filer latency

I don't understand this filer latency... I suppose the connection is not optimized? Thanks all for your help

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: WAE and filer latency

Ping the server from the core WAE by name and Ip to ensure name resolution and connectivity.

By default, if an edge is under 5 ms or if a core WAE is over 25 ms from a file server, it will not use the CIFS AO. However, if the traffic is being intercepted, it should be using tfo, dre, and lz. This is by design as WAAS is engineered to have the cores sitting next to the file servers to eliminate the CIFS latency effects over a WAN link.

Dan

2 REPLIES
Cisco Employee

Re: WAE and filer latency

Ping the server from the core WAE by name and Ip to ensure name resolution and connectivity.

By default, if an edge is under 5 ms or if a core WAE is over 25 ms from a file server, it will not use the CIFS AO. However, if the traffic is being intercepted, it should be using tfo, dre, and lz. This is by design as WAAS is engineered to have the cores sitting next to the file servers to eliminate the CIFS latency effects over a WAN link.

Dan

Community Member

Re: WAE and filer latency

Thanks for your reply, and yes the average latency is over the 25ms so CIFS is not in use! Many thanks for your help

155
Views
5
Helpful
2
Replies
CreatePlease to create content