Static routes allow end users to define how traffic is routed through the dVRS in addition to the routes learned by VSC through VM activation. By using static routes, end users can define for example that all traffic with a destination address towards a specific subnet must be forwarded to a specific VM attached in the dVRS and this VM could be a firewall
| address |
| associatedSubnetID |
| BFDEnabled |
| entityScope |
| externalID |
| IPType |
| IPv6Address |
| lastUpdatedBy |
| netmask |
| nextHopIp |
| routeDistinguisher |
| type |
This object has no members.
IP address of the route
Format: free
SDK attribute: address
UUID of Do Not Advertise Subnet
Format: free
SDK attribute: associatedSubnetID
Enable or disable Bidirectional Forwarding Detection for this static route
Default value: false
SDK attribute: BFDEnabled
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
IPv4 or IPv6
Allowed values: IPV4, IPV6
SDK attribute: IPType
IPv6 address of the route
Format: free
SDK attribute: IPv6Address
ID of the user who last updated the object.
Format: free
SDK attribute: lastUpdatedBy
Netmask associated with the route
Format: free
SDK attribute: netmask
IP address of the next hop. This must be a VM attached to the dVRS
Format: free
SDK attribute: nextHopIp
Route distinguisher associated with the nexthop. System generates this identifier automatically
Format: free
Min length: 1
Max length: 255
SDK attribute: routeDistinguisher
Type flag for static-route provisioning for exit-domain (break-to-underlay) prefixes.
Allowed values: EXIT_DOMAIN, OVERLAY, OVERLAY_ADDRESS_TRANSLATION
SDK attribute: type