3Com 3C13636 Configuration Manual page 894

3Com Router 3000 Ethernet Family
Configuration Guide
Perform the following configuration in route-policy view.
Table 3-29 Configure label processing on public network routes
Assign MPLS labels to the public network routes
that match route-policy conditions
Remove the assigned MPLS labels
Configure to only receive/transmit the public
network routes with MPLS labels
Remove the configuration of only receiving/sending
public network routes with MPLS labels
By default, public network routes do not carry MPLS labels and no route-policy is
defined.
The public network routes with MPLS labels are advertised by MP-BGP. According to
RFC 3107 (Carrying Label Information in BGP-4), the label mapping information of a
route can be piggybacked by advertising BGP Update messages of the route. This
capability is implemented through BGP extension attributes and requires BGP peers
processing labeled IPv4 routes.
Perform the following configuration in BGP view.
Table 3-30 Configure the capability for processing labeled IPv4 routes
Enable the capability for processing
labeled IPv4 routes
Disable the capability for processing
labeled IPv4 routes
By default, BGP peers cannot process labeled IPv4 routes.
3) Configuring Invariable Next Hop when Advertising Routes
Generally, BGP Speaker changes the next hop to itself when advertising routes to
EBGP peers. In the networking application that adopts Multihop MP-EBGP multi-AS
VPN mode and uses RR to advertise VPNv4 routes, BGP Speaker cannot vary the next
hop when advertising VPNv4 routes between RRs.
Perform the following configuration in BGP view, BGP-VPNv4 sub-address family view,
BGP VPN instance view, or BGP-IPv4 multicast sub-address family view.
Operation
Operation
3Com Corporation
3-32
Chapter 3 BGP/MPLS VPN Configuration
Command
apply mpls-label
undo apply mpls-label
if-match mpls-label
undo if-match mpls-label
Command
peer
label-route-capability
undo peer
label-route-capability
group-name
group-name