BGP-4 is capable of carrying routing information for IPv4 only. IETF defined multiprotocol BGP extensions to carry routing information for multiple network layer protocols.

For a network, the multicast topology may be different from the unicast topology. To meet the requirement, the multiprotocol BGP extensions enable BGP to carry the unicast Network Layer Reachability Information (NLRI) and multicast NLRI separately, and the multicast NLRI is used to perform reverse path forwarding (RPF) exclusively. In this way, route selection for a destination through the unicast routing table and through the multicast routing table will have different results, ensuring normal unicast and multicast routing.

Multi-protocol BGP is defined in RFC 2858 (Multiprotocol Extensions for BGP-4).

Multi-protocol BGP for IP multicast is referred to as Multicast BGP (MBGP) for short.

l This document covers configuration tasks related to multiprotocol BGP for IP multicast only. For information about BGP, refer to BGP Configuration in the IP Routing Volume.

l For information about RPF, refer to Multicast Routing and Forwarding in the IP Multicast Volume.

Protocols and Standards

l RFC2858: Multiprotocol Extensions for BGP-4

l RFC3392: Capabilities Advertisement with BGP-4

l draft-ietf-idmr-bgp-mcast-attr-00: BGP Attributes for Multicast Tree Construction

MBGP Configuration Task List

Complete the following tasks to configure MBGP:

Task		Remarks
Configuring MBGP Basic Functions		Required
Controlling Route Advertisement and Reception	Configuring MBGP Route Redistribution	Optional
	Configure Default Route Redistribution into MBGP	Optional
	Configuring MBGP Route Summarization	Optional
	Advertising a Default Route to an IPv4 MBGP Peer or Peer Group	Optional
	Configuring Outbound MBGP Route Filtering	Optional
	Configuring Inbound MBGP Route Filtering	Optional
	Configuring MBGP Route Dampening	Optional
Configuring MBGP Route Attributes	Configuring MBGP Route Preferences	Optional
	Configuring the Default Local Preference
	Configuring the MED Attribute
	Configuring the Next Hop Attribute
	Configuring the AS-PATH Attribute
Tuning and Optimizing MBGP Networks	Configuring MBGP Soft Reset	Optional
Tuning and Optimizing MBGP Networks	Configuring the Maximum Number of MBGP Routes	Optional
Configuring a Large Scale MBGP Network	Configuring IPv4 MBGP Peer Groups	Optional
	Configuring MBGP Community	Optional
	Configuring an MBGP Route Reflector	Optional

Configuring MBGP Basic Functions

Prerequisites

Before configuring MBGP, make sure neighboring nodes can access each other at the network layer.

Configuration Procedure

Follow these steps to configure MBGP basic functions:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Enter BGP view	bgp as-number	—
Specify a peer or peer group and its AS number	peer { group-name \| ip-address } as-number as-number	Required Not specified by default.
Enter IPv4 MBGP address family view	ipv4-family multicast	Required
Enable a peer or peer group created in IPv4 unicast view	peer { group-name \| ip-address } enable	Required Not enabled by default
Specify a preferred value for routes from an IPv4 MBGP peer or peer group	peer { group-name \| ip-address } preferred-value value	Optional The default preferred value is 0.

Controlling Route Advertisement and Reception

Prerequisites

You need to configure MBGP basic functions before configuring this task.

Configuring MBGP Route Redistribution

MBGP can advertise routing information in the local AS to neighboring ASs. It redistributes such routing information from IGP into its routing table rather than learns the information by itself.

Follow these steps to configure MBGP route redistribution:

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	—
Redistribute routes from another routing protocol	import-route protocol [ process-id [ med med-value \| route-policy route-policy-name ] * ]	At least one of these approaches is required. No route redistribution is configured by default.
Inject a network into the MBGP routing table	network ip-address [ mask \| mask-length ] [ short-cut \| route-policy route-policy-name ]

