Iscsi Configuration - Cisco Nexus B22 Design And Deployment Manual

Blade fabric extender for ibm
Hide thumbs Also See for Nexus B22:
Table of Contents

Advertisement

You can run these commands on a second Cisco Nexus Switches to verify the fabric.
Figure 9 shows a server that has successfully connected to the SAN.
Figure 9:
Server with FCoE Connected to Volumes on a Fibre Channel Array

iSCSI Configuration

iSCSI provides an alternative to FCoE for block-level storage. Through the use of the iSCSI type-length-value
(TLV) settings, iSCSI TLV-capable NICs/CNAs, and Cisco Nexus 5000/ 6000 Series Switches, configuration can
be simplified. The iSCSI TLV settings tell the host which QoS parameters to use, similar to the process for Data
Center Bridging Exchange (DCBX) Protocol and FCoE; DCBX negotiates the configuration between the switch
and the adapter through a variety of TLV and sub-TLV settings. The TLV settings can be used for traditional TCP
and drop-behavior iSCSI networks as well as for complete end-to-end lossless iSCSI fabrics. If you enable
Enchanced Transmisson Selection (ETS) and Priority Flow Control (PFC), storage traffic will be separated from
other IP traffic, allowing more accurate and error-free configurations to be transmitted from the switch to the
adapter.
Follow these steps to configure iSCSI TLV settings on each Cisco Nexus switch:
1. Define a class map for each class of traffic to be used in QoS policies.
2. Use QoS policies to classify the interesting traffic. QoS policies are used to classify the traffic of a specific
system class identified by a unique QoS group value.
3. Configure a no-drop class. If you do not specify this command, the default policy is drop.
4. Attach the created QoS policies to the system.
© 2014 Cisco | IBM. All rights reserved.
Page 27

Advertisement

Table of Contents
loading

Table of Contents