3Com 5500G Configuration And Command Reference Manual - page 11
Introduction to ACFP
11
control the traffic on the ACFP server (namely, the routing/switching
component shown in Figure 1), by implementing the following functions:
■
Mirroring and redirecting the traffic on the ACFP server to the ACFP
client
■
Permitting or denying the traffic from the ACFP server
■
Carrying the context ID in a packet to enable the ACFP server and
ACFP client to communicate the packet context with each other. The
detailed procedure is as follows:
The ACFP server maintains a context table that can be queried by context
ID. Each context ID corresponds with an ACFP collaboration policy that
contains information including the packet’s inbound and outbound ports
and the collaboration rules. When the packet received by the ACFP server
is redirected or mirrored to the ACFP client after matching a collaboration
rule, the packet carries the context ID of the collaboration policy to which
the collaboration rule belongs. When the redirected packet is returned
from the ACFP client, the packet also carries the context ID. With the
context ID, the ACFP server knows that the packet is returned after being
redirected and then forwards the packet normally.
For the ACFP client to better control traffic, the two-level structure of the
collaboration policy and collaboration rules is set in the collaboration MIB
to manage the traffic matching the collaboration rule based on the
collaboration policy. This provides flexible traffic management.
To better support the client/server collaboration mode and to be flexible
with setting different rules, the collaboration content is divided into four
parts:
■
ACFP server information
■
ACFP client information
■
ACFP collaboration policy
■
ACFP collaboration rules
This information is saved in the ACFP server. An ACFP server supports
multiple ACFP clients. Therefore, ACFP client information, ACFP
collaboration policy, and ACFP collaboration rules are organized in the
form of tables.