5.8. VPLS Services Command Reference

This command administratively disables an entity. When disabled, an entity does not change, reset, or remove any configuration settings or statistics.

The operational state of the entity is disabled as well as the operational state of any entities contained within. Many objects must be shut down before they may be deleted.

Services are created in the administratively down (shutdown) state. When a no shutdown command is entered, the service becomes administratively up and then tries to enter the operationally up state. Default administrative states for services and service entities is described as follows in Special Cases.

The no form of this command places the entity into an administratively enabled state.

This command creates 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.

This command enables the context to configure DHCP parameters.

This command enables DHCP Option 82 (Relay Agent Information Option) parameter processing and enters the context for configuring Option 82 suboptions.

The no form of this command reverts to the default value.

This command configures the Relay Agent Information Option (Option 82) processing.

By default, existing information is kept intact.

The no form of this command reverts to the default value.

When enabled, the router sends an ASCII-encoded tuple in the circuit-id suboption of the DHCP packet. This ASCII-tuple consists of the access-node-identifier, service-id, and SAP-ID, separated by “|”.

To send a tuple in the circuit ID, the action replace command must be configured in the same context.

If disabled, the circuit-id suboption of the DHCP packet is left empty.

The no form of this command reverts to the default value.

This command specifies that information that goes into the remote ID suboption in the DHCP relay packet.

If disabled, the remote-id suboption of the DHCP packet is left empty.

The no form of this command reverts to the default value.

This command configures the vendor-specific suboption of the DHCP relay packet.

This command enables the sending of the MAC address in the vendor-specific suboption of the DHCP relay packet.

The no form of this command disables the sending of the MAC address in the vendor-specific suboption of the DHCP relay packet.

This command enables the sending of the SAP ID in the vendor-specific suboption of the DHCP relay packet.

The no form of this command disables the sending of the SAP ID in the vendor-specific suboption of the DHCP relay packet.

This command enables the sending of the service ID in the vendor-specific suboption of the DHCP relay packet.

The no form of this command disables the sending of the service ID in the vendor-specific suboption of the DHCP relay packet.

This command specifies the string in the vendor-specific suboption of the DHCP relay packet.

The no form of this command reverts to the default value.

This command specifies whether the system ID is encoded in the vendor-specific suboption of Option 82.

This command enables DHCP snooping for DHCP messages on the SAP. Enabling DHCP snooping on VPLS interfaces (SAPs) is required for DHCP messages where Option 82 information is to be inserted. This includes interfaces in the path to receive messages from either DHCP servers or from subscribers.

The no form of this command disables DHCP snooping on the specified VPLS SAP.

This command creates or edits a Virtual Private LAN Services (VPLS) instance. The vpls command is used to create or maintain a VPLS service. If the service-id does not exist, a context for the service is created. If the service-id exists, the context for editing the service is entered.

A VPLS service connects multiple customer sites together acting like a zero-hop, Layer 2 switched domain. A VPLS is always a logical full mesh.

When a service is created, the create keyword must be specified if the create command is enabled in the environment context. When a service is created, the customer keyword and customer-id must be specified and must associate the service with a customer. The customer-id must already exist having been created using the customer command in the service context. When a service has been created with a customer association, it is not possible to edit the customer association. The service must be deleted and recreated with a new customer association.

When a service is created, the use of the customer customer-id is optional for navigating into the service configuration context. Attempting to edit a service with the incorrect customer-id specified results in an error.

More than one VPLS service may be created for a single customer ID.

By default, no VPLS instances exist until they are explicitly created.

The no form of this command deletes the VPLS service instance with the specified service-id. The service cannot be deleted until all SAPs defined within the service ID have been shutdown and deleted, and the service has been shut down.

This command enables the context to configure the BGP related parameters to BGP AD.

This command enables blocking after all configured SDPs or endpoints are in operationally down state.

