BGP-4 can carry routing information for IPv4 only. IETF defined multiprotocol BGP extensions to carry routing information for multiple network layer protocols.

On an IPv6 network, the IPv6 multicast topology must be different from the IPv6 unicast topology. To meet the requirement, the multiprotocol BGP extensions enable IPv6 BGP to carry the IPv6 unicast Network Layer Reachability Information (NLRI) and IPv6 multicast NLRI separately, and the multicast NLRI performs reverse path forwarding (RPF) exclusively. In this way, route selection for a destination through the IPv6 unicast routing table and through the IPv6 multicast routing table will have different results, ensuring the normal unicast and multicast operation across ASs.

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

Multiprotocol BGP for IPv6 multicast is called “IPv6 MBGP.”

NOTE:

· This document covers configuration tasks related to multiprotocol BGP for IPv6 multicast only. For BGP related information, see Layer 3—IP Routing Configuration Guide.

· For information about RPF, see the chapter “Configuring multicast routing and forwarding.”

IPv6 MBGP configuration task list

Complete the following tasks to configure IPv6 MBGP:

Task		Remarks
Configuring basic IPv6 MBGP functions	Configuring an IPv6 MBGP peer	Required
Configuring basic IPv6 MBGP functions	Configuring a preferred value for routes from a peer or a peer group	Optional
Controlling route distribution and reception	Injecting a local IPv6 MBGP route	Optional
	Configuring IPv6 MBGP route redistribution	Optional
	Configuring IPv6 MBGP route summarization	Optional
	Advertising a default route to a peer or peer group	Optional
	Configuring outbound IPv6 MBGP route filtering	Optional
	Configuring inbound IPv6 MBGP route filtering	Optional
	Configuring IPv6 MBGP route dampening	Optional
Configuring IPv6 MBGP route attributes	Configuring IPv6 MBGP route preferences	Optional
	Configuring the default local preference	Optional
	Configuring the MED attribute	Optional
	Configuring the next_hop attribute	Optional
	Configuring the as_path attribute	Optional
Tuning and optimizing IPv6 MBGP networks	Configuring IPv6 MBGP soft reset	Optional
	Enabling the IPv6 MBGP ORF capability	Optional
	Configuring the maximum number of equal-cost routes for load-balancing	Optional
Configuring a large scale IPv6 MBGP network	Configuring an IPv6 MBGP peer group	Optional
	Configuring IPv6 MBGP community	Optional
	Configuring an IPv6 MBGP route reflector	Optional

Configuring basic IPv6 MBGP functions

Configuration prerequisites

IPv6 MBGP is an application of multiprotocol BGP. Before you configure IPv6 MBGP, complete the following tasks:

· Enable IPv6.

· Configure network layer addresses for interfaces.

· Complete BGP basic configuration.

Configuring an IPv6 MBGP peer

To configure an IPv6 MBGP peer

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable BGP and enter BGP view.	bgp as-number	Not enabled by default
3. Enter IPv6 address family view.	ipv6-family	N/A
4. Specify a IPv6 BGP peer and its AS number.	peer ipv6-address as-number as-number	Not configured by default
5. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
6. Enable the IPv6 MBGP peer.	peer ipv6-address enable	Not enabled by default

Configuring a preferred value for routes from a peer or a peer group

To configure a preferred value for routes from a peer or a peer group:

Step	Command	Remarks
7. Enter system view.	system-view	N/A
8. Enter BGP view.	bgp as-number	N/A
9. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
10. Specify a preferred value for routes received from the IPv6 MBGP peer or the peer group.	peer { ipv6-group-name \| ipv6-address } preferred-value value	Optional. The preferred value defaults to 0.

CAUTION:

If you both reference a routing policy and use the command peer { ipv6-group-name | ipv6-address } preferred-value value to set a preferred value for routes from a peer or a peer group, the routing policy sets the specified preferred value for routes that match it. Other routes that do not match the routing policy use the value set through the command. If the preferred value in the routing policy is 0, the routes that match it also use the value set through the peer { ipv6-group-name | ipv6-address } preferred-value value command. To learn how to use a routing policy to set a preferred value, see the peer { ipv6-group-name | ipv6-address } route-policy route-policy-name { import | export } command and the apply preferred-value preferred-value command in Layer 3—IP Routing Command Reference.

