The following section guides you through the configuration of OSPF and OSPFv3 for Quagga service. The routers in your network must be configured for use with OSPF or OSPFv3 in order to use Anycast.
For more details on Quagga OSPF, visit the Quagga website:
- For information on configuring OSPF for IPv4, see https://www.nongnu.org/quagga/docs/docs-multi/OSPFv2.html.
- For infomration on configuring OSPF for IPv6, see https://www.nongnu.org/quagga/docs/docs-multi/OSPFv3.html.
Configuring the OSPF service in an IPv4 environment
The following steps illustrate configuration of the following OSPF topology for IPv4.
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.
- Complete the following:
In the Description field, enter a name for the new loopback address. You can enter up to 80 alphanumeric characters including spaces, but excluding special characters.
In the Address/CIDR field, enter 10.0.0.1/32.
Click Add Address. The loopback address appears in the Addresses list.
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.)
Log in to the Gateway instance that has the Distributed DDNS Application Node.
Under Available Actions, click Distributed DDNS.
Click the Service Nodes tab to access the service node page.
Click Anycast service.
Under the Configuration tab, select OSPF.
In the configuration window, enter the following information, changing commands as needed to fit your system topology, addresses, and business needs:
!ospf.conf hostname quagga_01 ! interface ens33 ! interface lo ! router ospf ospf router-id 6.0.0.2 network 6.0.0.0/8 area 0.0.0.0 network 10.0.0.1/32 area 0.0.0.0 ! line vty ! log trap informational log stdout log file /var/log/quagga/ospfd.log log record-priority !Where the parameters represent the following:hostname quagga_01: Sets the hostname of the router toquagga_01interface ens33: Configures the interface to up.router ospf: Enable the OSPF process. ospfd does not support multiple OSPF processes. You cannot specify an OSPF process number.ospf router-id 6.0.0.2: Set the router-ID of the OSPF process. The router-ID can be an IP address of the router but can also be configured to any 32-bit number.network 6.0.0.0/8 area 0.0.0.0: Specifies the OSPF enabled interface. If the interface has an address range then the command enables OSPF on this interface so that the router can provide network information to other OSPF routers through this interface.line vty: Enter the vty configuration mode.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 tostdout.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.
When you're done, click Save to save the BGP service configuration.
After the changes are saved, click Start to start the OSPF service and add it to the Distributed DDNS Service Node.
You can now continue with the next Service Node.
Configuring the OSPFv3 service in an IPv6 environment
The following steps illustrate configuration of the following OSPFv3 topology for IPv6.
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.
- Complete the following:
In the Description field, enter a name for the new loopback address. You can enter up to 80 alphanumeric characters including spaces, but excluding special characters.
In the Address/CIDR field, enter 2a01:278:1:f:10:0:0:1/128.
Click Add Address. The loopback address appears in the Addresses list.
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.)
Log in to the Gateway instance that has the Distributed DDNS Application Node.
Under AVAILABLE ACTIONS, click Distributed DDNS.
Click the Service Points tab to access the service node page.
Click Anycast service.
Under the Configuration tab, select OSPFv3.
In the configuration window, enter the following information, changing commands as needed to fit your system topology, addresses, and business needs:
!ospfd configuration ! router ospf6 router-id 9.0.0.9 interface lo area 0.0.0.0 interface ens33 area 0.0.0.0 redistribute connected ! log trap informational log stdout log file /var/log/quagga/ospf6d.log log record-priority !When you're done, click Save to save the OSPFv3 service configuration.
After the changes are saved, click Start to start the OSPFv3 service and add it to the Distributed DDNS Service Node.
You can now continue with the next Service Node.