Blocking brings the entity to an operationally down state. This event is signaled to corresponding T-LDP peer by withdrawing the service label (status-bit-signaling non-capable peer) or by setting “PW not forwarding” status bit in T-LDP message (status-bit-signaling capable peer).

This command enables the translation of bridge protocol data units (BPDUs) to a specific format, meaning that all BPDUs transmitted on a specific SAP or spoke-SDP will have a specified format.

The no form of this command reverts to the default value.

This command enables Layer 2 Protocol Tunneling (L2PT) termination on a specific SAP. L2PT termination is supported for STP, CDP, DTP, PAGP, UDLD, and VTP PDUs.

This command can be enabled only if STP is disabled in the context of the specific VPLS service.

This command disables MAC address aging across a VPLS service or on a VPLS service SAP.

Similar to a Layer 2 switch, learned MACs can be aged out if no packets are sourced from the MAC address for a period of time (the aging time). In a VPLS service instance, the local age timer is applicable to both the local learned and remote learned MAC entries in the VPLS forwarding database (FDB). The disable-aging command at the service level turns off aging for local and remote learned MAC addresses.

When no disable-aging is specified for a VPLS, it is possible to disable aging for specific SAPs by entering the disable-aging command at the appropriate level.

When the disable-aging command is entered at the VPLS level, the disable-aging state of individual SAPs is ignored.

The no form of this command enables aging on the VPLS service.

This command disables learning of new MAC addresses in the VPLS FDB for the service instance.

When disable-learning is enabled, new source MAC addresses are be entered in the VPLS service forwarding database.

When disable-learning is disabled, new source MAC addresses are learned and entered into the VPLS forwarding database.

This command is mainly used in conjunction with the discard-unknown command.

The no form of this command enables learning of MAC addresses.

This command enables, at the VPLS level, packets with unknown destination MAC address to be dropped instead of flooded (even when configured FIB size limits for VPLS or SAP are not yet reached). By default, packets with unknown destination MAC addresses are flooded.

The no form of this command allows flooding of packets with unknown destination MAC addresses in the VPLS.

This command configures a service endpoint.

This command creates a text description stored in the configuration file for a configuration context.

This 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.

When this command is enabled, the node ignores the standby-bit received from TLDP peers for the specific spoke-SDP and performs internal tasks without taking it into account.

This command is available at the endpoint level and the spoke-SDP level. If the spoke-SDP is part of the explicit endpoint, it is not possible to change this setting at the spoke-SDP level. The existing spoke-SDP will become part of the explicit endpoint only if the setting is not conflicting. The newly created spoke-SDP, which is part of the specific explicit endpoint, inherits this setting from the endpoint configuration.

This command creates a split-horizon group (SHG) for the VPLS instance. Traffic arriving on a SAP or spoke-SDP within this SHG is not copied to other SAPs or spoke-SDPs in the same SHG.

An SHG must be created before SAPs and spoke-SDPs can be assigned to the group. The SHG is defined within the context of a single VPLS instance. The same group name can be reused in different VPLS instances.

Note: Service-based SHGs are not supported in an R-VPLS service.

The no form of this command removes the group name from the configuration.

This command specifies the value to send logs and traps when the threshold is reached.

This command specifies the value to send logs and traps when the threshold is reached.

This command specifies the maximum number of MAC entries in the FDB for the VPLS instance on this node.

This command specifies the maximum number of forwarding database entries for both learned and static MAC addresses for the VPLS instance.

The no form of this command reverts the table size to the default value.

This command configures BGP auto-discovery.

This command configures the VPLS ID component that will be signaled in one of the extended community attributes (ext-comm). Values and format (6 bytes, other 2 bytes of type-subtype will be automatically generated).

This command specifies the name of the VSI export policies to be used for BGP auto-discovery, when this command is configured in the VPLS service. If multiple policy names are configured, the policies are evaluated in the order they are specified. The first policy that matches is applied.

The policy name list is handled by the SNMP agent as a single entity.

