What's the difference between CIFs AO and WAFs-edge?

Answered Question
Sep 4th, 2008

(version 4.1.1) I can only active one or the other, and not both, on my edge NME-WAE-522-K9. Does enable WAFs-edge file services give CIF acceleration also?

MDF-3845-EdgeWAE#sh accelerator detail

Accelerator Licensed Config State Operational State

----------- -------- ------------ -----------------

cifs Yes Disabled Shutdown

epm Yes Enabled Running

http Yes Enabled Running

mapi Yes Enabled Running

nfs Yes Enabled Running

video No Enabled Shutdown

wafs-core Yes Disabled Shutdown

wafs-edge Yes Enabled Running

I have this problem too.
0 votes
Correct Answer by Zach Seils about 8 years 4 months ago

[Q] What would be the preferred method - the new CIFS AO?

[A] The CIFS AO is preferred for new deployments. Existing deployments using WAFS should migrate to the CIFS AO when ready.

[Q] Also, what are the 4.1.1 replacement commands for:

sh tfo connection summary

sh statistics dre connection active

sh statistics tfo saving

[A] All of the connection related statistics are now available using the 'sh stat conn ...' command. That covers the first two commands above. The third command is now 'sh stat app savings'.

[Q] When connected via the GUI to an edge device running edge-services, when looking at 'Cisco WAFS' monitoring - the Cache size entry. Is that only showing the Cache size when WAFS/CIFS is being used, or does it also show the DRE Cache?

[A] That's just showing statistics for the CIFS object cache. The global DRE cache statistics can be seen with the 'sh stat dre' CLI command. For per-connection DRE statistics, use 'sh stat conn ...'.

Zach

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Zach Seils Thu, 09/04/2008 - 10:44

Hi Jim,

The WAFS-* services are the CIFS acceleration services available in WAAS 4.0. In WAAS 4.1, we added a new (transparent) CIFS application optimizer called CIFS AO. The WAFS-* services are still there for backwards compatibility, and cannot be run at the same time as the CIFS AO. You only need one or the other.

Zach

jkeeffe Thu, 09/04/2008 - 11:42

What would be the preferred method - the new CIFS AO?

Also, what are the 4.1.1 replacement commands for:

sh tfo connection summary

sh statistics dre connection active

sh statistics tfo saving

And one other question if I may?

When connected via the GUI to an edge device running edge-services, when looking at 'Cisco WAFS' monitoring - the Cache size entry. Is that only showing the Cache size when WAFS/CIFS is being used, or does it also show the DRE Cache?

I'd like to watch somehow that DRE is working, specifically how much is being retrieved from cache during a particular file transfer for instance.

Thanks for your responses.

Correct Answer
Zach Seils Thu, 09/04/2008 - 21:51

[Q] What would be the preferred method - the new CIFS AO?

[A] The CIFS AO is preferred for new deployments. Existing deployments using WAFS should migrate to the CIFS AO when ready.

[Q] Also, what are the 4.1.1 replacement commands for:

sh tfo connection summary

sh statistics dre connection active

sh statistics tfo saving

[A] All of the connection related statistics are now available using the 'sh stat conn ...' command. That covers the first two commands above. The third command is now 'sh stat app savings'.

[Q] When connected via the GUI to an edge device running edge-services, when looking at 'Cisco WAFS' monitoring - the Cache size entry. Is that only showing the Cache size when WAFS/CIFS is being used, or does it also show the DRE Cache?

[A] That's just showing statistics for the CIFS object cache. The global DRE cache statistics can be seen with the 'sh stat dre' CLI command. For per-connection DRE statistics, use 'sh stat conn ...'.

Zach

Actions

This Discussion