Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {@code {"foo-namespace": {"bar-key": "value"}}}
The OCID of the set of DHCP options the subnet will use.
A user-friendly name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
Simple key-value pair that is applied without any predefined name, type or scope. Exists for cross-compatibility only. Example: {@code {"bar-key": "value"}}
This is the IPv6 CIDR block for the subnet's IP address space. The subnet size is always /64. See IPv6 Addresses. The provided CIDR must maintain the following rules -
a. The IPv6 CIDR block is valid and correctly formatted. b. The IPv6 CIDR is within the parent VCN IPv6 range.
Example: {@code 2001:0db8:0123:1111::/64}
The list of all IPv6 CIDR blocks (Oracle allocated IPv6 GUA, ULA or private IPv6 CIDR blocks, BYOIPv6 CIDR blocks) for the subnet that meets the following criteria:
The OCID of the route table the subnet will use.
The OCIDs of the security list or lists the subnet will use. This replaces the entire current set of security lists. Remember that security lists are associated with the subnet, but the rules are applied to the individual VNICs in the subnet.
The CIDR block of the subnet. The new CIDR block must meet the following criteria:
- Must be valid. - The CIDR block's IP range must be completely within one of the VCN's CIDR block ranges. - The old and new CIDR block ranges must use the same network address. Example: {@code 10.0.0.0/25} and {@code 10.0.0.0/24}. - Must contain all IP addresses in use in the old CIDR range. - The new CIDR range's broadcast address (last IP address of CIDR range) must not be an IP address in use in the old CIDR range.
*Note:** If you are changing the CIDR block, you cannot create VNICs or private IPs for this resource while the update is in progress.
Example: {@code 172.16.0.0/16}