How to configure OSPF on Omada Gateway via Standalone Webpage

Configuration Guide
Updated 11-05-2024 02:04:16 AM 78
This Article Applies to: 

Contents

Objective

Requirements

Introduction

Configuration

Conclusion

FAQ

Objective

This article uses a typical configuration example to describe how to configure OSPF on Omada Gateway via standalone webpage. Note that the OSPF configuration is supported only in Standalone mode.

Requirements

  • Omada Gateway series
  • OSPF Area & Network
  • PC LAN Connection

Introduction

The Omada Gateway OSPF function is an internal gateway protocol. It uses the SPF algorithm to exchange routing information to make routing decisions within a single AS.

The common OSPF scenario is shown below:

Gateway 1 is connected to the LAN sides of Gateway 2 and Gateway 3 respectively and there is no connection between Gateway 2 and Gateway 3. By configuring OSPF, Gateway 2's LAN 4 and Gateway 3's LAN 3 can achieve routing communication.

Common OSPF scenario topology here takes three gateways as examples.

Gateway Configuration:

Router-id

LAN IP

Gateway 1

1.1.1.1

LAN 1:10.1.1.1/24

LAN 2:192.168.1.1/24

Gateway 2

2.2.2.2

LAN 1:10.1.1.2/24

LAN 4:172.16.0.1/16

Gateway 3

3.3.3.3

LAN 2:192.168.1.2/24

LAN 3:192.168.101.1/24

OSPF Area:

Area ID

Network

0 (backbone)

10.1.1.0/24

1

192.168.1.0/24、192.168.101.0/24

2

172.16.0.0/16

Configuration

Step 1. OSPF Global Config & OSPF Config.

Log in to a standalone webpage, go to Transmission > Routing > OSPF > OSPF Global Config, set Status to Enable, and set Router ID to Manual.

Note: If the Router ID is set to Auto, the IP address of the smallest interface on the current device will be automatically set as the OSPF Router ID.

Gateway 1:

Fill in the OSPF global configuration and OSPF configuration for gateway 1, including Status/Router ID.

Gateway 2:

Fill in the OSPF global configuration and OSPF configuration for gateway 2, including Status/Router ID.

Gateway 3:

Fill in the OSPF global configuration and OSPF configuration for gateway 3, including Status/Router ID.

Keep the default parameters in Transmission > Routing > OSPF > OSPF Config.

Step 2. Configure OSPF Network.

Go to Transmission > OSPF > Network Table and click Add to add the LAN to OSPF Area.

Gateway 1:

Add LAN 1 to Area 0:

Configure OSPF network of gateway 1, add LAN1 to OSPF area 0 in standalone webpage.

Add LAN 2 to Area 1:

Configure OSPF network of gateway 1, add LAN2 to OSPF area 1 in standalone webpage.

Gateway 2:

Add LAN 1 to Area 0:

Configure OSPF network of gateway 2, add LAN1 to OSPF area 0 in standalone webpage.

Add LAN 4 to Area 2:

Configure OSPF network of gateway 2, add LAN4 to OSPF area 2 in standalone webpage.

Gateway 3:

Add LAN 2 to Area 1:

Configure OSPF network of gateway 3, add LAN2 to OSPF area 1 in standalone webpage.

Add LAN 3 to Area 1:

Configure OSPF network of gateway 3, add LAN3 to OSPF area 1 in standalone webpage.

Step 3. Check OSPF neighbor status and OSPF LSDB.

Go to Transmission > OSPF > Neighbor Table and click Refresh to update the table. The state should be Full/DR or Full/Backup.

Gateway 1:

Check OSPF neighbor status and OSPF LSDB of gateway 1, The state should be Full/DR or Full/Backup.

Gateway 2:

Note: LAN 4 only imports OSPF Network and is not connected to other OSPF neighbors. Therefore, the LAN 4 of Area 2 will not be displayed in the Neighbor Table.

Check OSPF neighbor status and OSPF LSDB of gateway 2, The state should be Full/DR or Full/Backup.

Gateway 3:

Note: LAN 3 only imports OSPF Network and is not connected to other OSPF neighbors. Therefore, the LAN 3 of Area 1 will not be displayed in the Neighbor Table.

