/** * Network Monitoring API * Use the Network Monitoring API to troubleshoot routing and security issues for resources such as virtual cloud networks (VCNs) and compute instances. For more information, see the console documentation for the [Network Path Analyzer](https://docs.oracle.com/iaas/Content/Network/Concepts/path_analyzer.htm) tool. * OpenAPI spec version: 20160918 * * * NOTE: This class is auto generated by OracleSDKGenerator. * Do not edit the class manually. * * Copyright (c) 2020, 2026, Oracle and/or its affiliates. All rights reserved. * This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license. */ /** * All routing inside the DRG is driven by the contents of DRG route tables. * DRG route tables contain rules which route packets to a particular network destination, * represented as a DRG attachment. * The routing decision for a packet entering a DRG is determined by the rules in the DRG route table * assigned to the attachment-of-entry. *

Each DRG attachment can inject routes in any DRG route table, provided there is a statement corresponding to the attachment in the route table's {@code importDrgRouteDistribution}. * You can also insert static routes into the DRG route tables. *

The DRG route table is always in the same compartment as the DRG. There must always be a default * DRG route table for each attachment type. * */ export interface DrgRouteTable { /** * The [OCID](https://docs.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the * DRG route table. * */ "id": string; /** * The [OCID](https://docs.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the compartment the DRG is in. The DRG route table * is always in the same compartment as the DRG. * */ "compartmentId": string; /** * The [OCID](https://docs.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the DRG the DRG that contains this route table. * */ "drgId": string; /** * Defined tags for this resource. Each key is predefined and scoped to a namespace. * Example: {@code {\"foo-namespace\": {\"bar-key\": \"value\"}}} * */ "definedTags"?: { [key: string]: { [key: string]: any; }; }; /** * A user-friendly name. Does not have to be unique, and it's changeable. * Avoid entering confidential information. * */ "displayName"?: string; /** * Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. * Example: {@code {\"bar-key\": \"value\"}} * */ "freeformTags"?: { [key: string]: string; }; /** * The date and time the DRG route table was created, in the format defined by [RFC3339](https://tools.ietf.org/html/rfc3339). *

Example: {@code 2016-08-25T21:10:29.600Z} * */ "timeCreated": Date; /** * The DRG route table's current state. */ "lifecycleState": DrgRouteTable.LifecycleState; /** * The [OCID](https://docs.oracle.com/iaas/Content/General/Concepts/identifiers.htm) of the import route distribution used to specify how incoming route advertisements from * referenced attachments are inserted into the DRG route table. * */ "importDrgRouteDistributionId"?: string; /** * If you want traffic to be routed using ECMP across your virtual circuits or IPSec tunnels to * your on-premises network, enable ECMP on the DRG route table to which these attachments * import routes. * */ "isEcmpEnabled": boolean; } export declare namespace DrgRouteTable { enum LifecycleState { Provisioning = "PROVISIONING", Available = "AVAILABLE", Terminating = "TERMINATING", Terminated = "TERMINATED", /** * This value is used if a service returns a value for this enum that is not recognized by this * version of the SDK. */ UnknownValue = "UNKNOWN_VALUE" } function getJsonObj(obj: DrgRouteTable): object; function getDeserializedJsonObj(obj: DrgRouteTable): object; }