Controlling route distribution and reception

Configuration prerequisites

Before you configure this task, complete the following tasks:

· Enable IPv6

· Configure the IPv6 MBGP basic functions

Injecting a local IPv6 MBGP route

To inject a local IPv6 MBGP route:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Inject a network to the IPv6 MBGP routing table.	network ipv6-address prefix-length [ route-policy route-policy-name \| short-cut ]	Not injected by default

Configuring IPv6 MBGP route redistribution

To configure IPv6 MBGP route redistribution:

Step	Command	Description
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP multicast address family view.	ipv6-family multicast	N/A
4. Enable default route redistribution into the IPv6 MBGP routing table.	default-route imported	Optional. By default, default route redistribution is not allowed.
5. Enable route redistribution from another routing protocol.	import-route protocol [ process-id [ med med-value \| route-policy route-policy-name ] * ]	Not enabled by default.

NOTE:

If the default-route imported command is not configured, using the import-route command cannot redistribute any IGP default route.

Configuring IPv6 MBGP route summarization

To reduce the routing table size on medium and large BGP networks, you must configure route summarization on IPv6 MBGP routers. BGP supports only manual summarization of IPv6 multicast routes.

To configure IPv6 MBGP route summarization:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Configure manual route summarization.	aggregate ipv6-address prefix-length [ as-set \| attribute-policy route-policy-name \| detail-suppressed \| origin-policy route-policy-name \| suppress-policy route-policy-name ]*	Not configured by default

Advertising a default route to a peer or peer group

To advertise a default route to a peer or peer group

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Advertise a default route to an IPv6 MBGP peer or peer group.	peer { ipv6-group-name \| ipv6-address } default-route-advertise [ route-policy route-policy-name ]	Not advertised by default

NOTE:

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

Configuring outbound IPv6 MBGP route filtering

To configure outbound IPv6 MBGP route filtering:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Configure outbound IPv6 MBGP route filtering.	· Configure the filtering of outgoing routes: filter-policy { acl6-number \| ipv6-prefix ipv6-prefix-name } export [ protocol process-id ] · Specify an IPv6 ACL to filter routes advertised to a peer or a peer group: peer { ipv6-group-name \| ipv6-address } filter-policy acl6-number export · Specify an AS path ACL to filter IPv6 MBGP routing information advertised to a peer or a peer group: peer { ipv6-group-name \| ipv6-address } as-path-acl as-path-acl-number export · Specify an IPv6 prefix list to filter routes advertised to a peer or a peer group: peer { ipv6-group-name \| ipv6-address } ipv6-prefix ipv6-prefix-name export · Apply a routing policy to routes advertised to a peer or a peer group: peer { ipv6-group-name \| ipv6-address } route-policy route-policy-name export	Use one of the approaches. By default, no filtering is configured. You can configure filter policies as required. If you configure multiple filter policies, they are applied in the following order: 1. filter-policy export 2. peer filter-policy export 3. peer as-path-acl export 4. peer ipv6-prefix export 5. peer route-policy export A filter policy can be applied only after the previous one is passed. Routing information can be advertised only after passing all the configured filter policies.

NOTE:

· Members of an IPv6 MBGP peer group must have the same outbound route filtering policy as the peer group.

· IPv6 BGP advertises redistributed routes that pass the specified policy to the IPv6 MBGP peer.

Configuring inbound IPv6 MBGP route filtering

