Overview
You encounter an issue with your PeerApp cache out where it is a lot lower than expected. You have a significant increase in traffic yet the cache out is lower compared to what it was at an earlier point in time.
Solution
The reason behind low cache out compared to an earlier point in time can be due to a change in the SW update traffic. It might be possible that the earlier increase in your cache out traffic at a specific time was due to increased incoming SW update traffic and after that, the cache out returned to normal.
Another possible reason can be that your current PA cache is configured to serve only a particular type of traffic. For example;
"Your PA cache is configured to serve only HTTP traffic, and it takes a small part (like 10%) of your overall traffic, that's why your PA cache can't be higher than this percentage."
If those aren't the cases, another important reason can be that uTP (Micro Transport Protocol) is not diverting under your current PBR configuration.
See the figure below for an example. If there is no traffic on in BitTorrent UTP protocol. That means, you haven't included the rule to divert UDP port >1024 in your PBR configuration.
The basic PBR examples are as below;
-. HTTP
access-list 2001 permit tcp 203.81.128.0 0.0.31.255 gt 1024 any eq www
access-list 2001 permit tcp 211.111.224.0 0.0.31.255 gt 1024 any eq www
access-list 2002 permit tcp any eq www 203.81.128.0 0.0.31.255 gt 1024
access-list 2002 permit tcp any eq www 211.111.224.0 0.0.31.255 gt 1024
-.BT(P2P)
access-list 2003 permit tcp 203.81.128.0 0.0.31.255 gt 1024 any gt 1024
access-list 2003 permit tcp 211.111.224.0 0.0.31.255 gt 1024 any gt 1024
access-list 2004 permit tcp any gt 1024 203.81.128.0 0.0.31.255 gt 1024
access-list 2004 permit tcp any gt 1024 211.111.224.0 0.0.31.255 gt 1024
-.uTP(P2P)
access-list 2005 permit udp 203.81.128.0 0.0.31.255 gt 1024 any gt 1024
access-list 2005 permit ucp 211.111.224.0 0.0.31.255 gt 1024 any gt 1024
access-list 2006 permit udp any gt 1024 203.81.128.0 0.0.31.255 gt 1024
access-list 2006 permit udp any gt 1024 211.111.224.0 0.0.31.255 gt 1024
Including uTP in your PBR configuration should resolve the low cache-out traffic issue. However, you will require help from the PeerApp support team in order to change your PBR configuration.
And in case you're afraid that you will reach the maximum of the interface and wondering if you can add more links, you can. Just add the link to an unlinked eth port. In the following example, it is eth5.
IP is configured as below.
<nic nic_index="1">
<name>eth5</name>
<vip>10.151.1.124</vip>
<vip>FD83:DC9A:E703:201::101</vip>
</nic>
Note that in order to change IP address, the service will need to be restarted. However, in case you've just had your configuration updated, the restart will not be necessary.
If the above steps do not resolve your issue, or you need help performing the above configuration, raise a support ticket and PeerApp support team will be happy to help you.