l The Origin attribute of routes redistributed into the MBGP routing table with the import-route command is Incomplete.

l The Origin attribute of routes injected into the MBGP routing table with the network command is IGP.

l The networks to be injected must exist in the local IP routing table, and using a route policy makes route control more flexible.

Configure Default Route Redistribution into MBGP

You cannot use the import-route command to configure MBGP to redistribute default routes from other protocols. Instead, use the following commands:

Follow these steps to configure MBGP to redistribute default routes from other protocols

To do…	Use the command…	Remarks
Enter system view	system-view	—
Enter BGP view	bgp as-number	—
Enter MBGP address family view	ipv4-family multicast	—
Redistribute routes from another routing protocol	import-route protocol [ process-id [ med med-value \| route-policy route-policy-name ] * ]	Required No route redistribution is configured by default.
Enable default route redistribution into the MBGP routing table	default-route imported	Required Not enabled by default

Configuring MBGP Route Summarization

To reduce the routing table size on medium and large MBGP networks, you need to configure route summarization on peers. MBGP supports two summarization modes: automatic and manual.

l Automatic summarization: Summarizes subnets redistributed from IGP. With the feature configured, MBGP advertises only summary natural networks rather than subnets. The default routes and routes injected with the network command are not summarized.

l Manual summarization: Summarizes MBGP local routes. A manual summary route has a higher priority than an automatic one.

Follow these steps to configure MBGP route summarization:

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	—
Configure MBGP route summarization	Enable automatic route summarization	summary automatic	Required No route summarization is configured by default. Choose either as needed; if both are configured, the manual route summarization takes effect.
Configure MBGP route summarization	Configure manual route summarization	aggregate ip-address { mask \| mask-length } [ as-set \| attribute-policy route-policy-name \| detail-suppressed \| origin-policy route-policy-name \| suppress-policy route-policy-name ] *

Advertising a Default Route to an IPv4 MBGP Peer or Peer Group

Follow these steps to advertise a default route to an MBGP peer or peer group:

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 a default route to an MBGP peer or peer group	peer { group-name \| ip-address } default-route-advertise [ route-policy route-policy-name ]	Required Not advertised by default

With the peer default-route-advertise command executed, the router sends a default route with the next hop being itself to the specified MBGP peer or peer group, regardless of whether the default route is available in the routing table.

Configuring Outbound MBGP Route Filtering

If several filtering policies are configured, they are applied in the following sequence:

l filter-policy export

l peer filter-policy export

l peer as-path-acl export

l peer ip-prefix export

l peer route-policy export

Only the routes that have passed all the configured policies can be advertised.

Follow these steps to configure BGP route distribution filtering policies:

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	—
Configure the filtering of redistributed routes	filter-policy { acl-number \| ip-prefix ip-prefix-name } export [ direct \| isis process-id \| ospf process-id \| rip process-id \| static ]	At least one of these approaches is required. No outbound route filtering is configured by default
Apply a route policy to advertisements to an IPv4 MBGP peer/peer group	peer { group-name \| peer-address } route-policy route-policy-name export
Reference an ACL to filter advertisements to an IPv4 MBGP peer/peer group	peer { group-name \| ip-address } filter-policy acl-number export
Reference an AS path ACL to filer route advertisements to an IPv4 MBGP peer/peer group	peer { group-name \| ip-address } as-path-acl as-path-acl-number export
Reference an IP prefix list to filer route advertisements to an IPv4 MBGP peer/peer group	peer { group-name \| ip-address } ip-prefix ip-prefix-name export

Configuring Inbound MBGP Route Filtering

By configuring MBGP route reception filtering policies, you can filter out unqualified routes from an MBGP peer or peer group.

If several filtering policies are configured, they are applied in the following sequence:

l filter-policy import

l peer filter-policy import

l peer as-path-acl import

l peer ip-prefix import

l peer route-policy import

Only the routes that have passed all the configured policies can be advertised.

