Configuring Bgp4+ Route Aggregation - Huawei Quidway NetEngine80E Configuration Manual

HUAWEI NetEngine80E/40E Router
Configuration Guide - IP Routing
You can use the network command to statically inject the IPv6 routes to the BGP4+ routing
table.
To be specific, the command can be used to advertise the routes only with the exactly-matched
address prefix and mask. If the mask is not designated, the routes are exactly matched based on
the natural network segment.
The local routes to be advertised should be in the local IPv6 routing table. You can use routing
policies to control the routes to be advertised more flexibly.
----End

9.4.3 Configuring BGP4+ Route Aggregation

By configuring route aggregation, you can reduce the size of the routing table of a peer. BGP4
+ supports automatic aggregation and manual aggregation.
Procedure
Step 1 Run:
system-view
The system view is displayed.
Step 2 Run:
bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
Step 3 Run:
ipv6-family [ unicast ]
The IPv6 unicast address family view is displayed.
Step 4 Run:
aggregate ipv6-address prefix-length [ as-set | attribute-policy route-policy-
name1 | detail-suppressed | origin-policy route-policy-name2 | suppress-policy
route-policy-name3 ]
Manual aggregation of routes is configured.
Manual aggregation is valid for the routing entries in the local BGP4+ routing table. For example,
if 9:3::1/64 does not exist in the BGP routing table, BGP4+ does not advertise the aggregated
route even after the aggregate 9:3::1 64 command is run to aggregate this route.
When configuring manual aggregation of routes, you can apply various routing policies and set
the route attributes.
----End
9.4.4 Configuring BGP4+ to Import and Filter External Routes
After BGP4+ filters the imported routes, only the eligible routes are added to the local BGP4+
routing table and advertised to BGP4+ peers.
Issue 02 (2014-09-30)
*
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
9 BGP4+ Configuration
1063