Configuring Inter-As Vpn; Configuring Inter-As Option A - HP FlexNetwork 10500 Series Configuration Manual

Hide thumbs Also See for FlexNetwork 10500 Series:
Table of Contents

Advertisement

Step
15. Apply a prefix list to filter
routes received from or
advertised to a peer or peer
group.
16. Configure BGP updates
advertised to an EBGP peer
or peer group to carry only
public AS numbers.
17. Configure the device as an
RR and specify a peer or
peer group as its client.
18. Set the maximum number of
routes BGP can receive from
a peer or peer group.
19. Apply a routing policy to a
peer or peer group.
20. Enable route target filtering
of received VPNv4 routes.
21. Enable route reflection
between clients.
22. Configure a cluster ID for the
RR.
23. Configure filtering of
reflected routes.
24. Configure the SoO attribute
for a BGP peer or peer
group.

Configuring inter-AS VPN

If the MPLS backbone spans multiple ASs, you must configure inter-AS VPN.

Configuring inter-AS option A

Inter-AS option A applies to scenarios with a few VPNs.
To configure inter-AS option A, create VPN instances on PEs and ASBRs. The VPN instances on
PEs are used to allow CEs to access the network, The VPN instances on ASBRs are used to access
the peer ASBRs. An ASBR considers the peer ASBR as a CE.
Command
peer { group-name | ipv4-address
[ mask-length ] } prefix-list
prefix-list-name { export |
import }
peer { group-name | ipv4-address
[ mask-length ] } public-as-only
peer { group-name | ipv4-address
[ mask-length ] } reflect-client
peer { group-name | ipv4-address
[ mask-length ] } route-limit
prefix-number [ { alert-only |
discard | reconnect
reconnect-time } |
percentage-value ] *
peer { group-name | ipv4-address
[ mask-length ] } route-policy
route-policy-name { export |
import }
policy vpn-target
reflect between-clients
reflector cluster-id { cluster-id |
ip-address }
rr-filter ext-comm-list-number
peer { group-name | ipv4-address
[ mask-length ] } soo site-of-origin
211
Remarks
By default, no prefix list based
filtering is configured.
By default, BGP route updates
advertised to an EBGP peer or
peer group can carry both public
and private AS numbers.
By default, no RR is configured.
By default, the number of routes
that BGP can receive from a peer
or peer group is not limited.
By default, no routing policy is
applied to a peer or peer group.
By default, route target filtering is
enabled for received VPNv4
routes. Only VPNv4 routes whose
export route target attribute
matches local import route target
attribute are added to the routing
table.
By default, route reflection
between clients is enabled on the
RR.
By default, the RR uses its own
router ID as the cluster ID.
By default, the RR does not filter
reflected routes.
By default, the SoO attribute is not
configured.

Advertisement

Table of Contents
loading

Table of Contents