NSX-T Data Center REST API

Create a Event Log server for Firewall Identity store

More than one Event Log server can be created and only one event log
server is used to synchronize directory objects. If more
than one Event Log server is configured, NSX will try all the
servers until it is able to successfully connect to one.

Request:

Method:

PATCH

URI Path(s):

/policy/api/v1/infra/firewall-identity-stores/<firewall-identity-store-id>/event-log-servers/<event-log-server-id>

Request Headers:

n/a

Query Parameters:

PolicyIdfwEnforcementPointRequestParameters+

PolicyIdfwEnforcementPointRequestParameters (schema)

Name	Description	Type	Notes
enforcement_point_path	String Path of the enforcement point enforcement point path, forward slashes must be escaped using %2F.	string

Request Body:

DirectoryEventLogServer+

DirectoryEventLogServer (schema)

Name	Description	Type	Notes
_create_time	Timestamp of resource creation	EpochMsTimestamp	Readonly Sortable
_create_user	ID of the user who created this resource	string	Readonly
_last_modified_time	Timestamp of last modification	EpochMsTimestamp	Readonly Sortable
_last_modified_user	ID of the user who last modified this resource	string	Readonly
_links	References related to this resource The server will populate this field when returing the resource. Ignored on PUT and POST.	array of ResourceLink	Readonly
_protection	Indicates protection status of this resource Protection status is one of the following: PROTECTED - the client who retrieved the entity is not allowed to modify it. NOT_PROTECTED - the client who retrieved the entity is allowed to modify it REQUIRE_OVERRIDE - the client who retrieved the entity is a super user and can modify it, but only when providing the request header X-Allow-Overwrite=true. UNKNOWN - the _protection field could not be determined for this entity.	string	Readonly
_revision	Generation of this resource config The _revision property describes the current revision of the resource. To prevent clients from overwriting each other's changes, PUT operations must include the current _revision of the resource, which clients should obtain by issuing a GET operation. If the _revision provided in a PUT request is missing or stale, the operation will be rejected.	int
_schema	Schema for this resource	string	Readonly
_self	Link to this resource	SelfResourceLink	Readonly
_system_owned	Indicates system owned resource	boolean	Readonly
description	Description of this resource	string	Maximum length: 1024 Sortable
display_name	Identifier to use when displaying entity in logs or GUI Defaults to ID if not set	string	Maximum length: 255 Sortable
domain_name	Directory domain name Directory domain name which best describes the domain. It could be unique fqdn name or it could also be descriptive. There is no unique contraint for domain name among different domains.	string
host	Event log server host name Directory Event Log server DNS host name or ip address which is reachable by NSX manager to be connected and do event fetching.	string	Required Format: hostname-or-ip
id	Unique identifier of this resource	string	Sortable
password	Event log server password Directory event log server connection password.	string
resource_type	Must be set to the value DirectoryEventLogServer	string
status	Event log server connection status Event log server connection status object	DirectoryEventLogServerStatus
tags	Opaque identifiers meaningful to the API user	array of Tag	Maximum items: 30
username	Event log server username Directory event log server connection user name.	string

Example Request:

PATCH https://<nsx-mgr>/policy/api/v1/infra/firewall-identity-stores/idstore-1/event-log-servers/01ad13c6-23c1-4175-ad3f-881eac8e45ef { "host": "10.161.34.143", "username": "dummy", "password": "dummy", "domain_name": "nimbus event log server" }

Successful Response:

Response Code:

201 Created

Response Headers:

n/a

Response Body:

n/a

Required Permissions:

crud

Feature:

policy_identity

Additional Errors:

• 404 Not Found
• 301 Moved Permanently
• 307 Temporary Redirect
• 400 Bad Request
• 403 Forbidden
• 409 Conflict
• 412 Precondition Failed
• 500 Internal Server Error
• 503 Service Unavailable