H3C Technologies H3C SR8800 - Manual (Page 281)

270
Step Command Remarks
6. Redistribute remote site routes
advertised by the PE.
import-route protocol [ process-id
| all-processes ] [ med med-value |
route-policy route-policy-name ] *
By default, no routes of any other
protocol are redistributed to BGP.
7. Configure a filtering policy to
filter the routes to be
advertised.
filter-policy { acl-number |
ip-prefix ip-prefix-name } export
[ direct | isis process-id | ospf
process-id | rip process-id | static ]
Optional.
By default, BGP does not filter the
routes to be advertised.
8. Configure a filtering policy to
filter received routes. filter-policy { acl-number |
ip-prefix ip-prefix-name } import
Optional.
By default, BGP does not filter the
received routes.
NOTE:
•
Normally, BGP checks routing loops by examining AS numbers. If EBGP is used between the MCE and
a site, when the MCE advertises its routing information with its AS number to the site and then receives
routing update information from the site, the route update message will carry the AS number of the
MCE, making the MCE unable to receive this route update message. In this case, to enable the MCE to
receive route updates normally, configure the MCE to allow routing loops.
• In standard BGP/OSPF route redistribution, when a route is redistributed into OSPF from BGP on the
MCE, the route’s original OSPF attribute cannot be restored, making the route unable to be
distinguished from routes redistributed from other domains. To distinguish routes of different OSPF
domains, you need to enable a route to carry the OSPF domain ID when the route is redistributed from
OSPF into BGP on the peer PE. Thus, the domain ID of an OSPF process is carried in a route generated
by the process. When the OSPF route is redistributed into BGP, the domain ID is added to the BGP VPN
route and is transmitted over the network as the extended community attribute of BGP.
• After you configure a BGP VPN instance, the BGP route exchange in the VPN instance is the same as the
common BGP’s. For more information about BGP configuration, see
Layer 3—IP Routing Configuration
Guide.
2. Configurations on a VPN site
To configure the VPN site:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter BGP view. bgp as-number N/A
3. Configure the MCE as the
EBGP peer. peer { group-name | ip-address }
as-number as-number
N/A
4. Redistribute the IGP routes of
the VPN.
import-route protocol [ process-id ]
[ med med-value | route-policy
route-policy-name ] *
Optional.
A VPN site must advertise the VPN
network addresses it can reach to
the connected MCE.
Configuring IBGP beween MCE and VPN site
If IBGP is used for exchanging routing information between an MCE and VPN sites, you must configure
a BGP peer for each VPN instance respectively, and redistribute the IGP routes of each VPN instance on
the VPN sites.