Virtual Private LAN Services
Page 694 7750 SR OS Services Guide
secondary-shaper
secondary-shaper secondary-shaper-name
no secondary-shaper
Context config>service>vpls>sap>egress>hsmda-queue-over
Description This command configures an HSMDA secondary shaper. Note that an shaper override can only be
configured on an HSMDA SAP.
Parameters secondary-shaper-name — Specifies a secondary shaper name up to 32 characters in length.
multicast-group
Syntax multicast-group group-name
no multicast-group
Context config>service>vpls>sap>egress
Description This command places a VPLS Ethernet SAP into an egress multicast group. The SAP must comply
with the egress multicast group’s common requirements for member SAPs. If the SAP does not
comply, the command will fail and the SAP will not be a member of the group. Common
requirements for an egress multicast group are listed below:
• If an egress-filter is specified on the egress multicast group, the SAP must have the same egress
filter applied.
• If an egress-filter is not defined on the egress multicast group, the SAP cannot have an egress fil-
ter applied.
• If the egress multicast group has an encap-type set to null, the SAP must be defined on a port
with the port encapsulation type set to null.
• If the egress multicast group has an encap-type set to dot1q, the SAP must be defined on a port
with the port encapsulation type set to dot1q and the port’s dot1q-etype must match the dot1q-
etype defined on the egress multicast group.
• The access port the SAP is created on cannot currently be an egress mirror source.
Once a SAP is a member of an egress multicast group, the following rules apply:
• The egress filter defined on the SAP cannot be removed or modified. Egress filtering is managed
at the egress multicast group for member SAPs.
• If the encapsulation type for the access port the SAP is created on is set to dot1q, the port’s dot1q-
etype value cannot be changed.
• Attempting to define an access port with a SAP that is currently defined in an egress multicast
group as an egress mirror source will fail.
Once a SAP is included in an egress multicast group, it is then eligible for efficient multicast
replication if the egress forwarding plane performing replication for the SAP is capable. If the SAP is
defined as a Link Aggregation Group (LAG) SAP, it is possible that some links in the LAG are on
forwarding planes that support efficient multicast replication while others are not. The fact that some
or all the forwarding planes associated with the SAP cannot perform efficient multicast replication
does not affect the ability to place the SAP into an Egress multicast group.
To Next Page
Loading...
