Virtual Private LAN Service

This chapter provides information about Virtual Private LAN Service (VPLS), process overview, and implementation notes.

VPLS service overview

Virtual Private LAN Service (VPLS) is a class of virtual private network service that allows the connection of multiple sites in a single bridged domain over a provider-managed IP/MPLS network. The customer sites in a VPLS instance appear to be on the same LAN, regardless of their location. VPLS uses an Ethernet interface on the customer-facing (access) side which simplifies the LAN/WAN boundary and allows for rapid and flexible service provisioning. The 7210 SAS supports provisioning of access or uplink spokes to connect to the provider edge IP/MPLS routers.

VPLS provides a balance between point-to-point Frame Relay service and outsourced routed services (VPRN). VPLS enables each customer to maintain control of their own routing strategies. All customer routers in the VPLS service are part of the same subnet (LAN) which simplifies the IP addressing plan, especially when compared to a mesh constructed from many separate point-to-point connections. The VPLS service management is simplified because the service is not aware of nor participates in the IP addressing and routing.

A VPLS service provides connectivity between two or more SAPs on one (which is considered a local service) or more (which is considered a distributed service) service routers. The connection appears to be a bridged domain to the customer sites so protocols, including routing protocols, can traverse the VPLS service.

Other VPLS advantages include:

  • VPLS is a transparent, protocol-independent service.

  • There is no Layer 2 protocol conversion between LAN and WAN technologies.

  • There is no need to design, manage, configure, and maintain separate WAN access equipment, therefore, eliminating the need to train personnel on WAN technologies such as Frame Relay.

VPLS packet walkthrough

This section provides an example of VPLS processing of a customer packet sent across the network from site-A, which is connected to PE-Router-A through a 7210 SAS to site-C, which is connected through 7210 SAS to PE-Router-C (shown in the following figure) in an H-VPLS configuration. This section does not describe the processing on the PE routers, but only on 7210 SAS routers:

Figure 1. VPLS service architecture

  1. 7210-A (shown in the following figure)

    1. Service packets arriving at are associated with a VPLS service instance based on the combination of the physical port and the IEEE 802.1Q tag (VLAN-ID) in the packet.

      Figure 2. Access port ingress packet format and lookup

    2. 7210-A learns the source MAC address in the packet and creates an entry in the FIB table that associates the MAC address to the service access point (SAP) on which it was received.

    3. The destination MAC address in the packet is looked up in the FIB table for the VPLS instance. There are two possibilities: either the destination MAC address has already been learned (known MAC address) or the destination MAC address is not yet learned (unknown MAC address). For a Known MAC Address (Network port egress packet format and flooding Customer Location A).

    4. If the destination MAC address has already been learned by 7210, an existing entry in the FIB table identifies the far-end PE-Router and the service VC-label (inner label) to be used before sending the packet to PE-Router-A.

    5. The 7210 SAS chooses a transport LSP to send the customer packets to PE-Router-A. The customer packet is sent on this LSP when the IEEE 802.1Q tag is stripped and the service VC-label (inner label) and the transport label (outer label) are added to the packet. For an Unknown MAC Address (Network port egress packet format and flooding ).

    6. If the destination MAC address has not been learned, 7210 floods the packet to spoke-SDPs that are participating in the service.

      Figure 3. Network port egress packet format and flooding Customer Location A
      Figure 4. Network port egress packet format and flooding

  2. Core Router Switching

    All the core routers ('P' routers in IETF nomenclature) between PE-Router-A and PE-Router-B and PE-Router-C are Label Switch Routers (LSRs) that switch the packet based on the transport (outer) label of the packet until the packet arrives at far-end PE-Router. All core routers are unaware that this traffic is associated with a VPLS service.

  3. 7210-C (Access port ingress packet format and lookup)

    1. 7210-C associates the packet with the VPLS instance based on the VC label in the received packet after the stripping of the tunnel label.

    2. 7210-C learns the source MAC address in the packet and creates an entry in the FIB table that associates the MAC address to the spoke-SDP on which the packet was received.

    3. The destination MAC address in the packet is looked up in the FIB table for the VPLS instance. Again, there are two possibilities: either the destination MAC address has already been learned (known MAC address) or the destination MAC address has not been learned on the access side of 7210-C (unknown MAC address).

    4. If the destination MAC address has been learned by an existing entry in the FIB table identifies the local access port and the IEEE 802.1Q tag to be added before sending the packet to customer Location-C. The egress Q tag may be different from the ingress Q tag.

    5. If the destination MAC address has not been learned, 7210 floods the packet to all the access SAPs that are participating in the service.

VPLS features

This section describes VPLS features.

VPLS enhancements

The Nokia VPLS implementation includes several enhancements beyond basic VPN connectivity. The following VPLS features can be configured individually for each VPLS service instance:

  • Extensive MAC and IP filter support (up to Layer 4). Filters can be applied on a per SAP basis.

  • Forwarding Information Base (FIB) management features including:

    • Configurable FIB size limit

    • FIB size alarms

    • MAC learning disable

    • Discard unknown

    • Separate aging timers for locally and remotely learned MAC addresses.

  • Ingress rate limiting for broadcast, multicast, and destination unknown flooding on a per SAP basis.

  • Implementation of Spanning Tree Protocol (STP) parameters on a per VPLS, per SAP and per spoke-SDP basis.

  • Optional SAP and spoke-SDP redundancy to protect against node failure.

  • IGMP snooping on a per-SAP and SDP basis.

VPLS over MPLS

The VPLS architecture proposed in draft-ietf-ppvpn-vpls-ldp-0x.txt specifies the use of provider equipment (PE) that is capable of learning, bridging, and replication on a per-VPLS basis. The PE routers that participate in the service are connected using MPLS Label Switched Path (LSP) tunnels in a full-mesh composed of mesh SDPs or based on an LSP hierarchy (Hierarchical VPLS (H-VPLS)) composed of mesh SDPs and spoke SDPs. The 7210 SAS supports only H-VPLS.

Multiple VPLS services can be offered over the same set of LSP tunnels. Signaling specified in RFC 4905 is used to negotiate a set of ingress and egress VC labels on a per-service basis. The VC labels are used by the PE routers for de-multiplexing traffic arriving from different VPLS services over the same set of LSP tunnels.

H-VPLS is provided over MPLS by:

  • connecting the 7210 SAS-R6 and 7210 SAS-R12 to bridging-capable provider edge (PE) routers through a spoke-SDP. The PE routers are connected using a full mesh of LSPs.

  • negotiating per-service VC labels using draft-Martini encapsulation

  • replicating unknown and broadcast traffic in a service domain

  • enabling MAC learning over tunnel and access ports (see VPLS MAC learning and packet forwarding).

  • using a separate forwarding information base (FIB) per VPLS service

VPLS MAC learning and packet forwarding

The 7210 SAS edge devices perform the packet replication required for broadcast and multicast traffic across the bridged domain. MAC address learning is performed by the 7210 SAS device to reduce the amount of unknown destination MAC address flooding.

Each 7210 SAS maintains a Forwarding Information Base (FIB) for each VPLS service instance and learned MAC addresses are populated in the FIB table of the service. All traffic is switched based on MAC addresses and forwarded between all participating nodes using the LSP tunnels. Unknown destination packets (for example, the destination MAC address has not been learned) are forwarded on all LSPs to all participating nodes for that service until the target station responds and the MAC address is learned by the 7210 SAS associated with that service.

Configuration notes for VPLS forwarding

The 7210 SAS-R6 and 7210 SAS-R12 devices, uses the packet header fields that computes the hash for unicast traffic to be sent out of a SAP configured over a LAG and forwards it over the member ports of the LAG. For unknown unicast, broadcast and multicast traffic, it does not compute a hash and forwards all traffic out of the primary port of the LAG. For more information, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide.

IGMP snooping in VPLS service

Note: This section provides information about IGMP snooping support in a VPLS service. It does not apply to routed VPLS (R-VPLS) services. IGMP snooping can also be enabled for routed VPLS services. See Routed VPLS and IGMPv3 snooping for details.

In Layer 2 switches, multicast traffic is treated like an unknown MAC address or broadcast frame, which causes the incoming frame to be flooded out (broadcast) on every port within a VLAN. Although this is acceptable behavior for unknowns and broadcast frames, this flooded multicast traffic may result in wasted bandwidth on network segments and end stations, as IP multicast hosts can join and be interested in only specific multicast groups.

IGMP snooping entails using information in Layer 3 protocol headers of multicast control messages to determine the processing at Layer 2. By doing so, an IGMP snooping switch provides the benefit of conserving bandwidth on those segments of the network in which no node has expressed interest in receiving packets addressed to the group address.

IGMP snooping can be enabled in the context of VPLS services. The IGMP snooping feature allows for optimization of the multicast data flow to only those SAPs or SDPs that are members of the group. The system builds a database of group members per service by listening to IGMP queries and reports from each SAP or SDP, as follows:

  • When the switch receives an IGMP report from a host for a particular multicast group, the switch adds the host port number to the forwarding table entry.

  • When it receives an IGMP leave message from a host, it removes the host port from the table entry, if no other group members are present. It also deletes entries if it does not receive periodic IGMP membership reports from the multicast clients.

The following are IGMP snooping features:

  • IGMP v1, v2, and v3 are supported (RFC 1112, Host Extensions for IP Multicasting, and RFC 2236, Internet Group Management Protocol, Version 2).

  • IGMP snooping can be enabled and disabled on individual VPLS service instances.

  • IGMP snooping can be configured on individual SAPs that are part of a VPLS service. When IGMP snooping is enabled on a VPLS service, all its contained SAPs and SDPs automatically have snooping enabled.

  • Fast leave terminates the multicast session immediately instead of using the standard group-specific query to check if other group members are present on the network.

  • SAPs and SDPs can be statically configured as multicast router ports. This allows the operator to control the set of ports to which IGMP membership reports are forwarded.

  • Static multicast group membership on a per SAP and as per SDP basis can be configured.

  • The maximum number of multicast groups (static and dynamic) that a SAP or SDP can join can be configured. An event is generated when the limit is reached.

  • The maximum number of multicast groups (static and dynamic) that a VPLS instance simultaneously supports can be configured.

  • Proxy summarization of IGMP messages reduces the number of IGMP messages processed by upstream devices in the network.

  • IGMP filtering allows a subscriber to a service or the provider to block, receive, or transmit permission (or both) to individual hosts or a range of hosts. The following types of filters can be defined:

    • Filter group membership that report from a particular host or range of hosts. This filtering is performed by importing an appropriately-defined routing policy into the SAP or SDP.

    • Filters that prevent a host from transmitting multicast streams into the network. The operator can define a data-plane filter (ACL) that drops all multicast traffic, and apply this filter to a SAP or SDP.

Configuration guidelines for IGMP snooping in VPLS service

The following IGMP snooping considerations apply:

  • Layer 2 multicast is supported in VPLS services.

  • IGMP snooping is not supported for VCs (either VC-Ether or VC-VLAN) with control-word enabled.

  • IGMP snooping fast leave processing can be enabled only on SAPs and SDPs. IGMP snooping proxy summarization is enabled by default on SAPS and SDPs and cannot be disabled. Proxy summarization and fast leave processing are supported only on SDPs whose VC are configured to use vc-type ether and do not have control-word enabled.

  • IGMP filtering using policies is available on SAPs and SDPs. It is supported only on SDPs whose VC are configured to use vc-type ether and do not have control-word enabled.

  • Dynamic learning is only supported on SDPs whose VC are configured to use vc-type ether and do not have control-word enabled.

  • SDPs that are configured to use VC of type vc-vlan that need to be router ports must be configured statically. Multicast group memberships for such SDPs must be configured statically. Dynamic learning is not available for these SDPs.

  • IGMP snooping is not supported for control word-enabled SDPs.

Multicast VLAN Registration (MVR) support in VPLS service

Multicast VPLS Registration (MVR) is a bandwidth optimization method for multicast in a broadband services network. MVR allows a subscriber on a port to subscribe and unsubscribe to a multicast stream on one or more network-wide multicast VPLS instances.

MVR assumes that subscribers join and leave multicast streams by sending IGMP join and leave messages. The IGMP leave and join message are sent inside the VPLS to which the subscriber port is assigned. The multicast VPLS is shared in the network while the subscribers remain in separate VPLS services. Using MVR, users on different VPLS cannot exchange any information between them, but still multicast services are provided.

On the MVR VPLS, IGMP snooping must be enabled. On the user VPLS, IGMP snooping and MVR work independently. If IGMP snooping and MVR are both enabled, MVR reacts only to join and leave messages from multicast groups configured under MVR. Join and leave messages from all other multicast groups are managed by IGMP snooping in the local VPLS. This way, potentially several MVR VPLS instances could be configured, each with its own set of multicast channels.

MVR by proxy — In some situations, 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. This is called MVR by proxy and is shown in the following figure.

Figure 5. MVR and MVR by proxy

Configuration guidelines for MVR in VPLS service

In a MVR configuration, the svc-sap-type of the VPLS service that is the source (also known as MVR VPLS service) and the svc-sap-type of the VPLS service that is the sink (also known as user VPLS service) should match.

Layer 2 forwarding table management

The following sections describe VPLS features related to management of the Forwarding Information Base (FIB).

FIB size

MAC FIB size limits is a required MAC table management feature for each instance of a SAP or spoke-SDP within a particular VPLS service instance. It allows users to specify the maximum number of MAC FIB entries that are learned locally for a SAP or remotely for a spoke-SDP. If the configured limit is reached, then no new addresses are learned from the SAP or spoke-SDP until at least one FIB entry is aged out or cleared, as follows:

  • When the limit is reached on a SAP, packets with unknown source MAC addresses are still forwarded (this default behavior can be changed by configuration). By default, if the destination MAC address is known, it is forwarded based on the FIB, and if the destination MAC address is unknown, it is flooded. Alternatively, if discard unknown is enabled at the VPLS service level, unknown destination MAC addresses are discarded.

  • The log event SAP MAC limit reached is generated when the limit is reached. When the condition is cleared, the log event SAP MAC Limit Reached Condition Cleared is generated.

  • Disable learning at the VPLS service level allows users to disable the dynamic learning function on the service. Disable Learning is supported at the SAP and spoke-SDP level as well.

  • Disable aging allows users to turn off aging for learned MAC addresses. It is supported at the VPLS service level, SAP level and spoke-SDP level.

FIB size alarms

The size of the VPLS FIB can be configured with a low watermark and a high watermark, expressed as a percentage of the total FIB size limit. If the actual FIB size grows above the configured high watermark percentage, an alarm is generated. If the FIB size falls below the configured low watermark percentage, the alarm is cleared by the system.

Local and remote aging timers

Like a Layer 2 switch, learned MACs within a VPLS instance can be aged out if no packets are sourced from the MAC address for a specified period of time (the aging time). In each VPLS service instance, there are independent aging timers for locally learned MAC and remotely learned MAC entries in the forwarding database (FIB). A local MAC address is a MAC address associated with a SAP because it ingressed on a SAP. A remote MAC address is a MAC address received by an SDP from another router for the VPLS instance. The local-age timer for the VPLS instance specifies the aging time for locally learned MAC addresses, and the remote-age timer specifies the aging time for remotely learned MAC addresses.

In general, the remote-age timer is set to a longer period than the local-age timer to reduce the amount of flooding required for destination unknown MAC addresses. The aging mechanism is considered a low priority process. In most situations, the aging out of MAC addresses can happen in within tens of seconds beyond the age time. To minimize overhead, local MAC addresses on a LAG port and remote MAC addresses, in some circumstances, can take up to two times their respective age timer to be aged out.

Disable MAC aging

The MAC aging timers can be disabled which prevents any learned MAC entries from being aged out of the FIB. When aging is disabled, it is still possible to manually delete or flush learned MAC entries. Aging can be disabled for learned MAC addresses on a SAP or a spoke-SDP of a VPLS service instance.

Disable MAC learning

When MAC learning is disabled for a service, new source MAC addresses are not entered in the VPLS FIB. MAC learning can be disabled for individual SAPs or spoke-SDPs.

Unknown MAC discard

Unknown MAC discard is a feature which discards all packets ingressing the service where the destination MAC address is not in the FIB. The normal behavior is to flood these packets to all end points in the service.

Unknown MAC discard can be used with the disable MAC learning and disable MAC aging options to create a fixed set of MAC addresses allowed to ingress and traverse the service.

VPLS and rate limiting

Traffic that is flooded throughout the VPLS can be rate limited on SAP ingress through the use of service ingress QoS policies. In a service ingress QoS policy, individual meters can be defined per forwarding class to provide rate-limiting/policing of broadcast traffic, MAC multicast traffic and unknown destination MAC traffic.

MAC move

The MAC move feature is useful to protect against undetected loops in a VPLS topology as well as the presence of duplicate MACs in a VPLS service.

If two clients in the VPLS have the same MAC address, the VPLS experiences a high relearn rate for the MAC. When MAC move is enabled, the 7210 SAS-R6 or 7210 SAS-R12 shuts down the SAP or spoke-SDP and creates an alarm event when the threshold is exceeded.

MAC move allows sequential order port blocking. By configuration, some VPLS ports can be configured as ‟non-blockable” which allows simple level of control which ports are being blocked during loop occurrence.

Split horizon SAP groups and split horizon spoke-SDP groups

Within the context of VPLS services, a loop-free topology inside a fully meshed VPLS core is achieved by applying a split-horizon forwarding concept.The packets received from a mesh SDP are never forwarded to other mesh SDPs within the same service. The advantage of this approach is that no protocol is required to detect loops within the VPLS core network.

In applications such as DSL aggregation, it is useful to extend this split-horizon concept also to groups of SAPs or spoke-SDPs. This extension is referred to as a split horizon SAP group. Traffic arriving on a SAP or a spoke-SDP within a split horizon group is not forwarded to other SAPs and spoke SDPs configured in the same split horizon group, but is forwarded to other SAPs/spoke-SDPs, which are not part of the split horizon group.

Configuration guidelines for use of split horizon group in a VPLS service

On all 7210 SAS platforms, except for 7210 SAS-R6 and 7210 SAS-R12 IMM-b, mesh SDPs cannot be configured in a service which uses split horizon group. Conversely, if a service has a mesh-SDP configured, split horizon group cannot be used in the same service. On 7210 SAS-R6 and 7210 SAS-R12 IMM-b, SHG can be configured along with spoke-SDP and mesh-SDP.

VPLS and Spanning Tree Protocol

The Nokia VPLS service provides a bridged or switched Ethernet Layer 2 network. Equipment connected to SAPs forward Ethernet packets into the VPLS service. The participating in the service learns where the customer MAC addresses reside, on ingress SAPs.

Unknown destinations, broadcasts, and multicasts are flooded to all other SAPs in the service. If SAPs are connected together, either through misconfiguration or for redundancy purposes, loops can form and flooded packets can keep flowing through the network. The Nokia implementation of the Spanning Tree Protocol (STP) is designed to remove these loops from the VPLS topology. This is done by putting one or several SAPs in the discarding state.

The Nokia implementation of the Spanning Tree Protocol (STP) incorporates some modifications to make the operational characteristics of VPLS more effective.

The STP instance parameters allow the balancing between resiliency and speed of convergence extremes. Modifying particular parameters can affect the behavior. For information about command usage, descriptions, and CLI syntax, see Configuring a VPLS service with CLI.

Spanning tree operating modes

Per VPLS instance, a preferred STP variant can be configured. The STP variants supported are:

  • rstp - Rapid Spanning Tree Protocol (RSTP) compliant with IEEE 802.1D-2004 - default mode

  • dot1w - compliant with IEEE 802.1w

  • comp-dot1w - operation as in RSTP but backwards compatible with IEEE 802.1w (this mode allows interoperability with some MTU types)

  • mstp - compliant with the Multiple Spanning Tree Protocol specified in IEEE 802.1Q-REV/D5.0-09/2005. This mode of operation is only supported in an mVPLS

While the 7210 SAS initially uses the mode configured for the VPLS, it dynamically falls back (on a per-SAP basis) to STP (IEEE 802.1D-1998) based on the detection of a BPDU of a different format. A trap or log entry is generated for every change in spanning tree variant.

Some older 802.1W compliant RSTP implementations may have problems with some of the features added in the 802.1D-2004 standard. Interworking with these older systems is improved with the comp-dot1w mode. The differences between the RSTP mode and the comp-dot1w mode are:

  • The RSTP mode implements the improved convergence over shared media feature, for example, RSTP transitions from discarding to forwarding in 4 seconds when operating over shared media. The comp-dot1w mode does not implement this 802.1D-2004 improvement and transitions conform to 802.1w in 30 seconds (both modes implement fast convergence over point-to-point links).

  • In the RSTP mode, the transmitted BPDUs contain the port's designated priority vector (DPV) (conforms to 802.1D-2004). Older implementations may be confused by the DPV in a BPDU and may fail to recognize an agreement BPDU correctly. This would result in a slow transition to a forwarding state (30 seconds). For this reason, in the comp-dot1w mode, these BPDUs contain the port's port priority vector (conforms to 802.1w).

The 7210 SAS supports BDPU encapsulation formats, and can dynamically switch between the following supported formats (on a per-SAP basis):

  • IEEE 802.1D STP

  • Cisco PVST

Multiple Spanning Tree

The Multiple Spanning Tree Protocol (MSTP) extends the concept of the IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) by allowing grouping and associating VLANs to Multiple Spanning Tree Instances (MSTI). Each MSTI can have its own topology, which provides architecture enabling load balancing by providing multiple forwarding paths. At the same time, the number of STP instances running in the network is significantly reduced as compared to Per VLAN STP (PVST) mode of operation. Network fault tolerance is also improved because a failure in one instance (forwarding path) does not affect other instances.

The 7210 SAS implementation of Management VPLS (mVPLS) is used to group different VPLS instances under single RSTP instance. Introducing MSTP into the mVPLS allows the following:

  • interoperation with traditional Layer 2 switches in access network

  • provides an effective solution for dual homing of many business Layer 2 VPNs into a provider network

Configuration notes for Spanning Tree Protocol, L2PT and BPDU translation

The 7210 SAS-R6 and 7210 SAS-R12 devices, reserves some entries in the L2 FIB table for use with xSTP, L2PT and BPDU translation. A fixed amount of such resources are available per node. The user has an option to allocate these resources to services, where they plan to use one of these protocols, at service creation time. This is achieved with the new CLI parameter allow-l2pt-xstp-bpdu [enable | disable]. This is a mandatory parameter that the user must configure if they plan to enable one of these protocols in the service. The software fails any attempt to enable these protocols if this parameter has not been configured for the service.

MSTP for QinQ SAPs

MSTP runs in a MVPLS context and can control SAPs from source VPLS instances. QinQ SAPs are supported. The outer tag is considered by MSTP as part of VLAN range control

Enhancements to the Spanning Tree Protocol

To interconnect 7210 SAS devices (PE devices) across the backbone, service tunnels (SDPs) are used. These service tunnels are shared among multiple VPLS instances. The Nokia implementation of the Spanning Tree Protocol (STP) incorporates some enhancements to make the operational characteristics of VPLS more effective. The implementation of STP on the router is modified to guarantee that service tunnels is not blocked in any circumstance without imposing artificial restrictions on the placement of the root bridge within the network. The modifications introduced are fully compliant with the 802.1D-2004 STP specification.

When running MSTP, spoke-SDPs cannot be configured. Also, ensure that all bridges connected by mesh SDPs are in the same region. If not, the mesh is prevented from becoming active (trap is generated).

To achieve this, all mesh SDPs are dynamically configured as either root ports or designated ports. The PE devices participating in each VPLS mesh determine (using the root path cost learned as part of the normal protocol exchange) which of the 7210 SAS devices is closest to the root of the network. This PE device is internally designated as the primary bridge for the VPLS mesh. As a result of this, all network ports on the primary bridges are assigned the designated port role and therefore remain in the forwarding state.

The second part of the solution ensures that the remaining PE devices participating in the STP instance see the SDP ports as a lower cost path to the root instead of a path that is external to the mesh. Internal to the PE nodes participating in the mesh, the SDPs are treated as zero cost paths toward the primary bridge. As a consequence, the path through the mesh are seen as lower cost than any alternative and the PE node designates the network port as the root port. This ensures that network ports always remain in forwarding state.

A combination of the preceding features ensure that network ports are never blocked and maintain interoperability with bridges external to the mesh that are running STP instances.

L2PT termination

L2PT is used to transparently transport protocol data units (PDUs) of Layer 2 protocols such as STP, CDP, DTP, VTP, PAGP, and UDLD. This allows running these protocols between customer CPEs without involving backbone infrastructure.

The 7210 SAS routers allow transparent tunneling of PDUs across the VPLS core. However, in some network designs, the VPLS PE is connected to CPEs through a legacy Layer 2 network instead of having direct connections. In such environments termination of tunnels through such infrastructure is required.

L2PT tunnels protocol PDUs by overwriting MAC destination addresses at the ingress of the tunnel to a proprietary MAC address such as 01-00-0c-cd-cd-d0. At the egress of the tunnel, this MAC address is then overwritten back to MAC address of the respective Layer 2 protocol.

The 7210 SAS nodes support L2PT termination for STP BPDUs. More specifically:

  • At ingress of every SAP which is configured as L2PT termination, all PDUs with a MAC destination address, 01-00-0c-cd-cd-d0 are intercepted and their MAC destination address are overwritten to MAC destination address used for the corresponding protocol. The type of protocol can be derived from LLC and SNAP encapsulation.

  • In egress direction, PDUs of the corresponding protocol received on all VPLS ports are intercepted and L2PT encapsulation is performed for SAPs configured as L2PT termination points. Because of the implementation reasons, PDU interception and redirection to CPM can be performed only at ingress. Therefore, to comply with the preceding requirement, as soon as at least 1 port of a specific VPLS service is configured as L2PT termination port, redirection of PDUs to CPM is set on all other ports (SAPs) of the VPLS service.

L2PT termination can be enabled only if STP is disabled in a context of the specific VPLS service.

BPDU translation

VPLS networks are typically used to interconnect different customer sites using different access technologies such as Ethernet and bridged-encapsulated ATM PVCs. Typically, different Layer 2 devices can support different types of STP and even if they are from the same vendor. In some cases, it is necessary to provide BPDU translation to provide an interoperable e2e solution.

To address these network designs, BPDU format translation is supported on 7210 SAS devices. If enabled on a specific SAP, the system intercepts all BPDUs destined for that interface and perform required format translation such as STP-to-PVST or PVST-to-STP.

Similarly, BPDU interception and redirection to the CPM is performed only at ingress meaning that as soon as at least 1 port within a specific VPLS service has BPDU translation enabled, all BPDUs received on any of the VPLS ports are redirected to the CPM.

BPDU translation involves all encapsulation actions that the datapath would perform for a specific outgoing port (such as adding VLAN tags depending on the outer SAP and adding or removing all the required VLAN information in a BPDU payload.

This feature can be enabled on a SAP only if STP is disabled in the context of the specific VPLS service.

L2PT and BPDU translation

L2PT termination for only STP (Spanning Tree Protocol) and PVST (Per VLAN Spanning Tree Protocol), Cisco Discovery Protocol (CDP), Digital Trunking Protocol (DTP), Port Aggregation Protocol (PAgP), Uni-directional Link Detection (UDLD), Virtual Trunk Protocol (VTP), STP (Spanning Tree Protocol) and PVST (per-VLAN Spanning Tree protocol) are supported on 7210 SAS devices.

These protocols automatically pass the other protocols tunneled by L2PT toward the CPM and all carry the same specific Cisco MAC.

The existing L2PT limitations apply:

  • The protocols apply only to VPLS.

  • The protocols cannot be used while running STP on the same VPLS as soon as one SAP has L2PT/BPDU translation enabled.

  • Forwarding occurs on the CPM and uses CPU processing cycles.

VPLS redundancy

The VPLS standard (RFC 4762, Virtual Private LAN Services Using LDP Signaling) includes provisions for hierarchical VPLS, using point-to-point spoke SDPs. Two applications have been identified for spoke SDPs:

  • to connect to Multi-Tenant Units (MTUs) to PEs in a metro area network

  • to interconnect the VPLS nodes of two networks

In both applications the spoke SDPs serve to improve the scalability of VPLS. While node redundancy is implicit in non-hierarchical VPLS services (using a full mesh of SDPs between PEs), node redundancy for spoke SDPs needs to be provided separately. In VPLS services, only two spoke-SDPs are allowed in an endpoint.

Nokia routers have implemented special features for improving the resilience of hierarchical VPLS instances, in both MTU and inter-metro applications.

Spoke-SDP redundancy for metro interconnection

When two or more meshed VPLS instances are interconnected by redundant spoke SDPs (as shown in H-VPLS with spoke redundancy), a loop in the topology results. To remove such a loop from the topology, Spanning Tree Protocol (STP) can be run over the SDPs (links) which form the loop such that one of the SDPs is blocked. As running STP in each and every VPLS in this topology is not efficient, the node includes functionality which can associate a number of VPLSes to a single STP instance running over the redundant-SDPs. Node redundancy is therefore achieved by running STP in one VPLS, and applying the conclusions of this STP to the other VPLS services. The VPLS instance running STP is referred to as the ‟management VPLS” or mVPLS.

In the case of a failure of the active node, STP on the management VPLS in the standby node changes the link states from disabled to active. The standby node then broadcasts a MAC flush LDP control message in each of the protected VPLS instances, so that the address of the newly active node can be relearned by all PEs in the VPLS.

It is possible to configure two management VPLS services, where both VPLS services have different active spokes (this is achieved by changing the path-cost in STP). By associating different user VPLSes with the two management VPLS services, load balancing across the spokes can be achieved.

Figure 6. H-VPLS with spoke redundancy

Spoke-SDP-based redundant access

This feature provides the ability to have a node deployed as MTUs (Multi-Tenant Unit Switches) to be multi-homed for VPLS to multiple routers deployed as PEs without requiring the use of mVPLS.

In the configuration example shown in H-VPLS with spoke redundancy, the MTUs have spoke-SDPs to two PEs devices. One is designated as the primary and one as the secondary spoke-SDP. This is based on a precedence value associated with each spoke. If the primary and secondary spoke-SDPs have the same precedence value, the spoke-SDP with lower ID functions as the primary SDP.

The secondary spoke is in a blocking state (both on receive and transmit) as long as the primary spoke is available. When the primary spoke becomes unavailable (because of link failure, PEs failure, and so on), the MTU immediately switches traffic to the backup spoke and starts receiving/sending traffic to/from the standby spoke. Optional revertive operation (with configurable switch-back delay) is applicable only when one of the spokes is configured with precedence of primary. If not, this action does not take place. Forced manual switchover is also supported.

To speed up the convergence time during a switchover, MAC flush is configured. The MTUs generates a MAC flush message over the newly unblocked spoke when a spoke change occurs. As a result, the PEs receiving the MAC flush then flush all MACs associated with the impacted VPLS service instance and forward the MAC flush to the other PEs in the VPLS network if propagate-mac-flush is enabled.

Inter-domain VPLS resiliency using multi-chassis endpoints

Note: MC-EP is not supported on 7210 SAS platforms. This section provides an example of how 7210 SAS devices can be used as MTU devices in an MC-EP solution. In this solution the 7750 SR routers provide the MC-EP functionality.

Inter-domain VPLS refers to a VPLS deployment where sites may be located in different domains. An example of inter-domain deployment can be where different Metro domains are interconnected over a Wide Area Network (Metro1-WAN-Metro2) or where sites are located in different autonomous systems (AS1-ASBRs-AS2).

Multi-chassis endpoint (MC-EP) provides an alternate solution that does not require RSTP at the gateway VPLS PEs while still using pseudowires to interconnect the VPLS instances located in the two domains.

MC-EP expands the single chassis endpoint based on active-standby pseudowires for VPLS shown in the following figure. In the solution shown by the following figure, 7210 devices are used as MTUs.

Figure 7. H-VPLS resiliency based on AS pseudowires

The active-standby pseudowire solution is appropriate for the scenario when only one VPLS PE (MTU-s) needs to be dual-homed to two core PEs (PE1 and PE2).

VPLS access redundancy

A second application of hierarchical VPLS is using that are MPLS-enabled which must have spoke-SDPs to the closest PE node. To protect against failure of the PE node, an MTU can be dual-homed.

The following are several mechanisms that can be used to resolve a loop in an access circuit, however from operation perspective they can be subdivided into STP-based access, with or without mVPLS.

STP-based redundant access to VPLS

In configuration shown in the following figure, STP is activated on the MTU and two PEs to resolve a potential loop.

Figure 8. Dual homed MTU-s in two-tier hierarchy H-VPLS

To remove such a loop from the topology, Spanning Tree Protocol (STP) can be run over the SDPs (links) which form the loop such that one of the SDPs is blocked. Running STP in every VPLS in this topology is not efficient as the node includes functionality which can associate a number of VPLSes to a single STP instance running over the redundant SDPs. Node redundancy is therefore achieved by running STP in one VPLS. Therefore, this applies the conclusions of this STP to the other VPLS services.

The VPLS instance running STP is referred to as the management VPLS or mVPLS. In the case of a failure of the active node, STP on the management VPLS in the standby node changes the link states from disabled to active. The standby node then broadcasts a MAC flush LDP control message in each of the protected VPLS instances, so that the address of the newly active node can be relearned by all PEs in the VPLS. It is possible to configure two management VPLS services, where both VPLS services have different active spokes (this is achieved by changing the path-cost in STP). By associating different user VPLSes with the two management VPLS services, load balancing across the spokes can be achieved.

In this configuration the scope of STP domain is limited to MTU and PEs, while any topology change needs to be propagated in the whole VPLS domain.

This is done by using ‟MAC-flush” messages defined by RFC 4762, Virtual Private LAN Services Using LDP Signaling. In the case where STP acts as a loop resolution mechanism, every Topology Change Notification (TCN) received in a context of STP instance is translated into an LDP-MAC address withdrawal message (also referred to as a MAC-flush message) requesting to clear all FDB entries except the ones learned from the originating PE. Such messages are sent to all PE peers connected through SDPs (mesh and spoke) in the context of VPLS services which are managed by the specific STP instance.

Redundant access to VPLS without STP

The Nokia implementation also alternative methods for providing a redundant access to Layer 2 services, such as MC-LAG. Also in this case, the topology change event needs to be propagated into VPLS topology to provide fast convergence.

H-VPLS with spoke redundancy show a dual-homed connection to VPLS service (PE-A, PE-B, PE-C, PE-D) and operation in case of link failure (between PE-C and L2-B). Upon detection of a link failure PE-C sends MAC-Address-Withdraw messages, which indicates to all LDP peers that they should flush all MAC addresses learned from PE-C. This leads to a broadcasting of packets addressing affected hosts and relearning process in case an alternative route exists.

Note that the message described here is different from the message described in previous section and in RFC 4762, Virtual Private LAN Services Using LDP Signaling. The difference is in the interpretation and action performed in the receiving PE. According to the standard definition, upon receipt of a MAC withdraw message, all MAC addresses, except the ones learned from the source PE, are flushed,

This section specifies that all MAC addresses learned from the source are flushed. This message has been implemented as an LDP address message with vendor-specific type, length, value (TLV), and is called the flush-mine message.

The advantage of this approach (as compared to RSTP based methods) is that only MAC-affected addresses are flushed and not the full forwarding database. While this method does not provide a mechanism to secure alternative loop-free topology, the convergence time is dependent on the speed of the specific CE device opening alternative links (L2-B switch in Figure 57) as well as on the speed PE routers flush their FDB.

In addition, this mechanism is effective only if PE and CE are directly connected (no hub or bridge) as it reacts to physical failure of the link.

MAC flush message processing

The previous sections described operation principle of several redundancy mechanisms available in context of VPLS service. All of them rely on MAC flush message as a tool to propagate topology change in a context of the specific VPLS. This section aims to summarize basic rules for generation and processing of these messages.

As described on respective sections, the 7210 SAS supports two types of MAC flush message, flush-all-but-mine and flush-mine. The main difference between these messages is the type of action they signal. Flush-all-but-mine requests clearing of all FDB entries which were learned from all other LDP peers except the originating PE. This type is also defined by RFC 4762 as an LDP MAC address withdrawal with an empty MAC address list.

Flush-all-mine message requests clearing all FDB entries learned from originating PE. This means that this message has exactly other effect then flush-all-but-mine message. This type is not included in RFC 4762 definition and it is implemented using vendor specific TLV.

The advantages and disadvantages of the individual types should be apparent from examples in the previous section. The description here focuses on summarizing actions taken on reception and conditions individual messages are generated.

Upon reception of MAC flush messages (regardless the type) SR-Series PE takes following actions:

  • Clears FDB entries of all indicated VPLS services conforming the definition.

  • Propagates the message (preserving the type) to all LDP peers, if ‟propagate-mac-flush” flag is enabled at corresponding VPLS level.

The flush-all-but-mine message is generated under following conditions:

  • The flush-all-but-mine message is received from LDP peer and propagate-mac-flush flag is enabled. The message is sent to all LDP peers in the context of VPLS service it was received in.

  • TCN message in a context of STP instance is received. The flush-all-but-mine message is sent to all LDP-peers connected with spoke and mesh SDPs in a context of VPLS service controlled by the specific STP instance (based on mVPLS definition). The message is sent only to LDP peers which are not part of STP domain, which means corresponding spoke and mesh SDPs are not part of mVPLS.

  • Flush-all-but-mine message is generated when switch over between spoke SDPs of the same endpoint occurs. The message is sent to LDP peer connected through newly active spoke-SDP.

The flush-mine message is generated under following conditions:

  • The flush-mine message is received from LDP peer and propagate-mac-flush flag is enabled. The message is sent to all LDP peers in the context of VPLS service it was received.

  • The flush-mine message is generated when a SAP or SDP transitions from operationally up to an operationally down state and send-flush-on-failure flag is enabled in the context of the specific VPLS service. The message is sent to all LDP peers connected in the context of the specific VPLS service. Note, that enabling send-flush-on-failure the flag is blocked in VPLS service managed by mVPLS. This is to prevent both messages from being sent at the same time.

  • The flush-mine message is generated when an MC-LAG SAP transitions from an operationally up state to an operationally down state. The message is sent to all LDP peers connected in the context of the specific VPLS service.

MAC flush with STP

A second application of Hierarchical VPLS is in the use of Multi Tenant Units (MTU). MTUs are typically not MPLS-enabled, and therefore have Ethernet links to the closest PE node (see H-VPLS with SAP redundancy). To protect against failure of the PE node, an MTU could be dual-homed and therefore have two SAPs on two PE nodes. To resolve the potential loop, STP is activated on the MTU and the two PEs.

Like in the preceding scenario, STP only needs to run in a single VPLS instance, and the results of the STP calculations are applied to all VPLSs on the link. Equally, the standby node broadcasts MAC flush LDP messages in the protected VPLS instances when it detects that the active node has failed.

Figure 9. H-VPLS with SAP redundancy

Selective MAC flush

When using STP as described previously is not appropriate, the ‟Selective MAC flush” feature can be used instead.

In this scenario, the 7210 SAS that detects a port failure sends out a flush-all-from-ME LDP message to all PEs in the VPLS. The PEs receiving this LDP message removes all MAC entries originated by the sender from the indicated VPLS.

A drawback of this approach is that selective MAC flush does not signal that a backup path was found, only that the previous path is no longer available. In addition, the selective MAC Flush mechanism is effective only if the CE and PE are directly connected (no intermediate hubs or bridges) as it reacts only to a physical failure of the link. Consequently, Nokia recommends using the MAC flush with STP method described previously where possible.

Dual homing to a VPLS service

The following figure shows a dual-homed connection to VPLS service (PE-A, PE-B, PE-C, PE-D) and operation in case of link failure (between PE-C and L2-B). Upon detection of a link failure PE-C sends MAC-Address-Withdraw messages, which indicates to all LDP peers that they should flush all MAC addresses learned from PE-C. This leads to a broadcasting of packets addressing affected hosts and relearning process in case an alternative route exists.

Figure 10. Dual homed CE connection to VPLS

Note that the message described here is different from the message described in draft-ietf-l2vpn-vpls-ldp-xx.txt, Virtual Private LAN Services over MPLS. The difference is in the interpretation and action performed in the receiving PE. According the draft definition, upon receipt of a MAC-withdraw message, all MAC addresses, except the ones learned from the source PE, are flushed, This section specifies that all MAC addresses learned from the source are flushed. This message has been implemented as an LDP address message with vendor-specific type, length, value (TLV), and is called the flush-all-from-ME message.

The draft definition message is currently used in management VPLS which is using RSTP for recovering from failures in Layer 2 topologies. The mechanism described in this document represent an alternative solution.

The advantage of this approach (as compared to RSTP based methods) is that only MAC-affected addresses are flushed and not the full forwarding database. While this method does not provide a mechanism to secure alternative loop-free topology, the convergence time is dependent on the speed of the specific CE device opening alternative links (L2-B switch in Dual homed CE connection to VPLS) as well as on the speed PE routers flush their FDB.

In addition, this mechanism is effective only if PE and CE are directly connected (no hub or bridge) as it reacts to physical failure of the link.

VPLS service considerations

This section describes various 7210 SAS service features and any special capabilities or considerations as they relate to VPLS services.

SAP encapsulations

VPLS services are designed to carry Ethernet frame payloads, so it can provide connectivity between any SAPs that pass Ethernet frames. The following SAP encapsulations are supported on the VPLS service:

  • Ethernet null

  • Ethernet Dot1q

  • Ethernet Dot1q Default

  • Ethernet Dot1q Explicit Null

VLAN processing

The SAP encapsulation definition on Ethernet ingress ports defines which VLAN tags are used to determine the service that the packet belongs:

  1. null encapsulation defined on ingress

    Any VLAN tags are ignored and the packet goes to a default service for the SAP

  2. dot1q encapsulation defined on ingress

    Only first VLAN tag is considered.

  3. dot1q Default encapsulation defined on ingress

    Tagged packets not matching any of the configured VLAN encapsulations would be accepted. This is like a default SAP for tagged packets.

  4. dot1q Explicit Null encapsulation defined on ingress

    Any untagged or priority tagged packets are accepted.

BGP Auto-Discovery for LDP VPLS

BGP Auto Discovery (BGP AD) for LDP VPLS is a framework for automatically discovering the endpoints of a Layer 2 VPN offering an operational model similar to that of an IP VPN. This model allows carriers to leverage existing network elements and functions, including but not limited to, route reflectors and BGP policies to control the VPLS topology.

BGP AD is an excellent complement to an already established and well deployed Layer 2 VPN signaling mechanism target LDP providing one touch provisioning for LDP VPLS where all the related PEs are discovered automatically. The service provider may make use of existing BGP policies to regulate the exchanges between PEs in the same, or in different, autonomous system (AS) domains. The addition of BGP AD procedures does not require carriers to uproot their existing VPLS deployments and to change the signaling protocol.

BGP AD overview

The BGP protocol establishes neighbor relationships between configured peers. An open message is sent after the completion of the three-way TCP handshake. This open message contains information about the BGP peer sending the message. This message contains Autonomous System Number (ASN), BGP version, timer information and operational parameters, including capabilities. The capabilities of a peer are exchanged using two numerical values: the Address Family Identifier (AFI) and Subsequent Address Family Identifier (SAFI). These numbers are allocated by the Internet Assigned Numbers Authority (IANA). BGP AD uses AFI 65 (L2VPN) and SAFI 25 (BGP VPLS).

Information model

Following is the establishment of the peer relationship, the discovery process begins as soon as a new VPLS service instance is provisioned on the PE.

Two VPLS identifiers are used to indicate the VPLS membership and the individual VPLS instance:

  • VPLS-ID

    Membership information, unique network wide identifier; same value assigned for all VPLS switch instances (VSIs) belonging to the same VPLS; encodable and carried as a BGP extended community in one of the following formats:

    • a two-octet AS specific extended community

    • an IPv4 address specific extended community

  • VSI-ID

    The unique identifier for each individual VSI, built by concatenating a route distinguisher (RD) with a 4 bytes identifier (usually the system IP of the VPLS PE); encoded and carried in the corresponding BGP NLRI.

To advertise this information, BGP AD employs a simplified version of the BGP VPLS NLRI where just the RD and the next 4 bytes are used to identify the VPLS instance. There is no need for Label Block and Label Size fields as T-LDP takes care of signaling the service labels later on.

The format of the BGP AD NLRI is very similar with the one used for IP VPN, as shown in the following figure. The system IP may be used for the last 4 bytes of the VSI-ID further simplifying the addressing and the provisioning process.

Figure 11. BGP AD NLRI versus IP VPN NLRI

Network Layer Reachability Information (NLRI) is exchanged between BGP peers indicating how to reach prefixes. The NLRI is used in the Layer 2 VPN case to tell PE peers how to reach the VSI instead of specific prefixes. The advertisement includes the BGP next hop and a route target (RT). The BGP next hop indicates the VSI location and is used in the next step to determine which signaling session is used for pseudowire signaling. The RT, also coded as an extended community, can be used to build a VPLS full mesh or a H-VPLS hierarchy through the use of BGP import or export policies.

BGP is only used to discover VPN endpoints and the corresponding far end PEs. It is not used to signal the pseudowire labels. This task remains the responsibility of targeted-LDP (T-LDP).

FEC element for T-LDP signaling

Two LDP FEC elements are defined in RFC 4447, PW Setup & Maintenance Using LDP. The original pseudowire-ID FEC element 128 (0x80) employs a 32-bit field to identify the virtual circuit ID and it was used extensively in the initial VPWS and VPLS deployments. The simple format is easy to understand but it does not provide the required information model for BGP Auto-Discovery function. To support BGP AD and other new applications a new Layer 2 FEC element, the generalized FEC (0x81) is required.

The generalized pseudowire-ID FEC element has been designed for auto discovery applications. It provides a field, the address group identifier (AGI), that is used to signal the membership information from the VPLS-ID. Separate address fields are provided for the source and target address associated with the VPLS endpoints called the Source Attachment Individual Identifier (SAII) and respectively, Target Attachment Individual Identifier (TAII). These fields carry the VSI-ID values for the two instances that are to be connected through the signaled pseudowire.

The detailed format for FEC 129 is shown in the following figure.

Figure 12. Generalized pseudowire-ID FEC element

Each of the FEC fields are designed as a sub-TLV equipped with its own type and length providing support for new applications. To accommodate the BGP AD information model the following FEC formats are used:

  • AGI (type 1) is identical in format and content with the BGP extended community attribute used to carry the VPLS-ID value.

  • Source AII (type 1) is a 4-byte value that carries the local VSI-id (outgoing NLRI minus the RD).

  • Target AII (type 1) is a 4-byte value that carries the remote VSI-ID (incoming NLRI minus the RD).

BGP-AD and Target LDP (T-LDP) interaction

BGP is responsible for discovering the location of VSIs that share the same VPLS membership. LDP protocol is responsible for setting up the pseudowire infrastructure between the related VSIs by exchanging service specific labels between them.

When the local VPLS information is provisioned in the local PE, the related PEs participating in the same VPLS are identified through BGP AD exchanges. A list of far-end PEs is generated and triggers the creation, if required, of the necessary T-LDP sessions to these PEs and the exchange of the service specific VPN labels. The steps for the BGP AD discovery process and LDP session establishment and label exchange are shown in the following figure.

Figure 13. BGP-AD and T-LDP interaction

Key:

  1. Establish I-BGP connectivity RR.

  2. Configure VPN (10) on edge node (PE3).

  3. Announce VPN to RR using BGP-AD.

  4. Send membership update to each client of the cluster.

  5. LDP exchange or inbound FEC filtering (IFF) of non-match or VPLS down.

  6. Configure VPN (10) on edge node (PE2).

  7. Announce VPN to RR using BGP-AD.

  8. Send membership update to each client of the cluster.

  9. LDP exchange or inbound FEC filtering (IFF) of non-match or VPLS down.

  10. Complete LDP bidirectional pseudowire establishment FEC 129.

SDP usage

Service Access Points (SAP) are linked to transport tunnels using Service Distribution Points (SDP). The service architecture of the 7210 platform allows services to be abstracted from the transport network.

MPLS transport tunnels are signaled using the Resource Reservation Protocol (RSVP-TE) or by the Label Distribution Protocol (LDP). The capability to automatically create an SDP only exists for LDP based transport tunnels. Using a manually provisioned SDP is available for both RSVP-TE and LDP transport tunnels. See the 7210 SAS-Mxp, R6, R12, S, Sx, T MPLS Guide for more information about MPLS, LDP, and RSVP.

Automatic creation of SDPs

When BGP AD is used for LDP VPLS and LDP is used as the transport tunnel there is no requirement to manually create an SDP. The LDP SDP can be automatically instantiated using the information advertised by BGP AD. This simplifies the configuration on the service node.

Enabling LDP on the IP interfaces connecting all nodes between the ingress and the egress, builds transport tunnels based on the best IGP path. LDP bindings are automatically built and stored in the hardware. These entries contain an MPLS label pointing to the best next hop along the best path toward the destination.

When two endpoints need to connect and no SDP exists, a new SDP is automatically constructed. New services added between two endpoints that already have an automatically created SDP are immediately used. No new SDP is constructed. The far-end information is gleaned from the BGP next hop information in the NLRI. When services are withdrawn with a BGP_Unreach_NLRI, the automatically established SDP remains up as long as at least one service is connected between those endpoints. An automatically created SDP is removed and the resources released when the only or last service is removed.

Manually provisioned SDP

The carrier is required to manually provision the SDP if they create transport tunnels using RSVP-TE. Operators have the option to choose a manually configured SDP, if they use LDP as the tunnel signaling protocol. The functionality is the same regardless of the signaling protocol.

Creating a BGP-AD enabled VPLS service on an ingress node with the manually provisioned SDP option causes the Tunnel Manager to search for an existing SDP that connects to the far-end PE. The far-end IP information is gleaned from the BGP next hop information in the NLRI. If a single SDP exists to that PE, it is used. If no SDP is established between the two endpoints, the service remains down until a manually configured SDP becomes active.

When multiple SDPs exist between two endpoints, the tunnel manager selects the appropriate SDP. The algorithm preferred SDPs with the best (lower) metric. Should there be multiple SDPs with equal metrics, the operational state of the SDPs with the best metric is considered. If the operational state is the same, the SDP with the higher SDP ID is used. If an SDP with a preferred metric is found with an operational state that is not active, the tunnel manager flags it as ineligible and restarts the algorithm.

Automatic instantiation of pseudowires (SDP bindings)

The choice of manual or auto provisioned SDPs has limited impact on the amount of required provisioning. Most of the savings are achieved through the automatic instantiation of the pseudowire infrastructure (SDP bindings). This is achieved for every auto-discovered VSIs through the use of the pseudowire template concept. Each VPLS service that uses BGP AD contains the ‟pw-template-binding” option defining specific Layer 2 VPN parameters. This command references a ‟pw-template” which defines the pseudowire parameters. The same ‟pwtemplate” may be referenced by multiple VPLS services. As a result, changes to these pseudowire templates have to be treated with great care as they may impact many customers at the same time.

The Nokia implementation provides for safe handling of pseudowire templates. Changes to the pseudowire templates are not automatically propagated. Tools are provided to evaluate and distribute the changes. The following command is used to distribute changes to a ‟pw-template” at the service level to one or all services that use that template.

tools perform service id 300 eval-pw-template 1 allow-service-impact

If the service ID is omitted, then all services are updated. The type of change made to the ‟pwtemplate” influences how the service is impacted:

  1. Adding or removing a split-horizon-group causes the router to destroy the original object and recreate using the new value.

  2. Changing parameters in the vc-type {ether | vlan} command requires LDP to resignal the labels.

Both of these changes affect the services. Other changes are not service affected.

Mixing statically configured and auto-discovered pseudowires in a VPLS service

The services implementation allows for manually provisioned and auto-discovered pseudowire (SDP bindings) to coexist in the same VPLS instance (for example, both FEC128 and FEC 129 are supported). This allows for gradual introduction of auto discovery into an existing VPLS deployment.

As FEC 128 and 129 represent different addressing schemes, it is important to make sure that only one is used at any point in time between the same two VPLS instances. Otherwise, both pseudowires may become active causing a loop that may adversely impact the correct functioning of the service. Nokia recommends that the FEC128 pseudowire be disabled as soon as the FEC129 addressing scheme is introduced in a portion of the network. Alternatively, RSTP may be used during the migration as a safety mechanism to provide additional protection against operational errors.

Resiliency schemes

The use of BGP-AD on the network side, or in the backbone, does not affect the different resiliency schemes Nokia has developed in the access network. This means that both Multi-Chassis Link Aggregation (MC-LAG) and Management-VPLS (M-VPLS) can still be used.

BGP-AD may coexist with Hierarchical-VPLS (H-VPLS) resiliency schemes (for example, dual homed MTU-s devices to different PE-rs nodes) using existing methods (M-VPLS and statically configured Active or Standby pseudowire endpoint).

If provisioned SDPs are used by BGP AD, M-VPLS may be employed to provide loop avoidance. However, it is currently not possible to auto-discover active or standby pseudowires and to instantiate the related endpoint.

Routed VPLS

Routed VPLS (R-VPLS) allows a VPLS instance to be associated with an IP interface.

Within an R-VPLS service, traffic with a destination MAC matching that of the associated IP interface is routed based on the IP forwarding table; all other traffic is forwarded based on the VPLS forwarding table.

In network mode, R-VPLS service can be associated with an IPv4 interface and supports static routing and other routing protocols. It can be used to provide a service to the customer or for in-band management of the node.

IES or VPRN IP interface binding

A standard IP interface within an existing IES or VPRN service context may be bound to a service name. A VPLS service only supports binding for a single IP interface.

While an IP interface may only be bound to a single VPLS service, the routing context containing the IP interface (IES or VPRN) may have other IP interfaces bound to other VPLS service contexts. That is, R-VPLS allows the binding of IP interfaces in IES or VPRN services to be bound to VPLS services.

Assigning a service name to a VPLS service

When a service name is applied to any service context, the name and service ID association is registered with the system. A service name cannot be assigned to more than one service ID. Special consideration is made for a service name that is assigned to a VPLS service that has the configure>service>vpls>allow-ip-int-binding command enabled. If a name is applied to the VPLS service while the flag is set, the system scans the existing IES services for an IP interface that is bound to the specified service name. If an IP interface is found, the IP interface is attached to the VPLS service associated with the name. Only one interface can be bound to the specified name.

If the allow-ip-int-binding command is not enabled on the VPLS service, the system does not attempt to resolve the VPLS service name to an IP interface. As soon as the allow-ip-int-binding flag is configured on the VPLS, the corresponding IP interface is adhered and become operational up. There is no need to toggle the shutdown or no shutdown command.

If an IP interface is not currently bound to the service name used by the VPLS service, no action is taken at the time of the service name assignment.

Service binding requirements

When the defined service name is created on the system, the system checks to ensure that the service type is VPLS. If the created service type is VPLS, the IP interface is eligible to enter the operationally upstate.

Bound service name assignment

When a bound service name is assigned to a service within the system, the system first checks to ensure the service type is VPLS. Secondly the system ensures that the service is not already bound to another IP interface through the service name. If the service type is not VPLS or the service is already bound to another IP interface through the service ID, the service name assignment fails.

A single VPLS instance cannot be bound to two separate IP interfaces.

Binding a service name to an IP interface

An IP interface within an IES or VPRN service context may be bound to a service name at anytime. Only one interface can be bound to a service. When an IP interface is bound to a service name and the IP interface is administratively up, the system scans for a VPLS service context using the name and takes the following actions:

  • If the name is not currently in use by a service, the IP interface is placed in an operationally down: Non-existent service name or inappropriate service type state.

  • If the name is currently in use by a non-VPLS service or the wrong type of VPLS service, the IP interface is placed in the operationally down: Non-existent service name or inappropriate service type state.

  • If the name is currently in use by a VPLS service without the allow-ip-int-binding flag set, the IP interface is placed in the operationally down: VPLS service allow-ip-intbinding flag not set state. There is no need to toggle the shutdown or no shutdown command.

  • If the name is currently in use by a valid VPLS service and the allow-ip-int-binding flag is set, the IP interface is eligible to be placed in the operationally up state depending on other operational criteria being met.

Routed VPLS specific ARP cache behavior

In typical routing behavior, the system uses the IP route table to select the egress interface, an ARP entry is used forward the packet to the appropriate Ethernet MAC. With routed VPLS, the egress IP interface may be represented by multiple egress (VPLS service SAPs).

The following table describes how the ARP cache and MAC FIB entry states interact.

Table 1. Routing behavior in R-VPLS and interaction ARP cache and MAC FIB
ARP cache entry MAC FIB entry Routing or system behavior

ARP Cache Miss (No Entry)

Known or

Unknown

Triggers a request to control plane ARP processing module, to send out an ARP request, out of all the SAPs. (also known as virtual ports) of the VPLS instance.

ARP Cache Hit

Known

Forward to specific VPLS virtual port or SAP.

Unknown

This behavior cannot happen typically in 7210 SAS, as and when a L2 entry is removed from the FDB, the matching MAC address is also removed from the ARP cache.

The allow-ip-int-binding VPLS flag

The allow-ip-int-binding flag on a VPLS service context is used to inform the system that the VPLS service is enabled for routing support. The system uses the setting of the flag as a key to determine what type of ports the VPLS service may span.

The system also uses the flag state to define which VPLS features are configurable on the VPLS service to prevent enabling a feature that is not supported when routing support is enabled.

Routed VPLS SAPs only supported on standard Ethernet ports

The allow-ip-int-binding flag is set (routing support enabled) on a VPLS service. SAPs within the service can be created on standard Ethernet ports.

LAG port membership constraints

If a LAG has a non-supported port type as a member, a SAP for the routing-enabled VPLS service cannot be created on the LAG. When one or more routing enabled VPLS SAPs are associated with a LAG, a non-supported Ethernet port type cannot be added to the LAG membership.

VPLS feature support and restrictions

When the allow-ip-int-binding flag is set on a VPLS service, the following features cannot be enabled (the flag also cannot be enabled while any of these features are applied to the VPLS service):

  • In network mode, SDPs used in spoke or mesh SDP bindings cannot be configured.

  • In network mode, the VPLS service type must be R-VPLS; no other VPLS service is allowed.

  • MVR from an R-VPLS SAP to another SAP is not supported.

  • Default QinQ SAPs are not supported in an R-VPLS service.

  • The allow-ip-int-binding command cannot be used in a VPLS service that is acting as the G.8032 control instance.

  • IPv4 filters (ingress and egress) can be used with R-VPLS SAPs. Additionally IP ingress override filters are supported, which affects the behavior of the IP filters attached to the R-VPLS SAPs.

  • MAC filters (ingress and egress) are not supported for use with R-VPLS SAPs.

  • A VPLS IP interface is not allowed in an R-VPLS service, and an R-VPLS service/SAP cannot be configured with a VPLS IP interface.

  • In network mode, the R-VPLS service can be configured only with access SAPs or with SAPs on hybrid ports (applies only to the 7210 SAS-R6 and 7210 SAS-R12).

  • In network mode, the VPLS service can use the following svc-sap-type values: any, null-star, and dot1q-preserve.

  • G.8032 or MVPLS/STP based protection mechanisms can be used with an R-VPLS service. A separate G.8032 control instance or a separate MVPLS/STP instance must be used and the R-VPLS SAPs must be associated with these control instances such that the R-VPLS SAP forwarding state is driven by the control instance protocols

  • IP multicast is not supported in an R-VPLS service.

  • IGMP snooping is supported in an R-VPLS service for 7210 SAS-R6 and 7210 SAS-R12.

  • DHCP snooping is not supported for the SAPs configured in an R-VPLS service. Instead, DHCP relay can be enabled on the IES service associated with the R-VPLS service.

  • In network mode, an R-VPLS SAP drops packets received with extra tags. That is, if a packet is received on a R-VPLS SAP, with number of tags greater than the SAP tags to which it is mapped, then it is dropped. This is true for all supported encapsulations (that is, null, dot1q, and QinQ encapsulations) of the port. For example, double-tagged packets received on a dot1q SAP configured in a R-VPLS service is dropped on ingress.

VPLS SAP ingress IP filter override

When an IP Interface is attached to a VPLS service context, the VPLS SAP provisioned IP filter for ingress routed packets may be optionally overridden to provide special ingress filtering for routed packets. This allows different filtering for routed packets and non-routed packets. The filter override is defined on the IP interface bound to the VPLS service name. A separate override filter may be specified for IPv4 packet types.

If a filter for a specific packet type (IPv4) is not overridden, the SAP specified filter is applied to the packet (if defined).

The following tables list ACL lookup behavior with and without ingress override filter attached to an IES interface in a R-VPLS service.

Table 2. ACL lookup behavior with ingress override filter attached to an IES interface in an R-VPLS service
Type of traffic SAP ingress IPv4 filter SAP egress IPv4 filter Ingress override IPv4 filter

Destination MAC != IES IP interface MAC

Yes

Yes

No

Destination MAC = IES IP interface MAC and Destination IP on same subnet as IES interface

No

No

Yes

Destination MAC = IES IP interface MAC and destination IP not on same subnet as IES IP interface and route to destination IP does not exist

No

No

No

Destination MAC = IES IP interface MAC and destination IP not on same subnet as IES IP interface and route to destination IP exists

No

No

Yes

Destination MAC = IES IP interface MAC and IP TTL = 1

No

No

No

Destination MAC = IES IP interface MAC and IPv4 packet with Options

No

No

No

Destination MAC = IES IP interface MAC and IPv4 Multicast packet

No

No

No

Table 3. ACL lookup behavior without ingress override filter attached to an IES interface in an R-VPLS service
Type of traffic SAP ingress IPv4 filter SAP egress IPv4 filter

Destination MAC != IES IP interface MAC

Yes

Yes

Destination MAC = IES IP interface MAC and Destination IP on same subnet as IES IP interface

Yes

No

Destination MAC = IES IP interface MAC and destination IP not on same subnet as IES IP interface and route to destination IP

does not exist

No

No

Destination MAC = IES IP interface MAC and destination IP not on same subnet as IES IP interface and route to destination IP exists

Yes

No

Destination MAC = IES IP interface MAC and IP TTL = 1

No

No

Destination MAC = IES IP interface MAC and IPv4 packet with Options

No

No

Destination MAC = IES IP interface MAC and IPv4 Multicast packet

No

No

QoS support for VPLS SAPs and IP interface in a routed VPLS service

The following information describes QoS support for VPLSs SAPs and IP interface in a routed VPLS service:

  • SAP ingress classification (IPv4 and MAC criteria) is supported for SAPs configured in the service. SAP ingress policies cannot be associated with IES IP interface.

  • On 7210 SAS-R6 and 7210 SAS-R12, when the node is operating in SAP based queuing mode, unicast traffic sent out of R-VPLS SAPs uses SAP based egress queues while BUM traffic sent out of R-VPLS SAPs uses per port egress queues. When the 7210 SAS-R6 and 7210 SAS-R12 node is operating in port based queuing mode, both unicast and BUM traffic sent out of R-VPLS SAPS uses per port egress queues. For more information, refer to the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide.

  • Port based Egress Marking is supported for both routed packets and bridged packets. The existing access egress QoS policy can be used for Dot1p marking and DSCP marking.

Routed VPLS supported routing related protocols

In network mode, R-VPLS is supported in both the base routing instances (IES) and VPRN services. IPv4 addressing is supported for IES and VPRN IP interfaces associated with an R-VPLS service. The following table lists the support available for routing protocols on IP interfaces bound to a VPLS service in network mode.

Table 4. Routing protocols on IP interfaces bound to a VPLS service
Services Network

Static-routing

Supported

BGP

Supported

OSPF

Supported

ISIS

Supported

BFD

Supported

VRRP

Supported

ARP and Proxy-Arp

Both are supported

DHCP Relay1

Supported

Spanning tree and split horizon

An R-VPLS context supports all spanning tree capabilities that a non-routed VPLS service supports. Service-based SHGs are not supported in an R-VPLS context.

Routed VPLS and IGMPv3 snooping

This feature (IGMPv3 snooping in R-VPLS) extends IGMP snooping to a routed VPLS service. On 7210 SAS, VPLS services that use MPLS uplinks (network mode) support IGMP snooping with IGMP v1 and v2 only. That is, IGMP v3 is not supported, which means that only Layer 2 multicast is supported. To support source-based IP multicast, support for IGMPv3 is needed. To provide source-based IP multicast, support for IGMP snooping v1, v2, and v3 is added to routed VPLS service. The IGMPv3 snooping in R-VPLS feature gives customers an option to use a routed VPLS service without a configured IP interface association to deliver IP multicast traffic in access Layer 2 networks. Users also have an option to configure MVR service.

IGMPv3 snooping in R-VPLS is supported only for IES (not for VPRNs).

For information about IGMP snooping in the context of VPLS, see IGMP snooping in VPLS service.

Configuration guidelines and restrictions for IGMP snooping in R-VPLS

The following items apply to IGMP snooping in R-VPLS and should be included with the regular VPLS multicast configuration guidelines (see Configuration guidelines for IGMP snooping in VPLS service and Routed VPLS supported functionality and restrictions):

  • R-VPLS without an IP interface association can be used to emulate VPLS service with support for IGMPv3 snooping.

  • R-VPLS with or without IP interface association can be used for IGMPv3 snooping. If enabling MVR on the service then the service should not have an IP interface association.

  • IGMPv3 snooping can be enabled in the context of the R-VPLS (both with and without MVR). It cannot be enabled in regular VPLS service. Regular VPLS service supports IGMP v1 and v2 only.

  • MVR can be configured in an R-VPLS without an IP interface association. It can be used to leak multicast traffic to a user R-VPLS service with an IP interface configuration. Therefore, a user R-VPLS can be used to forward both unicast and multicast services.

In addition, the following list of guidelines and restrictions pertain to IGMP snooping in an R-VPLS service:

  • R-VPLS service can only have a single SAP per port configured in a service. That is, two SAPs on the same port cannot be configured in the same service.

  • Spoke SDPs and mesh SDPs cannot be configured in an R-VPLS service.

  • On 7210 SAS devices, on ingress of a port, multicast traffic can be processed in the context of either igmp-snooping (Layer 2 Ethernet multicast with IGMP v1 or v2 snooping) or l3-multicast (either multicast in an Layer 3 service or IGMP snooping in an R-VPLS), but not both. That is, it is not possible to configure SAPs on the port such that one SAP is a receiver for multicast traffic to be processed by IGMP snooping, and another SAP is a receiver for multicast traffic to be processed by IP multicast in the context of Layer 3 service or R-VPLS. An option per port is available using the configure>port>ethernet>multicast-ingress {l2-mc | ip-mc} command to enable one or the other. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more information about this command. By default, IGMP snooping is enabled to be backward compatible. Users need to explicitly change the IGMP snooping configuration to allow processing of received multicast traffic as IP multicast in the context of Layer 3 service or R-VPLS.

  • If a VPLS SAP is configured on the same port as the port on which IP multicast is enabled, then multicast traffic received on the SAP is dropped. Unicast, broadcast, and unknown-unicast packets received on the SAP are forwarded appropriately. This behavior is true only for VPLS SAPs and does not apply to VPLS SDPs, Epipe SAPs, and Epipe SDPs.

  • With R-VPLS multicast, a port on which receivers are present can be configured to perform either Layer 2 multicast replication (that is, no IP TTL decrement and no source MAC replacement) or Layer 3 multicast replication (that is, IP TTL is decremented and source MAC is replaced with 7210 SAS chassis MAC or IP interface MAC). An option to use either Layer 2 or Layer 3 multicast replication is available using the configure>port>ethernet>multicast-egress {l2-switch | l3-forward} command. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more information about this command. All SAPs on the port have the same behavior.

  • An MVR R-VPLS must be configured without an IP interface and supports Layer 2 forwarding of both unicast and multicast traffic (that is, no IP forwarding).

  • A user R-VPLS can be configured with an IP interface and supports Layer 2 forwarding of both unicast and multicast (with (S,G) IP multicast replications) and supports Layer 3 forwarding of unicast traffic.

  • On 7210 SAS-R6, when using SAP-based egress queues and scheduler, R-VPLS BUM traffic uses per port egress queues—not per SAP egress queues.

  • In an MVR configuration, the svc-sap-type of the R-VPLS service that is the source (also known as MVR R-VPLS service) and the svc-sap-type of the R-VPLS service that is the sink (also known as user R-VPLS service) should match.

  • On 7210 SAS-R6 and 7210 SAS-R12, the MVR R-VPLS service configured with IGMPv3 snooping shares resources with TWAMP. An increase in one decreases the amount of resources available for the other. Contact your Nokia representative for more information about scaling of these features.

Routed VPLS supported functionality and restrictions

Routed VPLS supported functionality and restrictions for network mode are specified as follows:

  • Static ARP cannot be configured with an IES IP interface that is associated with an R-VPLS, though static MAC can be configured in an R-VPLS service.

  • In network mode, both static routing and dynamic routing protocols are supported.

  • Whenever a VPLS FIB entry is removed because of user action, aging or mac-move, the corresponding ARP entry whose MAC address matches that of the MAC in the FIB is removed from the ARP cache.

  • In network mode, R-VPLS is supported in both the base routing instance (IES) and VPRN services. IPv4 addressing is supported for IES and VPRN IP interfaces associated with an R-VPLS service.

  • IPv6 addressing support is not available for IES interfaces associated with an R-VPLS service.

  • In both network modes, multiple SAPs configured on the same port cannot be part of the same R-VPLS Service. That is, a single service can only be configured with a single SAP on a specific port.

  • Service MTU configuration is not supported in the R-VPLS service.

  • In network mode, in any service (that is, svc-sap-type set to any), null SAP accepts only untagged packets. Tagged packets received are dropped.

  • In network mode, MPLS protocols (For example: RSVP, LDP) cannot be enabled on R-VPLS IP interface

  • In network mode, MPLS-TP cannot use R-VPLS, IES, and IP interface.

  • In network mode, R-VPLS SAPS can be configured on a MC-LAG LAG.

  • The discard-unknown feature is not supported in the VPLS service associated with R-VPLS (only on 7210 SAS-R6 and 7210 SAS-R12).

  • In the saved configuration file, for the R-VPLS service, the R-VPLS service instance appears twice; one appearance for service creation and one with all the other configuration parameters. This is required to resolve references to the R-VPLS service and to execute the configuration without any errors.

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

Configuring a VPLS service with CLI

This section provides information to configure VPLS services using the command line interface.

Basic configuration

The following fields require specific input (there are no defaults) to configure a basic VPLS service:

  • Customer ID (see Configuring customer accounts).

  • For a local service, configure two SAPs, specifying local access ports and encapsulation values.

  • For a distributed service, configure a SAP and an SDP for each far-end node.

VPLS service on ALA-1

*A:ALA-1>config>service>vpls# info
----------------------------------------------
...
        vpls 9001 customer 6 create
            description "Local VPLS"
            stp
                shutdown
            exit
            sap 1/2/2:0 create
                description "SAP for local service"
            exit
            sap 1/1/5:0 create
                description "SAP for local service"
            exit
            no shutdown
----------------------------------------------
*A:ALA-1>config>service>vpls#
*A:ALA-1>config>service# info
----------------------------------------------
...
       vpls 7 customer 7 create
            stp
                shutdown
            exit
            sap 1/1/21 create
            exit
            sap lag-1:700 create
            exit
            no shutdown
        exit
...
----------------------------------------------
*A:ALA-1>config>service#

Distributed VPLS service between ALA-1, ALA-2, and ALA-3

*A:ALA-1>config>service# info
----------------------------------------------
...
        vpls 9000 customer 6 create
            shutdown
            description "This is a distributed VPLS."
            stp
                shutdown
            exit
            sap 1/1/5:16 create
                description "VPLS SAP"
            exit
            spoke-sdp 2:22 create
            exit
        exit
...
----------------------------------------------
*A:ALA-1>config>service#

*A:ALA-2>config>service# info
----------------------------------------------
...
        vpls 9000 customer 6 create
            description "This is a distributed VPLS."
            stp
                shutdown
            exit
            sap 1/1/5:16 create
                description "VPLS SAP"
            exit
            spoke-sdp 2:22 create
            exit
            no shutdown
        exit
...
----------------------------------------------
*A:ALA-2>config>service#

*A:ALA-3>config>service# info
----------------------------------------------
...
        vpls 9000 customer 6 create
            description "This is a distributed VPLS."
            stp
                shutdown
            exit
            sap 1/1/3:33 create
                description "VPLS SAP"
            exit
            spoke-sdp 2:22 create
            exit
            no shutdown
        exit
...
----------------------------------------------
*A:ALA-3>config>service#

Common configuration tasks

This section provides a brief overview of the tasks that must be performed to configure both local VPLS services and provides the CLI commands.

For VPLS services:


  1. Associate VPLS service with a customer ID.


  2. Define SAPs:

    • Select nodes and ports.

    • Optional - select QoS policies other than the default (configured in config>qos context).

    • Optional — select filter policies (configured in config>filter context).

    • Optional — select accounting policy (configured in config>log context).


  3. Modify STP default parameters (optional) (see VPLS and Spanning Tree Protocol).


  4. Enable service.

Configuring VPLS components

Creating a VPLS service

Use the following syntax to create a VPLS service.

    config>service# vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] description description-string
    no shutdown
Configured VPLS service
*A:ALA-1>config>service>vpls# info
----------------------------------------------
...
        vpls 1000 customer 1 create
            description "This is a VPLS with NULL SAP"
            stp
                shutdown
            exit
            no shutdown
        exit
        vpls 2000 customer 6 create
            description "This is a Distributed VPLS with DOT1Q SAP"
            stp
                shutdown
            exit
            no shutdown
        exit
...
----------------------------------------------
*A:ALA-1>config>service>vpls#
Enabling MAC move

The mac-move feature is useful to protect against undetected loops in your VPLS topology as well as the presence of duplicate MACs in a VPLS service. For example, if two clients in the VPLS have the same MAC address, the VPLS experiences a high relearn rate for the MAC and shuts down the SAP when the threshold is exceeded.

Use the following syntax to configure mac-move parameters. 

config>service# vpls service-id [customer customer-id] [vpn vpn-id] [m-vpls]
    mac-move
    move-frequency frequency
    retry-timeout timeout
    no shutdown
MAC move information
*A:ALA-1# show service id 6 all
....
*A:ALA-1#
-------------------------------------------------------------------------------
Forwarding Database specifics
-------------------------------------------------------------------------------
Service Id        : 1150                Mac Move          : Disabled           
Mac Move Rate     : 2                   Mac Move Timeout  : 10                 
Table Size        : 1000                Total Count       : 1000               
Learned Count     : 1000                Static Count      : 0                  
Remote Age        : 900                 Local Age         : 300                
High WaterMark    : 95%                 Low Watermark     : 90%                
Mac Learning      : Enabl               Discard Unknown   : Dsabl              
Mac Aging         : Enabl               Relearn Only      : True               
===============================================================================
....
*A:ALA-1#
Configuring STP bridge parameters in a VPLS

Modifying some of the Spanning Tree Protocol parameters allows the operator to balance STP between resiliency and speed of convergence extremes. Modifying particular parameters, mentioned as follows, must be done in the constraints of the following two formulae:

2 x (Bridge_Forward_Delay - 1.0 seconds) >= Bridge_Max_Age

Bridge_Max_Age >= 2 x (Bridge_Hello0_Time + 1.0 seconds)

STP always uses the locally configured values for the first three parameters (Admin State, Mode and Priority).

For the parameters Max Age, Forward Delay, Hello Time and Hold Count, the locally configured values are only used when this bridge has been elected root bridge in the STP domain, otherwise the values received from the root bridge are used. The exception to this rule is: when STP is running in RSTP mode, the Hello Time is always taken from the locally configured parameter. The other parameters are only used when running mode MSTP.

Bridge STP admin state

The administrative state of STP at the VPLS level is controlled by the shutdown command.

When STP on the VPLS is administratively disabled, any BPDUs are forwarded transparently through the 7210 SAS-R6 and 7210 SAS-R12. When STP on the VPLS is administratively enabled, but the administrative state of a SAP is down, BPDUs received on such a SAP are discarded.

config>service>vpls service-id# stp
    no shutdown
Mode

To be compatible with the different iterations of the IEEE 802.1D standard, the 7210 SAS-R6 and 7210 SAS-R12 support several variants of the Spanning Tree protocol:

  • rstp

    Rapid Spanning Tree Protocol (RSTP) compliant with IEEE 802.1D-2004 - default mode.

  • dot1w

    compliant with IEEE 802.1w

  • comp-dot1w

    operation as in RSTP but backwards compatible with IEEE 802.1w (this mode was introduced for interoperability with some MTU types).

  • mstp

    compliant with the Multiple Spanning Tree Protocol specified in IEEE 802.1Q REV/D5.0-09/2005. This mode of operation is only supported in an mVPLS.

  • pmstp

    compliant with the Multiple Spanning Tree Protocol specified in IEEE 802.1Q REV/D3.0-04/2005 but with some changes to make it backwards compatible to 802.1Q 2003 edition and IEEE 802.1w.

See section Spanning tree operating modes for details on these modes.

config>service>vpls service-id# stp
    mode {rstp | comp-dot1w | dot1w | mstp | pmstp}

Default: rstp

Bridge priority

The bridge-priority command is used to populate the priority portion of the bridge ID field within outbound BPDUs (the most significant 4 bits of the bridge ID). It is also used as part of the decision process when determining the best BPDU between messages received and sent.

All values are truncated to multiples of 4096, conforming with IEEE 802.1t and 802.1D-2004.

config>service>vpls service-id# stp
    priority bridge-priority

Range: 1 to 65535

Default: 32768

Restore Default: no priority

Max age

The max-age command indicates 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. Each 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 by the BPDUs. The default value of max-age is 20. This parameter can be modified within a range of 6 to 40, limited by the standard STP parameter interaction formulae.

config>service>vpls service-id# stp
    max-age max-info-age

Range: 6 to 40 seconds

Default: 20 seconds

Restore Default: no max-age

Forward delay

RSTP, as defined in the IEEE 802.1D-2004 standards, transitions to the forwarding state by a handshaking mechanism (rapid transition), without any waiting times. If handshaking fails (such as on shared links, as follows), 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 Ethernet bridges (for example, a shared 10/100BaseT segment). The port-type command is used to configure a link as point-to-point or shared (see section SAP link type).

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 variable depends on the STP operating mode of the VPLS instance:

  • In rstp mode, but only when the SAP has not fallen back to legacy STP operation, the value configured by the hello-time command is used.

  • In all other situations, the value configured by the forward-delay command is used.

    config>service>vpls service-id# stp
forward-delay seconds

Range: 4 to 30 seconds

Default: 15 seconds

Restore Default: no forward-delay

Hello time

The hello-time command configures the Spanning Tree Protocol (STP) hello time for the Virtual Private LAN Service (VPLS) STP instance.

The seconds parameter 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 value can also be used to calculate the bridge forward delay, see Forward delay.

config>service>vpls service-id# stp
    hello-time hello-time

Range: 1 to 10 seconds

Default: 2 seconds

Restore Default: no hello-time

Hold count

The hold-count command configures the peak number of BPDUs that can be transmitted in a period of one second.

config>service>vpls service-id# stp
    hold-count count-value

Range: 1 to 10

Default: 6

Restore Default: no hold-count

MST instances

You can create up to 15 MST-instances. They can range from 1 to 4094. By changing path-cost and priorities, you can make sure that each instance forms its own tree within the region, therefore making sure different VLANs follow different paths.

You can assign non overlapping VLAN ranges to each instance. VLANs that are not assigned to an instance are implicitly assumed to be in instance 0, which is also called the CIST. This CIST cannot be deleted or created.

The parameter that can be defined per instance are mst-priority and vlan-range:

  • mst-priority

    The bridge-priority for this specific mst-instance. It follows the same rules as bridge-priority. For the CIST, the bridge-priority is used.

  • vlan-range

    The VLANs are mapped to this specific mst-instance. If no VLAN-ranges are defined in any mst-instances, then all VLANs are mapped to the CIST.

MST max hops

The mst-max-hops command defines the maximum number of hops the BPDU can traverse inside the region. Outside the region max-age is used.

MST name

The MST name defines the name that the operator gives to a region. Together with MST revision and the VLAN to MST-instance mapping, it forms the MST configuration identifier. Two bridges that have the same MST configuration identifier form a region if they exchange BPDUs.

MST revision

The MST revision together with MST-name and VLAN to MST-instance mapping define the MST configuration identifier. Two bridges that have the same MST configuration identifier form a region if they exchange BPDUs.

Configuring a VPLS SAP

A default QoS policy is applied to each ingress SAP. Additional QoS policies can be configured in the config>qos context. There are no default filter policies. Filter policies are configured in the config>filter context and must be explicitly applied to a SAP.

Local VPLS SAPs

To configure a local VPLS service, enter the sap sap-id command twice with different port IDs in the same service configuration.

Local VPLS configuration
*A:ALA-1>config>service# info
----------------------------------------------
       vpls 1150 customer 1 create
            fdb-table-size 1000
            fdb-table-low-wmark 5
            fdb-table-high-wmark 80
            local-age 60
            stp
                shutdown
            exit
            sap 1/1/1:1155 create     
            exit
            sap 1/1/2:1150 create
            exit
            no shutdown
        exit
----------------------------------------------
*A:ALA-1>config>service#
Distributed VPLS SAPs

To configure a distributed VPLS service, you must configure service entities on originating and far-end nodes. You must use the same service ID on all ends (for example, create a VPLS service ID 9000 on ALA-1, ALA-2, and ALA-3). A distributed VPLS consists of a SAP on each participating node and an SDP bound to each participating node.

For SDP configuration information, see Configuring an SDP. For SDP binding information, see Configuring SDP bindings.

VPLS SAP configuration
*A:ALA-3>config>service# info
----------------------------------------------
      vpls 1150 customer 1 create
            fdb-table-size 1000
            fdb-table-low-wmark 5
            fdb-table-high-wmark 80
            local-age 60
            stp
                shutdown
            exit
            sap 1/1/1:1155 create     
            exit
            sap 1/1/2:1150 create
            exit
            no shutdown
        exit
----------------------------------------------
*A:ALA-3>config>service#
Configuring SAP-specific STP parameters

When a VPLS has STP enabled, each SAP within the VPLS has STP enabled by default.

SAP STP administrative state

The administrative state of STP within a SAP controls how BPDUs are transmitted and handled when received. The allowable states are:

  • SAP Admin Up

    The default administrative state is up for STP on a SAP. BPDUs are handled in the normal STP manner on a SAP that is administratively up.

  • SAP Admin Down

    An administratively down state allows a service provider to prevent a SAP from becoming operationally blocked. BPDUs do not originate out the SAP toward the customer.

  • If STP is enabled on VPLS level, but disabled on the SAP, received BPDUs are discarded. Discarding the incoming BPDUs allows STP to continue to operate within the VPLS service while ignoring the down SAP. The specified SAP is always in an operationally forwarding state.

Note: The administratively down state allows a loop to form within the VPLS.
config>service>vpls>sap>stp# 
    [no] shutdown

Range: shutdown or no shutdown

Default: no shutdown (SAP admin up)

SAP virtual port number

The virtual port number 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 it’s own virtual port number that is unique to every other SAP defined on the VPLS. The virtual port number is assigned at the time that the SAP is added to the VPLS.

Because the order in which SAPs are added to the VPLS is not preserved between reboots of the system, the virtual port number may change between restarts of the STP instance. To achieve consistency after a reboot, the virtual port number can be specified explicitly.

config>service>vpls>sap# stp
    port-num number

Range: 1 — 2047

Default: (automatically generated)

Restore Default: no port-num

SAP priority

SAP priority allows a configurable ‟tie breaking” parameter to be associated with a SAP. When configuration BPDUs are being received, the configured SAP priority is used in some circumstances to determine whether a SAP is 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. See SAP virtual port number for details on the virtual port number.

STP computes the actual SAP priority by taking the configured priority value and masking out the lower four bits. The result is the value that is stored in the SAP priority parameter. For example, if a value of 0 was entered, masking out the lower 4 bits would result in a parameter value of 0. If a value of 255 was entered, the result would be 240.

The default value for SAP priority is 128. This parameter can be modified within a range of 0 to 255, 0 being the highest priority. Masking causes the values actually stored and displayed to be 0 to 240, in increments of 16.

config>service>vpls>sap>stp#
    priority stp-priority

Range: 0 to 255 (240 largest value, in increments of 16)

Default: 128

Restore Default: no priority

SAP path cost

The SAP 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 incremental 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 the STP path cost is a purely static configuration.

The default value for SAP path cost is 10. This parameter can be modified within a range of 1 to 65535, 1 being the lowest cost. 

config>service>vpls>sap>stp#
    path-cost sap-path-cost

Range: 1 to 200000000

Default: 10

Restore Default: no path-cost

SAP edge port

The SAP edge-port command is used to reduce the time it takes a SAP to reach the forwarding state when the SAP is on the edge of the network, and therefore has no further STP bridge to handshake with.

The edge-port command is used to initialize the internal OPER_EDGE variable. At any time, when OPER_EDGE is false on a SAP, the normal mechanisms are used to transition to the forwarding state (see Forward delay). When OPER_EDGE is true, STP assumes that the remote end agrees to transition to the forwarding state without actually receiving a BPDU with an agreement flag set.

The OPER_EDGE variable is dynamically set to false if the SAP receives BPDUs (the configured edge-port value does not change). The OPER_EDGE variable is dynamically set to true if auto-edge is enabled and STP concludes there is no bridge behind the SAP.

When STP on the SAP is administratively disabled and re-enabled, the OPER_EDGE is reinitialized to the value configured for edge-port.

Valid values for SAP edge-port are enabled and disabled with disabled being the default.

config>service>vpls>sap>stp#
    [no] edge-port

Default: no edge-port

SAP auto edge

The SAP edge-port command is used to instruct STP to dynamically decide whether the SAP is connected to another bridge.

If auto-edge is enabled, and STP concludes there is no bridge behind the SAP, the OPER_EDGE variable is dynamically set to true. If auto-edge is enabled, and a BPDU is received, the OPER_EDGE variable is dynamically set to true (see SAP edge port).

Valid values for SAP auto-edge are enabled and disabled with enabled being the default.

config>service>vpls>sap>stp#
    [no] auto-edge

Default: auto-edge

SAP link type

The SAP link-type parameter instructs STP on the maximum number of bridges behind this SAP. If there is only a single bridge, transitioning to forwarding state is based on handshaking (fast transitions). If more than two bridges are connected by a shared media, their SAPs should all be configured as shared, and timer-based transitions are used.

Valid values for SAP link-type are shared and pt-pt with pt-pt being the default.

config>service>vpls>sap>stp#
    link-type {pt-pt|shared}

Default: link-type pt-pt

Restore Default: no link-type

MST instances

The SAP mst-instance command is used to create MST instances at the SAP level. MST instance at a SAP level can be created only if MST instances are defined at the service level.

The parameters that can be defined per instance are mst-path-cost and mst-port-priority:

  • mst-path-cost

    Specifies path-cost within a specific MST instance. The path-cost is proportional to link speed.

  • mst-port-priority

    Specifies the port priority within a specific MST instance.

STP SAP operational states

The operational state of STP within a SAP controls how BPDUs are transmitted and handled when received.

Operationally disabled

Operationally disabled is the normal operational state for STP on a SAP in a VPLS that has any of the following conditions:

  • VPLS state administratively down

  • SAP state administratively down

  • SAP state operationally down

If the SAP enters the operationally up state with the STP administratively up and the SAP STP state is up, the SAP transitions to the STP SAP discarding state.

When, during normal operation, the router detects a downstream loop behind a SAP, BPDUs can be received at a very high rate. To recover from this situation, STP transitions the SAP to disabled state for the configured forward-delay duration.

Operationally discarding

A SAP in the discarding state only receives and sends BPDUs, building the local correct STP state for each SAP while not forwarding actual user traffic. The duration of the discarding state is described in section Forward delay.

Note: In previous versions of the STP standard, the discarding state was called a blocked state.
Operationally learning

The learning state allows population of the MAC forwarding table before entering the forwarding state. In this state, no user traffic is forwarded.

Operationally forwarding

Configuration BPDUs are sent out a SAP in the forwarding state. Layer 2 frames received on the SAP are source learned and destination forwarded according to the FIB. Layer 2 frames received on other forwarding interfaces and destined for the SAP are also forwarded.

SAP BPDU encapsulation state

IEEE 802.1d (referred as dot1d) and Cisco per-VLAN Spanning Tree (PVST) BPDU encapsulations are supported on a per SAP basis. The STP is associated with a VPLS service like PVST is per VLAN. The difference between the two encapsulations is in the Ethernet and LLC framing and a type-length-value (TLV) field trailing the BPDU.The encapsulation format cannot be configured by the user; the system automatically determines the encapsulation format based on the BPDUs received on the port.

The following table shows differences between Dot1d and PVST Ethernet BPDU encapsulations based on the interface encap-type field:

Table 5. SAP BPDU encapsulation states
Field dot1d encap-type null dot1d encap-type dot1q PVST encap-type null PVST encap-type dot1q

Destination MAC

01:80:c2:00:00:00

01:80:c2:00:00:00

N/A

01:00:0c:cc:cc:cd

Source MAC

Sending Port MAC

Sending Port MAC

N/A

Sending Port MAC

EtherType

N/A

0x81 00

N/A

0x81 00

Dot1p and CFI

N/A

0xe

N/A

0xe

Dot1q

N/A

VPLS SAP ID

N/A

VPLS SAP encap value

Length

LLC Length

LLC Length

N/A

LLC Length

LLC DSAP SSAP

0x4242

0x4242

N/A

0xaaaa (SNAP)

LLC CNTL

0x03

0x03

N/A

0x03

SNAP OUI

N/A

N/A

N/A

00 00 0c (Cisco OUI)

SNAP PID

N/A

N/A

N/A

01 0b

CONFIG

Standard 802.1d

Standard 802.1d

N/A

Standard 802.1d

TLV: Type & Len

N/A

N/A

N/A

58 00 00 00 02

TLV: VLAN

N/A

N/A

N/A

VPLS SAP encap value

Padding

As Required

As Required

N/A

As Required

Each SAP has a Read-Only operational state that shows which BPDU encapsulation is currently active on the SAP. The states are:

  • Dot1d

    This state specifies that the switch is currently sending IEEE 802.1d standard BPDUs. The BPDUs are tagged or non-tagged based on the encapsulation type of the egress interface and the encapsulation value defined in the SAP. A SAP defined on an interface with encapsulation type dot1q continues in the dot1d BPDU encapsulation state until a PVST encapsulated BPDU is received, in which case the SAP converts to the PVST encapsulation state. Each received BPDU must be properly IEEE 802.1q tagged if the interface encapsulation type is defined as dot1q. PVST BPDUs are silently discarded if received when the SAP is on an interface defined with encapsulation type null.

  • PVST

    This state specifies that the switch is currently sending proprietary encapsulated BPDUs. PVST BPDUs are only supported on Ethernet interfaces with the encapsulation type set to dot1q. The SAP continues in the PVST BPDU encapsulation state until a dot1d encapsulated BPDU is received, in which case, the SAP reverts to the dot1d encapsulation state. Each received BPDU must be properly IEEE 802.1q tagged with the encapsulation value defined for the SAP. PVST BPDUs are silently discarded if received when the SAP is on an interface defined with a null encapsulation type.

Dot1d is the initial and only SAP BPDU encapsulation state for SAPs defined on Ethernet interface with encapsulation type set to null.

Configuring VPLS SAPs with per service split horizon

To configure a VPLS service with a split horizon group, add the split-horizon-group parameter when creating the SAP. Traffic arriving on a SAP within a split horizon group is not copied to other SAPs in the same split horizon group.

VPLS with split horizon enabled
*A:ALA-1>config>service# info
----------------------------------------------
...
vpls 800 customer 6001 vpn 700 create
description "VPLS with split horizon for DSL"
stp
shutdown
exit
sap 1/1/3:100 split-horizon-group DSL-group1 create
description "SAP for residential bridging"
exit
sap 1/1/3:200 split-horizon-group DSL-group1 create
description "SAP for residential bridging"
exit
split-horizon-group DSL-group1
description "Split horizon group for DSL"
exit
no shutdown
exit
...
----------------------------------------------
*A:ALA-1>config>service#

Configuring SDP bindings

VPLS provides scaling and operational advantages. A hierarchical configuration eliminates the need for a full mesh of VCs between participating devices. Hierarchy is achieved by enhancing the base VPLS core mesh of VCs with access VCs (spoke) to form two tiers. Spoke SDPs are generally created between Layer 2 switches and placed at the Multi-Tenant Unit (MTU). The PE routers are placed at the service provider's Point of Presence (POP). Signaling and replication overhead on all devices is considerably reduced.

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 SDPs or SAPs) and not transmitted on the port it was received (unless a split horizon group was defined on the spoke-SDP, see section Configuring VPLS spoke SDPs with split horizon).

A spoke-SDP connects a VPLS service between two sites and, in its simplest form, could be a single tunnel LSP. A set of ingress and egress VC labels are exchanged for each VPLS service instance to be transported over this LSP. The PE routers at each end treat this as a virtual spoke connection for the VPLS service in the same way as the PE-MTU connections. This architecture minimizes the signaling overhead and avoids a full mesh of VCs and LSPs between the two metro networks.

A VC-ID can be specified with the SDP-ID. The VC-ID is used instead of a label to identify a virtual circuit. The VC-ID is significant between peer SRs on the same hierarchical level. The value of a VC-ID is conceptually independent from the value of the label or any other datalink specific information of the VC.

Configuring VPLS spoke SDPs with split horizon

To configure spoke SDPs with a split horizon group, add the split-horizon-group parameter when creating the spoke-SDP. Traffic arriving on a SAP or spoke-SDP within a split horizon group is not copied to other SAPs or spoke SDPs in the same split horizon group.

VPLS with split horizon enabled
*A:ALA-1>config>service# info
----------------------------------------------
...
vpls 800 customer 6001 vpn 700 create
description "VPLS with split horizon for DSL"
stp
shutdown
exit
spoke-sdp 51:15 split-horizon-group DSL-group1 create
exit
split-horizon-group DSL-group1
description "Split horizon group for DSL"
exit
no shutdown
exit
...
----------------------------------------------
*A:ALA-1>config>service#

Configuring VPLS redundancy

This section describes the service management tasks.

Creating a management VPLS for SAP protection

This section provides a brief overview of the tasks that must be performed to configure a management VPLS for SAP protection and provides the CLI commands, see Example configuration for protected VPLS SAP. The following tasks should be performed on both nodes providing the protected VPLS service.

Before configuring a management VPLS, first read VPLS redundancy for an introduction to the concept of management VPLS and SAP redundancy:


  1. Create an SDP to the peer node.


  2. Create a management VPLS.


  3. Define a SAP in the m-vpls on the port. Note that the port must be dot1q. The SAP corresponds to the (stacked) VLAN on the 7210 SAS-R6 and 7210 SAS-R12 in which STP is active.


  4. Optionally modify STP parameters for load balancing (see Configuring load balancing with management VPLS).


  5. Create an SDP in the m-vpls using the SDP defined in Step 1. Ensure that this SDP runs over a protected LSP.


  6. Enable the management VPLS service and verify that it is operationally up.


  7. Create a list of VLANs on the port that are to be managed by this management VPLS.


  8. Create one or more user VPLS services with SAPs on VLANs in the range defined by Step 6.

    Figure 14. Example configuration for protected VPLS SAP
Creating a management VPLS for SAP protection

Use the following commands to create a management VPLS for SAP protection.

config>service# vpls service-id [customer customer-id] [create] [m-vpls] 
    description description-string
    sap sap-id create
    managed-vlan-list
        range vlan-range
            stp
            no shutdown

The following example shows output for a configured management VPLS.

*A:ALA-1>config>service# info
----------------------------------------------
        vpls 2000 customer 6 m-vpls create
            stp
                no shutdown
            exit
            sap 1/1/1:100 create
            exit
            sap 1/1/2:200 create
            exit
            sap 1/1/3:300 create
               managed-vlan-list
                  range 1-50
            exit
            no shutdown
        exit           
----------------------------------------------
*A:ALA-1>config>service#

Creating a management VPLS for spoke-SDP protection

This section provides a brief overview of the tasks that must be performed to configure a management VPLS for spoke-SDP protection and provides the CLI commands, see Example configuration for protected VPLS spoke-SDP. The following tasks should be performed on all four nodes providing the protected VPLS service.

Before configuring a management VPLS, please first read Configuring a VPLS SAP for an introduction to the concept of management VPLS and spoke-SDP redundancy:

  1. Create an SDP to the local peer node (node ALA-A2 in the following example).

  2. Create an SDP to the remote peer node (node ALA-B1 in the following example).

  3. Create a management VPLS.

  4. Create a spoke-SDP in the m-vpls using the SDP defined in Step 1. Ensure that this mesh spoke-SDP runs over a protected LSP (see following note).

  5. Enable the management VPLS service and verify that it is operationally up.

  6. Create a spoke-SDP in the m-vpls using the SDP defined in Step 2. Optionally, modify STP parameters for load balancing.

  7. Create one or more user VPLS services with spoke SDPs on the tunnel SDP defined by Step 2.

As long as the user spoke SDPs created in step 7are in this same tunnel SDP with the management spoke-SDP created in step 6, the management VPLS protect them.

Figure 15. Example configuration for protected VPLS spoke-SDP

Use the following CLI syntax to create a management VPLS for spoke-SDP protection:

config>service# sdp sdp-id mpls create
    far-end ip-address
    lsp lsp-name
    no shutdown
vpls service-id customer customer-id [m-vpls] create
    description description-string
    spoke-sdp sdp-id:vc-id create
    stp
    no shutdown
VPLS configuration output
*A:ALA-A1>config>service# info
----------------------------------------------
...
       sdp 100 mpls create
            far-end 10.0.0.30
            lsp "toALA-B1"
            no shutdown
       exit
       sdp 300 mpls create
            far-end 10.0.0.20
            lsp "toALA-A2"
            no shutdown
       exit
       vpls 101 customer 1 m-vpls create
            spoke-sdp 100:1 create
            exit
            spoke-sdp 300:1 create
            exit
            stp
            exit
            no shutdown
        exit
...
----------------------------------------------
*A:ALA-A1>config>service#

Configuring a BGP-auto-discovery

config>service# sdp-template sdp-template-id
config>service# l2-auto-bind policy-id [use-provisioned-sdp]

BGP-AD automatically creates SDP-bindings using a template to configure SDP-binding configuration parameters. L2-auto-bind is a command used to initiate a template that is used by BGP-AD for PW instantiation under related VPLS instances.

The template may be referenced in the ‟service vpls bgp-ad” object and used subsequently to instantiate PWs to a remote PE and VSI instance advertised through BGP Auto-Discovery. Changes to these dynamically created objects cannot be performed directly through CLI or SNMP. There are two possible methods to initiate the change:

  • Configure a new ‟l2-auto-bind” association under service>vpls>bgp-ad. This method is used when the existing policy is used by multiple VPLS services and only one or a few require the change.

  • Change the parameters of the current template. This method is used when a change in parameter is required for the majority of VPLS services that use the template.

Changes are not automatically propagated to the instantiated objects and must be done through one of two tool commands:

tools>perform>service# eval-pw-template policy-id [allow-service-impact]
tools>perform>service>id# eval-pw-template policy-id [allow-service-impact]

This command forces evaluation of changes that were made in the l2-auto-bind template indicated in the command. This command can be applied to an individual VPLS service or all VPLS services that reference the template if no service is specified.

The parameters are divided into three classes:

  • class 1 - modified at create time only

  • class 2 - modified only when the object is administratively shutdown

  • class 3 - no restrictions

Parameters that fall into class 1 destroy existing objects and recreate objects with the new values. Parameters in class 2 momentarily shutdown the object, change the parameter, then re-enable the object. Class 3 can be changed without affecting the operational status of the objects of service.

For the l2-auto-bind template, the parameters are treated as follows:

  • class 1 - adding or removing a split-horizon-group, switching between a manual and auto SDP

  • class 2 - changing the vc-type {ether | vlan}

  • class 3 - all other changes

The keyword allow-service-impact enables service impacting changes. If this keyword is not configured, an error message is generated if the parameter changes are service impacting.

Configuring load balancing with management VPLS

With the concept of management VPLS, it is possible to load balance the user VPLS services across the two protecting nodes. This is done by creating two management VPLS instances, where both instances have different active spokes (by changing the STP path-cost). When different user VPLS services are associated with either the two management VPLS services, the traffic is split across the two spokes.

Load balancing can be achieved in both the SAP protection and spoke-SDP protection scenarios. Example configuration for load balancing across two protected VPLS spoke SDPs shows an example with the following configuration.

  • Dut-C - spoke-SDP 

         mvpls 100
     MVPLS M1
     Dut-A — Spoke SDP 1201:100 (STP blocked); 1401:100
     Dut-B — Spoke SDP 1201:100; 2301:100

  • Dut-C - Spoke-SDP 1401:100; 2301:100

         uvpls 101
     UVPLS U1
     Dut-A — Spoke SDP 1201:101; 1401:101
     Dut-B — Spoke SDP 1201:101; 2301:101

  • Dut-C - Spoke-SDP 1401:101; 2301:101

         mvpls 200
     MVPLSM2 
     Dut-A — Spoke SDP 1202:200; 1402:200 (STP blocked)
     Dut-B — Spoke SDP 1202:200; 2302:200

  • Dut-C - Spoke-SDP 1402:200; 2302:200

         uvpls 201
     UVPLS U2
     Dut-A — Spoke SDP 1202:201; 1402:201
     Dut-B — Spoke SDP 1202:201; 2302:201
     Dut-C — Spoke SDP 1402:201; 2302:201
Figure 16. Example configuration for load balancing across two protected VPLS spoke SDPs

Use the following syntax to create a load balancing across two management VPLS instances:

config>service# sdp sdp-id mpls create
    far-end ip-address
    lsp lsp-name
    no shutdown
vpls service-id customer customer-id [m-vpls] create
    description description-string
    spoke-sdp sdp-id:vc-id create
    stp
        path-cost 
    stp
    no shutdown

The following examples show configurations for load balancing across two protected VPLS spoke SDPs.

ALA-B configuration

The configuration on ALA-B (7210), the upper left node is shown as follows. It is configured such that it becomes the root bridge for MVPLS 100 and MVPLS 200.

# MVPLS 100 configs

*A:ALA-B# configure service vpls 100 
*A:ALA-B>config>service>vpls# info 
----------------------------------------------
            description "Default tls description for service id 100"
            stp
                priority 0
                no shutdown
            exit
            spoke-sdp 1201:100 create
            exit
            spoke-sdp 2301:100 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-B>config>service>vpls#

# UVPLS 101 configs

*A:ALA-B>config>service# vpls 101 
*A:ALA-B>config>service>vpls# info 
----------------------------------------------

            description "Default tls description for service id 101"
            spoke-sdp 1201:101 create
            exit
            spoke-sdp 2301:101 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-B>config>service>vpls#

# MVPLS 200 configs
 
*A:ALA-B# configure service vpls 200 
*A:ALA-B>config>service>vpls# info 
----------------------------------------------
            description "Default tls description for service id 200"
            stp
                priority 0
                no shutdown
            exit
            spoke-sdp 1202:200 create
            exit
            spoke-sdp 2302:200 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-B>config>service>vpls#


# UVPLS 201 configs
*A:ALA-B>config>service# vpls 201 
*A:ALA-B>config>service>vpls# info 
----------------------------------------------

            description "Default tls description for service id 201"
            spoke-sdp 1202:201 create
            exit
            spoke-sdp 2302:201 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-B>config>service>vpls#
ALA-C configuration

The configuration on ALA-C (7210), the upper right node is shown as follows.

# MVPLS 100 configs

*A:ALA-C# configure service vpls 100 
*A:ALA-C>config>service>vpls# info 
----------------------------------------------

            description "Default tls description for service id 100"
            stp
                priority 4096
                no shutdown
            exit
            spoke-sdp 1401:100 create
            exit
            spoke-sdp 2301:100 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-C>config>service>vpls#


# UVPLS 101 configs

*A:ALA-C>config>service# vpls 101 
*A:ALA-C>config>service>vpls# info 
----------------------------------------------

            description "Default tls description for service id 101"
            spoke-sdp 1401:101 create
            exit
            spoke-sdp 2301:101 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-C>config>service>vpls#
# MVPLS 200 configs
 
*A:ALA-C# configure service vpls 200 
*A:ALA-C>config>service>vpls# info 
----------------------------------------------
            description "Default tls description for service id 200"
            stp
                priority 4096
                no shutdown
            exit
            spoke-sdp 1402:200 create
            exit
            spoke-sdp 2302:200 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-C>config>service>vpls# 


# UVPLS 201 configs

*A:ALA-C>config>service# vpls 201 
*A:ALA-C>config>service>vpls# info 
----------------------------------------------

            description "Default tls description for service id 201"
            spoke-sdp 1402:201 create
            exit
            spoke-sdp 2302:201 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-C>config>service>vpls#

Configuring selective MAC Flush

Use the following syntax to enable selective MAC Flush in a VPLS.

config>service# vpls service-id 
    send-flush-on-failure

Use the following syntax to disable selective MAC Flush in a VPLS.

config>service# vpls service-id 
    no send-flush-on-failure

Configuring IGMPv3 snooping in RVPLS

IGMPv3 snooping in RVPLS is supported only for IES (not for VPRNs).

Use the following syntax to configure IGMPv3 snooping in routed VPLS bound to an IES.

config>service# vpls service-id customer customer-id [svc-sap-type {any}] [b-vpls | i-vpls | r-vpls] create
    config>service>vpls# service-name service-name 
    config>service>vpls# allow-ip-int-bind 
    config>service>vpls>allow-ip-int-bind# exit 
    config>service>vpls# igmp-snooping 
    config>service>vpls>igmp-snooping# no shutdown
    config>service>vpls# exit 
    config>service>vpls# sap sap-id create
    config>service>vpls>sap# igmp-snooping 
    config>service>vpls>sap>igmp-snooping# mrouter-port 
    config>service>vpls>sap>igmp-snooping# exit 
    config>service>vpls>sap># exit 
    config>service>vpls># exit 
    config>service# ies service-id customer customer-id create
    config>service>ies# interface ip-int-name create
    config>service>ies>interface# address ip-address/mask 
    config>service>ies>interface# vpls service-name

RVPLS configuration using IGMPv3 snooping

#--------------------------------------------------
echo "Port Configuration"
#--------------------------------------------------

    ...snip...

    port 1/1/5
        ethernet
            mode hybrid
            access
            exit
            encap-type dot1q
            multicast-ingress ip-mc
        exit
        no shutdown
    exit

#--------------------------------------------------
#--------------------------------------------------
echo "Service Configuration"
#--------------------------------------------------
    service
        customer 1 create
            description "Default customer"
        exit
        ies 6 customer 1 create
            interface "IGMP-test" create
            exit
        exit

        ....snip

        vpls 3 customer 1 r-vpls svc-sap-type any create
            allow-ip-int-bind
            exit
            stp
                shutdown
            exit
            igmp-snooping
                no shutdown
            exit
            service-name "GS-IGMP-Snooping"
            sap 1/1/5:333 create
                igmp-snooping
                    mrouter-port
                exit
                ingress
                exit
                egress
                exit
            exit

        ....snip

        ies 6 customer 1 create
            interface "IGMP-test" create
                address 192.168.x.x/24
                vpls "GS-IGMP-Snooping"
                exit
            exit
            no shutdown
        exit
    exit
#--------------------------------------------------

Configuring BGP Auto-Discovery

This section provides important information to describe the different configuration options used to populate the required BGP AD and generate the LDP generalized pseudowire-ID FEC fields. There are a large number of configuration options that are available with the this feature. Not all these configurations option are required to start using BGP AD. A very simple configuration automatically generates the required values used by BGP and LDP. In most cases, deployments provide full mesh connectivity between all nodes across a VPLS instance. However, capabilities are available to influence the topology and build hierarchies or hub and spoke models.

Configuration steps

In the following figure, assume PE6 was previously configured with VPLS 100 as indicated by the configurations lines in the upper right. The BGP AD process commences after PE134 is configured with the VPLS 100 instance as shown in the upper left. This shows a very basic and simple BGP AD configuration. The minimum requirement for enabling BGP AD on a VPLS instance is configuring the VPLS-ID and point to a pseudowire template.

Figure 17. BGP AD configuration example

In many cases, VPLS connectivity is based on a pseudowire mesh. To reduce the configuration requirement, the BGP values can be automatically generated using the VPLS-ID and the MPLS router-ID. By default, the lower six bytes of the VPLS-ID are used to generate the RD and the RT values. The VSI-ID value is generated from the MPLS router-ID. All of these parameters are configurable and can be coded to suit requirements and build different topologies

A helpful command displays the service information, the BGP parameters and the SDP bindings in use. When the discovery process is completed successfully, each endpoint has an entry for the service.

PE134># show service l2-route-table

When only one of the endpoints has an entry for the service in the l2-routing-table, it is most likely a problem with the RT values used for import and export. This would most likely happen when different import and export RT values are configured using a router policy or the route-target command.

Service-specific commands continue to be available to display service-specific information, including status.

PERs6# show service sdp-using

BGP AD advertises the VPLS-ID in the extended community attribute, VSI-ID in the NLRI and the local PE ID in the BGP next hop. At the receiving PE, the VPLS-ID is compared against locally provisioned information to determine whether the two PEs share a common VPLS. If it is found that they do, the BGP information is used in the signaling phase.

Configuring AS pseudowire in VPLS

Figure 18. Sample topology-AS pseudowire in VPLS

In the preceding figure, a pseudowire is configured on MTU. The following example shows configuration output on the MTU.

MTU pseudowire configuration

*A:MTU>config>service>vpls# info 
----------------------------------------------
            send-flush-on-failure
            stp
                shutdown
            exit
            endpoint "vpls1" create
                description "vpls1_endpoint"
                revert-time 60
                ignore-standby-signaling
                no suppress-standby-signaling
                block-on-mesh-failure
            exit
            sap 1/1/3 create
            exit
            spoke-sdp 301:1 endpoint "vpls1" create
                stp
                    shutdown
                exit
                block-on-mesh-failure
            exit
            spoke-sdp 302:1 endpoint "vpls1" create
                stp
                    shutdown          
                exit
                block-on-mesh-failure
            exit
            no shutdown
----------------------------------------------
*A:MTU>config>service>vpls#

Service management tasks

Modifying VPLS service parameters

You can change existing service parameters. The changes are applied immediately. To display a list of services, use the show>service>service-using vpls command. Enter the parameter such as description SAP and then enter the new information.

Modifying VPLS service parameters

*A:ALA-1>config>service>vpls# info
----------------------------------------------
            description "This is a different description."
            disable-learning
            disable-aging
            discard-unknown
            local-age 500
            stp
                shutdown
            exit
            sap 1/1/5:22 create
                description "VPLS SAP"
            exit
            exit
            no shutdown
----------------------------------------------
*A:ALA-1>config>service>vpls#

Modifying management VPLS parameters

To modify the range of VLANs on an access port that are to be managed by an existing management VPLS, first the new range should be entered and afterwards the old range removed. If the old range is removed before a new range is defined, all customer VPLS services in the old range become unprotected and may be disabled.

config>service# vpls service-id 
    - sap sap-id
        - managed-vlan-list
            - [no] range vlan-range

Deleting a management VPLS

As with normal VPLS service, a management VPLS cannot be deleted until SAPs and SDPs are unbound (deleted), interfaces are shutdown, and the service is shutdown on the service level.

Use the following syntax to delete a management VPLS service.

config>service
    - [no] vpls service-id
    - shutdown
    - [no] sap sap-id
        - shutdown

Disabling a management VPLS

You can shut down a management VPLS without deleting the service parameters.

When a management VPLS is disabled, all associated user VPLS services are also disabled (to prevent loops). If this is not wanted, first unmanage the user VPLS service by removing them from the managed-vlan-list.

config>service
    vpls service-id
    shutdown

Disabling a management VPLS

config>service# vpls 1
config>service>vpls# shutdown
config>service>vpls# exit

Deleting a VPLS service

A VPLS service cannot be deleted until SAPs and SDPs are unbound (deleted), interfaces are shutdown, and the service is shutdown on the service level.

Use the following syntax to delete a VPLS service.

config>service
    [no] vpls service-id 
    shutdown
    [no] spoke-sdp sdp-id 
        shutdown
    sap sap-id 
    no sap sap-id 
        shutdown

Disabling a VPLS service

Use the following syntax to shut down a VPLS service without deleting the service parameters. 

config>service> vpls service-id 
    [no] shutdown

Disabling a VPLS service

config>service# vpls 1
config>service>vpls# shutdown
config>service>vpls# exit

Re-enabling a VPLS service

Use the following syntax to re-enable a VPLS service that was shut down. 

config>service> vpls service-id 
    [no] shutdown

Re-enabling a VPLS service

config>service# vpls 1
config>service>vpls# no shutdown
config>service>vpls# exit

VPLS services command reference

Command hierarchies

VPLS configuration commands

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - [no] allow-ip-int-bind
            - bgp
                - pw-template-binding policy-id [split-horizon-group group-name] [import-rt {ext-community...(up to 5 max)}]
                - no pw-template-binding policy-id
                - route-distinguisher [ip-addr:comm-val | as-number:ext-comm-val]
                - no route-distinguisher
                - route-target {ext-community | {[export ext-community] [import ext-community]}}
                - no route-target
                - vsi-export policy-name [policy-name...(up to 5 max)]
                - no vsi-export
                - vsi-import policy-name [policy-name...(up to 5 max)]
                - no vsi-import
            - [no] bgp-ad
                - [no] shutdown
                - vpls-id vpls-id
                - vsi-id
                    - prefix low-order-vsi-id
                    - no prefix
            - description description-string
            - no description
            - [no] disable-aging 
            - [no] disable-learning 
            - [no] discard-unknown 
            - endpoint endpoint-name [create]
            - no endpoint
                - block-on-mesh-failure
                - [no] block-on-mesh-failure
                - description description-string
                - no description
                - [no] ignore-standby-signaling
                - [no] mac-pinning
                - max-nbr-mac-addr table-size
                - no max-nbr-mac-addr
                - revert-time revert-time | infinite
                - no revert-time
                - static-mac ieee-address [create]
                - no static-mac
                - [no] suppress-standby-signaling
            - eth-cfm
                - no vpls-sap-bidir
                - vpls-sap-bidir
            - [no] fdb-table-high-wmark high-water-mark
            - [no] fdb-table-low-wmark low-water-mark
            - fdb-table-size table-size 
            - no fdb-table-size [table-size]
            - local-age aging-timer 
            - no local-age
            - [no] mac-move
                - move-frequency frequency
                - no move-frequency
                - retry-timeout timeout
                - no retry-timeout
                - [no] shutdown
            - [no] propagate-mac-flush
            - remote-age aging-timer
            - no remote-age
            - [no] send-flush-on-failure
            - service-mtu octets
            - no service-mtu
            - service-mtu-check octets
            - no service-mtu-check
            - no root-guard 
            - [no] shutdown
            - split-horizon-group group-name [create] 
                - description description-string
                - no description

VPLS xSTP commands

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - stp
                - forward-delay forward-delay 
                - no forward-delay
                - hello-time hello-time
                - no hello-time
                - hold-count BDPU tx hold count
                - no hold-count
                - max-age max-age 
                - no max-age
                - mode {rstp | comp-dot1w | dot1w | mstp | pmstp}
                - no mode
                - [no] mst-instance mst-inst-number 
                    - mst-port-priority bridge-priority
                    - no mst-port-priority
                    - [no] vlan-range vlan-range
                - mst-max-hops hops-count
                - no mst-max-hops
                - mst-name region-name
                - no mst-name
                - mst-revision revision-number
                - no mst-revision
                - priority bridge-priority
                - no priority
                - [no] shutdown

VPLS SAP DHCP snooping commands

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index]
            - no sap sap-id 
                - dhcp
                    - description description-string
                    - no description
                    - [no] option
                        - action [dhcp-action]
                        - no action
                        - [no] circuit-id [ascii-tuple | vlan-ascii-tuple]
                        - [no] remote-id [mac | string string]
                        - [no] vendor-specific-option
                            - [no] client-mac-address
                            - [no] sap-id
                            - [no] service-id
                            - string text
                            - no string
                            - [no] system-id
                    - [no] shutdown
                    - [no] snoop

VPLS SAP commands

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [create] [capture-sap] [eth-ring ring-index] [g8032-shg-enable]
            - no sap sap-id 
                - accounting-policy acct-policy-id
                - no accounting-policy
                - bpdu-translation {auto | pvst | stp}
                - no bpdu-translation
                - [no] collect-stats
                - description description-string
                - no description
                - [no] disable-aging 
                - [no] disable-learning 
                - [no] discard-unknown-source
                - dist-cpu-protection policy-name
                - no dist-cpu-protection
                - eth-cfm
                    - mep mep-id domain md-index association ma-index [direction {up | down}] primary-vlan-enable 
                    - no mep mep-id domain md-index association ma-index
                        - [no] ais-enable
                            - client-meg-level [level [level...]]
                            - no client-meg-level
                            - [no] description
                            - interval 
                            - no interval
                            - priority priority-value
                            - no priority
                        - [no] ccm-enable
                        - ccm-ltm-priority priority
                        - no ccm-ltm-priority
                        - description description-string
                        - no description
                        - [no] eth-test-enable
                            - test-pattern {all-zeros | all-ones} [crc-enable]
                            - no test-pattern
                        - low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
                        - mac-address mac-address
                        - no mac-address
                        - one-way-delay-threshold seconds
                        - [no] shutdown
                    - mip [mac mac address] 
                    - mip default-mac
                    - no mip
                    - mip [mac mac address] [primary-vlan-enable vlan-id]
                    - mip default-mac [primary-vlan-enable vlan-id]
                    - no mip [primary-vlan-enable vlan-id]
                - l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp]
                - no l2pt-termination
                - limit-mac-move [blockable | non-blockable]
                - no limit-mac-move
                - [no] mac-pinning
                - max-nbr-mac-addr table-size
                - no max-nbr-mac-addr
                - managed-vlan-list
                    - default-sap
                    - no default-sap
                    - no range vlan-range
                    - range vlan-range

VPLS SAP filter and QoS commands

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index] [create]
            - no sap sap-id 
                - egress 
                    - agg-rate-limit [cir cir-rate] [pir pir-rate]
                    - no agg-rate-limit 
                    - aggregate-meter-rate rate-in-kbps [burst burst-in-kbits] [enable-stats]
                    - no aggregate-meter-rate
                    - filter ip ip-filter-id
                    - filter ipv6 ipv6 -filter-id 
                    - filter mac mac-filter-id
                    - no filter [ip ip-filter-id] [ipv6 ipv6 -filter-id] [mac mac-filter-id]
                    - qos policy-id 
                    - no qos
                - ingress 
                    - aggregate-meter-rate rate-in-kbps [burst burst-in-kbits] 
                    - no aggregate-meter-rate
                    - filter ip ip-filter-id
                    - filter [ipv6 ipv6-filter-id] 
                    - filter mac mac-filter-id
                    - no filter [ip ip-filter-id] [ ipv6 ipv6-filter-id] [mac mac-filter-id]
                    - qos policy-id [enable-table-classification] 
                    - no qos

VPLS SAP IGMP snooping and MVR commands

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - igmp-snooping
                - mvr 
                    - description description-string
                    - no description
                    - group-policy policy-name
                    - no group-policy
                    - no shutdown
                    - shutdown
                - query-interval interval 
                - no query-interval
                - no query-src-ip
                - query-src-ip ip-address
                - no report-src-ip
                - report-src-ip ip-address
                - robust-count count
                - no robust-count
                - no shutdown
                - shutdown
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index]
            - no sap sap-id 
                - igmp-snooping
                    - [no] fast-leave
                    - import policy-name
                    - no import
                    - last-member-query-interval interval
                    - no last-member-query-interval
                    - max-num-groups max-num-groups
                    - no max-num-groups
                    - max-num-sources max-num-sources 
                    - no max-num-sources 
                    - [no] mrouter-port
                    - mvr 
                        - from-vpls service-id
                        - no from-vpls
                        - to-sap sap-id
                        - no to-sap
                    - query-interval interval 
                    - no query-interval
                    - query-response-interval interval 
                    - no query-response-interval
                    - robust-count count
                    - no robust-count
                    - [no] send-queries
                    - static
                        - [no] group group-address
                            - [no] source ip-address 
                            - [no] starg
                    - version version
                    - no version
            - mfib-table-high-wmark high-water-mark
            - no mfib-table-high-wmark
            - mfib-table-low-wmark low-water-mark
            - no mfib-table-low-wmark
            - mfib-table-size table-size
            - no mfib-table-size

VPLS SAP meter override commands 

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index]
            - no sap sap-id 
                - ingress
                    - meter-override
                        - meter meter-id [create]
                        - no meter meter-id
                            - adaptation-rule [pir adaptation-rule] [cir adaptation-rule]
                            - cbs size [kbits | bytes | kbytes] 
                            - no cbs
                            - mbs size [kbits | bytes | kbytes] 
                            - no mbs
                            - mode mode
                            - no mode
                            - rate cir cir-rate [pir pir-rate]

VPLS SAP queue override commands 

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index] [create]
            - no sap sap-id 
                - ingress
                    - queue-override
                        - queue queue-id [create]
                            - adaptation-rule [pir adaptation-rule] [cir adaptation-rule]
                            - no port-parent
                            - port-parent [cir-level cir-level] [pir-weight pir-weight]
                            - queue-mgmt name
                            - no queue-mgmt
                            - no rate
                            - rate [cir cir-rate] [pir pir-rate]

VPLS SAP xSTP commands 

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index]
            - no sap sap-id 
                - stp
                    - [no] auto-edge
                    - [no] edge-port
                    - link-type {pt-pt | shared}
                    - no link-type [pt-pt | shared]
                    - mst-instance mst-inst-number
                        - mst-path-cost inst-path-cost
                        - no mst-path-cost
                        - mst-port-priority stp-priority
                        - no mst-port-priority
                    - path-cost sap-path-cost
                    - no path-cost
                    - [no] port-num virtual-port-number 
                    - priority stp-priority
                    - no priority
                    - [no] shutdown
                - tod-suite tod-suite-name
                - no tod-suite

VPLS SAP statistics commands 

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index] [create]
            - no sap sap-id 
                - statistics
                    - ingress
                        - counter-mode {in-out-profile-count | forward-drop-count}
                        - [no] drop-count-extra-vlan-tag-pkts

VPLS mesh SDP commands

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}]
            - no mesh-sdp sdp-id[:vc-id]
                - accounting-policy acct-policy-id
                - no accounting-policys
                - [no] collect-stats
                - [no] control-word
                - description description-string
                - no description
                - egress 
                    - no vc-label [egress-vc-label] 
                - eth-cfm
                    - mep mep-id domain md-index association ma-index [direction {up}{down}]
                    - no mep mep-id domain md-index association ma-index
                        - [no] ais-enable
                            - client-meg-level [[level [level...]]
                            - no client-meg-level
                            - interval {1 | 60}
                            - no interval
                            - priority priority-value
                            - no priority
                        - [no] ccm-enable
                        - ccm-ltm-priority priority
                        - no ccm-ltm-priority
                        - [no] description description-string
                        - [no] eth-test-enable
                            - test-pattern {all-zeros | all-ones} [crc-enable]
                            - no test-pattern
                        - low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
                        - mac-address mac-address
                        - no mac-address
                        - one-way-delay-threshold seconds
                        - [no] shutdown
                - [no] force-vlan-vc-forwarding
                - hash-label
                - hash-label [signal-capability]
                - no hash-label
                - igmp-snooping
                    - import policy-name
                    - no import
                    - last-member-query-interval interval
                    - no last-member-query-interval
                    - max-num-groups max-num-groups
                    - no max-num-groups
                    - [no] mrouter-port
                    - query-interval interval
                    - no query-interval 
                    - query-response-interval interval
                    - no query-response-interval 
                    - robust-count count
                    - no robust-count 
                    - [no] send-queries 
                    - static
                        - [no] group grp-ip-address
                        - [no] starg
                    - version version
                    - no version
                - ingress
                    - vc-label egress-vc-label
                - [no] mac-pinning
                - [no] static-mac ieee-address 
                - [no] shutdown vlan-vc-tag vlan-id
                - no vlan-vc-tag [vlan-id]

VPLS spoke-SDP commands

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [split-horizon-group group-name] [use-evpn-default-shg] 
            - no spoke-sdp sdp-id[:vc-id] 
                - accounting-policy acct-policy-id
                - no accounting-policy
                - [no] block-on-mesh-failure
                - bpdu-translation {auto | pvst | stp}
                - no bpdu-translation
                - [no] collect-stats
                - [no] control-word
                - description description-string
                - no description
                - [no] disable-aging 
                - [no] disable-learning 
                - [no] discard-unknown-source
                - eth-cfm
                    - mep mep-id domain md-index association ma-index [direction {up}{down}]
                        - no mep mep-id domain md-index association ma-index[no] ais-enable
                            - client-meg-level [[level [level...]]
                            - no client-meg-level
                            - interval {1 | 60}
                            - no interval
                            - priority priority-value
                            - no priority
                        - [no] ccm-enable
                        - ccm-ltm-priority priority
                        - no ccm-ltm-priority
                        - [no] description description string[
                        - no] eth-test-enable
                            - test-pattern {all-zeros | all-ones} [crc-enable]
                        - no test-patternlow-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
                        - mac-address mac-address
                        - no mac-addressone-way-delay-threshold seconds
                        - [no] shutdown
                    - mip [mac mac address]
                    - mip default-mac
                    - no mip
                - egress 
                    - vc-label egress-vc-label
                    - no vc-label [egress-vc-label] 
                - [no] force-vlan-vc-forwarding
                - hash-label [signal-capability]
                - no hash-label
                - igmp-snooping
                    - import policy-name
                    - no import
                    - last-member-query-interval interval
                    - no last-member-query-interval
                    - max-num-groups max-num-groups
                    - no max-num-groups
                    - [no] mrouter-port
                    - query-interval interval
                    - no query-interval 
                    - query-response-interval interval
                    - no query-response-interval 
                    - robust-count count
                    - no robust-count 
                    - [no] send-queries 
                    - static
                        - [no] group group-address
                            - [no] starg
                    - version version
                    - no version
                - [no] ignore-standby-signaling
                - ingress
                    - vc-label egress-vc-label
                    - no vc-label [egress-vc-label] 
                - [no] l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp]
                - limit-mac-move [blockable | non-blockable]
                - no limit-mac-move
                - [no] mac-pinning
                - max-nbr-mac-addr table-size
                - no max-nbr-mac-addr
                - precedence precedence-value | primary
                - no precedence
                - [no] pw-path-id
                    - agi agi
                    - no agi
                    - saii-type2 global-id:node-id:ac-id
                    - no saii-type2
                    - taii-type2 global-id:node-id:ac-id
                    - no taii-type2
                - [no] pw-status-signaling
                - [no] shutdown
                - [no] static-mac ieee-address 
                - stp
                    - [no] auto-edge
                    - [no] edge-port
                    - link-type {pt-pt | shared}
                    - no link-type [pt-pt | shared]
                    - path-cost sap-path-cost
                    - no path-cost
                    - [no] port-num virtual-port-number 
                    - priority stp-priority
                    - no priority
                    - no root-guard
                    - root-guard
                    - [no] shutdown
                - vlan-vc-tag vlan-id
                - no vlan-vc-tag [vlan-id]

Routed VPLS commands

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]
        - no vpls service-id
            - [no] allow-ip-int-bind

Show commands

show
    - service
        - egress-label egress-label1 [egress-label2]
        - fdb-info
        - fdb-mac ieee-address [expiry]
        - id service-id
            - all
            - base [msap] [bfd]
            - dhcp
                - statistics [sap sap-id] [interface interface-name]
                - summary [interface interface-name | saps]
            - endpoint [endpoint-name]
            - fdb [sap sap-id] [expiry]] | [mac ieee-address [expiry]] | [detail] [expiry] 
            - igmp-snooping
                - all
                - base
                - mvrmrouters [detail]
                - port-db sap sap-id [detail]
                - port-db sap sap-id group grp-address
                - port-db sdp sdp-id:vc-id [detail]
                - port-db sdp sdp-id:vc-id group grp-address
                - proxy-db [detail]
                - proxy-db [group grp-ip-address]
                - querier 
                - static [sap sap-id]
                - statistics[sap sap-id | sdp sdp-ic:vc-id]
            - labels
            - l2pt disabled
            - l2pt [detail]
            - mac-move
            - mfib [brief] 
            - mfib [group grp-address | mstp-configuration]
            - sap [sap-id [detail]]
            - sdp [sdp-id | far-end ip-addr] [detail]
            - split-horizon-group [group-name]
            - stp 
        - ingress-label start-label [end-label]
        - sap-using [sap sap-id]
        - sap-using [ingress | egress] filter filter-id
        - sap-using [ingress | egress] qos-policy qos-policy-id
        - sap-using [ingress | egress] 
        - sdp [sdp-id | far-end ip-address] [detail | keep-alive-history]
        - sdp-using [sdp-id[:vc-id] | far-end ip-address]
        - service-using [vpls]

Clear commands

clear
    - service
        - id service-id
            - fdb {all | mac ieee-address | sap sap-id | mesh-sdp sdp-id[:vc-id] | spoke-sdp sdp-id:vc-id}
            - igmp-snooping
                - port-db sap sap-id [group grp-address]
                - port-db sdp sdp-id:vc-id [group grp-ip-address]
                - querier
            - mesh-sdp sdp-id[:vc-id] ingress-vc-label
                - spoke-sdp sdp-id:vc-id ingress-vc-label
            - spoke-sdp sdp-id[:vc-id]
            - stp
                - detected-protocols [all | sap sap-id]
        - statistics
            - id service-id
                - counters
                - mesh-sdp sdp-id[:vc-id] {all | counters | stp}
                - spoke-sdp sdp-id[:vc-id] {all | counters | stp | l2pt}
                - stp
            - sap sap-id {all | counters | stp}

Debug commands

debug
    - service 
        - id service-id
            - [no] event-type {config-change | svc-oper-status-change | sap-oper-status-change | sdpbind-oper-status-change}
            - [no] sap sap-id

Command descriptions

VPLS configuration commands

Generic commands
shutdown
Syntax

[no] shutdown

Context

config>service>vpls

config>service>vpls>snooping

config>service>vpls>igmp-snooping

config>service>vpls>sap

config>service>vpls>sap>dhcp

config>service>vpls>sap>stp

config>service>vpls>stp

config>service>vpls>spoke-sdp>stp

config>service>vpls>bgp-ad

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

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

description
Syntax

description description-string

no description

Context

config>service>vpls

config>service>vpls>split-horizon-group

config>service>vpls>igmp-snooping>mvr

config>service>vpls>sap

config>service>vpls>sap>dhcp

config>service>vpls>spoke-sdp config>service>pw-template>split-horizon-group

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters
description-string

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, etc.), the entire string must be enclosed within double quotes.

dhcp
Syntax

dhcp

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure DHCP parameters.

action
Syntax

action {replace | drop | keep}

no action

Context

config>service>vpls>sap>dhcp>option

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Default

no action

Parameters
replace

Keyword to specify that, in the upstream direction (from the user), the Option 82 field from the router is inserted in the packet (overwriting any existing Option 82 field). In the downstream direction (toward the user) the Option 82 field is stripped (in accordance with RFC 3046).

drop

Keyword to specify that the DHCP packet is dropped if an Option 82 field is present, and a counter is incremented.

keep

Keyword to specify that the existing information is kept in the packet and the router does not add any more information. In the downstream direction, the Option 82 field is not stripped and is forwarded toward the client.

The behavior is slightly different in the case of Vendor Specific Options (VSOs). When the keep parameter is specified, the router inserts its own VSO into the Option 82 field. This is done only when the incoming message already has an Option 82 field.

If no Option 82 field is present, the router does not create the Option 82 field. In this case, no VSO is added to the message.

circuit-id
Syntax

circuit-id [ascii-tuple | vlan-ascii-tuple]

no circuit-id

Context

config>service>vpls>sap>dhcp>option

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

When enabled, the router sends an ASCII-encoded tuple in the circuit-id sub-option of the DHCP packet. This ASCII-tuple consists of the access-node-identifier, service-id, and SAPID, separated by ‟|”. If no keyword is configured, the circuit-id sub-option is not part of the information option (Option 82).

When this command is configured without parameters, it is the equivalent of circuit-id ascii-tuple.

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

By default, if any of the other options are configured (for example, remote-id or vso),circuit-id is enabled.

Default

no circuit-id

Parameters
ascii-tuple

Specifies that the ASCII-encoded concatenated tuple is used, which consists of the access-node-identifier, service-id, and interface-name.

hex

Specifies the circuit-id hex string.

vlan-ascii-tuple

Specifies that the format includes VLAN ID and dot1p bits, in addition to what is already included in the ascii-tuple. The format is supported on dot1q and qinq encapsulated ports only. Therefore, when the Option 82 bits are stripped, dot1p bits are copied to the Ethernet header of an outgoing packet.

option
Syntax

[no] option

Context

config>service>vpls>sap>dhcp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables DHCP Option 82 (Relay Agent Information Option) parameters processing and enables the context for configuring Option 82 sub-options.

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

Default

no option

remote-id
Syntax

remote-id [mac | string string]

no remote-id

Context

config>service>vpls>sap>dhcp>option

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

When enabled, the router sends the MAC address of the remote end (typically the DHCP client) in the remote-id sub-option of the DHCP packet. This command identifies the host at the other end of the circuit.

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

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

Default

remote-id

Parameters
mac

Keyword to specify that the MAC address of the remote end is encoded in the sub-option.

string string

Specifies the remote-id.

vendor-specific-option
Syntax

[no] vendor-specific-option

Context

config>service>vpls>sap>dhcp>option

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

client-mac-address
Syntax

[no] client-mac-address

Context

config>service>vpls>sap>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

sap-id
Syntax

[no] sap-id

Context

config>service>vpls>sap>dhcp>option>vendor config>service>ies>sap>dhcp>option>vendor config>service>vprn>sap>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

service-id
Syntax

[no] service-id

Context

config>service>vpls>sap>dhcp>option>vendor config>service>ies>sap>dhcp>option>vendor config>service>vprn>sap>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

string
Syntax

[no] string text

Context

config>service>vpls>sap>dhcp>option>vendor config>service>ies>sap>dhcp>option>vendor config>service>vprn>sap>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters
text

Specifies a string that can be any combination of ASCII characters up to 32 characters. If spaces are used in the string, enclose the entire string in quotation marks (‟ ”).

system-id
Syntax

[no] system-id

Context

config>service>vpls>sap>dhcp>option>vendor config>service>ies>sap>dhcp>option>vendor config>service>vprn>sap>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

relay-plain-bootp
Syntax

relay-plain-bootp

no relay-plain-bootp

Context

config>service>ies>if>dhcp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the relaying of plain BOOTP packets.

The no form of this command disables the relaying of plain BOOTP packets.

server
Syntax

server server1 [server2...(up to 8 max)]

Context

config>service>ies>if>dhcp

config>service>vprn>if>dhcp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies a list of servers to which requests are forwarded. The list of servers can be entered as either IP addresses or fully qualified domain names. There must be at least one server specified for DHCP relay to work. If there are multiple servers, the request is forwarded to all the servers in the list.

A maximum of 8 DHCP servers can be configured.

Default

no server

Parameters
server

Specifies the DHCP server IP address.

trusted
Syntax

[no] trusted

Context

config>service>ies>if>dhcp

config>service>vprn>if>dhcp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables relaying of untrusted packets.

The no form of this command disables the relay.

Default

not enabled

snoop
Syntax

[no] snoop

Context

config>service>vpls>sap>dhcp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures DHCP snooping of DHCP messages on the SAP. Enabling DHCP snooping on VPLS interfaces (SAPs) is required where vendor-specific information (as per RFC 4243) is to be inserted into the Option 82 field of the DHCP messages. This includes interfaces that are 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.

Note: DHCP snooping for SDP is not supported on the platforms as described in this document.
Default

no snoop

VPLS commands
vpls
Syntax

vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [r-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [customer-vid vlan-id] [allow-l2pt-xstp-bpdu enable | disable]

vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [customer-vid vlan-id] [svc-sap-type {null-star | dot1q-preserve | any}] [r-vpls]

no vpls service-id

Context

config>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates or edits a VPLS instance.

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, acting as 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 parameter must be specified to 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 command is optional for navigating into the service configuration context. Editing a service with the incorrect customer-id value 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 and SDPs defined within the service ID have been shut down and deleted, and the service has been shut down.

Parameters
service-id

Specifies the unique service identification number identifying the service in the service domain. This ID must be unique to this service and may not be used for another service of any type. The service-idmust be the same number used for every 7210 SAS on which this service is defined.

Values

1 to 2147483647

customer customer-id

Specifies the customer ID number to be associated with the service. This parameter is required on service creation and is optional for service editing or deleting.

Values

1 to 2147483647

m-vpls

Specifies a management VPLS.

r-vpls

Specifies to associate this VPLS instance with an IP interface to provide RVPLS functionality.

allow-l2pt-xstp-bpdu enable | disable

Specifies to allow the users to reserve resources for xSTP, L2PT, and BPDU services. Only if the service is created with this parameter, can the user later turn on the xSTP, L2PT, and BPDU features in the service. If not, all attempts to use these features fails.

create

Mandatory keyword while creating a VPLS service. The create keyword requirement can be enabled or disabled using the environment>create context.

vpn vpn-id

Specifies the VPN ID number, which allows you to identify virtual private networks (VPNs).

Values

1 to 2147483647

Default

null (0)

customer-vid vlan-id

Defines the dot1q VLAN ID to be specified while creating the local dot1q SAP for the svc-sap-type dot1q-preserve command.

Values

1 to 4094

svc-sap-type

Specifies the type of service and allowed SAPs in the service.

Values

dot1q-preserve — Keyword to specify that the allowed SAP in the service are dot1q. The dot1q ID is not stripped after packets matches the SAP. This option is supported only when the r-vpls keyword is specified.

null-star — Keyword to specify that the allowed SAP in the service, which can be null SAPs, dot1q default, Q.* SAP,0.* SAP or Default QinQ SAP. This option is supported only when the r-vpls keyword is specified.

any — Keyword to specify that, for network mode, all supported SAPs are allowed in the service. See section QinQ SAP configuration restrictions for 7210 SAS in network mode only for information about restrictions related to QinQ SAPs.

Default

any

bgp
Syntax

bgp

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure the BGP-related parameters to BGP AD.

block-on-mesh-failure
Syntax

[no] block-on-mesh-failure

Context

config>service>vpls>spoke-sdp

config>service>vpls>endpoint

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables blocking (brings the entity to an operationally down state) after all configured mesh-SDPs are in operationally down state. This event is signaled to corresponding T-LDP peers by withdrawing the service label (status-bit-signaling non-capable peer) or by setting the ‟PW not forwarding” status bit in the T-LDP message (status-bit-signaling capable peer).

Default

disabled

bpdu-translation
Syntax

bpdu-translation {auto | pvst | stp}

no bpdu-translation

Context

config>service>vpls>spoke-sdp

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the translation of BPDUs to a specific format, meaning that all BPDUs transmitted on a specific SAP or spoke-SDP have a specified format.

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

Default

no bpdu-translation

Parameters
auto

Keyword to specify the format is detected automatically, based on the type of BPDUs received on the port.

pvst

Keyword to specify the BPDU format as PVST. The correct VLAN tag is included in the payload, depending on the encapsulation value of the outgoing SAP.

stp

Keyword to specify the BPDU format as STP.

l2pt-termination
Syntax

l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp]

no l2pt-termination

Context

config>service>vpls>sap config>service>vpls>spoke-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Default

no l2pt-termination

Parameters
cdp

Keyword to specify the Cisco discovery protocol.

dtp

Keyword to specify the dynamic trunking protocol.

pagp

Keyword to specify the port aggregation protocol.

stp

Keyword to specify all spanning tree protocols: stp, rstp, mstp, pvst (default).

udld

Keyword to specify unidirectional link detection.

vtp

Keyword to specify the VLAN trunking protocol.

disable-aging
Syntax

[no] disable-aging

Context

config>service>vpls

config>service>vpls>sap

config>template>vpls-template config>service>pw-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Like in 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 VPLS Forwarding Database (FDB). The disable-aging command 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.

Default

no disable-aging

disable-learning
Syntax

[no] disable-learning

Context

config>service>vpls config>service>pw-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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 not entered in the VPLS service forwarding database.

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

This command is mainly used in conjunction with the disable-learning command.

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

Default

no disable-learning

discard-unknown
Syntax

[no] discard-unknown

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

By default, packets with unknown destination MAC addresses are flooded. If this command is enabled at the VPLS level, packets with unknown destination MAC address are dropped instead (even when the configured FIB size limits for VPLS or SAP are not yet reached).

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

Default

no discard-unknown

vpls-sap-bidir
Syntax

no vpls-sap-bidir

vpls-sap-bidir

Context

config>service>vpls>eth-cfm

Platforms

7210 SAS-R6 and 7210 SAS-R12 IMMv2

Description

This command links the MEP with the primary VLAN configured under the bridge-identifier for the MA. MEPs cannot be changed from or to primary VLAN functions. This must be configured as part of the creation step and can be changed only by deleting the MEP and recreating it.

This command is used to enable both the ingress and egress MIP functionality for a VPLS SAP.

Before enabling both Ingress and egress MIP functionality, the user must allocate sufficient resources in the egress-internal-tcam resource pool using the configure system resource-profile egress-internal-tcam eth-cfm bidir-mip-egress command. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information.

The following describes the behavior for this command:

  • MIP creation (without PVLAN enabled) is enabled under SAP with vpls-sap-bidir enabled and with either default or explicit mode configured for mhf-creation

    In this case, both ingress MIP and egress MIP are created; a MIP (ingress and egress) is created at the level greater than the highest level MEP configured for the VPLS SAP.

  • MIP creation (without PVLAN enabled) is enabled under SAP with vpls-sap-bidir disabled and with either default or explicit mode configured for mhf-creation

    In this case, only an ingress MIP is created; a MIP (ingress only) is created at the level greater than the highest level MEP configured for the VPLS SAP.

  • MIP creation (without PVLAN enabled) is enabled under SDP-Binding (that is, spoke-SDP/mesh-SDP) with vpls-sap-bidir enabled or disabled and with either default or explicit mode configured for mhf-creation

    In this case, only ingress MIP is created; a MIP (ingress only) is created at the level greater than the highest level MEP configured for the VPLS SDB binding.

  • MIP creation (with PVLAN enabled) is enabled under SAP with vpls-sap-bidir enabled or disabled and with either default or explicit mode configured for mhf-creation

    In this case, both ingress MIP and egress MIP are created; a MIP (ingress and egress) is created at the level greater than the highest level MEP configured for the VPLS SAP.

  • vpls-sap-bidir is enabled in a service and there are previously created and configured ingress MIPs (without PVLAN enabled) for any SAPs configured in the service

    In this case, those MIPS are automatically converted to ingress and egress MIPs, assuming sufficient resources are allocated in the egress-internal-tcam resource pool for this feature. If sufficient resources are not available, attempting to enable the vpls-sap-bidir command fails.

  • vpls-sap-bidir is enabled in a service and there are previously created and configured ingress MIPs (without PVLAN enabled) for any SDP bindings configured in the service

    In this case, those MIPS continue to function as ingress MIPs. That is, the vpls-sap-bidir has no effect on MIPs configured on SDP bindings.

  • vpls-sap-bidir is enabled in a service and there are previously created and configured ingress MIPs with PVLAN enabled for any SAP configured in the service

    In this case, those MIPS continue to function as both ingress MIP and egress MIP. That is, the vpls-sap-bidir setting has no effect on MIPs with primary VLAN enabled and configured on SAPs.

Default

no vpls-sap-bidir

endpoint
Syntax

endpoint endpoint-name [create]

no endpoint

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a service endpoint.

Parameters
endpoint-name

Specifies an endpoint name up to 32 characters.

create

Mandatory keyword for creating a service endpoint.

description
Syntax

description description-string

no description

Context

config>service>vpls>endpoint

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Parameters
description-string

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.

ignore-standby-signaling
Syntax

[no] ignore-standby-signaling

Context

config>service>vpls>endpoint

config>service>vpls>spoke-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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 present at the endpoint level and at 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 becomes 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.

Default

disabled

revert-time
Syntax

revert-time revert-time | infinite

no revert-time

Context

config>service>vpls>endpoint

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the time to wait before reverting to primary spoke-SDP.

In a regular endpoint, the revert-time setting affects only the pseudowire defined as primary (precedence 0). For a failure of the primary pseudowire followed by restoration, the revert-timer is started. After it expires, the primary pseudowire takes the active role in the endpoint. This behavior does not apply for case where both pseudowires are defined as secondary; for example, if the active secondary pseudowire fails and is restored, it stays in standby until a configuration change or a force command occurs.

Parameters
revert-time

Specifies the time to wait, in seconds, before reverting back to the primary spoke-SDP defined on this service endpoint, after having failed over to a backup spoke-SDP.

Values

0 to 600

infinite

Keyword that makes the endpoint non-revertive.

split-horizon-group
Syntax

split-horizon-group group-name [create]

Context

config>service>vpls config>service>pw-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a new split horizon group (SHG) for the VPLS instance. Traffic arriving on a SAP or spoke-SDP within this SHG are 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:

  • On the 7210 SAS-R6 with IMM (v1 cards) and IMM-c cards, service-based SHGs and mesh-SDPs are mutually exclusive in a VPLS service.

  • On the 7210 SAS-R6 and 7210 SAS-R12 with IMM-b cards, an SHG can be used with spoke-SDPs or mesh-SDPs configured in the service.

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

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

Parameters
group-name

Specifies the name of the split horizon group to which the SAP or spoke-SDP belongs.

create

Mandatory keyword to create a split-horizon group.

static-mac
Syntax

static-mac ieee-address [create]

no static-mac

Context

config>service>vpls>endpoint

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command assigns a static MAC address to the endpoint. In the FDB, the static MAC is then associated with the active spoke-SDP.

Parameters
ieee-address

Specifies the static MAC address to the endpoint. This value cannot be all zeros.

Values

6-byte mac-address (xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx)

create

Mandatory keyword for creating a static MAC.

suppress-standby-signaling
Syntax

[no] suppress-standby-signaling

Context

config>service>vpls>endpoint

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

When this command is enabled, the pseudowire standby bit (with value 0x00000020) is not sent to T-LDP peer when the specific spoke is selected as a standby. This allows faster switchover as the traffic is sent over this SDP and discarded at the blocking side of the connection. This is particularly applicable to multicast traffic.

Default

enabled

fdb-table-high-wmark
Syntax

[no] fdb-table-high-wmark high-water-mark

Context

config>service>vpls

config>template>vpls-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the upper threshold value for FDB entries. The high-water-mark is configured as a percentage of the FDB. When the number of FDB entries exceeds the high-water-mark, the system raises a log event.

Parameters
high-water-mark

Specifies the upper threshold for FDB entries, which when exceeded, causes the system to raise a log event.

Values

0 to 100

Default

95%

fdb-table-low-wmark
Syntax

[no] fdb-table-low-wmark low-water-mark

Context

config>service>vpls

config>template>vpls-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the lower threshold value for FDB entries. The low-water-mark is configured as a percentage of the FDB. When the number of FDB entries drops below the low-water-mark, the system raises a log event.

Parameters
low-water-mark

Specifies the lower threshold for FDB entries, which when dropped below, causes the system to raise a log event.

Values

0 to 100

Default

90%

fdb-table-size
Syntax

fdb-table-size table-size

no fdb-table-size [table-size]

Context

config>service>vpls

config>template>vpls-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

The fdb-table-size specifies the maximum number of FDB entries for both learned and static MAC addresses for the VPLS instance.

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

Default

fdb-table-size 250

Parameters
table-size

Specifies the maximum number of MAC entries in the FDB.

vsi-export
Syntax

vsi-export policy-name [policy-name...(up to 5 max)]

no vsi-export

Context

config>service>vpls>bgp-ad config>service>vpls>bgp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the name of the VSI export policies to be used for BGP auto-discovery, if this feature 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.

vsi-import
Syntax

vsi-import policy-name [policy-name...(up to 5 max)]

no vsi-import

Context

config>service>vpls>bgp-ad>vsi-id config>service>vpls>bgp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the name of the VSI import policies to be used for BGP auto-discovery, if this feature 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.

route-target
Syntax

route-target {ext-community | {[export ext-community][import ext-community]}}

no route-target

Context

config>service>vpls>bgp-ad config>service>vpls>bgp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

The following rules apply.

  • If BGP AD VPLS-id is configured and no RT is configured under the BGP node: RT = VPLS-ID.

  • If BGP AD VPLS-id is not configured, an RT value must be configured under the BGP node. (This is the case when only BGP VPLS is configured.)

  • If BGP AD VPLS-id is configured and an RT value is also configured under the BGP node, the configured RT value prevails.

Parameters
export ext-community

Specifies communities allowed to be sent to remote PE neighbors.

import ext-community

Specifies communities allowed to be accepted from remote PE neighbors.

pw-template-binding
Syntax

pw-template-binding policy-id [split-horizon-group group-name] [import-rt {ext-community,...(up to 5 max)}]

no pw-template-bind policy-id

Context

config>service>vpls>bgp-ad

config>service>vpls>bgp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command binds the advertisements received with the RT that match 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.

The pw-template-binding 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.

Parameters
policy-id

Specifies an existing policy ID.

Values

1 to 2147483647

split-horizon-group group-name

Specifies the group name that overrides the split horizon group template settings.

import-rt ext-comm

Specifies communities allowed to be accepted from remote PE neighbors. An extended BGP community in the type:x:y format. The value x can be an integer or IP address.

The type can be the target or origin; x and y are 16-bit integers.

Values

ip-addr:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val

where:

ip-addr — IP address in the form a.b.c.d.

comm-val — 0 to 65535

2byte-asnumber — 0 to 65535

ext-comm-val — 0 to 4294967295

4byte-asnumber — 0 to 4294967295

target:{ip-addr:comm-val| 2byte-asnumber:ext-comm-val|4byte-asnumber:comm-val} ip-addr a.b.c.d

route-distinguisher
Syntax

route-distinguisher [rd]

no route-distinguisher

Context

config>service>vpls>bgp-ad>vsi-id

config>service>vpls>bgp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the Route Distinguisher (RD) component that is signaled in the MPBGP NLRI for L2VPN AFI. This value is used for BGP-AD, if this feature is configured in the VPLS service.

If this command is not configured, the RD is automatically built using the BGP-AD VPLS ID. The following rules apply:

  • If BGP AD VPLS-id is configured and no RD is configured under BGP node: RD = VPLS-ID.

  • If BGP AD VPLS-id is not configured, an RD value must be configured under BGP node. (This is the case when only BGP VPLS is configured.)

  • If BGP AD VPLS-id is configured and an RD value is also configured under BGP node, the configured RD value prevails

The values and format consist of 6 bytes, where the other 2 bytes of type is automatically generated.

Parameters
rd

Specifies the RD component in one of the following forms:

  • ip-addr:comm-val

  • 2byte-asnumber:ext-comm-val

  • 4byte-asnumber:comm-val

Values

ip-addr — IP address in the form a.b.c.d.

comm-val — 0 to 65535

2byte-asnumber — 1 to 65535

ext-comm-val — 0 to 4294967295

4byte-asnumber — 0 to 4294967295

local-age
Syntax

local-age aging-timer

no local-age

Context

config>service>vpls

config>template>vpls-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies 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 Service Access Point (SAP). MACs associated with a SAP are classified as local MACs, and MACs associated with are remote MACs.

Like in 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 to the default value.

Default

local-age 300

Parameters
aging-timer

Specifies the aging time for local MACs, in seconds.

Values

60 to 86400

mac-move
Syntax

[no] mac-move

Context

config>service>vpls

config>template>vpls-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures 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, the mac-move command 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. A SAP can be marked 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 is disabled instead.

The mac-move command enables the feature at the service level for SAPs; 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 is 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) the mac-move command 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 occur in the first second if the real relearn rate is 5 relearns per second or higher.

The no form of this command disables the mac-move command.

move-frequency
Syntax

move-frequency frequency

no move-frequency

Context

config>service>vpls>mac-move

config>template>vpls-template>mac-move

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Default

move-frequency 2

Parameters
frequency

Specifies the rate, in 5-second intervals, for the maximum number of relearns.

Values

1 to 100

retry-timeout
Syntax

retry-timeout timeout

no retry-timeout

Context

config>service>vpls>mac-move

config>template>vpls-template>mac-move

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Nokia recommends that the retry-timeout value be larger 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 zero value indicates that the SAP is not automatically re-enabled after being disabled. If, after the SAP is re-enabled it is disabled again, the effective retry timeout is doubled to avoid thrashing.

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

Default

retry-timeout 10

Parameters
timeout

Specifies the time, in seconds, to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

Values

0 to 120

mfib-table-high-wmark
Syntax

[no] mfib-table-high-wmark high-water-mark

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters
high-water-mark

Specifies the MFIB high watermark as a percentage.

Values

1 to 100

Default

95%

mfib-table-low-wmark
Syntax

[no] mfib-table-low-wmark low-water-mark

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters
low-water-mark

Specifies the multicast FIB low watermark as a percentage.

Values

1 to 100

Default

90%

mfib-table-size
Syntax

mfib-table-size table-size

no mfib-table-size

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Parameters
table-size

Specifies the maximum number of (s,g) entries allowed in the MFIB.

Values

1 to 1024

remote-age
Syntax

remote-age seconds

no remote-age

Context

config>service>vpls

config>template>vpls-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies 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 or an SDP. MACs associated with a SAP are called local MACs, and MACs associated with an SDP are called remote MACs.

Like in 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 with a value larger than the local-age timer.

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

Default

remote-age 900

Parameters
seconds

Specifies the aging time for remote MACs, in seconds.

Values

60 to 86400

send-flush-on-failure
Syntax

[no] send-flush-on-failure

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Default

no send-flush-on-failure

service-mtu
Syntax

service-mtu octets

no service-mtu

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

When 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 service-mtu value for the indicated service type to the default.

Note:

To disable service MTU check, run 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.

Default

service-mtu 1514

Parameters
octets

Specifies the size of the MTU in octets, expressed as a decimal integer. The following table displays MTU values for specific VC types.

Table 6. MTU values for VC types
VC-type Example service MTU Advertised MTU

Ethernet

1514

1500

Ethernet (with preserved dot1q)

1518

1504

VPLS

1514

1500

VPLS (with preserved dot1q)

1518

1504

VLAN (dot1p transparent to MTU value)

1514

1500

VLAN (QinQ with preserved bottom Qtag)

1518

1504
Values

1 to 9194

service-mtu-check
Syntax

[no] service-mtu-check

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command, when disabled, allows the packets to pass to the egress if the packet length is less than or equal to the MTU configured on the port. The length of the packet sent from a SAP is limited only by the access port MTU. In case of a pseudowire, the length of a packet is limited by the network port MTU (including the MPLS encapsulation).

The no form of this command disables the service MTU check.

Note: If TLDP is used for signaling, the configured value for service-mtu is used during a pseudowire setup.
Default

enabled

root-guard
Syntax

[no] root-guard

Context

config>service>vpls>sap>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no root-guard

tod-suite
Syntax

tod-suite tod-suite-name

no tod-suite

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no tod-suite

Parameters
tod-suite-name

Specifies the collection of policies (ACLs, QoS), including time-ranges, that define the full or partial behavior of a SAP. The suite can be applied to more than one SAP.

vsi-id
Syntax

vsi-id

Context

config>service>vpls>bgp-ad

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure the Virtual Switch Instance Identifier (VSI-ID).

prefix
Syntax

prefix low-order-vsi-id

no prefix

Context

config>service>vpls>bgp-ad>vsi-id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Default

no prefix

Parameters
low-order-vsi-id

Specifies a unique VSI-ID.

Values

ip-addr — a.b.c.d

raw-prefix — 0 to 4294967295

VPLS STP commands
stp
Syntax

stp

Context

config>service>vpls

config>service>vpls>sap

config>template>vpls-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure the Spanning Tree Protocol (STP) parameters.

The Nokia STP is the Spanning Tree Protocol (STP) with 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.

auto-edge
Syntax

auto-edge

no auto-edge

Context

config>service>vpls>sap>stp

config>service>vpls>spoke-sdp>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Default

auto-edge

edge-port
Syntax

[no] edge-port

Context

config>service>vpls>sap>stp

config>service>vpls>spoke-sdp>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Initially, the value of the SAP parameter is set to edge-port. This value changes in the following circumstances:

  • a BPDU is received on that port. This means that there is another bridge connected to this port; in this case, the edge-port becomes disabled.

  • auto-edge is configured and no BPDU is received within a specified period of time; RSTP concludes that it is on an edge and enables the edge-port

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

Default

no edge-port

forward-delay
Syntax

forward-delay seconds

no forward-delay

Context

config>service>vpls>stp

config>template>vpls-template>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

RSTP, as defined in the IEEE 802.1D-2004 standards, transitions to the forwarding state via a handshaking mechanism (rapid transition), without wait times. If handshaking fails (for example, on shared links (see the following)), 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 parameter depends on the STP operating mode of the VPLS instance, as described in the following:

  • in rstp or mstp mode, but only when the SAP has not fallen back to legacy STP operation, the value configured by the hello-time command is used

  • in all other situations, the value configured by the forward-delay command is used

Default

forward-delay 15

Parameters
seconds

Specifies the forward delay timer for the STP instance, in seconds.

Values

4 to 30

hello-time
Syntax

hello-time hello-time

no hello-time

Context

config>service>vpls>stp

config>template>vpls-template>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

The hello-time parameter 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; in this case, 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 the auto-edge command for more information.

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

Default

hello-time 2

Parameters
hello-time

Specifies the hello time for the STP instance, in seconds.

Values

1 to 10

hold-count
Syntax

hold-count BDPU tx hold count

no hold-count

Context

config>service>vpls>stp

config>template>vpls-template>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Default

hold-count 6

Parameters
BDPU tx hold count

Specifies the hold count for the STP instance, in seconds.

Values

1 to 10

link-type
Syntax

link-type {pt-pt | shared}

no link-type

Context

config>service>vpls>sap>stp

config>service>vpls>spoke-sdp>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the maximum number of bridges for STP behind this SAP.

If there is only a single bridge, transitioning to forwarding state is based on handshaking (fast transitions). If more than two bridges are connected via a shared media, their SAPs should all be configured as shared, and timer-based transitions are used.

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

Default

link-type pt-pt

mst-instance
Syntax

mst-instance mst-inst-number

Context

config>service>vpls>sap>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures Multiple Spanning Tree Instance (MSTI) related parameters at the SAP level. This context can be open only for existing MSTIs defined at the service level.

Parameters
mst-inst-number

Specifies an existing MSTI number.

Values

1 to 4094

mst-path-cost
Syntax

mst-path-cost inst-path-cost

no mst-path-cost

Context

config>service>vpls>sap>stp>mst-instance

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This commands specifies 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 the lowest priority.

By default, the path-cost is proportional to the link speed.

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

Parameters
inst-path-cost

Specifies the contribution of this port to the MSTI path cost.

Values

1 to 200000000

mst-port-priority
Syntax

mst-port-priority stp-priority

no mst-port-priority

Context

config>service>vpls>sap>stp>mst-instance

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Default

mst-port-priority 128

Parameters
stp-priority

Specifies the value of the port priority field.

max-age
Syntax

max-age seconds

no max-age

Context

config>service>vpls>stp

config>template>vpls-template>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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. Each other bridge takes the message_age value from BPDUs received on their root port and increments this value by 1. The message_age therefore reflects the distance from the root bridge. BPDUs with a message age exceeding the max-age value 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.

Default

max-age 20

Parameters
seconds

Specifies the max info age for the STP instance in seconds.

Values

6 to 40

mode
Syntax

mode {rstp | comp-dot1w | dot1w | mstp | pmstp}

no mode

Context

config>service>vpls>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the version of STP that 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.

Default

mode rstp

Parameters
rstp

Keyword that corresponds to the Rapid STP specified in IEEE 802.1D/D4-2003.

dot1w

Keyword that corresponds to the mode where the Rapid STP is backward compatible with IEEE 802.1w.

compdot1w

Keyword that corresponds to the Rapid STP fully conformant to IEEE 802.1w.

mstp

Keyword that sets MSTP as the STP mode of operation. Corresponds to the Multiple STP specified in 802.1Q REV/D5.0-09/2005

pmstp

This mode is supported only in VPLS services where the mVPLS flag is configured.

mst-instance
Syntax

[no] mst-instance mst-inst-number

Context

config>service>vpls>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures Multiple Spanning Tree Instance (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.

Parameters
mst-inst-number

Specifies the MST instance.

Values

1 to 4094

mst-priority
Syntax

mst-priority bridge-priority

no mst-priority

Context

config>service>vpls>stp>mst-instance

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the bridge priority for this specific Multiple Spanning Tree Instance for this service. The bridge-priority value reflects likelihood that the switch is 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).

All instances that are created by the vlan-range command do not have an explicit definition of bridge-priority and inherit the default value.

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

Default

mst-priority 32768

Parameters
bridge-priority

Specifies the priority of this specific MSTI for this service.

Values

0 to 65535

vlan-range
Syntax

[no] vlan-range [vlan-range]

Context

config>service>vpls>stp>mst-instance

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies a range of VLANs associated with a particular MSTI. This range applies to all SAPs of the mVPLS.

Every VLAN range that is not assigned within any of the created mst-instance 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.

Parameters
vlan-range

The first VLAN range specifies the left-bound (minimum value) of a range of VLANs that are associated with the mVPLS SAP. This value must be smaller than (or equal to) the second VLAN range value. The second VLAN range specifies the right-bound (maximum value) of a range of VLANs that are associated with the mVPLS SAP.

Values

1 to 4094

mst-max-hops
Syntax

mst-max-hops hops-count

no mst-max-hops

Context

config>service>vpls>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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 the BPDU (or M-record) it generates.

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

Default

mst-max-hops 20

Parameters
hops-count

Specifies the maximum number of hops.

Values

1 to 40

mst-name
Syntax

mst-name region-name

no mst-name

Context

config>service>vpls>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command defines an MST region name. Two bridges are considered as 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 is identical.

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

Default

no mst-name

Parameters
region-name

Specifies an MST-region name, up to 32 characters.

mst-revision
Syntax

mst-revision revision-number

Context

config>service>vpls>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command defines the MST configuration revision number. Two bridges are considered as 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 to the default value.

Default

mst-revision 0

Parameters
revision-number

Specifies the MSTP revision number to define the MSTP region.

Values

0 to 65535

path-cost
Syntax

path-cost sap-path-cost

no path-cost

Context

config>service>vpls>sap>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the 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 STP, path cost is a static configuration.

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

Parameters
path-cost

Specifies the path cost for the SAP.

Values

1 to 200000000 (1 is the lowest cost)

Default

10

port-num
Syntax

[no] port-num virtual-port-number

Context

config>service>vpls>sap>stp

config>service>vpls>spoke-sdp>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the virtual port number, which 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 using a virtual port number that is unique from 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.

priority
Syntax

priority bridge-priority

no priority

Context

config>service>vpls>stp

config>template>vpls-template>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command is used to populate the priority portion of the bridge ID field within outbound BPDUs (the most significant 4 bits of the bridge ID). It is also used as part of the decision process when determining the best BPDU between messages received and sent. All values are truncated to multiples of 4096, conforming with IEEE 802.1t and 802.1D-2004.

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

Default

priority 4096

Parameters
bridge-priority

Specifies the bridge priority for the STP instance.

Values

Allowed values are integers in the range of 4096 to 65535 (4096 is the highest priority).

The actual bridge-priority value stored and used is the number entered with the lowest 12 bits masked off, which means the actual range of values is 4096 to 61440 in increments of 4096.

priority
Syntax

priority stp-priority

no priority

Context

config>service>vpls>spoke-sdp

config>service>vpls>sap>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the STP priority for the SAP or spoke SDP.

When configuration BPDUs are received, the priority is used in some circumstances as a tie breaking mechanism to determine whether the SAP is 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.

Default

priority 128

Parameters
stp-priority

Specifies the STP priority value for the SAP or spoke SDP.

Values

0 to 255 (with masking, actual values are 0 to 240, in increments of 16)

Default

128

VPLS SAP commands
sap
Syntax

sap sap-id [split-horizon-group group-name] [create] [capture-sap] [eth-ring ring-index] [g8032-shg-enable]

no sap sap-id

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command creates a SAP within a service. A SAP is a combination of port and encapsulation parameters that identifies the SAP 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.

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.

Special Cases

A default SAP has the following format: port-id:*. This type of SAP is supported only on Ethernet MDAs, and its creation is allowed only in the scope of Layer 2 services (Epipe and VPLS).

Parameters
sap-id

Specifies the physical port identifier portion of the SAP definition. See Common CLI command descriptions for command syntax.

create

Keyword used to create a SAP instance. The create keyword requirement can be enabled or disabled using the environment>create context.

g8032-shg-enable

Keyword that must be used only with the SAPs created in the service for the virtual channel on the interconnection nodes in a topology that uses multiple rings. This command creates a split-horizon group to ensure that Sub-Ring control messages from the major ring are only passed to the Sub-Ring control service.

eth-ring

Keyword to create an instance of a Ring APS Control SAP or a Data SAP whose traffic is protected by a Ring APS Instance.

ring-index

Specifies the ring index of the Ethernet ring.

split-horizon-group group-name

Specifies the name of the split horizon group to which the SAP belongs.

accounting-policy
Syntax

accounting-policy acct-policy-id

no accounting-policy

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the accounting policy context that can be applied to a SAP.

An accounting policy must be defined before it can be associated with a SAP. If the policy-id does not exist, an error message is generated.

A maximum of one accounting policy can be associated with a SAP at one time. Accounting policies are configured in the config>log context.

The no form of this command removes the accounting policy association from the SAP, and the accounting policy reverts to the default value.

Parameters
acct-policy-id

Specifies the accounting policy-id as configured in the config>log>accounting-policy context.

Values

1 to 99

discard-unknown-source
Syntax

[no] discard-unknown-source

Context

config>service>vpls>sap

config>service>vpls>spoke-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

When this command is enabled, packets received on a SAP or with an unknown source MAC address are dropped only if the maximum number of MAC addresses for that SAP (see the command) has been reached. If the max-nbr-mac-addr command has not been configured 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.

Default

no discard-unknown-source

dist-cpu-protection
Syntax

dist-cpu-protection policy-name

no dist-cpu-protection

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command assigns a valid existing Distributed CPU Protection (DCP) policy to a SAP. By default, no DCP policy is associated with the SAP.

The no form of this command disables the use of DCP policies for the SAP.

Default

no dist-cpu-protection

Parameters
policy-name

Specifies the name of the DCP policy, up to 32 characters.

VPLS SAP statistics commands
statistics
Syntax

statistics

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure the counters associated with SAP ingress and egress.

ingress
Syntax

ingress

Context

config>service>vpls>sap>statistics

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure the ingress SAP statistics counters.

counter-mode
Syntax

counter-mode {in-out-profile-count | forward-drop-count}

Context

config>service>vpls>sap>statistics>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the counter mode for the counters associated with SAP ingress meters (also known as policers). A pair of counters is available with each meter. These counters count different events based on the counter-mode value.

Note: The counter-mode command can be changed if an accounting policy is associated with a SAP. If the counter-mode is changed, the counters associated with the meter are reset and the counts are cleared. If an accounting policy is in use when the counter-mode is changed, a new record is written into the current accounting file.

Execute the following sequence of commands on the specified SAP to ensure the correct statistics are collected when the counter-mode is changed:

  1. Execute the config service vpls sap no collect-stats command to disable writing of accounting records for the SAP.

  2. Change the counter-mode to the desired option by executing the config service vpls sap counter-mode {in-out-profile-count | forward-drop-count} command

  3. Execute the config service vpls sap collect-stats command to enable writing of accounting records for the SAP.

Default

in-out-profile-count

Parameters
forward-drop-count

Keyword to specify that one counter counts the forwarded packets and octets received on ingress of a SAP and another counts the dropped packets. The forwarded count is the sum of in-profile and out-of-profile packets and octets received on SAP ingress. The dropped count is the count of packets and octets dropped by the policer. A packet is determined to be in-profile or out-of-profile based on the meter rate parameters configured. A packet is dropped by the policer if it exceeds the configured PIR rate. The in-profile count and out-of-profile count is not individually available when operating in this mode.

in-out-profile-count

Keyword to specify that one counter counts the total in-profile packets and octets received on ingress of a SAP and another counts the total out-of-profile packets and octets received on ingress of a SAP. A packet is determined to be in-profile or out-of-profile based on the meter rate parameters configured. A packet is dropped by the policer if it exceeds the configured PIR rate. Dropped counts are not maintained in hardware when this mode is used. It is obtained by subtracting the sum of in-profile count and out-of-profile count from the total SAP ingress received count and displayed.

drop-count-extra-vlan-tag-pkts
Syntax

[no] drop-count-extra-vlan-tag-pkts

Context

config>service>vpls>sap>statistics>ingress

config>service>vpls>mesh-sdp>statistics>ingress

config>service>vpls>spoke-sdp>statistics>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command associates a counter that enables the counting of extra VLAN-tag dropped packets for the SAP, spoke-SDP, or mesh SDP. A limited number of such counters are available for use.

The no form of this command removes the associated counter.

ETH-CFM service commands
eth-cfm
Syntax

eth-cfm

Context

config>service>vpls

config>service>vpls>mesh-sdp

config>service>vpls>spoke-sdp

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure ETH-CFM parameters.

mep
Syntax

mep mep-id domain md-index association ma-index [direction {up | down}] primary-vlan-enable

no mep mep-id domain md-index association ma-index

Context

config>service>vpls>mesh-sdp>eth-cfm

config>service>vpls>sap>eth-cfm

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

The primary-vlan-enable parameter provides a method for linking the MEP with the primary VLAN configured under the bridge-identifier for the MA. MEPs cannot be changed from or to primary vlan functions. This must be configured as part of the creation step and can only be changed by deleting the MEP and recreating it. Primary VLANs are only supported under Ethernet SAPs.

Parameters
mep-id

Specifies the maintenance association endpoint identifier.

Values

1 to 8191

md-index

Specifies the maintenance domain (MD) index value.

Values

1 to 4294967295

ma-index

Specifies the MA index value.

Values

1 to 4294967295

direction {up | down}

Indicates the direction in which the maintenance association (MEP) faces on the bridge port. Direction is not supported when a MEP is created directly in the vpls>eth-cfm context (vMEP).

Values

down — Sends ETH-CFM messages away from the MAC relay entity.

up — Sends ETH-CFM messages toward the MAC relay entity.

primary-vlan-enable

Provides a method for linking the MEP with the primary VLAN configured under the bridge-identifier for the MA.

ais-enable
Syntax

[no] ais-enable

Context

config>service>vpls>mesh-sdp>eth-cfm>mep

config>service>epipe>spoke-sdp>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the generation and reception of AIS messages.

client-meg-level
Syntax

client-meg-level [[level [level ...]]

no client-meg-level

Context

config>service>vpls>mesh-sdp>eth-cfm>mep>ais-enable

config>service>epipe>spoke-sdp>eth-cfm>mep>ais-enable

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters
level

Specifies the client MEG level.

Values

1 to 7

Default

1

interval
Syntax

interval {1 | 60}

no interval

Context

config>service>vpls>mesh-sdp>eth-cfm>mep>ais-enable

config>service>epipe>spoke-sdp>eth-cfm>mep>ais-enable

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the transmission interval of AIS messages in seconds.

Parameters
1 | 60

Specifies the transmission interval of AIS messages, in seconds.

Default

1

priority
Syntax

priority priority-value

no priority

Context

config>service>vpls>mesh-sdp>eth-cfm>mep>ais-enable

config>service>epipe>spoke-sdp>eth-cfm>mep>ais-enable

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Parameters
priority-value

Specifies the priority value of the AIS messages originated by the node.

Values

0 to 7

Default

7

ccm-enable
Syntax

[no] ccm-enable

Context

config>service>vpls>mep

config>service>vpls>sap>eth-cfm>mep

config>service>vpls>mesh-sdp>mep

config>service>epipe>spoke-sdp>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the generation of CCM messages.

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

ccm-ltm-priority
Syntax

ccm-ltm-priority priority

no ccm-ltm-priority

Context

config>service>vpls>sap>eth-cfm>mep

config>service>vpls>mesh-sdp>mep config>service>epipe>spoke-sdp>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Parameters
priority

Specifies the priority of CCM and LTM messages.

Values

0 to 7

Default

highest priority on the bridge-port

eth-test-enable
Syntax

[no] eth-test-enable

Context

config>service>vpls>spoke-sdp>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

test-pattern
Syntax

test-pattern {all-zeros | all-ones} [crc-enable]

no test-pattern

Context

config>service>vpls>sap>eth-cfm>mep>eth-test-enable

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

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

Parameters
all-zeros

Specifies to use all zeros in the test pattern.

all-ones

Specifies to use all ones in the test pattern.

crc-enable

Generates a CRC checksum.

Default

all-zeros

fault-propagation-enable
Syntax

fault-propagation-enable {use-if-tlv | suspend-ccm}

no fault-propagation-enable

Context

config>service>epipe>sap>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the fault propagation for the MEP.

Parameters
use-if-tlv

Keyword to specify the use of the interface TLV.

suspend-ccm

Keyword to suspend the continuity check messages.

low-priority-defect
Syntax

low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}

Context

config>service>epipe>spoke-sdp>eth-cfm>mep

config>service>vpls>mesh-sdp>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Default

macRemErrXcon

Parameters
allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon

Specifies the lowest priority defect.

Values

allDef

DefRDICCM, DefMACstatus, DefRemoteCCM, DefErrorCCM, and DefXconCCM

macRemErrXcon

Only DefMACstatus, DefRemoteCCM, DefErrorCCM, and DefXconCCM

remErrXcon

Only DefRemoteCCM, DefErrorCCM, and DefXconCCM

errXcon

Only DefErrorCCM and DefXconCCM

xcon

Only DefXconCCM; or

noXcon

No defects DefXcon or lower are to be reported
mac-address
Syntax

mac-address mac-address

no mac-address

Context

config>service>vpls>mesh-sdp>eth-cfm>mep

config>service>epipe>spoke-sdp>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Parameters
mac-address

Specifies the MAC address of the MEP.

Values

6-byte mac-address in the form of xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx of the MEP. Must be unicast. Using the all zeros address is equivalent to the no form of this command.

one-way-delay-threshold
Syntax

one-way-delay-threshold seconds

Context

config>service>vpls>sap>eth-cfm>mep

config>service>epipe>spoke-sdp>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Parameters
seconds

Specifies the one-way delay threshold, in seconds.

Values

0 to 600

Default

3

mip
Syntax

mip [mac mac-address] [primary-vlan-enable vlan-id]

mip default-mac [primary-vlan-enable vlan-id]

no mip [primary-vlan-enable vlan-id]

Context

config>service>vpls>sap>eth-cfm

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

The primary-vlan-enable parameter provides a method for linking the MEP with the primary VLAN configured under the bridge-identifier for the MA. MEPs cannot be changed from or to primary vlan functions. This must be configured as part of the creation step and can only be changed by deleting the MEP and recreating it. Primary VLANs are only supported under Ethernet SAPs.

Parameters
mac-address

Specifies the MAC address of the MIP.

Values

6-byte mac-address in the form of xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx of the MIP. The MAC must be unicast. Using the all zeros address is equivalent to the no form of this command.

default-mac

Using the no command deletes the MIP. This keyword is useful if the operator needs to change the MAC back to the default MAC without having to delete the MIP and reconfiguring.

Default

no mip

primary-vlan-enable vlan-id

Provides a method for linking the MEP with the primary VLAN configured under the bridge-identifier for the MA.

Values

0 to 4094

limit-mac-move
Syntax

limit-mac-move [blockable | non-blockable]

no limit-mac-move

Context

config>service>vpls>spoke-sdp

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies whether the mac-move agent, when enabled using the config service vpls mac-move or config service epipe mac-move command, limits the MAC relearn (move) rate on this SAP.

Default

blockable

Parameters
blockable

Keyword to specify that the agent monitors the MAC relearn rate on the SAP and blocks it when the relearn rate is exceeded.

non-blockable

Keyword to specify this SAP is not blocked, and another blockable SAP is blocked instead.

mac-pinning
Syntax

[no] mac-pinning

Context

config>service>vpls>sap

config>service>vpls>spoke-sdp

config>service>vpls>mesh-sdp

config>service>vpls>endpoint config>service>pw-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command disables relearning of MAC addresses on other mesh SDPs within the VPLS.

The MAC address remains attached to a specific mesh for duration of its age-timer.

The age of the MAC address entry in the FIB is set by the age timer. If MAC aging is disabled on a specific VPLS service, a MAC address learned on a mesh with mac-pinning enabled remains in the FIB on this mesh forever. Every event that otherwise results in relearning is logged (MAC address; original - mesh SDP; new - mesh SDP).

Default

no mac-pinning

max-nbr-mac-addr
Syntax

max-nbr-mac-addr table-size

no max-nbr-mac-addr

Context

config>service>vpls>sap

config>service>vpls>spoke-sdp config>service>vpls>endpoint

config>service>pw-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command specifies the maximum number of FDB entries for both learned and static MAC addresses for this SAP.

When the configured limit is reached, and discard-unknown-source has been enabled for this SAP or spoke-SDP (see the command), packets with unknown source MAC addresses are discarded.

The no form of this command restores the global MAC learning limitations for the SAP.

Default

no max-nbr-mac-addr

Parameters
table-size

Specifies the maximum number of learned and static entries allowed in the FDB of this service.

Values

1 to 65535 (X)

Values

1to 61439 (7210 SAS-R6 and 7210 SAS-R12)

statistics
Syntax

statistics

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure the counters associated with SAP ingress and egress.

ingress
Syntax

ingress

Context

config>service>epipe>sap>statistics

config>service>vpls>sap>statistics

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure the ingress SAP statistics counter.

counter-mode
Syntax

counter-mode {in-out-profile-count | forward-drop-count}

Context

config>service>epipe>sap>statistics>ingress

config>service>vpls>sap>statistics>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the counter mode for the counters associated with SAP ingress meters (also known as policers). A pair of counters is available with each meter. These counters count different events based on the counter-mode value.

The counter-mode can be changed if an accounting policy is associated with a SAP. If the counter-mode is changed, the counters associated with the meter are reset and the counts are cleared. If an accounting policy is in use when the counter-mode is changed a new record is written into the current accounting file.

Execute the following sequence of commands to ensure a new accounting file is generated when the counter-mode is changed:

  1. Execute the config service epipe or vpls sap no collect-stats command to disable the writing of accounting records.

  2. Change the counter-mode to the required value by executing the config service epipe or vpls sap counter-mode {in-out-profile-count | forward-drop-count} command.

  3. Execute the config service epipe or vpls sap collect-stats command to enable writing of accounting records.

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

Default

in-out-profile-count

Parameters
forward-drop-count

Keyword to specify that one counter counts the forwarded packets and octets received on ingress of a SAP and another counts the dropped packets. The forwarded count is the sum of in-profile and out-of-profile packets and octets received on SAP ingress. The dropped count is count of packets and octets dropped by the policer. A packet is determined to be in-profile or out-of-profile based on the meter rate parameters configured. A packet is dropped by the policer if it exceeds the configured PIR rate. The in-profile count and out-of-profile count is not individually available when operating in this mode.

in-out-profile-count

Keyword to specify that one counter counts the total in-profile packets and octets received on ingress of a SAP and another counts the total out-of-profile packets and octets received on ingress of a SAP. A packet is determined to be in-profile or out-of-profile based on the meter rate parameters configured. A packet is dropped by the policer if it exceeds the configured PIR rate. Dropped counts are not maintained in hardware when this mode is used. It is obtained by subtracting the sum of in-profile count and out-of-profile count from the total SAP ingress received count and displayed.

static-mac
Syntax

[no] static-mac ieee-mac-address [create]

Context

config>service>vpls>sap

config>service>vpls>mesh-sdp

config>service>vpls>spoke-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a local static MAC entry in the VPLS FDB associated with the SAP.

In a VPLS service, MAC addresses are associated with a SAP or with an SDP. MACs associated with a SAP are classified as local MACs, and MACs associated with an SDP are remote MACs.

Local static MAC entries create a permanent MAC address to SAP association in the forwarding database for the VPLS instance, so that the MAC address is not learned on the edge device.

Static MAC definitions on one edge device are not propagated to other edge devices participating in the VPLS instance; that is, each edge device has an independent forwarding database for the VPLS.

Only one static MAC entry (local or remote) can be defined per MAC address per VPLS instance.

By default, no static MAC address entries are defined for the SAP.

The no form of this command deletes the static MAC entry with the specified MAC address associated with the SAP from the VPLS FDB.

Parameters
ieee-mac-address

Specifies the 48-bit MAC address for the static ARP in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers. Allowed values are any non-broadcast, non-multicast MAC and non-IEEE reserved MAC addresses.

create

Mandatory keyword for specifying a static MAC address.

managed-vlan-list
Syntax

managed-vlan-list

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure VLAN ranges managed by a management VPLS. The list indicates, for each SAP, the ranges of associated VLANs that is affected when the SAP changes state.

This command is valid only when the VPLS in which it is entered was created as a management VPLS.

default-sap
Syntax

[no] default-sap

Context

config>service>vpls>sap>managed-vlan-list

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command adds a default SAP to the managed VLAN list.

The no form of this command removes the default SAP from the managed VLAN list.

range
Syntax

[no] range vlan-range

Context

config>service>vpls>sap>managed-vlan-list

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a range of VLANs on an access port that are to be managed by an existing management VPLS.

This command is valid only when the VPLS in which it is entered was created as a management VPLS, and when the SAP in which it was entered was created on an Ethernet port with encapsulation type of dot1q.

To modify the range of VLANs, first the new range should be entered and then the old range removed. See Modifying VPLS service parameters for more information.

Parameters
vlan-range

Specify the VLAN start value and VLAN end value. The end-vlan value must be greater than the start-vlan value. The format is start-vlan-end-vlan

Values

start-vlan: 0 to 4094 end-vlan: 0 to 4094

VPLS filter and QoS policy commands
egress
Syntax

egress

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure egress filter policies.

If no egress filter is defined, no filtering is performed.

agg-rate-limit
Syntax

agg-rate-limit [cir cir-rate] [pir pir-rate]

no agg-rate-limit

Context

config>service>vpls>sap>egress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures a maximum total rate for all egress queues on a service SAP.

The port scheduler mode should be set to ‟sap-based” scheduling mode before using this command. The egress port scheduler enforces the aggregate queue rate for the SAP as it distributes its bandwidth to all the SAPs configured on the port. The port scheduler stops distributing bandwidth to member queues when it has detected that the aggregate rate limit has been reached.

A SAP aggregate scheduler is created for each instance of the SAP queues created on each of the member ports of the LAG. For a LAG, the port scheduler-mode configured for the primary port is used for all the member ports of the LAG.

The scheduler mode is specified using the scheduler-mode command. To implement the aggregate-rate-limit, the scheduler mode must be specified as ‟sap-based”. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more information about the scheduler-mode command.

The no form of this command removes the aggregate rate limit from the SAP or multi-service site.

Parameters
cir-rate

Specifies the CIR in kilobits per second. This parameter is supported only on the 7210 SAS-R6 and 7210 SAS-R12.

Values

0 to 10000000

pir-rate

Specifies the PIR in kilobits per second.

Values

1 to 10000000, max

aggregate-meter-rate
Syntax

aggregate-meter-rate rate-in-kbps [burst burst-in-kbits] [enable-stats]

no aggregate-meter-rate

Context

config>service>vpls>sap>egress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command associates a set of two counters to count total forwarded packets and octets and total dropped packets and octets. When the counter is enabled, the amount of resources required increases by twice the amount of resources taken up when counter is not used. If the enable-stats keyword is specified during the creation of the meter, the counter is allocated by the software, if available. To free up the counter and relinquish its use, use the no aggregate-meter-rate command, and then recreate the meter using the aggregate-meter rate command.

If egress frame-based accounting is used, the SAP egress aggregate meter rate accounts for the Ethernet frame overhead. The system accounts for 12 bytes of IFG and 8 bytes of start delimiter. Frame-based counting does not affect the count of octets maintained by the counter, if in use.

Note:

  • Before enabling this command for a SAP, resources must be allocated to this feature from the egress internal TCAM resource pool using the configure system resource-profile egress-internal-tcam egress-sap-aggregate-meter command. For more information, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide.

  • The egress aggregate meter is not FC aware. The forward and drop decisions are made based on the order the packets are sent out of the SAP by the egress port scheduler.

The no form of this command removes the egress aggregate policer from use.

Default

no aggregate-meter-rate

Parameters
rate-in-kbps

Specifies the rate in kilobits/s.

Values

1 to 100000000 | max

Default

max

burst-in-kbits

Specifies the burst size for the policer in kilobits. The burst size cannot be configured without configuring the rate.

Values

4 to 2146959 | default

Default

512

enable-stats

Keyword to specify whether the counter is to count forwarded and dropped packets must be allocated.

filter
Syntax

filter ip ip-filter-id

filter ipv6 ipv6-filter-id

filter mac mac-filter-id

no filter [ip ip-filter-id] [ipv6 ipv6-filter-id] [mac mac-filter-id]

Context

config>service>vpls>sap>egress

config>service>vpls>sap>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command associates an IP filter policy or MAC filter policy with an ingress or egress SAP or IP interface.

Filter policies control the forwarding and dropping of packets based on IP or MAC matching criteria. There types of filter policies are IP and MAC. Only one type may be applied to a SAP at a time.

The filter command is used to associate a filter policy with a specified filter ID with an ingress or egress SAP. The filter ID must already be defined before the filter command is executed. If the filter policy does not exist, the operation fails and an error message is returned.

In general, filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is that non-IP packets are not applied to IP match criteria, so the default action in the filter policy applies to these packets.

The no form of this command removes any configured filter ID association with the SAP or IP interface. The filter ID is not removed from the system.

Special Cases
VPLS

Both MAC and IP filters are supported on a VPLS service SAP.

Parameters
ip ip-filter-id

Specifies the IP filter policy. The filter ID must already exist within the created IP filters.

Values

1 to 65535

ipv6 ipv6-filter-id

Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.

Values

1 to 65535

mac mac-filter-id

Specifies the MAC filter policy. The specified filter ID must already exist within the created MAC filters. The filter policy must already exist within the created MAC filters.

Values

1 to 65535

qos
Syntax

qos policy-id

qos policy-id [enable-table-classification]

no qos

Context

config>service>vpls>sap>egress config>service>vpls>sap>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command associates a QoS policy with an ingress SAP or IP interface.

QoS ingress policies are important for the enforcement of SLA agreements. The policy ID must be defined before associating the policy with a SAP. If the policy-id does not exist, an error is returned.

The qos command is used to associate both ingress and egress QoS policies. The qos command only allows ingress policies to be associated on SAP or IP interface ingress, and only allows egress policies on SAP or IP interface egress. Attempts to associate a QoS policy of the wrong type returns an error.

Only one ingress and one egress QoS policy can be associated with a SAP at one time. Attempts to associate a second policy of same or different type replaces the earlier one with the new policy.

On the 7210 SAS-R6 and 7210 SAS-R12 (ingress), using the enable-table-classification keyword enables the use of IP DSCP tables to assign FC and profile on a per-SAP ingress basis. The match-criteria configured in the service ingress policy, which require CAM resources, are ignored. Only meters from the service ingress policy are used (and the meters still require CAM resources). The IP DSCP classification policy configured in the SAP ingress policy is used to assign FC and profile. The default FC is assigned from the SAP ingress policy.

By default, if no specific QoS policy is associated with the SAP for ingress or egress, the default QoS policy is used.

The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.

Parameters
policy-id

Specifies the ingress or egress policy ID to associate with SAP on ingress or egress. The policy ID must already exist.

Values

1 to 65535

enable-table-classification

Keyword to enable the use of table-based classification instead of CAM-based classification at SAP ingress. The FC and profile are taken from the IP DSCP classification policy configured in the ingress policy, along with the meters from the SAP ingress policy. Match-criteria entries in the SAP ingress policy are ignored.

ingress
Syntax

ingress

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure ingress SAP QoS policies and filter policies.

If no SAP ingress QoS policy is defined, the system default SAP ingress QoS policy is used for ingress processing. If no ingress filter is defined, no filtering is performed.

aggregate-meter-rate
Syntax

aggregate-meter-rate rate-in-kbps [burst burst-in-kbits]

no aggregate-meter-rate

Context

config>service>vpls>sap>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description
Note: The sum of CIR of the individual FCs configured under the SAP cannot exceed the PIR rate configured for the SAP. The 7210 SAS software does not block this configuration, however it is not recommended.

The meter modes ‟srtcm” and ‟trtcm1” are used in the absence of an aggregate meter.

The SAP ingress meter counters increment the packet or octet counts based on the final disposition of the packet.

If ingress frame-based accounting is used, the SAP aggregate meter rate accounts for the Ethernet frame overhead. The system accounts for 12 bytes of IFG and 8 bytes of start delimiter.

The no form of this command removes the aggregate policer from use.

Default

no aggregate-meter-rate

Parameters
rate-in-kbps

Specifies the rate in kilobits per second.

Values

0 to 20000000 | max

Default

max

burst burst-in-kilobits

Specifies the burst size for the policer in kilobits. The burst size cannot be configured without configuring the rate.

Values

4 to 2146959

Default

512

The following table provides information about the final disposition of the packet, based on the operating rate of the per-FC policer and the per-SAP aggregate policer:

Table 7. Final disposition of the packet based on per-FC and per-SAP policer or meter
Per-FC meter operating rate Per-FC assigned color SAP aggregate meter operating rate SAP aggregate meter color Final packet color

Within CIR

Green

Within PIR

Green

Green or

In-profile

Within CIR2

Green

Above PIR

Red

Green or

In-profile

Above CIR, Within PIR

Yellow

Within PIR

Green

Yellow or

Out-of-Profile

Above CIR, Within PIR

Yellow

Above PIR

Red

Red or

Dropped

Above PIR

Red

Within PIR

Green

Red or

Dropped

Above PIR

Red

Above PIR

Red

Red or

Dropped

When the SAP aggregate policer is configured, per-FC policer can be configured only in ‟trtcm2” mode (RFC 4115).

meter-override
Syntax

[no] meter-override

Context

config>service>vpls>sap>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the context for specific overrides to one or more meters created on the SAP through the SAP ingress QoS policies.

The no form of this command removes existing meter overrides.

Default

no meter-override

meter
Syntax

meter meter-id [create]

no meter meter-id

Context

config>service>vpls>sap>ingress>meter-override

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the context for specific overrides to a specific meter created on the SAP through a sap-ingress QoS policies.

The no form of this command is used to remove any existing overrides for the specified meter-id.

Parameters
meter-id

Required when executing the meter command within the meter-overrides context. The specified meter-id must exist within the SAP ingress QoS policy applied to the SAP. If the meter is not currently used by any forwarding class or forwarding type mappings, the meter will not exist on the SAP. This does not preclude creating an override context for the meter-id.

create

Mandatory keyword for when a meter meter-id override node is being created and the system is configured to expect explicit confirmation that a new object is being created. When the system is not configured to expect explicit confirmation, the create keyword is not required.

adaptation-rule
Syntax

adaptation-rule [pir adaptation-rule] [cir adaptation-rule]

no adaptation-rule

Context

config>service>vpls>sap>ingress>meter-override>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides specific attributes of the specified meter adaptation rule parameters. The adaptation rule controls the method used by the system to derive the operational CIR and PIR settings when the meter is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.

The no form of this command removes explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for rate and cir apply.

Default

no adaptation-rule

Parameters
pir

Defines the constraints enforced when adapting the PIR rate defined using the meter-override meter meter-id command. The pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR for the queue. When the meter-override command is not specified, the default applies.

When the meter mode in use is ‟trtcm2”, this parameter is interpreted as EIR value. See the description and relevant notes for meter modes in the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide for more information.

cir

Defines the constraints enforced when adapting the CIR rate defined using the meter-override meter meter-id command. The cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the cir parameter is not specified, the default constraint applies.

adaptation-rule

Specifies the criteria to use to compute the operational CIR and PIR values for this meter, while maintaining a minimum offset.

Values

max — The max, min and closest options are mutually exclusive. When max (maximum) is defined, the operational PIR for the meter is equal to or less than the administrative rate specified using the meter-override command.

min — The min, max and closest options are mutually exclusive. When min (minimum) is defined, the operational PIR for the queue is equal to or greater than the administrative rate specified using the meter-override command.

closest — The closest, min and max options are mutually exclusive. When closest is defined, the operational PIR for the meter is the rate closest to the rate specified using the meter-override command.

cbs
Syntax

cbs size [kbits | bytes | kbytes]

no cbs

Context

config>service>vpls>sap>ingress>meter-override>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default CBS for the meter. The committed burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the CBS value then the packets are marked as in-profile by the meter to indicate that the traffic is complying meter configured parameters.

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

Default

32 kbits

Parameters
size

Specifies the value in kbits, bytes, or kilobytes.

Values

kbits: 4 to 2146959 | default bytes: 512 to 274810752 | kbytes: 1 to 268369

mbs
Syntax

mbs size [kbits | bytes | kbytes]

no mbs

Context

config>service>vpls>sap>ingress>meter-override>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the default MBS for the meter. The maximum burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the MBS value, the packets are marked as in-profile by the meter to indicate that the traffic is complying with meter configured parameters.

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

Default

512 kbits

Parameters
size

Specifies the value in kbits, bytes, or kilobytes.

Values

kbits: 4 to 2146959 | default bytes: 512 to 274810752 | kbytes: 1 to 268369

mode
Syntax

mode mode

no mode

Context

config>service>vpls>sap>ingress>meter-override>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the SAP ingress QoS policy configured mode parameters for the specified meter-id.

The no form of this command restores the policy defined metering and profiling mode to a meter.

Parameters
mode

Specifies the rate mode of the meter-override.

Values

trtcm1, trtcm2, srtcm

rate
Syntax

rate cir cir-rate [pir pir-rate]

no rate

Context

config>service>vpls>sap>ingress>meter-override>meter

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command overrides the SAP ingress QoS policy configured rate parameters for the specified meter-id.

The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir-rate value.

The no form of this command restores the policy defined metering and profiling rate to a meter.

Default

max

Parameters
pir-rate

Defines the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be specified as a positive integer.

When the meter mode is set to ‟trtcm2”, the PIR value is interpreted as the EIR value. For more information, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide.

The actual PIR rate is dependent on the queue adaptation-rule parameters and the hardware where the queue is provisioned.

Values

0 to 20000000 | max

Default

max

cir-rate

Overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and must be specified as a positive integer.

Values

0 to 20000000 | max

Default

0

collect-stats
Syntax

[no] collect-stats

Context

config>service>vpls>spoke-sdp

config>service>vpls>mesh-sdp

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables accounting and statistical data collection for either the SAP, network port, or IP interface. When applying accounting policies, by default the data is collected in the appropriate records and written to the designated billing file.

When the no collect-stats command is issued, the statistics are still accumulated by the cards. However, the CPU does not obtain the results and write them to the billing file. If a subsequent collect-stats command is issued, the counters written to the billing file include all the traffic while the no collect-stats command was in effect.

Default

no collect-stats

VPLS SDP commands
mesh-sdp
Syntax

mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}]

no mesh-sdp sdp-id[:vc-id]

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Special Cases
VPLS

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.

Parameters
sdp-id

Specifies the SDP identifier.

Values

1 to 17407

vc-id

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.

Values

1 to 4294967295

vc-type

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.

ether

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)

vlan

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
Syntax

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]

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Special Cases
VPLS

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.

Parameters
sdp-id

Specifies the SDP identifier.

Values

1 to 17407

vc-id

Specifies the virtual circuit identifier.

Values

1 to 4294967295

create

Mandatory keyword while creating a spoke-SDP.

endpoint

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.

no-endpoint

Keyword to remove the association of a spoke-SDP with an explicit endpoint name.

ether

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)

split-horizon-group group-name

Specifies the name of the split horizon group to which the SDP belongs.

vc-type

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.

Values

ether, vlan

vlan

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.

use-evpn-default-shg

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.

Note: The following restrictions apply for the use-evpn-default-shg keyword:

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

control-word
Syntax

[no] control word

Context

config>service>vpls>mesh-sdp

config>service>vpls>spoke-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no control word

egress
Syntax

egress

Context

config>service>vpls>mesh-sdp

config>service>vpls>spoke-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the egress SDP context.

ingress
Syntax

ingress

Context

config>service>vpls>mesh-sdp

config>service>vpls>spoke-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the ingress SDP context.

vc-label
Syntax

[no] vc-label vc-label

Context

config>service>vpls>mesh-sdp>egress

config>service>vpls>spoke-sdp>egress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the egress VC label.

Parameters
vc-label

Specifies a VC egress value that indicates a specific connection.

Values

16 to 1048575

vc-label
Syntax

[no] vc-label vc-label

Context

config>service>vpls>mesh-sdp>ingress

config>service>vpls>spoke-sdp>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the ingress VC label.

Parameters
vc-label

Specifies a VC ingress value that indicates a specific connection.

Values

2048 to 18431

vlan-vc-tag
Syntax

vlan-vc-tag vlan-id

no vlan-vc-tag [vlan-id]

Context

config>service>vpls>spoke-sdp

config>service>vpls>mesh-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no vlan-vc-tag

Parameters
vlan-id

Specifies a valid VLAN identifier to bind an 802.1Q VLAN tag ID.

Values

0 to 4094

description
Syntax

description description-string

no description

Context

config>service>vpls>igmp-snooping>mvr

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters
description-string

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.

fast-leave
Syntax

[no] fast-leave

Context

config>service>vpls>sap>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no fast-leave

from-vpls
Syntax

from-vpls service-id

no from-vpls

Context

config>service>vpls>sap>igmp-snooping>mvr

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no from-vpls

Parameters
service-id

Specifies the MVR VPLS from which multicast channels should be copied into this SAP.

Values

service-id: 1 to 2147483648

group
Syntax

[no] group grp-address

Context

config>service>vpls>sap>igmp-snooping>static

config>service>vpls>spoke-sdp>snooping>static

config>service>vpls>mesh-sdp>snooping>static

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Note: Only SAPs are supported in an RVPLS service. SDPs are not supported in an RVPLS service.
Parameters
grp-address

Specifies an IGMP multicast group address that receives data on an interface. The IP address must be unique for each static group.

group-policy
Syntax

group-policy policy-name

no group-policy

Context

config>service>vpls>igmp-snooping>mvr

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters
policy-name

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
Syntax

hash-label [signal-capability]

no hash-label

Context

config>service>vpls>spoke-sdp

config>service>vpls>mesh-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

Note: On 7210 SAS, the hash label is not used on the local node for purpose of ECMP hashing and LAG hashing. It is available for use by LSR nodes through which the traffic flows and that are capable of using the labels for hashing.

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.

Note:

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

Default

no hash-label

Parameters
signal-capability

Keyword to enable the signaling and negotiation of the use of the hash label between the local and remote PE nodes.

igmp-snooping
Syntax

igmp-snooping

Context

config>service>vpls

config>service>vpls>sap

config>service>vpls>spoke-sdp

config>service>vpls>mesh-sdp

config>service>pw-template

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the Internet Group Management Protocol (IGMP) snooping context.

import
Syntax

import policy-name

no import

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no import

Parameters
policy-name

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
Syntax

last-member-query-interval tenths-of-seconds

no last-member-query-interval

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

last-member-query-interval 10

Parameters
tenths-of-seconds

Specifies the frequency, in tenths of seconds, at which query messages are sent.

Values

1 to 50

max-num-groups
Syntax

max-num-groups count

no max-num-groups

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no max-num-groups

Parameters
count

Specifies the maximum number of groups that can be joined on this SAP.

Values

For VPLS (SAP, mesh SDP, and spoke-SDP):

1 to 1024

For RVPLS:

1 to 1000

max-num-sources
Syntax

max-num-sources max-num-sources

no max-num-sources

Context

config>service>vpls>sap>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Note: The max-num-sources command is applicable only in the context of RVPLS service. It cannot be used in the context of VPLS service.

The no form of this command disables checking the number of sources.

Default

no max-num-sources

Parameters
max-num-sources

Specifies the maximum number of multicast sources per group that can be joined on this SAP.

Values

1 to 2043

mrouter-port
Syntax

[no] mrouter-port

Context

config>service>vpls>sap>igmp-snooping

config>service>vpls>spoke-sdp>igmp-snooping

config>service>vpls>mesh-sdp>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no mrouter-port

mvr
Syntax

mvr

Context

config>service>vpls>igmp-snooping

config>service>vpls>sap>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context configure Multicast VPLS Registration (MVR) parameters.

query-interval
Syntax

query-interval seconds

no query-interval

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

125

Parameters
seconds

Specifies the time interval, in seconds, that the router transmits general host-query messages.

query-src-ip
Syntax

query-src-ip ip-address

no query-src-ip

Context

config>service>vpls>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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

query-response-interval
Syntax

query-response-interval seconds

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

query-response-interval 10

Parameters
seconds

Specifies the length of time to wait to receive a response to the host-query message from the host.

Values

1 to 1023

report-src-ip
Syntax

report-src-ip ip-address

no report-src-ip

Context

config>service>vpls>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

report-src-ip 0.0.0.0

Parameters
ip-address

Specifies the source IP source address in transmitted IGMP reports.

robust-count
Syntax

robust-count robust-count

no robust-count

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

robust-count 2

Parameters
robust-count

Specifies the robust count for the SAP or SDP.

Values

config>service>vpls>sap>igmp-snooping: 2 to 7

config>service>vpls>igmp-snooping: 1 to 255

config>service>vpls>spoke-sdp>igmp-snooping: 2 to 7

config>service>vpls>mesh-sdp>igmp-snooping: 2 to 7

precedence
Syntax

precedence precedence-value | primary

no precedence

Context

config>service>vpls>spoke-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command configures the spoke-SDP precedence.

Default

precedence 4

Parameters
precedence-value

Specifies the spoke-SDP precedence.

Values

0 to 4

primary

Specifies that the precedence is primary.

propagate-mac-flush
Syntax

[no] propagate-mac-flush

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no propagate-mac-flush

send-queries
Syntax

[no] send-queries

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no send-queries

static
Syntax

static

Context

config>service>vpls>sap>igmp-snooping

config>service>vpls>spoke-sdp>igmp-snooping

config>service>vpls>mesh-sdp>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

group
Syntax

[no] group grp-address

Context

config>service>vpls>sap>igmp-snooping>static

config>service>vpls>spoke-sdp>snooping>static

config>service>vpls>mesh-sdp>snooping>static

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters
grp-address

Specifies an IGMP multicast group address that receives data on an interface. The IP address must be unique for each static group.

source
Syntax

source ip-address

no source ip-address

Context

config>service>vpls>sap>igmp-snooping>static>group

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Note: The source command is applicable only in the context of RVPLS service. It cannot be used in the context of VPLS service.
Default

no source

starg
Syntax

[no] starg

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no starg

version
Syntax

version version

no version

Context

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

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Parameters
version

Specifies the IGMP version.

Values

1 or 2 (in network mode for VPLS services)

1, 2, 3 (for RVPLS, only in network mode)

to-sap
Syntax

to-sap sap-id

no to-sap

Context

config>service>vpls>sap>igmp-snooping>mvr

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

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.

Default

no to-sap

Parameters
sap-id

Specifies the SAP to which multicast channels should be copied.

Routed VPLS commands

allow-ip-int-bind
Syntax

[no] allow-ip-int-bind

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command sets a flag on the VPLS service that allows an IES or VPRN IP interface to attach 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.

VPLS Configuration Constraints for Enabling the allow-ip-int-bind Command

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

  • SAP ingress QoS policies applied to the VPLS SAPs cannot have MAC match criteria defined.

  • The VPLS service type cannot be I-VPLS, B-VPLS, or M-VPLS, and it cannot be an I-VPLS service bound to a B-VPLS context.

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

VPLS Service Name Bound to IP Interface without the allow-ip-int-bind Flag Set

In the event 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 /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 from an IES or VPRN service attached, the no allow-ip-int-bind command fails. When the allow-ip-int-bind flag is reset on the VPLS service, the configuration and hardware restrictions associated with setting the flag are removed. The port network mode hardware restrictions are also removed.

Show commands

VPLS show commands
egress-label
Syntax

egress-label egress-label1 [egress-label2]

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays service information using a range of egress labels.

If only the mandatory egress-label1 parameter is specified, only services using the specified label are displayed.

If both egress-label1 and egress-label2 parameters are specified, the services using the range of labels X where egress-label1 <= X <= egress-label2 are displayed.

Use the show router ldp bindings command to display dynamic labels.

Parameters
egress-label1

Specifies the starting egress label value for which to display services using the label range. If only egress-label1 is specified, services only using egress-label1 are displayed.

Values

0, 2049 to 131071

egress-label2

Specifies the ending egress label value for which to display services using the label range.

Default

egress-label1 value

Values

2049 to 131071

fdb-info
Syntax

fdb-info

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays global FDB usage information.

Output

The following output is an example of FDB information, and Output fields: FDB info describes the output fields.

Sample output 
A:7210-SAS# show service fdb-info 
===============================================================================
Forwarding Database(FDB) Information
===============================================================================
Service Id        : 1                   Mac Move          : Disabled           
Mac Move Rate     : 2                   Mac Move Timeout  : 10                 
Table Size        : 8191                Total Count       : 675                
Learned Count     : 675                 Static Count      : 0                  
Local Age         : 60                                                         
High WaterMark    : 5%                  Low Watermark     : 1%                 
Mac Learning      : Enabl               Discard Unknown   : Dsabl              
Mac Aging         : Enabl               Relearn Only      : False              
 
Service Id        : 2                   Mac Move          : Disabled           
Mac Move Rate     : 2                   Mac Move Timeout  : 10                 
Table Size        : 8191                Total Count       : 0                  
Learned Count     : 0                   Static Count      : 0                  
Local Age         : 80                                                         
High WaterMark    : 10%                 Low Watermark     : 2%                 
Mac Learning      : Enabl               Discard Unknown   : Dsabl              
Mac Aging         : Enabl               Relearn Only      : False              
 
Service Id        : 3                   Mac Move          : Disabled           
Mac Move Rate     : 2                   Mac Move Timeout  : 10                 
Table Size        : 8191                Total Count       : 675                
Learned Count     : 675                 Static Count      : 0                  
Local Age         : 100                                                        
High WaterMark    : 15%                 Low Watermark     : 3%                 
Mac Learning      : Enabl               Discard Unknown   : Dsabl              
Mac Aging         : Enabl               Relearn Only      : False              
 
Service Id        : 4                   Mac Move          : Disabled           
Mac Move Rate     : 2                   Mac Move Timeout  : 10                 
Table Size        : 8191                Total Count       : 0                  
Learned Count     : 0                   Static Count      : 0                  
Local Age         : 120                                                        
High WaterMark    : 20%                 Low Watermark     : 4%                 
Mac Learning      : Enabl               Discard Unknown   : Dsabl              
Mac Aging         : Enabl               Relearn Only      : False              
 
Service Id        : 5                   Mac Move          : Disabled           
Mac Move Rate     : 2                   Mac Move Timeout  : 10                 
Table Size        : 8191                Total Count       : 0                  
Learned Count     : 0                   Static Count      : 0                  
Local Age         : 600                                                        
High WaterMark    : 25%                 Low Watermark     : 5%                 
Mac Learning      : Enabl               Discard Unknown   : Dsabl              
Mac Aging         : Enabl               Relearn Only      : False              
 
Service Id        : 6                   Mac Move          : Disabled           
Mac Move Rate     : 2                   Mac Move Timeout  : 10                 
Table Size        : 8191                Total Count       : 675                
Learned Count     : 675                 Static Count      : 0                  
Local Age         : 86400                                                      
High WaterMark    : 30%                 Low Watermark     : 10%                
Mac Learning      : Enabl               Discard Unknown   : Dsabl              
Mac Aging         : Enabl               Relearn Only      : False              
-------------------------------------------------------------------------------
Total Service FDBs : 6          
Total FDB Configured Size : 49146     
Total FDB Entries In Use  : 2025      
-------------------------------------------------------------------------------
===============================================================================
A:7210-SAS#
Table 8. Output fields: FDB info
Label Description

Service ID

The value that identifies a service.

Mac Move

Indicates the administrative state of the MAC movement feature associated with the service.

Mac Move Rate

The maximum rate at which MACs can be relearned in this TLS 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 rate is computed as the maximum number of relearns allowed in a 5 second interval. The default rate of 10 relearns per second corresponds to 50 relearns in a 5 second period.

Mac Move Timeout

Indicates the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled. A value of zero indicates that the SAP is not automatically re-enabled after being disabled. If after the SAP is re-enabled it is disabled again, the effective retry timeout is doubled to avoid thrashing.

Table Size

The maximum number of learned and static entries allowed in the FDB.

Total Count

The current number of entries (both learned and static) in the FDB of this service.

Learned Count

The current number of learned entries in the FDB of this service.

Static Count

The current number of static entries in the FDB of this service.

Remote Age

The number of seconds used to age out FDB entries learned on an SDP. These entries correspond to MAC addresses learned on remote SAPs.

Local Age

The seconds used to age out FDB entries learned on local SAPs.

High WaterMark

The utilization of the FDB table of this service at which a ‟table full” alarm is raised by the agent.

Low WaterMark

The utilization of the FDB table of this service at which a ‟table full” alarm is cleared by the agent.

Mac Learning

Specifies whether the MAC learning process is enabled in this service.

Discard Unknown

Specifies whether frames received with an unknown destination MAC are discarded in this service.

MAC Aging

Specifies whether the MAC aging process is enabled in this service.

MAC Pinning

Specifies whether MAC pinning is enabled in this service.

Relearn Only

When enabled, indicates that either the FDB table of this service is full or that the maximum system-wide number of MACs supported by the agent has been reached; therefore MAC learning is temporary disabled, and only MAC relearns can take place.

Total Service FDB

The current number of service FDBs configured on this node.

Total FDB Configured Size

The sum of configured FDBs.

Total FDB Entries In Use

The total number of entries (both learned and static) in use.
fdb-mac
Syntax

fdb-mac ieee-address [expiry]

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays the FDB entry for a specific MAC address.

Parameters
ieee-address

Specifies the 48-bit MAC address for which to display the FDB entry in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers.

expiry

Keyword that displays the time until the MAC is aged out.

Output

The following output is an example of MAC address FDB entry information, and Output fields: FDB MAC describes the output fields.

Sample output 
*A:ALA-12# show service fdb-mac 00:99:00:00:00:00
==============================================================================
Services Using Forwarding Database Mac 00:99:00:00:00:00                       
==============================================================================
ServId  MAC                           Source-Identifier         Type/
Age Last Change            
------------------------------------------------------------------------------
1       00:99:00:00:00:00             sap:1/2/7:0               Static           
==============================================================================
*A:ALA-12#
Table 9. Output fields: FDB MAC
Label Description

Service ID

The service ID number.

MAC

The specified MAC address.

Source-Identifier

The location where the MAC is defined.

Type/Age

Static — FDB entries created by management.

Learned — Dynamic entries created by the learning process

OAM — Entries created by the OAM process.

H — Host, the entry added by the system for a static configured subscriber host.

D or DHCP — DHCP-installed MAC. Learned addresses can be temporarily frozen by the DHCP snooping application for the duration of a DHCP lease

P — Indicates the MAC is protected by the MAC protection feature.
ingress-label
Syntax

ingress-label start-label [end-label]

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays services using a range of ingress labels.

If only the mandatory start-label parameter is specified, only services using the specified label are displayed.

If both start-label and end-label parameters are specified, the services using the range of labels X where start-label <= X <= end-label are displayed.

Use the show router ldp bindings command to display dynamic labels.

Parameters
start-label

Specifies the starting ingress label value for which to display services using the label range. If only start-label is specified, services only using start-label are displayed.

Values

0, 2048 to 131071

end-label

Specifies the ending ingress label value for which to display services using the label range.

Default

start-label value

Values

2049 to 131071

Output

The following table describes the show service ingress-label output fields.

Sample output
Table 10. Output fields: service ingress label
Label Description

Svc ID

The service identifier.

SDP Id

The SDP identifier.

Type

Indicates whether the SDP is spoke.

I.Lbl

The ingress label used by the far-end device to send packets to this device in this service by the SDP.

E.Lbl

The egress label used by this device to send packets to the far-end device in this service by the SDP.

Number of Bindings Found

The number of SDP bindings within the label range specified.
sap-using
Syntax

sap-using interface [ip-address | ip-int-name]

sap-using [ingress | egress] filter filter-id

sap-using [sap sap-id]

sap-using [ingress] qos-policy qos-policy-id

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays SAP information.

If no optional parameters are specified, the command displays a summary of all defined SAPs.

The optional parameters restrict output to only SAPs matching the specified properties.

Parameters
ingress

Specifies matching an ingress policy.

egress

Specifies matching an egress policy.

filter filter-id

Specifies the ingress or egress filter policy ID for which to display matching SAPs.

Values

1 to 65535

sap-id

Specifies the physical port identifier portion of the SAP definition. See Common CLI command descriptions for command syntax.

Output

The following output is an example of SAP service information, and Output fields: service SAP-using describes the output fields.

Sample output 
*A:ALU_SIM2>config>service>vpls# show service sap-using
===============================================================================
Service Access Points 
===============================================================================
PortId                          SvcId      Ing.  Ing.    Egr.   Adm  Opr
                                           QoS   Fltr    Fltr
-------------------------------------------------------------------------
1/1/1:10                        1          1     none    1none   Up   Up  
1/1/3:500.*                     1          1     none    1none   Up   Up  
1/1/1:200                       200        1     none    1none   Up   Up  
1/1/3:100.200                   200        1     none    1none   Up   Up  
1/1/1:300                       300        1     none    1none   Up   Up  
-------------------------------------------------------------------------------
Number of SAPs : 5
-------------------------------------------------------------------------------
*A:ALU_SIM2>config>service>vpls# 

*A:DUT-B_sasx>show>service# sap-using

===============================================================================
Service Access Points
===============================================================================
PortId                          SvcId      Ing.  Ing.    Egr.  Egr.   Adm  Opr
                                           QoS   Fltr    QoS   Fltr
-------------------------------------------------------------------------------
1/1/3:1                         1          10    none    1     none   Up   Up
1/1/3:2                         2          1     none    1     none   Up   Up
1/1/3:3                         3          1     none    1     none   Up   Up
1/1/3:4                         4          1     none    1     none   Up   Up
1/1/3:5                         5          1     none    1     none   Up   Up
1/1/3:6                         6          1     none    1     none   Up   Up
1/1/3:7                         7          1     none    1     none   Up   Up
1/1/3:8                         8          1     none    1     none   Up   Up
1/1/3:9                         9          1     none    1     none   Up   Up
1/1/3:10                        10         1     none    1     none   Up   Up
1/1/3:11                        11         1     none    1     none   Up   Up
1/1/3:12                        12         1     none    1     none   Up   Up
1/1/3:13                        13         1     none    1     none   Up   Up
1/1/3:14                        14         1     none    1     none   Up   Up
1/1/3:15                        15         1     none    1     none   Up   Up
1/1/3:16                        16         1     none    1     none   Up   Up
1/1/3:17                        17         1     none    1     none   Up   Up
1/1/3:18                        18         1     none    1     none   Up   Up
1/1/3:19                        19         1     none    1     none   Up   Up
1/1/3:20                        20         1     none    1     none   Up   Up
1/1/3:21                        21         1     none    1     none   Up   Up
1/1/3:22                        22         1     none    1     none   Up   Up
1/1/3:23                        23         1     none    1     none   Up   Up
1/1/3:24                        24         1     none    1     none   Up   Up
1/1/3:25                        25         1     none    1     none   Up   Up
1/1/3:26                        26         1     none    1     none   Up   Up
1/1/3:27                        27         1     none    1     none   Up   Up
1/1/3:28                        28         1     none    1     none   Up   Up
1/1/3:29                        29         1     none    1     none   Up   Up
1/1/3:30                        30         1     none    1     none   Up   Up
1/1/3:31                        31         1     none    1     none   Up   Up
1/1/3:32                        32         1     none    1     none   Up   Up
1/1/3:33                        33         1     none    1     none   Up   Up
1/1/3:34                        34         1     none    1     none   Up   Up
1/1/3:35                        35         1     none    1     none   Up   Up
1/1/3:36                        36         1     none    1     none   Up   Up
1/1/3:37                        37         1     none    1     none   Up   Up
1/1/3:38                        38         1     none    1     none   Up   Up
1/1/3:39                        39         1     none    1     none   Up   Up
1/1/3:40                        40         1     none    1     none   Up   Up
1/1/3:41                        41         1     none    1     none   Up   Up
1/1/3:42                        42         1     none    1     none   Up   Up
1/1/3:43                        43         1     none    1     none   Up   Up
1/1/3:44                        44         1     none    1     none   Up   Up
1/1/3:45                        45         1     none    1     none   Up   Up
1/1/3:46                        46         1     none    1     none   Up   Up
1/1/3:47                        47         1     none    1     none   Up   Up
1/1/3:48                        48         1     none    1     none   Up   Up
1/1/3:49                        49         1     none    1     none   Up   Up
1/1/3:50                        50         1     none    1     none   Up   Up
1/1/3:51                        51         1     none    1     none   Up   Up
1/1/3:52                        52         1     none    1     none   Up   Up
1/1/3:53                        53         1     none    1     none   Up   Up
1/1/3:54                        54         1     none    1     none   Up   Up
1/1/3:55                        55         1     none    1     none   Up   Up
1/1/3:56                        56         1     none    1     none   Up   Up
1/1/3:57                        57         1     none    1     none   Up   Up
1/1/3:58                        58         1     none    1     none   Up   Up
1/1/3:59                        59         1     none    1     none   Up   Up
1/1/3:60                        60         1     none    1     none   Up   Up
1/1/3:61                        61         1     none    1     none   Up   Up
1/1/3:62                        62         1     none    1     none   Up   Up
1/1/3:63                        63         1     none    1     none   Up   Up
1/1/3:64                        257        1     none    1     none   Up   Up
-------------------------------------------------------------------------------
Number of SAPs : 64
-------------------------------------------------------------------------------
===============================================================================
Table 11. Output fields: service SAP-using
Label Description

Port ID

The ID of the access port where the SAP is defined.

Svc ID

The service identifier.

I.QoS

The SAP ingress QoS policy number specified on the ingress SAP.

I.MAC/IP

The MAC or IP filter policy ID applied to the ingress SAP.

Egr. Fltr

The filter policy ID applied to the egress SAP.

A.Pol

The accounting policy ID assigned to the SAP.

Adm

The administrative state of the SAP.

Opr

The actual state of the SAP.
sdp
Syntax

sdp [sdp-id | far-end ip-addr] [detail | keep-alive-history]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information for the SDPs associated with the service.

If no optional parameters are specified, a summary of all associated SDPs is displayed.

Parameters
sdp-id

Displays only information for the specified SDP ID. An SDP is a logical mechanism that ties a far-end 7210 SAS to a particular service without having to specifically define far end SAPs. Each SDP represents a method to reach a 7210 SAS router.

Default

All SDPs.

Values

1 to 17407

far-end ip-addr

Displays only SDPs matching with the specified system IP address of the far-end destination 7210 SAS router for the Service Distribution Point (SDP) that is the termination point for a service.

Default

SDPs with any far-end IP address.

detail

Displays detailed SDP information.

Output

The following table describes the show service SDP output fields.

Sample output
Table 12. Output fields: service SDP
Label Description

Sdp Id

The SDP identifier.

Type

Indicates whether the SDP is a spoke.

VC Type

Displays the VC type: ether or vlan.

VC Tag

Displays the explicit dot1Q value used when encapsulating to the SDP far end.

I. Lbl

The VC label used by the far-end device to send packets to this device in this service by the SDP.

Admin Path MTU

The operating path MTU of the SDP is equal to the admin path MTU (when one is set) or the dynamically computed tunnel MTU, when no admin path MTU is set (the default case.)

Oper Path MTU

The actual largest service frame size (in octets) that can be transmitted through this SDP to the far-end router, without requiring the packet to be fragmented.

Far End

Specifies the IP address of the remote end of the MPLS tunnel defined by this SDP.

Delivery

Specifies the type of delivery used by the SDP: MPLS.

Admin State

The administrative state of this SDP.

Oper State

The operational state of this SDP.

Ingress Label

The label used by the far-end device to send packets to this device in this service by this SDP.

Egress Label

The label used by this device to send packets to the far-end device in this service by the SDP.

Last Changed

The date and time of the most recent change to the SDP.

Signaling

Specifies the signaling protocol used to obtain the ingress and egress labels used in frames transmitted and received on this SDP.

Admin State

The administrative state of the keepalive process.

Oper State

The operational state of the keepalive process.

Hello Time

Specifies how often the SDP echo request messages are transmitted on this SDP.

Max Drop Count

Specifies the maximum number of consecutive SDP echo request messages that can be unacknowledged before the keepalive protocol reports a fault.

Hello Msg Len

Specifies the length of the SDP echo request messages transmitted on this SDP.

Hold Down Time

Specifies the amount of time to wait before the keepalive operating status is eligible to enter the alive state.

I. Fwd. Pkts.

Specifies the number of forwarded ingress packets.

I. Dro. Pkts

Specifies the number of dropped ingress packets.

E. Fwd. Pkts.

Specifies the number of forwarded egress packets.

E. Fwd. Octets

Specifies the number of forwarded egress octets.

Associated LSP List

When the SDP type is MPLS, a list of LSPs used to reach the far-end router displays. All the LSPs in the list must terminate at the IP address specified in the Far End field.

sdp-using
Syntax

sdp-using [sdp-id[:vc-id] | far-end ip-address]

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays services using SDP or far-end address options.

Parameters
sdp-id

Displays only services bound to the specified SDP ID.

Values

1 to 17407

vc-id

Specifies the virtual circuit identifier.

Values

1 to 4294967295

far-end ip-address

Displays only services matching with the specified far-end IP address.

Default

Services with any far-end IP address.

Output

The following output is an example of SDP service information, and Output fields: SDP-using describes the output fields.

Sample output 
*A:ALA-1# show service sdp-using 300
===============================================================================
Service Destination Point (Sdp Id : 300)
===============================================================================
SvcId       SdpId               Type Far End        Opr State I.Label  E.Label
-------------------------------------------------------------------------------
2           300:2               Spok 10.0.0.13      Up        131070   131070
-------------------------------------------------------------------------------
Number of SDPs : 51
-------------------------------------------------------------------------------
*A:ALA-1#
Table 13. Output fields: SDP-using
Label Description

Svc ID

The service identifier.

Sdp ID

The SDP identifier.

Type

Specifies the type of SDP: Spoke.

Far End

The far-end address of the SDP.

Oper State

The operational state of the service.

Ingress Label

The label used by the far-end device to send packets to this device in this service by this SDP.

Egress Label

The label used by this device to send packets to the far-end device in this service by this SDP.
service-using
Syntax

service-using [epipe] [vpls] [mirror] [customer customer-id]

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays services matching the specified usage properties. If no optional parameters are specified, all services defined on the system are displayed.

Parameters
epipe

Keyword to display matching Epipe services.

vpls

Keyword to display matching VPLS instances.

mirror

Keyword to display matching mirror services.

customer customer-id

Specifies to display services only associated with the specified customer ID.

Default

Services associated with a customer.

Values

1 to 2147483647

Output

The following output is an example of service information, and Output fields: service-using describes the output fields.

Sample output 
*A:ALA-12# show service service-using customer 10
==============================================================================
Services
==============================================================================
ServiceId    Type      Adm    Opr        CustomerId        Last Mgmt Change
------------------------------------------------------------------------------
1            VPLS      Up     Up         10                09/05/2006 13:24:15
100          IES       Up     Up         10                09/05/2006 13:24:15
300          Epipe     Up     Up         10                09/05/2006 13:24:15
------------------------------------------------------------------------------
Matching Services : 3
==============================================================================
*A:ALA-12#


*A:ALA-12# show service service-using epipe
===============================================================================
Services [epipe]
===============================================================================
ServiceId    Type      Adm    Opr        CustomerId        Last Mgmt Change
-------------------------------------------------------------------------------
6            Epipe     Up     Up         6                 09/22/2006 23:05:58
7            Epipe     Up     Up         6                 09/22/2006 23:05:58
8            Epipe     Up     Up         3                 09/22/2006 23:05:58
103          Epipe     Up     Up         6                 09/22/2006 23:05:58
-------------------------------------------------------------------------------
Matching Services : 4
===============================================================================
*A:ALA-12#


*A:ALA-14# show service service-using
===============================================================================
Services
===============================================================================
ServiceId    Type      Adm    Opr        CustomerId        Last Mgmt Change
-------------------------------------------------------------------------------
10           mVPLS     Down   Down       1                 10/26/2006 15:44:57
11           mVPLS     Down   Down       1                 10/26/2006 15:44:57
100          mVPLS     Up     Up         1                 10/26/2006 15:44:57
101          mVPLS     Up     Up         1                 10/26/2006 15:44:57
102          mVPLS     Up     Up         1                 10/26/2006 15:44:57
-------------------------------------------------------------------------------
Matching Services : 5
-------------------------------------------------------------------------------
*A:ALA-14#



A:Dut-A>config>service# show service service-using
===============================================================================
Services
===============================================================================
ServiceId    Type      Adm    Opr        CustomerId        Last Mgmt Change
-------------------------------------------------------------------------------
100          mVPLS     Up     Up         1                 07/07/2009 14:39:13
101          uVPLS     Up     Up         1                 07/07/2009 14:39:13
102          uVPLS     Up     Up         1                 07/07/2009 14:39:13
103          uVPLS     Up     Up         1                 07/07/2009 14:39:13
104          uVPLS     Up     Up         1                 07/07/2009 14:39:13
105          uVPLS     Up     Up         1                 07/07/2009 14:39:13
201          VPLS      Up     Up         1                 07/07/2009 14:39:13
202          VPLS      Up     Up         1                 07/07/2009 14:39:13
203          VPLS      Up     Up         1                 07/07/2009 14:39:13
204          VPLS      Up     Up         1                 07/07/2009 14:39:13
205          VPLS      Up     Up         1                 07/07/2009 14:39:13
300          mVPLS     Up     Up         1                 07/07/2009 14:39:13
301          uVPLS     Up     Up         1                 07/07/2009 14:39:13
302          uVPLS     Up     Up         1                 07/07/2009 14:39:13
303          uVPLS     Up     Up         1                 07/07/2009 14:39:13
304          uVPLS     Up     Up         1                 07/07/2009 14:39:1
305          uVPLS     Up     Up         1                 07/07/2009 14:39:1
401          VPLS      Up     Up         1                 07/07/2009 14:39:1
402          VPLS      Up     Up         1                 07/07/2009 14:39:1
403          VPLS      Up     Up         1                 07/07/2009 14:39:1
404          VPLS      Up     Up         1                 07/07/2009 14:39:1
405          VPLS      Up     Up         1                 07/07/2009 14:39:1
500          mVPLS     Up     Up         1                 07/07/2009 14:39:1
511          uVPLS     Up     Up         1                 07/07/2009 14:39:1
513          uVPLS     Up     Up         1                 07/07/2009 14:39:1
515          uVPLS     Up     Up         1                 07/07/2009 14:39:1
517          uVPLS     Up     Up         1                 07/07/2009 14:39:1
519          uVPLS     Up     Up         1                 07/07/2009 14:39:1
601          VPLS      Up     Up         1                 07/07/2009 14:39:1
602          VPLS      Up     Up         1                 07/07/2009 14:39:1
603          VPLS      Up     Up         1                 07/07/2009 14:39:1
604          VPLS      Up     Up         1                 07/07/2009 14:39:1
605          VPLS      Up     Up         1                 07/07/2009 14:39:1
701          VPLS      Up     Up         1                 07/07/2009 14:39:1
702          VPLS      Up     Up         1                 07/07/2009 14:39:1
703          VPLS      Up     Up         1                 07/07/2009 14:39:1
704          VPLS      Up     Up         1                 07/07/2009 14:39:1
801          VPLS      Up     Up         1                 07/07/2009 14:39:1
802          VPLS      Up     Up         1                 07/07/2009 14:39:1
803          VPLS      Up     Up         1                 07/07/2009 14:39:1
804          VPLS      Up     Up         1                 07/07/2009 14:39:1
805          VPLS      Up     Up         1                 07/07/2009 14:39:1
901          VPLS      Up     Up         1                 07/07/2009 14:39:1
902          VPLS      Up     Up         1                 07/07/2009 14:39:1
903          VPLS      Up     Up         1                 07/07/2009 14:39:1
904          VPLS      Up     Up         1                 07/07/2009 14:39:1
905          VPLS      Up     Up         1                 07/07/2009 14:39:1
906          VPLS      Up     Up         1                 07/07/2009 14:39:1
907          VPLS      Up     Up         1                 07/07/2009 14:39:1
908          VPLS      Up     Up         1                 07/07/2009 14:39:1
909          VPLS      Up     Up         1                 07/07/2009 14:39:1
910          VPLS      Up     Up         1                 07/07/2009 14:39:1
1101         Epipe     Up     Up         1                 07/07/2009 14:39:1
1102         Epipe     Up     Up         1                 07/07/2009 14:39:1
1103         Epipe     Up     Up         1                 07/07/2009 14:39:1
1104         Epipe     Up     Up         1                 07/07/2009 14:39:1
1105         Epipe     Up     Up         1                 07/07/2009 14:39:1
1501         Epipe     Up     Up         1                 07/07/2009 14:39:1
1502         Epipe     Up     Up         1                 07/07/2009 14:39:1
1503         Epipe     Up     Up         1                 07/07/2009 14:39:1
1504         Epipe     Up     Up         1                 07/07/2009 14:39:1
1505         Epipe     Up     Up         1                 07/07/2009 14:39:1
2001         Mirror    Up     Up         1                 07/07/2009 14:39:1
2002         Mirror    Up     Up         1                 07/07/2009 14:39:1
2011         Epipe     Up     Up         1                 07/07/2009 14:39:1
2012         VPLS      Up     Up         1                 07/07/2009 14:39:1
3000         mVPLS     Up     Up         1                 07/07/2009 14:39:1
4001         VPLS      Up     Up         1                 07/07/2009 14:39:1
4002         VPLS      Up     Up         1                 07/07/2009 14:39:1
-----------------------------------------------------------------------------
Matching Services : 69
=============================================================================
A:Dut-A>config>service#
Table 14. Output fields: service-using
Label Description

Service Id

The service identifier.

Type

Specifies the service type configured for the service ID.

Adm

The administrative state of the service.

Opr

The operating state of the service.

CustomerID

The ID of the customer who owns this service.

Last Mgmt Change

The date and time of the most recent management-initiated change to this service.
id
Syntax

id service-id {all | arp | base | endpoint | fdb | interface | label | labels | sap | splithorizon-group | stp |mstp-configuration}

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information for a particular service ID.

Parameters
service-id

Specifies the unique service identification number that identifies the service in the service domain.

Values

service-id: 1 to 214748364

svc-name: A string up to 64 characters.

all

Keyword to display detailed information about the service.

base

Keyword to display basic service information.

endpoint

Keyword to display service endpoint information.

fdb

Keyword to display FDB entries.

labels

Keyword to display labels being used by this service.

mstp-configuration

Keyword to display MSTP information.

sap

Keyword to display SAPs associated with the service.

sdp

Keyword to display SDPs associated with the service.

stp

Keyword to display STP information.

all
Syntax

all

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays detailed information for all aspects of the service.

Output

The following output is an example of detailed service information, and Output fields: service ID All describes the output fields.

Sample output 
show service id 100 all 
===============================================================================
Service Detailed Information
===============================================================================
Service Id        : 100                 Vpn Id            : 0
Service Type      : Epipe               
Name              : (Not Specified)
Description       : (Not Specified)
Customer Id       : 1                   Creation Origin   : manual
Last Status Change: 12/14/2019 11:35:20 
Last Mgmt Change  : 12/14/2019 13:09:09 
Test Service      : No                  
Admin State       : Down                Oper State        : Down
MTU               : 1514                
MTU Check         : Enabled             
Vc Switching      : False               
SAP Count         : 1                   SDP Bind Count    : 1
SAP Type:         : Qinq Inner Tag Pre* 
Propagate MacFlush: Disabled            Per Svc Hashing   : Disabled
Allow IP Intf Bind: Disabled            Fwd-IPv4-Mcast-To*: Disabled
VSD Domain        : <none>
Per Svc Hashing   : Disabled            
Force QTag Fwd    : Disabled            
 
-------------------------------------------------------------------------------
BGP Information
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
ETH-CFM service specifics
-------------------------------------------------------------------------------
Tunnel Faults     : ignore              
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Sdp Id 102:100  -(10.10.10.2)
-------------------------------------------------------------------------------
Description     : (Not Specified)
SDP Id             : 102:100                  Type              : Spoke
Spoke Descr     : (Not Specified)
VC Type            : VLAN                     VC Tag            : 2
Admin Path MTU     : 0                        Oper Path MTU     : 1578
Delivery           : MPLS                     
Far End            : 10.10.10.2
Tunnel Far End     : n/a                      LSP Types         : RSVP
Hash Label         : Disabled                 Hash Lbl Sig Cap  : Disabled
Oper Hash Label    : Disabled                 
 
Admin State        : Up                       Oper State        : Down
Acct. Pol          : None                     Collect Stats     : Disabled
Ingress Label      : 131065                   Egress Label      : None
Ingr Mac Fltr-Id   : n/a                      Egr Mac Fltr-Id   : n/a
Ingr IP Fltr-Id    : n/a                      Egr IP Fltr-Id    : n/a
Ingr IPv6 Fltr-Id  : n/a                      Egr IPv6 Fltr-Id  : n/a
Admin ControlWord  : Not Preferred            Oper ControlWord  : False
Admin BW(Kbps)     : 0                        Oper BW(Kbps)     : 0
BFD Template       : None
BFD-Enabled        : no                       BFD-Encap         : ipv4
Last Status Change : 12/14/2019 11:35:20      Signaling         : TLDP
Last Mgmt Change   : 12/14/2019 13:09:09      
Endpoint           : N/A                      Precedence        : 4
PW Status Sig      : Enabled                  
Force Vlan-Vc      : Disabled                 Force Qinq-Vc     : Disabled
Class Fwding State : Down                     
Flags              : SvcAdminDown
                     NoEgrVCLabel
Local Pw Bits      : lacIngressFault lacEgressFault psnEgressFault
Peer Pw Bits       : None
Peer Fault Ip      : None                     
Peer Vccv CV Bits  : None
Peer Vccv CC Bits  : None
Application Profile: None                     
Standby Sig Slave  : False                    
Block On Peer Fault: False                    
Use SDP B-MAC      : False                    
 
KeepAlive Information :
Admin State        : Disabled                 Oper State        : Disabled
Hello Time         : 10                       Hello Msg Len     : 0
Max Drop Count     : 3                        Hold Down Time    : 10
Statistics            :
I. Fwd. Pkts.      : 0                        I. Fwd. Octs.     : 0
E. Fwd. Pkts.      : 0                        E. Fwd. Octets    : 0
Extra-Tag-Drop-Pkts: n/a                      Extra-Tag-Drop-Oc*: n/a
-------------------------------------------------------------------------------
Control Channel Status
-------------------------------------------------------------------------------
PW Status          : disabled                 Refresh Timer     : <none>
Peer Status Expire : false                    
Request Timer      : <none>                   
Acknowledgement    : false                    
-------------------------------------------------------------------------------
ETH-CFM SDP-Bind specifics
-------------------------------------------------------------------------------
Squelch Levels     : None                     
 
-------------------------------------------------------------------------------
RSVP/Static LSPs
-------------------------------------------------------------------------------
Associated LSP List :
Lsp Name           : a_b                      
Admin State        : Up                       Oper State        : Up
Time Since Last Tr*: 00h00m13s                
 
-------------------------------------------------------------------------------
Number of SDPs : 1
-------------------------------------------------------------------------------
* indicates that the corresponding row element may have been truncated.
-------------------------------------------------------------------------------
Service Access Points
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
SAP 1/1/9:1.2
-------------------------------------------------------------------------------
Service Id         : 100                      
SAP                : 1/1/9:1.2                Encap             : qinq
QinQ Dot1p         : Default                  
Description        : (Not Specified)
Admin State        : Down                     Oper State        : Down
Flags              : ServiceAdminDown SapAdminDown
Last Status Change : 12/14/2019 11:35:20      
Last Mgmt Change   : 12/14/2019 13:09:09      
Dot1Q Ethertype    : 0x8100                   QinQ Ethertype    : 0x8100
Split Horizon Group: (Not Specified)
Admin MTU          : 1522                     Oper MTU          : 1522
Ingr IP Fltr-Id    : n/a                      Egr IP Fltr-Id    : n/a
Ingr Mac Fltr-Id   : n/a                      Egr Mac Fltr-Id   : n/a
Ingr IPv6 Fltr-Id  : n/a                      Egr IPv6 Fltr-Id  : n/a
tod-suite          : None                     
Egr Agg Rate CIR   : 0                        Egr Agg Rate PIR  : max
Endpoint           : N/A                      
                                              Limit Unused BW   : Disabled
Acct. Pol          : None                     Collect Stats     : Disabled
Oper Group         : (none)                   Monitor Oper Grp  : (none)
Host Lockout Plcy  : n/a                      
Lag Link Map Prof  : (none)                   
Cflowd             : Disabled                 
-------------------------------------------------------------------------------
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 1                        Egress qos-policy : 1
Table-based        : disabled                 
-------------------------------------------------------------------------------
Aggregate Policer
-------------------------------------------------------------------------------
Rate               : n/a                      Burst             : n/a
-------------------------------------------------------------------------------
Egress Aggregate Meter
-------------------------------------------------------------------------------
Rate               : n/a                      Burst             : n/a
-------------------------------------------------------------------------------
Ingress QoS Classifier Usage
-------------------------------------------------------------------------------
Classifiers Allocated: 2                     Meters Allocated   : 1
Classifiers Used     : 1                     Meters Used        : 1
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
                        Packets                 Octets
Ingress Stats:          0                       0                        
Egress Stats:           0                       0                        
Ingress Drop Stats:     0                       0                        
 
Extra-Tag Drop Stats:   n/a                     n/a                      
-------------------------------------------------------------------------------
Sap per Meter stats (in/out counter mode)
-------------------------------------------------------------------------------
                        Packets                 Octets
Ingress Meter 1
For. InProf           : 0                       0                        
For. OutProf          : 0                       0                        
-------------------------------------------------------------------------------
Sap per Egress Queue stats
-------------------------------------------------------------------------------
                        Packets                 Octets
Egress Queue 1 (be)
Fwd Stats            :  0                       0                        
Drop Stats           :  0                       0                        
 
Egress Queue 2 (l2)
Fwd Stats            :  0                       0                        
Drop Stats           :  0                       0                        
 
Egress Queue 3 (af)
Fwd Stats            :  0                       0                        
Drop Stats           :  0                       0                        
 
Egress Queue 4 (l1)
Fwd Stats            :  0                       0                        
Drop Stats           :  0                       0                        
 
Egress Queue 5 (h2)
Fwd Stats            :  0                       0                        
Drop Stats           :  0                       0                        
 
Egress Queue 6 (ef)
Fwd Stats            :  0                       0                        
Drop Stats           :  0                       0                        
 
Egress Queue 7 (h1)
Fwd Stats            :  0                       0                        
Drop Stats           :  0                       0                        
 
Egress Queue 8 (nc)
Fwd Stats            :  0                       0                        
Drop Stats           :  0                       0                        
-------------------------------------------------------------------------------
Service Endpoints
-------------------------------------------------------------------------------
No Endpoints found.
-------------------------------------------------------------------------------
==========================================================================
VLL Sites
==========================================================================
Site                Site-Id   Dest                Admin       Oper  Fwdr
--------------------------------------------------------------------------
No Matching Entries
==========================================================================
===============================================================================
* indicates that the corresponding row element may have been truncated.
A:Dut-A#
Table 15. Output fields: service ID All
Label Description

Service Id

Displays the service identifier

VPN Id

Displays the number that identifies the VPN

Service Type

Specifies the type of service

Name

Displays the name of the service

Description

Displays generic information about the service

Customer Id

Displays the customer identifier

Creation Origin

Displays how the service was created

Last Status Change

Displays the date and time of the most recent status change to this customer

Last Mgmt Change

Displays the date and time of the most recent management-initiated change to this customer

Admin State

Displays the administrative state of the service

Oper State

Displays the operational state of the service

MTU

Displays the largest frame size (in octets) that the service can handle

MTU Check

Displays whether the service performs an MTU check of the ingress packet before forwarding it

VC Switching

Specifies whether the service is configured as a PW switching point

SAP Count

Displays the number of SAPs specified for this service

SDP Bind Count

Displays the number of SDPs bound to this service

SAP Type

Displays the SAP type

Propagate MacFlush

Specifies whether propagating a MAC flush is enabled or disabled

Allow IP Intf Bind

Displays whether the service is enabled for route packets if used with an IES or VPRN service

ETH-CFM Service Specifics

Tunnel Faults

Displays whether tunnel faults are ignored or accepted

Service Destination Points (SDPs)

Description

Displays the description of the split horizon group

SDP Id

Displays the SDP identifier

Type

Indicates whether this service SDP binding is a spoke or a mesh

Spoke Descr

Displays the description of the spoke SDP

VC Type

Displays the service SDP type (for example, spoke)

VC Tag

Displays the explicit dot1q value used when encapsulating to the SDP far end

Admin Path MTU

The configured largest service frame size (in octets) that can be transmitted through this SDP to the far-end router, without requiring the packet to be fragmented.

Oper Path MTU

The actual largest service frame size (in octets) that can be transmitted through this SDP to the far-end router, without requiring the packet to be fragmented.

Delivery

Specifies the type of delivery used by the SDP: MPLS.

Tunnel Far End

Displays the far end IP address where the transport tunnel used by the SDP terminates

LSP Types

Displays the supported LSP types:

  • R = RSVP

  • L = LDP

  • B = BGP

  • I = SR-ISIS

  • O = SR-OSPF

  • T = SR-TE

  • n/a = not applicable

Hash Lbl Sig Cap

Displays whether the hash label signal capability is enabled

Oper Hash Label

Displays the operational state of the hash label

Admin State

Displays the administrative state of this SDP

Oper State

Displays the operational state of this SDP

Acct. Pol

Displays the accounting policy applied to the SDP

Collect Stats

Displays whether accounting statistics are collected on the SDP

Ingress Label

Displays the label used by the far-end device to send packets to this device in this service by this SDP

Egress Label

Displays the label used by this device to send packets to the far-end device in this service by this SDP

Ingress IP Filter-Id

The ID of the ingress IP filter policy

Egress IP Filter-Id

The ID of the egress IP filter policy

Ingress IPv6 Filter-Id

The ID of the ingress IPv6 filter policy

Egress IPv6 Filter-Id

The ID of the egress IPv6 filter policy

Admin ControlWord

Not Preferred — control-word is not configured on the spoke-SDP

Preferred — control-word is configured on the spoke-SDP

Oper ControlWord

True — the spoke-SDP transmits the control word when signaling the peer

False — the spoke-SDP does not transmit the control word when signaling the peer

Last Status Change

Displays the date and time of the most recent status change to this SDP

Signaling

Displays the signaling protocol used to obtain the ingress and egress labels used in frames transmitted and received on this SDP

Last Mgmt Change

Displays the date and time of the most recent management initiated change to this SDP

Endpoint

Displays the endpoint configured in the service

Precedence

Displays the precedence level of the SDP binding

PW Status Sig

Displays whether pseudowire status signaling for spoke SDPs is enabled or disabled

Force Vlan-Vc

Displays whether the spoke-SDP has been configured to transmit the VLAN of the customer packet ingressing the SAP in the service

Class Fwding State

Displays the admin state of class-based forwarding on this SDP

Flags

Specifies the conditions that affect the operating status of this SAP

Local Pw Bits

Displays the setting of the local pseudowire bits

Peer Pw Bits

Displays the setting of the peer pseudowire bits

Peer Vccv CV Bits

Displays the setting of the pseudowire peer VCCV control verification bits (lspPing)

Peer Vccv CC Bits

Displays the setting of the pseudowire peer VCCV control channel bits (pwe3ControlWord, mplsRouterAlertLabel, or both)

Keepalive Information

Admin State

Displays the configured keepalive state

Oper State

Displays the operating keepalive state

Hello Time

Displays how often the SDP Echo Request messages are transmitted on this SDP

Hello Msg Len

Displays the length of the SDP Echo Request messages transmitted on this SDP

Max Drop Count

Displays the maximum number of consecutive SDP Echo Request messages that can be unacknowledged before the keepalive protocol reports a fault

Hold Down Time

Displays the amount of time to wait before the keepalive operating status is eligible to enter the alive state

Statistics

I. Fwd. Pkts.

Displays the number of forwarded ingress packets

I. Fwd. Octs.

Displays the number of forwarded ingress octets

E. Fwd. Pkts.

Displays the number of forwarded egress packets

E. Fwd. Octets

Displays the number of forwarded egress octets

Extra-Tag-Drop-Pkts

Displays the number of packets that were dropped because the number of tags exceeded the number of tags supported by the SAP

Extra-Tag-Drop-Oc*

Displays the number of octets that were dropped because the number of tags exceeded the number of tags supported by the SAP

Control Channel Status

PW Status

Displays the status of the pseudowire (Active or Standby)

Refresh Timer

Displays the configured refresh timer.

The refresh timer is the interval at which the control channel status messages are sent between peers.

Peer Status Expire

False—The timer for receiving the control channel status bits from the peer has not expired; this is the default setting

True —The timer for receiving the control channel status bits from the peer has expired; this field is set to true if the bits are not received from the peer

Request Timer

Displays the configured request timer, which is based on the control channel status request messages sent to the peer

Acknowledgment

False — The node does not send an acknowledgment to the peer; this is the default setting

True — The node sends an acknowledgment to the peer

RSVP/Static LSPs

Associated LSP List

Displays the associated LSPs

Lsp Name

Displays the name of the static LSP

Admin State

Displays the configured state of the service

Oper State

Displays the actual state of the service

Time Since Last Tr*

Displays the time that the associated static LSP has been in service

Number of SDPs

Displays the number of SDPs

Service Access Points

Service Id

Displays the service ID

SAP

Displays the SAP ID

Encap

Displays the encapsulation type of the SAP

Description

Displays the description of the SAP

Admin State

Displays the administrative state of the SAP

Oper State

Displays the operating state of the SAP

Flags

Displays the conditions that affect the operating status of this SAP

Last Status Change

Displays the time of the most recent operating status change to this SAP

Last Mgmt Change

Displays the time of the most recent management-initiated change to this SAP

Dot1Q Ethertype

Displays the value of the dot1q Ethertype

QinQ Ethertype

Displays the value of the qinq Ethertype

Split Horizon Group

Displays the name of the split horizon group for this service

Admin MTU

Displays the configured largest service frame size (in octets) that can be transmitted through the SAP to the far-end router without requiring the packet to be fragmented

Oper MTU

Displays the actual largest service frame size (in octets) that can be transmitted through the SAP to the far-end router, without requiring the packet to be fragmented

Ingr IP Fltr-Id

Displays the ingress filter policy ID assigned to the SAP

Egr IP Fltr-Id

Displays the egress filter policy ID assigned to the SAP

Ingr Mac Fltr-Id

Displays the ingress MAC filter policy ID assigned to the SAP

Egr Mac Fltr-Id

Displays the egress MAC filter policy ID assigned to the SAP

Ingr IPv6 Fltr-Id

Displays the ingress IPv6 filter policy ID assigned to the SAP

Egr IPv6 Fltr-Id

Displays the egress IPv6 filter policy ID assigned to the SAP

tod-suite

Displays whether a time-based policy is applied to a multiservice site

Egr Agg Rate CIR

Displays the CIR rate limit in the access egress direction for the aggregate of the SAP queues

Egr Agg Rate PIR

Displays the PIR rate limit in the access egress direction for the aggregate of the SAP queues

Endpoint

Displays the endpoint configured in the service

Acct. Pol

Displays the accounting policy applied to the SAP

Collect Stats

Displays whether accounting statistics are collected on the SAP

QoS

Ingress qos-policy

Displays the SAP ingress QoS policy ID

Egress qos-policy

Displays the SAP egress QoS policy ID

Table-based

Enabled — Table-based classification has been configured in the QoS policy that has been applied on the SAP

Disabled — Table-based classification has not been configure in the QoS policy that has been applied on the SAP

Aggregate Policer

Rate

Displays the aggregate policer rate

Burst

Displays the aggregate policer burst size

Egress Aggregate Meter

Rate

Displays the egress aggregate meter rate

Burst

Displays the egress aggregate meter burst size

Ingress QoS Classifier Usage

Classifiers Allocated

Displays the number of classifiers allocated to the ingress QoS policy

Meters Allocated

Displays the number of meters allocated to the ingress QoS policy

Classifiers Used

Displays the number of classifiers in use by the ingress QoS policy

Meters Used

Displays the number of meters in use by the ingress QoS policy

SAP Statistics

Packets

(Header) Displays the number of packets counted for the statistic after the last counter reset

Octets

(Header) Displays the number of octets counted for the statistic after the last counter reset

Ingress Stats

Indicates that the following statistics are ingress statistics

Egress Stats

Indicates that the following statistics are egress statistics

Extra-Tag Drop Stats

Displays the number of packets that were dropped because they exceeded the number of tags supported on the SAP

Ingress Drop Stats

Displays the number of packets dropped because of policers that are applied on the SAP

Extra-Tag Drop Stats

Displays the number of packets dropped because they had more tags than the maximum number of tags supported on the SAP

Sap per Meter stats (in/out counter mode)

Packets

(Header) Displays the number of packets counted for the statistic after the last counter reset

Octets

(Header) Displays the number of octets counted for the statistic after the last counter reset

For. InProf

Displays the number of in-profile packets or octets (rate below CIR) forwarded

For. OutProf

Displays the number of out-of-profile packets or octets (rate above CIR) forwarded

Sap per Egress Queue stats

Packets

(Header) Displays the number of packets counted for the statistic after the last counter reset

Octets

(Header) Displays the number of octets counted for the statistic after the last counter reset

Fwd Stats

Displays the number of forwarded packets and octets

Drop Stats

Displays the number of dropped packets and octets

VLL Sites

Site-Id

Displays the site ID

Admin

Displays the administrative state of the VLL site

Oper

Displays the operational state of the VLL site
arp
Syntax

arp [ip-address] | [mac ieee-address] | [sap sap-id] | [interface ip-int-name]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays the ARP table for the VPLS instance. The ARP entries for a subscriber interface are displayed uniquely. Each MAC associated with the subscriber interface child group-interfaces is displayed with each subscriber interface ARP entry for easy lookup.

Parameters
ip-address

Displays all IP addresses.

mac ieee-address

Displays only ARP entries in the ARP table with the specified 48-bit MAC address. The MAC address is in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff, where aa, bb, cc, dd, ee and ff are hexadecimal numbers.

Default

All MAC addresses.

sap sap-id

Displays SAP information for the specified SAP ID.

interface

Specifies matching service ARP entries associated with the IP interface.

ip-address

Specifies the IP address of the interface for which to display matching ARP entries.

Values

a.b.c.d

ip-int-name

Specifies the IP interface name for which to display matching ARPs.

Output

The following table describes the show service-id ARP output fields.

Sample output
Table 16. Output fields: service ID ARP
Label Description

IP Address

The IP address.

MAC Address

The specified MAC address.

Type Static — FDB entries created by management.

Learned — Dynamic entries created by the learning process.

Other — Local entries for the IP interfaces created.

Expiry

The age of the ARP entry.

Interface

The interface applied to the service.

SAP

The SAP ID.
base
Syntax

base [msap]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays basic information about the service ID including service type, description, SAPs and SDPs.

Output

The following output is an example of basic service information, and Output fields: service ID base describes the output fields.

Sample output 

*A:7210SAS# show service id 10 base 

===============================================================================
Service Basic Information
===============================================================================
Service Id        : 10                  Vpn Id            : 0
Service Type      : VPLS                
Name              : (Not Specified)
Description       : (Not Specified)
Customer Id       : 1                   
Last Status Change: 02/06/2106 06:28:12 
Last Mgmt Change  : 01/10/1970 01:55:31 
Admin State       : Down                Oper State        : Down
MTU               : Not Applicable      Def. Mesh VC Id   : 10
SAP Count         : 0                   
Uplink Type:      : L2                  
SAP Type:         : dot1q Range         Customer vlan:    : n/a
 
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier                               Type         AdmMTU  OprMTU  Adm  Opr
-------------------------------------------------------------------------------
No Matching Entries                   
======================================================================
*A:7210SAS# show service id 10 base 

A:Dut-A# show service id 1 base
=======================================================
Service Basic Information
===============================================================================
Service Id : 1 Vpn Id : 0
Service Type : Epipe
Customer Id : 1
Last Status Change: 06/24/2001 00:57:55
Last Mgmt Change : 06/24/2001 00:51:36
Admin State : Up Oper State : Up
MTU : 1514
MTU Check : Disabled
Vc Switching : False
SAP count : 1 SDP Bind Count : 1
----------------------------------------------------------------------------------
Service Access and Destination Points
----------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
----------------------------------------------------------------------------------
sap:1/1/21:1 q-tag 1518 1518 Up Up
sdp:1:1 S<100.1.12> n/a 1518 1518 Up Up
==============================================================----------------------
A:Dut-A#
Table 17. Output fields: service ID base
Label Description

Service Id

The service identifier.

Service Type

Displays the type of service.

Description

Generic information about the service.

Customer Id

The customer identifier.

Last Mgmt Change

The date and time of the most recent management-initiated change to this customer.

Adm

The administrative state of the service.

Oper

The operational state of the service.

Mtu

The largest frame size (in octets) that the can handle.

Adm

The largest frame size (in octets) that the SAP can handle.

SAP Count

The number of SAPs defined on the service.

SAP Type

The type of SAPs allowed in the service. It also describes the applied processing by the node to the packets received on these SAPs.

Identifier

Specifies the service access (SAP).

OprMTU

Specifies the actual largest service frame size (in octets) that can be transmitted through this SAP, without requiring the packet to be fragmented.

Opr

The operating state of the SAP.
fdb
Syntax

fdb [sap sap-id [expiry]] | [mac ieee-address [expiry]] | [detail] [expiry]

Context

show>service>id

show>service>fdb-mac

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays FDB entries for a specific MAC address.

Parameters
sap sap-id

Specifies the physical port identifier portion of the SAP. See Common CLI command descriptions for command syntax.

detail

Keyword to display detailed information.

expiry

Keyword to display the time until the MAC is aged out.

Output

The following output is an example of FDB information, and Output fields: service FDB describes the output fields.

Sample output 
A:Dut-A# show service id 305 fdb
===============================================================================
Forwarding Database, Service 305
===============================================================================
Service Id        : 305                 Mac Move          : Disabled
Mac Move Rate     : 2                   Mac Move Timeout  : 10
Table Size        : 500                 Total Count       : 375
Learned Count     : 375                 Static Count      : 0
Remote Age        : 60                  Local Age         : 60
High WaterMark    : 95%                 Low Watermark     : 90%
Mac Learning      : Enabl               Discard Unknown   : Dsabl
Mac Aging         : Enabl               Relearn Only      : False
===============================================================================
A:Dut-A#
Table 18. Output fields: service FDB
Label Description

ServID

Displays the service ID.

MAC

Displays the associated MAC address.

Mac Move

Displays the administrative state of the MAC movement feature associated with this service.

Primary Factor

Displays a factor for the primary ports defining how many MAC-relearn periods should be used to measure the MAC-relearn rate.

Secondary Factor

Displays a factor for the secondary ports defining how many MAC-relearn periods should be used to measure the MAC-relearn rate.

Mac Move Rate

Displays the maximum rate at which MAC's can be relearned in this service, before the SAP where the moving MAC was last seen is automatically disabled to protect the system against undetected loops or duplicate MAs.

The rate is computed as the maximum number of relearns

allowed in a 5-second interval; for example, the default rate of 2 relearns per second corresponds to 10 relearns in a 5-second period.

Mac Move Timeout

Displays the time in seconds to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

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

Mac Move Retries

Displays the number of times retries are performed for re-enabling the SAP or SDP.

Table Size

Specifies the maximum number of learned and static entries allowed in the FDB of this service.

Total Count

Displays the total number of learned entries in the FDB of this service.

Learned Count

Displays the current number of learned entries in the FDB of this service.

Static Count

Displays the current number of static entries in the FDB of this service.

OAM-learned Count

Displays the current number of OAM entries in the FDB of this service.

Remote Age

Displays the number of seconds used to age out FDB entries learned on an SDP. These entries correspond to MAC addresses learned on remote SAPs.

Local Age

Displays the number of seconds used to age out FDB entries learned on local SAPs.

High Watermark

Displays the utilization of the FDB table of this service at which a table full alarm is raised by the agent.

Low Watermark

Displays the utilization of the FDB table of this service at which a table full alarm is cleared by the agent.

Mac Learning

Specifies whether the MAC learning process is enabled

Discard Unknown

Specifies whether frames received with an unknown destination MAC are discarded.

Mac Aging

Indicates whether the MAC aging process is enabled.

Relearn Only

Displays, that when enabled, either the FDB table of this service is full, or that the maximum system-wide number of

MACs supported by the agent has been reached, and therefore MAC learning is temporary disabled, and only MAC relearns can take place.

Mac Subnet Len

Displays the number of bits to be considered when performing MAC learning or MAC switching.

Source-Identifier

The location where the MAC is defined.

Type/Age

Type — Specifies the number of seconds used to age out TLS FDB entries learned on local SAPs

Age — Specifies the number of seconds used to age out TLS FDB entries learned on an SDP. These entries correspond to MAC addresses learned on remote SAPs

L (Learned) — Dynamic entries created by the learning process.

OAM — Entries created by the OAM process.

Static — Statically configured.

Last Change

Indicates the time of the most recent state changes.
host
Syntax

host [sap sap-id] [detail]

host summary

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays static host information configured on this service.

Parameters
sap-id

Specifies the physical port identifier portion of the SAP definition. See Common CLI command descriptions for command syntax.

summary

Keyword to display summary host information.

labels
Syntax

labels

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays the labels being used by the service.

Output

The following output is an example of service label information, and Output fields: service ID labels describes the output fields.

Sample output 
A:Dut-A# show service id 305 labels
===============================================================================
Martini Service Labels
===============================================================================
Svc Id     Sdp Binding        Type  I.Lbl                 E.Lbl
-------------------------------------------------------------------------------
305        1217:305           Spok  130506                130516
305        1317:305           Spok  130454                130591
305        1417:305           Spok  130428                131015
305        1617:305           Spok  131060                130843
-------------------------------------------------------------------------------
Number of Bound SDPs : 4
===============================================================================
A:Dut-A#
Table 19. Output fields: service ID labels
Label Description

Svc Id

The service identifier.

Sdp Id

The SDP identifier.

Type

Indicates whether the SDP is spoke.

I. Lbl

The VC label used by the far-end device to send packets to this device in this service by the SDP.

E. Lbl

The VC label used by this device to send packets to the far-end device in this service by the SDP.
l2pt
Syntax

l2pt disabled

l2pt [detail]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays Layer 2 Protocol Tunnel (L2-PT) route information associated with this service.

Parameters
disabled

Keyword to display only entries with termination disabled. This helps identify configuration errors.

detail

Keyword to display detailed information.

Output

The following output is an example of L2PT information, and Output fields: L2PT describes the output fields.

Sample output 
*A:7210SAS>show>service# id 1 l2pt detail

===============================================================================
L2pt details, Service id 1
===============================================================================

Service Access Points
-------------------------------------------------------------------------------
SapId                       L2pt-                      Admin Bpdu-  Oper Bpdu-
                            termination                translation  translation
-------------------------------------------------------------------------------
1/1/1                       stp cdp vtp dtp pagp udld  disabled     disabled
-------------------------------------------------------------------------------
Number of SAPs : 1
===============================================================================

===============================================================================
L2pt summary, Service id 1
===============================================================================
       L2pt-term   L2pt-term   Bpdu-trans  Bpdu-trans  Bpdu-trans  Bpdu-trans
       enabled     disabled    auto        disabled    pvst        stp
-------------------------------------------------------------------------------
SAP's  1           0           0           1           0           0
SDP's  0           0           0           0           0           0
-------------------------------------------------------------------------------
Total  1           0           0           1           0           0
===============================================================================
*A:7210SAS>show>service#
Table 20. Output fields: L2PT
Label Description

Service id

Displays the 24-bit (0 to 16777215) service instance identifier for the service.

L2pt-term enabled

Indicates if L2-PT-termination and/or BPDU translation is in use in this service by at least one SAP or spoke-SDP binding. If in use, at least one of L2PT-termination or BPDU translation is enabled.

When enabled it is not possible to enable STP on this service.

L2pt-term disabled

Indicates that L2-PT-termination is disabled.

Bpdu-trans auto

Specifies the number of L2-PT PDUs that are translated before being sent out on a port or sap.

Bpdu-trans disabled

Indicates that BPDU translation is disabled.

SAPs

Displays the number of SAPs with L2PT or BPDU translation enabled or disabled.

SDPs

Displays the number of SDPs with L2PT or BPDU translation enabled or disabled.

Total

Displays the column totals of L2PT entities.

SapId

The ID of the access point where this SAP is defined.

L2pt-termination

Indicates whether L2pt termination is enabled or disabled.

Admin Bpdu-translation

Specifies whether BPDU translation is administratively enabled or disabled.

Oper Bpdu-translation

Specifies whether BPDU translation is operationally enabled or disabled.

SAP Id

Specifies the SAP ID.
mac-move
Syntax

mac-move

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information related to the mac-move feature for the specified service.

Output

The following output is an example of service MAC move information, and Output fields: service MAC move describes the fields.

Sample output 
*A:ALU-48>show>service>id# mac-move
===============================================================================
Service Mac Move Information
===============================================================================
Service Id        : 5001                Mac Move          : Disabled
Primary Factor    : 3                   Secondary Factor  : 2
Mac Move Rate     : 2                   Mac Move Timeout  : 10
Mac Move Retries  : 3
-------------------------------------------------------------------------------
SAP Mac Move Information: 1/2/4:1/100
-------------------------------------------------------------------------------
Admin State       : Up                  Oper State        : Down
Flags              : ServiceAdminDown
                     PortOperDown L2OperDown
Time to RetryReset: never               Retries Left      : 3
Mac Move          : Blockable           Blockable Level   : Tertiary
-------------------------------------------------------------------------------
SDP Mac Move Information: 5001:100
-------------------------------------------------------------------------------
Admin State       : Up                  Oper State        : Down
Flags              : SvcAdminDown SdpOperDown
                     NoIngVCLabel NoEgrVCLabel
                     PathMTUTooSmall
Time to RetryReset: never               Retries Left      : 3
Mac Move          : Blockable           Blockable Level   : Tertiary
===============================================================================
*A:ALU-48>show>service>id#
Table 21. Output fields: service MAC move
Label Description

Service Id

The service identifier.

Mac Move

The administrative state of the MAC movement feature associated with this service.

Primary Factor

A factor for the primary ports defining how many MAC relearn periods should be used to measure the MAC relearn rate.

Secondary Factor

A factor for the secondary ports defining how many MAC relearn periods should be used to measure the MAC relearn rate.

Mac Move Rate

The maximum rate at which MACs can be relearned in this 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 rate is computed as the maximum number of relearns allowed in a 5-second interval: for example, the default rate of 2 relearns per second corresponds to 10 relearns in a 5-second period.

Mac Move Timeout

The time, in seconds, to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

A value of 0 indicates that the SAP is not automatically re-enabled after being disabled. If after the SAP is re-enabled it is disabled again, the effective retry timeout is doubled to avoid thrashing.

Mac Move Retries

The number of times retries are performed for re-enabling the SAP or SDP.

SAP Mac Move Information:

Admin State

The administrative state of the SAP.

Oper State

The operational state of the SAP.

Flags

Specifies the conditions that affect the operating status of this SAP. Display output includes: ServiceAdminDown, PortOperDown, L2OperDown.

Time to RetryReset

The time, in seconds, to wait before a SAP that has been disabled after exceeding the maximum relearn rate is re-enabled.

A value of 0 indicates that the SAP is not automatically re-enabled after being disabled. If after the SAP is re-enabled it is disabled again, the effective retry timeout is doubled to avoid thrashing.

Retries Left

The number of remaining attempts to re-enable the SAP.

Mac Move

Specifies whether MAC move is configured as blockable or not blockable on the SAP.

Blockable Level

Specifies the level at which MAC move is blockable on the SAP (primary, secondary, or tertiary).

SDP Mac Move Information

Admin State

The administrative state of the SDP.

Oper State

The operational state of the SDP.

Flags

Specifies the conditions that affect the operating status of this SDP. Display output includes: SvcAdminDown, SdpOperDown, NoIngVCLabel, NoEgrVCLabel, PathMTUTooSmall.

Time to RetryReset

The time, in seconds, to wait before a SDP that has been disabled after exceeding the maximum relearn rate is re-enabled.

A value of 0 indicates that the SDP is not automatically re-enabled after being disabled. If after the SDP is re-enabled it is disabled again, the effective retry timeout is doubled to avoid thrashing.

Retries Left

The number of remaining attempts to re-enable the SDP.

Mac Move

Specifies whether MAC move is configured as blockable or not blockable on the SDP.

Blockable Level

Specifies the level at which MAC move is blockable on the SDP (primary, secondary, or tertiary).
mrouters
Syntax

mrouters [detail]

Context

show>service>id>mld-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays all multicast routers.

sap
Syntax

sap sap-id detail

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information for the SAPs associated with the service.

If no optional parameters are specified, a summary of all associated SAPs is displayed.

Parameters
sap sap-id

Specifies the ID that displays SAPs for the service in the slot/mda/port[.channel] form. See Common CLI command descriptions for command syntax.

detail

Keyword to display detailed information for the SAP.

Output

The following outputs are examples of SAP information, and Output fields: service SAP describes the output fields.

Sample output 
*A:DUT-B_sasx>show>service>id# sap 1/1/3:63 detail

===============================================================================
Service Access Points(SAP)
===============================================================================
Service Id         : 63
SAP                : 1/1/3:63                 Encap             : q-tag
Description        : (Not Specified)
Admin State        : Up                       Oper State        : Up
Flags              : None
Last Status Change : 05/20/2000 13:33:22
Last Mgmt Change   : 05/19/2000 12:13:41
Loopback Mode      : Internal                 No-svc-port used : 1/1/13
Loopback Src Addr  : 00:00:00:22:22:22 
Loopback Dst Addr  : 00:00:00:11:11:11 
Dot1Q Ethertype    : 0x8100                   QinQ Ethertype    : 0x8100

Max Nbr of MAC Addr: No Limit                 Total MAC Addr    : 59
Learned MAC Addr   : 59                       Static MAC Addr   : 0
Admin MTU          : 1518                     Oper MTU          : 1518
Ingr IP Fltr-Id    : n/a                      Egr IP Fltr-Id    : n/a
Ingr Mac Fltr-Id   : n/a                      Egr Mac Fltr-Id   : n/a
tod-suite          : None                                                 
Egr Agg Rate Limit : 100000                   Host Conn Verify  : Enabled
Mac Learning       : Enabled                  Discard Unkwn Srce: Disabled
Mac Aging          : Enabled                  Mac Pinning       : Disabled
BPDU Translation   : Disabled
L2PT Termination   : Disabled

Acct. Pol          : None                     Collect Stats     : Disabled



-------------------------------------------------------------------------------
Stp Service Access Point specifics
-------------------------------------------------------------------------------
Stp Admin State    : Up                       Stp Oper State    : Down
Core Connectivity  : Down
Port Role          : N/A                      Port State        : Forwarding
Port Number        : 2048                     Port Priority     : 128
Port Path Cost     : 10                       Auto Edge         : Enabled
Admin Edge         : Disabled                 Oper Edge         : N/A
Link Type          : Pt-pt                    BPDU Encap        : Dot1d
Root Guard         : Disabled                 Active Protocol   : N/A
Last BPDU from     : N/A
CIST Desig Bridge  : N/A                      Designated Port   : N/A

Forward transitions: 0                        Bad BPDUs rcvd    : 0
Cfg BPDUs rcvd     : 0                        Cfg BPDUs tx      : 0
TCN BPDUs rcvd     : 0                        TCN BPDUs tx      : 0
RST BPDUs rcvd     : 0                        RST BPDUs tx      : 0
MST BPDUs rcvd     : 0                        MST BPDUs tx      : 0
-------------------------------------------------------------------------------
ARP host
-------------------------------------------------------------------------------
Admin State        : outOfService
Host Limit         : 1                        Min Auth Interval : 15 minutes

-------------------------------------------------------------------------------
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 1                        Egress qos-policy : 1
-------------------------------------------------------------------------------
Sap Egress Policy (1)
-------------------------------------------------------------------------------
Scope              : Template
Remark             : False                    Remark Pol Id     : 2
Accounting         : frame-based
Description    : Default SAP egress QoS policy.
-------------------------------------------------------------------------------
Queue Rates and Rules
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId        CIR          CIR Adpt Rule        PIR          PIR Adpt Rule
-------------------------------------------------------------------------------
Queue1          0              closest            max            closest
Queue2          0              closest            max            closest
Queue3          0              closest            max            closest
Queue4          0              closest            max            closest
Queue5          0              closest            max            closest
Queue6          0              closest            max            closest
Queue7          0              closest            max            closest
Queue8          0              closest            max            closest
-------------------------------------------------------------------------------
Parent Details
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId          Port       CIR Level      PIR Weight
-------------------------------------------------------------------------------
Queue1          True             1             1
Queue2          True             1             1
Queue3          True             1             1
Queue4          True             1             1
Queue5          True             1             1
Queue6          True             1             1
Queue7          True             1             1
Queue8          True             1             1
-------------------------------------------------------------------------------
High Slope
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId        State      Start-Avg(%)   Max-Avg(%)   Max-Prob(%)
-------------------------------------------------------------------------------
Queue1          Down            70           90            75
Queue2          Down            70           90            75
Queue3          Down            70           90            75
Queue4          Down            70           90            75
Queue5          Down            70           90            75
Queue6          Down            70           90            75
Queue7          Down            70           90            75
Queue8          Down            70           90            75
-------------------------------------------------------------------------------
Low Slope
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId        State      Start-Avg(%)   Max-Avg(%)   Max-Prob(%)
-------------------------------------------------------------------------------
Queue1          Down            50           75            75
Queue2          Down            50           75            75
Queue3          Down            50           75            75
Queue4          Down            50           75            75
Queue5          Down            50           75            75
Queue6          Down            50           75            75
Queue7          Down            50           75            75
Queue8          Down            50           75            75
-------------------------------------------------------------------------------
Burst Sizes and Time Average Factor
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId         CBS            MBS       Time Average Factor        Queue-Mgmt
-------------------------------------------------------------------------------
Queue1          def               def              7           default
Queue2          def               def              7           default
Queue3          def               def              7           default
Queue4          def               def              7           default
Queue5          def               def              7           default
Queue6          def               def              7           default
Queue7          def               def              7           default
Queue8          def               def              7           default
-------------------------------------------------------------------------------
Aggregate Policer (Not Available)
-------------------------------------------------------------------------------
rate               : n/a                      burst             : n/a
-------------------------------------------------------------------------------
Ingress QoS Classifier Usage
-------------------------------------------------------------------------------
Classifiers Allocated: 4                     Meters Allocated   : 2
Classifiers Used     : 2                     Meters Used        : 2
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
                        Packets                 Octets
Ingress Stats:          90551093                135826639500
Egress Stats:           0                       0
-------------------------------------------------------------------------------
Sap per Meter stats
-------------------------------------------------------------------------------
                        Packets                 Octets

Ingress Meter 1 (Unicast)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 11 (Multipoint)
For. InProf           : 3                       4500
For. OutProf          : 90611158                135916737000
-------------------------------------------------------------------------------
Sap per Queue stats
-------------------------------------------------------------------------------
                        Packets                 Octets

Egress Queue 1 (be)
Fwd Stats            :  90593283                137701790160
Drop InProf          :  0                       0
Drop OutProf         :  0                       0

Egress Queue 2 (l2)
Fwd Stats            :  0                       0
Drop InProf          :  0                       0
Drop OutProf         :  0                       0

Egress Queue 3 (af)
Fwd Stats            :  0                       0
Drop InProf          :  0                       0
Drop OutProf         :  0                       0

Egress Queue 4 (l1)
Fwd Stats            :  0                       0
Drop InProf          :  0                       0
Drop OutProf         :  0                       0

Egress Queue 5 (h2)
Fwd Stats            :  0                       0
Drop InProf          :  0                       0
Drop OutProf         :  0                       0

Egress Queue 6 (ef)
Fwd Stats            :  0                       0
Drop InProf          :  0                       0
Drop OutProf         :  0                       0

Egress Queue 7 (h1)
Fwd Stats            :  0                       0
Drop InProf          :  0                       0
Drop OutProf         :  0                       0

Egress Queue 8 (nc)
Fwd Stats            :  0                       0
Drop InProf          :  0                       0
Drop OutProf         :  0                       0
===============================================================================
*A:DUT-B_sasx>show>service>id#
Sample output for 7210 SAS-R6 and 7210 SAS-R12 
*A:Dut-A# show service id 10 sap 5/1/1:800 detail 
===============================================================================
Service Access Points(SAP)
===============================================================================
Service Id         : 10                       
SAP                : 5/1/1:800                Encap             : q-tag
Description        : (Not Specified)
Admin State        : Up                       Oper State        : Down
Flags              : PortOperDown
Last Status Change : 11/07/2017 04:48:25      
Last Mgmt Change   : 11/07/2017 05:02:47      
Dot1Q Ethertype    : 0x8100                   QinQ Ethertype    : 0x8100
Split Horizon Group: (Not Specified)
Admin MTU          : 1518                     Oper MTU          : 1518
Ingr IP Fltr-Id    : n/a                      Egr IP Fltr-Id    : n/a
Ingr Mac Fltr-Id   : n/a                      Egr Mac Fltr-Id   : n/a
Ingr IPv6 Fltr-Id  : n/a                      Egr IPv6 Fltr-Id  : n/a
BGP IPv4 FlowSpec  : Disabled
BGP IPv6 FlowSpec  : Disabled
tod-suite          : None                     
Egr Agg Rate CIR   : 0                        Egr Agg Rate PIR  : max
                                              Limit Unused BW   : Disabled
Acct. Pol          : None                     Collect Stats     : Disabled
Anti Spoofing      : None                     Dynamic Hosts     : Enabled
Oper Group         : (none)                   Monitor Oper Grp  : (none)
Host Lockout Plcy  : n/a                      
Lag Link Map Prof  : (none)                   
-------------------------------------------------------------------------------
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 17                       Egress qos-policy : 1
Table-based        : enabled
-------------------------------------------------------------------------------
Aggregate Policer
-------------------------------------------------------------------------------
Rate               : n/a                      Burst             : n/a
-------------------------------------------------------------------------------
Egress Aggregate Meter
-------------------------------------------------------------------------------
Rate               : n/a                      Burst             : n/a
-------------------------------------------------------------------------------
Ingress QoS Classifier Usage
-------------------------------------------------------------------------------
Classifiers Allocated: 60                    Meters Allocated   : 30
Classifiers Used     : 9                     Meters Used        : 8
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
                        Packets                 Octets
Ingress Stats:          0                       0                        
Egress Stats:           0                       0                        
Ingress Drop Stats:     0                       0                        
 
Extra-Tag Drop Stats:   n/a                     n/a                      
-------------------------------------------------------------------------------
Sap per Meter stats (in/out counter mode)
-------------------------------------------------------------------------------
                        Packets                 Octets
Ingress Meter 1
For. InProf           : 0                       0                        
For. OutProf          : 0                       0                        
 
Ingress Meter 2
For. InProf           : 0                       0                        
For. OutProf          : 0                       0                        
 
Ingress Meter 3
For. InProf           : 0                       0                        
For. OutProf          : 0                       0                        
 
Ingress Meter 4
For. InProf           : 0                       0                        
For. OutProf          : 0                       0                        
 
Ingress Meter 5
For. InProf           : 0                       0                        
For. OutProf          : 0                       0                        
 
Ingress Meter 6
For. InProf           : 0                       0                        
For. OutProf          : 0                       0                        
 
Ingress Meter 7
For. InProf           : 0                       0                        
For. OutProf          : 0                       0                        
 
Ingress Meter 8
For. InProf           : 0                       0                        
For. OutProf          : 0                       0                        
===============================================================================
Table 22. Output fields: service SAP
Label Description

Service Id

The service identifier.

SAP

The SAP and qtag.

Encap

The encapsulation type of the SAP.

Ethertype

Specifies an Ethernet type II Ethertype value.

Admin State

The administrative state of the SAP.

Oper State

The operational state of the SAP.

Flags

Specifies the conditions that affect the operating status of this SAP.

Display output includes: ServiceAdminDown, SapAdminDown, InterfaceAdminDown, PortOperDown, L2OperDown, RelearnLimitExceeded, ParentIfAdminDown, TodResourceUnavail, TodMssResourceUnavail, SapParamMismatch, SapIngressNamedPoolMismatch, SapEgressNamedPoolMismatch, NoSapEpipeRingNode.

Last Status Change

Specifies the time of the most recent operating status change to this SAP

Last Mgmt Change

Specifies the time of the most recent management-initiated change to this SAP.

Ingress qos-policy

The ingress QoS policy ID assigned to the SAP.

Ingress Filter-Id

The ingress filter policy ID assigned to the SAP.

Egress Filter-Id

The egress filter policy ID assigned to the SAP.

Acct. Pol

The accounting policy ID assigned to the SAP.

Collect Stats

Specifies whether collect stats is enabled.

SAP per Meter stats

Ingress Meter

Specifies the meter ID.

For. InProf

The number of in-profile packets and octets (rate below CIR) forwarded.

For. OutProf

The number of out-of-profile packets and octets.

Ingress TD Profile

The profile ID applied to the ingress SAP.

Egress TD Profile

The profile ID applied to the egress SAP.

Alarm Cell Handling

The indication that OAM cells are being processed.

AAL-5 Encap

The AAL-5 encapsulation type.

Aggregate Policer

rate-indicates the rate of the aggregate policer.

burst-indicates the burst-size of the aggregate policer.

Loopback Mode

Displays the Ethernet port loopback mode.

Loopback Src Addr

Displays the configured loopback source address.

Loopback Dst Addr

Displays the configured loopback destination address.

No-svc-port used

Displays the port ID of the port on which no service is configured.

This port is used for the port loop back with MAC swap functionality.

Egr Agg Rate Limit

Displays the egress aggregate rate limit.

Loopback Mode

Displays the Ethernet port loopback mode.

Loopback Src Addr

Displays the configured loopback source address.

Loopback Dst Addr

Displays the configured loopback destination address.

No-svc-port used

Displays the port ID of the port on which no service is configured. This port is used for the port loop back with MAC swap functionality.

Table-based

Indicates the use of table-based resource classification: Enabled (table-based) or Disabled (CAM-based).
sdp
Syntax

sdp [sdp-id | far-end ip-addr] [detail]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information for the SDPs associated with the service. If no optional parameters are specified, a summary of all associated SDPs is displayed.

Parameters
sdp-id

Displays information for only the specified SDP ID.

Default

All SDPs

Values

1 to 17407

far-end ip-addr

Displays only SDPs matching with the specified far-end IP address.

Default

SDPs with any far-end IP address.

detail

Keyword to display detailed SDP information.

Output

The following output is an example of SDP information, and Output fields: service ID SDP describes the output fields.

Sample output 
A:Dut-A>show>service>id# sdp 1217:305
===============================================================================
Service Destination Point (Sdp Id : 1217:305)
===============================================================================
SdpId            Type IP address      Adm     Opr       I.Lbl       E.Lbl
-------------------------------------------------------------------------------
1217:305         Spok 10.20.1.2       Up      Up        130506      130516
-------------------------------------------------------------------------------
Number of SDPs : 1
===============================================================================
A:Dut-A>show>service>id# sdp 1217:305  detail


A:Dut-A>show>service>id# 
===============================================================================
Service Destination Point (Sdp Id : 1217:305) Details
-------------------------------------------------------------------------------
 Sdp Id 1217:305  -(10.20.1.2)
-------------------------------------------------------------------------------
Description     : Default sdp description
SDP Id             : 1217:305                 Type              : Spoke
VC Type            : Ether                    VC Tag            : n/a
Admin Path MTU     : 0                        Oper Path MTU     : 9186
Far End            : 10.20.1.2                Delivery          : MPLS

Admin State        : Up                       Oper State        : Up
Acct. Pol          : None                     Collect Stats     : Disabled
Managed by Service : 300                      Prune State       : Not Pruned
Managed by Spoke   : 1217:300
Ingress Label      : 130506                   Egress Label      : 130516
Admin ControlWord  : Not Preferred            Oper ControlWord  : False
Last Status Change : 07/07/2009 18:49:40      Signaling         : TLDP
Last Mgmt Change   : 07/07/2009 14:39:14      Force Vlan-Vc     : Disabled
Last Mgmt Change   : 07/07/2009 14:39:14
Flags              : None
Peer Pw Bits       : None
Peer Fault Ip      : None
Max Nbr of MAC Addr: No Limit                 Total MAC Addr    : 0
Learned MAC Addr   : 0                        Static MAC Addr   : 0

MAC Learning       : Enabled                  Discard Unkwn Srce: Disabled
MAC Aging          : Enabled
L2PT Termination   : Disabled                 BPDU Translation  : Disabled
MAC Pinning        : Disabled

KeepAlive Information :
Admin State        : Enabled                  Oper State        : Alive
Hello Time         : 10                       Hello Msg Len     : 0
Max Drop Count     : 3                        Hold Down Time    : 10

Statistics            :
I. Fwd. Pkts.      : 13601                    I. Fwd. Octs.     : 10676338
E. Fwd. Pkts.      : 83776987                 E. Fwd. Octets    : 51589499116

Associated LSP LIST :
Lsp Name           : A_B_17
Admin State        : Up                       Oper State        : Up
Time Since Last Tr*: 08h31m06s
-------------------------------------------------------------------------------
Stp Service Destination Point specifics
-------------------------------------------------------------------------------
Mac Move           : Blockable
Stp Admin State    : Down                     Stp Oper State    : Down
Core Connectivity  : Down
Port Role          : N/A                      Port State        : Forwarding
Port Number        : 2049                     Port Priority     : 128
Port Path Cost     : 10                       Auto Edge         : Enabled
Admin Edge         : Disabled                 Oper Edge         : N/A
Link Type          : Pt-pt                    BPDU Encap        : Dot1d
Root Guard         : Disabled                 Active Protocol   : N/A
Last BPDU from     : N/A
Designated Bridge  : N/A                      Designated Port Id: 0

Fwd Transitions    : 0                        Bad BPDUs rcvd    : 0
Cfg BPDUs rcvd     : 0                        Cfg BPDUs tx      : 0
TCN BPDUs rcvd     : 0                        TCN BPDUs tx      : 0
RST BPDUs rcvd     : 0                        RST BPDUs tx      : 0
-------------------------------------------------------------------------------
Number of SDPs : 1
-------------------------------------------------------------------------------
===============================================================================
* indicates that the corresponding row element may have been truncated.
A:Dut-A>show>service>id#
Table 23. Output fields: service ID SDP
Label Description

Sdp Id

The SDP identifier.

Type

Indicates whether the SDP is spoke.

VC Type

Displays the VC type: Ether, VLAN, or VPLS.

VC Tag

Displays the explicit dot1Q value used when encapsulating to the SDP far end.

I. Lbl

The VC label used by the far-end device to send packets to this device in this service by the SDP.

Admin Path MTU

The operating path MTU of the SDP is equal to the admin path MTU (when one is set) or the dynamically computed tunnel MTU, when no admin path MTU is set (the default case.)

Oper Path MTU

The actual largest service frame size (in octets) that can be transmitted through this SDP to the far-end router, without requiring the packet to be fragmented.

Far End

Specifies the IP address of the remote end of the MPLS tunnel defined by this SDP.

Delivery

Specifies the type of delivery used by the SDP: MPLS.

Admin State

The administrative state of this SDP.

Oper State

The current status of the SDP.

Ingress Label

The label used by the far-end device to send packets to this device in this service by this SDP.

Egress Label

The label used by this device to send packets to the far-end device in this service by the SDP.

Last Changed

The date and time of the most recent change to the SDP.

Signaling

Specifies the signaling protocol used to obtain the ingress and egress labels used in frames transmitted and received on this SDP.

Admin State

The administrative state of the keepalive process.

Oper State

The operational state of the keepalive process.
split-horizon-group
Syntax

split-horizon-group [group-name]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays service split horizon groups.

Parameters
group-name

Specifies a split horizon group name.

Output

The following output is an example of service split horizon group information, and Output fields: split horizon group describes the fields.

Sample output 
*A:ALU-48>show>service>id# split-horizon-group
===============================================================================
Service: Split Horizon Group
===============================================================================
Name                               Description
-------------------------------------------------------------------------------
R   shg5001
-------------------------------------------------------------------------------
R = Residential Split Horizon Group
A = Auto Created Split Horizon Group
No. of Split Horizon Groups: 1
*A:ALU-48>show>service>id# split-horizon-group shg5001
===============================================================================
Service: Split Horizon Group
===============================================================================
Name                               Description
-------------------------------------------------------------------------------
R   shg5001
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
SAP                                1/2/4:1/100
SDP                                5001:100
-------------------------------------------------------------------------------
R = Residential Split Horizon Group
SAPs Associated : 1                SDPs Associated : 1
===============================================================================
*A:ALU-48>show>service>id#
Table 24. Output fields: split horizon group
Label Description

Name

The name of the split horizon group. When preceded by ‟R”, the group is a residential split horizon group.

Description

A description of the split horizon group as configured by the user.

Associations

A list of SAPs and SDPs associated with the split horizon group.
stp
Syntax

stp [detail]

stp mst-instance mst-inst-number

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information for the STP instance for the service.

Parameters
detail

Keyword to display detailed information.

mst-inst-number

Displays information about the specified MST.

Values

1 to 4094

Output

The following output is an example of STP information, and Output fields: service ID STP describes the output fields.

Sample output 
A:Dut-A>show>service>id# stp
===============================================================================
Stp info, Service 305
===============================================================================
Bridge Id          : 00:0d.00:20:ab:cd:00:01  Top. Change Count : 5
Root Bridge        : This Bridge              Stp Oper State    : Up
Primary Bridge     : N/A                      Topology Change   : Inactive
Mode               : Rstp                     Last Top. Change  : 0d 08:35:16
Vcp Active Prot.   : N/A
Root Port          : N/A                      External RPC      : 0
===============================================================================
Stp port info
===============================================================================
Sap/Sdp Id         Oper-     Port-      Port-       Port-  Oper-  Link-  Active
                   State     Role       State       Num    Edge   Type   Prot.
-------------------------------------------------------------------------------
1/1/16:305         Up        Designated Forward     2048   False  Pt-pt  Rstp
lag-4:305          Up        Designated Forward     2000   False  Pt-pt  Rstp
1217:305           Up        N/A        Forward     2049   N/A    Pt-pt  N/A
1317:305           Up        N/A        Forward     2050   N/A    Pt-pt  N/A
1417:305           Up        N/A        Forward     2051   N/A    Pt-pt  N/A
1617:305           Pruned    N/A        Discard     2052   N/A    Pt-pt  N/A
===============================================================================
A:Dut-A>show>service>id# 


A:Dut-A>show>service>id# stp detail
===============================================================================
Spanning Tree Information
===============================================================================
VPLS Spanning Tree Information
-------------------------------------------------------------------------------
VPLS oper state    : Up                       Core Connectivity : Down
Stp Admin State    : Up                       Stp Oper State    : Up
Mode               : Rstp                     Vcp Active Prot.  : N/A

Bridge Id          : 00:0d.00:20:ab:cd:00:01  Bridge Instance Id: 13
Bridge Priority    : 0                        Tx Hold Count     : 6
Topology Change    : Inactive                 Bridge Hello Time : 2
Last Top. Change   : 0d 08:35:29              Bridge Max Age    : 20
Top. Change Count  : 5                        Bridge Fwd Delay  : 15
MST region revision: 0                        Bridge max hops   : 20
MST region name    :

Root Bridge        : This Bridge
Primary Bridge     : N/A

Root Path Cost     : 0                        Root Forward Delay: 15
Rcvd Hello Time    : 2                        Root Max Age      : 20
Root Priority      : 13                       Root Port         : N/A
-------------------------------------------------------------------------------
Spanning Tree Sap/Spoke SDP Specifics
-------------------------------------------------------------------------------
SAP Identifier     : 1/1/16:305               Stp Admin State   : Up
Port Role          : Designated               Port State        : Forwarding
Port Number        : 2048                     Port Priority     : 128
Port Path Cost     : 10                       Auto Edge         : Enabled
Admin Edge         : Disabled                 Oper Edge         : False
Link Type          : Pt-pt                    BPDU Encap        : PVST
Root Guard         : Disabled                 Active Protocol   : Rstp
Last BPDU from     : 80:04.00:0a:1b:2c:3d:4e
CIST Desig Bridge  : This Bridge              Designated Port   : 34816
Forward transitions: 5                        Bad BPDUs rcvd    : 0
Cfg BPDUs rcvd     : 0                        Cfg BPDUs tx      : 0
TCN BPDUs rcvd     : 0                        TCN BPDUs tx      : 0
RST BPDUs rcvd     : 29                       RST BPDUs tx      : 23488
MST BPDUs rcvd     : 0                        MST BPDUs tx      : 0

SAP Identifier     : lag-4:305                Stp Admin State   : Up
Port Role          : Designated               Port State        : Forwarding
Port Number        : 2000                     Port Priority     : 128
Port Path Cost     : 10                       Auto Edge         : Enabled
Admin Edge         : Disabled                 Oper Edge         : False
Link Type          : Pt-pt                    BPDU Encap        : Dot1d
Root Guard         : Disabled                 Active Protocol   : Rstp
Last BPDU from     : 80:04.00:0a:1b:2c:3d:4e
CIST Desig Bridge  : This Bridge              Designated Port   : 34768
Forward transitions: 4                        Bad BPDUs rcvd    : 0
Cfg BPDUs rcvd     : 0                        Cfg BPDUs tx      : 0
TCN BPDUs rcvd     : 0                        TCN BPDUs tx      : 0
RST BPDUs rcvd     : 23                       RST BPDUs tx      : 23454
MST BPDUs rcvd     : 0                        MST BPDUs tx      : 0

SDP Identifier     : 1217:305                 Stp Admin State   : Down
Port Role          : N/A                      Port State        : Forwarding
Port Number        : 2049                     Port Priority     : 128
Port Path Cost     : 10                       Auto Edge         : Enabled
Admin Edge         : Disabled                 Oper Edge         : N/A
Link Type          : Pt-pt                    BPDU Encap        : Dot1d
Root Guard         : Disabled                 Active Protocol   : N/A
Last BPDU from     : N/A
Designated Bridge  : N/A                      Designated Port Id: 0
Fwd Transitions    : 0                        Bad BPDUs rcvd    : 0
Cfg BPDUs rcvd     : 0                        Cfg BPDUs tx      : 0
TCN BPDUs rcvd     : 0                        TCN BPDUs tx      : 0
RST BPDUs rcvd     : 0                        RST BPDUs tx      : 0

SDP Identifier     : 1317:305                 Stp Admin State   : Down
Port Role          : N/A                      Port State        : Forwarding
Port Number        : 2050                     Port Priority     : 128
Port Path Cost     : 10                       Auto Edge         : Enabled
Admin Edge         : Disabled                 Oper Edge         : N/A
Link Type          : Pt-pt                    BPDU Encap        : Dot1d
Root Guard         : Disabled                 Active Protocol   : N/A
Last BPDU from     : N/A
Designated Bridge  : N/A                      Designated Port Id: 0
Fwd Transitions    : 0                        Bad BPDUs rcvd    : 0
Cfg BPDUs rcvd     : 0                        Cfg BPDUs tx      : 0
TCN BPDUs rcvd     : 0                        TCN BPDUs tx      : 0
RST BPDUs rcvd     : 0                        RST BPDUs tx      : 0

SDP Identifier     : 1417:305                 Stp Admin State   : Down
Port Role          : N/A                      Port State        : Forwarding
Port Number        : 2051                     Port Priority     : 128
Port Path Cost     : 10                       Auto Edge         : Enabled
Admin Edge         : Disabled                 Oper Edge         : N/A
Link Type          : Pt-pt                    BPDU Encap        : Dot1d
Root Guard         : Disabled                 Active Protocol   : N/A
Last BPDU from     : N/A
Designated Bridge  : N/A                      Designated Port Id: 0
Fwd Transitions    : 1                        Bad BPDUs rcvd    : 0
Cfg BPDUs rcvd     : 0                        Cfg BPDUs tx      : 0
TCN BPDUs rcvd     : 0                        TCN BPDUs tx      : 0
RST BPDUs rcvd     : 0                        RST BPDUs tx      : 0

SDP Identifier     : 1617:305                 Stp Admin State   : Down
Port Role          : N/A                      Port State        : Discarding
Port Number        : 2052                     Port Priority     : 128
Port Path Cost     : 10                       Auto Edge         : Enabled
Admin Edge         : Disabled                 Oper Edge         : N/A
Link Type          : Pt-pt                    BPDU Encap        : Dot1d
Root Guard         : Disabled                 Active Protocol   : N/A
Last BPDU from     : N/A
Designated Bridge  : N/A                      Designated Port Id: 0
Fwd Transitions    : 0                        Bad BPDUs rcvd    : 0
Cfg BPDUs rcvd     : 0                        Cfg BPDUs tx      : 0
TCN BPDUs rcvd     : 0                        TCN BPDUs tx      : 0
RST BPDUs rcvd     : 0                        RST BPDUs tx      : 0
===============================================================================
A:Dut-A>show>service>id#
Table 25. Output fields: service ID STP
Label Description

Bridge-id

Specifies the MAC address used to identify this bridge in the network.

Bridge fwd delay

Specifies how fast a bridge changes its state when moving toward the forwarding state.

Bridge Hello time

Specifies the amount of time between the transmission of configuration BPDUs.

Bridge max age

Specifies the maximum age of STP information learned from the network on any port before it is discarded. This is the actual value that this bridge is currently using.

Bridge priority

Defines the priority of the STP instance associated with this service.

Topology change

Specifies whether a topology change is currently in progress.

Last Top. change

Specifies the time (in hundredths of a second) after the last time a topology change was detected by the STP instance associated with this service.

Top. change count

Specifies the total number of topology changes detected by the Spanning Tree Protocol instance associated with this service after the management entity was last reset or initialized.

Root bridge-id

Specifies the bridge identifier of the root of the spanning tree as determined by the STP instance associated with this service. This value is used as the Root Identifier parameter in all configuration BPDUs originated by this node.

Root path cost

Specifies the cost of the path to the root bridge as seen from this bridge.

Root forward delay

Specifies how fast the root changes its state when moving toward the forwarding state.

hello time

Specifies the amount of time between the transmission of configuration BPDUs.

Root max age

Specifies the maximum age of STP information learned from the network on any port before it is discarded.

Root priority

This object specifies the priority of the bridge that is currently selected as root-bridge for the network.

Root port

Specifies the port number of the port which provides the lowest cost path from this bridge to the root bridge.

SAP Identifier

The ID of the access port where this SAP is defined.

BPDU encap

Specifies the type of encapsulation used on BPDUs sent out and received on this SAP.

Port Number

Specifies the value of the port number field that is contained in the least significant 12 bits of the 16-bit port ID associated with this SAP.

Priority

Specifies the value of the port priority field that is contained in the most significant 4 bits of the 16-bit port ID associated with this SAP.

Cost

Specifies the contribution of this port to the path cost of paths toward the spanning tree root which include this port.

Designated Port

Specifies the port identifier of the port on the designated bridge for this port segment.

Designated Bridge

Specifies the bridge identifier of the bridge which this port considers to be the designated bridge for this port segment.
mstp-configuration
Syntax

mstp-configuration

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays the MSTP specific configuration data. This command is valid only on a management VPLS.

Output

The following table describes the show service ID MSTP command output fields.

Show output
Table 26. Output fields: service ID MSTP configuration
Label Description

Region Name

Displays the MSTP region name.

Region Revision

Displays the MSTP region revision.

MST Max Hops

Displays the MSTP maximum hops specified.

Instance

Displays the MSTP instance number.

Priority

Displays the MSTP priority.

Vlans mapped

Displays the VLAN range of the MSTP instance.
dhcp
Syntax

dhcp

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context display DHCP information for the specified service.

statistics
Syntax

statistics [sap sap-id]

statistics [sdp sdp-id:vc-id]

statistics [interface interface-name]

Context

show>service>id>dhcp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Displays DHCP statistics information.

Parameters
sap-id

Specifies the physical port identifier portion of the SAP definition.

sdp-id

Specifies the SDP identifier.

Values

1 to 17407

interface-name

Specifies an IP interface for which to display information.

Output

The following output is an example of DHCP statistics information, and Output fields: DHCP statistics describes the output fields.

Sample output 
*A:7210SAS>show>service>id>dhcp# statistics

====================================================================
DHCP Global Statistics, service 1
====================================================================
Rx Packets                           : 416554
Tx Packets                           : 206405
Rx Malformed Packets                 : 0
Rx Untrusted Packets                 : 0
Client Packets Discarded             : 0
Client Packets Relayed               : 221099
Client Packets Snooped               : 0
Client Packets Proxied (RADIUS)      : 0
Client Packets Proxied (Lease-Split) : 0
Server Packets Discarded             : 0
Server Packets Relayed               : 195455
Server Packets Snooped               : 0
DHCP RELEASEs Spoofed                : 0
DHCP FORCERENEWs Spoofed             : 0
====================================================================
*A:7210SAS>show>service>id>dhcp#
Table 27. Output fields: DHCP statistics
Label Description

Received Packets

The number of packets received from the DHCP clients. Includes DHCP packets received from both DHCP client and DHCP server.

Transmitted Packets

The number of packets transmitted to the DHCP clients. Includes DHCP packets transmitted from both DHCP client and DHCP server.

Received Malformed Packets

The number of corrupted/invalid packets received from the DHCP clients. Includes DHCP packets received from both DHCP client and DHCP server.

Received Untrusted Packets

The number of untrusted packets received from the DHCP clients. In this case, a frame is dropped because of the client sending a DHCP packet with Option 82 filled in before ‟trust” is set under the DHCP interface command.

Client Packets Discarded

The number of packets received from the DHCP clients that were discarded.

Client Packets Relayed

The number of packets received from the DHCP clients that were forwarded.

Client Packets Snooped

The number of packets received from the DHCP clients that were snooped.

Server Packets Discarded

The number of packets received from the DHCP server that were discarded.

Server Packets Relayed

The number of packets received from the DHCP server that were forwarded.

Server Packets Snooped

The number of packets received from the DHCP server that were snooped.
summary
Syntax

summary [interface interface-name]

Context

show>service>id>dhcp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays DHCP configuration summary information.

Parameters
interface interface-name

Specifies an IP interface for which to display information.

Output

The following output is an example of summary DHCP information, and Output fields: DHCP summary describes the output fields.

Sample output 
A:7210SAS# show service id 1 dhcp summary
DHCP Summary, service 1
=======================================================================

Interface Name                   Arp      Used/                 Info    Admin
  SapId/Sdp                      Populate Provided              Option  State
-------------------------------------------------------------------------------
egr_1                            No       0/0                   Replace Up
i_1                              No       0/0                   Replace Up
-------------------------------------------------------------------------------
Interfaces: 2
=======================================================================

*A:7210SAS>show>service>id>dhcp#
Table 28. Output fields: DHCP summary
Label Description

Interface Name

Name of the router interface.

Arp Populate

Specifies whether ARP populate is enabled. 7210 SAS does not support ARP populate.

Used/Provided

7210 SAS does not maintain lease state.

Info Option

Indicates whether Option 82 processing is enabled on the interface.

Admin State

Indicates the administrative state.
IGMP snooping show commands
igmp-snooping
Syntax

igmp-snooping

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context display IGMP snooping information.

all
Syntax

all

Context

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays detailed information for all aspects of IGMP snooping on the VPLS service.

Output

The following output is an example of detailed IGMP snooping information, and Output fields: service ID IGMP snooping describes the output fields.

Sample output 
*A:SAS-R2-043# show service id 100 igmp-snooping all

===============================================================================
IGMP Snooping info for service 100
===============================================================================

-------------------------------------------------------------------------------
IGMP Snooping Base info
-------------------------------------------------------------------------------
Admin State : Up
Querier     : 10.20.20.7 on SAP 1/1/1:100
-------------------------------------------------------------------------------
Sap/Sdp                    Oper  MRtr Send  Max  MVR       Num
Id                         State Port Qries Grps From-VPLS Grps
-------------------------------------------------------------------------------
sap:1/1/1:100              Up    Yes  No    None Local     0
sap:1/1/4:100              Up    No   No    None Local     2
sap:1/1/5                  Up    No   No    None Local     0
sap:1/1/10:100             Up    No   No    None Local     0
sap:2/1/1                  Up    No   No    None Local     0

-------------------------------------------------------------------------------
IGMP Snooping Querier info
-------------------------------------------------------------------------------
Sap Id                  : 1/1/1:100
IP Address              : 10.20.20.7
Expires                 : 254s
Up Time                 : 0d 00:26:11
Version                 : 2

General Query Interval  : 125s
Query Response Interval : 10.0s
Robust Count            : 2
-------------------------------------------------------------------------------
IGMP Snooping Multicast Routers
-------------------------------------------------------------------------------
MRouter          Sap/Sdp Id                 Up Time        Expires   Version
-------------------------------------------------------------------------------
10.20.20.7       1/1/1:100                  0d 00:26:11    255s      2
-------------------------------------------------------------------------------
Number of mrouters: 1

-------------------------------------------------------------------------------
IGMP Snooping Proxy-reporting DB
-------------------------------------------------------------------------------
Group Address    Up Time
-------------------------------------------------------------------------------
239.4.4.4        0d 00:21:59
239.4.4.5        0d 00:21:53
-------------------------------------------------------------------------------
Number of groups: 2

-------------------------------------------------------------------------------
IGMP Snooping SAP 1/1/1:100 Port-DB
-------------------------------------------------------------------------------
Group Address   Type    From-VPLS  Up Time        Expires  MC
                                                           Stdby
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Number of groups: 0

-------------------------------------------------------------------------------
IGMP Snooping SAP 1/1/4:100 Port-DB
-------------------------------------------------------------------------------
Group Address   Type    From-VPLS  Up Time        Expires  MC
                                                           Stdby
-------------------------------------------------------------------------------
239.4.4.4       static  local      0d 00:21:59    never
239.4.4.5       static  local      0d 00:21:53    never
-------------------------------------------------------------------------------
Number of groups: 2
-------------------------------------------------------------------------------
IGMP Snooping SAP 1/1/5 Port-DB
-------------------------------------------------------------------------------
Group Address   Type    From-VPLS  Up Time        Expires  MC
                                                           Stdby
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Number of groups: 0

-------------------------------------------------------------------------------
IGMP Snooping SAP 1/1/10:100 Port-DB
-------------------------------------------------------------------------------
Group Address   Type    From-VPLS  Up Time        Expires  MC
                                                           Stdby
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Number of groups: 0

-------------------------------------------------------------------------------
IGMP Snooping SAP 2/1/1 Port-DB
-------------------------------------------------------------------------------
Group Address   Type    From-VPLS  Up Time        Expires  MC
                                                           Stdby
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Number of groups: 0
-------------------------------------------------------------------------------
IGMP Snooping Static Groups
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
IGMP Snooping Static Groups for SAP 1/1/4:100
-------------------------------------------------------------------------------
Group
-------------------------------------------------------------------------------
239.4.4.4
239.4.4.5
-------------------------------------------------------------------------------
Static (*,G) entries: 2

-------------------------------------------------------------------------------
IGMP Snooping Statistics
-------------------------------------------------------------------------------
Message Type            Received      Transmitted   Forwarded
-------------------------------------------------------------------------------
General Queries         1269          0             5075
Group Queries           0             0             0
V1 Reports              0             0             0
V2 Reports              0             464           0
V2 Leaves               0             0             0
Unknown Type            0             N/A           0
-------------------------------------------------------------------------------
Drop Statistics
Bad Length               : 0
Bad IP Checksum          : 0
Bad IGMP Checksum        : 0
Bad Encoding             : 0
No Router Alert          : 0
Zero Source IP           : 0
Wrong Version            : 0
Lcl-Scope Packets        : 0

Send Query Cfg Drops     : 0
Import Policy Drops      : 0
Exceeded Max Num Groups  : 0
MCS Failures             : 0

MVR From VPLS Cfg Drops  : 0
MVR To SAP Cfg Drops     : 0

-------------------------------------------------------------------------------
IGMP Snooping Multicast VPLS Registration info
-------------------------------------------------------------------------------
IGMP Snooping Admin State : Up

MVR Admin State           : Down
MVR Policy                : None
-------------------------------------------------------------------------------
Local SAPs/SDPs
-------------------------------------------------------------------------------
Svc Id     Sap/Sdp                    Oper      From       Num Local
           Id                         State     VPLS       Groups
-------------------------------------------------------------------------------
100        sap:1/1/1:100              Up        Local      0
100        sap:1/1/4:100              Up        Local      2
100        sap:1/1/5                  Up        Local      0
100        sap:1/1/10:100             Up        Local      0
100        sap:2/1/1                  Up        Local      0
-------------------------------------------------------------------------------
MVR SAPs (from-vpls=100)
-------------------------------------------------------------------------------
Svc Id     Sap/Sdp                    Oper      From       Num MVR
           Id                         State     VPLS       Groups
-------------------------------------------------------------------------------
No MVR SAPs found.
===============================================================================
*A:SAS-R2-043#
Table 29. Output fields: service ID IGMP snooping
Label Description

Admin State

The administrative state of the IGMP instance.

Querier

Displays the address of the IGMP querier on the IP subnet to which the interface is attached.

Sap or SDP Id

Displays the SAP or SDP IDs of the service ID.

Oper State

Displays the operational state of the SAP or SDP IDs of the service ID.

Mrtr Port

Specifies if the port is a multicast router port.

Send Queries

Specifies whether the send-queries command is enabled or disabled.

Max Num Groups

Specifies the maximum number of multicast groups that can be joined on this SAP or SDP.

MVR From VPLS

Specifies MVR from VPLS.

Num MVR Groups

Specifies the actual number of multicast groups that can be joined on this SAP or SDP.

MVR From VPLS Cfg Drops

Displays the from VPLS drop count.

MVR To SAP Cfg Drops

Displays the to SAP drop count.

MVR Admin State

Displays the administrative state of MVR.

MVR Policy

The MVR policy name.
mfib
Syntax

mfib [brief] [ip | mac] brief

mfib [group grp-address]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays the multicast FIB on the VPLS service.

Parameters
brief

Keyword to display a brief output.

group grp grp-address

Specifies a specific multicast group address for which to displays the FIB.

Output

The following output is an example of multicast FIB information, and Output fields: service ID MFIB describes the output fields.

Sample output 
*A:SAS# show service id 1 mfib

===============================================================================
Multicast FIB, Service 1
===============================================================================
Group Address         Sap/Sdp Id               Svc Id   Fwd/Blk
-------------------------------------------------------------------------------
239.4.4.4             sap:1/1/1                Local    Fwd
-------------------------------------------------------------------------------
Number of entries: 1
==============================================================================
A:7210-SAS>show>service>id#
Table 30. Output fields: service ID MFIB
Label Description

Group Address

IPv4 multicast group address.

SAP ID

Indicates the SAP or SDP to which the corresponding multicast stream is forwarded or blocked.

Forwarding/Blocking

Indicates whether the corresponding multicast stream is blocked or forwarded.

Number of Entries

Specifies the number of entries in the MFIB.

Forwarded Packets

Indicates the number of multicast packets forwarded for the corresponding source or group.

Forwarded Octets

Indicates the number of octets forwarded for the corresponding source or group.

Svc ID

Indicates the service to which the corresponding multicast stream is forwarded or blocked. Local means that the multicast stream is forwarded or blocked to a SAP or SDP local to the service.
mrouters
Syntax

mrouters [detail]

Context

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays all multicast routers.

Parameters
detail

Keyword to display detailed information.

Output

The following output is an example of multicast router information.

Sample output 
A:7210-SAS>show>service>id>igmp-snooping# mrouters

===============================================================================
IGMP Snooping Multicast Routers for service 1
===============================================================================
MRouter          Sap/Sdp Id             Up Time        Expires   Version
-------------------------------------------------------------------------------
10.1.1.1         1/1/2                  0d 18:31:30    254s      2
-------------------------------------------------------------------------------
Number of mrouters: 1
===============================================================================
A:7210-SAS>show>service>id>igmp-snooping#
mvr
Syntax

mvr

Context

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays Multicast VPLS Registration (MVR) information.

Output

The following output is an example of IGMP snooping MVR information, and Output fields: IGMP-snooping MVR describes the fields.

Sample output 
A:ALA-1>show>service>id>snooping# mvr
===============================================================================
IGMP Snooping Multicast VPLS Registration info for service 10
===============================================================================
IGMP Snooping Admin State : Up                                                 
 
MVR Admin State           : Up                                                 
MVR Policy                : mvr-policy                                         
-------------------------------------------------------------------------------
Local SAPs/SDPs
-------------------------------------------------------------------------------
Svc Id     Sap/Sdp                Oper      From       Num Local
           Id                     State     VPLS       Groups   
-------------------------------------------------------------------------------
100         sap:1/1/10:10         Up       Local      100
100         sap:1/1/10:20         Up       Local      100
-------------------------------------------------------------------------------
MVR SAPs (from-vpls=10)
-------------------------------------------------------------------------------
Svc Id     Sap/Sdp                Oper      From       Num MVR  
           Id                     State     VPLS       Groups   
-------------------------------------------------------------------------------
20         sap:1/1/4:100          Up        10         100      
30         sap:1/1/31:10.10       Up        10         100
=============================================================================== 
A:ALA-1>show>service>id>snooping#
Table 31. Output fields: IGMP-snooping MVR
Label Description

IGMP Snooping Admin State

Displays the IGMP snooping administrative state.

MVR Admin State

Displays the MVR administrative state.

MVR Policy

Displays the MVR policy name.

Svc ID

Displays the service ID.

Sap/SDP

Displays the SAP or SDP ID.

Oper State

Displays the operational state.

From VPLS

Displays the originating VPLS name.

Num Local Groups

Displays the number of local groups.
port-db
Syntax

port-db sap sap-id [detail]

port-db sap sap-id group grp-address

port-db sdp sdp-id:vc-id [detail]

port-db sdp sdp-id:vc-id group grp-address

Context

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information about the IGMP snooping port database for the VPLS service.

Parameters
group grp-ip-address

Displays the IGMP snooping port database for a specific multicast group address.

sap sap-id

Displays the IGMP snooping port database for a specific SAP. See Common CLI command descriptions for command syntax.

sdp sdp-id

Displays only IGMP snooping entries associated with the specified mesh SDP or spoke-SDP. For a spoke-SDP, the VC ID must be specified, for a mesh SDP, the VC ID is optional.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID for which to display information.

Default

For mesh SDPs only, all VC IDs.

Values

1 to 4294967295

Output

The following output is an example of port database information, and Output fields: IGMP snooping port DB describes the output fields.

Sample output 
*A:MTU-T2#  show service id 100 igmp-snooping port-db sap 1/1/2 detail 
===============================================================================
IGMP Snooping SAP 1/1/2 Port-DB for service 100
===============================================================================
-------------------------------------------------------------------------------
IGMP Group 239.7.7.7
-------------------------------------------------------------------------------
Type             : dynamic              
Up Time          : 0d 00:06:17          Expires          : 30s
Compat Mode      : IGMP Version 2       
V1 Host Expires  : 0s                   V2 Host Expires  : 30s
-------------------------------------------------------------------------------
IGMP Group 239.7.7.8
-------------------------------------------------------------------------------
Type             : dynamic              
Up Time          : 0d 00:06:17          Expires          : 30s
Compat Mode      : IGMP Version 2       
V1 Host Expires  : 0s                   V2 Host Expires  : 30s
-------------------------------------------------------------------------------
IGMP Group 239.8.8.8
-------------------------------------------------------------------------------
Type             : static               
Up Time          : 0d 00:04:29          Expires          : never
Compat Mode      : IGMP Version 2       
V1 Host Expires  : 0s                   V2 Host Expires  : 0s
-------------------------------------------------------------------------------
Number of groups: 3
===============================================================================
*A:MTU-7210#
Table 32. Output fields: IGMP snooping port DB
Label Description

Group Address

The IP multicast group address for which this entry contains information.

Mode

Specifies the type of membership reports received on the interface for the group.

In the include mode, reception of packets sent to the specified multicast address is requested only from those IP source addresses listed in the source-list parameter of the IGMP membership report.

In the exclude mode, reception of packets sent to the specific multicast address is requested from all IP source addresses except those listed in the source-list parameter.

Type

Indicates how this group entry was learned.

If this group entry was learned by IGMP, the value is set to dynamic.

For statically configured groups, the value is set to static.

Compatibility mode

Specifies the IGMP mode. This is used in order for routers to be compatible with earlier version routers. IGMPv3 hosts must operate

in Version 1 and Version 2 compatibility modes. IGMPv3 hosts must keep state per local interface based on the compatibility mode of each attached network. A host's compatibility mode is determined from the host compatibility mode variable which can be in one of three states: IGMPv1, IGMPv2 or IGMPv3. This variable is kept per interface and is dependent on the version of general queries heard on that interface as well as the earlier VERSION querier present timers for the interface.

V1 host expires

The time remaining until the local router assumes that there are no longer any IGMPv1 members on the IP subnet attached to this interface. Upon hearing any IGMPv1 membership report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores any IGMPv2 leave messages for this group that it receives on this interface.

V2 host expires

The time remaining until the local router assumes that there are no longer any IGMPv2 members on the IP subnet attached to this interface. Upon hearing any IGMPv2 membership report, this value is reset to the group membership timer. While this time remaining is non-zero, the local router ignores any IGMPv3 leave messages for this group that it receives on this interface.

Up Time

The time after the source group entry was created.

Expires

The amount of time remaining before this entry is aged out.

Forwarding/Blocking

Indicates whether this entry is on the forward list or block list.

Number of groups

Indicates the number of groups configured for this SAP.
proxy-db
Syntax

proxy-db [detail]

proxy-db group grp-address

Context

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information about the IGMP snooping proxy reporting database for the VPLS service.

Parameters
group grp-ip-address

Displays the IGMP snooping proxy reporting database for a specific multicast group address.

Output

The following output is an example of proxy database information, and Output fields: IGMP snooping proxy DB describes the output fields.

Sample output 
*A:MTU-7210#  show service id 100 igmp-snooping proxy-db 
===============================================================================
IGMP Snooping Proxy-reporting DB for service 100
===============================================================================
Group Address    Up Time       
-------------------------------------------------------------------------------
239.7.7.7        0d 00:05:30   
239.7.7.8        0d 00:05:30   
239.8.8.8        0d 00:03:42   
-------------------------------------------------------------------------------
Number of groups: 3
===============================================================================
*A:MTU-7210#


*A:MTU-T2#  show service id 100 igmp-snooping proxy-db detail 
===============================================================================
IGMP Snooping Proxy-reporting DB for service 100
===============================================================================
-------------------------------------------------------------------------------
IGMP Group 239.7.7.7
-------------------------------------------------------------------------------
Up Time : 0d 00:05:43                   
-------------------------------------------------------------------------------
IGMP Group 239.7.7.8
-------------------------------------------------------------------------------
Up Time : 0d 00:05:43                   
-------------------------------------------------------------------------------
IGMP Group 239.8.8.8
-------------------------------------------------------------------------------
Up Time : 0d 00:03:55                   
-------------------------------------------------------------------------------
Number of groups: 3
===============================================================================
*A:MTU-7210#
Table 33. Output fields: IGMP snooping proxy DB
Label Description

Group Address

The IP multicast group address for which this entry contains information.

Mode

Specifies the type of membership reports received on the interface for the group. In the include mode, reception of packets sent to the specified multicast address is requested only from those IP source addresses listed in the source-list parameter of the IGMP membership report.

In the exclude mode, reception of packets sent to the specific multicast address is requested from all IP source addresses except those listed in the source-list parameter.

Up Time

The total operational time in seconds.

Number of groups

Number of IGMP groups.
querier
Syntax

querier

Context

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information about the IGMP snooping queries for the VPLS service.

Output

The following output is an example of IGMP snooping querier information, and Output fields: IGMP snooping querier describes the output fields.

Sample output 
*A:MTU-7210#  show service id 100 igmp-snooping querier 
===============================================================================
IGMP Snooping Querier info for service 100
===============================================================================
Sap Id                  : 1/1/1
IP Address              : 10.10.9.9
Expires                 : 24s
Up Time                 : 0d 00:05:20
Version                 : 2
 
General Query Interval  : 10s
Query Response Interval : 10.0s
Robust Count            : 2
===============================================================================
*A:MTU-7210# 


*A:MTU-T2#  show service id 100 igmp-snooping proxy-db 
===============================================================================
IGMP Snooping Proxy-reporting DB for service 100
===============================================================================
Group Address    Up Time       
-------------------------------------------------------------------------------
239.7.7.7        0d 00:05:30   
239.7.7.8        0d 00:05:30   
239.8.8.8        0d 00:03:42   
-------------------------------------------------------------------------------
Number of groups: 3
===============================================================================
*A:MTU-T2#
Table 34. Output fields: IGMP snooping querier
Label Description

SAP Id

Specifies the SAP ID of the service.

IP address

Specifies the IP address of the querier.

Expires

The time left, in seconds, until the query expires.

Up time

The length of time the query has been enabled.

Version

The configured version of IGMP.

General Query Interval

The frequency at which host-query packets are transmitted.

Query Response Interval

The time to wait to receive a response to the host-query message from the host.

Robust Count

Specifies the value used to calculate several IGMP message intervals.
static
Syntax

static [sap sap-id | sdp sdp-id:vc-id]

Context

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays information about static IGMP snooping source groups for the VPLS service.

Parameters
sap sap-id

Displays static IGMP snooping source groups for a specific SAP. See Common CLI command descriptions for command syntax.

sdp sdp-id

Displays the IGMP snooping source groups for a specific spoke or mesh SDP.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID for which to display information.

Default

For mesh SDPs only, all VC IDs.

Values

1 to 4294967295

Output

The following output is an example of static IGMP snooping information, and Output fields: IGMP snooping static describes the output fields.

Sample output 
*A:MTU-7210#  show service id 100 igmp-snooping static     
 
===============================================================================
IGMP Snooping Static Groups for service 100
===============================================================================
-------------------------------------------------------------------------------
IGMP Snooping Static Groups for SAP 1/1/2
-------------------------------------------------------------------------------
Group           
-------------------------------------------------------------------------------
239.8.8.8       
-------------------------------------------------------------------------------
Static (*,G) entries: 1
===============================================================================
*A:MTU-7210#
Table 35. Output fields: IGMP snooping static
Label Description

Source

Displays the IP source address used in IGMP queries.

Group

Displays the static IGMP snooping source groups for a specified SAP.
statistics
Syntax

statistics [sap sap-id | sdp sdp-id:vc-id]

Context

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays IGMP snooping statistics for the VPLS service.

Parameters
sap sap-id

Displays IGMP snooping statistics for a specific SAP. See Common CLI command descriptions for command syntax.

sdp sdp-id

Displays the IGMP snooping statistics for a specific spoke or mesh SDP.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID for which to display information.

Default

For mesh SDPs only, all VC IDs.

Values

1 to 4294967295

Output

The following output is an example of IGMP snooping statistics, and Output fields: service-ID IGMP statistics describes the output fields.

Sample output 
A:7210-SAS>show>service>id>igmp-snooping# statistics

===============================================================================
IGMP Snooping Statistics for service 1
===============================================================================
Message Type            Received      Transmitted   Forwarded
-------------------------------------------------------------------------------
General Queries         1987001       0             1987001
Group Queries           0             0             0
V1 Reports              0             0             0
V2 Reports              1987002       13200         0
V2 Leaves               0             0             0
Unknown Type            0             N/A           0
-------------------------------------------------------------------------------
Drop Statistics
-------------------------------------------------------------------------------
Bad Length               : 0
Bad IP Checksum          : 0
Bad IGMP Checksum        : 0
Bad Encoding             : 0
No Router Alert          : 0
Zero Source IP           : 0
Wrong Version            : 0
Lcl-Scope Packets        : 0

Send Query Cfg Drops     : 0
Import Policy Drops      : 0
Exceeded Max Num Groups  : 0
MCS Failures             : 0
===============================================================================
A:7210-SAS>show>service>id>igmp-snooping#
Table 36. Output fields: service-ID IGMP statistics
Label Description

Message Type

The column heading for IGMP snooping messages.

General Queries

The number of general query messages received, transmitted, and forwarded.

Group Queries

The number of group query messages received, transmitted, and forwarded.

Group-Source Queries

The number of group-source query messages received, transmitted, and forwarded.

V1 Reports

The number of IGMPv1 report messages received, transmitted, and forwarded.

V2 Reports

The number of IGMPv2 report messages received, transmitted, and forwarded.

V2 Leaves

The number of IGMP leave messages received, transmitted, and forwarded.

Unknown Type

The number of unknown type messages received, transmitted, and forwarded.

Drop Statistics

Bad Length

The number of packets dropped because of bad length.

Bad IP Checksum

The number of packets dropped because of a bad IP checksum.

Bad IGMP Checksum

The number of packets dropped because of a bad IGMP checksum.

Bad Encoding

The number of packets dropped because of bad encoding.

No Router Alert

The number of packets dropped because there was no router alert.

Zero Source IP

The number of packets dropped because of a source IP address of 0.0.0.0 or 00:00:00:00:00:00:00:00.

Send Query Cfg Drops

The number of messages dropped because of send query configuration errors.

Import Policy Drops

The number of messages dropped because of import policy.

Exceeded Max Num Groups

The number of packets dropped because the maximum number of groups has been exceeded.

MVR From VPLS Cfg Drops

The number of packets dropped because of VPLS configuration multicast VPLS registration (MVR).

MVR To SAP Cfg Drops

The number of packets dropped because of SAP configuration.
endpoint
Syntax

endpoint [endpoint-name]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command displays service endpoint information.

Parameters
endpoint-name

Specifies an endpoint name created in the config>service>vpls context.

Output

The following output is an example of endpoint information, and Output fields: service-ID endpoint describes the output fields.

Sample output 
*A:Dut-B# show service id 1 endpoint 
===============================================================================
Service 1 endpoints
===============================================================================
Endpoint name                : mcep-t1                                         
Description                  : (Not Specified)
Revert time                  : 0                                               
Act Hold Delay               : 0                                               
Ignore Standby Signaling     : false                                           
Suppress Standby Signaling   : false                                           
Block On Mesh Fail           : true                                            
Psv Mode Active              : No                                              
Tx Active                    : 231:1                                           
Tx Active Up Time            : 0d 00:06:57                                     
Revert Time Count Down       : N/A                                             
Tx Active Change Count       : 5                                               
Last Tx Active Change        : 02/13/2009 22:08:33                             
-------------------------------------------------------------------------------
Members
-------------------------------------------------------------------------------
Spoke-sdp: 221:1 Prec:1                             Oper Status: Up
Spoke-sdp: 231:1 Prec:2                             Oper Status: Up
===============================================================================
*A:Dut-B#
Table 37. Output fields: service-ID endpoint
Label Description

Endpoint name

The name of the endpoint.

Description

A description of the endpoint.

Revert time

The programmable time delay to switch back to the primary spoke SDP.

Act Hold Delay

Not applicable.

Ignore Standby Signaling

Specifies whether ignore standby signaling is configured.

True — standby signaling is ignored

False — standby signaling is not ignored

Suppress Standby Signaling

Specifies whether suppress standby signaling is configured.

True — standby signaling is suppressed

False — standby signaling is not suppressed

Block On Mesh Fail

Specifies whether to take down the spoke SDP when the mesh SDP is down.

True — the spoke SDP is not taken down

False — the spoke SDP is taken down

Tx Active

The identifier of the active spoke SDP.

Tx Active Up Time

The total amount of time that a spoke SDP remains the active spoke SDP.

Revert Time Count Down

The amount of time remaining before active transmission reverts to the primary spoke SDP.

Tx Active Change Count

The number of times that the active spoke SDP has changed.

Last Tx Active Change

The timestamp of the last active spoke SDP change.

Members

Spoke-sdp

Identifies the spoke SDP.

Prec

Specifies the precedence of this SDP binding when there are multiple SDP bindings attached to one service endpoint.

Oper Status

Indicates the operational status of the endpoint.

Clear commands

id
Syntax

id service-id

Context

clear>service

clear>service>statistics

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears commands for a specific service.

Parameters
service-id

Specifies the ID that uniquely identifies a service.

Values

service-id: 1 to 214748364 svc-name: A string up to 64 characters.

statistics
Syntax

statistics

Context

clear>service>stats

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears session statistics for this service.

fdb
Syntax

fdb {all | mac ieee-address | sap sap-id] | mesh-sdp sdp-id[:vc-id] | spoke-sdp sdp-id:vc-id}

Context

clear>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears FDB entries for the service.

Parameters
all

Clears all FDB entries.

mac ieee-address

Clears only FDB entries in the FDB table with the specified 48-bit MAC address. The MAC address can be expressed in the form aa:bb:cc:dd:ee:ff or aa-bb-cc-dd-ee-ff where aa, bb, cc, dd, ee and ff are hexadecimal numbers.

sap-id

Specifies the physical port identifier portion of the SAP definition. See Common CLI command descriptions for command syntax.

mesh-sdp

Clears only service FDB entries associated with the specified mesh SDP ID. For a mesh SDP, the VC ID is optional.

spoke-sdp

Clears only service FDB entries associated with the specified spoke-SDP ID. For a spoke-SDP, the VC ID must be specified.

sdp-id

Specifies the SDP ID for which to clear associated FDB entries.

vc-id

Specifies the virtual circuit ID on the SDP ID for which to clear associated FDB entries.

Values

sdp-id[:vc-id] sdp-id: 1 to 17407

vc-id: 1 to 4294967295

sdp-id:vc-id sdp-id: 1 to 17407

vc-id: 1 to 4294967295

mesh-sdp
Syntax

mesh-sdp sdp-id[:vc-id] ingress-vc-label

Context

clear>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears and resets the mesh SDP bindings for the service.

Parameters
sdp-id

Specifies the mesh SDP ID to be reset.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID to be reset.

Default

All VC IDs on the SDP ID.

Values

1 to 4294967295

spoke-sdp
Syntax

spoke-sdp sdp-id[:vc-id] {all | counters | stp | l2pt}}

Context

clear>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears and resets the spoke-SDP bindings for the service.

Parameters
sdp-id

Specifies the spoke-SDP ID to be reset.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID to be reset.

Values

1 to 4294967295

all

Clears all queue statistics and STP statistics associated with the SDP.

counters

Clears all queue statistics associated with the SDP.

stp

Clears all STP statistics associated with the SDP.

l2pt

Clears all L2PT statistics associated with the SDP.

sap
Syntax

sap sap-id

Context

clear>service>statistics

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears statistics for the SAP bound to the service.

Parameters
sap-id

Clears statistics for a specified SAP. See Common CLI command descriptions for command syntax.

all

Clears all queue statistics and STP statistics associated with the SAP.

counters

Clears all queue statistics associated with the SAP.

counters
Syntax

counters

Context

clear>service>statistics>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears all traffic queue counters associated with the service ID.

l2pt
Syntax

l2pt

Context

clear>service>statistics>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears the l2pt statistics for this service.

mesh-sdp
Syntax

mesh-sdp sdp-id[:vc-id] {all | counters | stp | mrp}

Context

clear>service>statistics>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears the statistics for a particular mesh SDP bind.

Parameters
sdp-id

Specifies the mesh SDP ID for which to clear statistics.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the mesh SDP ID to be reset.

Values

1 to 4294967295

all

Clears all queue statistics and STP statistics associated with the SDP.

counters

Clears all queue statistics associated with the SDP.

stp

Clears all STP statistics associated with the SDP.

mrp

Clears all MRP statistics associated with the SDP.

spoke-sdp
Syntax

spoke-sdp sdp-id[:vc-id] {all | counters | stp| l2pt}

Context

clear>service>statistics>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears statistics for the spoke-SDP bound to the service.

Parameters
sdp-id

Specifies the spoke-SDP ID for which to clear statistics.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID to be reset.

Values

1 to 4294967295

all

Clears all queue statistics and STP statistics associated with the SDP.

counters

Clears all queue statistics associated with the SDP.

stp

Clears all STP statistics associated with the SDP.

l2pt

Clears all L2PT statistics associated with the SDP.

stp
Syntax

stp

Context

clear>service>statistics>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears all STP statistics for the service ID.

detected-protocols
Syntax

detected-protocols {all | sap sap-id}

Context

clear>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

RSTP automatically falls back to STP mode when it receives an STP BPDU. The clear detected-protocols command forces the system to revert to the default RSTP mode on the SAP.

Parameters
all

Clears all detected protocol statistics.

sap-id

Clears the specified lease state SAP information. See Common CLI command descriptions for command syntax.

igmp-snooping
Syntax

igmp-snooping

Context

clear>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

Commands in this context clear IGMP snooping data.

port-db
Syntax

port-db [sap sap-id] [group grp-address]

port-db sdp sdp-id:vc-id [group grp-address]

Context

clear>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears the information about the IGMP snooping port database for the VPLS service.

Parameters
sap sap-id

Clears IGMP snooping statistics matching the specified SAP ID and optional encapsulation value. See Common CLI command descriptions for command syntax.

sdp-id

Clears only IGMP snooping entries associated with the specified mesh SDP or spoke-SDP. For a spoke-SDP, the VC ID must be specified, for a mesh SDP, the VC ID is optional.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID for which to clear information.

Default

For mesh SDPs only, all VC IDs.

Values

1 to 4294967295

group grp-address

Clears IGMP snooping statistics matching the specified group address.

querier
Syntax

querier

Context

clear>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command clears the information about the IGMP snooping queries for the VPLS service.

Debug commands

id
Syntax

id service-id

Context

debug>service

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command debugs commands for a specific service.

Parameters
service-id

Specifies the ID that uniquely identifies a service.

Values

service-id: 1 to 214748364 svc-name: A string up to 64 characters.

event-type
Syntax

[no] event-type {config-change | svc-oper-status-change | sap-oper-status-change | sdpbind-oper-status-change}

Context

debug>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables a particular debugging event type. The no form of this command disables the event type debugging.

Parameters
config-change

Debugs configuration change events.

svc-oper-status-change

Debugs service operational status changes.

sap-oper-status-change

Debugs SAP operational status changes.

sdpbind-oper-status-change

Debugs SDP operational status changes.

sap
Syntax

[no] sap sap-id

Context

debug>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables debugging for a particular SAP.

Parameters
sap-id

Specifies the SAP ID.

stp
Syntax

stp

Context

debug>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables the context for debugging STP.

all-events
Syntax

all-events

Context

debug>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for all events.

bpdu
Syntax

[no] bpdu

Context

debug>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for received and transmitted BPDUs.

core-connectivity
Syntax

[no] core-connectivity

Context

debug>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for core connectivity.

exception
Syntax

[no] exception

Context

debug>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for exceptions.

fsm-state-changes
Syntax

[no] fsm-state-changes

Context

debug>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for FSM state changes.

fsm-timers
Syntax

[no] fsm-timers

Context

debug>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for FSM timer changes.

port-role
Syntax

[no] port-role

Context

debug>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for changes in port roles.

port-state
Syntax

[no] port-state

Context

debug>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for port states.

sap
Syntax

[no] sap sap-id

Context

debug>service>id>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for a specific SAP.

Parameters
sap-id

Specifies the physical port identifier portion of the SAP definition. See Common CLI command descriptions for command syntax.

sdp
Syntax

[no] sdp sdp-id:vc-id

Context

debug>service>stp

Platforms

Supported on all 7210 SAS platforms as described in this document

Description

This command enables STP debugging for a specific SDP.

1 DHCP relay can be configured for the IES interface associated with the Routed VPLS service. DHCP snooping cannot be configured on the VPLS SAPs in the routed VPLS Service.
2 This row is not recommended for use. For more information, see the Note in the command description.