AS216394 · WireShield

Network Operations

BGP go-live checklist

A step-by-step checklist before taking a BGP session live: ASN and prefix authorization, RPKI and IRR records, session parameters and filters. Prevent mistakes up front.

BGP neighbors table

Taking a BGP session live changes how your network appears to the Internet. A wrong announcement can send your traffic the wrong way or nowhere at all. This checklist collects the steps to complete before going live, whether you are setting up BGP with WireShield for DDoS protection or doing any other network cutover.

Why does BGP go-live need care?

BGP is the protocol networks use to tell each other which IP blocks can be reached where. Every prefix you announce changes the direction of traffic. The cost of a mistake is high: announcing from the wrong origin, announcing a prefix that is too small, or opening a session without filters affects you and the other side. That is why preparation comes first, followed by a gradual cutover.

1. Preparation: authorization and records

  • Do the ASN and prefixes belong to you? Verify that you own the blocks you will announce.
  • Letter of authorization (LOA): If an announcement is made on behalf of a protection provider, the LOA must be ready.
  • RPKI ROA: ROA records must match the prefix, the allowed maximum length and the origin ASN exactly. A mismatching announcement is treated as "invalid" and rejected by many networks.
  • IRR objects: route / route6 objects must be current and show the correct origin ASN.
  • Prefix length: The global Internet generally accepts up to /24 for IPv4 and up to /48 for IPv6.

2. Session parameters

ParameterCheck
Neighbor address and ASNIdentical on both sides
Hold / keepalive timersCompatible and sensible (for example 90 / 30 s)
AuthenticationIf TCP-MD5 is used, the password matches on both sides
TTL security (GTSM)If enabled on a directly connected neighbor, consistent on both sides
MultihopExplicitly configured if the neighbor is not directly connected
IPv4 / IPv6A separate session per address family, or the right address family enabled

3. Filters and protection

  • Received prefix limit (max-prefix): The session should drop if far more prefixes arrive than expected.
  • Outbound filter: Announce only your own prefixes; never re-announce routes you learned.
  • Inbound filter: Do not accept bogons, private ranges or your own block from the other side.
  • Communities: Settle in advance which communities you will use (for example local preference, blackhole).

Tip: Attach the checklist to your change record. Do not go live if the rollback steps are not written down.

4. Verification and gradual cutover

  1. Test with a single prefix first; do not announce the whole block at once.
  2. Verify the session is Established and the announcements are visible on the far side.
  3. If clean traffic returns over a GRE tunnel in DDoS protection, check that the tunnel is up and return routing is correct. For tunnel MTU, see the GRE MTU guide.
  4. Verify reachability from outside (a looking glass, a traceroute from another network).
  5. If all is well, add the remaining prefixes gradually.
  6. Rollback plan: The steps to withdraw the announcement are written down and rehearsed.

5. Monitoring

Watch session state, the number of received and announced prefixes, and session flaps. On the WireShield side you see BGP sessions, announced and received prefixes with their status and rejection reasons in the portal. The announcement AS path and communities can also be managed; for details see the BGP and GRE guide in the documentation.

BGP with WireShield

With remote DDoS protection, a BGP session is built between your own ASN and prefixes and WireShield; traffic arrives at the filtering network and the clean part returns to you. We complete the letter of authorization (LOA) and RPKI details together during setup. If you have no router, we can discuss a Router VM. For the process and the preparation list read the pre-installation checklist, and for the whole flow see how remote DDoS protection works. We summarized the routing options on the Technology page.

Common mistakes

  • Announcing a prefix with no ROA or a wrong ROA.
  • Opening a session without max-prefix and filters.
  • Announcing all prefixes at once.
  • Routing traffic into a GRE tunnel without verifying MTU.
  • Not writing down the rollback steps.

Frequently asked questions

Is everything done once the BGP session is Established?

No. An established session only shows the neighborship works; you must separately verify that announcements are received, traffic takes the right path and the return path works.

Why test with a single prefix first?

If something goes wrong, the blast radius stays small. If it is fine, the remaining prefixes are added gradually.

Is an RPKI ROA mandatory?

Many networks reject RPKI "invalid" announcements, so without a correct ROA your announcement may not be accepted. Create the ROA before going live.

Next step

If you want to plan your BGP cutover together, share your ASN and prefix details. Talk to the technical team or start with the 7-day free trial.

All posts

Let’s review the right protection model for your network together.

Contact our team to talk through your technical needs.