Contents

EPM Accelerator Troubleshooting

The End Point Mapper (EPM) accelerator optimizes MS-RPC protocols that do not use predefined TCP ports. Clients contact the EPM service on the server (TCP port 135) to negotiate a dynamic port that is based on the application UUID. The EPM AO listens to the client communication and creates a dynamic policy entry to match the negotiated port. EPM is required to apply MAPI specific optimizations or to provide accounting on any MS-RPC protocol.

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 EPM accelerator operation.

Next, verify the status that is specific to the EPM AO by using the show accelerator epm command, as shown in Figure 1. You want to see that the EPM 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 EPM Accelerator Status

Use the show running-config command to verify that the EPM traffic policy is properly configured. You want to see adaptor EPM for the applications or UUIDs that are configured to use the EPM AO, as follows:

Use the show statistics connection optimized epm command to check that the WAAS device is establishing optimized EPM connections. Verify that "TE" or "TDLE" appears in the Accel column for EPM connections, which indicates that the EPM AO was used, as follows: