For Model Deployment Custom Networking
Troubleshoot custom networking model deployments.
Unable to Access the Specified Subnet
The specified subnet can't be accessed,
The network access policy is incorrectly configured.
Insufficient IPs Available in the Specified Subnet
Not enough IP addresses are available in the subnet.
The service requires that subnets for egress have at least 255 available IP addresses. This is so that the subnet has enough IP capacity reserved for service deployment maintenance tasks such as security patches. You can't create any more model deployments after the available IP address count is under 255.
- Update the model deployment with a different subnet that has enough capacity.
- Update the CIDR range of the subnet to increase available IP count.
Update SubnetId Operation Fails
The operation to update the subnet ID fails.
The custom networking update can't be run at the same time as the Instance Shape, Instance Count, or Load Balancer bandwidth update.
The Internet isn't Reachable with Custom Networking
You can't access the internet from custom networking.
The VCN or subnet aren't configured for public egress.