Table of Contents
Advertisement
Configuring VAS Traffic Forwarding
Specific IP Attack filter
The behavior depends on the action configured.
•
•
•
VAS Traffic Forwarding and Bandwidth Management
The complexity of the VAS traffic forwarding results in the modification of some SCE platform
bandwidth management capabilities when using this feature:
•
•
Certain changes are required in the configuration of the global controllers to support these two
restrictions.
Global Controllers and VAS flows
When VAS traffic forwarding is enabled, the global controllers function slightly differently.
•
•
•
•
Configuring VAS Traffic Forwarding
•
•
•
•
•
•
•
•
Cisco SCE 2000 and SCE 1000 Software Configuration Guide
12-16
Report only - VAS is not affected.
Block - flow is blocked, no VAS service to give.
Bypass – Traffic will be bypassed and NO SCA BB or VAS services are given.
VAS flows are not subject to global bandwidth control.
The number of global controllers available to regular flows has been decreased from 64 to 48.
Only 48 global controllers are available to the user.
Global controllers 49-63 are used to count VAS traffic.
The reserved global controllers cannot be configured.
On VAS flows, the flow does not get its global controller from the traffic controller to which it
belongs. Rather, its global controller is set according to VAS rules.
Configuring VAS Traffic Forwarding from the SCA BB Console, page 12-17
Global Options, page 12-17
Enabling VAS Traffic Forwarding, page 12-18
Disabling VAS Traffic Forwarding, page 12-18
How to Configure the VAS Traffic Link, page 12-19
How to Configure a VAS Server, page 12-20
How to Assign a VLAN ID to a VAS Server, page 12-21
How to Configure a VAS Server Group, page 12-25
Chapter 12
Value Added Services (VAS) Traffic Forwarding
OL-7827-12
Advertisement
Table of Contents