This command specifies the name of the VSI import policies used for BGP auto-discovery, when this command is configured in the VPLS service. If multiple policy names are configured, the policies are evaluated in the order they are specified. The first policy that matches is applied.The policy name list is handled by the SNMP agent as a single entity.

This command configures the route target (RT) component that is signaled in the related MPBGP attribute to be used for BGP auto-discovery, when this command is configured in the VPLS service.

If this command is not used, the RT is built automatically using the VPLS ID. The ext-comm can have the same two formats as the VPLS ID, a two-octet AS-specific extended community, IPv4 specific extended community.

The following rules apply.

This command binds the advertisements received with the RT that matches the configured list (either the generic or the specified import) to a specific pw-template. If the RT list is not present, the pw-template is used for all of them.

This command applies to BGP-AD, if this feature is configured in the VPLS service.

The tools perform commands can be used to control the application of changes in pw-template for BGP-AD.

The no form of this command removes the values from the configuration.

This command configures the aging time for locally learned MAC addresses in the FDB for the VPLS instance.

In a VPLS service, MAC addresses are associated with a SAP. MACs associated with a SAP are classified as local MACs, and MACs associated with are remote MACs QinQ / access uplink SAPs.

Similar to a Layer 2 switch, learned MACs can be aged out if no packets are sourced from the MAC address for a period of time (the aging time). The local-age timer specifies the aging time for local learned MAC addresses.

The no form of this command reverts the local aging timer to the default value.

This command enables the context to configure MAC move attributes. A sustained high relearn rate can be a sign of a loop somewhere in the VPLS topology. Typically, STP detects loops in the topology, but for those networks that do not run STP, the mac-move command is an alternative way to protect your network against loops.

When enabled in a VPLS, mac-move monitors the relearn rate of each MAC. If the rate exceeds the configured maximum allowed limit, it disables the SAP where the source MAC was last seen. The SAP can be disabled permanently (until a shutdown/no shutdown command is executed) or for a length of time that grows linearly with the number of times the specific SAP was disabled. You have the option of marking a SAP as non-blockable using the config>service>vpls>sap>limit-mac-move context. This means that when the relearn rate has exceeded the limit, another (blockable) SAP will be disabled instead.

The mac-move command enables the feature at the service level for SAPs, because only those objects can be blocked by this feature.

The operation of this feature is the same on the SAP; for example, if a MAC address moves from SAP to SAP, one will be blocked to prevent thrashing.

The mac-move command disables a VPLS port when the number of relearns detected has reached the number of relearns needed to reach the move-frequency in the 5-second interval; for example, when the move-frequency is configured to 1 (relearn per second) mac-move disables one of the VPLS ports when 5 relearns were detected during the 5-second interval because the average move-frequency of 1 relearn per second has been reached. This can already occur in the first second if the real relearn rate is 5 relearns per second or higher.

The no form of this command disables MAC move.

This command configures the maximum rate at which MACs can be relearned in the VPLS service, before the SAP where the moving MAC was last seen is automatically disabled to protect the system against undetected loops or duplicate MACs.

The no form of this command reverts to the default value.

This command configures the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is reenabled.

It is recommended that the retry-timeout value be larger than or equal to 5s * cumulative factor of the highest priority port, so that the sequential order of port blocking is not disturbed by reinitializing lower priority ports.

A value of zero indicates that the SAP will not be automatically reenabled after being disabled. If, after the SAP is reenabled it is disabled again, the effective retry timeout is doubled to avoid thrashing.

The no form of this command reverts to the default value.

This command specifies the multicast FIB (MFIB) high watermark. When the percentage filling level of the MFIB exceeds the configured value, a trap is generated and a log entry is added.

This command specifies the MFIB low watermark. When the percentage filling level of the MFIB drops below the configured value, the corresponding trap is cleared and a log entry is added.

This command specifies the maximum number of (s,g) entries in the MFIB for this VPLS instance.

