Active Directory (AD) - CMD to List the members in a AD Group

They are lot of commands to get to List the members in a AD Group. below step will work any workstation no matter what.

1. From Command Prompt
run the below cmd
>>Rundll32 dsquery.dll OpenQueryWindow
New window will open
enter the group name and click on 'find now'
below in the search result tab, you will see the Group Name, click on it.
new window will open with list of members :)


Other Commands:
>> net Group <AD-GroupName>
>> dsquery group -name <AD-GroupName> | dsget group -members -expand



Isilon Useful Commands


#####cmd to view the isilon Node hardware Serial Number
ISILON001-2#isi_for_array -s 'isi_hw_status | grep -i serno'
XXXXX001-1: SerNo: JXXXXX6120XXXX
XXXXX001-2: SerNo: JXXXXX6050XXXX

#####Check the time on isilon cluster
IsilonCluster1-2# date
Fri Aug 10 15:01:05 PDT 2018

#####Check the NTP Settings
IsilonCluster1-2# isi ntp servers list
Name          Key
------------------
10.xxx.xxx.xxx -
10.xxx.xxx.xxx -
10.xxx.xxx.xxx -
10.xxx.xxx.xxx -
------------------
Total: 4

#####cmd to view the isilon Node hardware details
isi_for_array -s 'isi_hw_status | grep -i product'
XXXXX001-1: Product: NL410-4U-Single-48GB-2x1GE-2x10GE SFP+-140TB-800GB SSD
XXXXX001-2: Product: NL410-4U-Single-48GB-2x1GE-2x10GE SFP+-140TB-800GB SSD

#####CLI command to show which nodes the worker/threads are using (Lnn=logical node number)
ISILON001-2# isi sync jobs reports view JobName_XX
Policy Name: 
JobName_XX
....
Worker ID: 0
Lnn: 1
....
Worker ID: 2
Lnn: 2


#####To view the boot drive wear life
IsilonCluster1-2#isi event events list | grep -i wear

#####View types of Jobs
IsilonCluster1-2# isi snapshot schedule list
ID   Name
------------------------------------
1    Tier-X
2    Tier-NL
3    OnBaseprdcopy_163099212
4    MHC_Infra_FileShare_Development
7    obdg$_Snapshot
8    obdg2$_Snapshot
9    obdg3$_Snapshot
10   obdg4$_Snapshot
11   obdg5$_Snapshot
12   obdg6$_Snapshot
13   obdg7$_Snapshot
14   obdg8$_Snapshot
15   obdg9$_Snapshot
16   obdiskgroups$_Snapshot
17   shc_Snapshot
18   uha-uswired_Snapshot
19   e-fax_Snapshot
20   Rad-Fax_Snapshot
21   RTA$_Snapshot
22   ProdClientFiles$_Snapshot
23   Processing_Snapshot
24   LabFaxes_Snapshot
25   ImageNet$_Snapshot
26   HimsRoiArchive_Snapshot
27   Billing-Healthlogic_Snapshot
28   EPIC_nonprod_Snapshot
29   EPIC_prod_Snapshot
30   msp_nfs_oracle
31   msp_ora_silver
32   longterm_cifs_msp_sql
33   longterm_cifs_stc_sql
34   MHC_Prod
------------------------------------

#####View Current Running Jobs
IsilonCluster1-1# isi job list
ID    Type           State   Impact  Pri  Phase  Running Time
--------------------------------------------------------------
16451 SnapshotDelete Running Medium  2    2/2    2m 46s
--------------------------------------------------------------
Total: 1

#####Delete a Snap
IsilonCluster1-1# isi snapshot snapshots delete --snapshot=<SnapShotName>
Are you sure? (yes/[no]): yes

#####Manually initiate the snapsnop clean up job
IsilonCluster1-1# isi job jobs start snapshotdelete
Started job [16451]

#####List all snapshots
IsilonCluster1-1# isi snapshot list

#####List all Shares
IsilonCluster1-1# isi smb shares list

#####Disable the FSA Snapshot Settings
IsilonCluster1-2# isi_gconfig -t job-config jobs.fsa.snap_based_mode
jobs.fsa.snap_based_mode (bool) = true

