2,187
edits
Difference between revisions of "VCP4"
Jump to navigation
Jump to search
Added VCP cat and Meta
m (→Configure vNetwork Distributed Switches: Added traffic shaping) |
(Added VCP cat and Meta) |
||
| (16 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
* [http://communities.vmware.com/community/vmtn/certedu/certification/vcp VMware VCP Forum] | * [http://communities.vmware.com/community/vmtn/certedu/certification/vcp VMware VCP Forum] | ||
* [http://mylearn.vmware.com/lcms/mL_faq/2726/VMware%20Certified%20Professional%20on%20vSphere%204%20Blueprint%208.13.09.pdf VCP4 Blueprint] | * [http://mylearn.vmware.com/lcms/mL_faq/2726/VMware%20Certified%20Professional%20on%20vSphere%204%20Blueprint%208.13.09.pdf VCP4 Blueprint] | ||
* VMware vSphere Documentation: [http://www.vmware.com/support/pubs/vs_pages/vsp_pubs_esx40_vc40.html PDF] [http://pubs.vmware.com/vsp40 HTML] | * VMware vSphere Documentation: [http://www.vmware.com/support/pubs/vs_pages/vsp_pubs_esx40_vc40.html PDF] [http://pubs.vmware.com/vsp40 HTML] (HTML version is good for searching) | ||
* [http://thinkvirtually.co.uk/#/overview/4535842936 Scott Vessey] | |||
* [http://www.simonlong.co.uk/blog/vcp-vsphere-upgrade-study-notes/ Simon Long blog] | * [http://www.simonlong.co.uk/blog/vcp-vsphere-upgrade-study-notes/ Simon Long blog] | ||
| Line 41: | Line 42: | ||
|- | |- | ||
| || <code> vmkcore </code> || 1.25GB || Core debugging dumps | | || <code> vmkcore </code> || 1.25GB || Core debugging dumps | ||
|} | |||
'''Optional Partitions''' | |||
{|cellpadding="4" cellspacing="0" border="1" | |||
|- style="background-color:#bbddff;" | |||
! Mount !! Type !! Size !! Description | |||
|- | |||
| <code>/home</code> || ext3 || 512MB || ESX user accounts | |||
|- | |||
| <code>/tmp</code> || ext3 || 1024MB || Temp files! | |||
|- | |||
| <code>/usr </code> || ext3 || || User programs and data (3rd party apps) | |||
|- | |||
|<code>/var/log</code>|| ext3 || 2000MB || Log files | |||
|- | |||
|} | |} | ||
| Line 55: | Line 72: | ||
| Standard || Essentials + HA | | Standard || Essentials + HA | ||
|- | |- | ||
| Advanced || Standard + 12 cores/CPU, Hot Add, FT, vShield | | Advanced || Standard + 12 cores/CPU, Hot Add, FT, VMotion, vShield, Data Recovery | ||
|- | |- | ||
| Enterprise || Advanced + 6 cores/CPU, Storage vMotion, Data Recovery, DRS | | Enterprise || Advanced + 6 cores/CPU, Storage vMotion, Data Recovery, DRS | ||
|- | |- | ||
| Enterprise Plus || 12 cores/CPU, 8way vSMP, | | Enterprise Plus || 12 cores/CPU, 8way vSMP, 1TB/ESX, vNetwork Distributed Switch, Host Profiles, 3rd Party Multipathing | ||
|- | |- | ||
| vCentre Foundation || Fully featured, but limited to managing 3 ESX's | | vCentre Foundation || Fully featured, but limited to managing 3 ESX's | ||
| Line 186: | Line 203: | ||
* VLAN - Traditional single VLAN assignment to a port group | * VLAN - Traditional single VLAN assignment to a port group | ||
* VLAN Trunking - Multiple VLAN's can be assigned to a dv Port Group | * VLAN Trunking - Multiple VLAN's can be assigned to a dv Port Group | ||
* Private VLAN - Allows Private VLANs ( | * Private VLAN - Allows Private VLANs | ||
** VLANs over a VLAN, the VLAN equivalent of subnetting. Hosts on differing subVLANs may be in same IP range, but need to go via router to communicate. | |||
** Primary (promiscuous) VLAN uplinks to rest of network | |||
** Ssee http://blog.internetworkexpert.com/2008/07/14/private-vlans-revisited/ | |||
'''Traffic Shaping''' | '''Traffic Shaping''' | ||
| Line 205: | Line 225: | ||
* '''Name''' - A ''friendly'' name based on storage type and manufacturer. User changeable, kept consistent across ESX's | * '''Name''' - A ''friendly'' name based on storage type and manufacturer. User changeable, kept consistent across ESX's | ||
* '''Identifier''' - Globally unique, human unintelligible. Persistent through reboot and consistent across ESX's | * '''Identifier''' - Globally unique, human unintelligible. Persistent through reboot and consistent across ESX's | ||
* '''Runtime Name''' - The first path to a device, created by host and | * '''Runtime Name''' - The first path to a device, created by host and not persistent. Of format '''<code>vmhba#:C#:T#:L#''' </code> | ||
** vmhba - Storage Adapter number | ** vmhba - Storage Adapter number | ||
** C - Storage Channel number (software iSCSI uses this to represent multiple paths to same target) | ** C - Storage Channel number (software iSCSI uses this to represent multiple paths to same target) | ||
** T - Target | ** T - Target | ||
** L - LUN (provided by storage system; if only 1 LUN its always L0) | ** L - LUN (provided by storage system; if only 1 LUN its always L0) | ||
'''PSA - Pluggable Storage Architecture''' | '''PSA - Pluggable Storage Architecture''' | ||
| Line 218: | Line 239: | ||
** Path Selection Plugin (PSP) - default assigned by NMP based on the SATP | ** Path Selection Plugin (PSP) - default assigned by NMP based on the SATP | ||
* Multipathing Plugin (MPP) - 3rd party, can run alongside or in addition to Native Multipathing Plugin, | * Multipathing Plugin (MPP) - 3rd party, can run alongside or in addition to Native Multipathing Plugin, | ||
'''PSA operations''' | '''PSA operations''' | ||
| Line 228: | Line 250: | ||
* Handles physical path discovery and removal | * Handles physical path discovery and removal | ||
* Provides logical device and physical path I/O stats | * Provides logical device and physical path I/O stats | ||
'''MPP / NMP operations''' | '''MPP / NMP operations''' | ||
| Line 237: | Line 260: | ||
** Depending on storage device, perform specific actions necessary to handle path failures and I/O cmd retries | ** Depending on storage device, perform specific actions necessary to handle path failures and I/O cmd retries | ||
* Support management tasks, EG abort or reset of logical devices | * Support management tasks, EG abort or reset of logical devices | ||
'''PSP types''' | '''PSP types''' | ||
Default (VMware) PSP Types (3rd party PSP's can be installed)... | Default (VMware) PSP Types (3rd party PSP's can be installed)... | ||
* '''Most Recently Used''' - Good for either Active/Active or Active/Passive | * '''Most Recently Used''' - Good for either Active/Active or Active/Passive | ||
* '''Fixed''' - Can cause path thrashing when used with Active/Passive | * '''Fixed''' - Can cause path thrashing when used with Active/Passive | ||
* '''Round Robin''' - Load balanced | * '''Round Robin''' - Load balanced | ||
'''PSA Claim Rules''' | '''PSA Claim Rules''' | ||
* Used to define paths should be used by a particular plugin module | * Used to define paths should be used by a particular plugin module | ||
'''LUN Masking''' | '''LUN Masking''' | ||
| Line 255: | Line 282: | ||
'''CHAP Authentication''' | '''CHAP Authentication''' | ||
* '''One-way CHAP''' - Unidirectional, iSCSI target authenticates the initiator (ESX) only | * '''One-way CHAP''' - Unidirectional, iSCSI target authenticates the initiator (ESX) only | ||
* '''Mutual CHAP''' - Bidirectional, ESX also authenticates the iSCSI target (''Software iSCSI only'') | * '''Mutual CHAP''' - Bidirectional, ESX also authenticates the iSCSI target (''Software iSCSI only'') | ||
'''Multipathing (software iSCSI)''' | |||
# Set-up a vSwitch with two VMkernel ports and two uplinks | |||
# For each VMkernel port, edit ''NIC Teaming'' | ''Override vSwitch failover order'' to bind one uplink each | |||
# Connect the iSCSI initiator to each VMkernel port | |||
#* <code> esxcli swiscsi nic add -n <vmk_port_name> -d <vmhba_no> </code> | |||
== Configure NFS Datastores == | == Configure NFS Datastores == | ||
* ESX supports NFS v3 on TCP ''only'' | |||
* ESX's manage exclusive access to files via <code> .lc-XXX </code> lock files | * ESX's manage exclusive access to files via <code> .lc-XXX </code> lock files | ||
* To use jumbo frames, enable on the vSwitch and the VMkernel port(s) | |||
** Frames up to 9kB are supported | |||
== Configure and Manage VMFS Datastores == | == Configure and Manage VMFS Datastores == | ||
| Line 318: | Line 353: | ||
* (Win) Sysprep must be installed on VC | * (Win) Sysprep must be installed on VC | ||
* (Linux) Guest OS must have Perl installed | * (Linux) Guest OS must have Perl installed | ||
'''vCenter Maps''' | |||
* Provide an overview of relationships for | |||
** Host Resources | |||
** VM Resources | |||
** Datastore Resources | |||
== Configure Access Control == | == Configure Access Control == | ||
| Line 370: | Line 411: | ||
** Only VM h/ware v7 with Win2k3, Win2k8 or Red Hat Ent v5 | ** Only VM h/ware v7 with Win2k3, Win2k8 or Red Hat Ent v5 | ||
** Not supported with | ** Not supported with | ||
*** Record/replay | *** Record/replay | ||
*** Fault Tolerance | *** Fault Tolerance | ||
*** MSCS Clustering (so also SQL clusters) | *** MSCS Clustering (so also SQL clusters) | ||
*** ''[Boot disks - not an issue since ESX4.0 Update 1]'' | |||
| Line 381: | Line 422: | ||
* ESX's HBA's must support NPIV | * ESX's HBA's must support NPIV | ||
* NPIV enabled VM's are assigned 4 NPIV WWN's | * NPIV enabled VM's are assigned 4 NPIV WWN's | ||
* Storage vMotion is not supported | |||
| Line 426: | Line 468: | ||
'''Guided Consolidation''' | '''Guided Consolidation''' | ||
* Active Domains - Systems being analysed need to be a member of an active domain | * Active Domains - Systems being analysed need to be a member of an active domain | ||
* Add to Analysis to analyse new systems, max 100 concurrent | * Add to Analysis to analyse new systems, max 100 concurrent, can take 1hr for new analysis to start | ||
* Confidence - Degree to which VC collected perf data, and how good a candidate | * Confidence - Degree to which VC collected perf data, and how good a candidate | ||
** High confidence is shown after 24 hrs, if workload varies over greater interval, further analysis is required | ** High confidence is shown after 24 hrs, if workload varies over greater interval, further analysis is required | ||
| Line 476: | Line 518: | ||
== Establish and Apply ESX Host Profiles == | == Establish and Apply ESX Host Profiles == | ||
* ESX 4 supported only | |||
* Used to ensure consistent configuration across ESX's | * Used to ensure consistent configuration across ESX's | ||
* Create a profile from a reference ESX, then apply to Cluster or ESX | * Create a profile from a reference ESX, then apply to Cluster or ESX | ||
| Line 548: | Line 591: | ||
# Turn on FT for appropriate VM's | # Turn on FT for appropriate VM's | ||
'''Not Protected''' caused by... | '''Not Protected''' caused by Secondary VM not running, because... | ||
* VM's are still starting up | * VM's are still starting up | ||
* Secondary VM | * Secondary VM cannot start, possible causes... | ||
** No suitable host on which start secondary | ** No suitable host on which start secondary | ||
** A fail-over has occurred but FT network link down, so new secondary not started | ** A fail-over has occurred but FT network link down, so new secondary not started | ||
| Line 584: | Line 627: | ||
* Max 8 VM backups can run concurrently | * Max 8 VM backups can run concurrently | ||
* Max 2 backup destinations used concurrently | * Max 2 backup destinations used concurrently | ||
* Max 100 VM's per back appliance | * Max 100 VM's per back up appliance | ||
* Backup's won't start if ESX CPU usage >90% | |||
'''VMware Data Recovery Setup''' | '''VMware Data Recovery Setup''' | ||
| Line 628: | Line 672: | ||
[[Category:VMware]] | [[Category:VMware]] | ||
[[Category:VCP]] | |||