The table-size parameter specifies the maximum number of multicast database entries for both learned and static multicast addresses for the VPLS instance. When a table-size limit is set on the MFIB of a service that is lower than the current number of dynamic entries present in the MFIB, the number of entries remains above the limit.

The no form of this command removes the configured maximum MFIB table size.

This command configures the aging time for remotely learned MAC addresses in the FDB for the VPLS instance. In a VPLS service, MAC addresses are associated with a SAP. MACs associated with a SAP are classified as local MACs.

Similar to a Layer 2 switch, learned MACs can be aged out if no packets are sourced from the MAC address for a period of time (the aging time). In each VPLS service instance, there are independent aging timers for local learned MAC and remote learned MAC entries in the FDB. The remote-age timer specifies the aging time for remote learned MAC addresses. To reduce the amount of signaling required between switches, configure this timer value larger than the local-age timer.

The no form of this command reverts the remote aging timer to the default value.

This command enables sending out “flush-all-from-ME” messages to all LDP peers included in the affected VPLS, in the event of physical port failures or “oper-down” events of individual SAPs.

This feature provides an LDP-based mechanism for recovering a physical link failure in a dual-homed connection to a VPLS service. This method provides an alternative to RSTP solutions where dual homing redundancy and recovery, in the case of link failure, is resolved by RSTP running between a PE router and CE devices. If the endpoint is configured within the VPLS and the send-flush-on-failure command is enabled, “flush-all-from-ME” messages are sent out only when all spoke-SDPs associated with the endpoint go down.

This feature cannot be enabled on management VPLS.

This command configures the service payload Maximum Transmission Unit (MTU), in bytes, for the service. This MTU value overrides the service-type default MTU. The service-mtu command defines the payload capabilities of the service. It is used by the system to validate the SAP and SDP binding operational state within the service.

The service MTU and a SAP service delineation encapsulation overhead (that is, 4 bytes for a dot1q tag) is used to derive the required MTU of the physical port or channel on which the SAP was created. If the required payload is larger than the port or channel MTU, the SAP is placed in an inoperative state. If the required MTU is equal to or less than the port or channel MTU, the SAP is able to transition to the operative state.

In the event that a service MTU, port or channel MTU, or path MTU is dynamically or administratively modified, all associated SAP and SDP binding operational states are automatically reevaluated.

The no form of this command reverts the default service-mtu for the indicated service type to the default value.

Note: To disable the service MTU check, execute the no service-mtu-check command. Disabling service MTU check allows the packets to pass to the egress if the packet length is less than or equal to the MTU configured on the port.

This command specifies whether this port is allowed to become an STP root port. It corresponds to the restrictedRole parameter in 802.1Q. If set, it can cause lack of spanning tree connectivity.

This command applies a time-based policy (filter or QoS policy) to the service SAP. The suite name must already exist in the config>cron context.

This command enables the context to configure the Virtual Switch Instance Identifier (VSI-ID).

This command specifies the low-order 4 bytes used to compose the VSI-ID to use for NLRI in BGP auto-discovery in this VPLS service.

If no value is set, the system IP address IS used.

This command configures an optional service name, up to 64 characters, that adds a name identifier to a specific service to then use that service name in configuration references and in show commands throughout the system. This helps service providers and administrators identify and manage services.

All services are required to assign a service ID to initially create a service. However, either the service ID or the service name can be used to identify and reference a specific service when it is initially created.

This command sets a flag on the VPLS service that enables the ability to attach an IP interface to the VPLS service to make the VPLS service routable. When the allow-ip-int-bind command is not enabled, the VPLS service cannot be attached to an IP interface.

On the 7210 SAS-D, 7210 SAS-Dxp, and 7210 SAS-K 2F1C2T, the VPLS can be bound to only an IES IP interface. On the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C, the VPLS can be bound to an IES or VPRN IP interface. Only IPv4 addressing and forwarding is supported in the R-VPLS context.

