nerdexam
Cisco

352-001 · Question #279

You are using iSCSI to transfer files between a 10 Gigabit Ethernet storage system and a 1 Gigabit Ethernet server. The performance is only approximately 700 Mb/s and output drops are occurring on the

The correct answer is A. Use a WRED random drop policy.. Output drops on the server switch port result from a 10 GbE-to-1 GbE speed mismatch; WRED proactively signals TCP senders to reduce their rate before the queue overflows, improving throughput cost-effectively.

Design Considerations

Question

You are using iSCSI to transfer files between a 10 Gigabit Ethernet storage system and a 1 Gigabit Ethernet server. The performance is only approximately 700 Mb/s and output drops are occurring on the server switch port. Which action will improve performance in a cost-effective manner?

Options

  • AUse a WRED random drop policy.
  • BIncrease the queue to at least 1 GB.
  • CEnable the TCP Nagle algorithm on the receiver.
  • DChange the protocol to CIFS.

How the community answered

(36 responses)
  • A
    75% (27)
  • B
    8% (3)
  • C
    3% (1)
  • D
    14% (5)

Why each option

Output drops on the server switch port result from a 10 GbE-to-1 GbE speed mismatch; WRED proactively signals TCP senders to reduce their rate before the queue overflows, improving throughput cost-effectively.

AUse a WRED random drop policy.Correct

WRED (Weighted Random Early Detection) monitors average queue depth and randomly discards packets as congestion builds, triggering TCP's congestion control mechanism at the sending storage system to reduce its window size and transmission rate. This prevents tail-drop scenarios where the entire queue fills and all packets are lost, resulting in more stable throughput than reactive drop policies. It is cost-effective because it requires only a QoS configuration change on the switch rather than a hardware upgrade.

BIncrease the queue to at least 1 GB.

A 1 GB output queue would delay drops but not prevent them - it causes severe bufferbloat by increasing latency without signaling TCP to slow down, and 1 GB of switch buffer memory is neither practical nor cost-effective.

CEnable the TCP Nagle algorithm on the receiver.

The TCP Nagle algorithm coalesces small segments to reduce overhead, but iSCSI workloads require Nagle to be disabled for optimal block storage performance; enabling it on the receiver would not resolve queue overflow from a speed mismatch.

DChange the protocol to CIFS.

CIFS (Common Internet File System) is a file-level sharing protocol and is not an equivalent replacement for iSCSI block storage; switching protocols does not address the underlying 10G-to-1G bandwidth mismatch causing the drops.

Concept tested: WRED congestion management for iSCSI storage traffic

Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/qos_conavd/configuration/xe-3s/qos-conavd-xe-3s-book/qos-conavd-cfg-wred.html

Topics

#iSCSI#WRED#storage networking#output drops

Community Discussion

No community discussion yet for this question.

Full 352-001 Practice