232
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter IPv4 MBGP address
family view.
ipv4-family multicast
N/A
4.
Specify the router as the next
hop of routes sent to a peer or a
peer group.
peer
{
group-name
|
ip-address
}
next-hop-local
Optional.
By default, MBGP
specifies the local router
as the next hop for routes
advertised to a MBGP
EBGP peer or a peer
group. It does not do this
for routes advertised to a
MBGP IBGP peer or a
peer group.
Configuring the AS_PATH attribute
In general, MBGP checks whether the AS_PATH attribute of a route from a peer contains the local
AS number. If it does, MGBP discards the route to avoid routing loops.
To configure the AS_PATH attribute:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter IPv4 MBGP address family
view.
ipv4-family multicast
N/A
4.
Configure the AS_PATH attribute.
•
Allow the local AS number to
appear in the AS path of
routes from a peer or a peer
group and specify the
number of times that the
local AS number can
appear:
peer
{
group-name
|
ip-address
}
allow-as-loop
[
number
]
•
Disable BGP from
considering the AS path
during best route selection:
bestroute as-path-neglect
•
Configure the update
messages to a peer or a
peer group not to carry
private AS numbers in the
AS path of routes:
peer
{
group-name
|
ip-address
}
public-as-only
Optional.
By default:
•
The local AS number
cannot appear in
routes from a
peer/peer group.
•
BGP
considers
AS_PATH during best
route selection.
•
BGP updates carry
private AS numbers.
