H3C Technologies H3C SecPath F5020 - Manual (Page 74)

65
Assigning a context to a security engine group
A context assigned to a security engine group resides on all security engines in the group.
You can assign up to 64 contexts to a security engine group. However, a context can be assigned only
to one security engine group. To change an assignment, you must reclaim the context before assigning
it to the new security engine group.
You can add a security engine to a security engine group before or after assigning a context to the
security engine group.
To assign a context to a security engine group:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter context view. context context-name N/A
3. Assign the context to a
security engine group. location blade-controller-team team-id
By default, the default context
resides on all security engine
groups. A non-default context does
not reside on any security engine
groups.
Assigning resources to a context
Assigning CPU, disk, and memory resources to a context
When you assign a context to a security engine group, the system automatically assigns CPU, disk space,
and memory space resources on the security engines to the context. All contexts residing on the same
security engine share and compete for the engine's free CPU, disk, and memory resources. To prevent
one context from occupying too many resources, assign CPU, disk space resources, and memory space
resources to the contexts. To assign resources to a context, specify a CPU weight, disk space percentage,
and memory space percentage for the context.
CPU resources assignment guidelines
When the CPU resources on a security engine cannot meet the processing requirements from contexts,
the system allocates CPU resources on the engine as follows:
1. Identifies the CPU weights of all contexts on the engine.
2. Calculates the percentage of each context's CPU weight among the CPU weights of all contexts.
3. Allocates CPU resources to contexts based on their CPU weight percentages.
For example, three contexts share the same CPU. You can assign a weight of 2 to the key context and a
weight of 1 to each of the other two contexts. When the system is running out of CPU resources, the key
context can use approximately two times of the CPU resources that each of the other two contexts can
use.
Disk space assignment guidelines
When you assign disk space to a context, follow these guidelines: