Difference between revisions of "maestro reference"
From cpwiki.net
(→policy installation) |
|||
| (One intermediate revision by one user not shown) | |||
| Line 12: | Line 12: | ||
asg_blade_config pull_config | asg_blade_config pull_config | ||
| + | ==Managing Security Groups== | ||
| + | ===Connecting to a Specific Security Group Member === | ||
| + | # member <Member ID> | ||
| + | or | ||
| + | # m <Member ID> | ||
| − | + | connecting to member in specific SG | |
| + | # m <Security Group ID> <Member ID> | ||
==HA== | ==HA== | ||
clusterXL_admin up | clusterXL_admin up | ||
| + | |||
| + | |||
| + | ==orchestrator== | ||
| + | |||
| + | get port transiever typoe | ||
| + | > show maestro port x optic info | ||
Latest revision as of 16:39, 13 May 2024
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
Managing Security Groups
Connecting to a Specific Security Group Member
# member <Member ID>
or
# m <Member ID>
connecting to member in specific SG
- m <Security Group ID> <Member ID>
HA
clusterXL_admin up
orchestrator
get port transiever typoe
> show maestro port x optic info
