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

ME60 V800R010C10SPC500 Feature Description - IP Multicast 01

This is ME60 V800R010C10SPC500 Feature Description - 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).
NG MVPN Control Messages

NG MVPN Control Messages

The key mechanism of NG MVPN is the transmission of VPN multicast routes and the establishment of public network tunnels. The two mechanisms are implemented by transmitting BGP messages on the public network. These messages are NG MVPN control messages.

PEs on an NG MVPN exchange control messages to implement functions such as MVPN membership autodiscovery, PMSI tunnel establishment, and VPN multicast joining and leaving. The following describes these NG MVPN control messages. All examples in this document are based on the network shown in Figure 8-2. On this network:
  • The service provider's backbone network provides both unicast and multicast VPN services for vpn1. The AS number of the backbone network is 65001.
  • The multicast source resides at Site1 and accesses PE1 by means of CE1. This multicast source sends multicast traffic to multicast group 232.1.1.1.
  • Multicast receivers reside at Site2 and Site3.
  • The backbone network provides MVPN services for vpn1 over RSVP-TE or mLDP P2MP tunnels.
Figure 8-2 NG MVPN

MVPN NLRI

A PE that participates in an NG MVPN is required to send a BGP Update message containing the MVPN NLRI. The SAFI of the MVPN NLRI is 5. Figure 8-3 shows the MVPN NLRI format.

Figure 8-3 MVPN NLRI format

Table 8-2 Description of the fields in the MVPN NLRI

Field

Description

Route type

Type of an MVPN route. Seven types of MVPN routes are specified. For more information, see Table 8-4.

Length

Length of the Route Type specific field of the MVPN NLRI.

Route type specific

MVPN route information. The value of this field depends on the Route Type field. For more information, see Table 8-3.

Table 8-3 describes the types and functions of MVPN routes. Type 1-5 routes are called MVPN A-D routes. These routes are used for MVPN membership autodiscovery and P2MP tunnel establishment. Type 6 and Type 7 routes are called C-multicast routes (C is short for Customer. C-multicast routes refer to multicast routes from the private network). These routes are used for VPN multicast joining and VPN multicast traffic forwarding.

Table 8-3 Types and functions of MVPN routes

Route Type

Name

Function

Route Type Specific Field Format

1

Intra-AS I-PMSI A-D route

Used for MVPN membership autodiscovery in intra-AS scenarios. MVPN-capable PEs use Intra-AS I-PMSI A-D routes to advertise and learn intra-AS MVPN membership information.

2

Inter-AS I-PMSI A-D route

Used for MVPN membership autodiscovery in inter-AS scenarios. MVPN-capable ASBRs use Inter-AS I-PMSI A-D routes to advertise and learn inter-AS MVPN membership information.

3

S-PMSI A-D route

Used by a sender PE to initiate a selective P-tunnel for a particular (C-S, C-G).

4

Leaf A-D route

Originated by a receiver PE in response to receiving a Type 3 route. A sender PE uses Leaf A-D routes to discover the leaf nodes of an S-PMSI tunnel.

NOTE:

The Route Key is set to the MVPN NLRI of the S-PMSI A-D route received.

5

Source Active A-D route

Used by PEs to learn the identity of active VPN multicast sources.

6

Shared Tree Join route

Used in (*, G) scenarios.

The Shared Tree Join route is originated when a receiver PE receives a (C-*, C-G) PIM Join message. A receiver PE sends the Shared Tree Join route to sender PEs with which it has established BGP peer relationships.
NOTE:
The (*, G) PIM-SM join initiated by a VPN is called a (C-*, C-G) PIM join.
NOTE:

Shared Tree Join routes and Source Tree Join routes have the same NLRI format. The multicast source address is the RP address for (C-*, C-G) joins.

7

Source Tree Join route

Used in (S, G) scenarios.

The Source Tree Join route is originated when a receiver PE receives a (C-S, C-G) PIM Join message. A receiver PE sends the Source Tree Join route to sender PEs with which it has established BGP peer relationships.
NOTE:
The (S, G) PIM-SSM join initiated by a VPN is called a (C-S, C-G) PIM join.

Intra-AS I-PMSI A-D Route

