> # Target Storage Device Requiring LUN Mapping Example

> This example scenario 2 assumes the following configuration:

> - Access control is based on Fibre Channel zoning.
> - There is target-based LUN mapping or LUN masking.
> - There is no iSCSI authentication (none).
> - The iSCSI initiator is assigned to different VSANs.

> ## Detailed Steps

> To configure this example, follow these steps:

> 1. Configure null authentication for all iSCSI hosts.
> 1. In Cisco DCNM-SAN, choose End Devices > iSCSI in the Physical Attributes pane.
> 2. Select none from the AuthMethod drop-down menu in the Information pane.
> 3. Click the Apply Changes icon.
> 2. Configure iSCSI to dynamically import all Fibre Channel targets into the iSCSI SAN using auto-generated iSCSI target names.
> 1. In Device Manager, click IP > iSCSI.
> 2. Click the Targets tab.
> 3. Check the Dynamically Import FC Targets check box.
> 4. Click Apply.
> 3. Configure the Gigabit Ethernet interface in slot 7 port 1 with an IPv4 address and enable the interface.
> 1. In Cisco DCNM-SAN, choose Switches > Interfaces > Gigabit Ethernet in the Physical Attributes pane.
> 2. Select the IP Address tab in the Information pane and click Create Row.
> 3. Set the IP address and subnet mask for the Gigabit Ethernet interface in slot 7 port 1.
> 4. Click Create.
> 5. Click the General tab and select up from the Admin drop-down menu for the Gigabit Ethernet interface in slot 7 port 1.
> 6. Click the Apply Changes icon.
> 4. Configure the iSCSI interface in slot 7 port 1 to identify all dynamic iSCSI initiators by their IP address and enable the interface.
> 1. In Cisco DCNM-SAN, choose Switches > Interfaces > FC Logical in the Physical Attributes pane.
> 2. Select the iSCSI tab in the Information pane.
> 3. Select ipaddress from the Initiator ID Mode drop-down menu and click the Apply Changes icon.
> 4. In Device Manager, choose Interfaces > Ethernet and iSCSI.
> 5. Click the iSCSI tab.
> 6. Select up from the Admin drop-down menu for the iSCSI interface in slot 7 port 1.
> 7. Click Apply.
> 5. Configure the Gigabit Ethernet interface in slot 7 port 5 with the IPv4 address and enable the interface.
> 1. In Cisco DCNM-SAN, choose Switches > Interfaces > Gigabit Ethernet in the Physical Attributes pane.
> 2. Click the IP Address tab in the Information pane and click Create Row.
> 3. Set the IP address and subnet mask for the Gigabit Ethernet interface in slot 7 port 5.
> 4. Click Create.
> 5. Select the General tab and select up from the Admin drop-down menu for the Gigabit Ethernet interface in slot 7 port 5.
> 6. Click the Apply Changes icon.
> 6. Configure the iSCSI interface in slot 7 port 5 to identify all dynamic iSCSI initiators by IP address and enable the interface.
> 1. In Cisco DCNM-SAN, choose Switches > Interfaces > FC Logical in the Physical Attributes pane.
> 2. Click the iSCSI tab in the Information pane.
> 3. Select ipaddress from the Initiator ID Mode drop-down menu and click the Apply Changes icon.
> 4. In Device Manager, choose Interfaces > Ethernet and iSCSI.
> 5. Click the iSCSI tab.
> 6. Select up from the Admin drop-down menu for the iSCSI interface in slot 7 port 5.
> 7. Click Apply.
> 7. Configure for static pWWN and nWWN for host 1.
> 1. In Device Manager, choose IP > iSCSI.
> 2. Click the Initiators tab.
> 3. Check the Node Address Persistent and Node Address System-assigned check boxes the Host 1 iSCSI initiator.
> 4. Click Apply.
> 8. Configure for static pWWN for Host 2.
> 1. In Device Manager, Choose IP > iSCSI.
> 2. Click the Initiators tab.
> 3. Right-click on the Host 2 iSCSI initiator and click Edit pWWN.
> 4. Select 1 from the System-assigned Num field and click Apply.
> 9. View the configured WWNs.

> Note The WWNs are assigned by the system. The initiators are members of different VSANs.

> 1. In Cisco DCNM-SAN, choose End Devices > iSCSI in the Physical Attributes pane.
> 2. Click the Initiators tab.
> 10. Create a zone for Host 1 and the iSCSI target in VSAN 1.

> Note Use the IP address of the host in zone membership configuration because the iSCSI interface is configured to identify all hosts based on IP address.

