|
- Introduction to GGC - Interconnect Help - Google Help
Introduction to GGC Google Global Cache (GGC) allows ISPs to serve certain Google content from within their own networks This eases congestion within your network, and reduces the amount on traffic on your peering and transit links If you do not currently host a GGC node, but would like to enquire about availability, please use this web form
- Content Served - Interconnect Help
Content Served GGC network traffic can be broadly divided into two types: high-volume and low-volume For all types of traffic, the choice of serving location is made at our discretion Our intent is to serve users from the best available location for each service, which may or may not be a local GGC node High-Volume traffic
- Carrier Grade NAT - Interconnect Help
Carrier Grade NAT Introduction This document describes how to configure Google Global Cache (GGC) nodes to operate with your Carrier Grade NAT (CGN) systems Once configured, this allows traffic between the GGC node and private user IPs to bypass the CGN GGC has no requirement that "private IP space" be in the RFC1918 allocation
- BGP Community Support for Google Serving
Google supports the exchange of BGP community tags with GGC nodes and peering sessions to signal important properties of a prefix for reporting, load-balancing, or policy enforcement
- Network Changes - Interconnect Help
We make use of either static routes or Router Advertisements to configure the default IPv6 gateway on the GGC machines: If you prefer we use a separate gateway as advertised via Router Advertisements, ensure these are enabled and working properly
- Monitoring GGC - Interconnect Help
Monitoring GGC Google conducts extensive monitoring of all GGC nodes and the GGC Support Team are automatically notified of any faults materially affecting the performance of a GGC node, or of individual GGC machines Fault tickets raised by GGC Program Partners or contracted third parties may:
- Cache-Fill - Interconnect Help
Cache-Fill Cache-fill traffic (also referred to as "ingress traffic") is data transfer into GGC servers from other Google data locations New GGC nodes initially require as much cache-fill traffic as there is user demand The amount of cache-fill traffic will reduce over time, as storage on GGC servers is filled with popular content
- Preparing your Network - Interconnect Help - Google Help
The GGC node must be reachable from any IP on the Internet Access Control Lists (ACLs) are not recommended on network equipment serving the GGC node An IP firewall runs on each machine in the GGC node If you use ACLs in your network, the following ports must be allowed for the entire GGC subnet: Inbound and outbound ICMP Inbound and outbound GRE
|
|
|