Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
112 Cards in this Set
- Front
- Back
|
Features that rely on shared storage |
HA, DRS, Storage vMotion |
|
|
2 available file systems and where they're used |
VMFS- SAN NFS - NAS |
|
|
Another name for connected storage |
Target |
|
|
Device Identifier Types |
SCSI INQUIRY Path-Based Legacy Runtime Name |
|
|
SCSI INQUIRY Prefixes (3) |
eua naa t10 |
|
|
characteristic of SCIS INQUIRY |
Persistent and Unique |
|
|
When is Path-based identifier created? |
When SCSI INQUIRY does not return an identifier |
|
|
Path-based identifier prefix & Format |
mpx.vmhba:C:T:L (:partition#) |
|
|
characteristic of path-based identifier |
Not persistent or unique |
|
|
Legacy identifier prefix/Format |
vml.(:) |
|
|
what is Runtime Identifier? |
Identifier used to identify the name of the first path to device |
|
|
characteristic of Runtime Name |
Not reliable or persistent |
|
|
Format of runtime identifier |
vmhba:C(controller#):T(target#):L(LUN #)
Remember (CTL) |
|
|
Reasons manual rescan is needed (6) |
* New Disk array is zoned on a SAN
* New device (LUN) created on a SAN * path masking on a host is changed * a cable is reconnected * CHAP settings modified (iSCSI) * Static or dynamic address modified (iSCSI) |
|
|
3 rescan options |
* All storage adapters in single ESXi host
* Single storage adapter * All adapters in multiple hosts |
|
|
What are storage filters used for? |
Prevent corruption and storage issues created by unsupported use of storage devices |
|
|
What are the storage filters and keys? |
VMFS : vmfsFilter RDM: rdmFilter Same Hosts and Transports: SameHostsAndTransportsFilter Host Rescan: hostRescanFilter
All start with config.vpxd.filter. |
|
|
Use of VMFS filter |
Filters out devices aleady in use as VMFS datastores |
|
|
Use of RDM Filter |
Filters out devices already in use as RDM filters |
|
|
Use of Same Host and Transports Filter (examples?) |
Filters out devices that have some sort of incompatibility (i.e adding an extent when the device is not exposed to all hosts, or adding an FC extent to a VMFS datastore on local storage) |
|
|
Use of Host Rescan Filter |
Automatically rescans for VMFS datastores after datastore management operations are performed. |
|
|
Best practice with storage filters |
Consult VMware support before changing. |
|
|
How do disable Storage filters after creation. Why? |
Set to False (Cannot be deleted) |
|
|
ESXi behavior when new device presented, regardless of hostRescanFilter setting? |
Will scan automatically |
|
|
What is zoning |
Used at switch level in FC sans to define which HBAs can connect to which controllers |
|
|
2 types of zoning |
single-initiatior and single-initiator-single-target |
|
|
What is LUN Masking? Where performed? |
Makes LUNs hidden from certain hosts. Done at host or target. |
|
|
what does an iSCSI initiator do? |
Encapsulates SCSI commands into Ethernet Packets |
|
|
3 types of iSCSI initiators. What they offload from host? |
Software - Nothing Dependent Hardware - iSCSI but not networking Independent Hardware - iSCSI and networking
|
|
|
Bonus of dependent hardware iSCSI adapter? |
Can be used as regular NIC |
|
|
How software iSCIS initiator added/removed in ESXi |
Enable/Disable |
|
|
Extra step to disable iSCSI initiatior |
reboot host |
|
|
what is iSCSI port binding? |
process of associating an iSCSI software/dependent hardware adapter with a VMkernel adapter |
|
|
What do software/dependent Hardware iSCSI adapter need before port binding? |
VMkernel connection type to be established. |
|
|
Where is CHAP supported in ESXi? |
adapter level |
|
|
2 CHAP methods supported in ESXi 5.5? |
Unidirectional and Bidirectonal CHAP (AKA mutual CHAP) |
|
|
What does authentication in unidirectional CHAP? |
The target (storage system) |
|
|
5 CHAP security Levels |
* None
* use unidiectional if required by target * Use unidirectional unless prohibited by target * use unidirectional * use bidirectional |
|
|
2 security levels not supported by independent hardware adapter |
* use unidirectional if required by target
* bidirectional |
|
|
Hardware/Software Adapters and CHAP apply to which storage tech? |
iSCSI technologies
|
|
|
Requirement for booting from iSCSI/FC LUN |
iSCSI HBA, NIC with specialized firmware (iSCSI), or FC HBA |
|
|
What versions of ESXi can boot from FCoE? |
5.1 and later |
|
|
Requirements for booting from FCoE? |
Adapter must support partial FCoE offload (Software FCoe) and must contain either FCoE Boot Firmware TAble (FBFT) or an FCoE Boot Parameter Table (FBPT) |
|
|
What NIC must support to boot from iSCSI |
iSCSI Boot Firmware Table (iBFT) |
|
|
what is iBFT? |
iSCSI Boot Firmware Table - Used to communicate info about iSCSI boot device to an OS for booting from iSCSI |
|
|
what kind of partition needed to boot from iSCSI or FC? |
diagnostic partition |
|
|
Network recommendations when booting from iSCSI (2) |
Static IPs Avoid Routing if possible |
|
|
FC configuration to complete before boot from SAN |
Masking and zoning |
|
|
What kind of path needed to boot from SAN? Why? |
First path must be available. Multipathing at first boot not supported. |
|
|
BIOS options needed for boot from SAN (2), and which kinds of devices needed on |
Boot from SAN enabled SAN before optical media
Needed for software or dependent hardware |
|
|
Steps to configure boot from san |
Check HCL Configure storage system Configure BIOS (software/dependent hardware) Configure Network card Install ESXi on boot LUN |
|
|
What kind of file system if VMFS |
Clustered File System |
|
|
How are VMs stored in VMFS |
Encapsulated in directoreis |
|
|
How does VMFS simplify administration? |
Storage admin creates pool of storage for Virtualization admin to use |
|
|
File system used for RDMs |
VMFS |
|
|
Block size in VMFS-5 vs previous |
1 MB vs 1, 2, 4, and 8 MB |
|
|
VMFS max file sizes (in which versions?). What determines file size? |
2TB-512 bytes in 5.0 and 5.1 62 TB in 5.5
Determined by ESXi host version (not VMFS version) |
|
|
RDM max file size (physical vs virtual compatibility mode) |
Physical compatibility mode: 64 TB Virtual: 2TB-512 bytes in 5.0 and 5.1/62 TB in 5.5 |
|
|
sub block size in VMFS-5 vs previous versions. Advantage of this? |
8 KB vs 64 KB. Files between 1 and 8 TB take up less space |
|
|
What is Small File support used for? |
Files < 1 KB in size |
|
|
Where is descriptor for small files stored (vs larger files?). What happens if file grows beyond 1 KB? |
Kept in VMFS metadata instead of file blocks. If file grows over 1 KB, file will start using 8 KB blocks |
|
|
What is ATS? |
Atomic Test and Set - used for file locking on storage devices that support hardware acceleration |
|
|
Best practice for relationship between VMFS datastore and LUN? |
one-to-one |
|
|
What does unmounting vs deleting a VMFS datastore do? |
Unmount leaves data intact and available to other hosts. Deleting will destroy it and remove from all hosts |
|
|
What cannot be on a datastore that is to be unmounted (3) |
* No VMs and Templates
* ISOs connected to VMs * Mapping files for RDMs |
|
|
What cannot be running/Enabled on a datastore that is to be unmounted? (5) |
* Datastore cluster
* Storage DRS * Storage I/O * HA Heartbeat * Any operations that would result in I/O during unmount |
|
|
What additional feature could cause unmount of VMFS volume to fail? |
Snapshots |
|
|
command to see SCSI INQUIRY identifiers for detached storage |
esxcli storage core device detached list |
|
|
command to permanently remove detached VMFS device |
esxcli storage core device detached remove -d |
|
|
2 options to increase VMFS datastore sizes (AKAs for both?) |
Add/Extend - Coupled with another device Grow/Expand - Size of existing datastore is increased in sizse |
|
|
prerequisite for growing extent? |
Supporting device must have already been expanded |
|
|
Final step to grow extent? |
rescan storage |
|
|
recommendation before upgrading VMFS datastore |
Backup all VMs |
|
|
How to reverse VMFS-3 to VMFS-5 upgrade? |
Can't be done |
|
|
What will happen to pre-5 ESXi host if VMFS datastore upgraded from version 3 to 5? |
Will lose connectivity to the datastore |
|
|
What to do with snapshots before VMFS upgrade? |
commit them |
|
|
What will happen if there are partitions that ESXi host does not recognize during VMFS 3 to 5 upgrade? How to prevent? |
Upgrade will fail. Remove partitions to prevent |
|
|
Old vs new Partition types |
Old: Master Boot Record (MBR) New: GUID Partition Table (GPT) |
|
|
Partition location of VMFS-3 (and upgraded) vs VMFS 5 |
sector 128 vs 2048 |
|
|
What is multipathing? |
Provides multiple paths to storage device for performance and fault tolerance |
|
|
What is PSA? |
Pluggable Storage Architecture- VMkernel APIs for multipathing |
|
|
What is an MPP |
Multipathing Plug in - responsible for claiming and managing multipathing for a device |
|
|
What is used to determine what MPP to use? |
claim rules |
|
|
What is NMP? |
Native Multipathing Plugin - VMware's MPP that provides multipathing by default. |
|
|
What are 2 components of NMP? |
Storage array Type Plugin (SATP) Path Selection Plugin (PSP) |
|
|
What is SATP? |
Storrage Array Type Plugin - Performs array-specific functions in a failover situation, monitoring health and reporting changes of each physical path |
|
|
What is PSP |
Path Selection Plugin - Deals with Path selection for a given device |
|
|
How is PSP chosen |
Based on information in SATP |
|
|
What are 3 types of PSPs? |
VMW_PSP_FIXED VMW_PSP_MRU VMW_PSP_RR |
|
|
PSP typically used by active-active arrays |
VMW_PSP_FIXED |
|
|
PSP typically used by active-passive arrays |
VMW_PSP_MRU |
|
|
How active-active and active-passive arrays use round robin? |
active-active: rotates through all available paths active-passive: rotates through all active paths |
|
|
How NMP PSPs show up in web client> |
(VMware) |
|
|
What to do with paths that might be affected by maintenance? |
Disable them |
|
|
When will path selection settings generally need to be changed and what to do if it does? |
Typically will not. Consult with storage Vendor or VMware if it does |
|
|
What is built into ESXi to use NFS storage? |
NFS Client |
|
|
What version of NFS is supported? |
NFS 3 over TCP |
|
|
What must be done before using NFS? |
File system must be created on NAS and exported |
|
|
What must be done for ESXi to access NFS server |
ESXi must have read-write access Read-write access must be allowed for root system account |
|
|
Networking requirement for NFS |
VMkernel networking over standard physical NIC |
|
|
How to use multiple NICS with NFS? |
Make sure all virtual/Physical switches are configured correctly |
|
|
Where to get specifics and bet practices for NFS device? |
Consult with vendor |
|
|
Difference in adding VMFS and NFS storage |
NFS must be added to each host |
|
|
What will happen if NFS server and file names not entered exactly the same in add storage wizard on different hosts? |
Will see NFS mounts as different devices |
|
|
Difference in how VMFS and NFS datastores are viewed when unmounted |
VMFS: shows inactive NFS: removed from views |
|
|
What happens to block size on datastore upgraded from VMFS-3 to VMFS-5 |
Keeps previous block size |
|
|
What happens to sub-block size on datastore upgraded from VMFS-3 to VMFS-5 |
Keeps 64-KB block size, cannot use new 8 KB sub-blocks |
|
|
What happens to file limit on datastore upgraded from VMFS-3 to VMFS-5 |
Keeps limit of 30,720 files |
|
|
What happens to MBR on datastore upgraded from VMFS-3 to VMFS-5 |
Will still use MBR until grows beyond 2 TB, then will switch to GBT |
|
|
What happens to partition location on datastore upgraded from VMFS-3 to VMFS-5 |
Will continue to have partition start at sector 128 |
|
|
What will change on upgraded VMFS 5 datastore? (4) |
* Can use 1KB small-files Feature
* Can be grown to 64 TB * Can use VAAI ATS improvements
|
|
|
What happens to maximum volume size on datastore upgraded from VMFS-3 to VMFS-5 |
Increases to 64 TB |
