Administrator Guide

The following gure shows iSCSI optimization between servers in an M1000e enclosure and a storage array in which an Aggregator
connects installed servers (iSCSI initiators) to a storage array (iSCSI targets) in a SAN network. iSCSI optimization running on the
Aggregator is congured to use dot1p priority-queue assignments to ensure that iSCSI trac in these sessions receives priority
treatment when forwarded on Aggregator hardware.
Figure 16. iSCSI Optimization Example
Monitoring iSCSI Trac Flows
The switch snoops iSCSI session-establishment and termination packets by installing classier rules that trap iSCSI protocol packets
to the CPU for examination.
Devices that initiate iSCSI sessions usually use well-known TCP ports 3260 or 860 to contact targets. When you enable iSCSI
optimization, by default the switch identies IP packets to or from these ports as iSCSI trac.
You can congure the switch to monitor trac for additional port numbers or a combination of port number and target IP address,
and you can remove the well-known port numbers from monitoring.
Information Monitored in iSCSI Trac Flows
iSCSI optimization examines the following data in packets and uses the data to track the session and create the classier entries that
enable QoS treatment:
• Initiator’s IP Address
• Target’s IP Address
• ISID (Initiator dened session identier)
• Initiator’s IQN (iSCSI qualied name)
• Target’s IQN
• Initiator’s TCP Port
106
iSCSI Optimization