156-836 · Question #108
What does the command'g_all' do?
The correct answer is A. It's followed by other command and execute it on all active Appliances within Security Group. The g_all command will perform following instruction on all ACTIVE SGMs. For example, g_all "touch test.txt" will create the test.txt file on all SGMs.
Question
What does the command'g_all' do?
Options
- AIt's followed by other command and execute it on all active Appliances within Security Group
- BIt's followed by other command and execute it on all Appliances connected to Orchestrator
- CSwitches all Appliances to Global mode
- DBring up all Appliances
How the community answered
(27 responses)- A89% (24)
- B7% (2)
- C4% (1)
Explanation
The g_all command will perform following instruction on all ACTIVE SGMs. For example, g_all "touch test.txt" will create the test.txt file on all SGMs.
Topics
Community Discussion
4
Samuel O.Mar 2, 2026The correct answer is A. The g_all command is a prefix you use in the Orchestrator CLI to fan out whatever follows it to every active Appliance inside the specific Security Group you are working in, not every single appliance connected to the Orchestrator across all groups. I ran into this distinction on a real deployment where someone used g_all thinking it would hit every box in the environment and was surprised when it only touched the active ones in that group, which is actually the safe behavior you want in production. Options B, C, and D are wrong because B confuses the Security Group scope with global Orchestrator scope, while C and D describe state changes that this command simply does not perform.
Orla P.Mar 4, 2026g_all is correct because it scopes the following command to every active Appliance inside the Security Group, not every Appliance the Orchestrator knows about, so option B is the common trap here. The distinction matters in production because you may have inactive or quarantined Appliances connected to the Orchestrator that you deliberately want to exclude.
Yusuf A.Mar 10, 2026So my senior had me run g_all on the Maestro box last week and it only hit the appliances in our specific Security Group, not every single box connected to the Orchestrator, which made me think the scope is tighter than it looks. Does g_all still skip an appliance in the group if it is in a non-active state, or does it try to reach all members regardless of their current status?
Orla P.Mar 12, 2026g_all sends to all members of that Security Group regardless of state, so you will see a timeout or connection error in the output for any non-active SGM rather than a clean skip.