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

NE40E V800R010C10SPC500 Configuration Guide - IP Multicast 01

This is NE40E V800R010C10SPC500 Configuration Guide - IP Multicast
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).
Configuring BGP A-D Multicast VPN

Configuring BGP A-D Multicast VPN

The configuration of BGP A-D multicast VPN enables the Auto Discovery (AD) of PEs on the same VPN and allows multicast VPN services to run in public network tunnels based on PIM-SSM distribution trees.

Usage Scenario

Before the BGP A-D MVPN is introduced, MD MVPNs can establish only PIM-SM MDTs. This is because PEs belonging to the same VPN cannot detect each other's peer information. As a result, PEs belonging to the same VPN cannot detect the multicast source, and therefore are unable to send PIM-SSM Join messages to the multicast source to establish a PIM-SSM MDT.

After the BGP A-D MVPN is introduced, MD MVPNs can also establish PIM-SSM MDTs. On a BGP A-D MVPN, PEs obtain and record peer information about a VPN by exchanging BGP Update packets that carry A-D route information. Then, these PEs send PIM-SSM Join messages directly to the multicast source to establish a PIM-SSM MDT. After the PIM-SSM MDT is established, the BGP A-D MVPN transmits multicast services over a public network tunnel based on the PIM-SSM MDT.

NOTE:

If multicast VPN is implemented in BGP A-D mode, the configured A-D mode must be consistent with the A-D address family type configured in the BGP view.

Pre-configuration Tasks

Before configuring BGP A-D Multicast VPN, complete the following tasks:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp { as-number-plain | as-number-dot }

    The BGP view is displayed.

  3. Run ipv4-family mdt

    The BGP-MDT address family view is displayed.

  4. Run peer { group-name | ipv4-address } enable

    Route exchange with a specific peer or peer group is enabled in the BGP-MDT address family view.

  5. Run quit

    The BGP-MDT address family view is closed.

  6. Run quit

    The BGP view is closed.

  7. Run ip vpn-instance vpn-instance-name

    The VPN instance view is displayed.

  8. Run ipv4-family

    The VPN instance IPv4 address family is enabled and its view is displayed.

  9. Run auto-discovery mdt [ import route-policy route-policy-name ]

    The MDT-SAFI A-D mode is configured for the VPN instance IPv4 address family.

  10. Run commit

    The configuration is committed.

Checking the Configurations

After the BGP A-D multicast VPN is configured, run the following commands to check the configurations:

  • Run the 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 } ] | incoming-interface { interface-type interface-number | register } | outgoing-interface { include | exclude | match } { interface-type interface-number | vpn-instance vpn-instance-name | register | none } | mode { ssm | sm } | flags flag-value | fsm ] * [ outgoing-interface-number [ number ] ] command to check the PIM routing table.
  • Run the 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 | vpn-instance vpn-instance-name | register | none } ] * [ outgoing-interface-number [ number ] ] command to check the multicast routing table.
  • Run the display multicast-domain vpn-instance vpn-instance-name share-group [ local | remote ] command to check the Share-Group information of a specified VPN instance in a multicast domain.

Run the display pim routing-table command to view the PIM routing table. For example:

<HUAWEI> display pim routing-table
 VPN-Instance: public net
 Total 2 (S, G) entries

 (1.1.1.1, 232.2.2.0)
     Protocol: pim-ssm, Flag: SG_RCVR
     UpTime: 00:05:30
     Upstream interface: GigabitEthernet1/0/0
         Upstream neighbor: 192.168.2.1
         RPF prime neighbor: 192.168.2.1
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: VPN-Instance: BLUE
             Protocol: MD, UpTime: 00:05:30, Expires: -

 (3.3.3.3, 232.2.2.0)
     Protocol: pim-ssm, Flag: LOC
     UpTime: 00:05:30
     Upstream interface: LoopBack1
         Upstream neighbor: NULL
         RPF prime neighbor: NULL
     Downstream interface(s) information:
     Total number of downstreams: 1
        1: GigabitEthernet1/0/0
             Protocol: pim-ssm, UpTime: 00:05:30, Expires: 00:03:01

The command output shows that a PIM-SSM MDT is set up on the public network to carry VPN multicast services.

Run the display multicast vpn-instance BLUE routing-table command to view the multicast routing table. For example:

<HUAWEI> display multicast vpn-instance BLUE routing-table
Multicast routing table of VPN-Instance: BLUE
 Total 1 entry

 00001. (10.110.1.100, 225.0.0.1)
       Uptime: 00:06:25
       Upstream Interface: MTunnel0
       List of 1 downstream interface
           1: GigabitEthernet2/0/0

The command output shows that multicast data has reached the receiver.

Run the display multicast-domain vpn-instance BLUE share-group command to view Share-Group information of a VPN instance named BLUE. For example:

<HUAWEI> display multicast-domain vpn-instance BLUE share-group
MD local share-group information for VPN-Instance: BLUE
  Share-group: 232.2.2.0
  MTunnel address: 3.3.3.3
MD remote share-group information for VPN-Instance: BLUE
  Share-group     Peer-address
  232.2.2.0       1.1.1.1

The command output shows that the remote Share-Group address of the VPN instance BLUE is 232.2.2.0; and the IP address of the remote peer is 1.1.1.1.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 43220

Downloads: 97

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