426
Step
Command
Remarks
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter IPv6 MBGP address
family view.
ipv6-family multicast
N/A
4.
Configure a default MED
value.
default med
med-value
Optional.
0 by default.
5.
Enable the comparison of the
MED for routes from different
ASs.
compare-different-as-med
Optional.
Not enabled by default.
6.
Enable the comparison of the
MED for routes from each AS.
bestroute compare-med
Optional.
Disabled by default.
7.
Enable the comparison of the
MED for routes from
confederation peers.
bestroute med-confederation
Optional.
Disabled by default.
Configuring the NEXT_HOP attribute
You can use the
peer next-hop-local
command to specify the local router as the next hop of routes sent
to an IPv6 multicast IBGP peer or a peer group. If load balancing is configured, the router specifies itself
as the next hop of routes sent to the IPv6 multicast IBGP peer or the peer group regardless of whether the
peer next-hop-local
command is configured.
In the environment where the local router has two IPv6 multicast EBGP peers in a broadcast network, the
router does not specify itself as the next hop of routes sent to the EBGP peers by default.
To specify the router as the next hop of routes sent to a peer or a peer group:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view.
bgp
as-number
N/A
3.
Enter IPv6 MBGP address
family view.
ipv6-family multicast
N/A
4.
Configure the router as the
next hop of routes sent to the
peer or the peer group.
peer
{
ipv6-group-name
|
ipv6-address
}
next-hop-local
Optional.
By default, IPv6 MBGP specifies
the local router as the next hop for
routes sent to an EBGP peer or a
peer group, but not for routes sent
to an IBGP peer or a peer group.
Configuring 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 IPv6 MBGP address
family view.
ipv6-family multicast
N/A