mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}]
no mesh-sdp sdp-id[:vc-id]
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
This command binds a VPLS service to an existing SDP. Mesh SDPs bound to a service are logically treated like a single bridge ‟port” for flooded traffic, where flooded traffic received on any mesh SDP on the service is replicated to other ‟ports” (spoke SDPs and SAPs) and not transmitted on any mesh SDPs.
This command creates a binding between a service and an SDP. The SDP has an operational state that determines the operational state of the SDP within the service; for example, if the SDP is administratively or operationally down, the SDP for the service is down.
The SDP must already be defined in the config>service>sdp context to associate the SDP with a valid service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.
SDPs must be explicitly associated and bound to a service. If an SDP is not bound to a service, no far-end devices can participate in the service.
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected, only the binding of the SDP to a service. When removed, no packets are forwarded to the far-end router.
Several SDPs can be bound to a VPLS. Each SDP must be destined for a different router. If two sdp-id bindings terminate on the same router, an error occurs and the second SDP is binding is rejected.
Specifies the SDP identifier.
Specifies the virtual circuit identifier. This value is used to validate the VC ID portion of each mesh SDP binding defined in the service. The default value of this object is equal to the service ID.
Keyword that overrides the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15 bit-quantity containing a value which represents the type of VC. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. A change of the bindings VC type causes the binding to signal the new VC type to the far end when signaling is enabled. VC types are derived according to IETF draft-martini-l2circuit-trans-mpls.
The VC type value for Ethernet is 0x0005.
The VC type value for an Ethernet VLAN is 0x0004.
Keyword that defines the VC type as Ethernet. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined, the default is Ethernet for spoke-SDP bindings. Defining Ethernet is the same as executing no vc-type, and restores the default VC type for the spoke-SDP binding. (hex 5)
Defines the VC type as VLAN. The ethernet and vlan keywords are mutually exclusive. When the VC type is not defined, the default is Ethernet for mesh SDP bindings.
spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] [split-horizon-group group-name] [use-evpn-default-shg]
no spoke-sdp sdp-id[:vc-id]
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
This command binds a service to an existing Service Distribution Point (SDP). A spoke-SDP is treated like the equivalent of a traditional bridge ‟port” where flooded traffic received on the spoke-SDP is replicated on all other ‟ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port on which it was received.
The operational state of the SDP determines the SDP state within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.
The SDP must already exist in the config>service>sdp context before it can be associated with a VPLS service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id exists, a binding between the specific sdp-id and service is created.
SDPs must be explicitly associated and bound to a service to allow far-end devices to participate in the service.
The no form of this command removes the SDP binding from the service; the SDP configuration is not affected. When the SDP binding is removed, no packets are forwarded to the far-end router.
Several SDPs can be bound to a VPLS service. Each SDP must use unique vc-ids. An error message is generated if two SDP bindings with identical vc-ids terminate on the same router. Split horizon groups can be created only in the scope of a VPLS service.
Specifies the SDP identifier.
Specifies the virtual circuit identifier.
Mandatory keyword while creating a spoke-SDP.
Specifies the service endpoint to which this SDP bind is attached. The service ID of the SDP binding must match the service ID of the service endpoint.
Keyword to remove the association of a spoke-SDP with an explicit endpoint name.
Keyword to define the VC type as Ethernet. The ether and vlan keywords are mutually exclusive. When the VC type is not defined, the default is Ethernet for spoke-SDP bindings. Defining Ethernet is the same as executing no vc-type and restores the default VC type for the spoke-SDP binding. (hex 5)
Specifies the name of the split horizon group to which the SDP belongs.
Keyword that overrides the default VC type signaled for the spoke or mesh binding to the far end of the SDP. The VC type is a 15-bit quantity containing a value that represents the VC type. The actual signaling of the VC type depends on the signaling parameter defined for the SDP. If signaling is disabled, the vc-type command can still be used to define the dot1q value expected by the far-end provider equipment. If signaling is enabled, a change of the bindings VC type causes the binding to signal the new VC type to the far end.
VC types are derived in accordance with IETF draft-martini-l2circuit-trans-mpls.
The VC type value for Ethernet is 0x0005.
The VC type value for an Ethernet VLAN is 0x0004.
Keyword that defines the VC type as VLAN. The ether and vlan keywords are mutually exclusive. When the VC type is not defined then the default is Ethernet for spoke-SDP bindings. The VLAN VC-type requires at least one dot1q tag within each encapsulated Ethernet packet transmitted to the far end.
Keyword to add the spoke-SDP to the default SHG, which causes the spoke-SDP to behave as a mesh SDP. See Note: for more information.
This option is not blocked in a VPLS service, but it can be configured only for an EVPN-VPLS service. The default SHG is created when EVPN is enabled in the service, and all EVPN bindings are added to it by default.
Use this option only when the 7210 SAS-R6 or 7210 SAS-R12 is equipped with an IMM-c card. It is not required when the node is equipped with only an IMM-b card.
[no] control word
config>service>vpls>mesh-sdp
config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command enables the use of the control word on pseudowire packets in VPLS, and enables the use of the control word individually on each mesh SDP or spoke-SDP. By default, the control word is disabled. When the control word is enabled, all VPLS packets, including the BPDU frames, are encapsulated with the control word when sent over the pseudowire. The T-LDP control plane behavior is the same as in the implementation of control word for VLL services. The configuration for the two directions of the Ethernet pseudowire should match.
The no form of this command reverts the mesh SDP or spoke-SDP to the default value.
no control word
egress
config>service>vpls>mesh-sdp
config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command enables the egress SDP context.
ingress
config>service>vpls>mesh-sdp
config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command enables the ingress SDP context.
[no] vc-label vc-label
config>service>vpls>mesh-sdp>egress
config>service>vpls>spoke-sdp>egress
Supported on all 7210 SAS platforms as described in this document
This command configures the egress VC label.
Specifies a VC egress value that indicates a specific connection.
[no] vc-label vc-label
config>service>vpls>mesh-sdp>ingress
config>service>vpls>spoke-sdp>ingress
Supported on all 7210 SAS platforms as described in this document
This command configures the ingress VC label.
Specifies a VC ingress value that indicates a specific connection.
vlan-vc-tag vlan-id
no vlan-vc-tag [vlan-id]
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
Supported on all 7210 SAS platforms as described in this document
This command specifies an explicit dot1q value used when encapsulating to the SDP far end. When signaling is enabled between the near and far end, the configured dot1q tag can be overridden by a received TLV specifying the dot1q value expected by the far end. This signaled value must be stored as the remote signaled dot1q value for the binding. The provisioned local dot1q tag must be stored as the administrative dot1q value for the binding.
When the dot1q tag is not defined, the default value of zero is stored as the administrative dot1q value. Setting the value to zero is equivalent to not specifying the value.
The no form of this command disables the command.
no vlan-vc-tag
Specifies a valid VLAN identifier to bind an 802.1Q VLAN tag ID.
description description-string
no description
config>service>vpls>igmp-snooping>mvr
Supported on all 7210 SAS platforms as described in this document
This command configures a text description stored in the configuration file for a configuration context. The description command associates a text string with a configuration context to help identify the content in the configuration file.
The no form of this command removes the string from the configuration.
Specifies the description character string. Allowed values are any string up to 80 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.
[no] fast-leave
config>service>vpls>sap>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command enables fast leave. When IGMP fast leave processing is enabled, the system immediately removes a SAP from the multicast group if it detects an IGMP ‟leave” on that SAP. Fast leave processing allows the switch to remove a SAP that sends a ‟leave” message from the forwarding table without first sending out group-specific queries to the SAP, and therefore speeds up the process of changing channels (known as ‟zapping”).
Fast leave should be enabled only when there is a single receiver present on the SAP. When fast leave is enabled, the configured last-member-query-interval value is ignored.
no fast-leave
from-vpls service-id
no from-vpls
config>service>vpls>sap>igmp-snooping>mvr
Supported on all 7210 SAS platforms as described in this document
This command configures the VPLS and RVPLS service from which multicast traffic is copied upon receipt of an IGMP join request. IGMP snooping must be enabled on the MVR VPLS and MVR RVPLS service.
no from-vpls
Specifies the MVR VPLS from which multicast channels should be copied into this SAP.
[no] group grp-address
config>service>vpls>sap>igmp-snooping>static
config>service>vpls>spoke-sdp>snooping>static
config>service>vpls>mesh-sdp>snooping>static
Supported on all 7210 SAS platforms as described in this document
This command adds a static multicast group as a (*, g). When a static IGMP group is added, multicast data for that (*,g) is forwarded to the specific SAP or SDP without receiving a membership report from a host.
Specifies an IGMP multicast group address that receives data on an interface. The IP address must be unique for each static group.
group-policy policy-name
no group-policy
config>service>vpls>igmp-snooping>mvr
Supported on all 7210 SAS platforms as described in this document
This command identifies a filter policy for multicast groups applied to this VPLS entity. The sources of the multicast traffic must be members of the VPLS.
The no form of this command removes the policy association from the VPLS configuration.
Specifies the group policy name. Allowed values are any string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. Routing policies are configured in the config>router>policy-options context. The router policy must be defined before it can be imported.
hash-label [signal-capability]
no hash-label
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
Supported on all 7210 SAS platforms as described in this document
This command enables the use of the hash label on a VLL or VPLS service bound to LDP or RSVP SDP using the autobind mode with the ldp, rsvp-te, or mpls options. When this feature is enabled, the ingress datapath is modified so that the result of the hash on the packet header is communicated to the egress datapath for use as the value of the label field of the hash label. The egress datapath appends the hash label at the bottom of the stack (BoS) and sets the S-bit to one (1).
Packets generated in CPM and that are forwarded labeled within the context of a service (for example, OAM packets) must also include a hash label at the BoS and set the S-bit accordingly.
The TTL of the hash label is set to a value of 0.
Enable the signaling of the hash-label capability under a VLL spoke-sdp, a VPLS spoke-sdp or mesh-sdp interface by adding the signal-capability option. In this case, the decision whether to insert the hash label on the user and control plane packets by the local PE is solely determined by the outcome of the signaling process and can override the local PE configuration. The following apply when the hash-label option and the signal-capability option are enabled on the local PE.
The 7210 local PE inserts the Flow Label Interface Parameters sub-TLV with T=1 and R=1 in the PW ID FEC element in the label mapping message for that spoke-sdp or mesh-sdp.
If the remote PE does not send the Flow Label sub-TLV in the PW ID FEC element, or sends a Flow Label sub-TLV in the PW ID FEC element with T=FALSE and R=FALSE, the local node disables the hash label capability. Therefore, the local PE node does not insert a hash label in user and control plane packets that it forwards on the spoke-sdp or mesh-sdp. It also drops user and control plane packets received from a remote PE if they include a hash label. The latter case may be caused by a remote 7210 PE that does not support the hash-label option, or that has the hash-label option enabled but does not support the signal-capability option, or does support both options but the user did not enable them.
If the remote PE sends Flow Label sub-TLV in the PW ID FEC element with T=TRUE and R=TRUE, the local PE enables the hash label capability. Therefore, the local PE inserts a hash label in user and control plane packets that it forwards on the spoke-sdp or mesh-sdp. It also accepts user and control plane packets remote PE with or without a hash label.
If the hash-labeloption was enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the pseudowire packets received by the local PE will have the hash label included. These packets must be dropped. Solve this by disabling the signaling capability option on the local node, which will result in the insertion of the hash label by both PE nodes.
If the hash-label option is not supported or was not enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the pseudowire received by the local PE will not have the hash label included.
The user can enable or disable the signal-capability option in CLI as needed. When doing so, the router must withdraw the label it sent to its peer and send a new label mapping message with the new value of the F bit in the flow label interface parameters sub-TLV of the PW ID FEC element.
This feature is supported only for VLL and VPLS services. It not supported for VPRN services. It is also not supported on multicast packets forwarded using RSVP P2MP LPS or mLDP LSP in both the base router instance and in the multicast VPN (mVPN) instance.
In 7x50 and possibly other vendor implementations, to allow applications where the egress LER infers the presence of the hash label implicitly from the value of the label, the Most Significant Bit (MSB) of the result of the hash is set before copying into the Hash Label. This means that the value of the hash label always in the range [524,288 to 1,048,575] and does not overlap with the signaled/static LSP and signaled/static service label ranges. This also guarantees that the hash label does not match a value in the reserved label range. This is not supported on 7210 SAS for service traffic (for MPLS OAM traffic the MSB bit is set). That is, 7210 SAS devices do not set the MSB bit in the hash label value for service traffic. Therefore, users must ensure that both ends are correctly configured to process hash labels or disable the feature.
The no form of this command disables the use of the hash label.
no hash-label
Keyword to enable the signaling and negotiation of the use of the hash label between the local and remote PE nodes.
igmp-snooping
config>service>vpls
config>service>vpls>sap
config>service>vpls>spoke-sdp
config>service>vpls>mesh-sdp
config>service>pw-template
Supported on all 7210 SAS platforms as described in this document
This command enables the Internet Group Management Protocol (IGMP) snooping context.
import policy-name
no import
config>service>vpls>sap>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config> service>vpls> mesh-sdp>igmp-snooping
config>service>pw-template>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command specifies the import routing policy for IGMP packets to be used on this SAP or SDP. Only a single policy can be imported on a single SAP or SDP at any time.
The no form of this command removes the policy association from the SAP or SDP.
no import
Specifies the import policy name. Values can be string up to 32 characters composed of printable, 7-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes. These policies are configured in the config>router>policy-options context. The router policy must be defined before it can be imported.
last-member-query-interval tenths-of-seconds
no last-member-query-interval
config>service>vpls>sap>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config>service>vpls>mesh-sdp>igmp-snooping
config>service>pw-template>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command configures the maximum response time used in group-specific queries sent in response to ‟leave” messages, and is also the amount of time between 2 consecutive group-specific queries. This value may be tuned to modify the leave latency of the network. A reduced value results in reduced time to detect the loss of the last member of a group. The configured last-member-query-interval is ignored when the fast-leave command is enabled on the SAP or SDP.
last-member-query-interval 10
Specifies the frequency, in tenths of seconds, at which query messages are sent.
max-num-groups count
no max-num-groups
config>service>vpls>sap>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config>service>vpls>mesh-sdp>igmp-snooping
config>service>pw-template>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command defines the maximum number of multicast groups that can be joined on this SAP or SDP. If the node receives an IGMP join message that would exceed the configured number of groups, the request is ignored.
no max-num-groups
Specifies the maximum number of groups that can be joined on this SAP.
max-num-sources max-num-sources
no max-num-sources
config>service>vpls>sap>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command defines the maximum number of multicast sources allowed per group that can be joined on this SAP. If the node receives an IGMP join message that would exceed the configured number of sources, the request is ignored.
The no form of this command disables checking the number of sources.
no max-num-sources
Specifies the maximum number of multicast sources per group that can be joined on this SAP.
[no] mrouter-port
config>service>vpls>sap>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config>service>vpls>mesh-sdp>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command specifies whether a multicast router is attached behind this SAP.
Configuring a SAP or SDP as an mrouter-port has a dual effect. Firstly, all multicast traffic received on another SAP or SDP is copied to this SAP or SDP. Secondly, IGMP reports generated by the system as a result of someone joining or leaving a multicast group are sent to this SAP or SDP.
If two multicast routers exist in the network, one of them becomes the active querier. While the other multicast router (non-querier) stops sending IGMP queries, it should still receive reports to keep its multicast trees up to date. To support this, the mrouter-port should be enabled on all SAPs or SDPs connecting to a multicast router.
The IGMP version to be used for the reports (v1 or v2) is only determined after an initial query is received. Until the IGMP version is determined, no reports are sent on the SAP or SDP, even if mrouter-port is enabled.
If the send-queries command is enabled on this SAP or SDP, the mrouter-port command cannot be enabled.
no mrouter-port
mvr
config>service>vpls>igmp-snooping
config>service>vpls>sap>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure Multicast VPLS Registration (MVR) parameters.
query-interval seconds
no query-interval
config>service>vpls>igmp-snooping
config>service>vpls>sap>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config>service>vpls>mesh-sdp>igmp-snooping config>service>pw-template>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command configures the IGMP query interval. If the send-queries command is enabled, this parameter specifies the interval between two consecutive general queries sent by the system on this SAP or SDP. The configured query-interval must be greater than the configured query-response-interval. If send-queries is not enabled on this SAP or SDP, the configured query-interval value is ignored.
125
Specifies the time interval, in seconds, that the router transmits general host-query messages.
query-src-ip ip-address
no query-src-ip
config>service>vpls>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command configures the IP source address used in IGMP queries.
query-response-interval seconds
config>service>vpls>sap>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config>service>vpls>mesh-sdp>igmp-snooping config>service>pw-template>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command configures the IGMP query response interval. If the send-queries command is enabled, this parameter specifies the maximum response time advertised in IGMP queries.
The configured query-response-interval must be smaller than the configured query-interval.
If send-queries is not enabled on this SAP or SDP, the configured query-response-interval value is ignored.
query-response-interval 10
Specifies the length of time to wait to receive a response to the host-query message from the host.
report-src-ip ip-address
no report-src-ip
config>service>vpls>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command specifies the source IP address used when generating IGMP reports. According the IGMPv3 standard, a zero source address is allowed in sending IGMP reports. However, for interoperability with some multicast routers, the source IP address of IGMP group reports can be configured using this command.
report-src-ip 0.0.0.0
Specifies the source IP source address in transmitted IGMP reports.
robust-count robust-count
no robust-count
config>service>vpls>igmp-snooping
config>service>vpls>sap>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config>service>vpls>mesh-sdp>igmp-snooping config>service>pw-template>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command configures tuning for the expected packet loss on a SAP or SDP, and is comparable to a retry count. This command is functional for a SAP or SDP if the send-queries command is enabled. If the send-queries command is not enabled, the robust-count command is ignored. If this SAP or SDP is expected to experience packet loss (called ‟lossy”), the value of the robust-count parameter may be increased. IGMP snooping on this SAP or SDP is robust up to robust-count minus 1 packet losses.
robust-count 2
Specifies the robust count for the SAP or SDP.
precedence precedence-value | primary
no precedence
config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command configures the spoke-SDP precedence.
precedence 4
Specifies the spoke-SDP precedence.
Specifies that the precedence is primary.
[no] propagate-mac-flush
config>service>vpls
Supported on all 7210 SAS platforms as described in this document
This command specifies whether MAC flush messages received from the specific LDP are propagated to all spoke and mesh SDPs within the context of this VPLS service. The propagation follows the split-horizon principle and any datapath blocking to avoid the looping of these messages.
no propagate-mac-flush
[no] send-queries
config>service>vpls>sap>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config>service>vpls>mesh-sdp>igmp-snooping config>service>pw-template>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command specifies whether to send IGMP general query messages on the SAP or SDP.
When the send-queries command is configured, all query reports generated locally are of the type belonging to the configured version. If a report of a version higher than the configured version is received, the report is dropped and a new counter to track the wrong version is incremented. If send-queries is not configured, the version command has no effect. The version used is the version of the querier.
no send-queries
static
config>service>vpls>sap>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config>service>vpls>mesh-sdp>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
Commands in this context configure static group addresses. Static group addresses can be configured on a SAP or SDP. When present either as a (*, g) entry, multicast packets matching the configuration are forwarded even if no join message was registered for the specific group.
[no] group grp-address
config>service>vpls>sap>igmp-snooping>static
config>service>vpls>spoke-sdp>snooping>static
config>service>vpls>mesh-sdp>snooping>static
Supported on all 7210 SAS platforms as described in this document
This command adds a static multicast group either as a (*, g) or as one or more (s,g) records. When a static IGMP group is added, multicast data for that (*,g) or (s,g) is forwarded to the specific SAP or SDP without receiving a membership report from a host.
Specifies an IGMP multicast group address that receives data on an interface. The IP address must be unique for each static group.
source ip-address
no source ip-address
config>service>vpls>sap>igmp-snooping>static>group
Supported on all 7210 SAS platforms as described in this document
This command adds a static (s,g) entry to allow multicast traffic for the corresponding multicast group from the specified source.
The no form of this command removes the source entry from the configuration.
no source
[no] starg
config>service>vpls>sap>igmp-snooping>static>group
config>service>vpls>spoke-sdp>igmp-snooping>static>group
config>service>vpls>mesh-sdp>igmp-snooping>static>group
Supported on all 7210 SAS platforms as described in this document
This command adds a static (*,g) entry to allow multicast traffic for the corresponding multicast group from any source. This command can be enabled only if no existing source addresses for this group are specified.
The no form of this command removes the starg entry from the configuration.
no starg
version version
no version
config>service>vpls>sap>igmp-snooping
config>service>vpls>mesh-sdp>igmp-snooping
config>service>vpls>spoke-sdp>igmp-snooping
config>service>pw-template>igmp-snooping
Supported on all 7210 SAS platforms as described in this document
This command specifies the version of IGMP that is running on this SAP or SDP. This object can be used to configure a router capable of running either value. For IGMP to function correctly, all routers on a LAN must be configured to run the same version of IGMP.
When the send-query command is configured, all query types generated locally are of the configured version. If a report of a version higher than the configured version is received, the report gets dropped and a new counter is incremented to track the wrong version.
If the send-query command is not configured, the version command has no effect. The version used on that SAP is the version of the querier.
Specifies the IGMP version.
to-sap sap-id
no to-sap
config>service>vpls>sap>igmp-snooping>mvr
Supported on all 7210 SAS platforms as described in this document
This command configures the SAP to which the multicast data needs to be copied.
In some scenarios, the multicast traffic should not be copied from the MVR VPLS or MVR RVPLS to the SAP on which the IGMP message was received (standard MVR behavior) but to another SAP.
no to-sap
Specifies the SAP to which multicast channels should be copied.