Running the Anycast configuration utility - BlueCat Edge - Service Point v4.x.x

BlueCat Edge Deployment Guide

Product name
BlueCat Edge
Service Point v4.x.x

The BlueCat Edge Anycast Configuration Utility is designed to help you configure Service Point v3 instances to be added to an Anycast pool.

Before you begin
  • On the computer you use to run the configuration utility, ensure that you are running Python 3.6.5 or greater. In addition, the following Python libraries must be installed:
    • certifi==2018.8.24
    • chardet==3.0.4
    • future==0.16.0
    • idna==2.7
    • requests==2.20.0
    • six==1.11.0
    • urllib3==1.23

    Refer to for more information.

  • This computer should also have access to the Service Point v3 IP on port 443.
  • Log in to the utility using your access key set credentials. Your user account must have administrative access.

Clone the repo and run the configuration utility

  1. In your browser, go to, and clone the anycast-config-utility repository.
  2. On a computer that can access the Service Point v3 IP (port 443), and that's running Python 3, connect to the configuration utility by running any of the commands in the step section under Staging and applying daemon configurations.
  3. When prompted to save your access key set credentials and the Service Point v3 hostname and IP, type Y. A Base64 encoded file named .script_config is created in the same location as the script. This file stores the user information, including the credentials.

    When you no longer need to use the utility, BlueCat recommends that you delete the .script_config file.

    If you need to change your user credentials or connect to a different Service Point v3 instance, rename or delete .script_config and restart the configuration utility.

  4. Enter your client ID and secret access key, and the Service Point v3 hostname or IP address when prompted. Your account must have administrative access.

Staging and applying daemon configurations

About the daemon configuration files:
  • In the following steps, for <daemon>, valid options are zebra, bgpd, and ospfd.
  • In the following steps, for <file>, valid configuration files are zebra.conf, bgpd.conf, and ospfd.conf.
    Note: The anycast configuration utility doesn't validate the content of the configuration files. You must ensure that the content conforms to a valid configuration format based on the zebra.conf, bgpd.conf, or ospfd.conf configuration.
  • When specifying configuration files, provide the full path to the files if they aren't in the same location as the script. If they're in the same location, you only need to provide the file name.
  • Providing a log file path in the configuration files is optional. If the path is provided, it must be /var/log/quagga/{ bgpd | ospfd | zebra }.log, or the request will be rejected with the error Unsucessful status code: Invalid parameters.
About staging and applying configurations:
  • You can choose to stage the configurations in one step (step 2), and then apply them in another (step 3), or you can apply the configurations in one step (step 4).
  • The configuration utility enables and disables daemons when set_run_conf, and no_run_conf commands are made.
  1. If required, set Anycast loopback interfaces. The set_loopbacks command will override all configured loopback IP addresses. A maximum of 255 loopback IPv4 addresses are allowed. Loopback IPs must be specified in a /32 CIDR notation. IPv6 isn't supported. set_loopbacks x.x.x.x/32 y.y.y.y/32 z.z.z.z/32

    To show the configured loopbacks: show_loopbacks

    To remove all configured loopbacks no_loopbacks
  2. To stage daemon configuration files without immediately applying them, and to view or remove the staged configurations, use the following commands:
    • set_staged_conf <daemon> <file.conf>

      For example: set_staged_conf zebra zebra.conf

      In this example, the .conf file is in the same location as the script.

    • show_staged_conf <daemon> <file.conf>
    • no_staged_conf <daemon> <file.conf>
  3. To apply the staged configurations, use the following command:
    • apply
  4. To apply configuration files without first staging them, and to view or remove the applied configurations, use the following commands:
    • set_run_conf <daemon> <file.conf>

      For example: set_run_conf bgpd bgpd.conf

      In this example, the .conf file is in the same location as the script.

    • show_run_conf <daemon> <file.conf>
    • no_run_conf <daemon> <file.conf>
  5. To stop, start, or show running daemons, use the following commands:
    • pause <daemon>
      This stops the daemon. For example: pause bgpd
    • start <daemon>
    • show_daemons


The commands in the following example show the following steps:
  1. Configure Anycast loopbacks
  2. Stage the zebra.conf, then the bgpd.conf, then the ospfd.conf files.

    In this example, the .conf files are in a different location from the script. Note that Windows users should use backslashes in the file path, and Mac users should use forward slashes.

  3. Apply the staged configuration files.
  4. Retrieve the contents of each of the daemon configuration files. set_loopbacks set_staged_conf zebra /home/abc/zebra.conf set_staged_conf bpgd /home/abc/bgpd.conf set_staged_conf ospfd /home/abc/ospfd.conf apply show_run_conf zebra show_run_conf bgpd show_run_conf ospfd

Getting status and troubleshooting information for the running Anycast daemons

For additional troubleshooting information, refer to Service Point v3 diagnostic and health APIs.

  • Run the following command to view the logs for a specified daemon (zebra, ospfd, or bgpd): show_logs <daemon>
  • Run the following command to retrieve information about the state of running Anycast daemons: show_debug <option>

    The available options are:

    Relevant daemon Option Internally wrapped command
    Zebra zebraSummary show zebra client summary
      routes show ip route
      interfaces show interfaces
      runningConfig show running-config
    BGP bgpSummary show ip bgp summary
      bgpNeighbors show ip bgp neighbors
    OSPF ospfNeighbors show ip ospf neighbors
      ospfRoutes show ip ospf route
      ospfRouterInfo show ip ospf router info
      ospfDatabase show ip ospf database