Peering Types
With FastConnect Classic, you can choose to use private peering, public peering, or both.
Comparison of Public Peering and Private Peering
The table below shows the differences between the two peering types.
| Categories | Public Peering | Private Peering |
|---|---|---|
| Description |
A peering with FastConnect Classic edge routers through which you can access Oracle Public resources using public IP prefixes. |
A peering with FastConnect Classic edge routers through which you can extend your on-premise private networks to the Oracle Cloud. Private peering enables you to connect to Oracle Cloud resources from your on-premise private (RFC1918) networks. |
| You can advertise... |
Only public IPv4 prefixes. These public IPv4 prefixes should be registered to your company or to your service provider in an Internet Routing Registry (IRR) or Regional Internet Registry (RIR). Work with your Internet service provider or with your RIR to obtain IPv4 address allocation. |
Any valid IPv4 prefixes, including RFC 1918 IPv4 prefixes. |
| Network Address Translation (NAT) |
If you are connecting through Direct Cross Connects, you are responsible for NATing your private IP addresses and you can advertise only public IP addresses to Oracle. If you are connecting through Oracle FastConnect Partner, your partner service will either provide NAT and advertise public routable IPv4 prefixes or you’ll need to provide your own NAT and advertise public routable IPv4 prefixes over the partner connection. If your partner provides NAT, your partner will translate your IP addresses to a public routable IPv4 prefix that will be advertised to Oracle. |
You can extend your remote datacenter resources that use a private (RFC1918) address without the need to use IPSec VPN or NAT. |
| Maximum number of IP Prefixes that you can advertise per peering |
200 public IPv4 prefixes |
2000 IPv4 prefixes |
The BGP session is brought down or disabled if you cross the specified prefix-limit of advertising 200 IPv4 prefixes over public peering or 2000 private (RFC1918) IPv4 prefixes over private peering. When the BGP session is torn down, you can’t access your Oracle Cloud services through FastConnect Classic.
To fix this issue, change the number of IP prefixes that you are advertising over the session. When the BGP session is torn down, Oracle checks after every one hour to identify if you have modified the number of advertised IP prefixes to match the prescribed limits. If you meet the prescribed limits, the connection is established.