183
Step
Command
Remarks
14.
Specify a preferred value for
routes received from a peer
or peer group.
peer
{
group-name
|
ip-address
[
mask-length
] }
preferred-value
value
By default, the preferred value is
0.
15.
Apply a prefix list to filter
routes received from or
advertised to a peer or peer
group.
peer
{
group-name
|
ip-address
[
mask-length
] }
prefix-list
prefix-list-name
{
export
|
import
}
By default, no prefix list based
filtering is configured.
16.
Configure
BGP updates
advertised to an EBGP peer
or peer group to carry only
public AS numbers.
peer
{
group-name
|
ip-address
[
mask-length
] }
public-as-only
By default, BGP route updates
advertised to an EBGP peer or
peer group can carry both public
and private AS numbers.
17.
Configure the router as a
route reflector and specify a
peer or peer group as its
client.
peer
{
group-name
|
ip-address
[
mask-length
] }
reflect-client
By default, no RR is configured.
18.
Specify the maximum
number of routes BGP can
receive from a peer or peer
group.
peer
{
group-name
|
ip-address
[
mask-length
] }
route-limit
prefix-number
[ {
alert-only
|
discard
|
reconnect
reconnect-time
} |
percentage-value
] *
By default, the number of routes
that BGP can receive from a peer
or peer group is not limited.
19.
Apply a routing policy to a
peer or peer group.
peer
{
group-name
|
ip-address
[
mask-length
] }
route-policy
route-policy-name
{
export
|
import
}
By default, no routing policy is
applied to a peer or peer group.
20.
Enable route target-based
filtering of received VPNv4
routes.
policy vpn-target
By default, this feature is enabled.
21.
Enable route reflection
between clients.
reflect between-clients
By default, route reflection
between clients is enabled on the
RR.
22.
Configure a cluster ID for the
route reflector.
reflector cluster-id
{
cluster-id
|
ip-address
}
By default, the RR uses its own
router ID as the cluster ID.
23.
Configure filtering of
reflected routes.
rr-filter
extended-community-number
By default, the RR does not filter
reflected routes.
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 "
."
Содержание FlexNetwork 5510 HI Series
Страница 9: ...vii Remote support 460 Documentation feedback 460 Index 462 ...
Страница 318: ...309 Request list 0 Retransmit list 0 ...
Страница 363: ...354 Verify that CE 1 and CE 2 can ping each other Details not shown ...
Страница 446: ...437 The MCE has redistributed the OSPF routes of the two VPN instances into the EBGP routing tables of PE 1 ...