H3C Technologies H3C SR8800 - Manual (Page 262)

251
NOTE:
•
After configuring an OSPF process for a VPN instance, you must enable OSPF. The configuration
procedure is the same as that for a normal OSPF process.
• For more information about OSPF, see Layer 3—IP Routing Configuration Guide.
• After you configure the domain-id domain-id [ secondary ] command, the configuration will not take
effect until you execute the reset ospf command.
Configuring IS-IS between PE and CE
An IS-IS process belongs to the public network or a single VPN instance. If you create an IS-IS process
without binding it to a VPN instance, the process belongs to the public network.
To configure IS-IS between PE and CE:
Step Command Remarks
1. Enter system view. system-view N/A
2. Create an IS-IS process for a
VPN instance and enter IS-IS
view.
isis [ process-id ] vpn-instance
vpn-instance-name
N/A
3. Configure a network entity
title for the IS-IS process.
network-entity net Not configured by default
4. Return to system view. quit N/A
5. Enter interface view.
interface interface-type
interface-number
N/A
6. Enable the IS-IS process on
the interface.
isis enable [ process-id ] Disabled by default
NOTE:
For more information about IS-IS, see Layer 3—IP Routing Configuration Guide.
Configuring PE-CE route exchange through EBGP
1. Configurations on a PE
To configure EBGP between PE and CE:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enable BGP and enter BGP
view.
bgp as-number N/A
3. Enter BGP VPN instance view. ipv4-family vpn-instance
vpn-instance-name
N/A
4. Configure the CE as the VPN
EBGP peer. peer { group-name | ip-address }
as-number as-number
N/A
5. Redistribute the routes of the
local CEs.
import-route protocol [ process-id ]
[ med med-value | route-policy
route-policy-name ] *
A PE needs to redistribute the
routes of the local CEs into its VPN
routing table so that it can
advertise them to the peer PE.