Follow these steps to configure MBGP route reception filtering policies:

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	—
Filter incoming routes using an ACL or IP prefix list	filter-policy { acl-number \| ip-prefix ip-prefix-name } import	At least one of these approaches is required. No inbound route filtering is configured by default.
Reference a route policy to routes from an IPv4 MBGP peer/peer group	peer { group-name \| ip-address } route-policy policy-name import
Reference an ACL to filter routing information from an IPv4 MBGP peer/peer group	peer { group-name \| ip-address } filter-policy acl-number import
Reference an AS path ACL to filter routing information from an IPv4 MBGP peer/peer group	peer { group-name \| ip-address } as-path-acl as-path-acl-number import
Reference an IP prefix list to filter routing information from an IPv4 MBGP peer/peer group	peer { group-name \| ip-address } ip-prefix ip-prefix-name import
Specify the maximum number of routes that can be received from an IPv4 MBGP peer/peer group	peer { group-name \| ip-address } route-limit limit [ percentage ]	Optional The number is unlimited by default.

Members of a peer group can have different route reception filtering policies from the peer group.

Configuring MBGP Route Dampening

By configuring MBGP route dampening, you can suppress unstable routes from being added to the MBGP routing table or being advertised to MBGP peers.

Follow these steps to configure BGP route dampening:

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	—
Configure BGP route dampening parameters	dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling \| route-policy route-policy-name ] *	Required Not configured by default

Configuring MBGP Route Attributes

You can modify MBGP route attributes to affect route selection.

Prerequisites

Before configuring this task, you need to configure MBGP basic functions.

Configuring MBGP Route Preferences

You can reference a route policy to set preferences for routes matching it. Routes not matching it use the default preferences.

Follow these steps to configure MBGP route preferences:

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	—
Configure preferences for external, internal, local MBGP routes	preference { external-preference internal-preference local-preference \| route-policy route-policy-name }	Optional The default preferences of multicast MBGP eBGP, MBGP iBGP, and local MBGP routes are 255, 255, and 130 respectively.

Configuring the Default Local Preference

Follow these steps to configure the default local preference:

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	—
Configure the default local preference	default local-preference value	Optional 100 by default.

Configuring the MED Attribute

When other conditions of routes to a destination are identical, the route with the smallest MED is selected.

Follow these steps to configure the MED attribute:

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	—
Configure the MED attribute	Configure the default MED value	default med med-value	Optional 0 by default.
	Enable the comparison of the MED of routes from different ASs	compare-different-as-med	Optional Not enabled by default
	Enable the comparison of the MED of routes from each AS	bestroute compare-med	Optional Not enabled by default
	Enable the comparison of the MED of routes from confederation peers	bestroute med-confederation	Optional Not enabled by default

Configuring the Next Hop Attribute

You can use the peer next-hop-local command to specify the local router as the next hop of routes sent to a MBGP iBGP peer/peer group. If load balancing is configured, the router specifies itself as the next hop of route advertisements to the multicast iBGP peer/peer group regardless of whether the peer next-hop-local command is configured.

In a “third party next hop" network, that is, the local router has two multicast eBGP peers in a broadcast network, the router does not specify itself as the next hop of routing information sent to the eBGP peers unless the peer next-hop-local command is configured.

Follow these steps to specify the router as the next hop of routes sent to a peer/peer group:

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	—
Specify the router as the next hop of routes sent to a peer/peer group	peer { group-name \| ip-address } next-hop-local	Optional By default, the next hop of routes sent to a MBGP eBGP peer/peer group is the advertising router, while that of routes sent to a MBGP iBGP peer/peer group is not.

Configuring the AS-PATH Attribute

In general, MBGP checks whether the AS_PATH attribute of a route from a peer contains the local AS number. If yes, it discards the route to avoid routing loops.

