199
When you configure 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.
To configure MBGP community:
Ste
Remarks
1. Enter system view.
system-view N/A
2. Enter BGP view.
bgp as-number N/A
3. Enter IPv4 MBGP address
family view.
ipv4-family multicast N/A
4. 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
Use either command
Not configured by
default.
5. 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
Not configured by
default.
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.
In general, it is not required that clients of a route reflector be fully meshed. The route reflector forwards
routing information between clients. If clients are fully meshed, you can disable route reflection between
clients to reduce routing costs.
In general, a cluster has only one route reflector, and the router ID of the route reflector identifies the
cluster. You can configure multiple route reflectors to improve network stability. In this case, you need to
specify the same cluster ID for these route reflectors to avoid routing loops.
To configure an MBGP route reflector:
Ste
To Next Page
Loading...