When attempting to set the allow-ip-int-bind VPLS flag, the system first checks to see if the correct configuration constraints exist for the VPLS service and the network ports. In Release 5.0 the following VPLS features must be disabled or not configured to set the allow-ip-int-bind flag:

When the VPLS allow-ip-int-bind flag is set on a VPLS service, the preceding features cannot be enabled on the VPLS service.

When a service name is applied to a VPLS service and that service name is also bound to an IP interface but the allow-ip-int-bind flag has not been set on the VPLS service context, the system attempt to resolve the service name between the VPLS service and the IP interface fails.

After the allow-ip-int-bind flag is successfully set on the VPLS service, either the service name on the VPLS service must be removed and reapplied, or the IP interface must be reinitialized using the shutdown or no shutdown commands. This causes the system to reattempt the name resolution process between the IP interface and the VPLS service.

The no form of this command resets the allow-ip-int-bind flag on the VPLS service. If the VPLS service currently has an IP interface attached, the no allow-ip-int-bind command fails. When the allow-ip-int-bind flag is reset on the VPLS service, the configuration restrictions associated with setting the flag are removed.

This command enables the context to configure the Spanning Tree Protocol (STP) parameters. The Nokia implementation of the STP has a few modifications to better suit the operational characteristics of VPLS services. The most evident change is to the root bridge election. Because the core network operating between the service routers should not be blocked, the root path is calculated from the core perspective.

This command configures automatic detection of the edge port characteristics of the SAP.

The no form of this command reverts to the default value.

This command configures the SAP as an edge or non-edge port. If auto-edge is enabled for the SAP, this value is used only as the initial value.

RSTP, however, can detect that the actual situation is different from what edge-port may indicate.

Initially, the value of the SAP parameter is set to edge-port. This value changes if the following is true.

The no form of this command reverts the edge port setting to the default value.

RSTP, as defined in the IEEE 802.1D-2004 standards, usually transitions to the forwarding state via a handshaking mechanism (rapid transition), without any waiting times. If handshaking fails (for example, on shared links), the system falls back to the timer-based mechanism defined in the original STP (802.1D-1998) standard.

A shared link is a link with more than two nodes (for example, a shared 10/100BaseT segment). The port-type command is used to configure a link as point-to-point or shared.

For timer-based transitions, the 802.1D-2004 standard defines an internal variable forward-delay, which is used in calculating the default number of seconds that a SAP spends in the discarding and learning states when transitioning to the forwarding state.

The value of the forward-delay command depends on the STP operating mode of the VPLS instance:

This command configures the STP hello time for the VPLS STP instance.

This command defines the default timer value that controls the sending interval between BPDU configuration messages by this bridge, on ports where this bridge assumes the designated role.

The active hello time for the spanning tree is determined by the root bridge (except when the STP is running in RSTP mode; then the hello time is always taken from the locally configured parameter).

The configured hello-time can also be used to calculate the forward delay. See auto-edge.

The no form of this command reverts to the default value.

This command configures the peak number of BPDUs that can be transmitted in a period of one second.

The no form of this command reverts to the default value.

This command configures the maximum number of bridges for STP behind this SAP. If there is only a single bridge, transitioning to forwarding state will be based on handshaking (fast transitions).

If more than two bridges are connected via shared media, their SAP should all be configured as shared, and timer-based transitions are used.

The no form of this command reverts to the default value.

This command enables the context to configure MSTI related parameters at the SAP level. This context can be open only for existing MSTIs defined at the service level.

This commands configures path cost within a specific instance. If a loop occurs, this parameter indicates the probability of a specific port being assigned a forwarding state. (The highest value expresses lowest priority).

The no form of this command reverts to the default value.

This commands specifies the port priority within a specific instance. If a loop occurs, this parameter indicates the probability of a specific port being assigned a forwarding state.

The no form of this command reverts to the default value.

