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 Inter-AS NG MVPN Option C

Configuring Inter-AS NG MVPN Option C

This section describes how to configure inter-AS NG MVPN Option C, in which PEs in different ASs establish multi-hop EBGP peer relationships to exchange VPNv4 routes.

Usage Scenario

In inter-AS NG MVPN Option C, PEs in different ASs establish MP-BGP peer relationships. For example, on the network shown in Figure 9-7, PE1 and PE2 establish an EBGP peer relationship to exchange VPN routes, PE1 and ASBR1 establish an IBGP peer relationship, ASBR1 and ASBR2 establish an EBGP peer relationship, and ASBR2 and PE2 establish an IBGP peer relationship. The public network uses non-segmented inter-AS mLDP tunnels to carry multicast VPN traffic. Figure 9-7 shows inter-AS NG MVPN Option C networking.

Inter-AS NG MVPN Option C is recommended if each AS needs to exchange a large number of VPN routes with other ASs. This option prevents an ASBR from impeding network expansion. After the local ASBR learns a labeled BGP public network route from the remote ASBR in an AS that is different from the AS of the local ASBR, the local ASBR allocates a label to this route based on the configured policy and advertises the route to the IBGP peer PE that is capable of label processing. A public network LSP is then set up.

NOTE:

In inter-AS NG MVPN Option C, do not enable LDP on ASBRs. If LDP is enabled on the interfaces that connect two ASBRs, LDP sessions are established between the ASBRs. The downstream ASBR then establishes an egress LSP and sends a Mapping message to the upstream ASBR. After receiving the Mapping message, the upstream ASBR establishes a transit LSP. When a large number of BGP routes exist, the LDP label consumption is high.

Figure 9-7 Inter-AS NG MVPN Option C networking

Pre-configuration Tasks

Before configuring inter-AS NG MVPN Option C, complete the following tasks:

  • Configure an IGP for the MPLS backbone network of each AS to ensure IP connectivity on each backbone network.

  • Configure basic MPLS functions and MPLS LDP for the MPLS backbone network of each AS.

  • Establish an IBGP peer relationship between the PE and ASBR in the same AS.

  • Configure a VPN instance on each PE connected to a CE and bind interfaces to VPN instances.

  • Assign an IP address to each CE interface that is connected to a PE.

Configuration Procedures

Figure 9-8 Flowchart for configuring inter-AS NG MVPN Option C

Perform one or more of the following configurations as required.

Configuring Global MPLS LDP Functions and Enabling MPLS LDP on Interfaces

Global LDP must be enabled on each node before LDP services can be configured in an MPLS domain.

Procedure

  1. Configure the MPLS LDP function globally and enable MPLS LDP on interfaces. For configuration details, see Configuring Global MPLS LDP Functions and Enabling MPLS LDP on Interfaces.

Configuring an Automatic mLDP P2MP Tunnel

Automatic mLDP P2MP tunnels are used to transmit NG MVPN traffic.

Procedure

  1. Enable mLDP P2MP and enable an mLDP P2MP service to span BGP AS domains. For configuration details, see Configuring an Automatic mLDP P2MP Tunnel.

Configuring a Static RP

To use a static Rendezvous Point (RP) in a PIM-SM domain, configure the same RP address and same address arrange of multicast groups that the RP serves on all routers in the PIM-SM domain.

Context

If a network is divided into multiple PIM-SM domains and the static RP needs to be used, configure the same static RP address on all the CEs and PEs in one PIM-SM domain to specify the range of each PIM-SM domain.

Procedure

  1. Configure a static RP to serve all routers in the PIM-SM domain. For configuration details, see Configuring a Static RP.

Configuring MP-IBGP Between a PE and an ASBR in the Same AS

By introducing extended community attributes into BGP, MP-IBGP can advertise VPNv4 routes between the PE and ASBR.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run peer peer-address as-number as-number

    The IBGP peer relationship is set up between the PE and ASBR in the same AS.

  4. Run peer peer-address connect-interface loopback interface-number

    The loopback interface is specified as the outbound interface of the BGP session.

  5. Run ipv4-family vpnv4 [ unicast ]

    The BGP-VPNv4 address family view is displayed.

  6. Run peer peer-address enable

    The function to exchange VPNv4 routes between the PE and ASBR is enabled.

  7. Run peer { group-name | ipv4-address } label-route-capability

    The capability to exchange labeled IPv4 routes is configured.

  8. Run commit

    The configuration is committed.