> 1. In Cisco DCNM-SAN, choose Zones > Edit Local Full Zone Database.
> 2. Select VSAN 1 from the VSAN drop-down menu in the Edit Local Full Zone Database dialog box.
> 3. Select the Zones folder in the left navigation pane and click Insert.
> 4. Set the Zone Name field to iscsi-zone-1 and click OK.
> 5. Select the iscsi-zone-1 folder in the left navigation pane and click Insert.
> 6. Set the ZoneBy radio button to WWN.
> 7. Set the Port WWN to the pWWN for the Fibre Channel target (that is, 21:00:00:20:37:6f:fd:97). and click Add.
> 8. Set the ZoneBy radio button to iSCSI IP Address/Subnet.
> 9. Set the IP Address/Mask field to the IP Address for Host 1 iSCSI initiator (10.11.1.10) and click Add.

> Note Fibre Channel storage for zone membership for the iSCSI initiator, either the iSCSI symbolic node name or the pWWN, can be used. In this case, the pWWN is persistent.

> 11. Create a zone set in VSAN 1 and activate it.
> 1. In Cisco DCNM-SAN, choose Zones > Edit Local Full Zone Database.
> 2. Select VSAN 1 from the VSAN drop-down menu in the Edit Local Full Zone Database dialog box.
> 3. Select the Zoneset folder in the left navigation pane and click Insert.
> 4. Set the Zoneset Name to zonset-iscsi-1 and click OK.
> 5. Click on the zoneset-iscsi-1 folder and click Insert.
> 6. Set the Zone Name field to iscsi-zone-1 and click OK.
> 7. Click Activate to activate the new zone set.
> 8. Click Continue Activation to finish the activation.
> 12. Create a zone with host 2 and two Fibre Channel targets.

> Note If the host is in VSAN 2, the Fibre Channel targets and zone must also be in VSAN 2.

> Note iSCSI interface is configured to identify all hosts based on node name.

> 1. In Cisco DCNM-SAN, choose Zones > Edit Local Full Zone Database.
> 2. Select VSAN 2 from the VSAN drop-down menu in the Edit Local Full Zone Database dialog box.
> 3. Select the Zones folder in the left navigation pane and click Insert.
> 4. Set the Zone Name field to iscsi-zone-2 and click OK.
> 5. Select the iscsi-zone-2 folder in the left navigation pane and click Insert.
> 6. Set the ZoneBy radio button toWWN.
> 7. Set the Port WWN to the pWWN for one of the Fibre Channel targets (for example, 21:00:00:20:37:6f:fe:5) and click Add.
> 8. Set the Port WWN to the pWWN for another of the Fibre Channel targets (for example, 21:00:00:20:37:a6:a6:5d) and click Add.
> 9. Set the ZoneBy radio button to iSCSI IP Address/Subnet.
> 10. Set the IP Address/Mask field to the IP Address for Host 2 iSCSI initiator (10.15.1.11) and click Add.
> 13. Create a zone set in VSAN 2 and activate it.
> 1. In Cisco DCNM-SAN, choose Zones > Edit Local Full Zone Database.
> 2. Select VSAN 2 from the VSAN drop-down menu in the Edit Local Full Zone Database dialog box.
> 3. Select the Zoneset folder in the left navigation pane and click Insert.
> 4. Set the Zoneset Name to zonset-iscsi-2 and click OK.
> 5. Click on the zoneset-iscsi-2 folder and click Insert.
> 6. Set the Zone Name field to iscsi-zone-2 and click OK.
> 7. Click Activate to activate the new zone set.
> 8. Click Continue Activation to finish the activation.
> 14. Start the iSCSI clients on both hosts.
> 15. Show all the iSCSI sessions.
> 1. In Device Manager, choose Interface > Monitor > Ethernet and select the iSCSI connections tab to show all the iSCSI sessions.
> 2. In Device Manager, choose IP > iSCSI and select the Session Initiators tab.
> 3. Click Details.
> 16. In Cisco DCNM- SAN, choose End Devices > iSCSI in the Physical Attributes pane to verify the details of the two iSCSI initiators.
> 17. In Cisco DCNM-SAN, choose Zones > E dit Local Full Zone Database to view the active zone set. The iSCSI initiators' FC IDs are resolved.

> 18. In Device Manager, choose FC > Name Server. The Fibre Channel name server shows the virtual N ports created for the iSCSI hosts.
> 19. In Device Manager, Choose FC > Name Server.
> 20. Click the Advanced tab. Verify the detailed output of the iSCSI initiator nodes in the Fibre Channel name server.

> Copyright 2010-2013, Cisco Systems, Inc. All rights reserved.