#####List the FSAnalyze Schedule
IsilonCluster1-2# isi_classic job schedule list --verbose | grep FSAnalyze
FSAnalyze       every 1 weeks on friday at 10:00 PM             07/27 22:00

#####Gather Logs
isi_gather_info
Package: /ifs/data/Isilon_Support/pkg/IsilonLogs-SHISOLPFCAP001-20180717-113405.tgz

#####CMD to Check Disk Drive Status
isi_for_array -sX isi devices list

#####Check where the client is connected
IsilonCluster1-2# isi_for_array -s netstat -an | grep "xxx.xxx.xxx.xxx"

#####Cmd to Check the ware life on Boot Disk
#isi_for_array -s isi_radish -a /dev/ad* | grep -E "Percent Life" | grep -v Used | awk '{print $1 $2 $3 $4 sprintf( "%d","0x"$9 )}'
IsilonCluster1-6:PercentLifeRemaining:99
IsilonCluster1-6:PercentLifeRemaining:92

#####Loop through the cluster nodes and grep for non-healthy drives using#####
isi_for_array "isi devices drive list| grep -iv healthy"

#####How to check the Data Target/Stored on which nodes for Isilon file / Share.
Way1:
ISILON-Cluster1-2# isi get -D /ifs/Dir1/Dir2/ | grep -i pools
*  Disk pools:         policy n410_140tb_800gb-ssd_48gb(2) -> data target n410_140tb_800gb-ssd_48gb:6(6), metadata target n410_140tb_800gb-ssd_48gb:6(6)
*  Disk pools:         policy 2
*  Disk pools:         policy n410_140tb_800gb-ssd_48gb(2) -> data target n410_140tb_800gb-ssd_48gb:7(7), metadata target n410_140tb_800gb-ssd_48gb:7(7)
*  Disk pools:         policy 2
*  Disk pools:         policy n410_140tb_800gb-ssd_48gb(2) -> data target n410_140tb_800gb-ssd_48gb:4(4), metadata target n410_140tb_800gb-ssd_48gb:4(4)
*  Disk pools:         policy 2

Way2:
#list polices
IsilonCluster1-2# isi filepool policies list
Name                 Description                                                 State
---------------------------------------------------------------------------------------
Policy1               Keeps Short Term Storage data in X nodes per GE requirement OK
Policy2               2-                                                           OK
Policy3               -                                                           OK
---------------------------------------------------------------------------------------
Total: 3
#View the polices Settings for 'Data Storage Target'
IsilonCluster1-2# isi filepool policies view --name=<Policy1>
                              Name: Policy1
                       Description: Keeps Short Term Storage data in X nodes per GE requirement
                             State: OK
                     State Details:
                       Apply Order: 1
             File Matching Pattern: Path == /Dir1/Dir2 (begins with)
          Set Requested Protection: -
               Data Access Pattern: -
                  Enable Coalescer: -
               Data Storage Target: x410_102tb_1.6tb-ssd_128gb
                 Data SSD Strategy: metadata
           Snapshot Storage Target: x410_102tb_1.6tb-ssd_128gb
             Snapshot SSD Strategy: metadata
                        Cloud Pool: -
         Cloud Compression Enabled: -
          Cloud Encryption Enabled: -
              Cloud Data Retention: -
Cloud Incremental Backup Retention: -
       Cloud Full Backup Retention: -
               Cloud Accessibility: -
                  Cloud Read Ahead: -
            Cloud Cache Expiration: -
         Cloud Writeback Frequency: -
      Cloud Archive Snapshot Files: -

Way3:
IsilonCluster1-2# isi filepool policies list --verbose --format=list
                              Name: Policy1
                       Description: Keeps Short Term Storage data in X nodes per Policy1 requirement
                             State: OK
                     State Details:
                       Apply Order: 1
             File Matching Pattern: Path == /Dir1/Dir2 (begins with)
          Set Requested Protection: -
               Data Access Pattern: -
                  Enable Coalescer: -
               Data Storage Target: x410_102tb_1.6tb-ssd_128gb
                 Data SSD Strategy: metadata
           Snapshot Storage Target: x410_102tb_1.6tb-ssd_128gb
             Snapshot SSD Strategy: metadata
                        Cloud Pool: -
         Cloud Compression Enabled: -
          Cloud Encryption Enabled: -
              Cloud Data Retention: -
