263
Step
Command
Remarks
2.
Enter BGP IPv6 unicast
address family view,
BGP-VPN IPv6 unicast
address family view, or BGP
IPv6 multicast address family
view.
•
Enter BGP IPv6 unicast
address family view:
a. bgp
as-number
[
instance
instance-name
]
b. address-family ipv6
[
unicast
]
•
Enter BGP-VPN IPv6 unicast
address family view:
c. bgp as-number
[
instance
instance-name
]
d. ip vpn-instance
vpn-instance-name
e. address-family ipv6
[
unicast
]
•
Enter BGP IPv6 multicast
address family view:
f. bgp
as-number
[
instance
instance-name
]
g. address-family ipv6
multicast
N/A
3.
Specify the router as the next
hop for routes sent to a peer
or peer group.
peer
{
group-name
|
ipv6-address
[
prefix-length
] }
next-hop-local
By default, the router sets itself as
the next hop for routes sent to an
EBGP peer or peer group.
However, it does not set itself as
the next hop for routes sent to an
IBGP peer or peer group.
Configuring the AS_PATH attribute
Permitting local AS number to appear in routes from a peer or peer group
In general, BGP checks whether the AS_PATH attribute of a route from a peer contains the local AS
number. If yes, it discards the route to avoid routing loops.
In certain network environments (for example, a Hub&Spoke network in MPLS L3VPN), however,
the AS_PATH attribute of a route from a peer must be allowed to contain the local AS number.
Otherwise, the route cannot be advertised correctly.
To permit the local AS number to appear in routes from a peer or peer group and specify the
appearance times (IPv4 unicast/multicast address family):
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
Summary of Contents for HPE FlexNetwork 7500 series
Page 505: ...493 Connector N A ...
