Enabling a BGP4+ Device to Add the Large-Community Attribute to Routes to Be Advertised
The Large-Community attribute can be flexibly applied in route-policies.
Context
The Large-Community attribute can represent a 2-byte or 4-byte Autonomous System Number (ASN), and has two 4-byte LocalData IDs. The administrator can therefore apply route-policies more flexibly. The Large-Community attribute extends and can be used together with a community attribute.
Procedure
- Run system-view
The system view is displayed.
- Run bgp { as-number-plain | as-number-dot }
The BGP view is displayed.
- Run ipv6-family unicast
The IPv6 unicast address family view is displayed.
- Run peer { ipv4-address | ipv6-address | group-name } route-policy route-policy-name export
An export route-policy is applied to routes to be advertised to a specified peer or peer group.
When configuring the BGP4+ Large-Community attribute, use a route-policy to define specific Large-Community values, and then apply the route-policy to the routes to be advertised.
For details about the route-policy configuration, see Routing Policy Configuration.
- Run peer { ipv4-address | ipv6-address | group-name } advertise-large-community
The device is enabled to advertise the Large-Community attribute to the specified peer or peer group.
- Run commit
The configuration is committed.