Cloud Incremental Backup Retention: -
       Cloud Full Backup Retention: -
               Cloud Accessibility: -
                  Cloud Read Ahead: -
            Cloud Cache Expiration: -
         Cloud Writeback Frequency: -

      Cloud Archive Snapshot Files: -

#####To view the performance on node 10 for particular protocol
IsilonCluster1-2# isi_for_array -n10 'isi statistics client list --protocols=smb1'
IsilonCluster1-10:   Ops     In   Out  TimeAvg  Node  Proto          Class  UserName     LocalName                          RemoteName
IsilonCluster1-10: -------------------------------------------------------------------------------------------------------------------
IsilonCluster1-10: 230.2  14.5k 14.5k    216.4    10   smb1           read   UNKNOWN 10.xxx.xxx.xxx host1.domain.org
IsilonCluster1-10: 211.4   2.9M 10.8k    161.4    10   smb1          write   UNKNOWN 10.xxx.xxx.xxx                 host2.domain.org

#####How to check Net Bios is enabled on SMB 
IsilonCluster1-2# isi smb settings  global view
    Access Based Share Enum: No
  Dot Snap Accessible Child: Yes
   Dot Snap Accessible Root: Yes
     Dot Snap Visible Child: No
      Dot Snap Visible Root: Yes
 Enable Security Signatures: No
                 Guest User: nobody
                 Ignore Eas: No
       Onefs Cpu Multiplier: 4
          Onefs Num Workers: 0
Require Security Signatures: No
           Server Side Copy: Yes
              Server String: Isilon Server
       Support Multichannel: Yes
            Support NetBIOS: No
               Support Smb2: Yes


ViPR SRM 4.2 - SolutionPack for Oracle Database - Error: Cannot locate driver 'oracle.jdbc.driver.OracleDriver' !


Error:
Testing connectivity to Oracle instance and also checking the associated grants for the user(XXXXX:XXXXX)
Click to show/hide the full result
line 22: sql: command returned with a non-zero status (status: 1) !
Cannot locate driver 'oracle.jdbc.driver.OracleDriver' !

Resolution/fix:
> login to the SRM Collector via Putty, where 'Collector-Manager - oracle-database' is installed or where 'Data collection' & 'ASM Data collection' services are installed

> change directory to below path
SRMCollector~ # cd /opt/APG/Databases/JDBC-Drivers/Default/lib

>check weather jdbc drives or located or not
SRMCollector:/opt/APG/Databases/JDBC-Drivers/Default/lib # dir | grep -i ojdbc
-rw-r--r-- 1 root root 3692096 Apr 23 05:15 ojdbc6.jar
-rw-r--r-- 1 root root 3698857 Apr 23 05:15 ojdbc7.jar
-rw-r--r-- 1 root root 4036257 Jun  6 11:17 ojdbc8.jar

<If Not like above>

>Download JDBC Drivers from oracle Website
Link: http://www.oracle.com/technetwork/database/features/jdbc/jdbc-ucp-122-3110062.html
Note: you need to have a Oracle account to download and its free to register

>download below 3 files
ojdbc6.jar
ojdbc7.jar
ojdbc8.jar

>use WinSCP or any other tool to upload the files to the SRM Collector

>once uploaded and verify then provide the privileges
SRMCollector:/opt/APG/Databases/JDBC-Drivers/Default/lib # chmod 777 ojdbc6.jar
SRMCollector:/opt/APG/Databases/JDBC-Drivers/Default/lib # chmod 777 ojdbc7.jar
SRMCollector:/opt/APG/Databases/JDBC-Drivers/Default/lib # chmod 777 ojdbc8.jar
SRMCollector:/opt/APG/Databases/JDBC-Drivers/Default/lib # dir | grep -i ojdbc
-rwxrwxrwx 1 root root 3692096 Apr 23 05:15 ojdbc6.jar
-rwxrwxrwx 1 root root 3698857 Apr 23 05:15 ojdbc7.jar
-rwxrwxrwx 1 root root 4036257 Jun  6 11:17 ojdbc8.jar

