HP 10500 Series Configuration Manual page 122

Step
9. Enter BGP-VPNv4 address
family view.
10. Enable the PE to exchange
VPNv4 routes with the peer or
peer group.
11. (Optional.) Configure the PE
to not change the next hop of
routes advertised to the EBGP
peer.
Configuring an ASBR PE
In the inter-AS option C solution, an inter-AS LSP is required, and the public network routes advertised
between the relevant PEs and ASBRs must carry MPLS label information.
An ASBR-PE establishes common IBGP peer relationships with PEs in the same AS, and a common EBGP
peer relationship with the peer ASBR PE. All of them can exchange labeled IPv4 routes.
Public network routes carrying MPLS labels are advertised through MP-BGP. According to RFC 3107
"Carrying Label Information in BGP-4," the label mapping information for a particular route is
piggybacked in the same BGP update message that is used to distribute the route. This capability is
implemented through BGP extended attributes and requires that BGP peers can handle labeled IPv4
routes.
To configure an ASBR PE for inter-AS option C:
Step
1. Enter system view.
2. Enter BGP view.
3. Configure the PE in the same
AS as an IBGP peer.
4. Configure the peer ASBR PE
as an EBGP peer.
5. Enter BGP IPv4 unicast
address family view.
6. Enable exchange of IPv4
unicast routes with the peer or
peer group.
7. Enable exchange of labeled
IPv4 routes with the PE in the
local AS and the peer ASBR
PE.
8. Configure the ASBR PE to set
itself as the next hop of routes
advertised to the PE in the
local AS.
Configuring a routing policy on an ASBR PE
A routing policy on an ASBR PE does the following:
Command
ipv4-family vpnv4
peer { group-name | ip-address }
enable
peer { group-name | ip-address }
next-hop-invariable
Command
system-view
bgp as-number
peer { group-name | ip-address }
as-number as-number
peer { group-name | ip-address }
as-number as-number
ipv4-family [ unicast ]
peer { group-name | ip-address }
enable
peer { group-name | ip-address }
label-route-capability
peer { group-name | ip-address }
next-hop-local
116
Remarks
N/A
By default, BGP does not 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
N/A
By default, no BGP peer is created.
By default, no BGP peer is created.
N/A
By default, BGP does not exchange
IPv4 unicast routes with any peer.
By default, BGP does not advertise
labeled routes to any IPv4 peer or
peer group.
By default, BGP does not use its
address as the next hop of routes
advertised to an IBGP peer or peer
group.