Ruijie RG-S2900G-E Series, Руководство по настройке

Страница: 815 / 943

Configuration Guide SEM Configuration
Policy is used to sort the relationship between events and between event and action. The
policy will be triggered when the policy event meets the preconfigured rule and policy
actions will be taken in turn.
Event detector
It is embedded in a specific service and monitor such service according to user
configurations. It will also trigger the event when the service meets user configurations
and forward the event message to the intelligent management server.
Intelligent management server
It receives the event notice sent by event detector and determines whether or not to
trigger the policy according to the actual circumstances. Once the policy is triggered, the
intelligent management server will execute such policy.
Policy manager
It manages SEM policy information and execute the actions defined in the policy after the
policy has been triggered by the intelligent management server.
SEM environment variable
The variable used by policy action during the process of SEM operation. There are three
types of SEM environment variables:

Global variable

System local variable

User local variable
When using variable in the policy, the word and symbol between "$" and the subsequent
first character which is not a letter, number or underline will be substituted as the name of
variable. The global variable can be used in all policies, while system local variable and
user local variable are both local variables which can only be used in a specific policy.
System local variable is read-only and cannot be changed. User local variable is defined
by the action in policy during its execution. Therefore, system local variable generally
starts with "_" to avoid conflicting with user local variable.
SEM application-specific event
SEM only supports internal use of application-specific event within SEM system, so as to
help the running policy to trigger other policies. To distinguish between different
application-specific events, sub-system and type are used to identify such events. SEM
application-specific events are detected by application-specific event detector according
to the sub-system and type, and will be published by the application-specific event action
during policy execution. When a policy action publishes an application-specific event of
certain sub-system and type, the event with corresponding sub-system and type being
detected will be triggered. For details, please refer to "SEM detection of
application-specific event" in "Typical SEM configuration example".
SEM named counter