Filter
Top Products
Chapter 16. Managing Networks and Traffic
206
• All network tiers inside the VPC should belong to the same account.
• When a VPC is created, by default, a SourceNAT IP is allocated to it. The Source NAT IP is
released only when the VPC is removed.
• A public IP can be used for only one purpose at a time. If the IP is a sourceNAT, it cannot be used
for StaticNAT or port forwarding.
• The instances can only have a private IP address that you provision. To communicate with the
Internet, enable NAT to an instance that you launch in your VPC.
• Only new networks can be added to a VPC. The maximum number of networks per VPC is limited
by the value you specify in the vpc.max.networks parameter. The default value is three.
• The load balancing service can be supported by only one tier inside the VPC.
• If an IP address is assigned to a tier:
• That IP can't be used by more than one tier at a time in the VPC. For example, if you have tiers A
and B, and a public IP1, you can create a port forwarding rule by using the IP either for A or B, but
not for both.
• That IP can't be used for StaticNAT, load balancing, or port forwarding rules for another guest
network inside the VPC.
• Remote access VPN is not supported in VPC networks.
16.27.2. Adding a Virtual Private Cloud
When creating the VPC, you simply provide the zone and a set of IP addresses for the VPC network
address space. You specify this set of addresses in the form of a Classless Inter-Domain Routing
(CIDR) block.
1. Log in to the CloudPlatform UI as an administrator or end user.
2. In the left navigation, choose Network.
3. In the Select view, select VPC.
4. Click Add VPC. The Add VPC page is displayed as follows: