Huawei UltraPath workingmode Value for Controller Load Balancing
Short answer
A Use `upadm set workingmode=0` in Huawei UltraPath to enable load balancing among storage controllers.
Question
Key Takeaways
This question tests the scope of UltraPath load balancing—controller-level versus intra-controller—and the trap of choosing the default mode 1 simply because it is also a balancing mode.
Huawei UltraPath's numeric working mode determines whether I/O balancing occurs within one controller or across controllers. The command upadm set workingmode=0 selects controller-level load balancing, so option A is correct.
Common mistake: Option B (1) is tempting because it is UltraPath's default load-balancing mode, but it balances paths within a single controller; the question explicitly requires load balancing among controllers, which mode 0 provides.
Expert Analysis
Where UltraPath makes the decision Huawei UltraPath is the host-side multipath layer between the operating system and the storage LUN. When an application issues I/O, UltraPath maps the LUN to a set of paths and applies its configured working mode to select the path or path group for that I/O. The question is therefore about the value that changes the scope of path selection from paths belonging to one controller to paths that reach both controllers.
Mode values and the trap
The command upadm set workingmode={ } takes a numeric working-mode value. In this context, 0 is the controller-level load-balancing mode: it allows I/O to be distributed across paths that lead to different storage controllers. 1 is the default mode described in community discussion as load balancing within a controller; it balances across paths to the same controller rather than across controllers. That makes option B the attractive wrong answer: it is a load-balancing mode, but its scope is the wrong one. The question wording says "among controllers", so the required scope is inter-controller, which points to 0.
Why A is correct
Tracing the request path makes the choice clear: application I/O -> UltraPath pseudo device -> path selection -> controller. Setting the working mode to 0 changes the path-selection policy at the UltraPath layer so that eligible paths to different controllers participate in load balancing. Modes 2 and 3 are not the parameter that implements the described controller-level balancing in this command, so they do not satisfy the scenario. The correct option is A.
Exam Strategy
When a command uses numeric mode values, translate the question's scope phrase first—for example, "among controllers" means inter-controller, not just any load balancing. Then map that scope to the documented mode instead of choosing the default value. Here, mode 1 is a distractor precisely because it is the default and still performs balancing, but only within a controller.
Frequently Asked Questions
What is the effect of upadm set workingmode=0 in Huawei UltraPath?
Is workingmode=1 the default for Huawei UltraPath?
Which UltraPath command changes the load-balancing working mode?
Community Votes
100% of anonymous learners picked answer A. Votes are pick records left by other test-takers — they are not the verified answer.
Discussion 1 contributions
Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.
From public community threads 1
-
10c5cfe 👍 1 Answered A0: load balancing between controllers 1: default setting, load balancing within a controller
Reader comments & corrections
No reader corrections yet — spotted an error or have a note? Share it below.