Configuring the BGP service for Anycast - Adaptive Applications - BlueCat Gateway - 23.2.3

Log in to the Address Manager server where the DNS/DHCP Server has been deployed as a service node.

Select the Servers tab.

Under Servers, click the name of the DNS/DHCP Server that the service node has been deployed to.

Click the server name menu button and select Service Configuration.

Under the Interface column, choose the loopback (lo) interface then navigate across the row to the Action column and click Edit.

Click OK. The Edit Interfaces pop-up window closes.

For each service node in your BGP topology, do the following. (In the above example, you would do this for both ServiceNode1 and ServiceNode2.)

1. Log in to the Gateway instance that has the Distributed DDNS Application Node.

2. Under Available Actions, click Distributed DDNS.

3. Click the Service Nodes tab to access the service node page.

4. In the Manage Service Nodes table, in the Anycast column, click the Settings gear icon of the node you want to manage. This icon will be different colors (typically  red at this time) depending on the service status.

   A BGP Service window opens, displaying the current Anycast configuration for the node.

5. In the list box under the Configuration tab, select BGP.

6. In the configuration window, enter the following information, changing commands as needed to fit your system topology, addresses, and business needs:

   !bgpd.conf
   !
   router bgp 200
   network 14.0.0.4/32
   neighbor 11.0.0.3 remote-as 200
   neighbor 11.0.0.3 update-source ens33
   !
   log trap informational
   log stdout
   log file /var/log/quagga/bgpd.log
   log record-priority
   !

   These commands and settings do the following:

   • router bgp 200: Enable a BGP process with the specified Autonomous System Number (ASN). Anycast BGP requires an ASN allocated for each Autonomous System in the Anycast BGP network. Any ASNs used on the internet must be officially registered and allocated by the Internet Assigned Numbers Authority (IANA). If ASNs are only used within a corporate network and the corresponding AS has no direct connection to the internet, then ASNs must be defined within the following range for private use: 64512-65534.

   • network 14.0.0.4/32: Announces the specific network to all neighbors.

   • neighbor 11.0.0.3 remote-as 200: Creates a new neighbor whose remote-as is the asn. The peer can be an IPv4 or IPv6 address.

   • neighbor 11.0.0.3 update-source ens33: Specify the IPv4 source address for use for the BGP session to this neighbour. This can be specified as either an IPv4 address directly or as an interface name (in which case the zebra daemon must be running for bgpd to be able to retrieve the interface state).

   • log trap informational: Sets the current logging level for all enabled logging destinations and sets the default logging level for all future logging commands that do not specify a level.

   • log stdout: Enable logging output to stdout.

   • log file /var/log/quagga/bgpd.log: Enable logging to a log file.

     Note: If you do not configure any file logging and the daemon crashes due to a signal or assertion failure, the service attempts to save the crash information in the /var/tmp/quagga.<daemon_name>.crashlog file. If this file already exists, the service will not save the crash information for security purposes. BlueCat recommends deleting this file after recording or saving the crash information.

   • log record-priority: Includes the severity of all messages logged to a file, stdout, or to a terminal monitor.

7. When you're done, click Save to save the BGP service configuration.

8. After the changes are saved, click Start to start the BGP service and add it to the Distributed DDNS Service Node.

   You can now continue with the next Service Node.

Log in to the Address Manager server where the DNS/DHCP Server has been deployed as a service node.

Select the Servers tab.

Under Servers, click the name of the DNS/DHCP Server that the service node has been deployed to.

Click the server name menu button and select Service Configuration.

Under the Interface column, choose the loopback (lo) interface then, navigate across the row to the Action column and click Edit.

Click OK. The Edit Interfaces pop-up window closes.

For each service node in your BGP topology, do the following. (In the above example, you would do this for both ServiceNode1 and ServiceNode2.)

1. Log in to the Gateway instance that has the Distributed DDNS Application Node.

2. Under Available Actions, click Distributed DDNS.

3. Click the Service Nodes tab to access the service node page.

4. In the Manage Service Nodes table, in the Anycast column, click the Settings gear icon of the node you want to manage. This icon will be different colors (typically  red at this time) depending on the service status.

   A BGP Service window opens, displaying the current Anycast configuration for the node.

5. Under the Configuration tab, select BGP.

6. In the configuration window, enter the following information, changing commands as needed to fit your system topology, addresses, and business needs:

   !bgpd.conf
   !
   router bgp 200
   network 2001:db8:acad:a::1 remote-as 200
   !
   address-family ipv6
   network 2001:200:1:f:10::1/128
   neighbor 2001:db8:acad:a::1 active
   exit-address-family
   !
   log trap informational
   log stdout
   log file /var/log/quagga/bgpd.log
   log record-priority
   !

7. When you're done, click Save to save the BGP service configuration.

8. After the changes are saved, click Start to start the BGP service and add it to the Distributed DDNS Service Node.

   You can now continue with the next Service Node.