beautypg.com

Tunnel policy configuration examples, Preferred tunnel configuration example – H3C Technologies H3C S12500-X Series Switches User Manual

Page 138

background image

127

Step Command

Remarks

3.

Enter BGP-VPNv4 address
family view.

address-family vpnv4

N/A

4.

Configure filtering of

advertised routes.

filter-policy { acl-number |
prefix-list prefix-list-name } export
[ protocol process-id ]

Optional.
By default, BGP does not filter
advertised routes.

5.

Configure filtering of received

routes.

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

Optional.
By default, BGP does not filter
received routes.

6.

Advertise community

attributes to a peer or peer

group.

peer { group-name | ip-address }
advertise-community

Optional.
By default, no community attributes
are advertised to any peer or peer

group.

7.

Allow the local AS number to
appear in the AS_PATH

attribute of routes received

from the peer, and set the
maximum number of

repetitions.

peer { group-name | ip-address }
allow-as-loop [ number ]

By default, BGP discards route
updates that contain the local AS
number.

8.

Filter routes received from or
advertised to a peer or peer

group based on an AS_PATH

list.

peer { group-name | ip-address }
as-path-acl aspath-filter-number

{ import | export }

Optional.
By default, no AS filtering list is
applied to a peer or peer group.

9.

Advertise a default VPN route
to a peer or peer group.

peer { group-name | ip-address }
default-route-advertise

vpn-instance vpn-instance-name

Optional.
By default, no default VPN route is

advertised to a peer or peer group.

10.

Apply an ACL to filter routes
received from or advertised to

a peer or peer group.

peer { group-name | ip-address }
filter-policy acl-number { export |

import }

Optional.
By default, no ACL-based filtering

is configured.

11.

Save all route updates from a

peer or peer group.

peer { group-name | ip-address }
keep-all-routes

By default, BGP does not save
route updates from any peer.

12.

Specify the router as the next

hop of routes sent to a peer or
peer group.

peer { group-name | ip-address }
next-hop-local

By default, the router sets itself as
the next hop for routes sent to a

peer or peer group.

13.

Configure BGP to not change
the next hop of routes sent to

an EBGP peer or peer group.

peer { group-name | ip-address }
next-hop-invariable

Optional.
By default, the router sets itself as

the next hop for routes sent to an
EBGP peer or peer group.
In an inter-AS option C network
where an RR is used to advertise

VPNv4 routes, configure this
command on the RR so the RR does

not change the next hop of routes

sent to EBGP peers and clients.

14.

Specify a preferred value for
routes received from a peer or

peer group.

peer { group-name | ip-address }
preferred-value value

Optional.
By default, the preferred value is 0.