Go to Transmission > Routing > OSPF > Link State Database and click Refresh to update the statistics.

Check OSPF neighbor status and OSPF LSDB of gateway 3, The state should be Full/DR or Full/Backup.

Gateway 1:

  • Area 0

LSA Type – Router, Router ID for Gateway 1 and Gateway 2;

LSA Type – Network, network address for Area 0;

LSA Type – Network-Summary, network address for Area 1 and Area 2;

  • Area 1

LSA Type – Router, Router ID for Gateway 1 and Gateway 3;

LSA Type – Network, network address for Area 1;

LSA Type – Network-Summary, network address for Area 0 and Area 2.

Check the link state database of gateway 1.

Gateway 2:

  • Area 0

LSA Type – Router, Router ID for Gateway 1 and Gateway 2;

LSA Type – Network, network address for Area 0;

LSA Type – Network-Summary, network address for Area 1 and Area 2;

  • Area 2

LSA Type – Router, Router ID for Router 2, no neighbors;

LSA Type – Network, no network address for Area 2 as there are no neighbors;

LSA Type – Network-Summary, network address for Area 0 and Area 1.

Check the link state database of gateway 2.

Gateway 3:

  • Area 1

LSA Type – Router, Router ID for Gateway 1 and Gateway 3;

LSA Type – Network, network address for Area 2

LSA Type – Network-Summary, network address for Area 0 and Area 2

Check the link state database of gateway 3.

Step 4. Go to Transmission > Routing > Routing Table to check the routing table and see if there is a global LAN route.

Gateway 1:

Check the routing table of gateway 1.

Gateway 2:

Check the routing table of gateway 2.

Gateway 3:

Check the routing table of gateway 3.

Note:

  • Plan the OSPF area division in advance to ensure that all non-backbone areas are connected to the backbone Area 0.
  • Go to Transmission > OSPF > Interface Table and ensure that the network type of each link is consistent with the actual network.

Ensure that the network type of each link is consistent with the actual network.

  • Some models (ER8411, ER605 V2, ER7206 V1) currently only support OSPF Global Config; that is, when configuring Area ID in Transmission > OSPF Global Config, Area ID is not filled based on the network segment, and all networks should be in the same Area, but the configuration process is similar.

Configure OSPF area ID in standalone webpage.

Conclusion

You have now successfully configured OSPF on the Omada Gateway.

Get to know more details of each function and configuration please go to Download Center to download the manual of your product.

FAQ

Q1. Can OSPF establish WAN network neighbors to calculate routes?

Re. OSPF is working within a single AS. Usually the WAN network of the Gateway belongs to a different AS, which exceeds the capability of OSPF. Therefore, the WAN address will not be used directly to establish OSPF neighbors. To protect the user's private network, the access from WAN to LAN will be filtered.

If you need to establish an OSPF neighbor relationship with a specified remote end through the WAN, you can select a VPN to establish a connection first. Take GRE VPN as an example (for the configuration of GRE VPN, refer to the relevant configuration guide):

Go to Transmission > OSPF > Network Table, and add the GRE IP of the GRE VPN to the OSPF Area. Because the GRE IP is a point-to-point connection, you need to fill in the GRE IP of the other end. Fill in "0.0.0.0" in Wildcard Mask to represent a 32-bit mask.

Q2. What should I do if the state of OSPF neighbor is not Full?

Re. You can check the following:

  • Check whether the Working state of the interface in the Interface Table is on;
  • Check whether the OSPF neighbor parameters, area number, network type, subnet, and mask are configured correctly (point-to-point links require the peer address);
  • Go to System Tools > Diagnostics, and select Ping as the Diagnostic Tool to ping peer address to check network connectivity;
  • Check the time parameters. The neighbor expiration time is at least 4 times the Hello sending interval;
  • If the state is Exstart/Exchange/Loading, the connection has been established and the link database is being exchanged. If the routing scale is large, it takes some time to reach the Full state.

Is this faq useful?

Your feedback helps improve this site.

Recommend Products

Community

TP-Link Community

Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.

Visit the Community >