Configuring ebgp between pe and ce – H3C Technologies H3C S10500 Series Switches User Manual
Page 260

249
To do…
Use the command…
Remarks
Configure a network entity title for
the IS-IS process
network-entity net
Required
Not configured by default
Return to system view
quit
—
Enter interface view
interface interface-type
interface-number
—
Enable the IS-IS process on the
interface
isis enable [ process-id ]
Required
Disabled by default
NOTE:
For more information about IS-IS, see
Layer 3—IP Routing Configuration Guide.
Configuring eBGP between PE and CE
1.
Configurations on the PE
Follow these steps to configure the PE:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enable BGP and enter BGP view
bgp as-number —
Enter BGP VPN instance view
ipv4-family vpn-instance
vpn-instance-name
Required
Configure the CE as the VPN eBGP
peer
peer { group-name | ip-address }
as-number as-number
Required
Redistribute the routes of the local
CEs
import-route protocol [ process-id ]
[ med med-value | route-policy
route-policy-name ] *
Required
A PE must redistribute the routes of
the local CEs into its VPN routing
table so that it can advertise them
to the peer PE.
Configure BGP to filter 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
routes to be advertised.
Configure BGP to filter received
routes
filter-policy { acl-number |
ip-prefix ip-prefix-name } import
Optional
By default, BGP does not filter
received routes.
Allow the local AS number to
appear in the AS_PATH attribute of
a received route and set the
maximum number of repetitions
peer { group-name | ip-address }
allow-as-loop [ number ]
Optional
For the hub and spoke network
scheme