H3C Technologies H3C S5820V2 Series Switches - Manual (Page 14)

8
Step Command Remarks
4. Redistribute remote site routes
advertised by the PE.
import-route protocol process-id
[ cost cost | type type | tag tag ] *
By default, OSPF does not
redistribute routes from any other
routing protocol.
5. Create an OSPF area and
enter OSPF area view.
area area-id
By default, no OSPF area is
created.
6. Enable OSPF on the interface
attached to the specified
network in the area. network ip-address wildcard-mask
By default, an interface does not
run OSPF.
NOTE:
•
An OSPF process that is bound with a VPN instance does not use the public network router ID
configured in system view. Therefore, you must configure a router ID when starting the OSPF process. All
OSPF processes for the same VPN must be configured with the same OSPF domain ID to ensure correct
route advertisement.
• An OSPF process can belong to only one VPN instance, but one VPN instance can use multiple OSPF
processes to advertise the VPN routes.
• For more information about OSPF, see Layer 3—IP Routing Configuration Guide.
Configuring EBGP between MCE and VPN site
To use EBGP for exchanging routing information between an MCE and VPN sites, you must configure a
BGP peer for each VPN instance on the MCE, and redistribute the IGP routes of each VPN instance on
the VPN sites.
1. Configure the MCE
To configure BGP on the MCE:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter BGP view. bgp as-number N/A
3. Enter BGP-VPN instance view. ip vpn-instance vpn-instance-name N/A
4. Specify an EBGP peer or peer
group. peer { group-name | ip-address }
[ as-number as-number ] No BGP peer or peer group is
specified by default.
5. Enter BGP-VPN IPv4 unicast
address family view.
ipv4-family [ unicast ] N/A
6. Enable exchange of IPv4
unicast routes with the
specified peer or peer group.
peer { group-name | ip-address }
enable
BGP cannot exchange IPv4 unicast
routes with any peer or peer
group.
7. Allow routing loops: allow the
local AS number to appear in
the AS_PATH attribute of
routes received from the peer
or peer group and specify the
maximum appearance times.
peer { group-name | ip-address }
allow-as-loop [ number ]
By default, the local AS number is
not allowed to appear in the
AS_PATH attribute of routes from a
peer or peer group.