Manual

[phone] www.qtech.ru
Москва, Новозаводская ул., 18, стр. 1
282
control(necessary)
the no operation of this command will globally
disable destination control. All of the other
configuration can only take effect after globally
enabled.
The next is configuring destination control rules, which are similar to that of source control, but
using ACL number from 9000 to 10099 instead.
Command
Explanation
Global Configuration Mode
[no] ipv6 access-list <9000-10099>
{deny|permit} {{<source/M>}|{host-source
<source-host-ip>}|any-source}
{{<destination/M>}|{host-destination
<destination-host-ip>}|any-destination}
Used to configure destination control rules,
these rules can only take effect when
applied to specified source IP, VLAN-MAC
or port. The no operation of this rule will
delete the specified rule.
The last step is to configure the rules to the specified source IP, source VLAN MAC or the
specified port. What should be paid attention to is that only when the MLD-SNOOPING is
enabled, these rules can be globally used, or, only rules of source IP can be used in MLD
protocol. The following is the configuration command:
Command
Explanation
Port Mode
[no] ipv6 multicast destination-control
access-group <9000-10099>
Used to configure the destination control
rule to a port, the no operation of this
command will cancel the configuration.
Global Configuration Mode
[no] ipv6 multicast destination-control <1-
4094> <macaddr> access-group <9000-
10099>
Used to configure the destination control
rules to the specified VLAN-MAC, the no
operation of this command will cancel the
configuration.
[no] ipv6 multicast destination-control
<IPADDRESS/M> access-group <9000-
100999>
Used to configure the destination control
rules to the specified source IPv6
address/MASK, the no operation of this
command will cancel the configuration.
The configuration of multicast policy
The multicast policy adopts the method of specifying a priority for the specified multicast data
to meet the user’s particular demand, what should be paid attention to is that only when
multicast data is transmitted in TRUNK, can it be taken special care of. The configuration is
quite simple, for only one command is needed, that is set priority for the specified multicast,
the following is the command: