You have executed the following FC configuration workflow:

1.

Verify IMT supported configuration.

2.

Install VSC for VMware vSphere on a Windows Server.

3.

Add the storage cluster to VSC and set recommended values.

4.

Update host HBA firmware and BIOS.

5.

Provision the LUN.

6.

Manually create an igroup and add the host WWPNs into it.

7.

Map the LUN to the igroup.

8.

Create datastore and its containing LUNS and volumes.

In step 8, you are not able to see the LUNs you provisioned on your storage controller. When you run

igroup showyou see the ESX host's initiators; however, they are listed "not logged in".

What is the problem?

A. You need to configure ALUA.

B. The LUN was not put online.

C. The LUN type is not set to type VMware.

D. You need to configure zoning.

Which information-gathering command should you use to gather logs for troubleshooting switch information for your Brocade switches?

A. cfgshow

B. fabricshow

C. configshow

D. supportsave

You are troubleshooting a node that had a core dump. The HA partner took over and you successfully performed a giveback. You need to get access to the core files.

Which two locations will give you access? (Choose two.)

A. /mroot/etc/crash

B. https:///spi/

C. https://

D. /mroot/etc/log

Exhibit

You currently have the following configuration on your cluster:

cl01::>igroup show -instance Vserver Name: svm1 Igroup Name: ig2 Protocol: mixed OS Type: linux Portset Binding Igroup: -Igroup UUID: 3fb136c7-cfd6-11df-a9ab-123478563412

Initiators:

What must you do to limit the LIFs that are used by an initiator to access a LUN?

A. Create a portset.

B. Create an additional igroup.

C. Change the protocol to iSCSI.

D. Change the OS type to windows_gpt.

A customer has recently deployed a clustered Data ONTAP 8.3 system and is trying to mount LUNs to a Windows 2012 Server using the iSCSI protocol. They are using Cisco Nexus 5548 network switches and the network administrator has informed the storage administrator that the ports are set to switchport mode trunk. The storage administrator has also been informed that the host and storage should be using VLAN 400 for iSCSI traffic. When the storage administrator attempts to add the SVM as an iSCSI target, it fails to connect.

What is causing the problem?

A. The storage administrator has not enabled VLAN tagging on the storage ports.

B. Clustered Data ONTAP 8.3 does not support the iSCSI protocol on a VLAN tagged interface.

C. Windows 2012 Server does not support the iSCSI protocol on a VLAN tagged interface.

D. Clustered Data ONTAP 8.3 does not support running iSCSI on a VLAN ID below 1024.