> Now restart the services
SRMCollector:/opt/APG/Databases/JDBC-Drivers/Default/lib # manage-modules.sh service restart all

> now try to Discover the Oracle Instance
!! I Guess it should work !!

or
refer below EMC Link
https://www.emc.com/techpubs/vipr/solutionpack_for_oracle_database-2.htm


Isilon Error: isi_visudo does not edit the correct sudoers configuration file


Error: isi_visudo does not edit the correct sudoers configuration file.

Issue: When issuing the command isi_visudo to add sudo privileges to a user, the command opens and edits the wrong configuration file /usr/local/etc/sudoers instead of the correct one /etc/mcp/override/sudoers. This issue affects OneFS version 8.0.0.6+, 8.0.1.2+, and 8.1.0.1+

Resolution: As a workaround, issue the following command to force isi_visudo to edit the correct sudoers configuration file which is /etc/mcp/override/sudoers. The changes would propagate across all nodes in the cluster 
# isi_visudo -f /etc/mcp/override/sudoers

How to Collect API response generated on the Isilon Cluster

How to Collect API response generated on the Isilon Cluster

Process:
1. Use the below URL in the browser
2. Enter the Login Credentials
3. Prompt to Downloaded the File, ex: eventlists.json
4. Open the file in Notepad and view the generated last 1000 Events

https://<Isilon IP>:8080/platform/3/event/eventlists?limit=1000

ViPR SRM - License Upload - Error: An unexpected error occured: 'Unable to upload license. License is invalid or expires.'


Issue: Unable to upload the ViPR SRM License Ley from GUI or CLI
Error: An unexpected error occured: 'Unable to upload license. License is invalid or expires.'
Cause: This error is caused because the ELMS license SWID is referring to a product that is already using the other licenses.
Fix: Uninstall the conflicted ELMS license SWID

Steps to Fix Issue:
1. Upload the New License File (.lic) to the Frontend Server, maybe to tmp directory/folder; using tools like WinSCP.
Ex: file name: <SRMS_XXXXX_exp>.lic

2. Login to the Frontend Server with root Credentials
<FrontendServer>:~ # cd /tmp/
<FrontendServer>:/tmp # ls -l | grep -i SRMS
-rw-r--r-- 1 root    root       694 May 21 18:42 <SRMS_XXXXX_exp>.lic

3. Test the issue by trying to install the new License (Can be Skipped)
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh install "<SRMS_XXXXX_exp>.lic"
Installing APG license key (SRMS_XXXXX_exp.lic)... SEVERE  -- [2018-05-22 11:47:40 EDT] -- BinaryDecoder$AbstractBagDecorator::getHashCodeBuilder(): ELMS license swid refers to a product that is already in use by other license(s).  If the current license is correct, please remove the installed license(s) that conflict,  otherwise contact SRM support about the current conflicting license(s). candidate swid: ELMSRM0XXXXXXX, candidate product: ViPR SRM, conflicting swid(s): [CB885L7VXXXXXX], installed license(s) swid-to-product-mapping: {CB885L7VXXXXXX=[ViPR SRM]}
 failed!
**** Unable to modify Java system preferences.
**** You may need to be root in order to perform this operation.

4. Uninstall the conflicted ELMS license SWID
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh remove "ELMS Features: CB885L7VXXXXXX"
Removing license for ELMS Features: CB885L7VXXXXXX... done.
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh remove "ELMS Features: ELMSRM0XXXXXXX"
Removing license for ELMS Features: ELMSRM0XXXXXXX... done.

5. After uninstalling all the license causing interruption for the fresh license we need to update the license-manager by using the following command:
<FrontendServer>:/tmp # /opt/APG/bin/manage-modules.sh update license-manager Default
Required dependencies, in processing order:
   [1]   java '8.0.151' v8.0.151
   [2] U license-manager 'Default' v5.7u2 => v5.7u2
> 1 not modified, 1 to update
> 2.2 MB space required / 346.9 GB available
 ? Enter the step to modify, 'yes' to accept them, or 'no' to cancel the operation [yes] > yes

Starting update of license-manager Default from v5.7u2 to v5.7u2...
 * Gathering information...
 * Module found in '/opt/APG/Tools/License-Manager/Default'.
 * It will now be updated using 'license-manager-5.7u2-linux-x64.pkg'.
 * Unpacking files...
 * Updating files... 100%
 * 19 files have been updated.
 * Finalizing update...
