Configuring The Next_Hop Attribute; Configuring The As_Path Attribute - HP A6600 Configuration Manual

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.
To do...
1. Enter system view.
2. Enter BGP view.
3. Enter IPv6 MBGP address
family view.
4. Configure the router as the
next hop of routes sent to the
peer/peer group.

Configuring the AS_PATH attribute

To do...
1. Enter system view.
2. Enter BGP view.
3. Enter IPv6 MBGP address
family view.
4. Allow the local AS number to
appear in the as-path of routes
from a peer/peer group and
specify the number of times
that the local AS number can
appear in the as-path of routes
from the peer/peer group.
5. Disable IPv6 MBGP from
considering the as_path
during best route selection.
6. Configure updates to a
peer/peer group to carry only
the public AS number.
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
ipv6-family multicast
peer { ipv6-group-name |
ipv6-address } allow-as-loop
[ number ]
bestroute as-path-neglect
peer { ipv6-group-name |
ipv6-address } public-as-only
376
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
—
—
—
Optional.
Not allowed by default.
Optional.
Enabled by default.
Optional.
By default, outbound IPv6 MBGP
updates can carry private AS
numbers.