|
Navigate to the Term level in the configuration
hierarchy.
|
In the J-Web configuration editor hierarchy, select Policy
options>Policy statement>Term.
|
From the top of the CLI configuration hierarchy, enter
edit policy-options policy-statement prependpolicy1 term prependterm1
|
|
Specify the routes to prepend AS numbers to.
|
- In the From option, click Configure.
- In the Value box, enter the prefixes you wish to prepend.
- In the Route filter box, click Add new
entry.
- Click OK.
|
- Prepend routes 172.168.0.0/12 or longer:
set from route-filter 172.16.0.0/12 orlonger
- Prepend routes 192.168.0.0/16 or longer:
set from route-filter 192.168.0.0/16 orlonger
- Prepend routes 10.0.0.0/8 or longer:
set from route-filter 10.0.0.0/8 orlonger
|
|
Specify the AS numbers to prepend.
|
- In the configuration editor hierarchy, select Policy
options>Policy statement>Term.
- In the Then option, click Configure.
- In the AS path prepend box, enter the string of AS numbers
to prepend. Separate each AS number with a space.
- Click OK.
|
Specify the AS numbers to prepend, and enclose them inside double quotation
marks:
set then as-path-prepend “1 1 1 1”
|
|
Navigate to the Protocols>BGP> level in the configuration
hierarchy.
|
In the J-Web configuration editor hierarchy, select Protocols>BGP>.
|
From the top of the CLI configuration hierarchy, enter
edit protocols bgp
|
|
Apply the policy as an import policy for all BGP routes.
|
- In the Import box, click Add new entry.
- In the Value box, enter the name of the policy.
- Click OK.
The routing policy is evaluated when routes are being imported to the
routing table.
|
Apply the policy:
set import prependpolicy1
You can refer to the same routing policy one or more times in the same
or a different import statement.
|