Follow these steps to configure the AS-PATH attribute:

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	—
Configure the AS_PATH attribute	Specify the maximum number of times the local AS number can appear in routes from the peer/peer group	peer { group-name \| ip-address } allow-as-loop [ number ]	Optional By default, the local AS number can not appear in routes from a peer/peer group.
	Disable BGP from considering the AS_PATH during best route selection	bestroute as-path-neglect	Optional By default, BGP considers AS_PATH during best route selection.
	Configure updates to a peer/peer group to not keep private AS numbers	peer { group-name \| ip-address } public-as-only	Optional By default, BGP updates carry private AS numbers.

Tuning and Optimizing MBGP Networks

This task involves resetting MBGP connections and configuring load balancing.

Prerequisites

You need to configure BGP basic functions before configuring this task.

Configuring MBGP Soft Reset

After modifying a route selection policy, you have to reset MBGP connections to make it take effect, causing short time disconnections.

After the route-refresh capability is enabled on all MBGP routers in a network, when a route selection policy is modified on a router, the local router can perform dynamic route updates without tearing down MBGP connections.

If the peer does not support route-refresh, you can save all route updates from the peer. When the route selection policy changes, you can refresh the MBGP routing table and apply the new policy without tearing down MBGP connections.

Soft reset through route-refresh

If the peer is enabled with route-refresh, when the MBGP route selection policy is modified on a router, the router advertises a route-refresh message to its MBGP peers, which resend their routing information to the router after receiving the message. Therefore, the local router can perform dynamic route update and apply the new policy without tearing down MBGP connections.

Follow these steps to configure MBGP soft reset through route-refresh:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Enter BGP view	bgp as-number	—
Enable BGP route refresh for a peer/peer group	peer { group-name \| ip-address } capability-advertise route-refresh	Optional Enabled by default

Perform a manual soft reset

If the peer does not support route-refresh, you can use the peer keep-all-routes command to save all the route updates from the peer, and then use the refresh bgp ipv4 multicast command to soft-reset MBGP connections to refresh the MBGP routing table and apply the new policy without tearing down MBGP connections.

Follow these steps to configure MBGP manual soft reset

To do…	Use the command…	Remarks
Enter system view	system-view	—
Enter BGP view	bgp as-number	—
Disable BGP route-refresh and multi-protocol extensions for a peer/peer group	peer { group-name \| ip-address } capability-advertise conventional	Optional Enabled by default
Enter IPv4 MBGP address family view	ipv4-family multicast	—
Keep all original routes from a peer/peer group regardless of whether they pass the inbound filtering policies	peer { group-name \| ip-address } keep-all-routes	Required Not kept by default
Return to user view	return	—
Soft-reset MBGP connections manually	refresh bgp ipv4 multicast { all \| ip-address \| group group-name \| external \| internal } { export \| import }	Optional

Configuring the Maximum Number of MBGP Routes for Load Balancing

Follow these steps to configure the number of MBGP routes for load balancing:

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	—
Configure the maximum number of MBGP routes for load balancing	balance number	Required Not configured by default.

Configuring a Large Scale MBGP Network

Prerequisites

Before configuring this task, you need to make peering nodes accessible to each other at the network layer.

Configuring IPv4 MBGP Peer Groups

In a large-scale network, configuration and maintenance become difficult due to large numbers of MBGP peers. You can configure peer groups to make management easier and improve route distribution efficiency.

Follow these steps to configure an IPv4 MBGP peer group:

To do…	Use the command…	Remarks
Enter system view	system-view	—
Enter BGP view	bgp as-number	—
Create a BGP peer group	group group-name [ external \| internal ]	Required Not created by default.
Add a peer into the peer group	peer ip-address group group-name [ as-number as-number ]	Required No peer is added by default.
Enter IPv4 MBGP address family view	ipv4-family multicast	—
Enable the IPv4 unicast peer group	peer group-name enable	Required
Add an IPv4 MBGP peer to the peer group	peer ip-address group group-name	Required Not configured by default.

