Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Configuring Multicast Groups for MLD

    You can configure various attributes related to MLD multicast groups. This topic describes how to configure multicast group attributes.

    Note: You can configure MLD only on IPv6 interfaces. For information about configuring IPv6 interfaces, see Configuring IPv6 in the JunosE IP, IPv6, and IGP Configuration Guide.

    Specifying MLD Multicast Groups

    You can use a standard IPv6 access list to specify the multicast groups that a host can join.

    To restrict the host to join only the groups permitted by the IPv6 access list:

    • Restrict hosts on this subnetwork to join only multicast groups on the specified IPv6 access list. The access list is queried whenever the router receives an MLDv1 report requesting membership of a group and MLDv2 ChangeToInclude, IsInclude, ChangeToExclude, or IsExclude reports. The request is ignored if the access list query fails. The ipv6 mld access-group command uses IPv6 access lists, which allow both source and destination/group addresses to be specified. You must set the source address to any.
      host1:boston(config-if)#ipv6 mld access-group boston-list

      Use the no version to dissociate the interface from an access list and to allow hosts on the interface to join any multicast group.

      Note: As an alternative method, you can restrict the hosts using the MLD-Access-Name RADIUS attribute (VSA 26-74) in RADIUS Access-Accept messages. The radius ignore command is used to ignore or accept RADIUS attributes from Access-Accept messages.

    • Restrict hosts on this subnetwork to membership only in (S,G) pairs (also known as channels) permitted by the specified IPv6 access list. When configured, both source and group addresses query the associated access list whenever the router receives an MLDv2 report requesting membership of the (S,G) pairs (that is, the router receives an MLDv2 ChangeToInclude, IsInclude, or AllowNewSource group report). The request is ignored if the access list query fails. The ipv6 mld access-source-group command uses IPv6 access lists, which allow both source and destination group addresses to be specified.
      host1:boston(config-if)#ipv6 mld access-source-group dallas-list

      Use the no version to remove any access list restriction.

      Note: As an alternative method, you can restrict the hosts using the MLD-Access-Src-Name RADIUS attribute (VSA 26-75) in RADIUS Access-Accept messages. The radius ignore command is used to ignore or accept RADIUS attributes from Access-Accept messages.

    Assigning an MLD Multicast Group to an Interface

    You can assign an interface to send and receive all traffic for a particular multicast group. This feature allows you to control MLD traffic and to test the behavior of multicast protocols in the network.

    To send and receive all traffic for a multicast group from the interface:

    • Issue the ipv6 mld static-group command in Interface Configuration mode. The interface sets no timers for this group.
      host1:boston(config-if)#ipv6 mld static-group ff0e::1

      Use the no version to remove the group from the interface.

    Configuring MLD Group Outgoing Interface Mapping

    You can configure an MLD protocol interface to use a different OIF for multicast-data-forwarding by applying an OIF map. When you configure an OIF map on an MLD protocol interface, the map is applied to all MLD membership requests that the interface receives. To configure OIF mapping on an interface, you first create the OIF map using the ipv6 mld oif-map command and then apply that map to an interface with the ipv6 mld apply-oif-map command.

    To properly configure an interface used in the OIF map for multicast-data-forwarding capability, you must configure the interface version as passive with the ipv6 mld version command. You can either specify a passive interface as the OIF or specify the OIF as self (to use the MLD protocol interface as the OIF) in the ipv6 mld oif-map command.

    To configure group outgoing interface mapping:

    1. Create an OIF map.
      host1(config)#ipv6 mld oif-map OIFMAP atm 3/0.1 ff0e::1:1/128 2001::1:1/128 host1(config)#ipv6 mld oif-map OIFMAP atm 3/0.2 ff0e::1:1/128 2001::1:1/128 host1(config)#ipv6 mld oif-map OIFMAP atm 3/0.3 ff0e::1:1/128 host1(config)#ipv6 mld oif-map OIFMAP atm 3/0.4 ff0e::1:0/112 2001::1:1/128 host1(config)#ipv6 mld oif-map OIFMAP atm 3/0.5 ff0e::1:0/112 2001::1:1/128 host1(config)#ipv6 mld oif-map OIFMAP self ::/0 2001::1:0/112

      Use the no version to remove an outgoing interface map attribute.

      Note: As an alternative method, you can create the OIF map using the MLD-OIF-Map-Name RADIUS attribute (VSA 26-76) in RADIUS Access-Accept messages. The radius ignore command is used to ignore or accept RADIUS attributes from Access-Accept messages.

    2. Apply the created OIF map to the current interface.
      host1(config-subif)#ipv6 mld apply-oif-map OIFMAP

      Use the no version to remove the outgoing interface map association from the interface.

    3. Configure the MLD version for the interface as passive with only multicast-data-forwarding capability.
      host1:dallas(config-if)#ipv6 mld version passive

      Use the no version to set the version to the default, MLDv2.

      Note: As an alternative method, you can configure the MLD version using the MLD-Version RADIUS attribute (VSA 26-77) in RADIUS Access-Accept messages. The radius ignore command is used to ignore or accept RADIUS attributes from Access-Accept messages.

    Published: 2014-08-19