For more information, refer to BGP Community Support For Google Serving. This includes indicating serving preferences for traffic ingressing your network from GGC and peering. BGP community tags allow you to provide additional signals to us about prefixes originating in your network.
Multi Exit Discriminators (MED) are not supported.MD5 passwords are supported, but not required, for GGC BGP sessions.Announcing more will result in BGP session termination. A maximum of 90000 IPv0 IPv6 prefixes can be announced to the GGC router.For IPv6, the most-specific prefix size is /56 for direct advertisements and /48 for indirect advertisements. The most-specific prefix size considered by a GGC node for traffic allocation is /27 for direct advertisements and /24 for indirect advertisements.Multiple BGP sessions with AS36040 are permitted at a single location.You should also re-advertise a covering prefix to your peers and transit providers, in case the GGC servers prefix is too small to be re-advertised directly. You should propagate this advertisement to your users, peers and transit providers. We may advertise the prefix of the the GGC servers to you.BGP is used both for receiving a list of user prefixes, and for traditional routing.Our router will need a route to your BGP peer, either static or via another BGP session. Your device may be in Active or Passive mode.The most-specific prefix size considered by a GGC node is /27 for direct advertisements and /24 for indirect advertisements.Consider using a route server if you need to advertise aggregated prefix data from multiple sources on your network.
0 kommentar(er)
