Gaia Clish Commands on MHO-200 - set maestro

Description:

Use these Gaia Clish commands to configure the various settings.

Important:

After each change in the configuration, you must run the save config command.

Syntax:

set maestro [ main-orchestrator <Site ID>_<Member ID> ]
      authentication
            apply-recovery-key <Site ID>_<Member ID>
            generate-recovery-key-for-peer <Site ID>_<Member ID>
      cluster <Cluster ID>
            description "Text"
            site <Site ID> member <Member ID> description "Text"
      configuration
            compatibility-mode {on | off}
      deployment
      port <Port ID>
            site <Site ID>
                   admin-state {up | down}
                   auto-negotiation {enabled | disabled}
                   description "Text"
                   external-lldp-emit {enabled | disabled}
                   fec rs544
                   speed {1G | 10G | 25G | 40G | 100G | 200G | 400G | 4x10G | 4x25G | 4x100G | 2x100G}
                   type {mgmt | uplink | downlink | ssm_sync | site_sync | tap}
      site <Site ID>
            description "Text"
            name "Text"
      site-connectivity
            apply-local
            from-token

Parameters:


Parameter	Description
`cluster <ID>`	Specifies the Cluster ID. Press the Tab key to see the available values.
`site <ID>`	Specifies the Site ID. Press the Tab key to see the available values.
`member <ID>`	Specifies the Member ID on the Site. Press the Tab key to see the available values.
`port <Port ID>`	Specifies the Port ID. Press the Tab key to see the available values.
`main-orchestrator <Site ID>_<Member ID>`	Configures the Main Orchestrator. Within a Maestro deployment, one Orchestrator acts as the Main Orchestrator - the authoritative source of truth for all deployment and cluster configuration. All configuration changes are first written to the Main Orchestrator and then propagated to all other Orchestrators in the deployment. The Main Orchestrator role is managed automatically. If the current Main Orchestrator becomes unreachable, the remaining Orchestrators in the deployment will elect a new Main Orchestrator automatically. This automatic failover ensures that cluster configuration remains consistent and accessible even during an Orchestrator failure.
`authentication apply-recovery-key <Site ID>_<Member ID>`	Applies a recovery key to recover an Orchestrator authentication.
`authentication generate-recovery-key-for-peer <Site ID>_<Member ID>`	Generates a recovery key for an Orchestrator authentication.
`description "Text"`	Configures the description text.
`configuration compatibility-mode {on \| off}`	Configures the compatibility mode.
`deployment`	Starts the interactive wizard that configures the Maestro (the number of Sites, the number of Maestro Orchestrators on each Site, the Member ID). Important: You run the command `set maestro deployment` only on the first Orchestrator. On all additional Orchestrators, you run the command `join maestro deployment`. Connection methods between sites: `direct` A dedicated cable connects the sites between each Orchestrator. `same_network` On the different Sites, the external synchronization ports on the corresponding Orchestrators must connect to each other on an isolated dedicated network. The external synchronization ports on different Sites share the same Layer 2 network. Tip: We recommend a dedicated VLAN. For each Orchestrator, for the external synchronization port, you must configure the IPv4 address and Subnet prefix. `routed` On the different Sites, the external synchronization ports on the corresponding Orchestrators must connect to each other on an isolated dedicated network. The external synchronization ports on different Sites connect across separate networks. For each Orchestrator, for the external synchronization port, you must configure the IPv4 address, Subnet prefix, and the Next Hop IPv4 address.
`admin-state {up \| down}`	Configures the administrative state of this port.
`auto-negotiation {enabled \| disabled}`	Configures the auto-negotiation for this port.
`external-lldp-emit {enabled \| disabled}`	Configures the LLDP in this port.
`fec rs544`	Configures the FEC mode for this port.
`speed`	Configures the speed for this port. To split a port, connect the Breakout cable and select the 4x value or the 2x value. See: Splitting the Ports with Breakout Cables. Changing the Speed and the Default Type of a Port in MHO-200.
`type`	Configures the type of this port: `mgmt` Management Port through which you manage a Cluster. `uplink` Uplink port that connects to your networks. `downlink` Downlink port that connects to Security Appliances. `ssm_sync` Internal Site Sync port (synchronization between Orchestrators on the same Site). `site_sync` External Site Sync port (synchronization between Orchestrators on the different Sites). `tap` Tap (Span) port - see Configuring a Tap Port on MHO-200. See Changing the Speed and the Default Type of a Port in MHO-200.
`site-connectivity {apply-local \| from-token}`	Starts the wizard that changes the Site-Sync configuration (IP address, mask length, default gateway) on one or more Orchestrators in an existing Dual Site deployment without running the full "`set maestro deployment`" wizard. `site-connectivity apply-local` Applies the new Site-Sync configuration locally and then waits for the peer Orchestrators to catch up once reachability is restored. `site-connectivity from-token` Reconfigures the Site-Sync from a deployment token. Note: The wizard applies changes in three phases - prepare, apply, finalize. Traffic continues to flow during the IP configuration. A reboot is not required. This wizard does not change the connection method (`direct` / `same_network` / `routed`).