Configuration Guide SEM Configuration
SEM Configuration
Introduction to SEM
Overview
SEM (Smart Embedded Manager) is a network management tool embedded in the
device. It can be deployed independently or configured through user commands, and is
independent of external network management, making it very easy to deploy.
The conventional external network management is accomplished by accessing the
device through the network. Once the network connection fails, the external network
management will become meaningless. Since SEM is embedded in the device, it can
directly manage the device under any circumstances and is capable of processing or
capturing the key information in case of any network and device failure.
SEM can detect the events configured by the user in a real-time manner, and will take the
corresponding actions once these events occur. The entire process is highly
customizable. By providing user with fault detection/handling and automated
management, SEM can well enhance the serviceability of device and network.
There are abundant types of SEM events. They can be critical events such as key alert
syslog, key trap and time point, or user inputs & operations such as CLI commands
inputted and user's SNMP operations. They can also be the thresholds related to
interface statistics count, snmp object value, system resources statistics and etc. SEM
also supports multiple actions, all CLI commands, log sending, device reload and etc.
Basic concepts
Event
The event concerned and configured by the user, and is affiliated with the policy. There
can be one or multiple events, and each event will be detected by a specific detector.
When event conditions are met, the event detector will trigger the event. For example, if
the user needs to detect commands containing "shutdown" in the privileged EXEC mode,
the user will need to execute "event tag example cli pattern shutdown mode exec" to
configure an event for the command line event detector.
Action
The action to be taken by the user upon occurrence of the event. Action is configured by
the user and is affiliated with the policy. There can be one or multiple actions, and each
action corresponds with a specific action configuration. Upon the occurrence of policy
event, the policy will execute the corresponding action. For example, if the user needs to
reload the device upon the occurrence of a specific event, he will need to execute "action
example reload" command.
Policy
To Next Page
Loading...
