Implementing Export Policies - 3Com corebuilder 3500 Implementation Manual

408 C 14: O
HAPTER PEN
Implementing Export
Policies
S P F (OSPF)
HORTEST ATH IRST
Import Example 1: Accept Route
The policy defined in Table 48 imports route 243.140.28.0 into the
routing table and assigns a cost of 10 to the route.
Table 48 Import Policy Example
Policy Field
Policy type
Route address
Route subnet mask
Policy action
Metric adjustment
Administrative weight
Import Example 2: Reject Route
The policy defined in Table 49 prohibits the router from adding route
243.140.28.0 to its routing table.
Table 49 Export Policy Example
Policy Field
Policy type
Route address
Route subnet mask
Policy action
Administrative weight
Using export policies, you can define which self-originated (external
routes being RIP) a router advertises. Self-originated refers to routes that
are originated by the router itself. You can also adjust the cost and
external metric type of each route that you allow the router to advertise.
Using RIP, you can define which external routes (RIP) a router advertises.
External routes are self-originated, but must be external to OSPF.
See the discussion about Type 1 and Type 2 metrics in "External Link State
Advertisements" earlier in this chapter for more information about
external metric types.
Definition
import
243.140.28.0
255.255.255.0
accept
10
16
Definition
import
243.140.28.0
255.255.255.0
reject
15