Overview
You are looking to change your PeerApp cache configuration from "Bridge mode" (Inline) to "Divert mode" (Bounce mode).
Solution
PACache can be deployed at the Core or Edge network.
Generally, there are two deployment types namely:
- Promisc mode (Inline mode)
- Bounce mode (PBR - Policy Based Routing)
Bridge/Inline mode and Divert mode use the same configuration file except that some configuration changes.
For "Divert mode" (Bounce Mode), traffic routing happens at L3, therefore, the config points to a router or a PBR appliance e.g. Sandvine DPI (Deep Packet Inspection) as illustrated below:
In order to change from Bridge mode (L2) to Divert mode (L3-Bounce Mode), the following information is required from the customer:
- Point to Point IP address with /30 to assign PBR router and PeerApp Data Interface
- Subscriber's IP blocks
Customers should provide the above information in a support ticket for configuration by a support agent.
<supportagent>
The support agent should execute the required configuration with the provided customer information as documented in PACache Configuration - cluster_conf.xml which provides example configurations for different modes. This article also includes the Cluster Configuration Guide which describes the different parameters in detail.
Example:
A customer looking to have the following subscriber IP blocks added in Bounce Mode (divert mode) to the 192.168.250.3/28 serial IP connecting to their PBR router via the eth4 interface will have the following configuration:
164.160.136.0/24
164.160.137.0/24
164.160.138.0/24
164.160.139.0/24
Once the requisite changes have been done based on the customer information provided, the new configuration can then be updated by following the steps in PeerApp: Updating the Cluster Configuration.
The PACache - Deployment with Customer Network article provides additional useful information on the supported deployment modes.
Note: As this is changing the development design, PS team should involve.
</supportagent>