l To configure an MBGP peer group, you need to enable the corresponding IPv4 BGP unicast peer group in IPv4 MBGP address family view.

l Before adding an MBGP peer to an MBGP peer group, you need to add the corresponding IPv4 unicast peer to the IPv4 BGP peer group.

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 route 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/peer group	Advertise the community attribute to an MBGP peer/peer group	peer { group-name \| ip-address } advertise-community	Required Not configured by default.
	Advertise the extended community attribute to an MBGP peer/peer group	peer { group-name \| ip-address } advertise-ext-community	Required Not configured by default.
Apply a route policy to routes advertised to an MBGP peer/peer group		peer { group-name \| ip-address } route-policy route-policy-name export	Required Not configured by default.

l When configuring MBGP community, you need to reference a route policy to define the specific community attributes, and apply the route policy for route advertisement.

l For route policy configuration, refer to Route Policy Configuration in the IP Routing Volume.

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 there are large numbers of multicast iBGP peers. 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	—
Configure the router as a route reflector and specify an MBGP peer/peer group as its client	peer { group-name \| peer-address } reflect-client	Required Not configured by default.
Enable route reflection between clients	reflect between-clients	Optional Enabled by default.
Configure the cluster ID of the route reflector	reflector cluster-id cluster-id	Optional By default, a route reflector uses its router ID as the cluster ID.

l 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.

l In general, a cluster has only one route reflector, and the router ID of the route reflector is used to identify 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.

Displaying and Maintaining MBGP

Displaying MBGP

To do…	Use the command…	Remarks
Display the IPv4 MBGP routing table	display ip multicast routing-table [ verbose]	Available in any view
Display the IPv4 MBGP routing information matching the specified destination IP address	display ip multicast routing-table ip-address [ mask-length \| mask ] [ longer-match ] [ verbose ]	Available in any view
Display MBGP peer group information	display bgp multicast group [ group-name ]	Available in any view
Display the advertised networks	display bgp multicast network	Available in any view
Display AS path information	display bgp multicast paths [ as-regular-expression ]	Available in any view
Display MBGP peer/peer group information	display bgp multicast peer [ ip-address { log-info \| verbose } \| group-name log-info \| verbose ]	Available in any view
Display MBGP routing information	display bgp multicast routing-table [ ip-address [ { mask \| mask-length } [ longer-prefixes ] ] ]	Available in any view
Display MBGP routing information matching the AS path ACL	display bgp multicast routing-table as-path-acl as-path-acl-number	Available in any view
Display MBGP CIDR routing information	display bgp multicast routing-table cidr	Available in any view
Display MBGP routing information matching the specified BGP community	display bgp multicast routing-table community[ aa:nn&<1-13> ] [ no-advertise \| no-export \| no-export-subconfed ] * [ whole-match ]	Available in any view
Display MBGP routing information matching an MBGP community list	display bgp multicast routing-table community-list { basic-community-list-number [ whole-match ] \| adv-community-list-number }&<1-16>	Available in any view
Display MBGP dampened routing information	display bgp multicast routing-table dampened	Available in any view
Display MBGP dampening parameter information	display bgp multicast routing-table dampening parameter	Available in any view
Display MBGP routing information originating from different ASs	display bgp multicast routing-table different-origin-as	Available in any view
Display IPv4 MBGP routing flap statistics	display bgp multicast routing-table flap-info [ regular-expression as-regular-expression \| as-path-acl as-path-acl-number \| ip-address [ { mask \| mask-length } [ longer-match ] ] ]	Available in any view
Display IPv4 MBGP routing information sent to or received from an MBGP peer	display bgp multicast routing-table peer ip-address { advertised-routes \| received-routes } [ network-address [ mask \| mask-length ] \| statistic ]	Available in any view
Display IPv4 MBGP routing information matching an AS regular expression	display bgp multicast routing-table regular-expression as-regular-expression	Available in any view
Display IPv4 MBGP routing statistics	display bgp multicast routing-table statistic	Available in any view