To configure IPv6 MBGP inbound route filtering:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Configure IPv6 MBGP inbound route filtering.	· Configure inbound route filtering: filter-policy { acl6-number \| ipv6-prefix ipv6-prefix-name } import · Apply a routing policy to routes from a peer or a peer group: peer { ipv6-group-name \| ipv6-address } route-policy route-policy-name import · Specify an IPv6 ACL to filter routes from a peer or a peer group: peer { ipv6-group-name \| ipv6-address } filter-policy acl6-number import · Specify an AS path ACL to filter IPv6 BGP routing information from a peer or a peer group: peer { ipv6-group-name \| ipv6-address } as-path-acl as-path-acl-number import · Specify an IPv6 prefix list to filter routes from a peer or a peer group: peer { ipv6-group-name \| ipv6-address } ipv6-prefix ipv6-prefix-name import	Use one of the approaches. By default, advertised routes are not filtered. You can configure a filtering policy as required. If you configure several filtering policies, they are applied in the following sequence: 1. filter-policy import 2. peer filter-policy import 3. peer as-path-acl import 4. peer ip-prefix import 5. peer route-policy import A filter policy can be applied only after the previous one is passed. Routing information can be received only after passing all the configured filter policies.
6. Specify the upper limit of prefixes that can be imported from a peer or a peer group.	peer { ipv6-group-name \| ipv6-address } route-limit limit [ percentage ]	Optional. The number is unlimited by default.

NOTE:

A peer can have an inbound route filtering policy that is different from the policy of the peer group that it belongs to. That is, peer group members can have different inbound route filtering policies.

Configuring IPv6 MBGP route dampening

To configure IPv6 MBGP route dampening parameters:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Configure IPv6 MBGP route dampening parameters.	dampening [ half-life-reachable half-life-unreachable reuse suppress ceiling \| route-policy route-policy-name ]*	Optional Not configured by default

Configuring IPv6 MBGP route attributes

This section describes how to use IPv6 MBGP route attributes to affect IPv6 MBGP route selection. IPv6 MBGP route attributes involve:

· IPv6 MBGP protocol preference

· Default LOCAL_PREF attribute

· MED attribute

· NEXT_HOP attribute

· AS_PATH attribute

Configuration prerequisites

Before you configure IPv6 MBGP route attributes, complete the following tasks:

· Enable IPv6.

· Configure the IPv6 MBGP basic functions.

Configuring IPv6 MBGP route preferences

To configure IPv6 MBGP route preferences:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Configure preferences for external, internal, and local IPv6 MBGP routes.	preference { external-preference internal-preference local-preference \| route-policy route-policy-name }	Optional. The default preference values of external, internal, and local routes are 255, 255, and 130, respectively.

Configuring the default local preference

To configure the default local preference:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Set the default local preference.	default local-preference value	Optional. By default, the default local preference is 100.

Configuring the MED attribute

To configure the MED attribute:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Configure a default MED value.	default med med-value	Optional. By default, the default med-value is 0.
5. Enable the comparison of the MED for routes from different ASs.	compare-different-as-med	Optional. Not enabled by default.
6. Enable the comparison of the MED for routes from each AS.	bestroute compare-med	Optional. Disabled by default.
7. Enable the comparison of the MED for routes from confederation peers.	bestroute med-confederation	Optional. Disabled 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 an IPv6 multicast IBGP peer or a peer group. If load balancing is configured, the router specifies itself as the next hop of routes sent to the IPv6 multicast IBGP peer or the 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 IPv6 multicast EBGP peers in a broadcast network—the router does not specify itself as the next hop of routes sent to the EBGP peers by default.

To specify the router as the next hop of routes sent to a peer or a peer group:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Configure the router as the next hop of routes sent to the peer or the peer group.	peer { ipv6-group-name \| ipv6-address } next-hop-local	Optional. By default, IPv6 MBGP specifies the local router as the next hop for routes sent to an EBGP peer or a peer group, but not for routes sent to an IBGP peer or a peer group.

Configuring the as_path attribute

To configure the as_path attribute:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Allow the local AS number to appear in the as-path of routes from a peer or a peer group and specify the number of times that the local AS number can appear in the as-path of routes from the peer or the peer group.	peer { ipv6-group-name \| ipv6-address } allow-as-loop [ number ]	Optional. Not allowed by default.
5. Disable IPv6 MBGP from considering the as_path during best route selection.	bestroute as-path-neglect	Optional. Enabled by default.
6. Configure updates to a peer or a peer group to carry only the public AS number.	peer { ipv6-group-name \| ipv6-address } public-as-only	Optional. By default, outbound IPv6 MBGP updates can carry private AS numbers.

Tuning and optimizing IPv6 MBGP networks

Configuration prerequisites

Before you tune and optimize an OSPF network, complete the following tasks:

