Chapters 13 - 14 Flashcards Preview

Mastering VMware > Chapters 13 - 14 > Flashcards

Flashcards in Chapters 13 - 14 Deck (12):

What are the questions you should ask before creating a custom alarm?

You should ask yourself several questions before you create a custom alarm:

Does an existing alarm meet my needs?

What is the proper scope for this alarm? Do I need to create it at the datacenter level so that it affects all objects of a particular type within the datacenter or at some lower point?

What are the values this alarm needs to use?

What actions, if any, should this alarm take when it is triggered? Does
it need to send an email or trigger an SNMP trap?


You find yourself using the Chart Options link in the Advanced layout of the Performance tab to set up the same chart over and over again. Is there a way to save yourself some time and effort so that you don’t have
to keep re-creating the custom chart?

Yes. After using the Chart Options dialog box to configure the performance chart to show the desired counters, use the Save ChartSettings button to save these settings for future use. The next time you need to access these same settings, they will be available from the Switch To drop-down list on the Advanced view of the Performance tab.


Explain how to run resxtop from the VMware vMA command line.

Enter the command vm-support -p -i 10 -d 180. This creates a resxtop snapshot, capturing data every 10 seconds, for the duration of 180 seconds.


A junior vSphere administrator is trying to resolve a performance problem with a VM. You’ve asked this administrator to see if it is a CPU problem, and the junior administrator keeps telling you that the
VM needs more CPU capacity because the CPU utilization is high within
the VM. Is the junior administrator correct, based on the information available to you?

Based on the available information, not necessarily. A VM may be using all of the cycles being given to it, but because the overall ESXi
host is CPU constrained, the VM isn’t getting enough cycles to perform acceptably. In this case, adding CPU capacity to the VM wouldn’t necessarily fix the problem. If the host is indeed constrained, migrating VMs to other hosts or changing the shares or the CPU limits for the VMs
on this host may help alleviate the problem.


VMware offers a number of automation tools. What are some guidelines for choosing which automation tool to use?

Two primary factors should dictate which tool you choose: your prior experience and the task you wish to complete. If you have experience with creating scripts using Perl, then you will likely be most effective in
using the vSphere SDK for Perl to create automation tools. Similarly, having prior experience or knowledge of PowerShell will mean you will
likely be most effective using PowerCLI. Recall that the most common tool used is PowerCLI because it is easy to adopt by administrators from the widest range of backgrounds. If you’re looking for end-to-end process automation, then vRealize Orchestrator is your tool.


If you are familiar with other scripting languages, what would be the biggest hurdle in learning to use PowerShell and PowerCLI, other
than syntax?

Everything in PowerShell and PowerCLI is object based. Thus, when a command outputs results, those results are objects. This means
you have to be careful to properly match object types between the output
of one command and the input of the next command.


ave you migrated management and configuration operations for which you currently use the ESXi command-line interface to vMA?

Migrating to vMA and the vCLI is extremely simple and can be done quickly using vMA’s fastpass technology. Once a host has been
configured for fastpass, you can execute the same scripts that were previously used by setting the fastpass target to transparently pass the
commands to the host.


Use a combination of shell scripting with vCLI commands to execute commands against a number of hosts.

Bash, the default shell for the vi-admin user, has a full-featured scripting environment capable of using functions, arrays, loops, and other control logic structures. By using these capabilities, in combination with the vCLI command set and fastpass, you can efficiently configure hosts in
clusters to match.


Browse the sample scripts and SDK documentation to discover the world of possibilities that are unlocked by using Perl, or any of the other supported languages, to accomplish management tasks.

Sample scripts are provided with the Perl toolkit on vMA at
/usr/share/doc/vmware-viperl/samples. You can find additional utility scripts that help with developing Perl applications at /usr/lib/vmwareviperl/apps in the vMA’s file structure. Refer to the documentation for their location when you install the Perl toolkit on a Windows server or desktop.


How can you tell which plug-ins are installed and available for your use?

The Plug-Ins tab of the vRealize Orchestrator Configuration page will list all of the plug-ins installed for vCenter Server. This requires the vRealize Orchestrator Configuration Service to be running. It can be accessed through your web browser at https://:8283.


An administrator in your environment configured vRealize Orchestrator and has now asked you to run a few workflows. However, when you log into the vCenter Server instance where vRealize Orchestrator
is also installed, you don’t see the icons for vRealize Orchestrator. Why?

The vCenter Server installer creates the vRealize Orchestrator Start menu icons in the user-specific side of the Start menu, so they are visible only to the user who was logged on when vCenter Server was
installed. Other users will not see the icons on the Start menu unless they are moved to the All Users portion of the Start menu.


You have several vRealize Orchestrator workflows that you want to allow other administrators and application owners to use. You don’t want to give them another tool that they have to learn and maintain credentials for.

Using vRealize Orchestrator workflow-to-object associations, you can assign a workflow to a vCenter object, such as a VM. Assign
workflow associations in the vSphere Web Client with tasks that you wish for other administrators and application owners to perform themselves directly from the vSphere Web Client.