C H A P T E R
14
Configuring iSCSI TLV
This chapter contains the following sections:
•
Information about iSCSI TLV, page 203
•
iSCSI TLV Configuration, page 203
•
iSCSI TLV and FCoE Configuration, page 207
Information about iSCSI TLV
NICs and converged network adapters connected to a Cisco Nexus 5000 or a Cisco Nexus 6000 Series switch
by utilizing iSCSI as a storage protocol can be programmed to accept the configuration values sent by the
switch leveraging DCBX or data center bridging exchange protocol. DCBX negtioates configuration and
settings between the switch and the adapter through a variety of type-length-value (TLV) and sub-TLVs. This
allows the switch to distribute configuration values to all attached adapters from a centralized location instead
of having to manually program CoS markings on each individual server and adapter. For flexibility, Enhanced
Transmission Selection (ETS) and Priority Flow Control (PFC) parameters are coded in TLV format. However,
the use of PFC or ETS for lossy and lossless protocol behavior is not a requirement for iSCSI TLV operations
- the TLV can be leveraged for both traditional TCP or drop behavior iSCSI networks as well as for a complete
end-to-end lossless iSCSI fabric. Enabling ETS and PFC will separate storage traffic from other IP traffic and
allow for accurate and error-free configuration information to be transmitted from the switch to the adapter.
The adapter management application must ensure that the Willing mode is set to enable to accept the CoS
values from the switch.
Note
iSCSI TLV Configuration
Identifying iSCSI Traffic
You can define a class map for each class of traffic to be used in QoS policies.
Cisco Nexus 5500 Series NX-OS SAN Switching Configuration Guide, Release 7.x
OL-30895-01
203