Resetting MBGP Connections

To do…	Use the command…	Remarks
Reset specified MBGP connections	reset bgp ipv4 multicast { all \| as-number \| ip-address \| group group-name \| external \| internal }	Available in user view

Clearing MBGP Information

To do…	Use the command…	Remarks
Clear dampened routing information and release suppressed routes	reset bgp ipv4 multicast dampening [ ip-address [ mask \| mask-length ] ]	Available in user view
Clear MBGP route flap statistics	reset bgp ipv4 multicast flap-info [ regexp as-path-regexp \| as-path-acl as-path-acl-number \| ip-address [ mask \| mask-length ] ]	Available in user view

MBGP Configuration Example

Network requirements

As shown in the following figure:

l PIM-SM 1 is in AS 100 and PIM-SM 2 is in AS 200. OSPF is the IGP in the two ASs, and MBGP runs between the two ASs to exchange multicast route information.

l The multicast source belongs to PIM-SM 1, and the receiver belongs to PIM-SM 2.

l It is required that the respective Loopback 0 of Switch A and Switch B be configured as the C-BSR and C-RP of the respective PIM-SM domains.

l Router A and Router B establishes an MSDP peer relationship through MBGP.

Network diagram

Figure 1-1 Network diagram for MBGP configuration

Device	Interface	IP address	Device	Interface	IP address
Source	—	10.110.1.100/24	Switch C	Vlan-int200	10.110.2.1/24
Switch A	Vlan-int100	10.110.1.1/24		Vlan-int102	192.168.2.2/24
	Vlan-int101	192.168.1.1/24		Vlan-int104	192.168.4.1/24
	Loop0	1.1.1.1/32		Loop0	3.3.3.3/32
Switch B	Vlan-int101	192.168.1.2/24	Switch D	Vlan-int103	192.168.3.2/24
	Vlan-int102	192.168.2.1/24		Vlan-int104	192.168.4.2/24
	Vlan-int103	192.168.3.1/24		Loop0	4.4.4.4/32
	Loop0	2.2.2.2/32

Configuration procedure

1) Configure IP addresses for interfaces as shown in the above figure (omitted).

2) Configure OSPF (omitted).

3) Enable IP multicast routing, PIM-SM and IGMP, and configure a PIM-SM domain border.

# Enable IP multicast routing on Switch A, and enable PIM-SM on each interface.

<SwitchA> system-view

[SwitchA] multicast routing-enable

[SwitchA] interface vlan-interface 100

[SwitchA-Vlan-interface100] pim sm

[SwitchA-Vlan-interface100] quit

[SwitchA] interface vlan-interface 101

[SwitchA-Vlan-interface101] pim sm

[SwitchA-Vlan-interface101] quit

The configuration on Switch B and Switch D is similar to the configuration on Switch A.

# Enable IP multicast routing on Switch C, enable PIM-SM on each interface, and enable IGMP on the host-side interface VLAN-interface 200.

<SwitchC> system-view

[SwitchC] multicast routing-enable

[SwitchC] interface vlan-interface 102

[SwitchC-Vlan-interface102] pim sm

[SwitchC-Vlan-interface102] quit

[SwitchC] interface vlan-interface 104

[SwitchC-Vlan-interface104] pim sm

[SwitchC-Vlan-interface104] quit

[SwitchC] interface vlan-interface 200

[SwitchC-Vlan-interface200] pim sm

[SwitchC-Vlan-interface200] igmp enable

[SwitchC-Vlan-interface200] quit

# Configure a PIM domain border on Switch A.

[SwitchA] interface vlan-interface 101

[SwitchA-Vlan-interface101] pim bsr-boundary

[SwitchA-Vlan-interface101] quit

# Configure a PIM domain border on Switch B.

[SwitchB] interface vlan-interface 101