Configuring MP-EBGP for PEs and ASBRs in Different ASs

By introducing extended community attributes into BGP, MP-EBGP can advertise VPNv4 routes between PEs. And after an MP-EBGP peer relationship is established between ASBRs in different ASs, an ASBR can advertise the VPNv4 routes of its AS to the other ASBR.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bgp as-number

    The BGP view is displayed.

  3. Run peer peer-address as-number as-number

    The peer ASBR is specified as an EBGP peer.

  4. Run peer peer-address connect-interface loopback interface-number

    A loopback interface is specified as the outbound interface for BGP sessions.

  5. Run peer ipv4-address ebgp-max-hop [ hop-count ]

    The maximum number of hops between PEs for which an EBGP peer relationship is to be configured is specified.

    PEs of different ASs are generally not directly connected. To set up the EBGP peer relationship between PEs of different ASs, configure the maximum number of hops between PEs and ensure that PEs are reachable.

  6. Run ipv4-family unicast

    The unicast IPv4 address family view is displayed.

  7. Run peer peer-address enable

    The function to exchange IPv4 routes is enabled.

  8. (On PEs) Run quit

    The BGP view is displayed.

  9. (On PEs) Run ipv4-family vpnv4 [ unicast ]

    The BGP-VPNv4 address family view is displayed.

  10. (On PEs) Run peer peer-address enable

    The capability to exchange VPNv4 routes is enabled.

  11. (On PEs) Run policy vpn-target

    The VPN-Target filter function is enabled on PEs.

  12. Run commit

    The configuration is committed.

Configuring a Routing Policy to Control Label Distribution on ASBRs

Configure a routing policy to control MPLS label allocation for each IPv4 route. The ASBR only allocates label to the routes that match the rules in the policy.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run route-policy policy-name1 permit node seq-number

    The routing policy for local PE is configured. For the labeled IPv4 routes established to PEs in the same AS, allocate a new MPLS label for them.

  3. Run if-match mpls-label

    A filter rule is configured to match IPv4 routes with labels.

  4. Run apply mpls-label

    New labels are allocated to matched IPv4 routes.

  5. Run quit

    The system view is displayed.

  6. Run route-policy policy-name2 permit node seq-number

    The routing policy for peer ASBRs is configured. For the routes received from PE of local AS, ASBR allocates MPLS labels to them before establish them to peer ASBRs.

  7. Run apply mpls-label

    New labels are allocated to matched IPv4 routes.

  8. Run quit

    The system view is displayed.

  9. Run bgp as-number

    The BGP view is displayed.

  10. Run ipv4-family unicast

    The unicast IPv4 address family view is displayed.

  11. Run peer ipv4-address route-policy route-policy-name1 export

    The route policy applicable to the local PE is applied.

  12. Run peer ipv4-address route-policy route-policy-name2 export

    The route policy applicable to the peer ASBR is applied.

  13. Run peer ipv4-address label-route-capability

    The capability to exchange labeled IPv4 routes with the local PE and the peer ASBR is configured.

    • In Option C, an inter-AS LSP must be established and the public network routes advertised between PEs and ASBRs carry MPLS labels.
    • An EBGP peer relationship must be established between ASBRs in different ASs for them to exchange labeled IPv4 routes.
    • The public network routes carrying MPLS labels are advertised through MP-BGP. According to relevant standards, label mappings about routes can be piggybacked inside the BGP Update messages that are used to advertise these routes. This feature is implemented through an extended BGP attribute, which enables BGP peers to process labeled IPv4 routes.
    • By default, BGP peers cannot process labeled IPv4 routes.

  14. Run commit

    The configuration is committed.

Configuring BGP MVPN Peers

Establish a BGP MVPN peer relationship between PEs belonging to the same MVPN so that the PEs can use BGP to exchange BGP A-D and BGP C-multicast routes.

Context

To exchange BGP A-D and BGP C-multicast routes, different PEs on an MVPN must be able to discover other PEs on the MVPN. The discovery process is called MVPN membership autodiscovery. An NG MVPN uses BGP to implement this process. To support MVPN membership autodiscovery, BGP defines a new BGP-MVPN address family.

On an NG MVPN, a PE can be either a sender or receiver PE. To transmit multicast traffic from multicast sources to multicast receivers, sender PEs must establish BGP MVPN peer relationships with receiver PEs.

