Http Nfc Lease Http Nfc Lease Probe Urls
Perform a series of validations on the target host to see if it can succesfully perform PullFromUrls.
Since: vSphere API Release 7.0.2.0
The unique identifier for the managed object to which the method attaches; the serialized managed object reference for a request has the form moType/moId
, in this case HttpNfcLease/{moId}
.
The vSphere release schema. The current specification covers vSphere 8.0.2.0 APIs.
{
"files": [
{
"_typeName": "string",
"targetDeviceId": "string",
"url": "string",
"memberName": "string",
"create": false,
"sslThumbprint": "string",
"httpHeaders": [
{
"_typeName": "string",
"key": "string",
"value": "string"
}
],
"size": 0
}
],
"timeout": 0
}
[in] List of remote source file descriptors There should be the same number of HttpNfcLeaseSourceFile as HttpNfcLeaseDeviceUrl provided by this lease.
[in] time in seconds for each url validation. Maximum timeout is 60.
OK
[
{
"_typeName": "string",
"serverAccessible": false
}
]
InvalidArgument: if no source files are provided.
InvalidState: if the lease has already been aborted.
{
"_typeName": "string",
"faultCause": "MethodFault Object",
"faultMessage": [
{
"_typeName": "string",
"key": "string",
"arg": [
{
"_typeName": "string",
"key": "string",
"value": {
"_typeName": "string"
}
}
],
"message": "string"
}
]
}