210-015 VCE Vblock System Deployment and Implementation – Virtualization Questions and Answers

The time required to restore a failed path on a heavily loaded system is less than the time required on a lightly loaded system.

After the path has been repaired, PowerPathVE will automatically restore the path and resume IO down the path.

The only way to restore a failed path is with the rpowermt restore CLI command.

The periodic testing of live and dead paths is low priority for PowerPathVE.

In vCenter, Click the File Export Export System Logs, select the desired host, select the components and performance data, browse to the download location, and select Finish to complete.

From the console session, run the vm-support -f -w vmfsvolumesDATASTORE_NAME command.

Launch a streaming SSH session using the ssh root@ESXHostnameOrIPAddress vm-support -s vm-support-Hostname.tgz command.

Use the vSphere Web Client and connect to the host using httpsusernamevCenterFQDNcgi-binvm-support.cgi.

esxtop

esxcfg-info

vmkfstools

vm-support

Verify that the targets in the SAN boot policy match the zoning and the masking on the array.

Verify that the vHBAs are logging into the SAN fabrics by examining the Fabric Login (FLOGI) database on the Cisco MDS switches.

Verify that PowerPathVE can see all paths to the device.

Verify that the vHBAs are logging into the SAN fabrics by examining the Fabric Login (FLOGI) database on the Cisco Nexus 5000 series switches.

Use the Technical Support Mode CLI.

Use the vSphere Client.

Use Powershell.

Use the Service Console.

1. Upload new VEM code to bootflash.

2. Install new Cisco Nexus 1000V bin.

3. Verify the upgrade using the show install all status command.

1. Upload new VSM code to bootflash.

2. Install new Cisco Nexus 1000V bin.

3. Verify the upgrade using the show version command.

1. Upload the new VSM code to a USB drive.

2. Install new Cisco Nexus 1000V bin.

3. Verify the upgrade using the show install all status command.

1. Upload the new VEM code to a USB drive.

2. Install a new Cisco Nexus 1000V bin.

3. Verify the upgrade using the show version command.

Create a vmkernel interface on the ESXi host.

Create a network label to identify the connection.

Choose the NFS folder name in the format volmountsdatastore1.

Choose Network File System as the storage type.

Assign a VSAN to the vmkernel interface.

The VEM VIB in the ESXi 5.x upgrade image is not compatible with the version of the VSM.

A VEM VIB is not available in the ESXi 5.x upgrade image.

The host and the image do not contain VEM VIBs, but the host is still listed in vCenter Server as managed by Cisco Nexus 1000V.

There was a problem with determining compatibility between the VEM VIB in the ESXi 5.x upgrade image and the VSM.

Enter maintenance mode, import patches, create the baseline, attach the baseline, and remediate host.

Disconnect the ESXi host, import patches, create the baseline, attach the baseline, and remediate host.

Import patches, create the baseline, attach the baseline, and install updates.

Import patches, reboot the ESXi host, create the baseline, attach the baseline, and remediate host.

There is insufficient vSphere licensing to license the new hosts.

There is insufficient Cisco licensing to license the new hosts.

The network drivers need to be updated.

The Cisco Nexus 1000V is limited to 32 hosts.