[SwitchB-Vlan-interface101] pim bsr-boundary

[SwitchB-Vlan-interface101] quit

4) Configure Loopback 0 and the position of C-BSR, and C-RP.

# Configure Loopback 0 and configure it as the C-BSR and C-RP on Switch A.

[SwitchA] interface loopback 0

[SwitchA-LoopBack0] ip address 1.1.1.1 32

[SwitchA-LoopBack0] pim sm

[SwitchA-LoopBack0] quit

[SwitchA] pim

[SwitchA-pim] c-bsr loopback 0

[SwitchA-pim] c-rp loopback 0

[SwitchA-pim] quit

# Configure Loopback 0 and configure it as the C-BSR and C-RP on Switch B.

[SwitchB] interface loopback 0

[SwitchB-LoopBack0] ip address 2.2.2.2 32

[SwitchB-LoopBack0] pim sm

[SwitchB-LoopBack0] quit

[SwitchB] pim

[SwitchB-pim] c-bsr loopback 0

[SwitchB-pim] c-rp loopback 0

[SwitchB-pim] quit

5) Configure BGP, specify the MBGP peer and enable direct route redistribution.

# On Switch A, configure the MBGP peer and enable direct route redistribution.

[SwitchA] bgp 100

[SwitchA-bgp] router-id 1.1.1.1

[SwitchA-bgp] peer 192.168.1.2 as-number 200

[SwitchA-bgp] import-route direct

[SwitchA-bgp] ipv4-family multicast

[SwitchA-bgp-af-mul] peer 192.168.1.2 enable

[SwitchA-bgp-af-mul] import-route direct

[SwitchA-bgp-af-mul] quit

[SwitchA-bgp] quit

# On Switch B, configure the MBGP peer and enable route redistribution from OSPF.

[SwitchB] bgp 200

[SwitchB-bgp] router-id 2.2.2.2

[SwitchB-bgp] peer 192.168.1.1 as-number 100

[SwitchB-bgp] import-route ospf 1

[SwitchB-bgp] ipv4-family multicast

[SwitchB-bgp-af-mul] peer 192.168.1.1 enable

[SwitchB-bgp-af-mul] import-route ospf 1

[SwitchB-bgp-af-mul] quit

[SwitchB-bgp] quit

6) Configure MSDP peer

# Specify the MSDP peer on Switch A.

[SwitchA] msdp

[SwitchA-msdp] peer 192.168.1.2 connect-interface vlan-interface 101

[SwitchA-msdp] quit

# Specify the MSDP peer on Switch B.

[SwitchB] msdp

[SwitchB-msdp] peer 192.168.1.1 connect-interface vlan-interface 101

[SwitchB-msdp] quit

7) Verify the configuration

You can use the display bgp multicast peer command to display MBGP peers on a switch. For example, display MBGP peers on Switch B.

[SwitchB] display bgp multicast peer

BGP local router ID : 2.2.2.2

Local AS number : 200

Total number of peers : 3 Peers in established state : 3

Peer V AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State

192.168.1.1 4 100 56 56 0 0 00:40:54 Established

You can use the display msdp brief command to display MSDP peers on a switch. For example, display brief information about MSDP peers on Switch B.

[SwitchB] display msdp brief

MSDP Peer Brief Information of VPN-Instance: public net

Configured Up Listen Connect Shutdown Down

1 1 0 0 0 0

Peer's Address State Up/Down time AS SA Count Reset Count

192.168.1.1 Up 00:07:17 100 1 0

04-IP Multicast Volume

1 MBGP Configuration

Protocols and Standards

Configuration Procedure

Configure Default Route Redistribution into MBGP

Advertising a Default Route to an IPv4 MBGP Peer or Peer Group

Soft reset through route-refresh

Perform a manual soft reset

Configuring the Maximum Number of MBGP Routes for Load Balancing

Network requirements

Network diagram

Configuration procedure

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us