Perform the following steps on the PE and ASBR.

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 mvpn

    The BGP-MVPN address family view is displayed.

  4. (On PEs) Run policy vpn-target

    The VPN—Target filter is enabled on PEs.

  5. (On ASBRs) Run undo policy vpn-target

    The VPN—Target filter is disabled on ASBRs.

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

    The device is specified as a BGP MVPN peer.

  7. Run commit

    The configuration is committed.

Configuring a P2MP LSP to Carry Multicast Traffic

An NG MVPN uses P2MP LSPs to carry multicast traffic. Only mLDP P2MP LSPs is supported.

Context

Currently, only mLDP P2MP tunnel is supported to carry multicast traffic in seamless inter-AS NG MVPN. The mLDP P2MP tunnel is easy to configure. It is usually applied to networks that do not require control over destination nodes and high service quality.

Procedure

  • Perform the following steps on a PE to be configured as a sender PE:
    1. Run system-view

      The system view is displayed.

    2. Run multicast mvpn mvpn-id

      An MVPN ID is configured.

    3. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    4. Run ipv4-family

      The VPN instance IPv4 address family view is displayed.

    5. Run route-distinguisher route-distinguisher

      The RD of IPv4 address family is configured.

    6. Run vpn-target vpn-target1 &<1-8> [ both | export-extcommunity | import-extcommunity ]

      The VPN-Target extended community attributesis are configured for VPN instance IPv4 address family. The VPN instance can receive and process VPNv4 routes.

    7. Run multicast routing-enable

      Multicast routing is enabled in for VPN instance IPv4 address family.

    8. Run mvpnThe VPN instance IPv4 address family MVPN view is displayed.

    9. Run sender-enable

      The PE is configured as a sender PE. By default, a PE is a receiver PE.

    10. Run c-multicast signaling bgp

      The BGP is configured as the signaling protocol for transmitting C-multicast routes.

    11. Run auto-discovery inter-as

      The inter-AS auto-discovery function is enabled.

    12. Run ipmsi-tunnel

      The MVPN I-PMSI view is displayed.

    13. Run mldp (MVPN I-PMSI view)

      The mLDP is used to establish an I-PMSI tunnel.

    14. Run commit

      The configuration is committed.

  • Perform the following steps on a PE to be configured as a receiver PE:
    1. Run system-view

      The system view is displayed.

    2. Run multicast mvpn mvpn-id

      An MVPN ID is configured.

    3. Run ip vpn-instance vpn-instance-name

      The VPN instance view is displayed.

    4. Run ipv4-family

      The VPN instance IPv4 address family view is displayed.

    5. Run route-distinguisher route-distinguisher

      The RD of IPv4 address family is configured.

    6. Run vpn-target vpn-target1 &<1-8> [ both | export-extcommunity | import-extcommunity ]

      The VPN-Target extended community attributesis are configured for VPN instance IPv4 address family. The VPN instance can receive and process VPNv4 routes.

    7. Run multicast routing-enable

      Multicast routing is enabled in for VPN instance IPv4 address family.

    8. Run mvpn

      The VPN instance IPv4 address family MVPN view is displayed.

    9. Run c-multicast signaling bgp

      The BGP is configured as the signaling protocol for transmitting C-multicast routes.

    10. Run auto-discovery inter-as

      The inter-AS auto-discovery function is enabled.

    11. Run commit

      The configuration is committed.

Configuring PIM

Configuring PIM on a VPN allows a VPN multicast routing table to be established to guide multicast traffic forwarding.

Context

NG MVPNs also use PIM as the multicast routing protocol on the user network. PIM neighbor relationships can be established between devices only after PIM-SM is enabled on interfaces. Then a VPN multicast routing table can be established to guide multicast traffic forwarding.

Perform the following steps on the PE interfaces bound to VPN instances and the CE interfaces.

Procedure

  1. Run system-view

    The system view is displayed.

  2. (On CEs) Run multicast routing-enable

    Multicast routing is enabled.

  3. Run interface interface-type interface-number

    The interface view is displayed.

  4. Run pim sm

    PIM-SM is enabled.

  5. Run the following command on the interfaces connected to users in CEs:

    igmp enable

    IGMP is enabled.

  6. Run commit

    The configuration is committed.

Configuring Route Exchange Between PEs and CEs

The routing protocol between CE and PE can be BGP, static routing (including default static routes), and IGP.

Procedure

  1. According to the routing protocol used between PE and CE, configure route exchange between them. For configuration details, see Configuring Route Exchange Between PEs and CEs.
Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055017

Views: 44105

Downloads: 97

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