This command configures how many hops a BPDU can traverse the network starting from the root bridge. The message age field in a BPDU transmitted by the root bridge is initialized to 0. Every other bridge takes the message age value from BPDUs received on their root port and increment this value by 1. The message age therefore reflects the distance from the root bridge. BPDUs with a message age exceeding max-age are ignored.

STP uses the max-age value configured in the root bridge. This value is propagated to the other bridges via the BPDUs.

The no form of this command reverts to the default value.

This command specifies the version of STP the bridge is currently running. See Spanning Tree Operating Modes for information about these modes.

The no form of this command reverts to the default value.

This command enables the context to configure MSTI related parameters. MSTP supports “16” instances. The instance “0” is mandatory (by protocol) and cannot be created by the CLI. The software automatically maintains this instance.

This command specifies the bridge priority for the specific MSTI for this service. The bridge-priority value reflects likelihood that the switch will be chosen as the regional root switch (65535 represents the least likely). It is used as the highest 4 bits of the bridge ID included in the MSTP BPDUs generated by this bridge.

The values of the priority are only multiples of 4096 (4k). If a value is specified that is not a multiple of 4K, the value is replaced by the closest multiple of 4K (lower than the value entered).

The no form of this command reverts to the default value.

This command specifies a range of VLANs associated with a certain MST instance. This range applies to all SAPs of the mVPLS.

Every VLAN range that is not assigned within any of the instances created by the mst-instance command is automatically assigned to mst-instance 0. This instance is automatically maintained by the software and cannot be modified. Changing the VLAN range value can be performed only when the specific MST-instance is shut down.

The no form of this command removes the vlan-range from the specific MST instance.

This command specifies the number of hops in the region before BPDU is discarded, and the information held for the port is aged out. The root bridge of the instance sends a BPDU (or M-record) with remaining-hop-count set to configured max-hops. When a bridge receives the BPDU (or M-record), it decrements the received remaining-hop-count by 1 and propagates it in BPDU (or M-record) it generates.

The no form of this command reverts to the default value.

This command defines an MST region name. Two bridges are considered a part of the same MST region as soon as their configuration of the MST region name, the MST-revision and VLAN-to-instance assignment are identical.

The no form of this command removes region-name from the configuration.

This command defines the MST configuration revision number. Two bridges are considered a part of the same MST region if their configured MST-region name, MST-revision, and VLAN-to-instance are identical.

The no form of this command reverts MST configuration revision to the default value.

This command configures the Spanning Tree Protocol (STP) path cost for the SAP.

The path cost is used by STP to calculate the path cost to the root bridge. The path cost in BPDUs received on the root port is incremented with the configured path cost for that SAP. When BPDUs are sent out other egress SAPs, the newly calculated root path cost is used.

STP suggests that the path cost is defined as a function of the link bandwidth. Because SAPs are controlled by complex queuing dynamics, in the 7210 SAS the STP path cost is a static configuration.

The no form of this command reverts the path cost to the default value.

This command configures the virtual port number that uniquely identifies a SAP within configuration BPDUs. The internal representation of a SAP is unique to a system and has a reference space much bigger than the 12 bits definable in a configuration BPDU. STP takes the internal representation value of a SAP and identifies it with its own virtual port number that is unique to every other SAP defined on the TLS. The virtual port number is assigned at the time that the SAP is added to the TLS. Because the order that the SAP was added to the TLS is not preserved between reboots of the system, the virtual port number may change between restarts of the STP instance.

The virtual port number cannot be administratively modified.

This command configures the STP priority for the SAP.

STP priority is a configurable parameter associated with a SAP. When configuration BPDUs are received, the priority is used in some circumstances as a tie breaking mechanism to determine whether the SAP will be designated or blocked.

In traditional STP implementations (802.1D-1998), this field is called the port priority and has a value of 0 to 255. This field is coupled with the port number (0 to 255 also) to create a 16-bit value. In the latest STP standard (802.1D-2004), only the upper 4 bits of the port priority field are used to encode the SAP priority. The remaining 4 bits are used to extend the port ID field into a 12-bit virtual port number field. The virtual port number uniquely references a SAP within the STP instance.

