A PowerScale cluster has two ports that are configured per node. Each port is on a different VLAN. Although incoming traffic is evenly distributed, transmitted data from PowerScale uses one port…

Question

Options

• AStatic routes are configured on the less-used port.
• BA default gateway was not configured on both ports.
• CSource-Based Routing is not enabled on the cluster.
• DPriority of the gateway in the less-used port set too low.

• A
  6% (2)
• B
  72% (23)
• C
  6% (2)
• D
  16% (5)

Explanation

Option B is correct because without a default gateway configured on both ports, the cluster has no outbound routing path through the second port for traffic destined beyond its directly connected subnet. Incoming clients can reach either port's IP address (explaining the balanced ingress), but when PowerScale needs to send responses or initiate outbound traffic to non-local subnets, only the port with a configured gateway can route that traffic - so egress flows predominantly through one port.

Why the distractors are wrong:

• A is wrong because static routes on the less-used port would add routing knowledge to that port, likely increasing its usage, not reducing it.
• C is wrong because Source-Based Routing (SBR) is a feature that helps fix asymmetric routing by tying response traffic to the interface that received the request - its absence is a contributing factor, not the root cause described here, and it depends on gateways being properly configured anyway.
• D is wrong because a low-priority gateway on the less-used port would mean that gateway loses tie-breaking decisions, but it doesn't explain the level of imbalance described; also, the question describes the less-used port as the problem, not the more-used one.

Memory tip: Think of each port as a one-way door: any door can let guests in, but only a door with a doorman (gateway) can direct guests back out. One doorman = one exit = imbalanced outbound traffic.

No community discussion yet for this question.