256
Step Command
Remarks
5.
(Optional.) Configure the
cluster ID of the route
reflector.
reflector cluster-id
{
cluster-id
|
ip-address
}
By default, a route reflector uses
its own router ID as the cluster
ID.
To configure a BGP route reflector (IPv6 unicast/multicast address family):
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP IPv6 unicast
address family view or BGP
IPv6 multicast address
family view.
•
Enter BGP IPv6 unicast address
family view:
a.
bgp
as-number
b.
address-family ipv6
[
unicast
]
•
Enter BGP IPv6 multicast address
family view:
a.
bgp
as-number
b.
address-family ipv6 multicast
N/A
3.
Configure the router as a
route reflector and specify a
peer or peer group as its
client.
peer
{
group-name
|
ipv6-address
}
reflect-client
By default, no route reflector or
client is configured.
4.
Enable route reflection
between clients.
reflect between-clients
By default, route reflection
between clients is enabled.
5.
(Optional.) Configure the
cluster ID of the route
reflector.
reflector cluster-id
{
cluster-id
|
ip-address
}
By default, a route reflector uses
its own router ID as the cluster
ID.
Ignoring the ORIGINATOR_ID attribute
By default, BGP drops incoming route updates whose ORIGINATOR_ID attribute is the same as the local
router ID. Some special networks such as firewall networks require BGP to accept such route updates. To
meet the requirement, you must configure BGP to ignore the ORIGINATOR_ID attribute.
To ignore the ORIGINATOR_ID attribute (IPv4 unicast/multicast address family):
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter BGP view or BGP-VPN
instance view.
•
Enter BGP view:
bgp
as-number
•
Enter BGP-VPN instance view:
a.
bgp
as-number
b.
ip vpn-instance
vpn-instance-name
N/A
