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 Configuration Guide - LAN Access and MAN Access 01

This is ME60 V800R010C10SPC500 Configuration Guide - LAN Access and MAN Access
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 an EVC to Transmit Multicast Services

Configuring an EVC to Transmit Multicast Services

To improve network resource usage and implement on-demand multicast data forwarding in an EVC scenario, configure an EVC to transmit multicast services.

Usage Scenario

  • Configure an EVC to transmit Layer 2 multicast services.

    After a multicast data message is received on an interface in a broadcast domain (BD), the message is broadcast to all the other interfaces in the same BD, including the interfaces not connected to multicast data receivers. Such data broadcasting wastes bandwidth resources and may result in security issues. To resolve these issues, configure an EVC to implement on-demand Layer 2 multicast service transmission in a specific BD.

  • Configure an EVC to transmit Layer 3 multicast services.

    An EVC applies to Layer 2 interfaces and does not support IP address configuration. To enable an EVC-capable BD to communicate with Layer 3 interfaces, configure a logical VBDIF interface for the BD. A VBDIF interface is a network-layer interface and supports IP address configuration. By configuring a VBDIF interface for a BD, you can enable an EVC to transmit Layer 3 multicast services , which simplifies network planning and management.

Pre-configuration Tasks

Before configuring an EVC to transmit multicast services, complete the following tasks:

  • Create an EVC model.
  • Configure a routing protocol so that devices can communicate at the network layer.

Configuration Procedures

Perform one or more of the following configurations as required.

Configuring an EVC to Transmit Layer 3 Multicast Services

To enable an EVC-capable BD to communicate with a Layer 3 multicast network, configure a VBDIF interface for the BD, so that the EVC can transmit Layer 3 multicast services and implement on-demand data forwarding.

Context

EVC applies to Layer 2 interfaces and does not support IP address configurations. To enable an EVC-capable BD to communicate with Layer 3 interfaces, configure a logical VBDIF interface for the BD. A VBDIF interface is a network-layer interface and supports IP address configuration. By configuring a VBDIF interface for a BD, you can enable an EVC to transmit Layer 3 multicast services, , which simplifies network planning and management.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run multicast routing-enable

    IP multicast routing is enabled.

  3. Run bridge-domain bd-id

    The BD view is displayed.

  4. Run quit

    Return to the system view.

  5. Run interface vbdif bd-id

    A VBDIF interface is created, and the interface view is displayed.

  6. Run pim sm

    PIM-SM is enabled.

  7. Run commit

    The configuration is committed.

Configuring an EVC to Transmit Layer 2 Multicast Services

To improve network resource usage and implement on-demand multicast data forwarding in an EVC scenario, configure an EVC to transmit Layer 2 multicast services.

Context

On a Layer 2 multicast network, a Layer 2 device sets up mappings between interfaces and multicast MAC addresses by analyzing Internet Group Management Protocol (IGMP) packets transmitted between Layer 3 devices and users. The mapping information helps implement on-demand multicast data forwarding at the data link layer. If Layer 2 multicast devices use multiple different access modes on a network, service management and configuration are complicated and difficult. To resolve this issue, configure an EVC to transmit Layer 2 multicast services, implementing simplified network planning and management.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run igmp-snooping enable

    IGMP snooping is enabled globally.

  3. Run bridge-domain bd-id

    The BD view is displayed.

  4. (Optional) Run igmp-snooping designated-vlan vlan-id

    The transparent transmission function is enabled in the BD for IGMP snooping messages with a specified VLAN ID.

    NOTE:

    This command can be run only in the BD that contains dot1q sub-interfaces with the default traffic behavior.

  5. Run igmp-snooping enable

    IGMP snooping is enabled in the BD view.

  6. Run interface interface-type interface-number.subnum mode l2

    An EVC Layer 2 sub-interface is specified, and its view is displayed.

    NOTE:
    EVC Layer 2 multicast can be configured only for termination-type user sub-interfaces (If the traffic encapsulation type is untag, do not configure any traffic behavior; if the traffic encapsulation type is dot1q, configure the traffic behavior of pop single; if the traffic encapsulation type is QinQ, configure the traffic behavior of pop double).

  7. (Optional) Run igmp-snooping static-router-port [ dot1q vid vid | qinq pe-vid pe-vid ce-vid ce-vid ]

    A static router interface is specified.

    To have multicast traffic received through a specific router interface, use this command to specify the interface.

  8. Run commit

    The configuration is committed.

Checking the Configurations

After configuring an EVC to transmit multicast services, you can check the status of multicast services.

Prerequisites

An EVC has been configured to transmit multicast services.

Procedure

  • Run the display igmp-snooping bridge-domain [ bd-id ] [ configuration ] command to check whether IGMP snooping is enabled.
  • Run the display igmp-snooping router-port bridge-domain bd-id command to check information about router interfaces.
  • Run the display pim interface [ interface-type interface-number ] [ verbose ] command to check whether PIM-SM is enabled.
  • Run the display pim routing table command to check IPv4 routing entries.

Example

Run the display igmp-snooping bridge-domain [ bd-id ] [ configuration ] command to view the status of IGMP snooping.

<HUAWEI> display igmp-snooping bridge-domain configuration
 IGMP Snooping Configuration for bridge-domain 10
     igmp-snooping enable

Run the display igmp-snooping router-port bridge-domain bd-id command to view information about router interfaces.

<HUAWEI> display igmp-snooping router-port bridge-domain 10
 Port Name                         UpTime        Expires       Flags
 ---------------------------------------------------------------------
 Bridge-domain 10, 1 router-port(s)
 GE1/0/0.1(PE:10)                  00:01:02      --          STATIC

The command output shows that GE 1/0/0.1 is specified as a static router interface.

Run the display pim interface [ interface-type interface-number ] [ verbose ] command to view the status of PIM-SM.

[~Device A] display pim interface 
  VPN-Instance: public net  Interface           State NbrCnt HelloInt   DR-Pri     DR-Address  Vbdif10             up    1      30         1          192.168.1.1  GE1/0/2             up    0      30         1          20.0.5.100 (local) 

Run the display pim routing table command to view IPv4 routing entries.

[~Device B] display pim routing table 
VPN-Instance: public net  Total 0 (*, G) entry; 1 (S, G) entry   (20.0.5.100, 225.1.0.0)      RP: 192.168.1.2 (local)      Protocol: pim-sm, Flag: SPT SG_RCVR      UpTime: 19:57:50      Upstream interface: Vbdif10          Upstream neighbor: 192.168.1.1          RPF prime neighbor: 192.168.1.1      Downstream interface(s) information:      Total number of downstreams: 1         1: GigabitEthernet1/0/2              Protocol: static, UpTime: 19:57:50, Expires: -
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059440

Views: 27149

Downloads: 18

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