Configuring The Next Hop Attribute; Configuring The As-Path Attribute - HP 4800G Series Configuration Manual

To do...
Configure
the MED
attribute

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 a MBGP iBGP peer/peer group. If load balancing is configured, the router specifies itself as the
next hop of route advertisements to the multicast iBGP peer/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 multicast eBGP peers in a broadcast
network, the router does not specify itself as the next hop of routing information sent to the eBGP peers
unless the peer next-hop-local command is configured.
Follow these steps to specify the router as the next hop of routes sent to a peer/peer group:
To do...
Enter system view
Enter BGP view
Enter IPv4 MBGP
address family view
Specify the router as the
next hop of routes sent to
a peer/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 yes, it discards the route to avoid routing loops.
Configure the default
MED value
Enable the
comparison of the
MED of routes from
different ASs
Enable the
comparison of the
MED of routes from
each AS
Enable the
comparison of the
MED of routes from
confederation peers
Use the command...
system-view
bgp as-number
ipv4-family multicast
peer { group-name |
ip-address } next-hop-local
Use the command...
default med med-value
compare-different-as-med
bestroute compare-med
bestroute med-confederation
—
—
—
Optional
By default, the next hop of routes sent
to a MBGP eBGP peer/peer group is
the advertising router, while that of
routes sent to a MBGP iBGP peer/peer
group is not.
1-9
Remarks
Optional
0 by default.
Optional
Not enabled by default
Optional
Not enabled by default
Optional
Not enabled by default
Remarks