Configuring The Next_Hop Attribute; Configuring The As_Path Attribute - HP 4800G Series Configuration Manual

To do...
Enter IPv6 MBGP address
family view
Configure a default MED value
Enable the comparison of the
MED for routes from different
ASs
Enable the comparison of the
MED for routes from each AS
Enable the comparison of the
MED for 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 IPv6 multicast iBGP peer/peer group. If load balancing is configured, the router specifies itself
as the next hop of routes sent to the IPv6 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 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.
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 IPv6 MBGP address
family view
Configure the router as the next
hop of routes sent to the
peer/peer group

Configuring the AS_PATH Attribute

Follow these steps to configure the AS_PATH attribute:
To do...
Enter system view
Enter BGP view
Use the command...
ipv6-family multicast
default med med-value
compare-different-as-med
bestroute compare-med
bestroute med-confederation
Use the command...
system-view
bgp as-number
ipv6-family multicast
peer { ipv6-group-name |
ipv6-address } next-hop-local
Use the command...
system-view
bgp as-number
1-9
Remarks
—
Optional
By default, the default
med-value is 0.
Optional
Not enabled by default
Optional
Disabled by default
Optional
Disabled by default
Remarks
—
—
—
Optional
By default, IPv6 MBGP
specifies the local router as the
next hop for routes sent to an
eBGP peer/peer group, but not
for routes sent to an iBGP
peer/peer group.
Remarks
—
—