Static routes are then published to OSPF.

OSPF routing protocol is often used in large networks. For example, the municipal unit center 7513 is used as the core device. The OSPF protocol is used in connection with the Provincial Unit at the upper level, subordinate county-level units connect to access routes such as 3745, 3600, and 2600, and also use OSPF. At the next level, lower-level units such as 1721 are connected, due to the limited CPU processing capability of 1721, when the OSPF routing protocol is used, there are hundreds of routes in the network and these routes will be in the area allocated by the superiors. The CPU utilization is very high and the processing speed is very slow, so we use the Static Routing Protocol at this level, so it will be involved in county-level units such as 3745, 3600, and 2600, and the static routing will be published to OSPF, so we will use the command:
Router (config) # router ospf 100
Router (config-router) # redistrbute static
In the actual project, after using this command, the problem could not be solved in some places. Later, I tried to use the parameter SUBNETS following it, and the problem was solved.

There are many parameters after Static Routing is published to OSPF.
Static Routing is then published to OSPF. parameters include metric, route-map, subnets, and tag.
Metric: Any parameter used to specify the Metric value of the route to be published. The default value is 20, E1 is 1, and E2 is 2.
Route-map: Any parameter that identifies a configured Route image. The routing image is used to filter the Route input from the source Route selection Protocol specified earlier to the current Route protocol.
Subnets: Any parameter that specifies that the subnet route should also be published.

Tag: Optional 32-bit decimal value, attached to an external route.