Acfp Information Overview - H3C SR6600 Configuration Manual

For the ACFP client to better control traffic, the two-level structure of collaboration policy and
collaboration rules is set in the collaboration to manage the traffic matching the collaboration rule based
on the collaboration policy, implementing flexible traffic management.
To better support the Client/Server collaboration mode and granularly and flexibly set different rules,
the collaboration content is divided into four parts: ACFP server information, ACFP client information,
ACFP collaboration policy and ACFP collaboration rules. These four parts of information are 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.
ACFP server information is generated by the ACFP server itself. ACFP client information, ACFP
collaboration policy, and ACFP collaboration rules are generated on the ACFP client and sent to the
ACFP server through the collaboration MIB or collaboration protocol.
The SR6600 routers do not support rate restriction of the traffic on the ACFP server.

ACFP Information Overview

ACFP server information
ACFP server information contains the following:
Supported working modes: host, pass-through, mirroring, and redirect. An ACFP server can
support multiple working modes among these four at the same time. The ACFP server and client(s)
can collaborate with each other only when the ACFP server supports the working mode of the
ACFP client.
Maximum expiration time of the supported collaboration policy: This indicates for how long the
collaboration policy of the ACFP server will remain valid.
Whether the ACFP server can permanently save the collaboration policy: It mainly refers to
whether the ACFP server can keep the original collaboration policy after reboot.
Currently supported context ID type: The location of the context ID in the packet may vary with
ACFP servers. There are five types of context IDs: no-context (no context ID is carried),
HG-context (carrying the preamble HG as the context ID), HGPlus-context (carrying the preamble
HGPlus as the context ID), FlowID-context (carrying the preamble Flow ID as the context ID),
VLANID-context (carrying VLAN ID as the context ID).
The above-mentioned information indicates the collaboration capabilities of an ACFP server. ACFP
clients can access this information through a collaboration protocol or collaboration MIB.
The SR6600 routers support only one type of context ID, namely, the VLANID-context (carrying VLAN
ID as the context ID).
2-6