Configuration Prerequisites; Configuring Ipv6 Bgp Preference And Default Local_Pref And Next_Hop Attributes; Configuring The Med Attribute - HPE 5800 Series Configuration Manual

Configuration prerequisites

Before you configure IPv6 BGP route attributes, complete the following tasks:
•
Enable IPv6 function.
•
Configure IPv6 BGP basic functions.
Configuring IPv6 BGP preference and default LOCAL_PREF
and NEXT_HOP attributes
To ensure an IBGP peer can find the correct next hop, you can configure routes advertised to the
IPv6 IBGP peer or 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 or
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 or peer group
by default, unless the peer next-hop-local command is configured.
To perform this configuration:
Step
Enter system view.
1.
Enter BGP view.
2.
Enter IPv6 address family
3.
view or IPv6 BGP-VPN
instance view.
Configure preference values
4.
for IPv6 BGP external,
internal, local routes.
Configure the default local
5.
preference.
Advertise routes to an IPv6
6.
peer or peer group with the
local router as the next hop.

Configuring the MED attribute

Step
Enter system view.
1.
Enter BGP view.
2.
Command
system-view
bgp as-number
ipv6-family [ vpn-instance
vpn-instance-name ]
preference
{ external-preference
internal-preference
local-preference |
route-policy
route-policy-name }
default local-preference
value
peer { ipv6-group-name |
ipv6-address } next-hop-local
Command
system-view
bgp as-number
325
Remarks
N/A
N/A
N/A
Optional.
The default preference values of
external, internal, and local routes
are 255, 255, and 130, respectively.
Optional.
The value defaults to 100.
By default, IPv6 BGP specifies the
local router as the next hop for routes
sent to an IPv6 EBGP peer or peer
group, but does not change the next
hop for routes sent to an IPv6 IBGP
peer or peer group.
The IPv6 BGP-VPN instance view
does not support this command.
Remarks
N/A
N/A