No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


ME60 V800R010C10SPC500 Feature Description - WAN Access 01

This is ME60 V800R010C10SPC500 Feature Description - WAN Access
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Community Attribute

Community Attribute

A community is a set of destination addresses with the same characteristics. It is four bytes long. On the ME60, the community attribute is expressed in the format of aa:nn or as a community number.

  • aa:nn: aa indicates an AS number and nn indicates the community identifier defined by an administrator. The value of aa or nn ranges from 0 to 65535, which is configurable. For example, if a route is from AS 100 and the community identifier defined by the administrator is 1, the community is 100:1.

  • Community number: It is an integer ranging from 0 to 4294967295. As defined in standard protocols, numbers from 0 (0x00000000) to 65535 (0x0000FFFF) and from 4294901760 (0xFFFF0000) to 4294967295 (0xFFFFFFFF) are reserved.

The community attribute is used to simplify the application, maintenance, and management of routing policies. With the community attribute, a group of BGP peers in multiple ASs can share the same routing policy. The community attribute is a route attribute. It is transmitted between BGP peers and is not restricted by the AS. Before advertising a route with the community attribute to peers, a BGP peer can change the original community attribute of this route.

The peers in a peer group share the same policy, while the routes with the same community attribute share the same policy.

The well-known communities are described in the next section. Users can also create their own communities to filter routes.

Well-known Community

Table 9-1 lists well-known communities of BGP routes.

Table 9-1 Well-known communities of BGP routes

Community Name

Community Identifier





By default, all routes belong to the Internet community. A route with this attribute can be advertised to all BGP peers.


4294967041 (0xFFFFFF01)

A route with this attribute cannot be advertised beyond the local AS.


4294967042 (0xFFFFFF02)

A route with this attribute cannot be advertised to any other BGP peers.


4294967043 (0xFFFFFF03)

A route with this attribute cannot be advertised beyond the local AS or to other sub-ASs.

Usage Scenario

On the network shown in Figure 9-8, EBGP connections are established between Device A and Device B, and between Device B and Device C. If the community attribute of No_Export is configured on Device A and Device A sends a route with the community attribute to Device B, Device B does not advertise the route to other ASs after receiving it.

Figure 9-8 Networking for BGP communities

Updated: 2019-01-04

Document ID: EDOC1100059473

Views: 14723

Downloads: 10

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next