· Enable IPv6.

· Configure the IPv6 MBGP basic functions.

Configuring IPv6 MBGP soft reset

After you modify a route selection policy, you must reset IPv6 MBGP connections to make the new one take effect.

The current IPv6 MBGP implementation supports the route refresh feature that enables dynamic route refresh without terminating IPv6 MBGP connections.

If a peer that does not support route refresh exists in the network, you must configure the peer keep-all-routes command to save all routes from the peer. When the routing policy is changed, the system will update the IPv6 MBGP routing table and apply the new policy.

Performing soft reset through route refresh

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

To configure IPv6 MBGP soft reset through route refresh:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 address family view.	ipv6-family	N/A
4. Enable IPv6 BGP route refresh for a peer or a peer group.	peer { ipv6-group-name \| ipv6-address } capability-advertise route-refresh	Optional Enabled by default

Performing soft-reset manually

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 ipv6 multicast command to soft-reset IPv6 MBGP connections to refresh the IPv6 MBGP routing table and apply the new policy without terminating IPv6 MBGP connections.

To perform soft reset manually:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 address family view.	ipv6-family	N/A
4. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
5. Keep all routes from a peer or a peer group regardless of whether they pass the inbound filtering policy.	peer { ipv6-group-name \| ipv6-address } keep-all-routes	Not kept by default
6. Perform soft reset manually.	refresh bgp ipv6 multicast { all \| ipv6-address \| group ipv6-group-name \| external \| internal } { export \| import }	Optional

Enabling the IPv6 MBGP ORF capability

The BGP Outbound Route Filter (ORF) feature enables a BGP speaker to send a set of ORFs to its BGP peer through route-refresh messages. The peer then applies the ORFs, in addition to its local routing policies (if any), to filter updates to the BGP speaker, thus reducing the number of exchanged update messages and saving network resources.

After you enable the ORF capability, the local BGP router negotiates the ORF capability with the BGP peer through open messages. That is, the router determines whether to carry ORF information in messages, and if yes, whether to carry non-standard ORF information in the packets. After completing the negotiation process and establishing the neighboring relationship, the BGP router and its BGP peer can exchange ORF information through specific route-refresh messages.

For the parameters configured on both sides for ORF capability negotiation, see Table 1.

To enable the IPv6 MBGP ORF capability:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 address family view.	ipv6-family	N/A
4. Enable BGP route refresh for a peer or a peer group.	peer { group-name \| ipv6-address } capability-advertise route-refresh	Optional. Enabled by default. If this feature is not enabled, you must configure this command.
5. Enable the non-standard ORF capability for a BGP peer or a peer group.	peer { group-name \| ipv6-address } capability-advertise orf non-standard	Optional. By default, standard BGP ORF capability defined in RFC 5291 and RFC 5292 is supported. If this feature is not enabled, you must configure this command.
6. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
7. Enable the ORF IP prefix negotiation capability for a BGP peer or a peer group	peer { group-name \| ipv6-address } capability-advertise orf ip-prefix { both \| receive \| send }	Not enabled by default.

Table 1 Description of the send, receive, and both parameters and the negotiation result

Local parameter	Peer parameter	Negotiation result
send	· receive · both	The ORF sending capability is enabled locally and the ORF receiving capability is enabled on the peer.
receive	· send · both	The ORF receiving capability is enabled locally and the ORF sending capability is enabled on the peer.
both	both	Both the ORF sending and receiving capabilities are enabled locally and on the peer, respectively.

Configuring the maximum number of equal-cost routes for load-balancing

To configure the maximum number of equal-cost routes for load-balancing:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Configure the maximum number of equal-cost routes for load balancing.	balance number	By default, load balancing is disabled.

Configuring a large scale IPv6 MBGP network

Configuration prerequisites

Before you configure the following tasks, you must configure IPv6 MBGP basic functions.

Configuring an IPv6 MBGP peer group

For easy management and configuration, you can organize some IPv6 MBGP peers that have the same route update policy into a peer group. A policy configured for a peer group applies to all the members in the group.

