> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/tests/bgp-tests/private-bgp-monitoring/configuring-an-enterprise-agent-with-bgp-route-collector.md).

# Configuring Private BGP Monitoring with Enterprise Agents

ThousandEyes already supports private BGP monitoring through a direct eBGP connection between your router and a ThousandEyes-hosted route collector. That collection method provides your router's view of routes to internet destinations without an Enterprise Agent.

This article describes the Enterprise Agent collection method, which adds local collection to the same private BGP monitoring workflow. Enable the **BGP Route Collector** module on an Enterprise Agent to collect routing updates through local external Border Gateway Protocol (eBGP) sessions with your routers. The module supports private autonomous system (AS) numbers, private prefixes, or both.

The Enterprise Agent relays the collected routing telemetry to ThousandEyes over its existing secure, authenticated HTTPS connection. Your router peers with the collector inside your network rather than with a ThousandEyes-hosted collector. The router's BGP export policy determines which routes the collector receives.

For a comparison of both collection methods and the hosted-collector configuration procedure, see [Private BGP Monitoring](/product-documentation/tests/bgp-tests/private-bgp-monitoring.md#choosing-a-collection-method).

## Use Cases

Use an Enterprise Agent with BGP Route Collector to:

* Monitor private networks that use eBGP with private AS numbers or private prefixes.
* Keep BGP collection local to your network by peering your routers with an Enterprise Agent deployed within your security perimeter. The BGP Route Collector then sends the data to ThousandEyes over an encrypted HTTPS connection.
* Investigate unexpected route announcements and withdrawals, reachability changes, and suspected routing misconfigurations in near real time or through historical data for forensic analysis.
* Identify routing changes and where they were observed. Then compare routing events with network and application performance to assess user impact.

## Before You Begin

Install an Enterprise Agent or deploy a ThousandEyes Virtual Appliance (TEVA). You can also use an existing Enterprise Agent or TEVA that meets the requirements in this section. For supported operating systems and general host requirements, see [Enterprise Agents](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents). For installation instructions, see [Linux Package Agent Installation](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/installing/linux-package-agent-installation) or [ThousandEyes Virtual Appliance Installation](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/installing).

Before you enable the **BGP Route Collector** module, verify that the Enterprise Agent host meets these BGP-specific requirements:

| Requirement            | Required Value                                                     |
| ---------------------- | ------------------------------------------------------------------ |
| Compute                | 3 vCPUs                                                            |
| Memory                 | 4 GB                                                               |
| Disk                   | 30 GB                                                              |
| Operating system       | A supported Linux distribution                                     |
| Internet connectivity  | Outbound HTTPS; a proxy is acceptable                              |
| Local BGP connectivity | Bidirectional TCP port 179 between the router and Enterprise Agent |
| IP support             | IPv4, IPv6, or both                                                |
| Clustered              | No                                                                 |

For general Enterprise Agent connectivity requirements, see [Firewall Configuration for Enterprise Agents](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/configuring/firewall-configuration-for-enterprise-agents). If the Enterprise Agent connects to ThousandEyes through a proxy, see [Configuring an Enterprise Agent to Use a Proxy Server](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/proxy/configuring-an-enterprise-agent-to-use-a-proxy-server).

{% hint style="info" %}
The compute, memory, and disk requirements in this article are specific to the **BGP Route Collector** module and are based on collecting up to one million routes. They might exceed the general Enterprise Agent requirements. If the router exports more than one million routes to the collector, allocate additional memory.
{% endhint %}

### Permissions and Information to Collect

Before you begin, collect the following information and confirm that you have the required access:

* A ThousandEyes role with the *Edit agents in account group* and *Edit BGP monitors* permissions.
* Administrative access to the Enterprise Agent host and configuration access to the monitored router.
* The router IP address and local AS number for the BGP session.
* If you plan to use TCP MD5 authentication, a password configured on both BGP peers.

For details about ThousandEyes permissions, see [Built-In Roles and Permissions](https://docs.thousandeyes.com/product-documentation/user-management/authorization/rb-access-control/built-in-roles-and-permissions).

## Workflow Overview

1. [Install the Enterprise Agent](#installing-the-enterprise-agent): Generate the installation commands in the ThousandEyes platform, then run them on the Enterprise Agent host.
2. [Enable BGP Route Collector](#enabling-the-bgp-route-collector-module): Enable the module on the Enterprise Agent.
3. [Create a Private BGP Monitor](#create-a-private-bgp-monitor-by-peering-with-an-enterprise-agent): Associate the monitor with the Enterprise Agent that hosts the collector.
4. [Configure the Router BGP Session](#configuring-the-router-bgp-session): Configure the monitored router to peer with the Enterprise Agent.
5. [Validate the Installation](#validating-the-installation): Verify the agent, collector, BGP session, and route data.

## Installing the Enterprise Agent

### Choose an Installation Path

* **Existing Enterprise Agent or TEVA:** If you already have an Enterprise Agent or TEVA that meets the requirements in [Before You Begin](#before-you-begin), continue to [Enabling the BGP Route Collector Module](#enabling-the-bgp-route-collector-module).
* **New TEVA:** If you are deploying a TEVA, follow [ThousandEyes Virtual Appliance Installation](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/installing), and then continue to [Enabling the BGP Route Collector Module](#enabling-the-bgp-route-collector-module).
* **New Linux package agent:** If you need to install an Enterprise Agent as a Linux package, complete the following steps.

1. Prepare an on-premises Linux host that meets the requirements in [Before You Begin](#before-you-begin).
2. In ThousandEyes, select **Network & App Synthetics > Agent Settings**, and then select **Add New Enterprise Agent**.
3. In the dialog, select the **Linux Package** tab.
4. Copy the installation commands generated by the ThousandEyes platform and run them on the host.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>Use the account group token displayed for the current account group. Do not use a token from another account group.</p></div>
5. Return to **Network & App Synthetics > Agent Settings > Enterprise Agents** and confirm that the new Enterprise Agent appears in the list.

For complete installation instructions, including proxy configuration and time synchronization, see [Linux Package Agent Installation](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/installing/linux-package-agent-installation).

## Enabling the BGP Route Collector Module

1. In **Network & App Synthetics > Agent Settings > Enterprise Agents**, select the Enterprise Agent.
2. In the agent details panel, select the **Advanced Settings** tab.
3. Enable **BGP Route Collector**.

   ThousandEyes installs the BGP Route Collector components on the Enterprise Agent host.
4. Wait for the Enterprise Agent to check in and complete the installation.

   The installation runs in the background. When the module is ready, the Enterprise Agent appears in the list of available agents when you create or edit a private BGP monitor with the **Enterprise Agent** connection type.

## Create a Private BGP Monitor by Peering with an Enterprise Agent

Use this procedure to create a private BGP monitor by establishing a BGP peering session between your router and an Enterprise Agent. To peer with a ThousandEyes-hosted route collector instead, see [Configuring a Private BGP Monitor with a ThousandEyes-Hosted Route Collector](/product-documentation/tests/bgp-tests/private-bgp-monitoring.md#configuring-a-private-bgp-monitor).

1. In ThousandEyes, go to **Routing > Private BGP Monitors**, and then select **Add Private BGP Monitor**.
2. Enter the BGP peer information:

   | Field                | Value                                                                                                                                                         |
   | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | **Monitor Name**     | Enter a descriptive name, such as the router or site name.                                                                                                    |
   | **IP Address**       | Enter the IP address of the router's BGP interface. Unlike a ThousandEyes-hosted collector, this address can be private if the Enterprise Agent can reach it. |
   | **AS Number**        | Enter the local AS number configured on the router.                                                                                                           |
   | **TCP MD5 Password** | Optional. Enter the password configured for the BGP peer.                                                                                                     |
3. Under **Select Connections**, select **Enterprise Agent**.
4. Under **Agent**, select the Enterprise Agent that has the **BGP Route Collector** module enabled.

   If multiple Enterprise Agents are available, select the agent closest to the monitored router and with sufficient capacity for the expected route volume.
5. Select **Create BGP Monitor**.

   ThousandEyes associates the monitor with the selected Enterprise Agent. The monitor displays a **Pending** status until you configure the router and establish the BGP session. It then becomes **Active**.

## Configuring the Router BGP Session

Configure the router to use the Enterprise Agent private IP address as its BGP neighbor. Use AS 50414 as the remote AS, configure eBGP multihop with a minimum value of two, and preserve the next-hop information. For example, use **next-hop-unchanged** on Cisco XE/XR routers. Other router platforms provide equivalent commands.

{% hint style="warning" %}
Do not use the peer address or AS 65315 associated with a ThousandEyes-hosted route collector. An Enterprise Agent with BGP Route Collector uses its private IP address and AS 50414.
{% endhint %}

The following IPv4 example shows a Cisco IOSv configuration. Replace the placeholders with values from your environment, and adapt the commands for your router platform and software version.

```
router bgp <router-local-as>
 neighbor <agent-private-ip> remote-as 50414
 neighbor <agent-private-ip> ebgp-multihop 2
 !
 address-family ipv4 unicast
  neighbor <agent-private-ip> activate
  neighbor <agent-private-ip> next-hop-unchanged allpaths
 exit-address-family
```

* Replace *router-local-as* with the AS number that you entered when you created the private BGP monitor.
* Replace *agent-private-ip* with the private IP address displayed for the Enterprise Agent in **Network & App Synthetics > Agent Settings > Enterprise Agents**.
* If you entered a **TCP MD5 Password** when you created the monitor, configure the same password on the router. TCP MD5 authenticates the BGP session; it does not encrypt the routing data between the router and the collector.
* Have qualified network personnel review and apply the configuration.

{% hint style="info" %}
This example configures the IPv4 unicast address family. If you use IPv6, configure the equivalent IPv6 address family and neighbor settings for your router platform.
{% endhint %}

## Validating the Installation

Before you finish, verify the deployment:

| Check               | Expected Result                                                                                                                                                                                                                                                                               |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Enterprise Agent    | The agent is online in **Network & App Synthetics > Agent Settings > Enterprise Agents**.                                                                                                                                                                                                     |
| BGP Route Collector | The Enterprise Agent appears in the list of available agents for the **Enterprise Agent** connection type when you create or edit a private BGP monitor.                                                                                                                                      |
| Router session      | The router reports the neighbor at *agent-private-ip* as established.                                                                                                                                                                                                                         |
| Private BGP monitor | The monitor is **Active** in **Routing > Private BGP Monitors**.                                                                                                                                                                                                                              |
| Peer identity       | The monitor IP address and AS number match the router configuration.                                                                                                                                                                                                                          |
| Route data          | Add the monitor to a BGP test or a supported test with BGP data collection enabled to view routes in **BGP Updates** or **BGP Route Visualization**. Go to **Routing > Looking Glass** to view routes received by the collector and review the historical routing state of internal prefixes. |

{% hint style="info" %}
An **Active** monitor confirms that the BGP session is established. Route data appears after you add the monitor to a BGP test or a supported test with BGP data collection enabled.
{% endhint %}

For information about reviewing collected routing data, see [Using the BGP Updates Table](https://docs.thousandeyes.com/product-documentation/tests/bgp-tests/using-the-bgp-updates-table) and [Using the BGP Route Visualization View](https://docs.thousandeyes.com/product-documentation/tests/bgp-tests/using-the-bgp-route-visualization-view).

## Managing a Private BGP Monitor

You can change the Enterprise Agent associated with an existing private BGP monitor. However, you cannot change the connection type between **Enterprise Agent** and a ThousandEyes-hosted route collector. To use a different connection type, delete the monitor and create a new one.

## Troubleshooting the BGP Session

If the private BGP monitor does not become **Active**, perform the following checks in order:

1. Confirm that the Enterprise Agent is online and that **BGP Route Collector** is enabled on the **Advanced Settings** tab. When you create or edit a private BGP monitor, confirm that the agent appears in the agent dropdown list.
2. Verify that the router uses the intended Enterprise Agent's IP address as its BGP neighbor.
3. Verify the router's local AS, remote AS 50414, address-family activation, eBGP multihop setting, and next-hop preservation configuration.
4. Confirm bidirectional connectivity between the router and the Enterprise Agent. Verify that the router can establish a TCP connection to port 179 on the Enterprise Agent. Check firewall or access control list logs for blocked traffic.
5. If TCP MD5 authentication is enabled, verify that both peers use the same password. Confirm that no device performs network address translation (NAT), port address translation (PAT), or TCP-field rewriting between the peers.
6. Refresh **Routing > Private BGP Monitors** and confirm that the monitor becomes **Active**.
7. Confirm that the expected monitor and route data appear in **Looking Glass**, **BGP Updates**, or **BGP Route Visualization**.

If the Enterprise Agent is offline or the BGP Route Collector does not install, review the installer output, outbound HTTPS connectivity, package-repository access, proxy configuration, and time synchronization. For more information, see:

* [Linux Package Agent Installation](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/installing/linux-package-agent-installation)
* [Installing Enterprise Agents in Proxy Environments](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/proxy/installing-enterprise-agents-in-proxy-environments)
* [Firewall Configuration for Enterprise Agents](https://docs.thousandeyes.com/product-documentation/global-vantage-points/enterprise-agents/configuring/firewall-configuration-for-enterprise-agents)
