Configuration Guide How to Configure OSPF on Omada Router in Standalone Mode
Background:
This post provides a comprehensive configuration guide on OSPF on Omada router in standalone mode.
This Article Applies to:
Omada routers with OSPF feature supported.
Application Scenario:
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 Steps:
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:
Gateway 2:
Gateway 3:
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:
Add LAN 2 to Area 1:
Gateway 2:
Add LAN 1 to Area 0:
Add LAN 4 to Area 2:
Gateway 3：
Add LAN 2 to Area 1:
Add LAN 3 to Area 1:
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:
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.
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.
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.
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.
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
Step 4. Review the Routing Table and OSPF to see if it is effective.
Go to Transmission > Routing > Routing Table to check the routing table and see if there is a global LAN route.
Gateway 1:
Gateway 2:
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.
- 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.
QA:
Q1. Can OSPF establish WAN network neighbors to calculate routes?
A1: 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?
A2: 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.
Update Log:
Nov 6th, 2024:
Release of the article.
Recommended Threads:
How to Configure GRE VPN on Omada Router
Configuration Guide How to Configure WireGuard VPN on Omada Controller
Feedback:
- If this was helpful, welcome to give us Kudos by clicking the upward triangle below.
- If there is anything unclear in this solution post, please feel free to comment below.
Thank you in advance for your valuable feedback!
------------------------------------------------------------------------------------------------
Have other off-topic issues to report?
Welcome to > Start a New Thread < and elaborate on the issue for assistance.