STP computes the actual priority by taking the input value and masking out the lower four bits.The result is the value that is stored in the priority parameter; for example, if a value of 0 is entered, masking out the lower 4 bits results in a parameter value of 0. If a value of 255 is entered, the result is 240.

The no form of this command reverts the STP priority to the default value.

This command creates a Service Access Point (SAP) within a service. A SAP is a combination of port and encapsulation parameters that identify the service access point on the interface and within the 7210 SAS. Each SAP must be unique.

A physical port can have only one SAP to be part of one service. Multiple SAPs can be defined over a physical port, but each of these SAPs should belong to a different service.

All SAPs must be explicitly created. If no SAPs are created within a service or on an IP interface, a SAP does not exist on that object.

Enter an existing SAP without the create keyword to edit SAP parameters. The SAP is owned by the service in which it was created.

A SAP can only be associated with a single service. A SAP can only be defined on a port that has been configured as an access port using the config interface port-type port-id mode access command.

If a port is shut down, all SAPs on that port become operationally down. When a service is shut down, SAPs for the service are not displayed as operationally down, although all traffic traversing the service is discarded. The operational state of a SAP is relative to the operational state of the port on which the SAP is defined.

This command is also used to create a ring APS control SAP or a data SAP whose traffic is protected by a ring APS instance.

The no form of this command deletes the SAP with the specified port. When a SAP is deleted, all configuration parameters for the SAP are also deleted. For IES, the IP interface must be shut down before the SAP on that interface may be removed.

When this command is enabled, packets received on a SAP or with an unknown source MAC address will be dropped only if the maximum number of MAC addresses for that SAP (see max-nbr-mac-addr) has been reached. If the max-nbr-mac-addr command has not been set for the SAP, enabling the discard-unknown-source command has no effect.

When disabled, the packets are forwarded based on the destination MAC addresses.

The no form of this command causes packets with an unknown source MAC addresses to be forwarded by destination MAC addresses in VPLS.

This command enables the context to configure ETH-CFM parameters.

This command configures the ETH-CFM maintenance endpoint (MEP).

This command enables the generation and the reception of AIS messages.

This command configures the client maintenance entity group (MEG) levels to use for AIS message generation. Up to 7 levels can be provisioned, with the restriction that the client MEG level must be higher than the local MEG level.

This command specifies the transmission interval of AIS messages.

This command specifies the priority of AIS messages originated by the node.

This command enables the generation of CCM messages.

The no form of this command disables the generation of CCM messages.

This command specifies the priority value for CCMs and LTMs transmitted by the MEP.

By default, the highest priority on the bridge port is configured.

The no form of this command removes the priority value from the configuration.

For ETH-test to work, operators need to configure ETH-test parameters on both sender and receiver nodes. The ETH-test can then be performed using the following OAM commands:

oam eth-cfm eth-test mac-address mep mep-id domain md-index association ma-index [priority priority] [data-length data-length]

A check is performed for both the provisioning and test to ensure the MEP is an Y.1731 MEP (MEP provisioned with domain format none, association format icc-based). If not, the operation fails. An error message in the CLI and SNMP indicates the problem.

This command configures the test pattern for eth-test frames.

The no form of this command removes the values from the configuration.

This command configures the threshold value of bit errors.

This command configures the fault propagation for the MEP.

This command specifies the MAC address of the MEP.

The no form of this command reverts the MAC address of the MEP back to that of the port (if the MEP is on a SAP) or the bridge (if the MEP is on a spoke).

This command specifies the lowest priority defect that is allowed to generate a fault alarm.

This command specifies the MAC address of the MEP.

The no form of this command reverts the MAC address of the MEP back to that of the port (if the MEP is on a SAP) or the bridge (if the MEP is on a spoke).

This command enables or disables eth-test functionality on MEP.

This command allows Maintenance Intermediate Points (MIPs) to be created if mhf-creation for the MA is configured using the default option.

