Distributed Cloud Customer Edge Custom VIP with BGP Advertisement Configuration

This repo will provide a solution to introduce a process to configure a Custom VIP Advertisement on a Customer Edge with BGP

Prerequisite

Minimun requirements needed for this environment:
  • Im using a Distributed Cloud Site configured with the Secure Mesh Site Version 2 (SMSv2). You can use a general site or SMSv1 Legacy Site as well.

  • Our example we will use a vmware site (called netta-bgp) configured with SMSv2 and 2 interfaces ens192 (SLO) and ens224 (SLI)

  • We will use ens224 to establish BGP with a VYOS Router

  • Customer Edge Deployed and connected to network for L4-L7 Load Balancing.

  • Have a connection between the network and Customer Edge that has the capability to utilize eBGP.

  • F5 XC Advanced Networking BGP

Highlevel topology below:

../_images/bgp_example_topology.png

Review

Before we jump in if you need a refresher please see the following articles:

BGP Configuration

As stated and shown above in the prerequisite and topology sections we have the following setup:
  • Distributed Cloud Site configured with the Secure Mesh Site Version 2 (SMSv2).

  • Our example we will use a vmware site (called netta-bgp) configured with SMSv2 and 2 interfaces ens192 (SLO) and ens224 (SLI)

  • We will use ens224 to establish BGP with a VYOS Router

../_images/bgp_ce_site_netta_bgp.png
Vyos Config:
  • VYOS Router configured to establish BGP on ethernet 1 interface peering to IP 192.168.20.10 and remote ASN 65519 with local ASN of 65520.

  • In my config example I have 2 peers in the configuration we will only focus on the one

../_images/bgp_vyos_config.png
Distributed Cloud BGP CE Config:
  • Goto Multi-Cloud Network Connect

  • Networking
    • BGPs
      • Add BGP

../_images/bgp_xc_ce_config_1.png
  • On the BGP Screen Provide:
    • Name

    • Description (optional)

    • Site
      • Example site - netta-bgp

    • ASN
      • Example ASN-65519

    • Router ID
      • Example From Interface Add

    • Peers

  • Add Item

../_images/bgp_xc_ce_config_2.png
  • On the BGP Screen Provide:
    • Name

    • Description (optional)

    • Peer Type
      • External

    • ASN
      • Example 65520

    • Peer Address
      • Example 192.168.20.1

    • Peer Port
      • 179

    • Peer Interface
      • Chose interface on CE my example is ens224.

      • If using a 3 node cluster or a multi-node virtual site you need to configure for each node interface individually

    • Apply

  • Bottom Right
    • Save and Exit

../_images/bgp_xc_ce_bgp_peer_config_3.png
Now that we have established a BGP peering relationship between the Customer Edge and Vyos Router we need to create a HTTP LB with a healthy origin to advertise the /32 VIP into the network
  • Goto Multi-Cloud App Connect
    • Manage
      • HTTP LB
        • Add HTTP LB

../_images/bgp_xc_http_lb.png
  • Fill out HTTP LB Values

  • Include an active or healthy origin

  • Goto Other Settings
    • VIP Advertisement
      • Custom

../_images/bgp_xc_other_settings_vip.png
  • Configure
    • Select Site
      • Choose which network to Advertise the VIP on my example is the Inside

    • Site Reference is the CE Site My example
      • System/netta-bgp

    • Custom VIP you want to advertise
      • Example - 10.200.200.100

../_images/bgp_vip_config.png

BGP Validation

We will see the output of the vyos router and CE bgp commands:

Vyos Output:

../_images/bgp_vyos_output.png

Customer Edge Output:

  • Goto Multi-Cloud Network Connect
    • CE Site
      • Tools
        • Show BGP Peers

        • Show BGP Route

../_images/bgp_ce_output.png