Configure OSPF routing on the Operations Manager

The following article provides an example of configuring the Operations Manager to be an OSPF neighbor to a Cisco router (or similar). Utilizing OSPF on the Operations allows users to integrate into their enterprise while learning routes dynamically without the need for static routing entries. The example assumes the Cisco router is already configured per the below diagram.

Note: Router config snippets are located at the bottom of the page.

OM Configuration Steps

1. Enable OSPF through the Web UI.

To enable Dynamic Routing on the Operations Manager, navigate to the CONFIGURE > SERVICES > Routing page.

• Tick OSPF
• Click Apply

Optionally, the routing services can be enabled within the CLI, however, will not persist after reboot. Example below of starting and showing status of ospfd in CLI. Start zebra and ospfd services.

root@om2224-24e-l:~# systemctl start zebra
root@om2224-24e-l:~# systemctl start ospfd

2. Allow OSPF on the built in Operations Manager firewall through the Web UI.

To allow OSPF service to operate over the NET1 interface, navigate to CONFIGURE > FIREWALL > Management page.

• Click WAN then Edit Zone
• Scroll down to Permitted Services
• In the left hand column, click + to add the OSPF service
• Click Apply

 

3. Configure OSPF on the OM.

Access the Quagga shell typing “vtysh” in the Operations Manager CLI. Once in the shell, enter the commands in the snippet below.

root@om2224-24e-l:~# vtysh

Hello, this is Quagga (version 1.2.4).
Copyright 1996-2005 Kunihiro Ishiguro, et al.

om2224-24e-l# conf t
om2224-24e-l(config)# router ospf
om2224-24e-l(config-router)# router-id 0.0.0.2
om2224-24e-l(config-router)# log-adjacency-changes
om2224-24e-l(config-router)# passive-interface net2
om2224-24e-l(config-router)# exit
om2224-24e-l(config)# interface net1
om2224-24e-l(config-if)# ip ospf area 0.0.0.0
om2224-24e-l(config-if)# interface net2
om2224-24e-l(config-if)# ip ospf area 0.0.0.0
om2224-24e-l(config)# exit
om2224-24e-l# wr mem
Building Configuration...
Configuration saved to /etc/quagga/zebra.conf
Configuration saved to /etc/quagga/ospfd.conf
[OK]
om2224-24e-l# exit
root@om2224-24e-l:~#

To verify the configuration, type is show run while in the Quagga vtysh session. You can also verify the config by viewing /etc/quagga/ospfd.conf.

Alternatively to configuring through the Quagga vtysh, you can edit /etc/quagga/ospfd.conf. Once changes are made, restart the ospfd service by issuing systemctl restart ospfd.

4. Verify OSPF neighbor on the Operations Manager.

To verify an OSPF neighbor, use command show ip ospf neighbor in the Quagga vtysh session.

om2224-24e-l# show ip ospf neighbor

Neighbor ID Pri State Dead Time Address Interface RXmtL RqstL DBsmL
0.0.0.1 1 Full/DROther 31.528s 10.10.0.1 net1:10.10.0.2 0 0 0
om2224-24e-l#

To check if the routes are being learned, use command show ip route in the Quagga vtysh session. Look for routes with code O.

om2248-FL# show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
O - OSPF, I - IS-IS, B - BGP, P - PIM, A - Babel, N - NHRP,
> - selected route, * - FIB route

C>* 10.10.0.0/24 is directly connected, net1
O>* 10.10.0.2/32 [110/0] is directly connected, net1, 08:12:56
O>* 10.10.0.1/32 [110/0] via 10.10.0.1, net1, 08:12:56
O>* 192.168.1.0/32 [110/0] via 10.10.0.1, net1, 08:12:56
C>* 192.168.2.0/24 is directly connected, net2
O 192.168.2.1/32 [110/0] is directly connected, net2, 22:48:43
om2248-FL#

Router Configs

Cisco Router Config

interface GigabitEthernet0/0
ip address 10.10.0.1 255.255.255.0
!
interface GigabitEthernet0/1
ip address 192.168.1.1 255.255.255.0
!
router ospf 10
router-id 0.0.0.1
network 10.100.0 0.0.0.255 area 0
network 192.168.1.0 0.0.0.255 area 0

Operations Manager ospfd.conf

interface net1
ip ospf area 0.0.0.0
!
interface net2
ip ospf area 0.0.0.0
!
router ospf
ospf router-id 0.0.0.2
log-adjacency-changes
!
line vty