To configure an IPv6 MBGP peer group:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 address family view.	ipv6-family	N/A
4. Create an IPv6 BGP peer group.	group ipv6-group-name [ external \| internal ]	N/A
5. Add a peer to the peer group.	peer ipv6-address group ipv6-group-name [ as-number as-number ]	By default, no peer is added.
6. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
7. Enable the configured IPv6 unicast BGP peer group to create the IPv6 MBGP peer group.	peer ipv6-group-name enable	N/A
8. Add the IPv6 MBGP peer into the peer group.	peer ipv6-address group ipv6-group-name	By default, no peer is added.

CAUTION:

· To create an IPv6 MBGP peer group, you must enable an existing IPv6 unicast peer group in IPv6 MBGP address family view.

· Before you add an IPv6 MBGP peer to the IPv6 MBGP peer group, you must add the corresponding IPv6 BGP unicast peer to the corresponding IPv6 BGP unicast peer group.

Configuring IPv6 MBGP community

A peer group enables a group of peers to share the same policy, and a community enables a group of IPv6 MBGP routers in multiple ASs to share the same policy. The community attribute is propagated among IPv6 MBGP peers and not restricted to AS boundaries.

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

To advertise the community attribute to an IPv6 MBGP peer or a peer group:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Advertise the community attribute to an IPv6 MBGP peer or a peer group.	peer { ipv6-group-name \| ipv6-address } advertise-community	By default, no community attribute is advertised to any peer group/peer.
5. Advertise the extended community attribute to an IPv6 MBGP peer or a peer group.	peer { ipv6-group-name \| ipv6-address } advertise-ext-community	By default, no extended community attribute is advertised to any peer or peer group.
6. Apply a routing policy to routes sent to an IPv6 MBGP peer or a peer group.	peer { ipv6-group-name \| ipv6-address } route-policy route-policy-name export	Not configured by default.

NOTE:

· You must configure a routing policy to define the community attribute, and apply the policy to outgoing routes.

· For more information about routing policy configuration, see Layer 3—IP Routing Configuration Guide.

Configuring an IPv6 MBGP route reflector

To guarantee connectivity between IPv6 multicast IBGP peers, you must make them fully meshed. However, this becomes unpractical when too many IPv6 multicast IBGP peers exist. Using route reflectors can solve the problem.

To configure an IPv6 BGP route reflector:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter BGP view.	bgp as-number	N/A
3. Enter IPv6 MBGP address family view.	ipv6-family multicast	N/A
4. Configure the router as a route reflector and specify an IPv6 MBGP peer or a peer group as its client.	peer { ipv6-group-name \| ipv6-address } reflect-client	Not configured by default.
5. Enable route reflection between clients.	reflect between-clients	Optional. Enabled by default.
6. 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.

NOTE:

· The clients of a route reflector should not be fully meshed, and the route reflector reflects the routes of a client to the other clients. If the clients are fully meshed, you must disable route reflection between clients to reduce routing costs.

· If a cluster has multiple route reflectors, you must specify the same cluster ID for these route reflectors to avoid routing loops.

Displaying and maintaining IPv6 MBGP

Displaying IPv6 MBGP

