Maestro Auto-Scaling

1. Connect to the Gaia Portal on the Orchestrator.

2. From the left tree, click Orchestrator.

3. In the left pane Unassigned Gateways / assigned Gateways (if there is more than one appliance assigned to the Security Group), right-click a Security Appliance and click Set Scale Unit.

4. In the middle pane Topology, right-click the Security Group and click Set Security Group configuration.

5. Click the tab Auto-Scaling settings.

6. Configure the Scale up policy rules:

   1. Click Add.

   2. Select the applicable values in the fields:

      Field	Available Values
      When	Each Member Measures the value according to "Each Member" KPIs. "Asks" for new Security Appliances to be added to the Security Group when "Each Member" passes the threshold configured in the rule. Security Group (Average) Measures the value according to "Security Group (Average)" KPIs. "Asks" for new Security Appliances to be added to the Security Group when the "Security Group (Average)" passes the threshold configured in the rule.
      With	CPU Utilization (%) Throughput (Gbps) Packets (p/s) Connections The KPI for the rule.
      More than	Configure the threshold between: 1 and 100 for the CPU utilization metric. 1 and 1099511627776 (1TB) for other metrics.
      For consecutive period of	Configure the duration between 1 and 86400 seconds (1 day).

   3. Click OK.

   4. In the Attach up to field, configure the number of Security Appliances to attach to this Security Group.

7. Configure the Scale down policy rules:

   1. Click Add.

   2. Select the applicable values in the fields:

      Field	Available Values
      When	Security Group (Average) Measures the value according to "Security Group (Average)" KPIs. Marks the scale unit that is currently occupied by the Security Group (if there is such a one) as a release candidate when the "Security Group (Average)" is less than the threshold configured in the rule. This means the Security Group can release the current scale unit.
      With	CPU Utilization (%) Throughput (Gbps) Packets (p/s) Connections The KPI for the rule.
      Less than	Configure the threshold between: 1 and 100 for the CPU utilization metric. 1 and 1099511627776 (1TB) for other metrics.
      For consecutive period of	Configure the duration between 1 and 86400 seconds (1 day).

   3. Click OK.

   4. In the Detach single scale unit field, configure the number of Security Appliances to detach from this Security Group.

8. Click OK.

1. Connect to the command line on the Orchestrator.

2. Log in to Gaia Clish.

3. Configure the Scale up policy rules:

   add maestro auto-scale security-group-id <Security Group ID> scale-up-policy when {Each-Member | Security-Group-Average} with {CPU | bps | pps | connections} more-than <Threshold> period <Duration>

4. Configure the number of Security Appliances to attach to this Security Group when conditions match a minimum of one of the configured scale up rules:

   set maestro auto-scale security-group-id <Security Group ID> scale-units-to-attach <1-4>

5. Configure the Scale down policy rules:

   add maestro auto-scale security-group id <Security Group ID> scale-down-policy when <Security-Group-Average> with {CPU | bps | pps | connections} less-than <Threshold> period <Duration>

6. Enable Auto-Scaling in this Security Group:

   set maestro auto-scale security-group-id <Security Group ID> state enable

7. Configure a scale Security Appliance on a specific site based on the Security Appliance serial number:

   Important - If this Security Appliance is the only one in the Security Group (and Site), then do not configure it as a scale Security Appliance.

   set maestro auto-scale site-id <Site ID> scale-unit-serial <Serial Number> state on

The applicable commands in Gaia Clish:

• add maestro auto-scale

• set maestro auto-scale

• show maestro auto-scale

• delete maestro auto-scale

To troubleshoot issues with Auto-Scaling, make sure that the masd service is running on the Orchestrator and Security Group Members:

1. On the Orchestrator:

   1. Connect to the command line on the Orchestrator.

   2. Log in to the Expert mode.

   3. Get the status of the masd service:

      service masd status

      The output must be:

      masd is running...

2. On the Security Group:

   1. Connect to the command line on the Security Group.

   2. Log in to the Expert mode.

   3. Get the status of the masd service:

      service masd status

      The output must be:

      masd is running...

Examine the logs of the masd daemon on the Orchestrator and Security Group Members:

• On the Orchestrator:

  1. Connect to the command line on the Orchestrator.

  2. Log in to the Expert mode.

  3. Examine the masd log file in real time:

     tail -F /var/log/masd.elg

• On the Security Group:

  1. Connect to the command line on the Security Group.

  2. Log in to the Expert mode.

  3. Examine the masd log file in real time:

     tail -F /var/log/masd.elg

To make sure that the Orchestrator correctly applied the Auto-Scaling rules you configured in Gaia Portal or Gaia Clish:

1. Connect to the command line on the Orchestrator.

2. Log in to the Expert mode.

3. Get the list of rules:

   mas_cli --interactive-rules

4. Compare the rules you see in the command line with the rules you configured on the Orchestrator.

To see if Security Group Members are reporting their KPIs to the Orchestrator:

1. Connect to the command line on the Orchestrator.

2. Log in to the Expert mode.

3. Get the KPI status:

   mas_cli --interactive