The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Following is an example illustrating the steps in configuring VAS traffic forwarding, first on the SCE platform and then from the SCA BB Console. This example shows how to configure one VAS group. This group will forward traffic to VAS servers for content filtering.
In configuring the SCE platform for VAS traffic forwarding, the purpose of the traffic forwarding is irrelevant. It is only necessary to know how many servers there are, how many server groups, and which servers should be assigned to which groups.
After the SCE platform has been configured, open the SCA BB console to configure VAS traffic forwarding in the SCA BB application. While configuring the SCA BB application for VAS traffic forwarding, the purpose of the traffic forwarding is relevant. So, assign meaningful names to the VAS server groups and traffic forwarding tables.
This example illustrates how to configure the SCA BB application to forward traffic for content filtering. The VAS server group and the traffic forwarding table are both named ‘Content Filtering’. A package is created, named ‘VAS Package’, and the Content Filtering table is assigned to that package.
See Chapter 1, “Configuring the SCA BB Application to Support VAS Traffic Forwarding” for a full description of the steps provided in this section.
To configure VAS traffic forwarding in the SCA BB application, complete the following steps:
Step 2 Rename the VAS server group to “Content Filtering”.
Figure 1-1 Renaming the Traffic Forwarding Group
Step 3 Create and configure the “Content Filtering” VAS forwarding table.
Figure 1-2 Configuring the VAS Forwarding Table
Step 4 Create the “VAS Package” package and assign the “Content Filtering” VAS forwarding table to it.
Figure 1-3 Assigning the VAS Forwarding Table to a Package