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.
There are three broad aspects to configuring VAS traffic forwarding on the SCE platform:
There are two global VAS traffic forwarding options:
By default, VAS traffic forwarding is disabled. If you require VAS traffic forwarding, you can enable it any time.
For instructions on how to disable VAS traffic forwarding, see Disabling VAS Traffic Forwarding.
There are certain other SCE platform features that are incompatible with VAS traffic forwarding. Before enabling VAS traffic forwarding, you must make sure that no incompatible features or modes are configured.
The following options are available:
To enable VAS traffic forwarding, use the VAS-traffic-forwarding command in the SCE interface configuration mode.
There are two conditions to consider while disabling the VAS Traffic Forwarding feature in run time:
Therefore, dismiss all VAS traffic forwarding rules in the applied SCA BB policy before you disable the VAS traffic forwarding in the SCE platform.
Therefore, to avoid inconsistency with the flows that are already forwarded to the VAS servers, shutdown the line card before you disable the VAS traffic forwarding in the SCE platform.
To disable VAS traffic forwarding, complete the following steps:
Step 1 From the SCA BB console, remove all the VAS table associations to packages and apply the changed policy.
Step 2 Shut down the line card.
At the SCE(config if)# prompt, enter the shutdown command, and press Enter.
Step 3 Disable VAS traffic forwarding.
At the SCE(config if)# prompt, enter the no VAS-traffic-forwarding command and press Enter.
At the SCE(config if)# prompt, enter the no shutdown command and press Enter.
By default, the VAS traffic is transmitted on Link 1. If the VAS servers are connected on Link 0, configure the VAS traffic link to Link 0.
Note Although it supports up to eight GBE links, the SCE 8000 GBE platform supports VAS traffic forwarding only on Link 0 and Link 1. VAS traffic cannot be configured on any other link.
Note The VAS traffic link should be in Forwarding mode.
To select the link for VAS traffic, enter the VAS-traffic-forwarding traffic-link {link-0|link-1} command at the SCE interface configuration mode.
To revert to the default link for VAS traffic, enter the no VAS-traffic-forwarding traffic-link command at the SCE interface configuration mode.
To configure a VAS server, first define the VAS servers. Each VAS server has the following parameters:
These sections explain how to perform the following operations for individual VAS servers:
Note The VAS server is not operational until the VLAN tag is defined, even if the server itself is enabled.
Note The server is not operational until a VLAN tag has also been defined.
To enable a VAS server, enter VAS-traffic-forwarding VAS server-id number enable command at the SCE interface configuration mode.
To disable a VAS server, enter VAS-traffic-forwarding VAS server-id number disable command at the SCE interface configuration mode.
To restore all VAS server properties to default value, no VAS-traffic-forwarding VAS server-id number command at the SCE interface configuration mode.
Use VAS-traffic-forwarding VAS server-id number VLAN vlan-id command to the assign the VLAN ID to a specified VAS server.
The following options are available:
The VLAN tag can be redefined as necessary.
Note the following important points:
To configure the VLAN tag number for a VAS server, enter the VAS-traffic-forwarding VAS server-id number VLAN vlan-id command at the SCE interface configuration mode.
To remove the VLAN tag number from a VAS server, enter the no VAS-traffic-forwarding VAS server-id number VLAN command at the SCE interface configuration mode.
You can also use the default form of the command to remove the VLAN tag configuration.
By default, the VAS server health check is enabled, however you may disable it.
The health check is activated only if all the following conditions are true. If the health check is enabled and if any one or more of the following conditions are not met, then the server will be in a Down state:
If the health check of the server is disabled, its operational status depends on the following (requirements for Up state are in parentheses):
The following options are available:
– source portnumber —Source port number for health check.
– destination portnumber —Destination port number for health check.
– Default—<63140,63141>used for Server 0 through <63154,63155> used for Server 7.
To enable VAS server health check, enter the VAS-traffic-forwarding VAS server-id number health-check command at the SCE interface configuration mode.
To disable VAS server health check, enter the no VAS-traffic-forwarding VAS server-id number health-check command at the SCE interface configuration mode.
To define the UDP ports for health check traffic, enter the VAS-traffic-forwarding VAS server-id number health-check UDP ports source portnumber destination portnumber command at the SCE interface configuration mode.
To remove the UDP ports configuration, enter the no VAS-traffic-forwarding VAS server-id number health-check UDP ports command at the SCE interface configuration mode.
You can also use the default form of the command to remove the UDP port configuration.
Use the pseudo-ip ip-address [mask] command to configure source and destination pseudo IP addresses for the health check packets. This command allows you to specify a unique IP address for use by the health check packets.
This command is a ROOT level command and is available under the GBE configuration interface mode. Configure those interfaces that connect the SCE platform to the VAS servers. The following are the default interfaces:
The SCE platform uses the pseudo IP address as follows:
– Source IP address for health check packets going upstream direction.
– Destination IP address for health check packets going downstream direction.
– Source IP address for health check packets going downstream direction.
– Destination IP address for health check packets going upstream direction.
The following options are available:
– Default—255.255.255.255 (The subnet mask can be set to 255.255.255.255, because the health check mechanism requires only one IP address per interface.)
To define the pseudo IP address, enter the pseudo-ip ip-address [mask] command at the SCE interface configuration mode.
To delete the pseudo IP address, enter the no pseudo-ip ip-address [mask] command at the SCE interface configuration mode.
You can define up to eight VAS server groups. Each VAS server group has the following parameters:
You can perform these operations for a VAS server group:
This section explains how to add servers to and remove servers from a specified VAS server group. This section consists of these topics:
To add a VAS server to a VAS server group, enter the VAS-traffic-forwarding VAS server-group group-number server-id id-number command at the SCE interface configuration mode.
To remove a VAS server from a VAS server group, enter the no VAS-traffic-forwarding VAS server-group group-number server-id id-number command at the SCE interface configuration mode.
To remove all VAS servers from a specified VAS server group and set all group parameters to their default values, enter the no VAS-traffic-forwarding VAS server-group group-number command at the SCE interface configuration mode.
This section explains how to configure the following failure parameters for the specified VAS server group:
– Block—The SCE platform blocks all new flows assigned to the failed VAS server group.
– Pass—The SCE platform considers all new flows assigned to the failed VAS server group as regular nonVAS flows and processes these flows without VAS service.
The following options are available:
To configure the minimum number of active servers, enter the VAS-traffic-forwarding VAS server-group group-number failure minimum-active-servers min-number command at the SCE interface configuration mode.
To reset the minimum number of active servers, enter the default VAS-traffic-forwarding VAS server-group group-number failure minimum-active-servers min-number command at the SCE interface configuration mode.
To configure the failure action for a specified VAS server group, enter the VAS-traffic-forwarding VAS server-group group-number failure action {block | pass} command at the SCE interface configuration mode.
To revert the failure action configuration for the specified VAS server group to the default value (pass), enter the default VAS-traffic-forwarding VAS server-group group-number failure action command at the SCE interface configuration mode.