318
session to the peer PE. Then, the
PE exchanges the PW ID FEC
and PW label mapping with the
peer.
Configuring a BGP PW
To configure a BGP PW, perform the following configurations on PEs:
• Configure BGP to advertise MPLS L2VPN label block information.
• Create a BGP PW.
Configuring BGP to advertise MPLS L2VPN label block information
1. Enter system view.
system-view
N/A
2. Enable BGP and e
view.
bgp
as-number
enabled.
3. Configure the remote PE as a
BGP peer.
peer
{ group-name | ip-address
[ mask-length ] }
as-number
as-number
By default, no BGP peer is
configured.
4. Create a BGP L2VPN address
family and enter BGP L2VPN
address family view.
address-family l2vpn
By default, no BGP L2VPN
address family is created.
5. Enable BGP to exchange BGP
L2VPN information with the
specified peer or peer group.
peer
{ group-name | ip-address
[ mask-length ] }
enable
By default, BGP cannot
exchange BGP L2VPN
information with any peer or
peer group.
6. Enable BGP to exchange label
blo
specified peer or peer group.
peer
{ group-name | ip-address
[ mask-length ] }
signaling
[
non-standard
]
By default, BGP can
exchange label block
information with a BGP
L2VPN peer or peer group by
MP_REACH_NLRI.
7. (Optional.) Permit the local AS
number to appear in routes
from the specified peer or peer
appearance times.
peer
{ group-name | ip-address
[ mask-length ] }
allow-as-loop
[ number ]
By default, the local AS
number is not allowed in
routes from a peer or peer
group.
8. (Optional.) En
target-
based filtering of
incoming BGP L2VPN
information.
policy vpn-target
target-
based filtering of
incoming BGP L2VPN
information is enabled.
9. (Optional.) 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 route reflector
or client is configured.
10. (Optional.)
information reflection between
clients.
reflect between-clients
By default, L2VPN
information reflection is
enabled between clients.
11. (Optional.)
cluster ID of the route reflector.
reflector cluster-id
{ cluster-id |
ip-address }
By default, a route reflector
uses its own router ID as the
cluster ID.