>
    Strata Copilot
    Recover BGP Session and Route Re-convergence
    Focus
    Download PDF
    Focus
    1. Home
    2. Prisma SD-WAN
    3. Prisma SD-WAN Administrator’s Guide
    4. Prisma SD-WAN ION Recovery and Debugging Mechanism
    5. Recover BGP Session and Route Re-convergence
    Download PDF
    Prisma SD-WAN

    Recover BGP Session and Route Re-convergence

    Table of Contents

    Recover BGP Session and Route Re-convergence

    Diagnose and restore a BGP session on a Prisma SD-WAN ION device and verify that routes are correctly programmed in the forwarding table.
    Where Can I Use This?What Do I Need?
    • Prisma SD-WAN (Managed by Strata Cloud Manager)
    • Prisma SD-WAN license
    • Network Administrator or Superuser role
    When a BGP session drops on a Prisma SD-WAN ION, routes from the BGP peer stop being advertised into the forwarding table, which can cause traffic blackholing for prefixes that depend on that session. This procedure verifies session state, checks that routes are programmed, and confirms reachability for affected prefixes.
    1. Check whether the BGP session is up by running the following CLI command:
      dump routing peer status all
      Review the State/PfxRcd column in the output:
      • A numeric value (for example, 3) indicates the session is up and the peer is advertising that many prefixes.
      • A state of Idle, Active, or Connect indicates the session is down. Before proceeding, verify the following:
        • The BGP peer IP and AS number match on both sides.
        • No firewall or policy is blocking TCP port 179 between peers.
        • If BGP authentication is configured, keys match on both sides.
    2. Verify that routes from the BGP peer are programmed in the forwarding table. First, run dump vpn ha all and note the vpnlink_id for the target site and active ION. Then use that value as the path-id:
      inspect fib path-id=<vpnlink_id>
      Confirm that the expected prefixes appear in the output under the path.
    3. Check reachability for a specific prefix. Replace <prefix> with the prefix you are troubleshooting in CIDR notation (for example, 192.168.2.0/24):
      dump routing prefix-reachability prefix=<prefix>
      Review the output to confirm the prefix is reachable and note the path type shown (public-direct, private-wan, public-vpn, or private-vpn). Verify the path type matches what is expected for this site.
    4. Verify the route manager process is running:
      debug process status name=rtr_mgr_api
      Expected output shows RUNNING with a stable uptime. A recent restart or STOPPED state requires escalation to Palo Alto Networks support.
    5. If the issue is not resolved, contact Palo Alto Networks support for route manager log analysis.

    © 2026 Palo Alto Networks, Inc. All rights reserved.