Figure 8-4 (a) shows the format of an Intra-AS I-PMSI A-D route. Figure 8-4 (b) shows the contents of the Intra-AS I-PMSI A-D route sent by PE1 to PE2 and PE3 on the network shown in Figure 8-2.

Figure 8-4 Intra-AS I-PMSI A-D route format

Table 8-4 Description of the fields for an Intra-AS I-PMSI A-D route

Field

Description

RD

Route distinguisher, an 8-byte field. An RD and a 4-byte IPv4 address prefix form a VPNv4 address, which is used to differentiate IPv4 prefixes using the same address space.

Originating router's IP address

IP address of the device that originates the A-D route. In ME60, the value is equal to the MVPN ID of the router that originates the A-D route.

Inter-AS I-PMSI A-D route

Figure 8-5 (a) shows the format of an Inter-AS I-PMSI A-D route. Figure 8-5 (b) shows the contents of the Inter-AS I-PMSI A-D route sent by local PE to PEs in other AS.

Figure 8-5 Inter-AS I-PMSI A-D route format
Table 8-5 Description of the fields for an Inter-AS I-PMSI A-D route

Field

Description

RD

Route distinguisher, an 8-byte field. An RD and a 4-byte IPv4 address prefix form a VPNv4 address, which is used to differentiate IPv4 prefixes using the same address space.

Source AS

AS of the source device which sends Inter-AS A-D route.

S-PMSI A-D Route

Figure 8-6 (a) shows the format of an S-PMSI A-D route. Figure 8-6 (b) shows the contents of the S-PMSI A-D route sent by PE1 to PE2 and PE3 on the network shown in Figure 8-2.

Figure 8-6 S-PMSI A-D route format

Table 8-6 Description of the fields for an S-PMSI A-D route

Field

Description

RD

Route distinguisher, an 8-byte field in a VPNv4 address. An RD and a 4-byte IPv4 address prefix form a VPNv4 address, which is used to differentiate IPv4 prefixes using the same address space.

Multicast source length

Length of the multicast source address. The value is 32 if the multicast source address is an IPv4 address or 128 if the multicast source address is an IPv6 address.

Multicast source

Multicast source address.

Multicast group length

Length of the multicast group address. The value is 32 if the multicast group address is an IPv4 address or 128 if the multicast group address is an IPv6 address.

Multicast group

Multicast group address.

Originating router's IP address

IP address of the router that originates the A-D route. In ME60, the value is equal to the MVPN ID of the router that originates the A-D route.

Leaf A-D Route

Figure 8-7 (a) shows the format of a Leaf A-D route. Figure 8-7 (b) shows the contents of the Leaf A-D route sent by PE2 to PE1 in response to receiving an S-PMSI A-D route on the network shown in Figure 8-2.
Figure 8-7 Leaf A-D route format
Table 8-7 Description of the fields for a Leaf A-D route

Field

Description

Route key

Set to the MVPN NLRI of the S-PMSI A-D route received.

Originating router's IP address

IP address of the router that originates the A-D route. In ME60, the value is equal to the MVPN ID of the router that originates the A-D route.

Source Active A-D Route

Figure 8-8 (a) shows the format of a Source Active A-D route. Figure 8-8 (b) shows the contents of the Source Active route sent by PE1 to PE2 and PE3 after PE1 discovers an active multicast source and the corresponding multicast group (192.168.1.2, 224.1.1.1) on the network shown in Figure 8-2.

Figure 8-8 Source Active A-D route format

Table 8-8 Description of the fields for a Source Active A-D route

Field

Description

RD

RD of the sender PE connected to the multicast source.

Multicast source length

Length of the multicast source address. The value is 32 if the multicast source address is an IPv4 address or 128 if the multicast source address is an IPv6 address.

Multicast source

Multicast source address.

Multicast group length

Length of the multicast group address. The value is 32 if the multicast group address is an IPv4 address or 128 if the multicast group address is an IPv6 address.

Multicast group

Multicast group address.

Shared Tree Join route

Figure 8-9 (a) shows the format of a Shared Tree Join route. Figure 8-9 (b) shows the contents of the Shared Tree Join route sent by PE2 to PE1 on the network shown in Figure 8-2.

Figure 8-9 Shared Tree Join route format
Table 8-9 Description of the fields for a Shared Tree Join route

Field

Description

