4–ConfigurationConnecting iSCSI Hosts to the iSR62004-16 ISR651101-00 EFigure 4-13 shows presenting LUN 3 incorrectly. If an iSCSI host logged into bothVPG0 and VPG1, it would have access to LUN 3 through two virtual port groups.This is invalid and will lead to serious problems.Figure 4-13. Incorrectly Presenting LUN 3Presenting the LUN at different LUN indexes for each VP will confuse the iSCSIhost MPIO software because it will see the same LUN WWLUNID at two differentindexes. This would cause the multipath I/O (MPIO) driver to panic and show ablue screen. Without an MPIO driver, the system could corrupt data on the LUN,without crashing—a situation you want to avoid.Connecting iSCSI Hosts to the iSR6200Upon logging into a Fibre Channel target WWPN, an iSR6200 blade presents aniSCSI target to which iSCSI initiators can connect. This target is defined by itsiSCSI qualified name (IQN) string. To correctly connect iSCSI initiators to FibreChannel targets through the iSR6200, it is important to understand thecomposition of the iSCSI target IQN string.iSR6200Storage ArrayBlade 121:00:00:c0:dd:13:16:4421:00:00:c0:dd:13:16:45FC1FC2Host EntitiesHost Entity 021:01:00:c0:dd:13:16:4421:01:00:c0:dd:13:16:45Host Entity 121:02:00:c0:dd:13:16:4421:02:00:c0:dd:13:16:45Host Entity 221:03:00:c0:dd:13:16:4421:03:00:c0:dd:13:16:45Host Entity 3LUN 1LUN 2LUN 3LUN 4LUN 521:00:00:c0:dd:13:16:4421:01:00:c0:dd:13:16:4421:02:00:c0:dd:13:16:4421:03:00:c0:dd:13:16:4421:00:00:c0:dd:13:16:4521:01:00:c0:dd:13:16:4521:02:00:c0:dd:13:16:4521:03:00:c0:dd:13:16:45
