Configuring route advertisement between pe and ce, Configuring static routes between pes and ces, Configuring rip between pe and ce – H3C Technologies H3C SecPath F1000-E User Manual
Page 74
11
To do…
Use the command…
Remarks
Create a VPN instance and enter
VPN instance view
ip vpn-instance
vpn-instance-name
Required
No VPN instance exists by default.
Configure an RD for the VPN
instance
route-distinguisher
route-distinguisher
Required
Associate the current VPN instance
with one or more VPN targets
vpn-target vpn-target&<1-8>
[ both |
export-extcommunity |
import-extcommunity ]
Required
Return to system view
quit
—
Enter interface view
interface interface-type
interface-number
—
Associate the current interface with
the VPN instance
ip binding vpn-instance
vpn-instance-name
Required
By default, an interface is
associated with no VPN instance.
Configuring Route Advertisement between PE and CE
Route advertisement between PE and CE can depend on static routes, RIP, OSPF, or EBGP. You may
choose one as needed.
Configuring static routes between PEs and CEs
Follow these steps to configure static routes between PEs and CEs:
To do…
Use the command…
Remarks
Enter system view
system-view
—
ip route-static dest-address { mask | mask-length }
{ gateway-address | interface-type interface-number
[ gateway-address ] | vpn-instance d-vpn-instance-name
gateway-address } [ preference preference-value ] [ tag
tag-value ] [ description description-text ]
Configure static
routes for a specified
VPN instance
ip route-static vpn-instance s-vpn-instance-name&<1-5>
dest-address { mask | mask-length } { gateway-address [ public ] |
interface-type interface-number [ gateway-address ] |
vpn-instance d-vpn-instance-name gateway-address }
[ preference preference-value ] [ tag tag-value ] [ description
description-text ]
Required
NOTE:
•
Perform this configuration on the PEs. The configuration method on the CEs is the same for configuring
ordinary static routes.
•
For information about static route, see
Static Route Configuration in the IP Routing Volume.
Configuring RIP between PE and CE
A RIP process belongs to only one VPN instance. If you run a RIP process without binding it to a VPN
instance, the process is considered a public network process.