Login
- Table of Contents
-
- 07-IP Multicast Command Reference
- 00-Preface
- 01-IGMP snooping commands
- 02-PIM snooping commands
- 03-Multicast VLAN commands
- 04-Multicast routing and forwarding commands
- 05-IGMP commands
- 06-PIM commands
- 07-MSDP commands
- 08-Multicast VPN commands
- 09-MLD snooping commands
- 10-IPv6 PIM snooping commands
- 11-IPv6 multicast VLAN commands
- 12-IPv6 multicast routing and forwarding commands
- 13-MLD commands
- 14-IPv6 PIM commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-Multicast VPN commands | 62.58 KB |
display bgp routing-table ipv4 mdt
display multicast-domain default-group
multicast rpf-proxy-vector compatible
Multicast VPN commands
address-family ipv4
Use address-family ipv4 to create an MD IPv4 address family and enter its view, or enter the view of the existing MD IPv4 address family.
Use undo address-family ipv4 to delete the MD IPv4 address family and configurations in MD IPv4 address family view.
Syntax
address-family ipv4
undo address-family ipv4
Default
No MD IPv4 address family exists.
Views
MD view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
Configurations in MD IPv4 address family view of a VPN instance apply only to IPv4 multicast packets of that instance.
Examples
# In MD view of VPN instance mvpn, create an MD IPv4 address family and enter its view.
<Sysname> system-view
[Sysname] multicast-domain vpn-instance mvpn
[Sysname-md-mvpn] address-family ipv4
[Sysname-md-mvpn-ipv4]
address-family ipv4 mdt
Use address-family ipv4 mdt to create a BGP IPv4 MDT address family and enter its view, or enter the view of the existing BGP IPv4 MDT address family.
Use undo address-family ipv4 mdt to delete the BGP IPv4 MDT address family and all configurations in BGP IPv4 MDT address family view.
Syntax
address-family ipv4 mdt
undo address-family ipv4 mdt
Default
No BGP IPv4 MDT address family exists.
Views
BGP instance view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
Execute this command before you use the peer enable command to enable BGP peers to exchange MDT information. MDT information includes the IP address of a PE device and the default-group to which the PE device belongs. On a public network running PIM-SSM, multicast VPN establishes a default-MDT rooted at the PE device (multicast source) based on the MDT information.
Configurations in BGP IPv4 MDT address family view takes effect only on BGP MDT messages, BGP MDT peers, and BGP MDT peer groups.
Examples
# In BGP instance view of BGP instance default, create a BGP IPv4 MDT address family and enter its view.
<Sysname> system-view
[Sysname] bgp 100
[Sysname-bgp-default] address-family ipv4 mdt
[Sysname-bgp-default-mdt]
# In BGP instance view of BGP instance abc, create a BGP IPv4 MDT address family and enter its view.
<Sysname> system-view
[Sysname] bgp 100 instance abc
[Sysname-bgp-abc] address-family ipv4 mdt
[Sysname-bgp-abc-mdt]
Related commands
peer enable (see Layer 3—IP Routing Configuration Guide)
data-delay
Use data-delay to set the data-delay period (delay period before the default-MDT switches to the data-MDT).
Use undo data-delay to restore the default.
Syntax
data-delay delay
undo data-delay
Default
The data-delay period is 3 seconds.
Views
MD IPv4 address family view
Predefined user roles
network-admin
mdc-admin
Parameters
delay: Specifies a data-delay period in the range of 1 to 60 seconds.
Examples
# In MD IPv4 address family view of VPN instance mvpn, set the data-delay period to 20 seconds.
<Sysname> system-view
[Sysname] multicast-domain vpn-instance mvpn
[Sysname-md-mvpn] address-family ipv4
[Sysname-md-mvpn-ipv4] data-delay 20
data-group
Use data-group to specify a data-group range and optionally configure the criteria for the default-MDT to data-MDT switchover.
Use undo data-group to restore the default.
Syntax
data-group group-address { mask-length | mask } [ acl acl-number] *
undo data-group
Default
No data-group range exists, and the default-MDT to data-MDT switchover never occurs.
Views
MD IPv4 address family view
Predefined user roles
network-admin
mdc-admin
Parameters
group-address: Specifies a multicast group address in the range of 224.0.1.0 to 239.255.255.255.
mask-length: Specifies a mask length for the multicast group address. The value range for this argument is 24 to 32.
mask: Specifies a subnet mask for the multicast group address. The value range for this argument is 255.255.255.x, where x can be only 0, 128, 192, 224, 240, 248, 252, 254, or 255.
acl acl-number: Specifies an advanced ACL by its number in the range of 3000 to 3999. If you specify an ACL, the multicast data permitted by the ACL can trigger the switchover. If you do not specify an ACL, any multicast data can trigger the switchover. For the ACL to take effect, specify the protocol type as IP, and include the source and destination keywords when you create an ACL rule. The source and destination keywords specify a multicast source address range and a multicast group address range, respectively.
Usage guidelines
On a PE, the data-group range for an MD cannot include the default-group or data-groups of any other MD.
The data-group ranges for different MDs on different PE devices cannot overlap with one another if the PIM mode is not PIM-SSM on the public network.
If you execute this command multiple times for an MD, the most recent configuration takes effect.
Examples
# In MD IPv4 address family view of VPN instance mvpn, specify 239.1.2.0 through 239.1.2.255 as the data-group range.
<Sysname> system-view
[Sysname] multicast-domain vpn-instance mvpn
[Sysname-md-mvpn] address-family ipv4
[Sysname-md-mvpn-ipv4] data-group 239.1.2.0 24
default-group
Use default-group to specify a default-group.
Use undo default-group to restore the default.
Syntax
default-group group-address
undo default-group
Default
No default-group exists.
Views
MD IPv4 address family view
Predefined user roles
network-admin
mdc-admin
Parameters
group-address: Specifies a default-group in the range of 224.0.1.0 to 239.255.255.255.
Usage guidelines
You must specify the same default-group on all PE devices that belong to the same MD.
The default-group for an MD must be different from the default-group and the data-group used by any other MD.
Examples
# In MD IPv4 address family view of VPN instance mvpn, specify 239.1.1.1 as the default-group.
<Sysname> system-view
[Sysname] multicast-domain vpn-instance mvpn
[Sysname-md-mvpn] address-family ipv4
[Sysname-md-mvpn-ipv4] default-group 239.1.1.1
[Sysname-md-mvpn-ipv4] quit
display bgp routing-table ipv4 mdt
Use display bgp routing-table ipv4 mdt to display BGP MDT routing information.
Syntax
display bgp [ instance instance-name ] routing-table ipv4 mdt [ route-distinguisher route-distinguisher ] [ ip-address [ advertise-info ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
instance instance-name: Specifies a BGP instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a BGP instance, this command displays BGP MDT routing information for the BGP instance default.
route-distinguisher route-distinguisher: Specifies an RD, a string of 3 to 21 characters. If you do not specify an RD, this command displays BGP MDT routing information for all RDs. An RD can be in one of the following formats:
· 16-bit AS number:32-bit user-defined number. For example, 101:3.
· 32-bit IP address:16-bit user-defined number. For example, 192.168.122.15:1.
· 32-bit AS number:16-bit user-defined number, where the AS number must be equal to or greater than 65536. For example, 65536:1.
ip-address: Specifies a multicast source by its IP address. The ip-address argument represents the IP address of the PE device in the default-MDT. If you do not specify a multicast source, this command displays brief information about BGP MDT routes for all multicast sources.
advertise-info: Displays advertisement information. If you do not specify this keyword, no advertisement information is displayed.
Examples
# Display brief information about BGP MDT routes for all multicast sources.
<Sysname> display bgp routing-table ipv4 mdt
BGP local router ID is 1.1.1.1
Status codes: * - valid, > - best, d - dampened, h - history,
s - suppressed, S - stale, i - internal, e - external
Origin: i - IGP, e - EGP, ? - incomplete
Route distinguisher: 100:1
Total number of routes: 2
Network NextHop MED LocPrf PrefVal Path/Ogn
* > 1.1.1.1/32 0.0.0.0 32768 ?
* >i 2.2.2.2/32 2.2.2.2 100 0 ?
# Display detailed information about BGP MDT routes for multicast source 1.1.1.1.
<Sysname> display bgp routing-table ipv4 mdt 1.1.1.1
BGP local router ID: 1.1.1.1
Local AS number: 100
Route distinguisher: 100:1
Total number of routes: 1
Paths: 1 available, 1 best
BGP MDT information of source 1.1.1.1:
Default-group : 224.1.1.1
Original nexthop: 0.0.0.0
AS-path : (null)
Origin : incomplete
Attribute value : pref-val 32768
State : valid, local, best
IP precedence : N/A
QoS local ID : N/A
Traffic index : N/A
# Display advertisement information about BGP MDT routes for multicast source 1.1.1.1.
<Sysname> display bgp routing-table ipv4 mdt 1.1.1.1 advertise-info
BGP local router ID: 1.1.1.1
Local AS number: 100
Route distinguisher: 100:1
Total number of routes: 1
Paths: 1 best
BGP MDT information of source 1.1.1.1:
Default-group: 224.1.1.1
Advertised to peers (1 in total):
6.6.6.6
Table 1 Command output
|
Field |
Description |
|
BGP local router ID |
ID of the local router. |
|
Status codes |
Codes of route status: · * – valid—Valid route. · > – best—Best route. · d – damped—Dampened route. · h – history—History route. · s – suppressed—Suppressed route. · S – Stale—Stale route. · i – internal—Internal route. · e – external—External route. |
|
Origin |
Origin of the route information: · i – IGP—Originated in the AS. The origins of the routes advertised by the network command are IGP. · e – EGP—Learned through EGP. · ? – incomplete—Learned by some other means. The origins of routes redistributed by IGP are incomplete. |
|
Total number of routes |
Total number of BGP MDT routes. |
|
Network |
Source IP address of the default-MDT. |
|
NextHop |
IP address of the next hop. |
|
MED |
Attribute value of Multi-Exit-Discrimination (MED). |
|
LocPrf |
Local preference value. |
|
PrefVal |
Preferred value of a route. |
|
Path/Ogn |
AS PATH attribute and ORIGIN attribute: · AS_PATH—Records the ASs the packet has passed to avoid routing loops. · ORIGIN—Identifies the origin of the BGP MDT routes. |
|
Paths |
Number of the BGP MDT routes: · available—Number of valid BGP MDT routes. · best—Number of the best BGP MDT routes. |
|
BGP MDT information of source 1.1.1.1 |
BGP MDT routing information for the multicast source 1.1.1.1. |
|
Default-group |
Default-group address to which the route belongs. |
|
Advertised to peers (1 in total) |
Peers to which the route has been advertised and total number of peers. |
|
From |
IP address of the BGP peer that advertises the BGP MDT route. |
|
Original nexthop |
IP address of the original next hop. If the BGP MDT route is learned from the BGP update message, this field displays the IP address of the next hop that receives the message. |
|
AS-path |
AS PATH attribute of the path, recording the ASs that the BGP MDT route has passed to avoid routing loops. |
|
Attribute value |
Attributes of the BGP MDT routes: · MED—MED value related to destination network. · Localpref—Local preferred value. · pref-val—Preferred value of the route. · pre—Preferred value of the protocol. |
|
State |
Current states: · valid—Valid routes. · internal—Internal routes. · external—External routes. · local—Local routes. · synchronize—Synchronized routes. · best—Best routes. |
|
IP precedence |
IP precedence of the route, which is set by the QPPB feature. This field displays N/A if the IP precedence of the route is not set. |
|
QoS local ID |
QoS local ID of the route, which is set by the QPPB feature. This field displays N/A if the QoS local ID of the route is not set. |
|
Traffic index |
Traffic index of the route, which is set by the QPPB feature. This field displays N/A if the Traffic index of the route is not set. |
display multicast-domain default-group
Use display multicast-domain default-group to display information about default-groups for IPv4 multicast transmission.
Syntax
display multicast-domain [ vpn-instance vpn-instance-name ] default-group { local | remote }
Views
Any view
Predefined user roles
network-admin
network-operator
mdc-admin
mdc-operator
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify a VPN instance, this command displays information about default-groups of all VPN instances for IPv4 multicast transmission.
local: Specifies local default-groups for IPv4 multicast transmission.
remote: Specifies remote default-groups for IPv4 multicast transmission.
Examples
# Display information about the local default-group for IPv4 multicast transmission in each VPN instance.
<Sysname> display multicast-domain default-group local
MD local default-group information:
Group address Source address Interface VPN instance
239.1.1.1 1.1.1.1 MTunnel0 mvpna
239.2.1.1 1.1.1.1 MTunnel1 mvpnb
239.3.1.1 -- MTunnel2 mvpnc
# Display information about the remote default-group for IPv4 multicast transmission in each VPN instance.
<Sysname> display multicast-domain default-group remote
MD remote default-group information:
Group address Source address Next hop VPN instance
239.1.1.1 1.2.0.1 1.2.0.1 a
239.1.1.1 1.2.0.2 1.2.0.2 a
239.1.1.1 1.2.0.3 1.2.0.3 a
239.1.1.2 1.2.0.1 1.2.0.1 b
239.1.1.2 1.2.0.2 1.2.0.2 b
239.1.1.3 1.2.0.1 1.2.0.1 -
Table 2 Command output
|
Field |
Description |
|
Group address |
IP address of the default-group for IPv4 multicast transmission. |
|
Source address |
IP address of the MD source interface, which is used by the MTI as the source address to encapsulate multicast packets for the VPN instance. |
|
Interface |
MTI interface. |
|
Next hop |
IP address of the next hop. |
|
VPN instance |
VPN instance to which the default-group belongs. |
log data-group-reuse
Use log data-group-reuse to enable data-group reuse logging.
Use undo log data-group-reuse to disable data-group reuse logging.
Syntax
log data-group-reuse
undo log data-group-reuse
Default
Data-group reuse logging is disabled.
Views
MD IPv4 address family view
Predefined user roles
network-admin
mdc-admin
Examples
# In MD IPv4 address family view of VPN instance mvpn, enable data-group reuse logging.
<Sysname> system-view
[Sysname] multicast-domain vpn-instance mvpn
[Sysname-md-mvpn] address-family ipv4
[Sysname-md-mvpn-ipv4] log data-group-reuse
multicast rpf-proxy-vector compatible
Use multicast rpf-proxy-vector compatible to enable RPF vector compatibility.
Use undo multicast rpf-proxy-vector compatible to disable RPF vector compatibility.
Syntax
multicast rpf-proxy-vector compatible
undo multicast rpf-proxy-vector compatible
Default
RPF vector compatibility is disabled.
Views
System view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
This command enables the device to work with other manufacturers' products on the RPF vector. You must configure this command on all H3C routers on the public network for multicast VPN inter-AS option B.
Examples
# Enable RPF vector compatibility.
<Sysname> system-view
[Sysname] multicast rpf-proxy-vector compatible
multicast-domain
Use multicast-domain to create an MD for a VPN instance and enter its view, or enter the view of the existing MD.
Use undo multicast-domain to delete configurations in MD view for a VPN instance.
Syntax
multicast-domain vpn-instance vpn-instance-name
undo multicast-domain vpn-instance vpn-instance-name
Default
No MD exists.
Views
System view
Predefined user roles
network-admin
mdc-admin
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters.
Examples
# Create an MD for VPN instance mvpn and enter MD view.
<Sysname> system-view
[Sysname] multicast-domain vpn-instance mvpn
[Sysname-md-mvpn]
rpf proxy vector
Use rpf proxy vector to enable the RPF vector feature.
Use undo rpf proxy vector to disable the RPF vector feature.
Syntax
rpf proxy vector
undo rpf proxy vector
Default
The RPF vector feature is disabled.
Views
MRIB view
Predefined user roles
network-admin
mdc-admin
Usage guidelines
This feature enables PE devices to carry the RPF vector information in PIM join messages for other devices to perform RPF check on the messages.
You must enable this feature on PE devices (excluding the PE devices that do not have attached receivers) when you configure multicast VPN inter-AS option B.
Only the configuration made in MRIB view of a VPN instance takes effect. The configuration made in MRIB view on the public network does not take effect.
Examples
# Enable the RPF vector feature for VPN instance mvpn.
<Sysname> system-view
[Sysname] multicast routing vpn-instance mvpn
[Sysname-mrib-mvpn] rpf proxy vector
source
Use source to specify an MD source interface.
Use undo source to restore the default.
Syntax
source interface-type interface-number
undo source
Default
No MD source interface is specified.
Views
MD IPv4 address family view
Predefined user roles
network-admin
mdc-admin
Parameters
interface-type interface-number: Specifies an interface by its type and number.
Usage guidelines
For the PE device to obtain correct routing information, you must specify the interface used for establishing BGP peer relationship as the MD source interface.
Examples
# In MD IPv4 address family view of VPN instance mvpn, specify Loopback 1 as the MD source interface. (Loopback 1 is the source interface used for establishing BGP peer relationship.)
<Sysname> system-view
[Sysname] multicast-domain vpn-instance mvpn
[Sysname-md-mvpn] address-family ipv4
[Sysname-md-mvpn-ipv4] source loopback 1
[Sysname-md-mvpn-ipv4] quit
