Configuring a BGP MDT route reflector
About configuring BGP MDT route reflectors
Configuring a BGP MDT route reflector—BGP MDT peers in the same AS must be fully meshed to maintain connectivity. However, when multiple BGP MDT peers exist in an AS, connection establishment among them might result in increased costs. To reduce connections between BGP MDT peers, you can configure one of them as a route reflector and specify other devices as clients.
Disabling routing reflection between clients—When clients establish BGP MDT connections with the route reflector, the route reflector forwards (or reflects) BGP MDT routing information between clients. The clients are not required to be fully meshed. To save bandwidth if the clients have been fully meshed, you can disable the routing reflection between clients by using the undo reflect between-clients command.
Configuring the cluster ID of the route reflector—The route reflector and its clients form a cluster. Typically, a cluster has only one route reflector whose router ID identifies the cluster. However, you can configure several route reflectors in a cluster to improve network reliability. To avoid routing loops, make sure the route reflectors in a cluster have the same cluster ID.
Procedure
Enter system view.
system-view
Enter BGP instance view.
bgp as-number [ instance instance-name ]
Enter BGP IPv4 MDT address family view.
address-family ipv4 mdt
Configure the device as a route reflector and specify its peers or peer groups as clients.
peer { group-name | ip-address [ mask-length ] } reflect-client
By default, neither route reflectors nor clients exist.
(Optional.) Disable route reflection between clients.
undo reflect between-clients
By default, route reflection between clients is disabled.
For more information about this command, see Layer 3—IP Routing Command Reference.
(Optional.) Configure the cluster ID of the route reflector.
reflector cluster-id { cluster-id | ip-address }
By default, a route reflector uses its router ID as the cluster ID.
For more information about this command, see Layer 3—IP Routing Command Reference.