beautypg.com

Configuring ibgp – H3C Technologies H3C S10500 Series Switches User Manual

Page 26

background image

15

NOTE:

After you configure an IS-IS process for a VPN instance, you must enable the IS-IS process. For more
information about IS-IS, see

Layer 3—IP Routing Configuration Guide.

Configuring iBGP

To use iBGP for route exchange between an MCE and a PE or the egress router of a site, configure the

MCE and the PE or the egress router of the site as iBGP peers.
If the MCE is connected with multiple sites in the same VPN, configure the MCE and the egress routers

of the sites as a cluster and configure the MCE as the route reflector of the cluster.
Follow these steps to configure the MCE to use iBGP for route exchange with a PE or a site:

To do…

Use the command…

Remarks

Enter system view

system-view

Enter BGP view

bgp as-number

Enter BGP-VPN instance view

ipv4-family vpn-instance
vpn-instance-name

Required

Configure the PE or the egress
router of the site as the iBGP peer

of the VPN

peer { group-name | ip-address }
as-number as-number

Required

Configure the egress router of the
site as a client of the route reflector

peer { group-name | ip-address }
reflect-client

Optional
By default, no route reflector or
client is configured.

Enable route reflection between
clients

reflect between-clients

Optional
Enabled by default.
If the clients are fully meshed, you

do not need to enable route
reflection.

Specify a cluster ID for the route

reflector

reflector cluster-id cluster-id

Optional
By default, each RR in a cluster uses

its own router ID as the cluster ID.
If more than one RR exists in a
cluster, use this command to

configure the same cluster ID for all

RRs in the cluster to avoid routing

loops.

Configure the filtering policy for
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, routes to be advertised
are not filtered.

Configure the filtering policy for
routes received

filter-policy { acl-number |
ip-prefix ip-prefix-name } import

Optional
By default, routes received are not

filtered.