Border router links provide a way to interconnect VNS domains in the wide-area to datacenter domains. Service chaining links allow domain leaking in order to simplify and enhance capabilities of doing service chaining and traffic steering for NFV and service-provider-grade VPN services.
This object has no members.
A route filtering criteria enum. Defaults to ALL.
Allowed values: ALL, SUBNETS_ONLY
Default value: ALL
SDK attribute: acceptanceCriteria
This is the ID of the domain receiving the routes from the source. This can only be set for links of type OVERLAY_ADDRESS_TRANSLATION.
Format: free
SDK attribute: associatedDestinationID
None
SDK attribute: associatedDestinationName
Type of the entity type for the source
Allowed values: DOMAIN
SDK attribute: associatedDestinationType
The ID of the domain receiving the routes from another domain
Format: free
SDK attribute: associatedSourceID
None
Format: free
SDK attribute: associatedSourceName
This is the source object type for the associatedSourceID
Format: free
SDK attribute: associatedSourceType
Metadata objects associated with this entity. This will contain a list of Metadata objects if the API request is made using the special flag to enable the embedded Metadata feature. Only a maximum of Metadata objects is returned based on the value set in the system configuration.
SDK attribute: embeddedMetadata
Specify if scope of entity is Data center or Enterprise level
Allowed values: ENTERPRISE, GLOBAL
SDK attribute: entityScope
External object ID. Used for integration with third party systems
Format: free
SDK attribute: externalID
ID of the user who last updated the object.
Format: free
SDK attribute: lastUpdatedBy
This is set to true if a link has been created in the opposite direction
SDK attribute: readOnly
This is used to distinguish between different type of links: hub and spoke, IP address, VNS border router links.
Allowed values: BIDIR, BORDER_ROUTER, HUB_AND_SPOKE, OVERLAY_ADDRESS_TRANSLATION, SERVICE_CHAINING
SDK attribute: type