H3C S5500-EI - Configuring the MED Attribute; Configuring the NEXT_HOP Attribute

457
Ste
p
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. Set the default local
preference.
default local-preference value
Optional.
By default, the default local
preference is 100.
Configuring the MED attribute
Ste
p
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 a default MED
value.
default med med-value
Optional.
By default, the default med-value is
0.
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 a third-party next-hop network, that is, 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:
Ste
p
Command Remarks
1. Enter system view.
system-view
N/A