Configuring BGP route reflection

Configuring a BGP route reflector

Perform this task to configure a BGP route reflector and its clients. The route reflector and its clients automatically form a cluster identified by the router ID of the route reflector. The route reflector forwards route updates among its clients.

To improve availability, you can specify multiple route reflectors for a cluster. The route reflectors in the cluster must have the same cluster ID to avoid routing loops.

To configure a BGP route reflector (IPv4 unicast/multicast address family):

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP IPv4 unicast address family view, BGP-VPN IPv4 unicast address family view, or BGP IPv4 multicast address family view.	Enter BGP IPv4 unicast address family view: bgp as-number [ instance instance-name ] address-family ipv4 [ unicast ] Enter BGP-VPN IPv4 unicast address family view: bgp as-number [ instance instance-name ] ip vpn-instance vpn-instance-name address-family ipv4 [ unicast ] Enter BGP IPv4 multicast address family view: bgp as-number [ instance instance-name ] address-family ipv4 multicast	N/A
3. Configure the router as a route reflector and specify a peer or peer group as its client.	peer { group-name \| ipv4-address [ mask-length ] } 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 \| ipv4-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: bgp as-number [ instance instance-name ] address-family ipv6 [ unicast ] Enter BGP IPv6 multicast address family view: bgp as-number [ instance instance-name ] 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 [ prefix-length ] } 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 \| ipv4-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 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 instance view or BGP-VPN instance view.

Enter BGP instance view:bgp as-number [ instance instance-name ]
Enter BGP-VPN instance view:
1. bgp as-number [ instance instance-name ]
2. ip vpn-instance vpn-instance-name

N/A

3. Ignore the ORIGINATOR_ID attribute.

peer { group-name | ipv4-address [ mask-length ] } ignore-originatorid

By default, BGP does not ignore the ORIGINATOR_ID attribute.

Make sure this command does not result in a routing loop.

After you execute this command, BGP also ignores the CLUSTER_LIST attribute.

To ignore the ORIGINATOR_ID attribute (IPv6 unicast/multicast address family):