Configure Time Settings
Configures time settings for the HCX Manager appliance. Supports NTP server configuration, manual time setting, and timezone selection.
Validations:
- NTP server must be valid hostname or IP address
- Timezone must be valid (e.g., America/Los_Angeles, UTC, Europe/London)
- Datetime format: MMM dd yyyy HH:mm:ss (e.g., Nov 14 2025 10:30:00)
- Cannot set manual datetime when NTP is configured
Important Notes:
- Services restart may be required: Component services may need restart for NTP changes to take effect
- NTP servers can be hostnames or IP addresses
- Timezone changes take effect immediately
- Incorrect time can cause certificate validation failures
{
"ntpServer": [
"pool.ntp.org",
"time.google.com"
],
"datetime": "Nov 14 2025 10:30:00",
"timezone": "America/Los_Angeles"
}List of NTP server hostnames or IP addresses
Manual date/time (only when NTP not configured). Format is 'MMM dd yyyy HH:mm:ss'
Timezone identifier (e.g., America/Los_Angeles, UTC, Europe/London)
Time settings configured successfully
{
"ntpServer": [
"pool.ntp.org",
"time.google.com"
],
"datetime": "Nov 14 2025 10:30:00",
"timezone": "America/Los_Angeles"
}List of NTP server hostnames or IP addresses
Manual date/time (only when NTP not configured). Format is 'MMM dd yyyy HH:mm:ss'
Timezone identifier (e.g., America/Los_Angeles, UTC, Europe/London)
Bad request - Invalid time settings configuration
{
"isSuccess": false,
"message": "Request schema validation failed",
"httpStatusCode": 400
}Indicates if the operation was successful
Human-readable error message
HTTP status code
Internal server error - Failed to configure time settings
{
"isSuccess": false,
"message": "Request schema validation failed",
"httpStatusCode": 400
}Indicates if the operation was successful
Human-readable error message
HTTP status code
curl -X PUT -H 'Authorization: <value>' -H 'Content-Type: application/json' -d '{}' https://{api_host}/system/timesettings