H3C Technologies H3C SR8800 - Manual (Page 369)

353
NOTE:
•
To make sure an IBGP peer can find the correct next hop, you can configure routes advertised to the IPv6
IBGP peer/peer group to use the local router as the next hop. If BGP load balancing is configured, the
local router specifies itself as the next hop of routes sent to an IPv6 IBGP peer/peer group regardless of
whether the peer next-hop-local command is configured.
• In a “third party next hop” network where the two IPv6 EBGP peers reside in a common broadcast
subnet, the router does not change the next hop for routes sent to the IPv6 EBGP peer/peer group by
default, unless the peer next-hop-local command is configured.
Configuring the MED attribute
To configure the MED attribute:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter BGP view. bgp as-number N/A
3. Enter IPv6 address family
view.
ipv6-family N/A
4. Configure a default MED
value.
default med med-value
Optional
0 by default
5. Enable the comparison of
MED for routes from different
EBGP peers.
compare-different-as-med
Optional
Not enabled by default
6. Enable the comparison of
MED for routes from each AS. bestroute compare-med Optional
Disabled by default
7. Enable the comparison of
MED for routes from
confederation peers. bestroute med-confederation
Optional
Disabled by default
Configuring the AS_PATH attribute
To configure the AS_PATH attribute:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter BGP view. bgp as-number N/A
3. Enter IPv6 address family
view.
ipv6-family N/A
4. Allow the local AS number to
appear in AS_PATH of routes
from a peer/peer group and
specify the repeat times.
peer { ipv6-group-name |
ipv6-address } allow-as-loop
[ number ]
Optional.
Not allowed by default.
5. Specify a fake AS number for
an IPv6 peer/peer group. peer { ipv6-group-name |
ipv6-address } fake-as as-number Optional.
Not specified by default.