Contents

NFS Accelerator Troubleshooting

The NFS accelerator optimizes NFSv3 traffic. Other NFS versions are not optimized by the NFS AO.

You can verify the general AO configuration and status with the show accelerator and show license commands, as described in the Troubleshooting Application Acceleration article. The Enterprise license is required for NFS accelerator operation.

Next, verify the status specific to the NFS AO by using the show accelerator nfs command, as shown in Figure 1. You want to see that the NFS AO is Enabled, Running, and Registered, and that the connection limit is displayed. If the Config State is Enabled but the Operational State is Shutdown, it indicates a licensing problem.

Figure 1. Verifying the NFS Accelerator Status

Use the show running-config command to verify that the NFS traffic policy is properly configured. You want to see accelerate nfs for the File-System application classifier NFS action and you want to see appropriate match conditions listed for the NFS classifier, as follows:

Use the show statistics connection optimized nfs command to check that the WAAS device is establishing optimized NFS connections. Verify that "N" appears in the Accel column for NFS connections, which indicates that the NFS AO was used.

Use the show statistics accelerator nfs command to verify the following:

The NFS traffic is NFSv3. Look at the Total RPC Calls per NFS Version field. The output of that field is an array of 5 values, and you want to see mostly NFSv3 traffic, which is reported in the 4th counter. High numbers in other array positions signify other NFS versions.

NFS traffic is not encrypted. Look at the Total RPC Calls per Authentication Flavor field. The output of that field is an array of 4 values, and you want to see mostly unencrypted traffic, which corresponds to the first 3 counters. A high number in the last counter signifies encrypted NFS traffic. Also check the Total RPC Calls with Unknown Authentication Flavor field, where you want to see 0 or a small number because these connections are not optimized.

The NFS connection is asynchronous. Verify that the Percentage of Requests Served Locally field is nonzero.

WAE# sh statistics accelerator nfs
NFS:
Global Statistics
-----------------
Time Accelerator was started: Fri Oct 23
16:40:06 2009
Time Statistics were Last Reset/Cleared: Fri Oct 23
16:40:06 2009
Total Handled Connections: 170
Total Optimized Connections: 170
Total Connections Handed-off with Compression Policies Unchanged: 0
Total Dropped Connections: 0
Current Active Connections: 0
Current Pending Connections: 0
Maximum Active Connections: 13
Total RPC Calls per Authentication Flavor: 65
298544 0 0 <----Should see 0 or few in last field
Total RPC Calls with Unknown Authentication Flavor: 0 <----Should see 0 or few
Total RPC Calls per NFS Version: 0
0 0 298609 0 <----Should see 0 or few in first two and last fields
Total RPC Calls with Unknown NFS Version: 0 <----Should see 0 or few
Total Requests: 298609
Total Local Replies: 191713
Percentage of Requests Served Locally: 64 <----Should be nonzero
Percentage of Requests Served Remotely: 36
Average Time to Generate Local READ Reply (ms): 15
Average Time to Generate Local WRITE Reply (ms): 0
Average Time to Generate Local GETATTR Reply (ms): 0
Average Time to Generate Local Reply (ms): 0
Average Time to Receive Remote Reply (ms): 10
Meta-Data Cache Access Count: 206017
Meta-Data Cache Hit Count: 191673
Remaining Number Of Entries in Meta-Data Cache: 128926
Meta-Data Cache Hit Ratio: 93

You can view the NFS connection statistics by using the show statistics connection optimized nfs detail command as follows: