service type (Eth-trunk interface view)

Usage Scenario

The switch can receive the VPN multicast packets and use GRE to encapsulate them only after a multicast loopback interface has been configured.

Follow-up Procedure

Configure member interfaces of the multicast loopback interface using the trunkport command.

Precautions

• After you configure an interface as a multicast loopback interface, the switch automatically disables STP on this interface. The interface then does not support STP configuration commands. After the multicast loopback interface configuration is cancelled, the switch automatically enables STP on the interface.
• On the switch, only one Eth-Trunk interface can function as the multicast loopback interface. All VPN multicast packets are encapsulated on this interface into public network multicast data packets.

• The configurations allowed on an Eth-Trunk to be configured as a loopback interface include description, enable snmp trap updown, jumboframe enable, mixed-rate link enable, qos phb marking enable, set flow-stat interval, shutdown, local-preference enable, traffic-policy (interface view), and trust. If other configurations exist on the Eth-Trunk, the Eth-Trunk cannot be configured as a loopback interface.

• After an Eth-Trunk is configured as a loopback interface, the Eth-Trunk supports only the following configurations: authentication open ucl-policy enable, description, enable snmp trap updown, jumboframe enable, mixed-rate link enable, qos phb marking enable, set flow-stat interval, shutdown, local-preference enable, statistic enable (interface view), traffic-policy (interface view), vcmp disable, and trust.

• Before disabling an Eth-Trunk interface from working as the multicast loopback interface, delete all member interfaces of the Eth-Trunk interface.
• If "Warning: ACL resources are insufficient when the physical interface is added to the multicast loopback interface, so the multicast VPN function may be abnormal." is displayed when you add a physical interface to a multicast loopback interface, resources on the multicast loopback interface are occupied by other services. To ensure normal running of services, delete this physical interface from the multicast loopback interface or delete unnecessary configurations, for example, unnecessary traffic policies.
• If an Eth-Trunk has been configured as a multicast VPN loopback interface, do not use the MIB to perform other service configuration on the Eth-Trunk. Otherwise, the multicast VPN loopback interface will become invalid or the service configuration issued by the MIB may not take effect.