HP FlexNetwork 10500 Series Configuration Manual page 223

Step
4. Configure the PE of another
AS as an EBGP peer.
5. Create the BGP IPv4 unicast
address family and enter its
view.
6. Enable BGP to exchange
IPv4 unicast routes with the
ASBR in the same AS.
7. Enable BGP to exchange
labeled IPv4 routes with the
ASBR in the same AS.
8. Return to BGP instance view.
9. Enter BGP VPNv4 address
family view.
10. Enable BGP to exchange
VPNv4 routes with the PE in
different ASs.
11. (Optional.) Configure the PE
to not change the next hop of
routes advertised to the peer.
Configuring an ASBR
To set up an inter-AS public tunnel for the inter-AS option C solution, an ASBR must assign an MPLS
label to the route destined for a PE, and advertise the label along with the route. Typically, the routes
advertised by an ASBR through BGP include the PE address as well as other routes. You can
configure a routing policy to filter routes. Routes surviving the filtering are assigned labels, and all
others are advertised as common IPv4 routes.
To configure a routing policy, use the following commands:
•
if-match mpls-label—Matches routes carrying MPLS labels.
•
apply mpls-label—Sets MPLS labels for IPv4 routes advertised to a peer. You can use this
command together with if-match clauses. For example, the apply mpls-label command works
together with the if-match mpls-label command to set new MPLS labels for routes with MPLS
labels. The newly assigned labels are advertised along with the routes.
For more information about routing policy configuration, see Layer 3—IP Routing Configuration
Guide.
To configure an ASBR for inter-AS option C:
Step
1. Enter system view.
2. (Optional.) Create a routing
policy, and enter routing
policy view.
3. (Optional.) Match IPv4
routes carrying labels.
4. (Optional.) Set labels for
IPv4 routes.
5. Return to system view.
Command
peer { group-name | ipv4-address
[ mask-length ] } as-number
as-number
address-family ipv4 [ unicast ]
peer { group-name | ipv4-address
[ mask-length ] } enable
peer { group-name | ipv4-address
[ mask-length ] }
label-route-capability
quit
address-family vpnv4
peer { group-name | ipv4-address
[ mask-length ] } enable
peer { group-name | ipv4-address
[ mask-length ] }
next-hop-invariable
Command
system-view
route-policy route-policy-name
{ deny | permit } node
node-number
if-match mpls-label
apply mpls-label
quit
214
Remarks
By default, no BGP peers exist.
By default, the BGP IPv4 unicast
address family is not created.
By default, BGP does not
exchange IPv4 unicast routes with
any peer.
By default, BGP cannot exchange
labeled routes with any IPv4 peer
or peer group.
N/A
N/A
By default, BGP cannot exchange
VPNv4 routes with any peer.
Configure this command on the
RR so the RR does not change
the next hop of advertised VPNv4
routes.
Remarks
N/A
By default, no routing policies
exist.
By default, no MPLS label match
criterion is configured.
By default, no MPLS label is set
for IPv4 routes.
N/A