Route type

MVPN route type. The value 6 indicates that the route is a Type 6 route (Shared Tree Join route).

Rt-import

VRF Route Import Extended Community of the unicast route to the multicast source. For more information about the VRF Route Import Extended Community, see MVPN Extended Communities.

The VRF Route Import Extended Community is used by sender PEs to determine whether to process the BGP C-multicast route sent by a receiver PE. This attribute also helps a sender PE to determine to which VPN instance routing table a BGP C-multicast route should be added.

Next hop

Next hop address.

RD

RD of the sender PE connected to the multicast source.

Source AS

Source AS Extended Community of the unicast route to the multicast source. For more information about the Source AS Extended Community, see MVPN Extended Communities.

Multicast source length

Length of the multicast source address. The value is 32 if the multicast group address is an IPv4 address or 128 if the multicast group address is an IPv6 address.

RP address

Rendezvous Point (Rendezvous Point) address.

Multicast group length

Length of the multicast group address. The value is 32 if the multicast group address is an IPv4 address or 128 if the multicast group address is an IPv6 address.

Multicast group

Multicast group address.

Source Tree Join Route

Figure 8-10 (a) shows the format of a Source Tree Join route. Figure 8-10 (b) shows the contents of the Source Tree Join route sent by PE2 to PE1 on the network shown in Figure 8-2.

Figure 8-10 Source Tree Join route format

Table 8-10 Description of the fields for a Source Tree Join route

Field

Description

RD

RD of the sender PE connected to the multicast source.

Source AS

Source AS Extended Community of the unicast route to the multicast source. For more information about the Source AS Extended Community, see MVPN Extended Communities.

Multicast source length

Length of the multicast source address. The value is 32 if the multicast group address is an IPv4 address or 128 if the multicast group address is an IPv6 address.

Multicast source

Multicast source address.

Multicast group length

Length of the multicast group address. The value is 32 if the multicast group address is an IPv4 address or 128 if the multicast group address is an IPv6 address.

Multicast group

Multicast group address.

PMSI Tunnel Attribute

The PMSI Tunnel attribute carries P-tunnel information used for P-tunnel establishment. Figure 8-11 shows the PMSI Tunnel attribute format.

Figure 8-11 PMSI Tunnel attribute format

Table 8-11 Description of fields for the PMSI Tunnel attribute

Field

Description

Flags

Flags bits. Currently, only one flag indicating whether leaf information is required is specified:
  • If the PMSI Tunnel attribute carried with a Type 3 route has its Flags bit set to Leaf Information Not Required, the receiver PE that receives the Type 3 route does not need to respond.
  • If the PMSI Tunnel attribute carried with a Type 3 route has its Flags bit set to Leaf Information Required, the receiver PE that receives the Type 3 route needs to send a Leaf A-D route in response.

Tunnel type

Tunnel type, which can be:
  • 0: No tunnel information present
  • 1: RSVP-TE P2MP LSP
  • 2: mLDP P2MP LSP
  • 3: PIM-SSM Tree
  • 4: PIM-SM Tree
  • 5: BIDIR-PIM Tree
  • 6: Ingress Replication
  • 7: mLDP MP2MP LSP
Currently, ME60 supports only RSVP-TE and mLDP P2MP tunnels.

MPLS label

MPLS labels are used for VPN tunnel multiplexing. Currently, tunnel multiplexing is not supported.

Tunnel identifier

Tunnel identifier. Its value depends on the value set in the Tunnel Type field: The ME60 supports only the following two types of tunnels:
  • If the tunnel type is RSVP-TE P2MP LSP, its value is <P2MP ID, Tunnel ID, Extended Tunnel ID>.
  • If the tunnel type is mLDP P2MP LSP, its value is <Root node address, Opaque value>.

On an NG MVPN, the sender PE sets up the P-tunnel, and therefore is responsible for originating the PMSI Tunnel attribute. The PMSI Tunnel attribute can be attached to Type 1-3 routes and sent to receiver PEs. Figure 8-12 is an example shows the format of an Intra-AS I-PMSI A-D route carrying the PMSI Tunnel attribute.

Figure 8-12 Intra-AS I-PMSI A-D route carrying the PMSI Tunnel attribute

Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059456

Views: 10686

Downloads: 13

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