Configuring the Cluster State (g_clusterXL_admin)

Description

Use the "g_clusterXL_admin" command in the Expert mode to change the cluster state manually, to UP or DOWN, for one or more Security Group Members.

Use Case

This command is useful for tests and debug.

Best Practice - Do not use this command in production environments, because it can cause performance degradation.

Syntax

g_clusterXL_admin -h

g_clusterXL_admin -b <SGM IDs> {up | down [-a]} [-r]

Parameters

Parameter

Description

-h

Shows the built-in help.

-b <SGM IDs>

Applies to Security Group Members as specified by the <SGM IDs>.

<SGM IDs> can be:

  • No <SGM IDs> specified, or all

    Applies to all Security Group Members and all Maestro Sites

  • One Security Group Member (for example, 1_1)

  • A comma-separated list of Security Group Members (for example, 1_1,1_4)

  • A range of Security Group Members (for example, 1_1-1_4)

  • In Dual Site, one Maestro Site (chassis1, or chassis2)

  • In Dual Site, the Active Maestro Site (chassis_active)

up

Changes the cluster state to UP.

down

Changes the cluster state to DOWN.

-a

Synchronizes accelerated connections to other Security Group Members.

-r

Runs this command on all <SGM IDs>, except the local Security Group Member.

Notes:

  • When the Security Group Member is in the Administrative DOWN state:

    • Gaia gClish commands do not run on this Security Group Member.

    • Traffic is not sent to this Security Group Member.

    • The "asg stat" command shows this Security Group Member as "DOWN (admin)".

  • When the cluster state of the Security Group Member is changed to Administrative UP, it automatically synchronizes the configuration from a different Security Group Member that is in the UP state.

  • This command cannot change the state of a Security Group Member to UP if it is in the DOWN state because of a software or hardware problem.

  • The "g_clusterXL_admin" command generates log entries.

    To see these log entries, run:

    asg log --file audit

Example

[Expert@MyChassis-ch0x-0x:0]# g_clusterXL_admin -b 2_03 up
You are about to perform blade_admin up on blades: 2_03
This action will change members state
 
Are you sure? (Y - yes, any other key - no) y
 
Blade_admin up requires auditing
Enter your full name: John Doe
Enter reason for blade_admin up [Maintenance]: test
WARNING: Blade_admin up on blades: 2_03, User: John Doe, Reason: test
 
Members outputs:
-*- 1 blade: 2_03 -*-
Setting member to normal operation ...
Member current state is ACTIVE
[Expert@MyChassis-ch0x-0x:0]#