Configuring the Route Server Function

This section describes how to configure the route server function. The function reduces network resource consumption onASBRs.

Usage Scenario

In some scenarios on the live network, to achieve network traffic interworking, EBGP full-mesh connections may be required. However, establishing full-mesh connections among devices that function as ASBRs is costly and places high requirements on the performance of the devices, which adversely affects the network topology and device expansion. The route server function is similar to the RR function in IBGP scenarios and allows devices to advertise routes to their clients (ASBR devices) without changing route attributes, such as AS_Path, Nexthop, and MED. With the route server function, EBGP full-mesh connections are not required among the ASBR devices, which reduces network resource consumption.

Pre-configuration Tasks

Before configuring the route server function, configure basic BGP functions.

Procedure

Run system-view
The system view is displayed.
Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
(Optional) Run ipv4-family unicast
The IPv4 unicast address family view is displayed.
Run peer { ipv4-address | group-name } route-server-client
The route server function is enabled on the device, and an EBGP peer is specified as its client.
Run commit
The configuration is committed.

Verifying the Route Server Configuration

After configuring the route server function, verify the configuration.

Run the display bgp routing-table command to view routes in the BGP routing table.