1-11
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter BGP view
bgp
as-number
—
Enter IPv6 address family view
ipv6-family
—
Configure preference values for
IPv6 BGP external, internal,
local routes
preference
{
external-preference
internal-preference
local-preference
|
route-policy
route-policy-name
}
Optional
The default preference values of
external, internal and local routes are
255, 255, 130 respectively.
Configure the default local
preference
default
local-preference
value
Optional
The
value
defaults to 100.
Advertise routes to an IPv6
peer/peer group with the local
router as the next hop
peer
{
ipv6-group-name
| ipv6-address
}
next-hop-local
Required
By default, IPv6 BGP specifies the
local router as the next hop for routes
sent to an IPv6 eBGP peer/peer group,
but not for routes sent to an IPv6 iBGP
peer/peer group.
z
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.
z
In a “third party next hop" network, that is, the two IPv6 eBGP peers reside in a common broadcast
subnet, the router does not specify itself as 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
Follow these steps to configure the MED attribute:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter BGP view
bgp
as-number
—
Enter IPv6 address family view
ipv6-family
—
Configure a default MED value
default med med-value
Optional
Defaults to 0
Enable the comparison of MED
for routes from different eBGP
peers
compare-different-as-med
Optional
Not enabled by default.
Enable the comparison of MED
for routes from each AS
bestroute compare-med
Optional
Disabled by default
