Configuring Inter-As Vpn; Configuring Inter-As Option A - HP MSR2000 Configuration Manual

Step
16. Configure
advertised to an EBGP peer or
peer group to carry only public
AS numbers.
17. Configure the router as a route
reflector and specify a peer or
peer group as its client.
18. Specify 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
filtering of received VPNv4
routes.
21. Enable
between clients.
22. Configure a cluster ID for the
route reflector.
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.
The route targets configured on the PEs must match those configured on the ASBRs in the same AS to
make sure VPN routes sent by the PEs (or ASBRs) can be received by the ASBRs (or PEs). Route targets
configured on the PEs in different ASs do not have such requirements.
For more information, see
Command
BGP updates
peer { group-name | ip-address }
public-as-only
peer { group-name | ip-address }
reflect-client
peer { group-name | ip-address }
route-limit prefix-number
[ { alert-only | discard | reconnect
reconnect-time } |
percentage-value ] *
peer { group-name | ip-address }
route-policy route-policy-name
{ export | import }
route target-based
policy vpn-target
route reflection
reflect between-clients
reflector cluster-id { cluster-id |
ip-address }
rr-filter
extended-community-number
peer { group-name | ip-address }
soo site-of-origin
"Configuring basic MPLS L3VPN."
198
Remarks
Optional.
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, this feature is enabled.
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.