InlineInstanceEndpoint1

InlineInstanceEndpoint1

JSON Example

{
    "service_attachments": [
        {
            "target_display_name": "string",
            "is_valid": false,
            "target_id": "string",
            "target_type": "string"
        }
    ],
    "target_ips": [
        {
            "ip_addresses": [
                "string"
            ],
            "prefix_length": 0
        }
    ],
    "endpoint_type": "string",
    "link_ids": [
        {
            "target_display_name": "string",
            "is_valid": false,
            "target_id": "string",
            "target_type": "string"
        }
    ]
}

array of ResourceReference

service_attachments

Optional

Id(s) of the Service Attachment where this enndpoint is connected to. Service Attachment is mandatory for LOGICAL Instance Endpoint.

array of IPInfo

target_ips

Required

Target IPs on an interface of the Service Instance.

string

endpoint_type

Optional

LOGICAL - It must be created with a ServiceAttachment and identifies a destination connected to the Service Port of the ServiceAttachment, through the ServiceAttachment's Logical Switch. VIRTUAL - It represents a L3 destination the router can route to but does not provide any further information about its location in the network. Virtual InstanceEndpoints are used for redirection targets that are not connected to Service Ports, such as the next-hop routers on the Edge uplinks.

Possible values are : LOGICAL, VIRTUAL,

array of ResourceReference

link_ids

Optional

Link Ids are mandatory for VIRTUAL Instance Endpoint. Even though VIRTUAL, the Instance Endpoint should be connected/accessible through an NSX object. The link id is this NSX object id. Example - For North-South Service Insertion, this is the LogicalRouter Id through which the targetIp/L3 destination accessible.

Used By

InstanceEndpoint