Configuring Soft Gre - HP HSR6800 Configuration Manual

Step
8. Filter all or certain types of
routes to be advertised.
9. Filter received routes.
10. Advertise community
attributes to a peer or peer
group.
11. Filter routes received from or
to be advertised to a peer or
peer group based on an
AS_PATH list.
12. Advertise a default VPN
route to a peer or peer
group.
13. Apply a filtering policy to a
peer or peer group.
14. Apply a route filtering policy
based on IP prefix list to a
peer or peer group.
15. Specify not to change the
next hop of a route when
advertising it to a peer or
peer group.
16. Specify the preference value
for the routes received from
the peer/peer group.
17. Make BGP updates to be
sent carry no private AS
numbers.
18. Apply a routing policy to a
peer or peer group.
For more information about BGP routing, see Layer 3—IP Routing Configuration Guide.

Configuring soft GRE

Soft GRE can replace MPLS LDP, MPLS TE, or GREto set up a public tunnel for an MPLS L3VPN
network. It has simpler configuration.
After soft GRE is enabled on a PE, the PE uses an encapsulation method for VPN packets:
Command
filter-policy { acl-number |
ip-prefix ip-prefix-name } export
[ direct | isis process-id | ospf
process-id | rip process-id |
static ]
filter-policy { acl-number |
ip-prefix ip-prefix-name } import
peer { group-name | ip-address }
advertise-community
peer { group-name | ip-address }
as-path-acl aspath-filter-number
{ import | export }
peer { group-name | ip-address }
default-route-advertise
vpn-instance vpn-instance-name
peer { group-name | ip-address }
filter-policy acl-number { export
| import }
peer { group-name | ip-address }
ip-prefix prefix-name { export |
import }
peer { group-name | ip-address }
next-hop-invariable
peer { group-name | ip-address }
preferred-value value
peer { group-name | ip-address }
public-as-only
peer { group-name | ip-address }
route-policy route-policy-name
{ export | import }
273
Remarks
Optional.
By default, BGP does not filter
routes to be advertised.
Optional.
By default, BGP does not filter
received routes.
Optional.
By default, no community
attributes are advertised to any
peer or peer group.
Optional.
By default, no AS filtering list is
applied to a peer or peer group.
Optional.
By default, no default VPN route
is advertised to a peer or peer
group.
Optional.
By default, no filtering policy is
applied to a peer or peer group.
Optional.
By default, no route filtering policy
based on IP prefix list is applied to
a peer or peer group.
Optional.
By default, a device uses its
address as the next hop when
advertising a route to its EBGP
peer or peer group.
Optional.
0 by default.
Optional.
By default, a BGP update carries
private AS numbers.
Optional.
By default, no routing policy is
applied to a peer or peer group.