Task	Command	Remarks
Display IPv6 MBGP peer group information.	display bgp ipv6 multicast group [ ipv6-group-name ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 MBGP routing information injected with the network command.	display bgp ipv6 multicast network [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display the IPv6 MBGP AS path information of routes.	display bgp ipv6 multicast paths [ as-regular-expression \| \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 MBGP peer information or peer group information.	display bgp ipv6 multicast peer [ [ ipv6-address ] verbose ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display the prefix entries in the ORF information of the specified BGP peer.	display bgp ipv6 multicast peer ipv6-address received ipv6-prefix [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 MBGP routing table information.	display bgp ipv6 multicast routing-table [ ipv6-address prefix-length ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 MBGP routing information that matches an AS path ACL.	display bgp ipv6 multicast routing-table as-path-acl as-path-acl-number [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 MBGP routing information with the specified community attribute.	display bgp ipv6 multicast routing-table community [ aa:nn<1-13> ] [ no-advertise \| no-export \| no-export-subconfed ]* [ whole-match ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display routing information matching an IPv6 MBGP community list.	display bgp ipv6 multicast routing-table community-list { { basic-community-list-number \| comm-list-name } [ whole-match ] \| adv-community-list-number }&<1-16> [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 MBGP dampened routing information.	display bgp ipv6 multicast routing-table dampened [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 MBGP dampening parameter information.	display bgp ipv6 multicast routing-table dampening parameter [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 MBGP routing information originated from different ASs.	display bgp ipv6 multicast routing-table different-origin-as [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 MBGP routing flap statistics.	display bgp ipv6 multicast routing-table flap-info [ regular-expression as-regular-expression \| [ as-path-acl as-path-acl-number \| ipv6-address prefix-length [ longer-match ] ] [ \| { begin \| exclude \| include } regular-expression ] ]	Available in any view
Display the IPv6 MBGP routes received from or advertised to the IPv6 MBGP peer or peer group.	display bgp ipv6 multicast routing-table peer ipv6-address { advertised-routes \| received-routes } [ network-address prefix-length \| statistic ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display IPv6 multicast routing information matching an AS regular expression.	display bgp ipv6 multicast routing-table regular-expression as-regular-expression	Available in any view
Display IPv6 MBGP routing statistics.	display bgp ipv6 multicast routing-table statistic [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display the IPv6 MBGP routing table information.	display ipv6 multicast routing-table [ verbose ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view
Display the multicast routing information of the specified destination address.	display ipv6 multicast routing-table ipv6-address prefix-length [ longer-match ] [ verbose ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view

Resetting IPv6 MBGP connections

When you change an IPv6 MBGP routing policy, you can make the new configuration effective by resetting the IPv6 MBGP connections.

Task	Command	Remarks
Reset the specified IPv6 MBGP connections.	reset bgp ipv6 multicast { as-number \| ipv6-address \| all \| group ipv6-group-name \| external \| internal }	Available in user view

Clearing IPv6 MBGP information

Task	Command	Remarks
Clear dampened IPv6 MBGP routing information and release suppressed routes.	reset bgp ipv6 multicast dampening [ ipv6-address prefix-length ]	Available in user view
Clear IPv6 MBGP route flap statistics.	reset bgp ipv6 multicast flap-info [ ipv6-address/prefix-length \| regexp as-path-regexp \| as-path-acl as-path-acl-number ]	Available in user view

IPv6 MBGP configuration example

Network requirements

As shown in Figure 1, IPv6 PIM-SM 1 is in AS 100 and IPv6 PIM-SM 2 is in AS 200. OSPFv3 is the IGP in the two ASs, and IPv6 MBGP runs between the two ASs to exchange IPv6 multicast route information. The multicast source belongs to IPv6 PIM-SM 1, and the receiver belongs to IPv6 PIM-SM 2. The POS 5/1/1 of Router A and Router B must be configured as the C-BSR and C-RP of the IPv6 PIM-SM domains respectively.

Figure 1 Network diagram

Device	Interface	IP address	Device	Interface	IP address
Source	N/A	1002::100/64	Router C	GE3/1/1	3002::1/64
Router A	GE3/1/1	1002::1/64		S4/1/9/1:1	3001::1/64
	POS5/1/1	1001::1/64		S4/1/9/1:2	2001::2/64
Router B	POS5/1/1	1001::2/64	Router D	S4/1/9/1:1	2002::2/64
	S4/1/9/1:1	2001::1/64		S4/1/9/1:2	3001::2/64
	S4/1/9/1:2	2002::1/64

Configuration procedure

1. Configure IPv6 addresses for router interfaces as shown in Figure 1 . (Details not shown)

2. Configure OSPFv3. (Details not shown)

3. Enable IPv6 multicast routing, IPv6 PIM-SM and MLD, and configure an IPv6 PIM-SM domain border:

# Enable IPv6 multicast routing on Router A, and enable PIM-SM on each interface.

<RouterA> system-view

[RouterA] multicast ipv6 routing-enable

[RouterA] interface GigabitEthernet 3/1/1

[RouterA-GigabitEthernet3/1/1] pim ipv6 sm

[RouterA-GigabitEthernet3/1/1] quit

[RouterA] interface POS 5/1/1

[RouterA-Pos5/1/1] pim ipv6 sm

[RouterA-Pos5/1/1] quit

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

# Enable IPv6 multicast routing on Router C, enable IPv6 PIM-SM on each interface, and enable MLD on the host-side interface GigabitEthernet 3/1/1.

<RouterC> system-view

[RouterC] multicast ipv6 routing-enable

[RouterC] interface serial 4/1/9/1:1

[RouterC-Serial4/1/9/1:1] pim ipv6 sm

[RouterC-Serial4/1/9/1:1] quit

[RouterC] interface serial 4/1/9/1:2

[RouterC-Serial4/1/9/1:2] pim ipv6 sm

[RouterC-Serial4/1/9/1:2] quit

[RouterC] interface GigabitEthernet 3/1/1

[RouterC-GigabitEthernet3/1/1] pim ipv6 sm

[RouterC-GigabitEthernet3/1/1] mld enable

[RouterC-GigabitEthernet3/1/1] quit

# Configure an IPv6 PIM domain border on Router A.

[RouterA] interface POS 5/1/1

[RouterA-Pos5/1/1] pim ipv6 bsr-boundary

[RouterA-Pos5/1/1] quit

# Configure an IPv6 PIM domain border on Router B.

[RouterB] interface POS 5/1/1

[RouterB-Pos5/1/1] pim ipv6 bsr-boundary

[RouterB-Pos5/1/1] quit

4. Configure the position of C-BSR and C-RP:

# Configure the position of C-BSR and C-RP on Router A.

[RouterA] pim ipv6

[RouterA-pim6] c-bsr 1001::1

[RouterA-pim6] c-rp 1001::1

[RouterA-pim6] quit

# Configure the position of C-BSR and C-RP on Router B.

[RouterB] pim ipv6

[RouterB-pim6] c-bsr 1001::2

[RouterB-pim6] c-rp 1001::2

[RouterB-pim6] quit

5. Configure BGP, and specify the IPv6 MBGP peer:

# On Router A, configure the IPv6 MBGP peer.

[RouterA] ipv6

[RouterA] bgp 100

[RouterA-bgp] router-id 1.1.1.1

[RouterA-bgp] ipv6-family

[RouterA-bgp-af-ipv6] peer 1001::2 as-number 200

[RouterA-bgp-af-ipv6] import-route direct

[RouterA-bgp-af-ipv6] quit

[RouterA-bgp] ipv6-family multicast

[RouterA-bgp-af-ipv6-mul] peer 1001::2 enable

[RouterA-bgp-af-ipv6-mul] import-route direct

[RouterA-bgp-af-ipv6-mul] quit

[RouterA-bgp] quit

# On Router B, configure the IPv6 MBGP peers and redistribute OSPF routes.

[RouterB] ipv6

[RouterB] bgp 200

[RouterB-bgp] router-id 2.2.2.2

[RouterB-bgp] ipv6-family

[RouterB-bgp-af-ipv6] peer 1001::1 as-number 100

[RouterB-bgp-af-ipv6] import-route ospfv3 1

[RouterB-bgp-af-ipv6] quit

[RouterB-bgp] ipv6-family multicast

[RouterB-bgp-af-ipv6-mul] peer 1001::1 enable

[RouterB-bgp-af-ipv6-mul] import-route ospfv3 1

[RouterB-bgp-af-ipv6-mul] quit

[RouterB-bgp] quit

6. Verify the configuration:

You can use the display bgp ipv6 multicast peer command to display IPv6 MBGP peers on each router. For example, display IPv6 MBGP peers on Router B.

[RouterB] display bgp ipv6 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 AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State

1001::1 100 56 56 0 0 00:40:54 Established

07-IP Multicast Configuration Guide

IPv6 MBGP configuration task list

Configuring outbound IPv6 MBGP route filtering

Configuring inbound IPv6 MBGP route filtering

Configuring the as_path attribute

Performing soft reset through route refresh

Performing soft-reset manually

Enabling the IPv6 MBGP ORF capability

Configuring the maximum number of equal-cost routes for load-balancing

Configuration prerequisites

Network requirements

Configuration procedure

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

Company Information

News & Events

Contact Us