InlineLogicalRouter1

InlineLogicalRouter1
InlineLogicalRouter1
JSON Example
{
    "edge_cluster_member_indices": [
        0
    ],
    "failover_mode": "string",
    "allocation_profile": {
        "allocation_pool": {
            "allocation_pool_type": "string"
        }
    },
    "firewall_sections": [
        {
            "target_display_name": "string",
            "is_valid": false,
            "target_id": "string",
            "target_type": "string"
        }
    ],
    "advanced_config": {
        "internal_transit_network": "string",
        "transport_zone_id": "string",
        "ha_vip_configs": [
            {
                "ha_vip_subnets": [
                    {
                        "prefix_length": 0,
                        "active_vip_addresses": [
                            "string"
                        ]
                    }
                ],
                "redundant_uplink_port_ids": [
                    "string"
                ],
                "enabled": false
            }
        ],
        "external_transit_networks": [
            "string"
        ]
    },
    "router_type": "string",
    "preferred_edge_cluster_member_index": 0,
    "high_availability_mode": "string",
    "edge_cluster_id": "string"
}
array of integer
edge_cluster_member_indices
Optional

For stateful services, the logical router should be associated with edge cluster. For TIER 1 logical router, for manual placement of service router within the cluster, edge cluster member indices needs to be provided else same will be auto-allocated. You can provide maximum two indices for HA ACTIVE_STANDBY. For TIER0 logical router this property is no use and placement is derived from logical router uplink or loopback port.

string
failover_mode
Optional

Determines the behavior when a logical router instance restarts after a failure. If set to PREEMPTIVE, the preferred node will take over, even if it causes another failure. If set to NON_PREEMPTIVE, then the instance that restarted will remain secondary. This property must not be populated unless the high_availability_mode property is set to ACTIVE_STANDBY. If high_availability_mode property is set to ACTIVE_STANDBY and this property is not specified then default will be NON_PREEMPTIVE.

Possible values are : PREEMPTIVE, NON_PREEMPTIVE,
allocation_profile
Optional

allocation_profile

firewall_sections
Optional

List of Firewall sections related to Logical Router.

advanced_config
Optional

advanced_config

string
router_type
Required

Type of Logical Router

Possible values are : TIER0, TIER1,
integer As int64 As int64
preferred_edge_cluster_member_index
Optional

Used for tier0 routers only

string
high_availability_mode
Optional

High availability mode

Possible values are : ACTIVE_ACTIVE, ACTIVE_STANDBY,
string
edge_cluster_id
Optional

Used for tier0 routers