This a known issue in 5.1 have a look at the below article
To verify this, check if the same working from the vCenter server itself
This a known issue in 5.1 have a look at the below article
To verify this, check if the same working from the vCenter server itself