Update complete.

6. Now you can then install the fresh license using the following command
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh install "SRMS_XXXXXXX_DD-MMM-YYYY_exp.lic"
Installing APG license key (SRMS_XXXXXXX_DD-MMM-YYYY_exp.lic)... done.

7. You can then verify the installed license by using the below command:
<FrontendServer>:/tmp # /opt/APG/bin/manage-licenses.sh check

Note: Moreover, if it’s a distributed environment you will need to go to the >> ViPR SRM centralized management > License Management > and then click on Synchronize so that the new license is copied on all the hosts.

Hope this would help :)


How to Generate Logs in ViPR SRM Using


Process Steps to follow:
  1. Download the Calypso zip file:
    1. https://support.emc.com/downloads/34247_ViPR-SRM              
  2. Place the Calypso zip file on the User interface host
  3. Extract the zip file to c:\calypso
  4. Right Click on the command line icon and select Run As Administrator
  5. Answer yes if prompted to continue – if asked
  6. Change to the c:\calypso directory
  7. Run the following batch file based on the type of installation of ViPR SRM
    1. For a Linux Front End
      1. Calypso.bat
    2. For a Windows Front End (Binary)
      1. Calypso_win.bat
  8. Enter the Frontend Hostname or IP
  9. Accept all possible defaults - this is preferable by support unless otherwise directed
  10. FE username – enter for root  Note: this is the username to log into the host itself
  11. FE password – Default is Changeme1!   Note: the 'C' in Changeme1! is a capital letter
  12. Enter the installation directory – default hit enter
  13. Press Enter to collect diagnostics for all hosts – Default hit enter
  14. Press enter to collect logs for the last 3 days – Default hit enter
  15. It may take 20-30 minutes for the information to be collected
  16. For Health reports hit enter to accept defaults
  17. For port 58080 – Default hit enter  -  if a secure port is used enter that 
  18. For HTTP – Default hit enter  -  if you are using a secure connection enter HTTPS 
  19. For Frontend UI portal username – if admin is used – Default hit enter
  20. For Frontend UI portal password – if changeme – Default hit enter
  21. Zip up the entire \out\ directory and upload to the case or location designated by the Support Engineer
  22. Notify the support engineer that the file is uploaded

To view a Video on how to install and run the Calypso Tool please click the following link:
https://community.emc.com/videos/174428

How to generate Diagnostic file from ViPR SRM GUI & CLI


Process for GUI:
1. To generate the Diagnostic file for the entire SRM server set, navigate to the centralized management page
In the left pane expand the tree and navigate to the 'Logs and Diagnostics' section > Select 'Diagnostic Files' > Click on "Generate Diagnostic Files" button (which will collect and compress all logs and configuration files for each server in the installation).
Once that function completes then click the "Download" button which will move the files to a location of your choice (default is Downloads directory).

Link to diagnostics window
http://<srm front end server>:58080/centralized-management/#/audit/diagnostics

Process for CLI:

Windows
From command prompt cd to:
/APG/bin/
Run: diagnostic.cmd
This will create DiagnosticFiles.zip

Linux
Run the following command:
diagnostic.sh
This will create the file DiagnosticFiles.tar.gz within the /tmp directory

If unable to save the diagnostics file to the tmp directory due to lack of disk space, you can change the destination by doing the following:
- Log into the host in question
- Edit /APG/Tools/APG-Diagnostic-Tools/Default/bin/diagnostics.sh
- Look for the entry in the file TARFILE="/tmp/DiagnosticFiles.tar"
- Replace the tmp directory with the directory location you wish to save the DiagnosticFiles.tar
- Rerun the script /APG/bin/./diagnostic.sh and the DiagnosticFiles.tar will be placed in the new location when it completes


VNX Best Practices

1. Storage Processor (SP) Cache Size:
Read Cache - 10% of the available Cache. (Recommended Min 200MB & Max 1024 MB).
   Note: read cache facilitates pre-fetching, so it doesn't need to be large. Increases read cache above recommended values only if if you know that you have multiple application with sequential read-intensive.
