Login
- Table of Contents
-
- 04-IP Multicast Volume
- 00-IP Multicast Volume Organization
- 01-Mulitcast Overview
- 02-Multicast Routing and Forwarding Configuration
- 03-IGMP Configuration
- 04-PIM Configuration
- 05-MSDP Configuration
- 06-MBGP Configuration
- 07-Multicast VPN Configuration
- 08-IGMP Snooping Configuration
- 09-Multicast VLAN Configuration
- 10-IPv6 Multicast Routing and Forwarding Configuration
- 11-MLD Configuration
- 12-IPv6 PIM Configuration
- 13-IPv6 MBGP Configuration
- 14-MLD Snooping Configuration
- 15-IPv6 Multicast VLAN Configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 13-IPv6 MBGP Configuration | 193.64 KB |
IPv6 MBGP Configuration Task List
Configuring IPv6 MBGP Basic Functions
Configuring a Preferred Value for Routes from a Peer/Peer Group
Controlling Route Distribution and Reception
Injecting a Local IPv6 MBGP Route
Configuring IPv6 MBGP Route Redistribution
Advertising a Default Route to a Peer or Peer Group
Configure Outbound IPv6 MBGP Route Filtering
Configuring Inbound IPv6 MBGP Route Filtering
Configuring IPv6 MBGP Route Dampening
Configuring IPv6 MBGP Route Attributes
Configuring IPv6 MBGP Route Preferences
Configuring the Default Local Preference
Configuring the NEXT_HOP Attribute
Configuring the AS_PATH Attribute
Tuning and Optimizing IPv6 MBGP Networks
Configuring IPv6 MBGP Soft Reset
Configuring the Maximum Number of Equal-Cost Routes for Load-Balancing
Configuring a Large Scale IPv6 MBGP Network
Configuring an IPv6 MBGP Peer Group
Configuring IPv6 MBGP Community
Configuring an IPv6 MBGP Route Reflector
Displaying and Maintaining IPv6 MBGP
Resetting IPv6 MBGP Connections
Clearing IPv6 MBGP Information
IPv6 MBGP Configuration Example
When configuring IPv6 MBGP, go to these sections for information you are interested in:
l IPv6 MBGP Configuration Task List
l Displaying and Maintaining IPv6 MBGP
l IPv6 MBGP Configuration Example
This chapter describes only configuration for IPv6 MBGP. For IPv6 BGP related information, refer to IPv6 BGP Configuration in the IP Routing Volume.
IPv6 MBGP Overview
BGP-4 is capable of carrying routing information for IPv4 only. IETF defined multi-protocol BGP extensions to carry routing information for multiple network layer protocols.
For an IPv6 network, the IPv6 multicast topology need be different from the IPv6 unicast topology. To meet the requirement, the multi-protocol BGP extensions enable IPv6 BGP to carry the IPv6 unicast Network Layer Reachability Information (NLRI) and IPv6 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 IPv6 unicast routing table and through the IPv6 multicast routing table will have different results, ensuring the normal unicast and multicast operation across ASs.
Multi-protocol BGP is defined in RFC 2858 (Multiprotocol Extensions for BGP-4).
Multi-protocol BGP for IPv6 multicast is referred to as IPv6 multicast BGP (IPv6 MBGP).
This document covers configuration tasks related to multi-protocol BGP for IPv6 multicast only. For BGP related information, refer to BGP Configuration in the IP Routing Volume.
For information about RPF, refer to Multicast Routing and Forwarding in the IP Multicast Volume.
IPv6 MBGP Configuration Task List
Complete the following tasks to configure IPv6 MBGP:
|
Task |
Remarks |
|
|
Required |
||
|
Configuring a Preferred Value for Routes from a Peer/Peer Group |
Optional |
|
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Optional |
||
|
Configuring the Maximum Number of Equal-Cost Routes for Load-Balancing |
Optional |
|
|
Optional |
||
|
Optional |
||
|
Optional |
||
Configuring IPv6 MBGP Basic Functions
Configuration Prerequisites
IPv6 MBGP is an application of multi-protocol BGP. Therefore, before configuring IPv6 MBGP, you need to
l Enable IPv6
l Configure network layer addresses for interfaces
l Complete BGP basic configuration
Configuring an IPv6 MBGP Peer
Follow these steps to configure an IPv6 MBGP peer
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enable BGP and enter BGP view |
bgp as-number |
Required Not enabled by default |
|
Enter IPv6 address family view |
ipv6-family |
— |
|
Specify a IPv6 BGP peer and its AS number |
peer ipv6-address as-number as-number |
Required Not configured by default |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Enable the IPv6 MBGP peer |
Required Not enabled by default. |
Configuring a Preferred Value for Routes from a Peer/Peer Group
Follow these steps to configure a preferred value for routes from a peer/peer group:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Specify a preferred value for routes received from the IPv6 MBGP peer/peer group |
peer { ipv6-group-name | ipv6-address } preferred-value value |
Optional The preferred value defaults to 0. |
If you both reference a route policy and use the command peer { ipv6-group-name | ipv6-address } preferred-value value to set a preferred value for routes from a peer/peer group, the route policy sets a non-zero preferred value for routes matching it. Other routes not matching the route policy uses the value set with the command. If the preferred value in the route policy is zero, the routes matching it will also use the value set with the command. For information about using a route policy to set a preferred value, refer to the peer { ipv6-group-name | ipv6-address } route-policy route-policy-name { import | export } command and the apply preferred-value preferred-value command in Route Policy Commands in the IP Routing Volume.
Controlling Route Distribution and Reception
Configuration Prerequisites
Before configuring this task, you need to:
l Enable IPv6.
l Configure the IPv6 MBGP basic functions.
Injecting a Local IPv6 MBGP Route
Follow these steps to inject a local IPv6 MBGP route:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Inject a network to the IPv6 MBGP routing table |
network ipv6-address prefix-length [ route-policy route-policy-name | short-cut ] |
Required Not injected by default |
Configuring IPv6 MBGP Route Redistribution
Follow these steps to configure IPv6 MBGP route redistribution:
|
To do… |
Use the command… |
Description |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter the MBGP multicast address family view |
ipv6-family multicast |
— |
|
Enable default route redistribution into the IPv6 MBGP routing table |
default-route imported |
Optional By default, default route redistribution is not allowed. |
|
Enable route redistribution from another routing protocol |
import-route protocol [ process-id ] [ med med-value | route-policy route-policy-name ] * |
Required Not enabled by default |
If the default-route imported command is not configured, using the import-route command cannot redistribute any IGP default route.
Advertising a Default Route to a Peer or Peer Group
Follow these steps to advertise a default route to a peer or peer group
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
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 ] |
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 IPv6 MBGP peer/peer group, regardless of whether the default route is available in the routing table.
Configure Outbound IPv6 MBGP Route Filtering
Follow these steps to configure outbound IPv6 MBGP route filtering:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Configure the filtering of outgoing routes |
filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } export [ protocol process-id ] |
Use any of the commands. No filtering is configured by default. You can configure filter policies as needed. If you configure multiple filter policies, they will be applied in the following order: l filter-policy export l peer filter-policy export l peer as-path-acl export l peer ipv6-prefix export l 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 filter policies configured. |
|
Specify an IPv6 ACL to filer routes advertised to a peer/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/peer group |
peer { ipv6-group-name | ipv6-address } as-path-acl as-path-acl-number export |
|
|
Specify an IPv6 prefix list to filer routes advertised to a peer/peer group |
peer { ipv6-group-name | ipv6-address } ipv6-prefix ipv6-prefix-name export |
|
|
Apply a route policy to routes advertised to a peer/peer group |
peer { ipv6-group-name | ipv6-address } route-policy route-policy-name export |
l Members of an IPv6 MBGP peer group must have the same outbound route filtering policy as the peer group.
l IPv6 BGP advertises redistributed routes passing the specified policy to the IPv6 MBGP peer.
Configuring Inbound IPv6 MBGP Route Filtering
Follow these steps to configure IPv6 MBGP inbound route filtering:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Configure inbound route filtering |
filter-policy { acl6-number | ipv6-prefix ipv6-prefix-name } import |
Use any of the commands By default, advertised routes are not filtered. You can configure a filtering policy as needed. 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 A filter policy can be applied only after the previous one is passed; routing information can be received only after passing all the filter policies configured. |
|
Apply a route policy to routes from a peer/peer group |
peer { ipv6-group-name | ipv6-address } route-policy route-policy-name import |
|
|
Specify an IPv6 ACL to filter routes from a peer/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/peer group |
peer { ipv6-group-name | ipv6-address } as-path-acl as-path-acl-number import |
|
|
Specify an IPv6 prefix list to filer routes from a peer/peer group |
peer { ipv6-group-name | ipv6-address } ipv6-prefix ipv6-prefix-name import |
|
|
Specify the upper limit of prefixes that can be imported from a peer/peer group |
peer { ipv6-group-name | ipv6-address } route-limit limit [ percentage ] |
Optional The number is unlimited by default. |
A peer can has an inbound route filtering policy different from that of the peer group it belongs to. That is, peer group members can have different inbound route filtering policies.
Configuring IPv6 MBGP Route Dampening
Follow these steps to configure IPv6 MBGP route dampening parameters:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
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:
l IPv6 MBGP protocol preference
l Default LOCAL_PREF attribute
l MED attribute
l NEXT_HOP attribute
l AS_PATH attribute
Configuration Prerequisites
Before the configuration, accomplish the following tasks:
l Enable IPv6
l Configure the IPv6 MBGP basic functions
Configuring IPv6 MBGP Route Preferences
Follow these steps to configure IPv6 MBGP route preferences:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Configure preferences for external, internal, 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
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 IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Set the default local preference |
default local-preference value |
Optional By default, the default local preference is 100. |
Configuring the MED Attribute
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 IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Configure a default MED value |
default med med-value |
Optional By default, the default med-value is 0. |
|
Enable the comparison of the MED for routes from different ASs |
compare-different-as-med |
Optional Not enabled by default |
|
Enable the comparison of the MED for routes from each AS |
bestroute compare-med |
Optional Disabled by default |
|
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/peer group. If load balancing is configured, the router specifies itself as the next hop of routes sent to the IPv6 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 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.
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 IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Configure the router as the next hop of routes sent to the peer/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/peer group, but not for routes sent to an iBGP peer/peer group. |
Configuring the AS_PATH Attribute
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 IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Allow the local AS number to appear in the AS-PATH of routes from a peer/peer group and specify the number of times that the local AS number can appear in the AS-PATH of routes from the peer/peer group |
peer { ipv6-group-name | ipv6-address } allow-as-loop [ number ] |
Optional Not allowed by default |
|
Disable IPv6 MBGP from considering the AS_PATH during best route selection |
bestroute as-path-neglect |
Optional Enabled by default |
|
Configure updates to a peer/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 tuning and optimizing an OSPF network, perform the following tasks:
l Enable IPv6
l Configure the IPv6 MBGP basic functions
Configuring IPv6 MBGP Soft Reset
After modifying a route selection policy, you have to reset IPv6 MBGP connections to make it take effect, causing short time disconnections.
After the route-refresh capability is enabled on all IPv6 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 IPv6 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 IPv6 MBGP routing table and apply the new policy without tearing down IPv6 MBGP connections.
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 receiving the message. Therefore, the local router can perform dynamic route update and apply the new policy without tearing down IPv6 MBGP connections.
Follow these steps to configure IPv6 MBGP soft reset through route-refresh:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 address family view |
ipv6-family |
— |
|
Enable IPv6 BGP route refresh for a peer/peer group |
peer { ipv6-group-name | ipv6-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 ipv6 multicast command to soft-reset IPv6 MBGP connections to refresh the IPv6 MBGP routing table and apply the new policy without tearing down IPv6 MBGP connections.
Follow these steps to perform a manual soft-reset
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 address family view |
ipv6-family |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Keep all routes from a peer/peer group regardless of whether they pass the inbound filtering policy |
peer { ipv6-group-name | ipv6-address } keep-all-routes |
Required Not kept by default |
|
Soft-reset IPv6 MBGP connections manually |
refresh bgp ipv6 multicast { all | ipv6-address | group ipv6-group-name | external | internal } { export | import } |
Optional |
Configuring the Maximum Number of Equal-Cost Routes for Load-Balancing
Follow these steps to configure the maximum number of equal-cost routes for load-balancing:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Configure the maximum number of equal-cost routes for load balancing |
balance number |
Required By default, load balancing is disabled. |
Configuring a Large Scale IPv6 MBGP Network
Configuration Prerequisites
Before configuring the following tasks, you need to configure IPv6 MBGP basic functions.
Configuring an IPv6 MBGP Peer Group
For easy management and configuration, you can organize some IPv6 MBGP peers having the same route update policy into a group, known as a peer group. A policy configured for a peer group applies to all the members in the group.
Follow these steps to configure an IPv6 MBGP peer group:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 address family view |
ipv6-family |
— |
|
Create an IPv6 BGP peer group |
group ipv6-group-name [ external | internal ] |
Required |
|
Add a peer to the peer group |
peer ipv6-address group ipv6-group-name [ as-number as-number ] |
Required By default, no peer is added. |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Enable the configured IPv6 unicast BGP peer group to create the IPv6 MBGP peer group |
peer ipv6-group-name enable |
Required |
|
Add the IPv6 MBGP peer into the peer group |
peer ipv6-address group ipv6-group-name |
Required By default, no peer is added. |
l To create an IPv6 MBGP peer group, you need to enable an existing IPv6 unicast peer group in IPv6 MBGP address family view.
l Before adding an IPv6 MBGP peer to the IPv6 MBGP peer group, you need to add the corresponding IPv6 BGP unicast peer to the corresponding IPv6 BGP unicast peer group.
Configuring IPv6 MBGP Community
A peer group allows a group of peers to share the same policy, while a community allows 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 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 advertise the community attribute to an IPv6 MBGP peer/peer group:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Advertise the community attribute to an IPv6 MBGP peer/peer group |
peer { ipv6-group-name | ipv6-address } advertise-community |
Required By default, no community attribute is advertised to any peer group/peer. |
|
Advertise the extended community attribute to an IPv6 MBGP peer/peer group |
peer { ipv6-group-name | ipv6-address } advertise-ext-community |
Required By default, no extended community attribute is advertised to any peer/peer group. |
|
Apply a route policy to routes sent to an IPv6 MBGP peer/peer group |
peer { ipv6-group-name | ipv6-address } route-policy route-policy-name export |
Required Not configured by default |
l You need to configure a route policy to define the community attribute, and apply the policy to outgoing routes.
l For route policy configuration, refer to Route Policy Configuration in the IP Routing Volume.
Configuring an IPv6 MBGP Route Reflector
To guarantee connectivity between IPv6 multicast iBGP peers, you need to make them fully meshed, but it becomes unpractical when there are too many IPv6 multicast iBGP peers. Using route reflectors can solve the problem.
Follow these steps to configure an IPv6 BGP route reflector:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Enter BGP view |
bgp as-number |
— |
|
Enter IPv6 MBGP address family view |
ipv6-family multicast |
— |
|
Configure the router as a route reflector and specify an IPv6 MBGP peer/peer group as its client |
peer { ipv6-group-name | ipv6-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 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 need to disable route reflection between clients to reduce routing costs.
l If a cluster has multiple route reflectors, you need to specify the same cluster ID for these route reflectors to avoid routing loops.
Displaying and Maintaining IPv6 MBGP
Displaying IPv6 MBGP
|
To do… |
Use the command… |
Remarks |
|
Display the IPv6 MBGP peer group information |
display bgp ipv6 multicast group [ ipv6-group-name ] |
Available in any view |
|
Display IPv6 MBGP routing information injected with the network command |
display bgp ipv6 multicast network |
Available in any view |
|
Display the IPv6 MBGP AS path information of routes |
display bgp ipv6 multicast paths [ as-regular-expression ] |
Available in any view |
|
Display IPv6 MBGP peer/peer group information |
display bgp ipv6 multicast peer [ [ ipv6-address ] verbose ] |
Available in any view |
|
Display IPv6 MBGP routing table information |
display bgp ipv6 multicast routing-table [ ipv6-address prefix-length ] |
Available in any view |
|
Display IPv6 MBGP routing information matching a AS path ACL |
display bgp ipv6 multicast routing-table as-path-acl as-path-acl-number |
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 ] |
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 [ whole-match ] | adv-community-list-number }&<1-16> |
Available in any view |
|
Display IPv6 MBGP dampened routing information |
Available in any view |
|
|
Display IPv6 MBGP dampening parameter information |
display bgp ipv6 multicast routing-table dampening parameter |
Available in any view |
|
Display IPv6 MBGP routing information originated from different ASs |
display bgp ipv6 multicast routing-table different-origin-as |
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 | network-address [ prefix-length [ longer-match ] ] ] |
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 ] |
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 |
Available in any view |
|
Display the IPv6 MBGP routing table information |
display ipv6 multicast routing-table [ verbose ] |
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 ] |
Available in any view |
Resetting IPv6 MBGP Connections
When an IPv6 MBGP route policy is changed, you can make the new configuration effective by resetting the IPv6 MBGP connections.
|
To do… |
Use the command… |
Remarks |
|
Reset 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
|
To do… |
Use the 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 the following figure:
l 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.
l The IPv6 multicast source belongs to IPv6 PIM-SM 1 and the receiver belongs to IPv6 PIM-SM 2.
l It is required that the respective VLAN-interface 101 of Switch A and Switch B be configured as the C-BSR and C-RP of the respective IPv6 PIM-SM domains.
Network diagram
Figure 1-1 Network diagram for IPv6 MBGP configuration
|
Device |
Interface |
IP address |
Device |
Interface |
IP address |
|
Source |
— |
1002::100/64 |
Switch C |
Vlan-int200 |
3002::1/64 |
|
Switch A |
Vlan-int100 |
1002::1/64 |
|
Vlan-int102 |
2001::2/64 |
|
|
Vlan-int101 |
1001::1/64 |
|
Vlan-int104 |
3001::1/64 |
|
Switch B |
Vlan-int101 |
1001::2/64 |
Switch D |
Vlan-int103 |
2002::2/64 |
|
|
Vlan-int102 |
2001::1/64 |
|
Vlan-int104 |
3001::2/64 |
|
|
Vlan-int103 |
2002::1/64 |
|
|
|
Configuration procedure
1) Configure IPv6 addresses for interfaces as shown in the above figure (omitted).
2) Configure OSPFv3 (omitted).
3) Enable IPv6 multicast routing, IPv6 PIM-SM and MLD, and configure an IPv6 PIM-SM domain border.
# Enable IPv6 multicast routing on Switch A, and enable IPv6 PIM-SM on each interface.
<SwitchA> system-view
[SwitchA] multicast ipv6 routing-enable
[SwitchA] interface vlan-interface 100
[SwitchA-Vlan-interface100] pim ipv6 sm
[SwitchA-Vlan-interface100] quit
[SwitchA] interface vlan-interface 101
[SwitchA-Vlan-interface101] pim ipv6 sm
[SwitchA-Vlan-interface101] quit
The configuration on Switch B and Switch D is similar to the configuration on Switch A.
# Enable IPv6 multicast routing on Switch C, enable IPv6 PIM-SM on each interface, and enable MLD on the host-side interface VLAN-interface 200.
<SwitchC> system-view
[SwitchC] multicast ipv6 routing-enable
[SwitchC] interface vlan-interface 102
[SwitchC-Vlan-interface102] pim ipv6 sm
[SwitchC-Vlan-interface102] quit
[SwitchC] interface vlan-interface 104
[SwitchC-Vlan-interface104] pim ipv6 sm
[SwitchC-Vlan-interface104] quit
[SwitchC] interface vlan-interface 200
[SwitchC-Vlan-interface200] pim ipv6 sm
[SwitchC-Vlan-interface200] mld enable
[SwitchC-Vlan-interface200] quit
# Configure an IPv6 PIM domain border on Switch A.
[SwitchA] interface vlan-interface 101
[SwitchA-Vlan-interface101] pim ipv6 bsr-boundary
[SwitchA-Vlan-interface101] quit
# Configure an IPv6 PIM domain border on Switch B.
[SwitchB] interface vlan-interface 101
[SwitchB-Vlan-interface101] pim ipv6 bsr-boundary
[SwitchB-Vlan-interface101] quit
4) Configure the position of C-BSR and C-RP.
# Configure the position of C-BSR and C-RP on Switch A.
[SwitchA] pim ipv6
[SwitchA-pim6] c-bsr 1001::1
[SwitchA-pim6] c-rp 1001::1
[SwitchA-pim6] quit
# Configure the position of C-BSR and C-RP on Switch B.
[SwitchB] pim ipv6
[SwitchB-pim6] c-bsr 1001::2
[SwitchB-pim6] c-rp 1001::2
[SwitchB-pim6] quit
5) Configure BGP, specify the IPv6 MBGP peer and enable direct route redistribution.
# On Switch A, configure the IPv6 MBGP peer and enable direct route redistribution.
[SwitchA] ipv6
[SwitchA] bgp 100
[SwitchA-bgp] router-id 1.1.1.1
[SwitchA-bgp] ipv6-family
[SwitchA-bgp-af-ipv6] peer 1001::2 as-number 200
[SwitchA-bgp-af-ipv6] import-route direct
[SwitchA-bgp-af-ipv6] quit
[SwitchA-bgp] ipv6-family multicast
[SwitchA-bgp-af-ipv6-mul] peer 1001::2 enable
[SwitchA-bgp-af-ipv6-mul] import-route direct
[SwitchA-bgp-af-ipv6-mul] quit
[SwitchA-bgp] quit
# On Switch B, configure the IPv6 MBGP peers and redistribute OSPF routes.
[SwitchB] ipv6
[SwitchB] bgp 200
[SwitchB-bgp] router-id 2.2.2.2
[SwitchB-bgp] ipv6-family
[SwitchB-bgp-af-ipv6] peer 1001::1 as-number 100
[SwitchB-bgp-af-ipv6] import-route ospfv3 1
[SwitchB-bgp-af-ipv6] quit
[SwitchB-bgp] ipv6-family multicast
[SwitchB-bgp-af-ipv6-mul] peer 1001::1 enable
[SwitchB-bgp-af-ipv6-mul] import-route ospfv3 1
[SwitchB-bgp-af-ipv6-mul] quit
[SwitchB-bgp] quit
6) Verify the configuration
You can use the display bgp ipv6 multicast peer command to display IPv6 MBGP peers on a switch. For example, display IPv6 MBGP peers on Switch B.
[SwitchB] 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 V AS MsgRcvd MsgSent OutQ PrefRcv Up/Down State
1001::1 4 100 56 56 0 0 00:40:54 Established
