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 default MED
value.
default med med-value
Optional.
0 by default.
5. Enable the comparison of the
MED of routes from different
ASs.
compare-different-as-med
Optional.
Not enabled by default.
6. Enable the comparison of the
MED of routes from each AS.
bestroute compare-med
Optional.
Not enabled by default.
7. Enable the comparison of the
MED of routes from
confederation peers.
bestroute med-confederation
Optional.
Not enabled 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 MBGP IBGP peer or peer group. If load balancing is configured, the router specifies itself as the
next hop of route advertisements to the multicast IBGP peer or peer group regardless of whether the peer
next-hop-local command is configured.
In a broadcast network where the local router has two multicast EBGP peers, the router does not specify
itself as the next hop of routing information sent to the EBGP peers by default unless the peer
next-hop-local command is configured.
To specify the router as the next hop of routes sent to a peer or a peer group:
Ste
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, 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 MBGP IBGP peer or a peer
group.
Configuring the AS_PATH attributes
In general, MBGP checks whether the AS_PATH attribute of a route from a peer contains the local AS
number. If it does, it discards the route to avoid routing loops.
To configure the AS_PATH attributes:
To Next Page
Loading...
