Configuring The Next_Hop Attribute; Configuring The As_Path Attribute - HP MSR ASM Configuration Manual

Step
2. Enter BGP view.
3. Enter IPv6 MBGP address
family view.
4. Configure a default MED
value.
5. Enable the comparison of the
MED for routes from different
ASs.
6. Enable the comparison of the
MED for routes from each AS.
7. 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 or a peer group. If load balancing is configured, the router specifies itself
as the next hop of routes sent to the IPv6 multicast IBGP peer or the peer group regardless of whether the
peer next-hop-local command is configured.
In the environment where 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 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 IPv6 MBGP address
family view.
4. Configure the router as the
next hop of routes sent to the
peer or the peer group.

Configuring the AS_PATH attribute

Step
1. Enter system view.
2. Enter BGP view.
3. Enter IPv6 MBGP address
family view.
Command
bgp as-number
ipv6-family multicast
default med med-value
compare-different-as-med
bestroute compare-med
bestroute med-confederation
Command
system-view
bgp as-number
ipv6-family multicast
peer { ipv6-group-name |
ipv6-address } next-hop-local
Command
system-view
bgp as-number
ipv6-family multicast
426
Remarks
N/A
N/A
Optional.
0 by default.
Optional.
Not enabled by default.
Optional.
Disabled by default.
Optional.
Disabled 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 IBGP peer or a peer group.
Remarks
N/A
N/A
N/A