Configuring The Next_Hop Attribute; Configuring The As_Path Attributes - HP 6125G Configuration Manual

Step
1. Enter system view.
2. Enter BGP view.
3. Enter IPv4 MBGP address
family view.
4. Configure the default MED
value.
5. Enable the comparison of the
MED of routes from different
ASs.
Enable the comparison of the
6.
MED of routes from each AS.
7. Enable the comparison of the
MED of routes from
confederation peers.

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:
Step
1. Enter system view.
2. Enter BGP view.
3. Enter IPv4 MBGP address
family view.
4. Specify the router as the next
hop of routes sent to a 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:
Command
system-view
bgp as-number
ipv4-family multicast
default med med-value
compare-different-as-med
bestroute compare-med
bestroute med-confederation
Command
system-view
bgp as-number
ipv4-family multicast
peer { group-name | ip-address }
next-hop-local
194
Remarks
N/A
N/A
N/A
Optional.
0 by default.
Optional.
Not enabled by default.
Optional.
Not enabled by default.
Optional.
Not enabled by default.
Remarks
N/A
N/A
N/A
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.