Difference between revisions of "maestro reference"
From cpwiki.net
(→policy installation) |
(→policy installation) |
||
| Line 6: | Line 6: | ||
===policy installation=== | ===policy installation=== | ||
| − | Management ServerClosed installs the policy on the SMO Master and then it is copied to the other members. Use [[asg policy - command|asg policy]] to verify or unload a policy. | + | Management ServerClosed installs the policy on the SMO Master and then it is copied to the other UP members. Use [[asg policy - command|asg policy]] to verify or unload a policy. |
| + | ===Synchronizing Policy and Configuration Between Security Group Members=== | ||
| + | |||
| + | synchronize the policies manually to a SG member | ||
| + | asg_blade_config pull_config | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ==HA== | ||
| + | clusterXL_admin up | ||
Revision as of 21:57, 20 October 2023
Contents |
security groups
Single Management Object (SMO) handles all management tasks, such as Security Gateway configuration, policy installation, remote connections, and logging. The Active Security Group Member with the lowest ID number is automatically assigned to be the SMO.
identify the SMO and tasks
# asg stat -i tasks
policy installation
Management ServerClosed installs the policy on the SMO Master and then it is copied to the other UP members. Use asg policy to verify or unload a policy.
Synchronizing Policy and Configuration Between Security Group Members
synchronize the policies manually to a SG member
asg_blade_config pull_config
HA
clusterXL_admin up