For more information about the ETH-CFM matrix support for different platforms, see the following tables:

The no form of this command deletes the MIP.

This command enables the Internet Group Management Protocol (IGMP) router alert check option.

The no form of this command disables the router alert check.

This command creates 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.

This command enables fast leave. When the IGMP fast leave processing is enabled, the 7210 SAS immediately removes a SAP from the multicast group when it detects an IGMP “leave” on that SAP.

Fast-leave processing allows the switch to remove a SAP that sends a “leave” from the forwarding table without first sending out group-specific queries to the SAP, and therefore speeds up the process of changing channels (“zapping”).

Fast leave should only be enabled when there is a single receiver present on the SAP.

When fast-leave is enabled, the configured last-member-query-interval value is ignored.

This command configures the VPLS from which multicast traffic is copied upon receipt of an IGMP join request. IGMP snooping must be enabled on the MVR VPLS.

This command adds a static multicast group as a (*, g). When a static IGMP group is added, multicast data for that (*,g) or (s,g) is forwarded to the specific SAP without receiving any membership report from a host.

This command identifies filter policy of multicast groups to be applied to this VPLS entity. The sources of the multicast traffic must be a member of the VPLS. By default, no group policy is identified.

The no form of this command removes the policy association from the VPLS configuration.

This command forces VC VLAN-type forwarding in the data path for spoke-SDPs or mesh SDPs that have either VC type. This command is not allowed on VLAN VC type SDPs.

The no form of this command reverts to the default value.

This command enables the IGMP snooping context.

This command configures the maximum number of multicast sources allowed per group.

The no form of this command removes the value from the configuration.

This command specifies the import routing policy to be used 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.

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 fast-leave is enabled on the SAP.

This command configures 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.

This command configues whether a multicast router is attached behind this SAP.

Configuring a SAP or SDP as an mrouter-port has a double 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 command should be enabled on all SAPs or SDPs connecting to a multicast router.

The IGMP version to be used for the reports (v1or v2) can only be determined after an initial query has been received. Until that time, no reports are sent on the SAP, even if mrouter-port is enabled.

If the send-queries command is enabled on this SAP or SDP, the mrouter-port command cannot be configured.

This command enables the context to configure Multicast VPLS Registration (MVR) parameters.

This command configures the IGMP query interval. If the send-queries command is enabled, this command 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.

This command configures the IP source address used in IGMP queries.

This command configures the IGMP query response interval. If the send-queries command is enabled, this command specifies the maximum response time advertised in IGMP queries.

The query-response-interval must be smaller than the query-interval.

If send-queries is not enabled on this SAP or SDP, the query-response-interval value is ignored.

This command configures 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.

If the send-queries command is enabled, this command allows tuning for the expected packet loss on a SAP or SDP. The robust-count value allows tuning for the expected packet loss on a subnet and is comparable to a retry count. If this SAP or SDP is expected to be “lossy”, this parameter may be increased. IGMP snooping on this SAP or SDP is robust to (robust-count-1) packet losses.

If send-queries is not enabled, this command is ignored.

This command configures the spoke-SDP precedence.

This command configures 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 data-path blocking to avoid the looping of these messages.

This command configures 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, and the version used is the version of the querier.

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.

This command adds a static (s,g) entry, to allow multicast traffic for a multicast group from a specified source. For a multicast group, more than one source address can be specified. Static (s,g) entries cannot be added, if a starg is previously created.

The no form of this command removes the source from the configuration.

This command adds a static (*,g) entry to allow multicast traffic for the corresponding multicast group from any source. This command can only be enabled if no existing source addresses for this group are specified.

The no form of this command removes the starg entry from the configuration.

This command enables the context to 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.

This command specifies the version of IGMP that is running on this SAP. 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 on that LAN.

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, and the version used is the version of the querier.

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 to the SAP on which the IGMP message was received (standard MVR behavior) but to another SAP.