Configuring Centralized Data Policy

Configuring Centralized Data Policy

Centralized Data policy is configured on vSmart controllers and can be used for different purpose listed below:

• Centralized Data Policy based on Prefixes and IP Headers
• Centralized Data Policy based on application information in packet payload
• Configure Data Policy to VPNs from where they receive Routes from.

Configure Centralized Data Policy based on Prefixes & IP Headers.

This Policy contains Sequence of matched action and if matches occurs associated action is taken place and policy evolution stops and if packet matches no parameter, it is dropped and discarded by default.

In Match, by default matching is done based on 6 tuple which contains Source IP address, Destination IP address, Source Port, Destination port, protocol and DSCP.

Create a list of network site to which this Centralized Policy to be applied.

Create lists of IP prefixes and VPNs:

Create lists of TLOCs

Define policing parameters, as needed:

Create a data policy and associate it with a list of VPNs:

Create a series of match–pair sequences:

Define match parameters for packets:

If a route does not match any of the conditions,it is rejected by default. To accept nonmatching prefixed, configure the default action for the policy:

Apply the policy to one or more sites in the overlay network:

Policer Parameters

In order to configure the policing parameter, configure policer which defines maximum bandwidth, burst rate for traffic interface and what to do if traffic exceeds these values.