12-18
Cisco SCE 2000 and SCE 1000 Software Configuration Guide
OL-7827-12
Chapter 12 Value Added Services (VAS) Traffic Forwarding
Configuring VAS Traffic Forwarding
Enabling VAS Traffic Forwarding
By default, VAS traffic forwarding is disabled. If VAS traffic forwarding is required, the user must
enable it.
For instructions on how to disable VAS traffic forwarding, see
Disabling VAS Traffic Forwarding,
page 12-18
.
There are certain other SCE platform features that are incompatible with VAS traffic forwarding. Before
enabling VAS traffic forwarding, it is the responsibility of the user to make sure that no incompatible
features or modes are configured.
The features and modes listed below cannot coexist with VAS mode:
•
Line-card connection modes — receive-only, receive-only-cascade, inline-cascade
•
Link mode other than forwarding
•
All link encapsulation protocols, including VLAN, MPLS, L2TP
•
Enhanced open flow mode
Options
The following options are available:
•
Enable/disable
— Enable or disable VAS traffic forwarding
–
Default — Disable
Step 1
From the SCE(config if)# prompt, type
VAS-traffic-forwarding
and press
Enter
.
Disabling VAS Traffic Forwarding
Disabling the VAS Traffic Forwarding feature in runtime must be done with special care. There are two
points to consider:
•
You cannot disable VAS mode in the SCE platform while the applied SCA BB policy instructs the
SCE platform to forward traffic to the VAS servers.
Therefore, you must dismiss all VAS Traffic forwarding rules in the applied SCA BB policy before
disabling the VAS traffic forwarding in the SCE platform.
•
After the SCA BB has been reconfigured, there may still be some open flows that have already been
forwarded to the VAS servers. If the VAS feature is stopped while there are still such flows open,
their packets coming back from the VAS servers may be routed to their original destination with the
VLAN tag of the VAS server on it.
Therefore, it is also highly recommended to shutdown the line card before you disable the VAS
traffic forwarding in the SCE platform to avoid inconsistency with flows that were already
forwarded to the VAS servers.