Write Cache - set remaining memory to write cache.

2. Cache Page Size: min amount of SP memory used to serve a single I/O request.
Default: 8 KB provide a good balance for both Block ad File Storage.
Increase Max 16 KB; in case your environment has large-lock I/O size.
Other sizes 2 KB and 4 KB is good for like database environments.

3. Cache watermark: controls the flushing behavior of write cache.
Recommended - Low 60% High 80% (maintain diff b/w low ad high of about 20%)

4. Physical drive placement: place highest performing drives in lowest numbered enclosures on each bus.

5.Hot Spares: allocate 1 hot spare or every 30 drives.

6. Drive Type:
FLASH: extreme performance / transactional random workloads.
SAS: General Permormance
NL-SAS: Archive Purpose / aging data.

7. IOPS: Calculated based on drive types


8. RAID Level:
RAID 1/0 - Heavy Transnational with >25% random writes
RAID 5 - Medium-High performance, sequential
RAID 6 - archiving, read-biased workloads

9. Maximum Drives in a Pool:


10. FAST Cache: Recommended to have size of Active Data set.
EMC has tools to determine the active data set, or else in general 5% of the capacity would be good


ESX Version Comparision



Virtual Machine Maximums

ESX 5.5
ESX 5.1
ESX 5
ESX 4.1
ESX 4.0
ESX 3.5
ESX 3
ESX 2
ESX 1
Virtual CPUs per virtual machine
64
64
32
8
8
4
4
2
1
RAM per virtual machine
1TB
1TB
1TB
255GB
255GB
65GB
16GB
3,6GB
2GB
Virtual SCSI adapters per virtual machine
4
4
4
4
4
4
4
4
4
Virtual disk size
62TB
2TB
2TB
2TB
2TB
2TB
2TB


IDE controllers per virtual machine
1
1
1
1
1
1



IDE devices per virtual machine
4
4
4
4
4
4



Floppy controllers per virtual machine
1
1
1
1
1
1
1
1

Floppy devices per virtual machine
2
2
2
2
2
2
2
2

Virtual NICs per virtual machine
10
10
10
10
10
4
4
4
4
USB controllers per virtual machine
1
1
1
1





USB devices connected to a virtual machine
20
20
20
20





Parallel ports per virtual machine
3
3
3
3
3
3
3
1

USB 3.0 devices per virtual machine

1
1






Concurrent remote console connections
40
40
40
40
40
10
10



Host Maximums

ESX 5.5
ESX 5.1
ESX 5
ESX 4.1
ESX 4.0
ESX 3.5
ESX 3
ESX 2
ESX 1
Logical CPUs per host
320
160
160
160
64
32
32
16
8
Virtual machines per host
512
512
512
320
320
128
128
80
64
Virtual CPUs per host
4096
2048
2048
512
512
128
128
80
64
Virtual CPUs per core
32
25
25
25
20
8
8
8
8
RAM per host
4TB
2TB
2TB
1TB
1TB
256GB
256GB
64GB
64GB
LUNs per server
256
256
256
256
256





vCenter Server Maximums
vCenter Server Maximums
ESX 5.5
ESX 5.1
ESX 5
ESX 4.1
ESX 4.0
ESX 3.5
ESX 3
Hosts per vCenter Server
1000
1000
1000
1000
300
200
200
Powered on virtual machines
10000
10000
10000
10000
3000
2000

Registered virtual machines
15000
15000
15000
15000
4500
2000

Linked vCenter Servers
10
10
10
10
10


Hosts in linked vCenter Servers
3000
3000
3000
3000
1000


Powered on virtual machines in linked vCenter
30000
30000
30000
30000
10000


Registered virtual machines in linked vCenter
50000
50000
50000
50000
15000


Concurrent vSphere Clients
100
100
100
100
30


Number of host per datacenter
500
500
500
400
100


MAC addresses per vCenter Server
65536
65536
65536




USB devices connected at vSphere Client
20
20
20





Cluster and Resource Pool Maximums

ESX 5.5
ESX 5.1
ESX 5
ESX 4.1
ESX 4.0
ESX 3.5
Hosts per cluster
32
32
32
32
32
32
Virtual machines per cluster
4000
4000
3000
3000
1280

