H3C Technologies H3C S10500 Series Switches - Manual (Page 264)

249
Configuring MBGP community
The community attribute can be advertised between MBGP peers in different ASs. Routers in the same
community share the same policy.
You can reference a routing policy to modify the community attribute for routes sent to a peer. In addition,
you can define extended community attributes as needed.
Follow these steps to configure MBGP community:
To do… Use the command… Remarks
Enter system view system-view —
Enter BGP view bgp as-number —
Enter IPv4 MBGP address family
view
ipv4-family multicast —
Advertise the community attribute
to an MBGP peer or a peer group
Advertise the community attribute to an MBGP
peer or a peer group:
peer { group-name | ip-address }
advertise-community
Advertise the extended community attribute to
an MBGP peer or a peer group:
peer { group-name | ip-address }
advertise-ext-community
Required
Use either command
Not configured by
default.
Apply a routing policy to routes
advertised to an MBGP peer or a
peer group
peer { group-name | ip-address } route-policy
route-policy-name export
Required
Not configured by
default.
CAUTION:
•
When configuring MBGP community, you must reference a routing policy to define the specific
community attributes, and apply the routing policy for route advertisement.
• For routing policy configuration, see Layer 3—IP Routing Configuration Guide.
Configuring an MBGP route reflector
To guarantee the connectivity between multicast iBGP peers in an AS, you need to make them fully
meshed. But this becomes unpractical when large numbers of multicast iBGP peers exist. Configuring
route reflectors can solve this problem.
Follow these steps to configure an MBGP route reflector:
To do… Use the command… Remarks
Enter system view system-view —
Enter BGP view bgp as-number —
Enter IPv4 MBGP address family
view
ipv4-family multicast —