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):
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP view or BGP-VPN instance view. |
| N/A |
3. Enter BGP IPv4 unicast address family view or BGP-VPN IPv4 unicast address family view. | address-family ipv4 [ unicast ] | N/A |
4. Configure the router as a route reflector and specify a peer or peer group as its client. | peer { group-name | ip-address } reflect-client | By default, no route reflector or client is configured. |
5. Enable route reflection between clients. | reflect between-clients | By default, route reflection between clients is enabled. |
6. (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):
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP view. | bgp as-number | N/A |
3. Enter BGP IPv6 unicast address family view. | address-family ipv6 [ unicast ] | N/A |
4. 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. |
5. Enable route reflection between clients. | reflect between-clients | By default, route reflection between clients is enabled. |
6. (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
A router is configured with a router ID. When a router receives a BGP route update, it compares the router ID with the ORIGINATOR_ID attribute in the route update. If they are the same, the router drops the route update to avoid routing loops. However, for some networks (such as firewall networks) to operate correctly, BGP must not drop but accept such route updates. For BGP to accept such route updates, you must configure BGP to ignore the ORIGINATOR_ID attribute in BGP route updates.
To ignore the ORIGINATOR_ID attribute (IPv4):
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP view or BGP-VPN instance view. |
| N/A |
3. Ignore the ORIGINATOR_ID attribute. | peer { group-name | ip-address } ignore-originatorid | By default, BGP does not ignore the ORIGINATOR_ID attribute. Make sure that 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):
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP view or BGP-VPN instance view. |
| N/A |
3. Ignore the ORIGINATOR_ID attribute. | peer { group-name | ipv6-address } 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. |