Virtual machines per host
512
512
512
320
100

Maximum concurrent host HA failover

32
32
4
4

Failover as percentage of cluster

100%
100%
50%
50%

Resource pools per cluster
1600
1600
1600
512
512
128
Resource pools per host
1600
1600
1600

4096

Children per resource pool
1024
1024
1024
1024


Resource pool tree depth
8
8
8
8
12
12


Network Maximums

ESX 5.5
ESX 5.1
ESX 5
ESX 4.1
ESX 4.0
ESX 3.5
ESX 3
Total virtual network switch ports per host
4096
4096
4096
4096
4096
127

Maximum active ports per host
1016
1050
1016
1016
1016
1016

Virtual network switch creation ports
4088
4088
4088
4088
4088


Port groups
512
256
256
512
512
512

Distributed virtual network switch ports per vCenter
60000
60000
30000
20000
6000


Static port groups per vCenter
10000
10000
5000
5000
512


Ephemeral port groups per vCenter
1016
256
256
1016



Hosts per VDS
500
500
350
350
64


Distributed switches per vCenter
128
128
32
32
16


e1000 1Gb Ethernet ports (Intel PCI?x)

32
32
32
32
32
32
e1000e 1Gb Ethernet ports (Intel PCI?e)
24
24
24
24
32
32
32
igb 1Gb Ethernet ports (Intel)
16
16
16
16
16


tg3 1Gb Ethernet ports (Broadcom)
32
32
32
32
32


bnx2 1Gb Ethernet ports (Broadcom)
16
16
16
16
16


forcedeth 1Gb Ethernet ports (NVIDIA)

2
2
2
2


nx_nic 10Gb Ethernet ports (NetXen)
8
8
8
4
4


ixgbe 10Gb Ethernet ports (Intel)
8
8
8
4
4


bnx2x 10Gb Ethernet ports (Broadcom)
8
8
8
4
4


be2net 10Gb Ethernet ports (Emulex)
8
8
8
4
4


VMDirectPath PCI/PCIe devices per host
8
8
8
8
8


VMDirectPath PCI/PCIe devices per virtual machine
4
4
4
4



Concurrent vMotion operations per host (1Gb/s network)
4
4
4
2
2


Concurrent vMotion operations per host (10Gb/s network)
8
8
8







Storage Maximums

ESX 5.5
ESX 5.1
ESX 5
ESX 4.1
ESX 4.0
ESX 3.5
ESX 3
Qlogic 1Gb iSCSI HBA initiator ports per server
4
4
4
4



Broadcom 1Gb iSCSI HBA initiator ports per server
4
4
4
4



Broadcom 10Gb iSCSI HBA initiator ports per server
4
4
4
4



Software iSCSI NICs per server
8
8
8
8



Number of total paths on a server
1024
1024
1024
1024



Number of paths to a iSCSI LUN
8
8
8
8



Qlogic iSCSI: dynamic targets per adapter port
64
64
64
64



Qlogic iSCSI: static targets per adapter port
62
62
62
62



Broadcom 1Gb iSCSI HBA targets per adapter port
64
64
64
64



Broadcom 10Gb iSCSI HBA targets per adapter port
128
128
128
64



Software iSCSI targets
256
256
256
256
256


NFS mounts per host
256
256
256
64
64


FC LUNs per host
256
256
256
256
256
256
256
FC LUN ID
255
255
255
255
255
255
255
FC Number of paths to a LUN
32
32
32
32
32
32
32
Number of total paths on a server
1024
1024
1024
1024
1024
1024
1024
Number of HBAs of any type
8
8
8
8
8


HBA ports
16
16
16
16
16
16

Targets per HBA
256
256
256
256
256
15

Software FCoE adapters
4
4
4




Volumes per host
256
256
256
256
256
256

Hosts per volume
64
64
64
64
64
32

Powered on virtual machines per VMFS volume
2048
2048
2048

256


Concurrent vMotion operations per datastore
128
128
128




Concurrent Storage vMotion operations per datastore
8
8
8




Concurrent Storage vMotion operations per host
2
2
2




Concurrent non vMotion provisioning operations per host
8
8
8




VMFS Volume size
64TB
64TB
64TB
64TB
64TB
64TB