There are several reasons that a MACH5 deployment may result in no ADN acceleration. Here are a few things to look for:
Is ADN enabled?
Check and make sure ADN is enabled.
Check the configured server subnets.
Verify that there are no incorrectly configured server subnets in the ADN routing section. Accidentally advertising a server subnet that is not actually "behind" the ProxySG will result in clients behind that ProxySG not being accelerated when requesting those resources. ProxySG nodes do not attempt to establish an ADN connection for content in server subnets that they are advertising (unless you have "prefer transparent connection over advertised routes" enabled).
The service is not being intercepted in proxy services.
Acceleration requires that one or more services be intercepted. Verify that the service in question is being intercepted.
Is there a problem with the node on the other side of the ADN tunnel?
Keep in mind that ADN acceleration requires two nodes. If you are confident that you have configured the branch node correctly but there is no acceleration, the node at the receiving end of the tunnel may be the problem.