No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

CLI-based Configuration Guide - IP Multicast

AR500, AR510, and AR530 V200R007

This document describes the principles and configurations of IP multicast, and provides configuration examples.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Checking the Configuration

Checking the Configuration

After configuring multicast VPN extranet, you can view information about the multicast routing table, PIM routing table, and source-specific or source/group-specific RPF route to ensure normal multicast data transmission between VPN instances.

Prerequisites

Multicast VPN extranet has been configured.

Procedure

  • Run either of the following commands to check the multicast routing table:

    • display multicast { vpn-instance vpn-instance-name | all-instance } routing-table [ group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask { source-mask | source-mask-length } ] | incoming-interface { interface-type interface-number | register | mcast-extranet } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } | extranet { source-vpn-instance { all | public | vpn-instance-name } | receive-vpn-instance { all | vpn-instance-name } } ] * [ outgoing-interface-number [ number ] ]

    • display multicast routing-table [ group-address [ mask { group-mask | group-mask-length } ] | source-address [ mask { source-mask | source-mask-length | mcast-extranet } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { include | exclude | match } { interface-type interface-number | vpn-instance vpn-instance-name | register | none } | extranet { source-vpn-instance { all | public | vpn-instance-name } | receive-vpn-instance { all | vpn-instance-name } } ] * [ outgoing-interface-number [ number ] ]

  • Run one of the following commands to check the PIM routing table:

    • display pim { vpn-instance vpn-instance-name | all-instance } routing-table [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | extranet { source-vpn-instance { all | public | vpn-instance-name } | receive-vpn-instance { all | vpn-instance-name } } | incoming-interface { interface-type interface-number | register | mcast-extranet } | outgoing-interface { include | exclude | match } { interface-type interface-number | register | none } | mode { dm | sm | ssm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ]

    • display pim routing-table [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | extranet { source-vpn-instance { all | public | vpn-instance-name } | receive-vpn-instance { all | vpn-instance-name } } | incoming-interface { interface-type interface-number | register | mcast-extranet } | outgoing-interface { include | exclude | match } { interface-type interface-number | vpn-instance vpn-instance-name | register | none } | mode { dm | sm | ssm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ]

    • display pim [ vpn-instance vpn-instance-name | all-instance ] routing-table brief [ group-address [ mask { group-mask-length | group-mask } ] | source-address [ mask { source-mask-length | source-mask } ] | extranet { source-vpn-instance { all | public | vpn-instance-name } | receive-vpn-instance { all | vpn-instance-name } } | incoming-interface { interface-type interface-number | register | mcast-extranet } ] *

  • Run the display multicast [ vpn-instance vpn-instance-name | all-instance ] rpf-info source-address [ group-address ] [ rpt | spt ] command to check the source-specific or source/group-specific RPF route.

Example

Run the display multicast vpn-instance RED routing-table extranet source-vpn-instance BLUE command to view information about the multicast routing table of VPN BLUE, which is the upstream of the RPF route of the multicast entry in VPN RED. For example:

<Huawei> display multicast vpn-instance RED routing-table extranet source-vpn-instance BLUE
Multicast routing table of VPN-Instance: RED
 Total 1 entry ,1 matched

 00001. (10.110.1.2, 228.0.0.1)
       Uptime: 00:00:39
       Upstream Interface: MCAST_Extranet(BLUE)
       List of 1 downstream interface
           1:  Pos1/0/1

The command output shows that the upstream of the RPF route of the entry (10.110.1.2, 228.0.0.1) in VPN RED is a multicast extranet interface, namely, VPN BLUE.

Run the display pim vpn-instance RED routing-table extranet source-vpn-instance BLUE command to view information about the PIM routing table of VPN BLUE, which is the upstream of the RPF route of the multicast entry in VPN RED. For example:

<Huawei> display pim vpn-instance RED routing-table extranet source-vpn-instance BLUE
 VPN-Instance: RED
 Total 2 (*, G) entries; 1 (S, G) entry

 Total matched 1 (*, G) entry; 1 (S, G) entry

 (*, 228.0.0.1)
     RP: 11.11.11.11
     Protocol: pim-sm, Flag: WC
     UpTime: 00:01:28
     Upstream interface: MCAST_Extranet(BLUE)
         Upstream neighbor: 1.1.1.1
         RPF prime neighbor: 1.1.1.1
     Downstream interface(s) information:
     Total number of downstreams: 1
         1: Pos1/0/1
             Protocol: pim-sm, UpTime: 00:01:28, Expires: 00:03:01

 (10.110.1.2, 228.0.0.1)
     RP: 11.11.11.11
     Protocol: pim-sm, Flag: SPT ACT
     UpTime: 00:01:28
     Upstream interface: MCAST_Extranet(BLUE)
         Upstream neighbor: 1.1.1.1
         RPF prime neighbor: 1.1.1.1
     Downstream interface(s) information:
     Total number of downstreams: 1
         1: Pos1/0/1
             Protocol: pim-sm, UpTime: 00:01:28, Expires: 00:03:07

The command output shows that the upstream of the RPF route of the PIM entry with the group address being 228.0.0.1 in VPN RED is a multicast extranet interface, namely, VPN BLUE.

Run the display multicast vpn-instance RED rpf-info 10.110.1.2 228.0.0.0 command to view information about the RPF route of the multicast source 10.110.1.2 in VPN RED. For example:

<Huawei> display multicast vpn-instance RED rpf-info 10.110.1.2 228.0.0.0
 VPN-Instance: RED
 RPF information about source 10.110.1.2 and group 228.0.0.0
     RPF interface: MCAST_Extranet
     RPF Source VPN-Instance: BLUE
     Referenced route/mask: 10.110.1.0/24
     Referenced route type: unicast
     Route selection rule: preference-preferred
     Load splitting rule: disable

The command output shows that the upstream of the RPF route of the entry (10.110.1.2, 228.0.0.0) in VPN RED is a multicast extranet interface, namely, VPN BLUE.

Translation
Download
Updated: 2019-06-12

Document ID: EDOC1000097280

Views: 9416

Downloads: 20

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next