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 that 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 (PE) IP/MPLS routers.

VPLS provides a balance between point-to-point Frame Relay service and outsourced routed services (VPRN). VPLS enables customers 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. 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 the following:

  • 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, which eliminates the need to train personnel on WAN technologies, such as Frame Relay.

VPLS packet walk-through in network mode

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 7210-A 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 (shown in the following figure):

    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 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 (shown in the following figure):

    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
  2. Core Router Switching

    1. The PE router encapsulates this packet in an MPLS header and transports it across the core network to the remote 7210-C.

  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 7210-C, an existing entry in the FIB table identifies the local access port and the IEEE 802.1Q tag (if any) 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 packet walk-through in access-uplink mode

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 (VPLS service architecture) in an H-VPLS configuration. This section does not describe the processing on the PE routers but only on 7210 SAS routers:

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

    1. Service packets arriving at 7210-A 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 4. 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 ):

    4. If the destination MAC address has already been learned by 7210, an existing entry in the FIB table identifies destination uplink QinQ SAP to be used for sending the packet toward the PE-Router-A.

    5. The customer packet is sent on this uplink SAP when the IEEE 802.1Q tag is stripped and the uplink SAP tag is added to the packet.

      For an Unknown MAC Address (shown in the following figure):

    6. If the destination MAC address has not been learned, 7210 will flood the packet to all the uplink SAP spoke-SDPs that are participating in the service.

      Figure 5. Network port egress packet format and flooding
  2. Core Router Switching

    1. The PE router will encapsulate this packet in the appropriate MPLS header and transport it across the core network to the remote 7210-C.

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

    1. 7210-C associates the packet with the VPLS instance based on the VLAN tags in the received packet.

    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 access-uplink port 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 7210-C, an existing entry in the FIB table identifies the local access port and the IEEE 802.1Q tag (if any) 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

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 in network operating mode

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.

VPLS/H-VPLS is provided over MPLS by:

  • connecting 7210 SAS to bridging-capable PE routers through a mesh/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 FIB per VPLS service

VPLS over QinQ spokes for 7210 SAS devices configured in access-uplink operating mode

7210 SAS devices configured in access-uplink operating mode support QinQ spokes or dot1q spokes, which allows them to connect to upstream PE nodes which provides IP/MPLS transport.

VPLS is provided over QinQ/Dot1q spokes by:

  • connecting bridging-capable 7210 SAS devices

  • replicating unknown and broadcast traffic in a service domain

  • enabling MAC learning over QinQ/Dot1q spokes and access ports (see VPLS MAC learning and packet forwarding)

  • using a separate 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.

IGMP snooping in a VPLS service

Note:

  • IGMP snooping is supported on all 7210 SAS platforms as described in this document, including those configured in the access-uplink operating mode.

  • This section provides information about IGMP snooping support in a VPLS service. It does not apply to R-VPLS services. IGMP snooping can also be enabled for R-VPLS services. See R-VPLS and IGMPv3 snooping for more information.

In Layer 2 switches, multicast traffic is treated as 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 unknown and broadcast frames, this flooded multicast traffic may result in wasted bandwidth on network segments and end stations because IP multicast hosts can join and be interested in only specific multicast groups.

IGMP snooping uses 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.

Note:

References to SDP in the following section about IGMP snooping are applicable only to 7210 SAS platforms operating in network mode.

IGMP snooping can be enabled in the context of VPLS services. The IGMP snooping optimizes the multicast data flow to only those SAPs or SDPs that are members of the group. The system builds a database of group members for each 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 the switch 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 is a list of supported IGMP snooping features:

  • IGMPv1, IGMPv2, and IGMPv3 are supported in accordance with RFC 1112, Host Extensions for IP Multicasting, and RFC 2236, Internet Group Management Protocol, Version 2:

    • The 7210 SAS-T configured in the access-uplink operating mode supports IGMPv1, IGMPv2, and IGMPv3 snooping in a VPLS service.

    • All 7210 SAS platforms as described in this document, except those configured in the access-uplink operating mode, support only IGMPv1 and IGMPv2 snooping in a VPLS service.

  • 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 a 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 reports from a particular host or range of hosts. This filtering is performed by importing a 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 (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 for which VCs 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 for which VCs are configured to use vc-type ether and do not have control-word enabled.

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

  • SDPs that are configured to use VCs of type vc-vlan that need to be mrouter 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 SDP.

  • All 7210 SAS platforms as described in this document, except those configured in the access-uplink operating mode, support only IGMPv1 and IGMPv2 snooping in a VPLS service. These platforms do not support IGMPv3 snooping in a VPLS service.

  • All 7210 SAS platforms as described in this document, except those configured in the access-uplink operating mode, support IGMPv3 in an R-VPLS service only. See R-VPLS and IGMPv3 snooping for more information.

DHCPv4 snooping

To support a DHCP-based address assignment in a Layer 2 aggregation network, the 7210 SAS supports DHCPv4 snooping. The 7210 SAS can copy packets designated to the standard UDP port for DHCP (port 67) to its control plane for inspection, this process is called DHCPv4 snooping.

DHCPv4 snooping can be performed in two directions:

  • From the client to the DHCP server (Discover or Request messages) to insert Option 82 information. For these applications, DHCPv4 snooping must be enabled on the SAP toward the subscriber.

  • From the DHCP server (ACK messages), to remove the Option 82 field toward the client. For these applications, DHCPv4 snooping must be enabled on both the SAP toward the network and the SAP toward the subscriber.

DHCPv6 snooping

The 7210 SAS supports DHCPv6 snooping, as described in RFC 6221, Lightweight DHCPv6 Relay Agent. DHCPv6 snooping allows the user to enable the Lightweight DHCPv6 Relay Agent (LDRA) in a VPLS service.

An LDRA allows relay agent information to be inserted by an 7210 SAS access node that performs a link-layer bridging function. An LDRA resides on the same IPv6 link as the client and a DHCPv6 relay agent or DHCPv6 server, and is similar in function to the DHCPv4 snooping function. DHCPv6 snooping allows relay agent information, including the interface ID option, to be inserted by the access node so that it can be used by the DHCPv6 server for client identification. It also allows for insertion of the remote ID option, allowing the DHCPv6 server to know where the client is attached to the network and if the location is trusted.

DHCPv6 snooping can be performed in two directions:
  • From the client to the DHCPv6 server/relay (for example, Discover or Request messages) to insert relay agent information. For these applications, DHCP snooping must be enabled on the SAP (using the config>service>vpls>sap>dhcp6>snoop command) toward the subscriber.

  • From the DHCPv6 server or relay (for example, ACK messages) to remove the relay agent information toward the client. For these applications, DHCPv6 snooping must be enabled on both the SAP toward the network (using the config>service>vpls>sap>dhcp6>snoop command), the SDP binding toward the network (using the config>service>vpls>spoke-sdp>snoop or config>service>vpls>mesh-sdp>snoop command), and the SAP toward the subscriber (using the config>service>vpls>sap>dhcp6>snoop command).

    Note: On the 7210 SAS, DHCPv6 snooping on SDP bindings is only supported for spoke SDPs and mesh SDPs in TLDP VPLS services.

In the following figure, the 7210 SAS is used as an access aggregation device to aggregate business CPE for enterprise services, Digital Subscriber Line Access Multiplexers (DSLAMs), and Optical Line Terminations (OLTs) for residential broadband services that use Layer 2 VPLS services.

Figure 6. DHCPv6 snooping for Layer 2 services


Operators need a mechanism to identify the DHCPv6 messages received on their customer-facing ports so that the appropriate IPv6 address and parameters can be provided by the DHCPv6 server. In a Layer 2 network, this is achieved by using DHCPv6 snooping to insert option-18 and option-37 (relay agent information options) in the DHCPv6 messages received from customer-facing ports before being forwarded toward the DHCPv6 server or relay.

Client and network-facing service objects

DHCPv6 snooping enables users to identify client and network-facing service objects, in accordance with RFC 6221. Use the following commands to specify if the service object is client-facing, network-facing, or both:

  • config>service>vpls>sap>dhcp6>snoop [client-facing | network-facing | both]
  • config>service>vpls>mesh-sdp>dhcp6>snoop [network-facing]
  • config>service>vpls>spoke-sdp>dhcp6>snoop [network-facing]

To support ring deployments, which employs a ring protection mechanism and the forwarding state of the ring port can change dynamically, a configured service object (for example, a SAP or SDP binding) on a ring port can be client-facing or network-facing depending on the forwarding state of the ring port. To support this scenario, the both option is provided. When the both option is configured, the processing rules that apply to both client-facing and network-facing service objects are applied.

On the 7210 SAS, SAPs in a VPLS service are configured as client-facing (customer-facing ports) by default. In other words, all SAPs with DHCPv6 snooping enabled are client facing. The option to configure the SAP as network-facing or both is supported; for example, access ports facing the core as a Layer 2 switch with a high SAP scale mode may need to be configured as network-facing or both.

SDP bindings that are explicitly configured for DHCPv6 snooping are network-facing ports by default.

In accordance with RFC 6221, the 7210 SAS does not forward a DHCPv6 relay-forward message out of client-facing service objects. The message is only forwarded out of network-facing service objects or objects configured as both.

DHCP relay-reply messages are only processed when received on a network-facing service object. DHCPv6 snooping intercepts and processes all IP traffic received on the network-facing service object that matches:
  • a link-local scoped source address
  • a link-local scoped destination address
  • protocol type UDP
  • destination port 547

DHCPv6 snooping inspects the DHCP message type and only forwards the relay-reply message. The other DHCP message types are silently discarded.

The 7210 SAS processes the DHCPv6 client messages received on client-facing interfaces when DHCPv6 snooping is enabled on the SAP or SDP binding and the client-facing option is configured.

All IP traffic received on the client-facing service object (for example, a SAP or SDP binding) that meets the following conditions is intercepted and processed:
  • destination IP address is set to "All_DHCP_Relay_Agents_and_Servers (ff02::1:2)"
  • protocol type UDP
  • destination port 547

When snooping is enabled, all DHCPv6 messages that match the preceding criteria are trapped to the CPU. Only the DHCPv6 client messages are processed further; other messages are silently dropped.

Trusted and untrusted service objects

The 7210 SAS provides the option to configure a service object, which is configured as client-facing or both, as trusted or untrusted with the config>service>vpls>sap>dhcp6> [no] trusted command.

Use the trusted command to process and forward a relay-forward message received on a client-facing service object (when DHCPv6 snooping is enabled).

Use the no trusted command to disable processing and forwarding of relay-forward message received on a client-facing service object (when DHCPv6 snooping is enabled).

DHCPv6 relay agent options

The 7210 SAS provides an option to add option-18 (interface ID option) and option-37 (relay agent remote ID option).

To configure option-18, use the config>service>vpls>sap>dhcp6>option> [no] interface-id command . To configure option-37, use the config>service>vpls>sap>dhcp6>option> [no] remote-id command.

The interface-id option is added to relay-forward messages when DHCPv6 snooping is enabled on client-facing service objects.

The remote-id command is optional and only added to relay-forward messages if configured by the user. Configure the no remote-id option to disable the addition of this option. IANA Enterprise-numbers.txt specifies the Nokia Enterprise ID value to use with the DHCPv6 remote-id option.

DHCPv6 snooping QoS considerations

DHCPv6 messages processed by the node are rate-controlled toward the CPU. A Self-Generated Traffic (SGT) QoS configuration is not supported for DHCPv6 messages. However, in most scenarios the incoming packet markings is used to determine the ingress FC and color (if applicable) and the FC is used for forwarding it out of the appropriate queue on the egress with the appropriate packet header markings (depending on the egress object that packet is forwarded out of - dot1p, IP DSCP, and MPLS EXP field in the packet is updated).

Note:

On the 7210 SAS-Mxp, when SAP egress queues are enabled, CPU-generated and forwarded packets are sent out using default port queues.

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 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, shown in the following figure.

Figure 7. MVR and MVR by proxy

Configuration guidelines for MVR in VPLS services

In an 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 FIB.

FIB size

The following MAC table management features are required for each instance of a SAP or spoke-SDP within a particular VPLS service instance:

  • MAC FIB size limits

    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, no new addresses will be 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 or spoke-SDP, 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 will be 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 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 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 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 that 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 will experience a high relearn rate for the MAC. When MAC move is enabled, the 7210 SAS will shut down the SAP or spoke-SDP and create 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
Note:

Per-service split horizon groups are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

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 and 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 will not be forwarded to other SAPs and spoke-SDPs configured in the same split horizon group, but will be 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

The following configuration guidelines for the use of split horizon group in a VPLS service apply:

  • On 7210 SAS-T, and 7210 SAS-Sx/S 1/10GE operating in network mode, mesh SDPs cannot be configured in a service which uses split horizon group (SHG). Conversely, if a service has a mesh SDP configured, split horizon group cannot be used in the same service.

  • On 7210 SAS-Mxp, service based SHG can be configured along with mesh SDPs and spoke-SDPs.

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 7210 SAS 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, refer to Configuring a VPLS service with CLI.

Spanning tree operating modes

For each 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 will dynamically fall 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 as follows:

  • The RSTP mode implements the improved convergence over shared media feature, for example, RSTP will transition 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 two 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

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

Redundancy access to VPLS

The GigE MAN portion of the network is implemented with traditional switches. Using MSTP running on individual switches facilitates redundancy in this part of the network. To provide dual homing of all VPLS services accessing from this part of the network, the VPLS PEs must participate in MSTP.

This can be achieved by the following:

  • configuring mVPLS on VPLS-PEs (only PEs directly connected to GigE MAN network)

  • assign different managed-vlan ranges to different MSTP instances

Typically, the mVPLS would have SAPs with null encapsulations (to receive, send, and transmit MSTP BPDUs) and a mesh SDP to interconnect a pair of VPLS PEs.

Different access scenarios are displayed in the following figure as example network diagrams dually connected to the PBB PEs:

  • Access type A - source devices connected by null or Dot1q SAPs

  • Access type B - one QinQ switch connected by QinQ/801ad SAPs

  • Access type C - two or more ES devices connected by QinQ/802.1ad SAPs

    Figure 8. Access resiliency

The following mechanisms are supported for the I-VPLS:

  • STP/RSTP - can be used for all access types

  • M-VPLS with MSTP - can be used as is just for access Type A

    MSTP is required for access type B and C.

  • LAG and MC-LAG - can be used for access Type A and B

  • Split-horizon-group - does not require residential

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.

Provider MSTP

Note:

Provider MSTP is only supported on platforms that support PBB, and therefore is supported only on 7210 SAS-T operating in the network mode.

Provider MSTP is specified in (IEEE-802.1ad-2005). It uses a provider bridge group address instead of a regular bridge group address used by STP, RSTP, MSTP BPDUs. This allows for implicit separation of source and provider control planes.

The 802.1ad access network sends PBB PE P-MSTP BPDUs using the specified MAC address and also works over QinQ interfaces. P-MSTP mode is used in PBBN for core resiliency and loop avoidance.

Similar to regular MSTP, the STP mode (for example, PMSTP) is only supported in VPLS services where the m-VPLS flag is configured.

MSTP general principles

MSTP represents modification of RSTP which allows the grouping of different VLANs into multiple MSTIs. To enable different devices to participate in MSTIs, they must be consistently configured. A collection of interconnected devices that have the same MST configuration (region-name, revision and VLAN-to-instance assignment) comprises an MST region.

There is no limit to the number of regions in the network, but every region can support a maximum of 16 MSTIs. Instance 0 is a special instance for a region, known as the Internal Spanning Tree (IST) instance. All other instances are numbered from 1 to 4094. IST is the only spanning-tree instance that sends and receives BPDUs (typically BPDUs are untagged). All other spanning-tree instance information is included in MSTP records (M-records), which are encapsulated within MSTP BPDUs. This means that single BPDU carries information for multiple MSTI which reduces overhead of the protocol.

Any specific MSTI is local to an MSTP region and completely independent from an MSTI in other MST regions. Two redundantly connected MST regions will use only a single path for all traffic flows (no load balancing between MST regions or between MST and SST region).

Traditional Layer 2 switches running MSTP protocol assign all VLANs to the IST instance per default. The operator may then ‟re-assign” individual VLANs to a specific MSTI by configuring per VLAN assignment. This means that an SR-series PE can be considered as the part of the same MST region only if the VLAN assignment to IST and MSTIs is identical to the one of Layer 2 switches in access network.

MSTP in the 7210 SAS platform

The 7210 SAS platform uses a concept of mVPLS to group different SAPs under a single STP instance. The VLAN range covering SAPs to be managed by a specific mVPLS is declared under a specific mVPLS SAP definition. MSTP mode-of-operation is only supported in an mVPLS.

When running MSTP, by default, all VLANs are mapped to the CIST. On the VPLS level VLANs can be assigned to specific MSTIs. When running RSTP, the operator must explicitly indicate, per SAP, which VLANs are managed by that SAP.

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 will not be blocked in any circumstance without imposing artificial restrictions on the placement of the root bridge within the network. The modifications 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 will be 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 will designate the network port as the root port. This ensures that network ports always remain in forwarding state.

A combination of the previously mentioned 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 Cisco Discovery Protocol (CDP), Dynamic Trunking Protocol (DTP), Port Aggregation Protocol (PAGP), Spanning Tree Protocol (STP), Unidirectional Link Detection (UDLD), VLAN trunking protocol (VTP), and Link Layer Discovery Protocol (LLDP). This allows users to run these protocols between customer CPEs without involving backbone infrastructure.

The 7210 SAS routers support the 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 via direct connections. In this type of environment, the termination of tunnels through the infrastructure is required.

L2PT tunnels transport 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. On egress of the tunnel, the MAC address is overwritten back to the MAC address of the respective Layer 2 protocol.

The 7210 SAS nodes support L2PT termination for STP BPDUs as follows:

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

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

L2PT termination can be enabled only if STP is disabled in the 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 inter-operable e2e solution.

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

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 will be 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 the SDP encapsulation type) and adding or removing all the required VLAN information in a BPDU payload.

This feature can be enabled on a SAP/spoke 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), Unidirectional 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 are mutually exclusive with running STP on the same VPLS as soon as one SAP/spoke 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 Signalling) 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.

The 7210 SAS 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 will change the link states from disabled to active. The standby node will then broadcast 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 9. 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 displayed 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 will 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 platforms can be used as MTU devices in an MC-EP solution. In this solution, 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 depicted by the following figure, 7210 SAS devices are used as MTUs.

Figure 10. 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 MTUs 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 network where 7210 SAS devices are used:

  • STP-based access, with or without mVPLS

  • Ethernet APS using G.8032

STP-based redundant access to VPLS

Figure 11. Dual-homed MTUs in two-tier hierarchy H-VPLS

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

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 will change the link states from disabled to active. The standby node will then broadcast 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 provides alternative methods for providing 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 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 Layer 2-B). Upon detection of a link failure PE-C will send MAC-Address-Withdraw messages, which will indicate to all LDP peers that they should flush all MAC addresses learned from PE-C. This will lead that 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 will open alternative link (Layer 2-B switch in Figure 57) as well as on the speed PE routers will 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 will take 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 on a SAP or SDP transition 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. When enabling ‟send-flush-on-failure” the flag is blocked in VPLS service managed by mVPLS. This is to prevent both messages being sent at the same time.

  • The flush-mine message is generated on an MC-LAG SAP transition 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 the following figure). 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 previous scenario, STP only needs to run in a single VPLS instance, and the results of the STP calculations are applied to all VPLSes on the link. Equally, the standby node will broadcast MAC flush LDP messages in the protected VPLS instances when it detects that the active node has failed.

Figure 12. 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 will send out a flush-all-from-ME LDP message to all PEs in the VPLS. The PEs receiving this LDP message will remove all MAC entries originated by the sender from the indicated VPLS.

A drawback of this approach is that the 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 previously described where possible.

Dual homing to a VPLS service

Figure 13. Dual homed CE connection to VPLS

The preceding 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 Layer 2-B). Upon detection of a link failure PE-C will send MAC-Address-Withdraw messages, which will indicate to all LDP peers that they should flush all MAC addresses learned from PE-C. This will lead that 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 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 will open alternative link (Layer 2-B switch in the preceding figure) as well as on the speed PE routers will 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 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

    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

    Accepted tagged packets not matching any of the configured VLAN encapsulations. This is like a default SAP for tagged packets.

  4. dot1q Explicit Null encapsulation defined on ingress

    Any untagged or priority-tagged packets will be 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 will take 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 14. 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 15. 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 bytes value destined to carry the local VSI-id (outgoing NLRI minus the RD).

  • Target AII (type 1) is a 4 bytes value destined to carry 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 16. 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 will automatically be constructed. New services added between two endpoints that already have an automatically created SDP will be immediately used. No new SDP will be 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 will remain up as long as at least one service is connected between those endpoints. An automatically created SDP will be 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 once.

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.

PERs-4# 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 in the following ways:

  1. Adding or removing a split-horizon-group will cause 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 re-signal 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 might adversely impact the correct functioning of the service. It is recommended that 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

Note:

R-VPLS with IPv6 interfaces is supported only on 7210 SAS-Mxp operating in the network mode.

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

Note:

  • R-VPLS is supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode.

  • For 7210 SAS platforms operating in network mode, R-VPLS can provide both customer service and in-band management of the node.

  • For 7210 SAS platforms operating in access-uplink mode, R-VPLS can only provide in-band management of the node.

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 access-uplink mode, an R-VPLS service can be associated with an IPv4 interface and supports only static routing. It is primarily designed for use of in-band management of the node. It allows for in-band management of the 7210 SAS nodes in a ring deployment using a single IPv4 subnet, reducing the number of IP subnets needed.

In network mode, an R-VPLS service can be associated with an IPv4 or IPv6 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 and 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 given to 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 allow-ip-int-binding flag is set, the system scans the existing IES and VPRN 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 service with 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 bound and becomes operational up. There is no need to toggle the shutdown or no shutdown command.

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

Service binding requirements

If a 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

If a bound service name is assigned to a service within the system, the system first checks to ensure that 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-int-binding 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.

IP interface attached VPLS service constraints

When a VPLS service has been bound to an IP interface through its service name, the service name assigned to the service cannot be removed or changed unless the IP interface is first unbound from the VPLS service name.

A VPLS service that is currently attached to an IP interface cannot be deleted from the system unless the IP interface is unbound from the VPLS service name.

The allow-ip-int-binding flag within an IP interface attached VPLS service cannot be reset. The IP interface must first be unbound from the VPLS service name to reset the flag.

IP interface and VPLS operational state coordination

When the IP interface is successfully attached to a VPLS service, the operational state of the IP interface is dependent upon the operational state of the VPLS service.

The VPLS service remains down until at least one virtual port (SAP, spoke-SDP, or mesh SDP) is operational.

IP interface MTU and fragmentation

Note:

VPLS service MTU is supported on all 7210 SAS platforms as described in this document, except the 7210 SAS-T operating in access-uplink mode.

The user must ensure that the port MTU is configured appropriately so that the largest packet traversing through any of the SAPs (virtual ports) of the VPLS service can be forwarded out of any of the SAPs. VPLS services do not support fragmentation and can discard packets larger than the configured port MTU.

When an IP interface is associated with a VPLS service, the IP-MTU is based on either the administrative value configured for the IP interface or an operational value derived from port MTU of all the SAPs configured in the service. The port MTU excluding the Layer 2 Header and tags for all the ports which have SAPs configured in this VPLS service are considered and the minimum value among those are computed (which is called computed MTU). The operational value of the IP interface is set as follows:

  • If the configured (administrative) value of IP MTU is greater than the computed MTU, then the operational IP MTU is set to the computed MTU.

  • If the configured (administrative) value of IP MTU is lesser than or equal to the computed MTU, then operational IP MTU is set to the configured (administrative) value of IP MTU.

ARP and VPLS FIB interactions

Two address-oriented table entries are used when routing into a VPLS service. On the routing side, an ARP entry is used to determine the destination MAC address used by an IP next-hop. In the case where the destination IP address in the routed packet is a host on the local subnet represented by the VPLS instance, the destination IP address is used as the next-hop IP address in the ARP cache lookup. If the destination IP address is in a remote subnet that is reached by another router attached to the VPLS service, the routing lookup returns the local IP address on the VPLS service of the remote router is returned. If the next-hop is not currently in the ARP cache, the system generates an ARP request to determine the destination MAC address associated with the next-hop IP address. IP routing to all destination hosts associated with the next-hop IP address stops until the ARP cache is populated with an entry for the next-hop. The dynamically populated ARP entries age out according to the ARP aging timer.

The second address table entry that affects VPLS routed packets is the MAC destination lookup in the VPLS service context. The MAC associated with the ARP table entry for the IP next-hop may or may not currently be populated in the VPLS Layer 2 FIB table. While the destination MAC is unknown (not populated in the VPLS FIB), the system is flooded with all packets destined for that MAC (routed or bridged) to all SAPs within the VPLS service context. When the MAC is known (populated in the VPLS FIB), all packets destined to the MAC (routed or bridged) is targeted to the specific SAP where the MAC has been learned. As with ARP entries, static MAC entries may be created in the VPLS FIB. Dynamically learned MAC addresses are allowed to age out or be flushed from the VPLS FIB while static MAC entries always remain associated with a specific virtual port. Dynamic MACs may also be relearned on another VPLS SAP than the current SAP in the FIB. In this case, the system automatically moves the MAC FIB entry to the new VPLS SAP.

Note:

  • In 7210 SAS, whenever a MAC entry is removed from the VPLS FIB (either explicitly by the user or because of MAC aging or mac-move), ARP entries which match this MAC address is removed from the ARP cache. Though the VPLS FIB entries are not removed; an ARP entry ages out and is removed from the ARP cache.

  • If the VPLS FIB limit is reached and the node is no longer able to learn new MAC address, ARP will also not be learned.

R-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 R-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 on 7210 SAS-D, as and when an Layer 2 entry is removed from the FDB, the matching MAC address is also removed from the ARP cache. On 7210 SAS-K, the packet is sent out of all the SAPs of the VPLS instance.

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.

R-VPLS SAP support 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 unsupported 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 unsupported 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. Additionally, the flag cannot be enabled while any of these features are applied to the VPLS service. The following restrictions apply to both network mode and access-uplink mode, unless otherwise noted:

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

  • In access-uplink mode, the VPLS service type cannot be MVPLS.

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

  • In access-uplink mode, MVR from an R-VPLS SAP to another SAP is not supported.

  • In access-uplink mode, default QinQ SAPs are not supported in an R-VPLS service.

  • In network mode, MVR from an R-VPLS SAP to another R-VPLS SAP is supported. See R-VPLS and IGMPv3 snooping for more information.

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

  • IP (IPv4 and IPv6) 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 supported with R-VPLS SAPs only on the 7210 SAS-Mxp.

  • In access-uplink mode, 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 access-uplink mode, the VPLS service can be configured with either access SAPs or access-uplink SAPs. In network mode, the VPLS service can be configured only with access SAPs or with SAPs on hybrid ports.

  • In access-uplink mode, the VPLS service can use the following svc-sap-type values: any, dot1q-preserve, and null-star. Only specific SAP combinations are allowed for a specific svc-sap-type. Allowed SAP combinations are similar to those for plain VPLS service, except that default QinQ SAPs are not supported.

  • 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-T (network mode), 7210 SAS-Mxp, 7210 SAS-S, and 7210 SAS-Sx.

  • In access-uplink mode, 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, only on 7210 SAS-Mxp, DHCP IPv6 relay can be enabled on the IES service and VPRN service associated with the R-VPLS service. DHCPv6 snooping is not supported.

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

  • In network mode, R-VPLS SAPs are allowed on access ports and hybrid ports.

  • In network mode, an R-VPLS SAP drops packets received with extra tags. That is, if a packet is received on an R-VPLS SAP, with the 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 an R-VPLS service is dropped on ingress.

  • In the saved configuration file, for the R-VPLS service, the R-VPLS service instance appears twice, once for service creation and once 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.

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 (IP) 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 an 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 R-VPLS service

The follows information describes QoS support for VPLS SAPs and IP interface in an R-VPLS service:

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

  • On 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE, egress port-based queuing and shaping are available. It is shared among all the SAPs on the port.

  • On 7210 SAS-Mxp, 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 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, see 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.

  • In access-uplink mode, IES IP interface bound to R-VPLS services, IES IP interface on access SAPs, and IES IP interface on access-uplink SAPs are designed for use with inband management of the node. Consequently, they share a common set of queues for CPU-bound management traffic. All CPU bound traffic is policed to predefined rates before being queued into CPU queues for application processing. The system uses meters per application or a set of applications. It does not allocate meters per IP interface. The possibility of CPU overloading has been reduced by use of these mechanisms. Users must use appropriate security policies either on the node or in the network to ensure that this does not happen.

R-VPLS and routing protocols support

In access-uplink mode, R-VPLS is supported only in the base routing instance. Only IPv4 addressing support is available for IES interfaces associated with a R-VPLS service.

In network mode, R-VPLS is supported in both base routing instances (IES) and VPRN services. IPv4 and IPv6 addressing support is available for IES and VPRN IP interfaces associated with a R-VPLS service.

The following table lists the support available for routing protocols on IP interfaces bound to a VPLS service in access-uplink mode and network mode.

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

Services

Access-uplink

Network

Static-routing

Supported

Supported

BGP

Not Supported

Supported

OSPF

Not Supported

Supported

ISIS

Not Supported

Supported

BFD

Not Supported

Supported

VRRP

Not Supported

Supported

ARP and Proxy-Arp

ARP is supported

Both are supported

DHCP Relay1

Supported

Supported

DHCPv6 Relay

Not Supported

Supported only on the 7210 SAS-Mxp operating in network mode

Spanning tree and split horizon

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

R-VPLS MAC ACLs

Note:

This feature is supported only on the 7210 SAS-Mxp.

Operators deploy R-VPLS in enterprise networks on 7210 SAS nodes to provide Layer 2 and Layer 3 connectivity to end devices. To restrict access to the network, operators can use MAC ACLs to selectively allow traffic for specific MAC addresses and drop all other traffic, or the other way around.

Configure filter mac mac-filter-id in the config>service>vpls>sap>egress and config>service>vpls>sap>ingress contexts to associate an existing MAC filter policy with an R-VPLS service.

The following figure shows an example of an R-VPLS service that provides routed and bridging services to end devices connected to the enterprise LAN and that uses MAC ACLs to restrict traffic.

Figure 17. Secure access to network using MAC filter

R-VPLS features supported with MAC ACLs

This following information describes R-VPLS feature support in conjunction with MAC ACLs:

  • MAC criteria are supported with the following features in an R-VPLS service:

    • SAP ingress and egress for both bridged and routed packets with drop and forward action

    • matching for source MAC addresses, destination MAC addresses, Ethertype, and dot1p

    • filter entry counters and mirroring (ingress filters only)

    • either MAC or IP filters can be associated with SAP ingress or SAP egress; that is, they are mutually exclusive

  • MAC filter policies are supported in R-VPLS services associated with either an IES or VPRN service.

  • MAC filter policies are supported in sap-scale-mode high and low.

  • MAC criteria filter policies associated with R-VPLS SAP ingress and SAP egress use the resources for the ingress ACL and egress ACL resource pools configured using the system resource profile. If there are no resources allocated for MAC criteria, the association of the MAC criteria filter policy fails. That is, the user must first allocate the required resources for MAC criteria using the system resource profile before associating a MAC criteria policy with SAPs.

  • For routed packets, when the SAP ingress MAC filters and IP override ingress filters are configured, if the entries are matched in both filters and the drop action is configured, the drop action in either the MAC filter policy or IP override filter policy takes precedence. That is, if both the MAC filter policy and IP filter (IP override) policy match a routed packet, the packet is forwarded only if the action configured for all matched entries in both the MAC filter policy and IP filter policy is forward. Otherwise, the packet is dropped if there is a matched entry in either the MAC filter policy of IP filter policy with a drop action.If a counter is associated with both the MAC filter and IP override filter, the counter is incremented for matched entries in both the MAC filter and IP override filter. See VPLS SAP ingress IP filter override for more information about ACL behavior for IP override filters.

  • When an IP filter is associated with an R-VPLS SAP on ingress and an IP override filter is associated with the R-VPLS IP interface, and the R-VPLS SAP and IP interface belong to the same R-VPLS service, routed traffic is matched only with IP override filter entries. It is not matched with R-VPLS SAP ingress filter entries. See VPLS SAP ingress IP filter override for more information about ACL behavior for IP override filters.

R-VPLS and IGMPv3 snooping

Note:

This feature is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

This feature (IGMPv3 snooping in R-VPLS) extends IGMP snooping to an R-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 R-VPLS service. The IGMPv3 snooping in R-VPLS feature gives customers an option to use an R-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 a 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 R-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 and when using MVR capability, 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 will support Layer 2 forwarding of both unicast and multicast traffic (that is, no IP forwarding).

  • A user RPVLS can be configured with an IP interface and will support Layer 2 forwarding of both unicast and multicast (with (S,G) IP multicast replications) and support Layer 3 forwarding of unicast traffic.

  • On 7210 SAS-Mxp and 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-Mxp and 7210 SAS-T, 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.

R-VPLS supported functionality and restrictions

R-VPLS supported functionality and restrictions for both access-uplink and network modes are listed as follows. The following items are applicable to both the modes, unless specified explicitly:

  • 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 access-uplink mode, only static routes are supported. No dynamic routing protocols are supported.

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

  • Whenever a VPLS FIB entry is removed either 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 access-uplink mode, R-VPLS is supported only in the base routing instance. Only IPv4 addressing support is available for IES interfaces associated with an R-VPLS service.

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

  • In access-uplink mode, IPv6 addressing support is not available for IES interfaces associated with an R-VPLS service.

  • In network mode, only on the 7210 SAS-Mxp, IPv6 addressing support is available for IES and VPRN interfaces associated with an R-VPLS service.

  • In both network mode and access-uplink mode, 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. Received tagged packets are dropped.

  • In network mode, MPLS protocols (for example, RSVP and LDP) cannot be enabled on an R-VPLS IP interface.

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

  • In network mode, R-VPLS SAPs can be configured on an MC-LAG LAG.

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

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

Epipe emulation using dot1q VLAN range SAP in VPLS with G.8032

Note:

This feature is only supported on 7210 SAS-T operating in access-uplink mode.

On the node where the service originates, in addition to the access dot1q range SAP, the service needs to be configured with access-uplink SAPs on the two G.8032 ring ports. G.8032 mechanism is used to for breaking the loop in the ring and VPLS service protection. The intermediate nodes on the ring needs to use VPLS service with access-uplink SAPs on the ring ports and use the same G.8032 instance for protection, as one is used for service protection on the originating node.

The following figure shows how two business offices, served by an operator are connected in a ring network deployment using Dot1q range SAPs and a VPLS service with G.8032 for protection.

Figure 18. Epipe Emulation in a Ring using VPLS with G.8032

The following are the requirements to provide for an Epipe service connectivity between two business sites:

  • Transport all the VLANs used by the internal enterprise network of the businesses.

  • Support high availability for the service between the business sites by protecting against failure of the links or nodes in the ring.

To achieve connectivity between two business sites in access-uplink/Layer 2 mode is to configure SAPs for each of the individual VLANs used in the enterprise network in a VPLS service and use G.8032 for protection. The number of VLANs that was supported is limited by the number of SAPs supported on the platform.

The 7210 SAS platforms, currently support the use of Dot1q range SAPs with only Epipe services in either network/MPLS mode or access-uplink/Layer 2 mode. Dot1q range SAPs allows operators to transport a range of VLANs by providing similar service treatment (service treatment refers to forwarding decision along with encapsulation used, QoS and ACL processing, accounting, and so on) to all the VLANs configured in the range. It simplifies service configuration and allows operators to scale the number of VLANs that can be handled by the node. This took care of the need to support hundreds of VLANs using a single SAP or a small number of SAPs. When MPLS the mode is deployed in ring topology, operators have the option of using different redundancy mechanisms such as FRR, primary/secondary LSPs, Active/Standby PWs, to improve Epipe service availability. No such option is available to protect Epipe service in Layer 2 mode when deployed in a ring topology. Additionally many operators prefer G.8032 based ring protection mechanism, because a single control instance on the ring can potentially protect all the VPLS services on the ring.

This feature allows operators to deploy Epipe services in a ring topology when using Layer 2 mode, by emulating an Epipe service using a VPLS service with G.8032 protection and at the same time provides the benefits of using dot1q range SAPs. The user should ensure that the VPLS service is a point-to-point service. This is achieved by configuring a VPLS service with an access dot1q range SAP used at the customer handoff on one node in the ring and an access dot1q range SAP in a customer handoff of a VPLS service on another node (that is, at the other end of the Epipe), such that there are only two endpoints for the service in the network.

On the node where the service originates, in addition to the access dot1q range SAP, the service needs to be configured with access-uplink SAPs on the two G.8032 ring ports. G.8032 mechanism is used to for breaking the loop in the ring and VPLS service protection. The intermediate nodes on the ring needs to use VPLS service with access-uplink SAPs on the ring ports and use the same G.8032 instance for protection, as one is used for service protection on the originating node.

Epipe emulation configuration guidelines and restrictions

The VPLS service with dot1q-range SAPs uses svc-sap-type of dot1q-range and supports limited functionality in comparison to a normal VPLS service. The following list provides more information about the feature, configuration guidelines, and restrictions:

  • The user can define access dot1q range SAPs, which specifies a group of VLANs which receive similar service treatment; that is, forwarding behavior, SAP ingress QoS treatment and SAP (behavior similar to that available in Epipe service) and allows it to be configured in a VPLS service:

    • On the node, where the service originates, in addition to the access dot1q range SAP, the service should be configured with Q1.* SAPs on the two G.8032 ring ports. The access or access-uplink Q1.*SAPs can be used, but the access-uplink SAPs are recommended for use.The user cannot configure any other SAPs in the same VPLS service.

    • There is no special configuration required on intermediate nodes, that is, the ring nodes which do not terminate or originate the service. The nodes should be configured for providing transit VPLS service and the VPLS service must use the same G.8032 instance for protection as is used by the service on originating and terminating node.

    • The Epipe service on 7210, currently does not check if the inner tag received on a Q1.* SAP is within the range of the configured VLANs. VPLS service too has the same behavior.

  • Support for SAP Ingress QoS, Ingress and Egress ACLs, accounting, and other services, for dot1q range SAP configured in a VPLS service matches the support available in Epipe service.

  • G.8032 mechanism is used for loop detection in ring network and service protection. A separate VPLS service representing the G.8032 control instance must be configured and the state should be associated with this service:

    • Use of dot1q range SAPs to provide service on the interconnection node, in a G.8032 major-ring/sub-ring deployment, when using the virtual channel, is not supported. This restriction is not applicable when the interconnection node in a G.8032 major-ring/sub-ring is configured without a virtual channel.

  • mVPLS/xSTP support is available for use with Q1.* SAP on the ring ports to break the loop. This is a add-on to the G.8032 support.

  • Broadcast, Unknown Unicast and Multicast (BUM) traffic is flooded in the service.

  • Learning is enabled on the service by default, to avoid the need to flood the service traffic out of one of the ring ports, after network MAC addresses are learned. The user has an option to disable learning per service. Learning enable/disable per SAP is not supported.

  • MAC limiting is available per service. MAC limiting per SAP is not supported.

  • CFM OAM is supported. The support for UP MEPs on the dot1q range SAP in the service to be used for fault management and performance management using the CFM/Y.1731 OAM tools is available:

    • Only UP MEP is allowed to be configured only on the dot1q VLAN range SAPs. CFM/Y.1731 tools can be used for trouble shooting and performance measurements. User must pick a VLAN value from the range of VLANs configured for the dot1-range SAP using the CLI command config>eth-cfm>domain>association>bridge-identifier VLAN and enable the use of using the CLI command primary-vlan-enable under the MEP CLI context. It is used as the VLAN tag in the packet header for all the CFM/Y.1731 messages sent out in the context of the UP MEP.

    • Down MEPs and MIPs are not allowed to be configured.

    • Fault propagation is not supported with UP MEPs for dot1q range SAP in access-uplink mode.

  • CFM support is not available for SAPs on the ring ports.

  • IGMP snooping and MVR is not supported.

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 customers 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 (only for 7210 SAS devices in network mode) for each far-end node.

Local VPLS service on ALA-1

For 7210 SAS devices configured in access-uplink mode:

*A:SAS>config>service>vpls# info
----------------------------------------------
            stp
                shutdown
            exit
            sap 1/1/1:10.* create
                ingress
                    filter mac 1
                exit
            exit
            sap 1/1/2:10.* create
            exit
            no shutdown
----------------------------------------------
*A:SAS>config>service>vpls#
*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 syntax 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.

For 7210 SAS (other than access-uplink mode):
    config>service# vpls service-id [customer customer-id] [create][vpn vpn-id] [m-vpls]
    description description-string
    no shutdown
    For 7210 SAS in Access uplink mode:
    config>service# vpls service-id [customer customer-id] [create][ vpn vpn-id] [m-vpls] <service-id> [customer <customer-id>] [create] [vpn <vpn-id>] [m-vpls] [svc-sap-type {null-star|dot1q-preserve|any}] [customer-vid <vlan-id>] 
    description description-string
    no shutdown

The following is a sample VPLS configuration output.

*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 will experience a high relearn rate for the MAC and will shut 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

The following is a sample of 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 must be done in the constraints of the following two formulas:

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. 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 supports 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 more information about 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 will be 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 will take 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 formulas.

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, will transition to the forwarding state by a handshaking mechanism (rapid transition), without any waiting times. If handshaking fails (for example on shared links), the system falls back to the timer-based mechanism defined in the original STP (802.1D-1998) standard.

A shared link is a link with more than two 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 will form it's 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.

*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
Note:

Distributed VPLS is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

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.

The following is a sample configuration output of VPLS SAPs configured for ALA-1, ALA-2, and ALA-3.

*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 default QinQ SAPs to pass all traffic from access to access-uplink Port without any tag modifications
Note:

Default QinQ SAPs are only supported on 7210 SAS platforms operating in access-uplink mode.

The following is a sample VPLS SAP configuration output of Default QinQ SAPs.

ALA-1>config>service# vpls 9 customer 1 svc-sap-type null-star create
            shutdown
            stp                       
                shutdown
            exit
            sap 1/1/5:*.* create
                statistics
                    ingress
                    exit
                exit
            exit
            sap 1/1/6:*.* create
                statistics
                    ingress
                    exit
                exit
            exit
        exit
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 will 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 will always be 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 will be used in some circumstances to determine whether a SAP will be designated or blocked.

In traditional STP implementations (802.1D-1998), this field is called the port priority and has a value of 0 to 255. This field is coupled with the port number (0 to 255 also) to create a 16 bit value. In the latest STP standard (802.1D-2004) only the upper 4 bits of the port priority field are used to encode the SAP priority. The remaining 4 bits are used to extend the port ID field into a 12 bit virtual port number field. The virtual port number uniquely references a SAP within the STP instance. See SAP Virtual Port Number for more information about 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 7210 SAS 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 will dynamically be set to false if the SAP receives BPDUs (the configured edge-port value does not change). The OPER_EDGE variable will dynamically be 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 will dynamically be set to true. If auto-edge is enabled, and a BPDU is received, the OPER_EDGE variable will dynamically be 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 will be 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 will transition 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 will transition 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 the 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 will convert to the PVST encapsulation state. Each received BPDU must be correctly IEEE 802.1q tagged if the interface encapsulation type is defined as Dot1q. PVST BPDUs will be 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 correctly 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
Note:

Per-service split horizon groups are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

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 will not be copied to other SAPs in the same split horizon group.

The following is a sample VPLS configuration output 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

Note:

SDPs are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

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
Note:

Split horizon groups are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

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 will not be copied to other SAPs or spoke-SDPs in the same split horizon group.

The following is a sample VPLS configuration output 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 toward the 7210 SAS. Note that the port must be dot1q. The SAP corresponds to the (stacked) VLAN on the 7210 SAS 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 19. 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

Note:

SDPs are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode. For 7210 SAS platforms operating in access-uplink mode, management VPLS can be used for protection of QinQ uplinks. Refer to the following example for more information.

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 Example configuration for protected VPLS spoke-SDP).

  2. Create an SDP to the remote peer node (node ALA-B1 in Example configuration for protected VPLS spoke-SDP).

  3. Create a management VPLS.

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

  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 7 are in this same tunnel SDP with the management spoke-SDP created in step 6, the management VPLS will protect them.

Figure 20. Example configuration for protected VPLS spoke-SDP

Use the following 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 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 QinQ spokes (by changing the STP path-cost). When different user VPLS services are associated with either the two management VPLS services, the traffic will be split across the two QinQ spokes. Load balancing can be achieved in SAP protection scenarios.

The following figure shows an example of a configuration for load balancing with management VPLS.

Figure 21. Example configuration for load balancing with management VPLS

Note: the STP path costs in each peer node should be reversed.

config>service# vpls service-id [customer customer-id] [create] [m-vpls] [svc-sap-type {null-star | dot1q | dot1q-preserve}] [customer-vid vlan-id]
    description description-string
    sap sap-id create
    managed-vlan-list
        range vlan-range
    stp
    no shutdown
VPLS configuration output
*A:ALA-1>config>service# info
----------------------------------------------
        vpls 100 customer 1 m-vpls svc-sap-type dot1q create
            stp
                no shutdown
            exit
            sap 1/1/2:100.* create
                managed-vlan-list
                    range 1-10
                exit
                stp
                    path-cost 1
                exit
            exit
            sap 1/1/3:500.* create
                shutdown
                managed-vlan-list
                    range 1-10
                exit                  
            exit
            no shutdown
        exit
        vpls 200 customer 6 m-vpls svc-sap-type dot1q create
            stp
                no shutdown
            exit
            sap 1/1/2:1000.* create
                managed-vlan-list
                    range 110-200
                exit
            exit
            sap 1/1/3:2000.* create
                managed-vlan-list
                    range 110-200
                exit
                stp
                    path-cost 1
                exit
            exit
            no shutdown
        exit
        vpls 101 customer 1 svc-sap-type dot1q create
            stp
                shutdown
            exit
            sap 1/1/1:100 create
            exit
            sap 1/1/2:1.* create
            exit
            sap 1/1/3:1.* create
            exit
            no shutdown
        exit
        vpls 201 customer 1 svc-sap-type dot1q create
            stp
                shutdown
            exit
            sap 1/1/1:200 create
            exit
            sap 1/1/2:110.* create
            exit
            sap 1/1/3:110.* create
            exit
            no shutdown
        exit                          
----------------------------------------------
*A:ALA-1>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. Layer 2-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 ‟Layer 2-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 Layer 2-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 will destroy existing objects and recreate objects with the new values. Parameters in class 2 will 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 Layer 2-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 will be split across the two spokes.

Load balancing can be achieved in both the SAP protection and spoke-SDP protection scenarios. The following figure 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 22. 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

This following output shows example configurations for load balancing across two protected VPLS spoke-SDPs:

ALA-A configuration

The following is a sample configuration output on ALA-A.

# MVPLS 100 configs

*A:ALA-A# configure service vpls 100 
*A:ALA-A>config>service>vpls# info 
----------------------------------------------
            description "Default tls description for service id 100"
            stp
                no shutdown
            exit
            sap lag-3:100 create
                description "Default sap description for service id 100"
                managed-vlan-list
                    range 101-110
                exit
            exit
            spoke-sdp 1201:100 create
                stp
                    path-cost 100
                exit
            exit
            spoke-sdp 1401:100 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-A>config>service>vpls# 


# UVPLS 101 configs

*A:ALA-A>config>service# vpls 101 
*A:ALA-A>config>service>vpls# info 
----------------------------------------------
            description "Default tls description for service id 101"
            sap lag-3:101 create
                description "Default sap description for service id 101"
            exit
            spoke-sdp 1201:101 create
            exit
            spoke-sdp 1401:101 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-A>config>service>vpls# 


# MVPLS 200 configs
 
*A:ALA-A# configure service vpls 200 
*A:ALA-A>config>service>vpls# info 
----------------------------------------------
            description "Default tls description for service id 200"
            stp
                no shutdown
            exit
            sap lag-3:200 create
                description "Default sap description for service id 200"
                managed-vlan-list
                    range 201-210
                exit
            exit
            spoke-sdp 1202:200 create
            exit
            spoke-sdp 1402:200 create
                stp
                    path-cost 100
                exit
            exit
            no shutdown
----------------------------------------------
*A:ALA-A>config>service>vpls#


# UVPLS 201 configs

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

            description "Default tls description for service id 201"
            sap lag-3:201 create
                description "Default sap description for service id 201"
            exit
            spoke-sdp 1202:201 create
            exit
            spoke-sdp 1402:201 create
            exit
            no shutdown
----------------------------------------------
*A:ALA-A>config>service>vpls# exit all

ALA-B configuration

The following is a sample configuration output on ALA-B (7210), the upper left node. 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 following is a sample configuration output on ALA-C (7210), the upper right node.

# 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 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 QinQ spokes (by changing the STP path-cost). When different user VPLS services are associated with either the two management VPLS services, the traffic will be split across the two QinQ spokes. Load balancing can be achieved in SAP protection scenarios.

The following figure shows an example of a configuration for load balancing with management VPLS.

Figure 23. Example configuration for load balancing with management VPLS
Note:

The STP path costs in each peer node should be reversed.

config>service# vpls service-id [customer customer-id] [create][m-vpls] [svc-sap-type {null-star | any | dot1q-preserve}] [customer-vid vlan-id]
    description description-string
    sap sap-id create
    managed-vlan-list
        range vlan-range
    stp
    no shutdown

The following is a sample VPLS configuration output.

*A:ALA-1>config>service# info
----------------------------------------------
        vpls 100 customer 1 m-vpls svc-sap-type any create
            stp
                no shutdown
            exit
            sap 1/1/2:100.* create
                managed-vlan-list
                    range 1-10
                exit
                stp
                    path-cost 1
                exit
            exit
            sap 1/1/3:500.* create
                shutdown
                managed-vlan-list
                    range 1-10
                exit                  
            exit
            no shutdown
        exit
        vpls 200 customer 6 m-vpls svc-sap-type any create
            stp
                no shutdown
            exit
            sap 1/1/2:1000.* create
                managed-vlan-list
                    range 110-200
                exit
            exit
            sap 1/1/3:2000.* create
                managed-vlan-list
                    range 110-200
                exit
                stp
                    path-cost 1
                exit
            exit
            no shutdown
        exit
        vpls 101 customer 1 svc-sap-type any create
            stp
                shutdown
            exit
            sap 1/1/1:100 create
            exit
            sap 1/1/2:1.* create
            exit
            sap 1/1/3:1.* create
            exit
            no shutdown
        exit
        vpls 201 customer 1 svc-sap-type any create
            stp
                shutdown
            exit
            sap 1/1/1:200 create
            exit
            sap 1/1/2:110.* create
            exit
            sap 1/1/3:110.* create
            exit
            no shutdown
        exit                          
----------------------------------------------
*A:ALA-1>config>service# 

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 

The following is a sample RVPLS configuration output that uses 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. At the end of this section, it will be apparent that a very simple configuration will automatically generate the required values used by BGP and LDP. In most cases, deployments will 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

Using 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 will commence 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 24. 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 will have 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 Layer 2-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 25. Sample topology-AS pseudowire in VPLS

In the preceding figure, pseudowire is configured on MTU.

The following is a sample configuration output on the MTU.

*A:MTU>config>service>vpls>endpoint# back 
*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

This section describes the 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.

The following is a sample modified VPLS configuration output.

*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 is to be managed by an existing management VPLS, enter the new range first and then remove the old range. If the old range is removed before a new range is defined, all customer VPLS services in the old range will 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] spoke-sdp sdp-id
    [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 needed, first un-manage the user VPLS service by removing them from the managed-vlan-list or moving the spoke-SDPs on to another tunnel SDP.

config>service
    vpls service-id
    shutdown
Example:
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 (not applicable for 7210 SAS-T configured in access-uplink mode) 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
Example:
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
Example:
config>service# vpls 1 
    config>service>vpls# no shutdown
    config>service>vpls# exit

VPLS services command reference

Command hierarchies

VPLS service configuration commands

Global commands
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid] 
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id] 
        - no vpls service-id
            - 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 rd
                - 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
            - [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 service-name 
            - [no] shutdown
            - split-horizon-group group-name [create] 
                - description description-string
                - no description
VPLS service xSTP commands
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid] 
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
        - 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 service SAP DHCP snooping commands
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index] [create]
            - no sap sap-id 
                - dhcp
                    - description description-string
                    - no description
                    - [no] option
                        - action {replace | drop | keep}
                        - 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 DHCPv6 snooping commands for SAP and SDP bindings
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
        - no vpls service-id
            - mesh-sdp sdp-id[:vc-id] [vc-type {ether | vlan}]
            - no mesh-sdp sdp-id[:vc-id]
                - dhcp
                    - [no] description description-string
                    - [no] shutdown
                    - [no] snoop [network-facing]
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index] [create]
            - no sap sap-id 
                - dhcp
                    - [no] description description-string
                    - [no] option
                        - interface-id
                        - interface-id ascii-tuple
                        - interface-id sap-id
                        - interface-id string string
                        - no interface-id
                        - [no] remote-id [mac | string string]
                    - [no] shutdown
                    - [no] snoop [client-facing | network-facing | both]
                    - [no] trusted
 - 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] 
                - dhcp
                    - [no] description description-string
                    - [no] shutdown
                    - [no] snoop [network-facing]
SAP commands
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index] [create]
            - 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
                - 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 {1 | 60}
                            - 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
                            - bit-error-threshold bit-errors
                            - 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
                - l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp] [lldp]
                - 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
                - [no] shutdown
VPLS SAP QoS and filter commands (for 7210 SAS-T, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-Sx 10/100GE)
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
        - no vpls service-id
            - sap sap-id [create] [g8032-shg-enable] [eth-ring ring-index] [split-horizon-group group-name] 
            - sap sap-id [g8032-shg-enable] [eth-ring ring-index] [create]
            - no sap sap-id 
                - egress 
                    - 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]
                - 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
                    - no qos
VPLS SAP QoS and filter Commands (for 7210 SAS-Mxp)
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
            - sap sap-id [create] [g8032-shg-enable] [eth-ring ring-index] [split-horizon-group group-name] 
            - sap sap-id [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
                    - 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 policy-id 
VPLS service and SAP IGMP snooping and MVR commands
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid] 
            - 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] [create]
            - no sap sap-id 
                - igmp-snooping
                    - [no] disable-router-alert-check
                    - [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 seconds 
                    - 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] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
        - 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
                    - 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 service SAP xSTP commands
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
        - no vpls service-id
            - sap sap-id [split-horizon-group group-name] [g8032-shg-enable] [eth-ring ring-index] [create]
            - 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
                    - root-guard
                    - no root-guard 
                    - [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] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
        - 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 
Mesh SDP commands
Note:

Mesh SDP commands are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - 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
                            - bit-error-threshold bit-errors
                            - 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
                    - [no] disable-router-alert-check
                    - 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] source
                    - version version
                    - no version
                - ingress
                    - vc-label egress-vc-label
                - [no] mac-pinning
                - [no] static-mac ieee-address 
                - [no] shutdown
                - statistics
                    - ingress
                        - [no] drop-count-extra-vlan-tag-pkts 
                - vlan-vc-tag 0..4094
                - no vlan-vc-tag [0..4094]
Spoke-SDP commands
Note:

Spoke-SDP commands are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - no vpls service-id
            - 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] 
                - 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
                            - bit-error-threshold bit-errors
                            - 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
                    - [no] disable-router-alert-check
                    - 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] source
                    - version version
                    - no version
                - [no] ignore-standby-signaling
                - ingress
                    - vc-label egress-vc-label
                    - no vc-label [egress-vc-label] 
                - l2pt-termination [cdp] [dtp] [pagp] [stp] [udld] [vtp] [lldp]
                - no l2pt-termination 
                - no 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] shutdown
                - [no] static-mac ieee-address 
                - statistics
                    - ingress
                        - [no] drop-count-extra-vlan-tag-pkts 
                - 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 0..4094
                - no vlan-vc-tag [0..4094]
Routed VPLS commands
config
    - service
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | any}] [b-vpls | i-vpls | r-vpls] [b-vid vid]
        - vpls service-id [customer customer-id] [create] [vpn vpn-id] [m-vpls] [svc-sap-type {null-star | dot1q-preserve | dot1q-range | any}] [customer-vid vlan-id]
        - no vpls service-id
            - [no] allow-ip-int-bind 

Show commands

Note:

SDP commands are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

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]
            - dhcp6
                - statistics [interface interface-name]
                - statistics sap sap-id
                - statistics sdp sdp-id:vc-id
            - endpoint [endpoint-name]
            - fdb [sap sap-id] [expiry]] | [mac ieee-address [expiry]] | [detail] [expiry] 
            - igmp-snooping
                - all
                - base
                - mvr
                - mrouters [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 [detail]
        - 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

Note:

SDP commands are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.

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]
                - querier
            - statistics [all | sap sap-id | sdp sdp-id:vc-id]
            - 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

Command descriptions

VPLS configuration commands

Generic commands
description
Syntax

description description-string

no description

Context

config>service>vpls

config>service>vpls>split-horizon-group (not supported in access-uplink operating mode)

config>service>vpls>igmp-snooping>mvr

config>service>vpls>sap

config>service>vpls>sap>dhcp

config>service>vpls>sap>dhcp6 (supported on the 7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone))

config>service>vpls>mesh-sdp>dhcp6 (supported on the 7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone))

config>service>vpls>spoke-sdp>dhcp6 (supported on the 7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone))

config>service>vpls>spoke-sdp (not supported in access-uplink operating mode)

config>service>pw-template>split-horizon-group (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

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>dhcp6 (supported on the 7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone))

config>service>vpls>mesh-sdp>dhcp6 (supported on the 7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone))

config>service>vpls>spoke-sdp>dhcp6 (supported on the 7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone))

config>service>vpls>sap>stp

config>service>vpls>stp

config>service>vpls>spoke-sdp>stp (not supported in access-uplink operating mode)

config>service>vpls>bgp-ad (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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. Default administrative states for services and service entities is described as follows in Special Cases.

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

VPLS service commands
vpls
Syntax

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

no vpls service-id

Context

config>service

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

Description

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

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

When a service is created, the create keyword must be specified if the create command is enabled in the environment context. When a service is created, the customer keyword and customer-id parameter must be specified to associate the service with a customer. The customer-id value 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 any other service of any type. The service-id must be the same number used for every 7210 SAS on which this service is defined.

Values

service-id: 1 to 2147483648

customer customer-id

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

Values

1 to 2147483647

m-vpls

Specifies a management VPLS.

b-vpls

Specifies a PBB backbone-VPLS service, which can only be configured with SAPs. This keyword is supported only on 7210 SAS-T operating in network mode.

i-vpls

Specifies a PBB I-VPLS service, which can only be configured with SAPs. This keyword is only supported when the svc-sap-type value any is configured. This keyword is supported only on 7210 SAS-T operating in network mode.

create

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

svc-sap-type

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

Values

dot1q-preserve — Specifies that the allowed SAPs in the service are dot1q. The dot1q ID is not stripped after packets match the SAP. This option can be configured in conjunction with the b-vpls or r-vpls keywords.

null-star — Specifies the allowed SAP in the service, which can be null SAP, dot1q default, Q.* SAP, 0.* SAP, or default QinQ SAP. This option can be configured in conjunction with the b-vpls or r-vpls keywords.

any — Specifies that all supported SAPs are allowed in the service. This option can be configured in conjunction with the b-vpls, r-vpls, or i-vpls keywords.When these keywords are not configured, any can be used with a plain VPLS service, which can be configured with SAPs, spoke-SDPs, and mesh SDPs. See section QinQ SAP Configuration Restrictions for 7210 SAS platforms in network operating mode for more information about restrictions related to QinQ SAPs.

Default

any

b-vid vid

Specifies the VLAN ID to use when the svc-sap-type value is set to dot1q-preserve. This parameter is supported only when the b-vpls keyword and svc-sap-type value dot1q-preserve are configured.

Values

1 to 4094

r-vpls

Specifies the VPLS instance to be associated with an IP interface to provide routed VPLS (R-VPLS) functionality. When configured with the svc-sap-type values null-star, dot1q-preserve, and any, this keyword instantiates an R-VPLS service that can be configured only with SAPs.

Note:

The r-vpls keyword is not supported in access-uplink mode (that is, in access-uplink mode, a routed VPLS service can be configured without using this parameter).

vpls
Syntax

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

no vpls service-id

Context

config>service

Platforms

Supported only on platforms configured in the access-uplink operating mode

Description

This command creates or maintains a virtual private LAN services (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 like a zero-hop, Layer 2 switched domain. A VPLS is always a logical full mesh.

When a service is created, the create keyword must be specified if the create command is enabled in the environment context. When a service is created, the customer keyword and customer-id parameter must be specified to associate the service with a customer. The customer-id value 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 any other service of any type. The service-id must be the same number used for every 7210 SAS on which this service is defined.

Values

service-id: 1 to 2147483648

customer customer-id

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

Values

1 to 2147483647

create

Mandatory keyword when creating a VPLS service. This keyword is used to create the service instance. The create keyword requirement can be enabled or disabled in the environment>create context.

customer-vid vlan-id

Defines the dot1q VLAN ID to be specified while creating the local dot1q SAP for the svc-sap-type value dot1q-preserve. This parameter is supported only on platforms operating in access-uplink mode.

Values

1 to 4094

svc-sap-type

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

Values

dot1q-preserve — Specifies that the allowed SAPs in the service are dot1q. The dot1q ID is not stripped after packets matches the SAP.

dot1q-range - Specifies that the access SAP in the service can use VLAN ranges as the SAP tags. The VLAN ranges are configured using the configure>connection-profile CLI command. On ingress of the access dot1q SAP using VLAN ranges, the outermost tag is not removed before forwarding. This option is supported only in the access-uplink operating mode.

null-star — Specifies the allowed SAP in the service, which can be null SAPs, dot1q default, Q.* SAP, 0.* SAP or default QinQ SAP.

any — Specifies that the SAPs allowed in the service are defined as shown in SAP and service combinations for 7210 SAS-T in access-uplink mode. See the section SAP configuration notes for 7210 SAS platforms in access-uplink operating mode for more information about configuring SAPs.

Default

any

bgp
Syntax

bgp

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

Description

Commands in this context configure the parameters related to BGP.

bgp-ad
Syntax

bgp-ad

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

Description

Commands in this context configure the parameters related 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, except those operating in access-uplink mode

Description

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

Default

disabled

bpdu-translation
Syntax

bpdu-translation {auto | pvst | stp}

no bpdu-translation

Context

config>service>vpls>spoke-sdp (not supported in access-uplink operating mode)

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

Default

no bpdu-translation

Parameters
auto

Specifies that appropriate format is detected automatically, based on type of bpdus received on such port.

pvst

Specifies the BPDU-format as PVST. Note that the correct VLAN tag is included in the payload (depending on encapsulation value of outgoing SAP).

stp

Specifies the BPDU-format as STP.

l2pt-termination
Syntax

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

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, including those operating in access-uplink mode

Description
Note:

The config>service>vpls>spoke-sdp context is not supported on 7210 SAS platforms configured in the access-uplink operating mode.

This command enables Layer 2 Protocol Tunneling (L2PT) termination on a specific SAP or spoke-SDP. L2PT termination is supported for CDP, DTP, PAGP, STP, UDLD, VTP, and LLDP 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

Specifies the Cisco Discovery Protocol.

dtp

Specifies the Dynamic Trunking Protocol.

pagp

Specifies the Port Aggregation Protocol.

stp

Specifies all spanning tree protocols: stp, rstp, mstp, pvst (default) values.

udld

Specifies Unidirectional Link Detection.

vtp

Specifies the VLAN Trunking Protocol.

lldp

Specifies Link Layer Discovery Protocol (LLDP). This keyword is supported only on the 7210 SAS-Mxp.

disable-aging
Syntax

[no] disable-aging

Context

config>service>vpls

config>service>vpls>spoke-sdp

config>service>vpls>sap

config>service>pw-template

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description
Note:

The config>service>vpls>spoke-sdp and config>service>pw-template contexts are not supported on platforms configured in the access-uplink operating mode.

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 or spoke-SDPs 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 or SDPs 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

config>template>vpls-template

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description
Note:

The config>service>pw-template context is not supported on platforms configured in the access-uplink operating mode.

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

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

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

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

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

Default

no disable-learning (Normal MAC learning is enabled)

discard-unknown
Syntax

[no] discard-unknown

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

By default, packets with unknown destination MAC addresses are flooded. If discard-unknown is enabled at the VPLS level, packets with unknown destination MAC address is dropped instead (even when 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

endpoint
Syntax

endpoint endpoint-name [create]

no endpoint

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

Description

This command configures a service endpoint.

Parameters
endpoint-name

Specifies an endpoint name up to 32 characters.

create

Mandatory keyword to create 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, except those operating in access-uplink mode

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.

Default

no description

Parameters
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, except those operating in access-uplink mode

Description

This command causes the node to ignore 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 endpoint level as well as 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 a 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, except those operating in access-uplink mode

Description

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

In a regular endpoint the revert-time setting affects just 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 the case when 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

Specifies that the endpoint is non-revertive.

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, except those operating in access-uplink mode

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.

Values

6-byte mac-address (xx:xx:xx:xx:xx:xx or xx-xx-xx-xx-xx-xx). (Note: This value cannot be all zeros.)

create

Mandatory keyword while 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, except those operating in access-uplink mode

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

propagate-mac-flush
Syntax

[no] propagate-mac-flush

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

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

fdb-table-high-wmark
Syntax

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

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

Parameters
high-water-mark

Specifies the value to send logs and traps when the threshold is reached.

Values

0 to 100

Default

95%

fdb-table-low-wmark
Syntax

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

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

Parameters
low-water-mark

Specifies the value to send logs and traps when the threshold is reached.

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

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

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

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

Default

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, except those operating in access-uplink mode

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, except those operating in access-uplink mode

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.

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-binding policy-id

Context

config>service>vpls>bgp-ad

config>service>vpls>bgp

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

Description

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

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 the 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, and x and y are 16-bit integers.

Values

target:{ip-addr:comm-val | 2byte-asnumber:ext-comm-val | 4byte-asnumber:comm-val} ip-addr 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

route-distinguisher
Syntax

route-distinguisher [ip-addr:comm-val | as-number:ext-comm-val]

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, except those operating in access-uplink mode

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 then 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 Values and format (6 bytes, other 2 bytes of type is automatically generated)

Parameters
ip-addr:comm-val

Specifies the IP address.

Values

ip-addr a.b.c.d

comm-val 0 to 65535

as-number:ext-comm-val — Specifies the ASN and the

as-number 1 to 65535

ext-comm-val 0 to 4294967295

local-age
Syntax

local-age aging-timer

no local-age

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command configures the aging time for locally learned MAC addresses in the forwarding database (FDB) for the Virtual Private LAN Service (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 MACsQinQ / access-uplink SAPs.

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 — Local MACs aged after 300 seconds.

Parameters
aging-timer

Specifies the aging time for local MACs expressed in seconds.

Values

60 to 86400

mac-move
Syntax

[no] mac-move

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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 feature is an alternative way to protect your network against loops.

When enabled in a VPLS, mac-move monitors the relearn rate of each MAC. If the rate exceeds the configured maximum allowed limit, it disables the SAP where the source MAC was last seen. The SAP can be disabled permanently (until a shutdown/no shutdown command is executed) or for a length of time that grows linearly with the number of times the specific SAP was disabled. You have the option of marking a SAP as non-blockable in 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, as 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) mac-move disables one of the VPLS ports when 5 relearns were detected during the 5-second interval because then the average move-frequency of 1 relearn per second has been reached. This can already occur in the first second if the real relearn rate is 5 relearns per second or higher.

The no form of this command disables MAC move.

move-frequency
Syntax

move-frequency frequency

no move-frequency

Context

config>service>vpls>mac-move

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

2 (when mac-move is enabled). For example, 10 relearns in a 5 second period.

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

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

It is recommended that the retry-timeout value is 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

10 (when mac-move is enabled)

Parameters
timeout

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

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, including those operating in access-uplink mode

Description

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

Parameters
high-water-mark

Specifies the multicast FIB 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, including those operating in access-uplink mode

Description

This command specifies the multicast FIB low watermark. When the percentage filling level of the Multicast FIB 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 size

no mfib-table-size

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command specifies the maximum number of (s,g) entries in the multicast forwarding database (MFIB) 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 which is lower than the current number of dynamic entries present in the mfib then the number of entries remains above the limit.

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

Parameters
size

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

Values

1 to 2047 (M and Mxp)

1 to 2043(T)

remote-age
Syntax

remote-age seconds

no remote-age

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command specifies the aging time for remotely learned MAC addresses in the forwarding database (FDB) for the Virtual Private LAN Service (VPLS) instance. In a VPLS service, MAC addresses are associated with a Service Access Point (SAP) or with a Service Distribution Point (SDP). MACs associated with a SAP are classified as local MACs, and MACs associated with an SDP 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). 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 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 expressed 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, except those operating in access-uplink mode

Description

This command enables sending out ‟flush-all-from-ME” messages to all LDP peers included in affected VPLS, in the event of physical port failures or ‟oper-down” events of individual SAPs. This feature provides an LDP-based mechanism for recovering a physical link failure in a dual-homed connection to a VPLS service. This method provides an alternative to RSTP solutions where dual homing redundancy and recovery, in the case of link failure, is resolved by RSTP running between a PE router and CE devices. If the endpoint is configured within the VPLS and send-flush-on-failure is enabled, flush-all-from-me messages is 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, except those operating in access-uplink mode

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 defines the payload capabilities of the service. It is used by the system to validate the SAP and SDP binding operational state within the service.

The service MTU and a SAP service delineation encapsulation overhead (that is, 4 bytes for a dot1q tag) is used to derive the required MTU of the physical port or channel on which the SAP was created. If the required payload is larger than the port or channel MTU, then 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.

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

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

Note:

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

Default

VPLS: 1514

The following table displays MTU values for specific VC types.

Table 6. MTU Values for VC Types (VPLS)

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

Parameters
octets

Specifies the size of the MTU in octets, expressed as a decimal integer.

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, except those operating in access-uplink mode.

Description

Disabling service MTU check allows the packets to pass to the egress if the packet length is lesser 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).

Note:

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

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

Default

enabled

service-name
Syntax

service-name service-name

no service-name

Context

config>service>epipe

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command configures an optional service name, up to 64 characters, which adds a name identifier to a specific service to then use that service name in configuration references as well as display and use service names in show commands throughout the system. This helps the service provider/administrator to identify and manage services within the 7210 SAS platforms.

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

Parameters
service-name

Specifies a unique service name to identify the service. Service names may not begin with an integer (0-9).

split-horizon-group
Syntax

[no] 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, except those operating in access-uplink mode

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 is not copied to other SAPs or spoke-SDPs in the same SHG.

The 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. The same group name can be reused in different VPLS instances.

Note:

  • The split-horizon-group command is only supported on 7210 SAS platforms operating in the network mode.

  • Service-based SHGs are only supported on the 7210 SAS-T, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE operating in the network mode. On these platforms, service-based SHGs and mesh-SDPs are mutually exclusive in a VPLS service.

  • On the 7210 SAS-Mxp, 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 SHG to which the SAP or spoke-SDP belongs.

create

Mandatory keyword to create an SHG.

root-guard
Syntax

[no] root-guard

Context

config>service>vpls>sap>stp

config>service>vpls>spoke-sdp>stp (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

vpls-id
Syntax

vpls-id vpls-id

Context

config>service>vpls>bgp-ad

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

Description

This command configures the VPLS ID component that is signaled in one of the extended community attributes (ext-comm).

Values and format (6 bytes, other 2 bytes of type-subtype are automatically generated).

Parameters
vpls-id

Specifies a globally unique VPLS ID for BGP auto-discovery in this VPLS service.

Values

vpls-id : ip-addr:comm-val>|<as-number:ext-comm-val

ip-addr: a.b.c.d

comm-val 0 to 65535

as-number: 1 to 65535

ext-comm-val 0 to 4294967295

vsi-id
Syntax

vsi-id

Context

config>service>vpls>bgp-ad

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

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, except those operating in access-uplink mode

Description

This command specifies the low-order 4 bytes used to compose the Virtual Switch Instance Identifier

(VSI-ID) to use for NLRI in BGP auto-discovery in this VPLS service.

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

Default

no prefix

Parameters
low-order-vsi-id

Specifies a unique VSI-ID.

Values

0 to 4294967295

service-name
Syntax

service-name service-name

no service-name

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command configures an optional service name, up to 64 characters, which adds a name identifier to a specific service to then use that service name in configuration references as well as display and use service names in show commands throughout the system. This helps the service provider/administrator to identify and manage services within the 7210 SAS platforms.

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

Parameters
service-name

Specifies a unique service name to identify the service. Service names may not begin with an integer (0 to 9).

VPLS STP commands
stp
Syntax

stp

Context

config>service>vpls

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

The Nokia STP has a few modifications to better suit the operational characteristics of VPLS services. The most evident change is to the root bridge election. Because the core network operating between the Nokia 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 (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command configures automatic detection of the edge port characteristics of the SAP or spoke-SDP.

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, including those operating in access-uplink mode

Description
Note:

The config>service>vpls>spoke-sdp>stp context is not supported on platforms configured in the access-uplink operating mode.

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

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

Initially, the value of the SAP or spoke-SDP parameter is set to edge-port. This value changes if:

  • A BPDU is received on that port. This means that after all there is another bridge connected to this port. Then the edge-port becomes disabled.

  • If auto-edge is configured and no BPDU is received within a specific 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>service>vpls>spoke-sdp>stp

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description
Note:

The config>service>vpls>spoke-sdp>stp context is not supported on platforms configured in the access-uplink operating mode.

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

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

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

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

  • 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

15 seconds

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>service>vpls>spoke-sdp>stp

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description
Note:

The config>service>vpls>spoke-sdp>stp context is not supported on platforms configured in the access-uplink operating mode.

This command configures the STP hello time for the Virtual Private LAN Service (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, then the hello time is always taken from the locally configured parameter).

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

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

Default

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>service>vpls>spoke-sdp>stp (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

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 (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command 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 via a shared media, their SAP should all be configured as shared, and timer-based transitions are used.

The no form of this command reverts the default value.

Default

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, including those operating in access-uplink mode

Description

This command configures MSTI related parameters at SAP level. This context can be open only for existing mst-instances 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, including those operating in access-uplink mode

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 lowest priority).

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

Default

The path-cost is proportional to link speed.

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, including those operating in access-uplink mode

Description

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

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

Default

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

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This 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 via the BPDUs.

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

Default

20

Parameters
seconds

Specifies the max info age for the STP instance in seconds. Allowed values are integers in the range 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, including those operating in access-uplink mode

Description

This command specifies the version of STP the bridge is currently running.

See Spanning tree operating modes for more information about these modes.

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

Default

rstp

Parameters
rstp

Corresponds to the Rapid Spanning Tree Protocol specified in IEEE 802.1D/D4-2003.

dot1w

Corresponds to the mode where the Rapid Spanning Tree is backward compatible with IEEE 802.1w.

compdot1w

Corresponds to the Rapid Spanning Tree Protocol fully conformant to IEEE 802.1w.

mstp

Sets MSTP as the STP mode of operation. Corresponds to the Multiple Spanning Tree Protocol specified in 802.1Q REV/D5.0-09/2005

pmstp

Specifies the PMSTP mode, which is only supported 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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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 BPDU's generated by this bridge.

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

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

Default

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

Parameters
bridge-priority

Specifies the priority of this specific Multiple Spanning Tree Instance 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, including those operating in access-uplink mode

Description

This command specifies a range of VLANs associated with a specific MST-instance. 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 shutdown.

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

Parameters
vlan-range

The first VLAN range specifies the left-bound (that is, 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 (that is, 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, including those operating in access-uplink mode

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

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

Default

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, including those operating in access-uplink mode

Description

This command defines an MST region name. Two bridges are considered part of the same MST region when 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, including those operating in access-uplink mode

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

0

Parameters
revision-number

Specifies the MSTP region 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

config>service>vpls>spoke-sdp>stp (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command configures the STP path cost for the SAP or spoke-SDP.

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 or spoke-SDPs, the newly calculated root path cost is used.

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

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

Parameters
path-cost

Specifies the path cost for the SAP or spoke-SDP.

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 (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command configures the virtual port number which uniquely identifies a SAP within configuration bridge protocol data units (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 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

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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.

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

Default

4096

Parameters
bridge-priority

Specifies the bridge priority for the STP instance.

Values

Allowed values are integers in the range of 4096 to 65535 with 4096 being the highest priority. The actual bridge priority value stored/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 (not supported in access-uplink operating mode)

config>service>vpls>sap>stp

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command configures the Nokia STP priority for the SAP or spoke-SDP.

STP priority is a configurable parameter associated with a 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 or spoke-SDP 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 or spoke-SDP 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 instance, 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 to the default value.

Default

128

Parameters
stp-priority

Specifies the STP priority value for the SAP. Allowed values are integers in the range of 0 to 255, 0 being the highest priority. The actual value used for STP priority (and stored in the configuration) is the result of masking out the lower 4 bits, therefore the actual value range is 0 to 240 in increments of 16.

VPLS SAP commands
sap
Syntax

sap sap-id [split-horizon-group group-name] [create] [g8032-shg-enable] [eth-ring ring-index] (for 7210 SAS-Sx/S 1/10GE, 7210 SAS-Sx 10/100GE, and 7210 SAS-T (network mode), 7210 SAS Mxp)

sap sap-id [g8032-shg-enable] [eth-ring ring-index] [create] (for 7210 SAS-T (access-uplink mode))

no sap sap-id

Context

config>service>vpls

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

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

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

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

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

If a port is shutdown, all SAPs on that port become operationally down. When a service is shutdown, 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 is also deleted.

This command is also used to create a Ring APS Control SAP or a Data SAP whose traffic is protected by a Ring APS Instance.

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).The 7210 SAS supports explicit null encapsulation for VPLS service.

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/disabled in the environment>create context.

g8032-shg-enable

Platforms Supported - 7210 SAS-T (access-uplink).

This command must only be used 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.

discard-unknown-source
Syntax

[no] discard-unknown-source

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

When this command is enabled, packets received on a SAP or a spoke-SDP with an unknown source MAC address is dropped only if the maximum number of MAC addresses for that SAP or spoke-SDP (see max-nbr-mac-addr) has been reached. If max-nbr-mac-addr has not been set for the SAP or spoke-SDP, enabling discard-unknown-source 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 address to be forwarded by destination MAC addresses in VPLS.

Default

no discard-unknown-source

VPLS service SAP DHCP snooping commands
dhcp
Syntax

dhcp

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

Commands in this context configure DHCP snooping 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, including those operating in access-uplink mode

Description

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

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

Default

no action

Parameters
replace

Specifies 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

Specifies that a DHCP packet is dropped if an Option 82 field is present, and a counter is incremented.

keep

Specifies 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 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 only done when the incoming message has already an Option 82 field.

If no Option 82 field is present, the router does not create the Option 82 field. In this in that 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, including those operating in access-uplink mode

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, then the circuit-id sub-option is not part of the information option (Option 82).

When the command is configured without any parameters, it equals to circuit-id ascii-tuple.

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

Note:

By default, circuit-id is enabled if any of the other options, such as remote-id or vso, are configured.

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 is used.

hex

Specifies the circuit-id hex string.

vlan-ascii-tuple

Specifies that the format includes VLAN ID and dot1p bits as well as what is included in ascii-tuple already. 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, including those operating in access-uplink mode

Description

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

The no form of this command reverts 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, including those operating in access-uplink mode

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

Specifies 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, including those operating in access-uplink mode

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

config>service>ies>if>dhcp>option>vendor

config>service>vprn>if>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

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

sap-id
Syntax

[no] sap-id

Context

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

config>service>ies>if>dhcp>option>vendor

config>service>vprn>if>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command enables sending 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>if>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command enables sending 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>if>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

The string 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>if>dhcp>option>vendor

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

relay-plain-bootp
Syntax

relay-plain-bootp

no relay-plain-bootp

Context

config>service>vpls>if>dhcp

config>service>ies>if>dhcp

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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 (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command specifies a list of servers where 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 then the request is forwarded to all of the servers in the list.

There can be a maximum of eight DHCP servers 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 (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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, including those operating in access-uplink mode

Description

This command enables DHCP snooping of DHCP messages on the SAP. Enabling DHCP snooping on VPLS interfaces (SAPs) is required where DHCP messages where Option 82 information is to be inserted. 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.

Default

no snoop

VPLS DHCPv6 snooping commands for SAP and SDP bindings
dhcp6
Syntax

dhcp6

Context

config>service>vpls>mesh-sdp

config>service>vpls>sap

config>service>vpls>spoke-sdp

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

Commands in this context configure DHCPv6 parameters.

option
Syntax

option

no option

Context

config>service>vpls>sap>dhcp6

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

This command enters the context for configuring option-18 (interface ID option) and option-37 (remote ID option) suboptions.

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

Default

no option

interface-id
Syntax

interface-id

interface-id ascii-tuple

interface-id sap-id

interface-id string string

interface-id vlan-ascii-tuple

no interface-id

Context

config>service>vpls>sap>dhcp6>option

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

This command configures the interface ID option to be inserted in the DHCPv6 client messages and sent toward the DHCPv6 server.

The no form of this command disables sending the interface ID option.

Default

Nothing is enabled by default, but if the option command is enabled but not configured explicitly the default is interface-id ascii-tuple [system-name | service-id | sap-id].

Parameters
ascii-tuple

Keyword to specify the use of the ASCII-encoded concatenated tuple, which consists of the system-name, service-id, and sap-id, separated by the pipe (" | ") symbol.

sap-id

Keyword to specify the use of the SAP identifier.

string

Specifies a string of up to 32 characters, composed of printable, seven-bit ASCII characters. If the string contains special characters (#, $, spaces, and so on), the entire string must be enclosed within double quotes.

vlan-ascii-tuple

Keyword to specify that the format includes a VLAN ID and dot1p bits, in addition to the information already included in ASCII tuple. The format is supported on dot1q and qinq ports only.

remote-id
Syntax

no remote-id

remote-id

remote-id mac

remote-id string string

Context

config>service>vpls>sap>dhcp6>option

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

This command configures the information that is included in the remote ID suboption that is inserted in the DHCPv6 messages received from the client and forwarded toward the DHCPv6 sever.

If disabled, the remote-id suboption of the DHCPv6 packet is left empty. When this command is configured without any parameters, its behavior is the same as the remote-id mac option.

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

Default

If the remote-id command is enabled but not configured explicitly the default is remote-id mac.

Parameters
mac

Keyword to specify that the MAC address of the remote end is encoded in the suboption.

string

Specifies the remote ID, up to 32 characters.

snoop
Syntax

no snoop

snoop [network-facing]

snoop [client-facing | network-facing | both]

Context

config>service>vpls>mesh-sdp>dhcp6

config>service>vpls>sap>dhcp6

config>service>vpls>spoke-sdp>dhcp6

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

This command enables DHCPv6 snooping of DHCP messages on the SAP or SDP binding. DHCPv6 snooping is enabled on VPLS interfaces (SAPs or SDP bindings) and indicates where option-18 (interface ID option) and option-37 (remote ID option) information must be inserted or removed in a DHCPv6 message. This includes interfaces that are in the path to receive messages from either DHCPv6 servers or DHCPv6 clients.

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

Default

snoop network-facing (for SDP bindings)

snoop client-facing (for SAPs)

Parameters
client-facing

Keyword to specify that the service object is client-facing. On client-facing ports, only DHCPv6 client messages are processed. The parameter is only supported under the config>service>vpls>sap>dhcp6>snoop context.

network-facing

Keyword to specify that the service object is network-facing. On network-facing ports, only DHCPv6 relay-reply messages are processed.

both

Keyword to specify that the service object is both client-facing and network-facing. Specifying both indicates that DHCPv6 messages received from both the client and server/relay must be processed. The parameter is only supported under the config>service>vpls>sap>dhcp6>snoop context.

trusted
Syntax

no trusted

trusted

Context

config>service>vpls>sap>dhcp6

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

This command enables the forwarding of relay-forward messages received on service objects configured as client-facing or both.

The no form of this command results in dropping the relay-forward messages received on service objects configured as client-facing or both.

Default

no trusted

ETH-CFM service commands
eth-cfm
Syntax

eth-cfm

Context

config>service>vpls

config>service>vpls>mesh-sdp (not supported in access-uplink operating mode)

config>service>vpls>spoke-sdp (not supported in access-uplink operating mode)

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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 (not supported in access-uplink operating mode)

config>service>vpls>sap>eth-cfm

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

Parameters
mep-id

Specifies the maintenance association end point 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 under the vpls>eth-cfm construct (vMEP).

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. 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. This parameter is only supported on 7210 SAS-T (network mode), 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC).

ais-enable
Syntax

[no] ais-enable

Context

config>service>vpls>mesh-sdp>eth-cfm>mep (not supported in access-uplink operating mode)

config>service>vpls>sap>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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 (not supported in access-uplink operating mode)

config>service>vpls>sap>eth-cfm>mep>ais-enable

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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 (not supported in access-uplink operating mode)

config>service>vpls>sap>eth-cfm>mep>ais-enable

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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 (not supported in access-uplink operating mode)

config>service>vpls>sap>eth-cfm>mep>ais-enable

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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.

ccm-enable
Syntax

[no] ccm-enable

Context

config>service>vpls>mep

config>service>vpls>sap>eth-cfm>mep

config>service>vpls>mesh-sdp>mep (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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 (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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.

Default

The highest priority on the bridge-port.

Parameters
priority

Specifies the priority of CCM and LTM messages.

Values

0 to 7

eth-test-enable
Syntax

[no] eth-test-enable

Context

config>service>vpls>spoke-sdp>eth-cfm>mep (not supported in access-uplink operating mode)

config>service>vpls>sap>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

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

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

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

config>service>vpls>mesh-sdp>eth-cfm>mep>eth-test-enable (not supported in access-uplink operating mode)

config>service>vpls>spoke-sdp>eth-cfm>mep>eth-test-enable (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

low-priority-defect
Syntax

low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}

Context

config>service>vpls>mesh-sdp>eth-cfm>mep (not supported in access-uplink operating mode)

config>service>vpls>sap>eth-cfm>mep

config>service>vpls>spoke-sdp>eth-cfm>mep (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

Default

macRemErrXcon

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 (not supported in access-uplink operating mode)

config>service>vpls>sap>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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>mesh-sdp>eth-cfm>mep (not supported in access-uplink operating mode)

config>service>vpls>sap>eth-cfm>mep

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

Parameters
seconds

Specifies the one way delay threshold, in seconds.

Values

0..600

Default

3

limit-mac-move
Syntax

limit-mac-move [blockable | non-blockable]

no limit-mac-move

Context

config>service>vpls>spoke-sdp (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp (not supported in access-uplink operating mode)

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

Specifies that the agent monitors the MAC relearn rate on the SAP, and it blocks it when the relearn rate is exceeded.

non-blockable

Specifies that 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 (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp (not supported in access-uplink operating mode)

config>service>pw-template (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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, any 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

MAC pinning is not enabled by default.

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 (not supported in access-uplink operating mode)

config>service>vpls>endpoint (not supported in access-uplink operating mode)

config>service>pw-template (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command specifies the maximum number of FDB entries for both learned and static MAC addresses for this SAP, spoke-SDP or endpoint.

When the configured limit has been reached, and discard-unknown-source has been enabled for this SAP or spoke-SDP (see discard-unknown-source), packets with unknown source MAC addresses are discarded.

The no form of this command restores the global MAC learning limitations for the SAP or spoke-SDP.

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 30719 (7210 SAS-T)

1 to 61439 (7210 SAS-Mxp)

1 to 30202 (7210 SAS-Sx)

static-mac
Syntax

[no] static-mac ieee-mac-address [create]

Context

config>service>vpls>sap

config>service>vpls>mesh-sdp (not supported in access-uplink operating mode)

config>service>vpls>spoke-sdp (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command creates a local static MAC entry in the Virtual Private LAN Service (VPLS) forwarding database (FDB) associated with the Service Access Point (SAP).

In a VPLS service, MAC addresses are associated with a Service Access Point (SAP) or with a Service Distribution Point (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 MAC addresses are not learned on the edge device.

Note that 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 forwarding database.

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 when 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, including those operating in access-uplink mode

Description

Commands in this context configure VLAN ranges to be managed by a management VPLS. The list indicates, for each SAP, the ranges of associated VLANs that are affected when the SAP changes state.

This command is only valid 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, including those operating in access-uplink mode

Description

This command adds a default SAP to the managed VLAN list.

The no form of this command removes the default SAP to 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, including those operating in access-uplink mode

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 only valid 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 afterwards the old range removed. See Modifying VPLS service parameters.

Parameters
vlan-range

Specifies the VLAN start value and VLAN end value. The end-vlan must be greater than start-vlan. The format is <start-vlan>-<end-vlan>

Values

start-vlan: 0 to 4094

end-vlan: 0 to 4094

VPLS SAP statistics commands
statistics
Syntax

statistics

Context

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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, including those operating in access-uplink operating mode

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, including those operating in access-uplink operating mode

Description

This command allows the user to set 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 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.

Perform the following steps on the specified SAP to ensure that the correct statistics are collected when the counter-mode is changed.

  1. Disable writing of accounting records for the SAP by executing the config service vpls sap no collect-stats command.

  2. Change the counter-mode to the needed option by executing the config service vpls sap counter-mode {in-out-profile-count | forward-drop-count} command.

  3. Enable writing of accounting records for the SAP by executing the config service vpls sap collect-stats command.

Default

in-out-profile-count

Parameters
forward-drop-count

Specifies 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/octets received on SAP ingress. The dropped count is count of packets/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

Specifies 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, except those operating in access-uplink mode

Description

This command associates a counter which enables the counting of extra VLAN-tag dropped packets for the SAP, spoke-SDP, or mesh SDP. A limited amount of such counters are available for use.

The no form of this command removes the associated counter.

VPLS filter and QoS policy commands
egress
Syntax

egress

Context

config>service>vpls>sap

config>service>ies>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

Commands in this context configure egress filter policies.

If no egress filter is defined, no filtering is performed.

ingress
Syntax

ingress

Context

config>service>vpls>sap

config>service>ies>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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.

agg-rate-limit
Syntax

agg-rate-limit [cir cir-rate] [pir pir-rate]

no agg-rate-limit

Context

config>service>vpls>sap>egress

config>service>epipe>sap>egress

Platforms

7210 SAS-Mxp

Description

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

Values

0 to 10000000

pir-rate

Specifies the PIR in kilobits per second.

Values

1 to 10000000, max

filter
Syntax

filter ip ip-filter-id

filter ipv6 ipv6-filter-id

filter mac mac-filter-id

Context

config>service>vpls>sap>egress

config>service>vpls>sap>ingress

config>service>ies>sap>egress

config>service>ies>sap>ingress

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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 are two types of filter policies: 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 returned.

In general, filters applied to SAPs (ingress or egress) apply to all packets on the SAP. One exception is 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

Specifies that both MAC and IP filters are supported on a VPLS service SAP.

Parameters
ip ip-filter-id

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

Values

1 to 65535

qos
Syntax

qos policy-id

qos policy-id [enable-table-classification]

no qos policy-id

Context

config>service>vpls>sap>ingress

config>service>vpls>sap>egress (for 7210 SAS-Mxp only)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command associates a Quality of Service (QoS) policy with an ingress or egress Service Access Point (SAP).

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.

Note:

SAP egress QoS policies are only supported on the 7210 SAS-Mxp.

On the 7210 SAS-Mxp (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

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

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

accounting-policy
Syntax

accounting-policy acct-policy-id

no accounting-policy

Context

config>service>vpls>spoke-sdp (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp (not supported in access-uplink operating mode)

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

Default

default accounting policy

Parameters
acct-policy-id

Enter the accounting policy-id as configured in the config>log>accounting-policy context.

Values

1 to 99

collect-stats
Syntax

[no] collect-stats

Context

config>service>vpls>spoke-sdp (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp (not supported in access-uplink operating mode)

config>service>vpls>sap

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command enables accounting and statistical data collection for either the SAP, network port, or IP interface. When applying accounting policies the data, by default, 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 then 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, except those operating in access-uplink mode

Description

This command binds a VPLS service to an existing Service Distribution Point (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, which 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 the SDP binding is removed, no packets are forwarded to the far-end router.

Default

no sdp-id is bound to a service

Special Cases
VPLS

Specifies that 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 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

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 type of VC. The 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 binding 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

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.

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, except those operating in access-uplink mode

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” on which 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.

SDPs must be explicitly associated and bound to a service to allow far-end devices to participate in the service. The SDP must already exist in the config>service>sdp context before it can be associated with a VPLS service. If the 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.

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 a unique vc-id. An error message is generated if two SDP bindings with an identical vc-id terminate on the same router. Split-horizon groups can only be created 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 to create a spoke-SDP.

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

vlan

Keyword to define the VC type as VLAN. The ether and vlan keywords are mutually exclusive. When the VC type is not defined, 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.

split-horizon-group group-name

Specifies the name of the split horizon group to which the SDP belongs.

vc-type

Keyword to override 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.

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. This keyword is supported only on the 7210 SAS-Sx/S 1/10GE operating in standalone mode.

Note:

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.

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, except those operating in access-uplink mode

Description

Commands in this context configure egress SDP.

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, except those operating in access-uplink mode

Description

Commands in this context configure ingress SDP.

force-vlan-vc-forwarding
Syntax

[no] force-vlan-vc-forwarding

Context

config>service>epipe>spoke-sdp

config>service>vpls>mesh-sdp

config>service>vpls>spoke-sdp

config>service>pw-template

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

Description

This command forces vc-vlan-type forwarding in the datapath for spoke/mesh SDPs which have either vc-type. This command is not allowed on vlan-vc-type SDPs.

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

Default

disabled

hash-label
Syntax

hash-label [signal-capability]

no hash-label

Context

config>service>vpls>spoke-sdp

config>service>vpls>mesh-sdp

Platforms

7210 SAS-Mxp, 7210 SAS-R6 IMM-b, 7210 SAS-R12 IMM-b, 7210 SAS-R6 IMM-c, 7210 SAS-R12 IMM-c, and 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC)

Description

This command enables the use of a 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 command is enabled, the ingress datapath is modified such 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. Only the hash-2 parameters are used to compute the hash label, even if the SDP is over a lag (with load-balancing set as hash-1 or hash-2) or a port. The egress datapath adds the hash label at the bottom of the stack (BoS) and sets the S-bit to one.

Note:

On the 7210 SAS, the hash label is not used on the local node for ECMP hashing and LAG hashing. It is available for use by LSR nodes, through which the traffic flows and which 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.

The user enables 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 procedures 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 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, then the local node disables the hash label capability. Therefore local PE node does not insert a hash label in user and control plane packets it forwards on the spoke-sdp or mesh-sdp. It also drops user and control plane packets received from remote PE if they include a hash label. Note that the latter may be caused by a remote 7210 PE which does not support the hash-label option, or which 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 because of a mis-configuration.

  • If remote PE sends Flow Label sub-TLV in the PW ID FEC element with T=TRUE and R=TRUE, then the local PE enables the hash label capability. Therefore local PE inserts a hash label in user and control plane packets it forwards on the spoke-sdp or mesh-sdp. It also accepts user and control plane packets remote PE with or without hash label

    • If the hash-label option 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 have the hash label included. These packets must be dropped. The only way to solve this is to disable the signaling capability option on the local node which results 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 does 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 is always in the range [524,288 - 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 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, user must ensure that both the ends are correctly configured to either process hash labels or disable it.

The no form of this command disables the use of the hash label.

Default

no hash-label

Parameters
signal-capability

Enables the signaling and negotiation of the use of the hash label between the local and remote PE nodes.

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, except those operating in access-uplink mode

Description

This command configures the egress VC label.

Parameters
vc-label

Specifies the 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, except those operating in access-uplink mode

Description

This command configures the ingress VC label.

Parameters
vc-label

Specifies the VC ingress value that indicates a specific connection.

Values

2048 to 18431

vlan-vc-tag
Syntax

vlan-vc-tag 0..4094

no vlan-vc-tag [0..4094]

Context

config>service>vpls>spoke-sdp

config>service>vpls>mesh-sdp

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

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
0..4094

Specifies a valid VLAN identifier to bind an 802.1Q VLAN tag ID.

SAP IGMP-snooping commands
igmp-snooping
Syntax

igmp-snooping

Context

config>service>vpls

config>service>vpls>sap

config>service>vpls>spoke-sdp (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp (not supported in access-uplink operating mode)

config>service>pw-template (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

Commands in this context configure Internet Group Management Protocol (IGMP) snooping.

disable-router-alert-check
Syntax

[no] disable-router-alert-check

Context

config>service>vpls>sap>igmp-snooping

Platforms

Supported on 7210 SAS platforms operating in access-uplink mode, or in an R-VPLS on 7210 SAS platforms operating in network mode.

Description

This command enables the IGMP router alert check option.

Note:

The disable-router-alert-check command is not supported in a VPLS on 7210 SAS platforms operating in network mode.

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

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, including those operating in access-uplink mode

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.

Default

no description

Parameters
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, including those operating in access-uplink mode

Description

This command enables fast leave. When IGMP fast leave processing is enabled, the 7210 SAS immediately removes a SAP or SDP from the multicast group when it detects an IGMP ‟leave” on that SAP or SDP. Fast leave processing allows the switch to remove a SAP or SDP that sends a 'leave' from the forwarding table without first sending out group-specific queries to the SAP or SDP, and therefore speeds up the process of changing channels ('zapping').

Fast leave should only be enabled when there is a single receiver present on the SAP or SDP. 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, including those operating in access-uplink mode

Description

This command configures the VPLS and R-VPLS 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 R-VPLS 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>igmp-snooping>static (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping>static (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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 any membership report from a host.

Note:

Only SAPs are supported in an R-VPLS. SDPs are not supported in an R-VPLS.

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, including those operating in access-uplink mode

Description

This command identifies a filter policy of multicast groups to be applied to this VPLS entity. The sources of the multicast traffic must be a member of the VPLS.

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

Default

no group policy

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.

import
Syntax

import policy-name

no import

Context

config>service>vpls>sap>igmp-snooping

config>service>vpls>spoke-sdp>igmp-snooping (not supported in access-uplink operating mode)

config> service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>pw-template>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command specifies the import routing policy to be used for IGMP packets to be used on this SAP or SDP. Only a single policy can be imported on a single SAP or SDP at any time.

The no form of this command removes the policy association from the SAP or SDP.

Default

no import

Parameters
policy-name

Specifies the import policy name. Values can be string up to 32 characters 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 (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>pw-template>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

Default

10

Parameters
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 max-num-groups

no max-num-groups

Context

config>service>vpls>sap>igmp-snooping

config>service>vpls>spoke-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>pw-template>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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
max-num-groups

Specifies the maximum number of groups that can be joined on this SAP or SDP.

Values

For VPLS (SAP, mesh SDP, and spoke-SDP):

1 to 2043

For R-VPLS:

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, including those operating in access-uplink mode

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 R-VPLS 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 (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command specifies whether a multicast router is attached behind this SAP or SDP.

Configuring a SAP or SDP as an mrouter-port has a double effect. First, all multicast traffic received on another SAP or SDP is copied to this SAP or SDP. Second, 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. Even though the other multicast router (non-querier) stops sending IGMP queries, it still receives reports to keep its multicast trees up to date. To support this, the mrouter-port command should be enabled on all SAPs or SDPs connecting to a multicast router.

Note that the IGMP version to be used for the reports (v1or v2) can only be determined after an initial query has been received. Until then, 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, the mrouter-port parameter cannot be set.

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, including those operating in access-uplink mode

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 (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>pw-template>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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.

Values

2 to 1024

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, including those operating in access-uplink mode

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 (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>pw-template>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

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

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 (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>pw-template>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

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

Default

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

report-src-ip
Syntax

report-src-ip-address

no report-src-ip

Context

config>service>vpls>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

0.0.0.0

Parameters
ip-address

Specifies the source IP source address in transmitted IGMP reports.

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, except those operating in access-uplink mode

Description

This command configures the spoke-SDP precedence.

Default

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, except those operating in access-uplink mode

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 (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>pw-template>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command specifies whether to send IGMP general query messages on the SAP or SDP.

When send-queries is configured, all type of queries generate ourselves 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 wrong version counter gets 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 (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command enables access to the context to configure static group addresses. Static group addresses can be configured on a SAP or SDP. When present either as a (*, g) entry, multicast packets matching the configuration is forwarded even if no join message was registered for the specific 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, including those operating in access-uplink mode

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 supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode. For 7210 SAS platforms operating in the network mode, the source command must be executed within the context of an R-VPLS.

The source command cannot be used within the context of a VPLS.

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 (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>igmp-snooping>static>group (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

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

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

Default

no starg

version
Syntax

version version

no version

Context

config>service>vpls>sap>igmp-snooping

config>service>vpls>mesh-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>vpls>spoke-sdp>igmp-snooping (not supported in access-uplink operating mode)

config>service>vpls>mesh-sdp>snooping>static (not supported in access-uplink operating mode)

config>service>pw-template>igmp-snooping (not supported in access-uplink operating mode)

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command specifies the version of IGMP which 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 on that LAN.

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 the ‟wrong version” counter is incremented.

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.

Note:

IGMPv3 is only supported on 7210 SAS platforms operating in access-uplink mode, or in an R-VPLS on 7210 SAS platforms operating in network mode.

Parameters
version

Specifies the IGMP version.

Values

1 or 2 (in network mode for VPLS services)

1, 2, or 3 (access-uplink mode)

1, 2, 3 (for R-VPLS, 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, including those operating in access-uplink mode

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 R-VPLS 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, including those operating in access-uplink mode

Description

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

VPLS Configuration Constraints for Enabling allow-ip-int-bind

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

  • SAP ingress QoS policies applied to the VPLS SAPs cannot have MAC match criteria defined

  • The VPLS service type cannot be 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

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

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, except those operating in access-uplink mode

Description

This command displays service information using the 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.

Values

2049 to 131071

Default

The egress-label1 value.

fdb-info
Syntax

fdb-info

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

Displays global FDB usage information.

Output

The following output is an example of global FDB usage information, and Output fields: FDB information describes the output fields.

Sample output
A:7210-SASE# 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-SASE# 
Table 7. Output fields: FDB information

Label

Description

Service ID

The value that identifies a service.

Mac Move

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

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

Whether the MAC learning process is enabled in this service.

Discard Unknown

Whether frames received with an unknown destination MAC are discarded in this service.

MAC Aging

Whether the MAC aging process is enabled in this service.

MAC Pinning

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, and 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, including those operating in access-uplink mode

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

Shows the time until the MAC is aged out.

Output

The following output is an example of FDB entry information for a specific MAC address, 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 8. 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, except those operating in access-uplink mode

Description

This command displays services using the 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.

Values

2049 to 131071

Default

The start-label value.

Output

The following table describes show service ingress-label output fields.

Sample output
Table 9. Output fields: 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, including those operating in access-uplink mode

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

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 service SAP information, and Output fields: 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# 
Table 10. Output fields: 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, except those operating in access-uplink mode

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.

Values

1 to 17407

Default

All SDPs.

far-end ip-addr

Displays only SDPs matching with the specified system IP address of the far-end destination 7210 SAS M 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 11. Output fields: SDP

Label

Description

Sdp Id

The SDP identifier.

Type

Indicates whether the SDP is a spoke.

VC Type

The VC type, ether or vlan.

VC Tag

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

The IP address of the remote end of the MPLS tunnel defined by this SDP.

Delivery

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

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

How often the SDP echo request messages are transmitted on this SDP.

Max Drop Count

the maximum number of consecutive SDP echo request messages that can be unacknowledged before the keepalive protocol reports a fault.

Hello Msg Len

The length of the SDP echo request messages transmitted on this SDP.

Hold Down Time

The amount of time to wait before the keepalive operating status is eligible to enter the alive state.

I. Fwd. Pkts.

The number of forwarded ingress packets.

I. Dro. Pkts

The number of dropped ingress packets.

E. Fwd. Pkts.

The number of forwarded egress packets.

E. Fwd. Octets

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, except those operating in access-uplink mode

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 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 12. Output fields: SDP-using

Label

Description

Svc ID

The service identifier.

Sdp ID

The SDP identifier.

Type

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, including those operating in access-uplink mode

Description

This command displays the services matching certain usage properties. If no optional parameters are specified, all services defined on the system are displayed.

Parameters
epipe

Displays matching Epipe services.

vpls

Displays matching VPLS instances.

mirror

Displays matching mirror services.

customer customer-id

Displays services only associated with the specified customer ID.

Values

1 to 2147483647

Default

Services associated with a customer.

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 13. Output fields: service-using

Label

Description

Service Id

The service identifier.

Type

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

Context

show>service

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

Displays more information about the service.

base

Displays basic service information.

endpoint

Displays service endpoint information.

fdb

Displays FDB entries.

labels

Displays labels being used by this service.

mstp-configuration

Displays MSTP information.

sap

Displays SAPs associated with the service.

sdp

Displays SDPs associated with the service.

stp

Displays STP information.

all
Syntax

all

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command displays more information for all aspects of the service.

Output

The following outputs are examples of detailed service information, and Output fields: service ID all describes the output fields.

Sample output

A:Dut-A>config>service#  show service id 305 all
===============================================================================
Service Detailed Information
===============================================================================
Service Id        : 305                 Vpn Id            : 305
Service Type      : uVPLS
Description       : Default tls description for service id 305
Customer Id       : 1
Last Status Change: 07/07/2009 14:39:57
Last Mgmt Change  : 07/07/2009 14:39:14
Admin State       : Up                  Oper State        : Up
MTU               : 1514
MTU Check         : Disabled
SAP Count         : 2                   SDP Bind Count    : 4
Send Flush on Fail: Disabled
Uplink Type       : MPLS                
Propagate MacFlush: Disabled 
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
 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
Ignore Standby Sig : False                    Block On Mesh Fail: False

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.      : 65165676                 E. Fwd. Octets    : 39462444830

Associated LSP LIST :
Lsp Name           : A_B_17
Admin State        : Up                       Oper State        : Up
Time Since Last Tr*: 05h24m26s
-------------------------------------------------------------------------------
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
-------------------------------------------------------------------------------
 Sdp Id 1317:305  -(10.20.1.3)
-------------------------------------------------------------------------------
Description     : Default sdp description
SDP Id             : 1317:305                 Type              : Spoke
VC Type            : Ether                    VC Tag            : n/a
Admin Path MTU     : 0                        Oper Path MTU     : 9186
Far End            : 10.20.1.3                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   : 1317:300
Ingress Label      : 130454                   Egress Label      : 130591
Admin ControlWord  : Not Preferred            Oper ControlWord  : False
Last Status Change : 07/07/2009 18:49:43      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.      : 10100                    I. Fwd. Octs.     : 7178960
E. Fwd. Pkts.      : 65466629                 E. Fwd. Octets    : 39665246044

Associated LSP LIST :
Lsp Name           : A_C_17
Admin State        : Up                       Oper State        : Up
Time Since Last Tr*: 05h24m23s
-------------------------------------------------------------------------------
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        : 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 Id 1417:305  -(10.20.1.4)
-------------------------------------------------------------------------------
Description     : Default sdp description
SDP Id             : 1417:305                 Type              : Spoke
VC Type            : Ether                    VC Tag            : n/a
Admin Path MTU     : 0                        Oper Path MTU     : 9186
Far End            : 10.20.1.4                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   : 1417:300
Ingress Label      : 130428                   Egress Label      : 131015
Admin ControlWord  : Not Preferred            Oper ControlWord  : False
Last Status Change : 07/07/2009 18:13:42      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    : 250
Learned MAC Addr   : 250                      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.      : 97516328                 I. Fwd. Octs.     : 47531982212
E. Fwd. Pkts.      : 166191635                E. Fwd. Octets    : 67215031404

Associated LSP LIST :
Lsp Name           : A_D_17
Admin State        : Up                       Oper State        : Up
Time Since Last Tr*: 09h33m18s
-------------------------------------------------------------------------------
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        : 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 Id 1617:305  -(10.20.1.6)
-------------------------------------------------------------------------------
Description     : Default sdp description
SDP Id             : 1617:305                 Type              : Spoke
VC Type            : Ether                    VC Tag            : n/a
Admin Path MTU     : 0                        Oper Path MTU     : 9186
Far End            : 10.20.1.6                Delivery          : MPLS

Admin State        : Up                       Oper State        : Up
Acct. Pol          : None                     Collect Stats     : Disabled
Managed by Service : 300                      Prune State       : Pruned
Managed by Spoke   : 1617:300
Ingress Label      : 131060                   Egress Label      : 130843
Admin ControlWord  : Not Preferred            Oper ControlWord  : False
Last Status Change : 07/07/2009 14:40:52      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.      : 12889                    I. Fwd. Octs.     : 6000654
E. Fwd. Pkts.      : 11999                    E. Fwd. Octets    : 5208494

Associated LSP LIST :
Lsp Name           : A_F_17
Admin State        : Up                       Oper State        : Up
Time Since Last Tr*: 09h33m18s
-------------------------------------------------------------------------------
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        : 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
-------------------------------------------------------------------------------
Number of SDPs : 4
-------------------------------------------------------------------------------
Service Access Points
-------------------------------------------------------------------------------
SAP 1/1/16:305
-------------------------------------------------------------------------------
Service Id         : 305
SAP                : 1/1/16:305               Encap             : q-tag
Dot1Q Ethertype    : 0x8100                   QinQ Ethertype    : 0x8100
Description        : Default sap description for service id 305

Admin State        : Up                       Oper State        : Up
Flags              : None
Last Status Change : 07/07/2009 14:39:57
Last Mgmt Change   : 07/07/2009 14:39:14
Max Nbr of MAC Addr: No Limit                 Total MAC Addr    : 0
Learned MAC Addr   : 0                        Static MAC Addr   : 0
Admin MTU          : 9212                     Oper MTU          : 9212
Ingress qos-policy : 10
Ingr IP Fltr-Id    : n/a                      Egr IP Fltr-Id    : n/a
Ingr Mac Fltr-Id   : 305                      Egr Mac Fltr-Id   : n/a
tod-suite          : None
Egr Agg Rate Limit : max
Mac Learning       : Enabled                  Discard Unkwn Srce: Disabled
Mac Aging          : Enabled                  Mac Pinning       : Disabled
L2PT Termination   : Disabled                 BPDU Translation  : Disabled

Acct. Pol          : None                     Collect Stats     : Disabled
-------------------------------------------------------------------------------
Stp Service Access Point specifics
-------------------------------------------------------------------------------
Mac Move           : Blockable
Stp Admin State    : Up                       Stp Oper State    : Up
Core Connectivity  : Down
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        : 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   : 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      : 17610
MST BPDUs rcvd     : 0                        MST BPDUs tx      : 0
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
                        Packets                 Octets
Ingress Stats:          66655                   39685976
Egress Stats:           65864342                38651746348
-------------------------------------------------------------------------------
Sap per Meter stats
-------------------------------------------------------------------------------
                        Packets                 Octets

Ingress Meter 1 (Unicast)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 2 (Unicast)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 3 (Unicast)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 4 (Unicast)
For. InProf           : 11406                   4291328
For. OutProf          : 12575                   4325376

Ingress Meter 11 (Multipoint)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 12 (Multipoint)
For. InProf           : 3108                    3108000
For. OutProf          : 2235                    2235000

Ingress Meter 13 (Multipoint)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 14 (Multipoint)
For. InProf           : 8772                    5166272
For. OutProf          : 4840                    3072000
-------------------------------------------------------------------------------
SAP lag-4:305
-------------------------------------------------------------------------------
Service Id         : 305
SAP                : lag-4:305                Encap             : q-tag
Description        : Default sap description for service id 305

Admin State        : Up                       Oper State        : Up
Flags              : None
Last Status Change : 07/07/2009 14:39:57
Last Mgmt Change   : 07/07/2009 14:39:14
Max Nbr of MAC Addr: No Limit                 Total MAC Addr    : 125
Learned MAC Addr   : 125                      Static MAC Addr   : 0
Admin MTU          : 9212                     Oper MTU          : 9212
Ingress qos-policy : 10
Ingr IP Fltr-Id    : n/a                      Egr IP Fltr-Id    : n/a
Ingr Mac Fltr-Id   : 305                      Egr Mac Fltr-Id   : n/a
tod-suite          : None
Egr Agg Rate Limit : max
Mac Learning       : Enabled                  Discard Unkwn Srce: Disabled
Mac Aging          : Enabled                  Mac Pinning       : Disabled
L2PT Termination   : Disabled                 BPDU Translation  : Disabled

Acct. Pol          : None                     Collect Stats     : Disabled
-------------------------------------------------------------------------------
Stp Service Access Point specifics
-------------------------------------------------------------------------------
Mac Move           : Blockable
Stp Admin State    : Up                       Stp Oper State    : Up
Core Connectivity  : Down
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      : 17578
MST BPDUs rcvd     : 0                        MST BPDUs tx      : 0
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
                        Packets                 Octets
Ingress Stats:          190824363               87464904956
Egress Stats:           97572636                45409567760
-------------------------------------------------------------------------------
Sap per Meter stats
-------------------------------------------------------------------------------
                        Packets                 Octets
Ingress Meter 1 (Unicast)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 2 (Unicast)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 3 (Unicast)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 4 (Unicast)
For. InProf           : 56963244                20851041536
For. OutProf          : 59512115                19403302144

Ingress Meter 11 (Multipoint)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 12 (Multipoint)
For. InProf           : 12922550                12922550000
For. OutProf          : 9452800                 9452800000

Ingress Meter 13 (Multipoint)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 14 (Multipoint)
For. InProf           : 43268112                21539479708
For. OutProf          : 6788456                 2546422464
-------------------------------------------------------------------------------
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 05:21:37              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
-------------------------------------------------------------------------------
Forwarding Database specifics
-------------------------------------------------------------------------------
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>config>service#
Sample output for 7210 SAS-T in access-uplink mode
*A:SAS-T>show>service>id# all

===============================================================================
Service Detailed Information
===============================================================================

Service Id        : 1                   Vpn Id            : 0
Service Type      : VPLS
Description       : (Not Specified)
Customer Id       : 1
Last Status Change: 04/29/2001 06:59:15
Last Mgmt Change  : 04/28/2001 03:03:03
Admin State       : Up                  Oper State        : Up
MTU               : 1514
MTU Check         : Enabled
SAP Count         : 2                   SDP Bind Count    : 0
Snd Flush on Fail : Disabled
Uplink Type:      : MPLS
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
No Matching Entries
-------------------------------------------------------------------------------
Service Access Points
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
SAP 1/1/1:10.*
-------------------------------------------------------------------------------
Service Id         : 1
SAP                : 1/1/1:10.*               Encap             : qinq
QinQ Dot1p         : Default
Description        : (Not Specified)
Admin State        : Up                       Oper State        : Up
Flags              : None
Last Status Change : 04/29/2001 06:59:15
Last Mgmt Change   : 04/28/2001 03:09:30
Dot1Q Ethertype    : 0x8100                   QinQ Ethertype    : 0x8100

Max Nbr of MAC Addr: No Limit                 Total MAC Addr    : 0
Learned MAC Addr   : 0                        Static MAC Addr   : 0
Admin MTU          : 1522                     Oper MTU          : 1522
Ingr IP Fltr-Id    : n/a                      Egr IP Fltr-Id    : n/a
Ingr Mac Fltr-Id   : 1                        Egr Mac Fltr-Id   : n/a
tod-suite          : None
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
-------------------------------------------------------------------------------
Aggregate Policer
-------------------------------------------------------------------------------
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:          142761481188            9707780720784
Egress Stats:           0                       0
Extra-Tag Drop Stats:   n/a                     n/a
-------------------------------------------------------------------------------
Sap per Meter stats
-------------------------------------------------------------------------------
                        Packets                 Octets

Ingress Meter 1 (Unicast)
For. InProf           : 17                      1162
For. OutProf          : 0                       0

Ingress Meter 11 (Multipoint)
For. InProf           : 61                      4148
For. OutProf          : 142761547917            9707785259394

-------------------------------------------------------------------------------
SAP 1/1/2:10.*
-------------------------------------------------------------------------------
Service Id         : 1
SAP                : 1/1/2:10.*               Encap             : qinq
QinQ Dot1p         : Default
Description        : (Not Specified)
Admin State        : Up                       Oper State        : Up
Flags              : None
Last Status Change : 04/29/2001 07:03:49
Last Mgmt Change   : 04/28/2001 03:02:15
Dot1Q Ethertype    : 0x8100                   QinQ Ethertype    : 0x8100

Max Nbr of MAC Addr: No Limit                 Total MAC Addr    : 0
Learned MAC Addr   : 0                        Static MAC Addr   : 0
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
tod-suite          : None
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        : 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
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
-------------------------------------------------------------------------------
Aggregate Policer
-------------------------------------------------------------------------------
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:          0                       0
Egress Stats:           535194841               36393249188
Extra-Tag Drop Stats:   n/a                     n/a
-------------------------------------------------------------------------------
Sap per Meter stats
-------------------------------------------------------------------------------
                        Packets                 Octets

Ingress Meter 1 (Unicast)
For. InProf           : 0                       0
For. OutProf          : 0                       0

Ingress Meter 11 (Multipoint)
For. InProf           : 0                       0
For. OutProf          : 0                       0

-------------------------------------------------------------------------------
VPLS Spanning Tree Information
-------------------------------------------------------------------------------
VPLS oper state    : Up                       Core Connectivity : Down
Stp Admin State    : Down                     Stp Oper State    : Down
Mode               : Rstp                     Vcp Active Prot.  : N/A

Bridge Id          : 80:00.00:25:ba:02:ea:00  Bridge Instance Id: 0
Bridge Priority    : 32768                    Tx Hold Count     : 6
Topology Change    : Inactive                 Bridge Hello Time : 2
Last Top. Change   : 0d 00:00:00              Bridge Max Age    : 20
Top. Change Count  : 0                        Bridge Fwd Delay  : 15

Root Bridge        : N/A
Primary Bridge     : N/A

Root Path Cost     : 0                        Root Forward Delay: 15
Rcvd Hello Time    : 2                        Root Max Age      : 20
Root Priority      : 32768                    Root Port         : N/A

-------------------------------------------------------------------------------
Forwarding Database specifics
-------------------------------------------------------------------------------
Service Id        : 1                   Mac Move          : Disabled
Mac Move Rate     : 2                   Mac Move Timeout  : 10
Mac Move Retries  : 3
Table Size        : 250                 Total Count       : 0
Learned Count     : 0                   Static Count      : 0
Remote Age        : 900                 Local Age         : 300
High Watermark    : 95%                 Low Watermark     : 90%
Mac Learning      : Enabled             Discard Unknown   : Disabled
Mac Aging         : Enabled             Relearn Only      : False

-------------------------------------------------------------------------------
Service Endpoints
-------------------------------------------------------------------------------
No Endpoints found.
===============================================================================
*A:SAS-T>show>service>id#
Table 14. Output fields: service ID all

Label

Description

Service Id

The service identifier.

VPN Id

The number which identifies the VPN.

Service Type

The type of service.

SDP Id

The SDP identifier.

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.

SAP Count

The number of SAPs specified for this service.

SDP Bind Count

The number of SDPs bound to this service.

Split Horizon Group

Name of the split horizon group for this service.

Description

Description of the split horizon group.

Last Changed

The date and time of the most recent management-initiated change to this split horizon group.

SDP Id

The SDP identifier.

Type

Indicates whether this service SDP binding is a spoke or a mesh.

Admin Path MTU

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

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 this SDP.

Ingress Filter

The ID of the ingress filter policy.

Egress Filter

The ID of the egress filter policy.

Far End

The IP address of the remote end of the MPLS tunnel defined by this SDP.

Last Changed

The date and time of the most recent change to this customer.

Hello Time

How often the SDP echo request messages are transmitted on this SDP.

Hello Msg Len

The length of the SDP echo request messages transmitted on this SDP.

Max Drop Count

The maximum number of consecutive SDP Echo Request messages that can be unacknowledged before the keepalive protocol reports a fault.

Hold Down Time

The amount of time to wait before the keepalive operating status is eligible to enter the alive state.

SDP Delivery Mechanism

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.

Number of SDPs

The total number SDPs applied to this service ID.

Service Id

The service identifier.

Port Id

The ID of the access port where this SAP is defined.

Description

Generic information about the SAP.

Encap Value

The value of the label used to identify this SAP on the access port.

Admin State

The administrative state of the SAP.

Oper State

The operating state of the SAP.

Last Changed

The date and time of the last change.

Admin MTU

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

Ingress qos-policy

The SAP ingress QoS policy ID.

Ingress Filter-Id

The SAP ingress filter policy ID.

Egress Filter-Id

The SAP egress filter policy ID.

Multi Svc Site

Indicates the multi-service site that the SAP is a member.

Ingress sched-policy

Indicates the ingress QoS scheduler for the SAP.

Egress sched-policy

Indicates the egress QoS scheduler for the SAP.

Acct. Pol

Indicates the accounting policy applied to the SAP.

Collect Stats

Specifies whether accounting statistics are collected on the SAP.

Ingress Stats

The number of received packets/octets for this SAP.

Egress Stats

The number of packets/octets forwarded out of this SAP.

Ingress Meter 1

The index of the ingress QoS meter of this SAP.

High priority offered

The packets or octets count of the high priority traffic for the SAP.

For.InProf

The packets or octets count of the in-profile forwarded traffic for the SAP.

For.OutProf

The number of out of profile traffic packets/octets forwarded.

Managed by Service

The service-id of the management VPLS managing this SAP.

Managed by MSTI

The MST instance inside the management VPLS managing this SAP.

Last BPDU from

The bridge ID of the sender of the last BPDU received on this SAP.

Managed by SAP

The sap-id inside the management VPLS managing this SAP.

Prune state

The STP state inherited from the management VPLS.

Managed by Service

The service-id of the management VPLS managing this spoke-SDP.

Last BPDU from

The bridge ID of the sender of the last BPDU received on this SAP.

Managed by Spoke

The sap-id inside the management VPLS managing this spoke-SDP.

Prune state

The STP state inherited from the management VPLS.

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, including those operating in access-uplink mode

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

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 show service-id ARP output fields.

Sample output
Table 15. Output Fields: 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

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command displays basic information about the service ID including service type, description, SAPs and SDP.

Output

The following output is an example of basic service information, and Output fields: 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 16. Output fields: base

Label

Description

Service Id

the service identifier

Service Type

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 port 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

The service access (SAP)

OprMTU

the actual largest service frame size (in octets) that can be transmitted through this port, 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, including those operating in access-uplink mode

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

Displays more information.

expiry

Displays time until MAC is aged out.

Output

The following output is an example of service FDB information, and Output fields: 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 17. Output fields: FDB

Label

Description

ServID

The service ID.

MAC

The associated MAC address.

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

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

The number of times retries are performed for reenabling the SAP/SDP.

Table Size

The maximum number of learned and static entries allowed in the FDB of this service.

Total Count

The total number of learned entries 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.

OAM-learned Count

The current number of OAM 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 number of 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

Whether the MAC learning process is enabled

Discard Unknown

Whether frames received with an unknown destination MAC are discarded.

Mac Aging

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

MA's supported by the agent has been reached, and therefore MAC learning is temporary disabled, and only MAC relearns can take place.

Mac Subnet Len

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 - the number of seconds used to age out TLS FDB entries learned on local SAPs

Age - 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

The time of the most recent state changes.

labels
Syntax

labels

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

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: 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 18. Output fields: labels

Label

Description

Svc Id

The service identifier.

Sdp Id

The SDP identifier.

Type

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, including those operating in access-uplink mode

Description

This command displays Layer 2 Protocol Tunnel (L2-PT) route information associated with this service.

Parameters
disabled

Displays only entries with termination disabled. This helps identify configuration errors.

detail

Displays more 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 19. Output fields: L2PT

Label

Description

Service id

Displays the 24-bit (0 to 16777215) service instance identifier for the service

L2pt-term enabled

Indicates whether L2PT-termination or BPDU-translation is in use on 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 L2PT-termination is disabled

Bpdu-trans auto

Displays the number of L2PT 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

Displays the ID of the access point where this SAP is defined

L2pt-termination

Displays whether L2pt termination is enabled or disabled

Admin Bpdu-translation

Displays whether Bpdu translation is administratively enabled or disabled

Oper Bpdu-translation

Displays whether Bpdu translation is operationally enabled or disabled

SAP Id

Displays the SAP ID

mac-move
Syntax

mac-move

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command displays MAC move related information about the service.

mstp-configuration
Syntax

mstp-configuration

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command displays the MSTP specific configuration data. This command is only valid on a management VPLS.

Output

The following output is an example of MSTP configuration information, and Output fields: MSTP configuration describes the output fields.

Sample output
*A:SASMX>show>service>id# mstp-configuration

==============================================
Mstp configuration info, Service 5
==============================================
Region Name        : abc
Region Revision    : 0
MST Max Hops       : 20

===============================================================================
vlan to MST instance mapping
===============================================================================
Instance  Priority  Vlans mapped
-------------------------------------------------------------------------------
2         0
===============================================================================
*A:SASMX>show>service>id#

Table 20. Output fields: MSTP configuration

Label

Description

Region Name

The MSTP region name.

Region Revision

The MSTP region revision.

MST Max Hops

The MSTP maximum hops specified.

Instance

The MSTP instance number.

Priority

The MSTP priority.

Vlans mapped

The VLAN range of the MSTP instance.

sap
Syntax

sap sap-id detail

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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

Displays more information for the SAP.

Output

The following outputs are examples of service SAP information, and Output fields: service ID SAP describes the output fields.

Sample output
A:7210>show>service>id# sap 1/1/1:1 detail

===============================================================================
Service Access Points(SAP)
===============================================================================
Service Id         : 1
SAP                : 1/1/1:1                  Encap             : q-tag
Description        : (Not Specified)
Admin State        : Up                       Oper State        : Down
Flags              : ServiceAdminDown
Last Status Change : 10/05/2010 07:22:04
Last Mgmt Change   : 10/05/2010 07:22:05
Dot1Q Ethertype    : 0x8100                   QinQ Ethertype    : 0x8100

Max Nbr of MAC Addr: No Limit                 Total MAC Addr    : 0
Learned MAC Addr   : 0                        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
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        : Discarding
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 : 5                        Egress qos-policy : 1
-------------------------------------------------------------------------------
Aggregate Policer (Not Available)
-------------------------------------------------------------------------------
rate               : n/a                      burst             : n/a
-------------------------------------------------------------------------------
Ingress QoS Classifier Usage
-------------------------------------------------------------------------------
Classifiers Allocated: 256                   Meters Allocated   : 32
Classifiers Used     : 2                     Meters Used        : 2
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
                        Packets                 Octets
Ingress Stats:          0                       0
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           : 0                       0
For. OutProf          : 0                       0
===============================================================================
*A:SAS>show>service>id# sap 1/1/1:10.* detail

===============================================================================
Service Access Points(SAP)
===============================================================================
Service Id         : 1
SAP                : 1/1/1:10.*               Encap             : qinq
QinQ Dot1p         : Default
Description        : (Not Specified)
Admin State        : Up                       Oper State        : Up
Flags              : None
Last Status Change : 04/29/2001 06:59:15
Last Mgmt Change   : 04/28/2001 03:09:30
Dot1Q Ethertype    : 0x8100                   QinQ Ethertype    : 0x8100

Max Nbr of MAC Addr: No Limit                 Total MAC Addr    : 0
Learned MAC Addr   : 0                        Static MAC Addr   : 0
Admin MTU          : 1522                     Oper MTU          : 1522
Ingr IP Fltr-Id    : n/a                      Egr IP Fltr-Id    : n/a
Ingr Mac Fltr-Id   : 1                        Egr Mac Fltr-Id   : n/a
tod-suite          : None
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
-------------------------------------------------------------------------------
Aggregate Policer
-------------------------------------------------------------------------------
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:          142761481188            9707780720784
Egress Stats:           0                       0
Extra-Tag Drop Stats:   n/a                     n/a
-------------------------------------------------------------------------------
Sap per Meter stats
-------------------------------------------------------------------------------
                        Packets                 Octets

Ingress Meter 1 (Unicast)
For. InProf           : 17                      1162
For. OutProf          : 0                       0

Ingress Meter 11 (Multipoint)
For. InProf           : 61                      4148
For. OutProf          : 142761547917            9707785259394
===============================================================================

Sample output for 7210 SAS-Mxp
*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 21. Output fields: service ID SAP

Label

Description

Service Id

The service identifier.

SAP

The SAP and qtag.

Encap

The encapsulation type of the SAP.

Ethertype

An Ethernet type II Ethertype value.

Admin State

The administrative state of the SAP.

Oper State

The operational state of the SAP.

Flags

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

The time of the most recent operating status change to this SAP

Last Mgmt Change

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

Whether collect stats is enabled.

SAP per Meter stats

Ingress Meter

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. (rate above CIR and below PIR) forwarded by the ingress meter.

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

The Ethernet port loopback mode

Loopback Src Addr

The configured loopback source address

Loopback Dst Addr

The configured loopback destination address

No-svc-port used

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

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, except those operating in access-uplink mode

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.

Values

1 to 17407

Default

All SDPs

far-end ip-addr

Displays only SDPs matching with the specified far-end IP address.

Default

SDPs with any far-end IP address.

detail

Displays detailed SDP information.

Output

The following output is an example of service 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 22. Output fields: service ID SDP

Label

Description

Sdp Id

The SDP identifier.

Type

Whether the SDP is spoke.

VC Type

The VC type: ether, vlan, or vpls.

VC Tag

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

The IP address of the remote end of the MPLS tunnel defined by this SDP.

Delivery

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

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, except those operating in access-uplink mode

Description

This command displays service split horizon groups.

stp
Syntax

stp [detail]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command displays information for the spanning tree protocol instance for the service.

Parameters
detail

Displays more information.

Output

The following outputs are examples of STP information, and Output fields: 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#

*7210-SAS>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               : Mstp                     Vcp Active Prot.  : N/A

Bridge Id          : 80:00.00:25:ba:04:66:a0  Bridge Instance Id: 0
Bridge Priority    : 32768                    Tx Hold Count     : 6
Topology Change    : Inactive                 Bridge Hello Time : 2
Last Top. Change   : 0d 02:54:16              Bridge Max Age    : 20
Top. Change Count  : 27                       Bridge Fwd Delay  : 15

Root Bridge        : 40:00.7c:20:64:ac:ff:63
Primary Bridge     : N/A

Root Path Cost     : 10                       Root Forward Delay: 15
Rcvd Hello Time    : 2                        Root Max Age      : 20
Root Priority      : 16384                    Root Port         : 2048

MSTP info for CIST :
Regional Root      : 80:00.7c:20:64:ad:04:5f  Root Port         : 2048
Internal RPC       : 10                       Remaining Hopcount: 19
MSTP info for MSTI 1 :
Regional Root      : This Bridge              Root Port         : N/A
Internal RPC       : 0                        Remaining Hopcount: 20
MSTP info for MSTI 2 :
Regional Root      : 00:02.7c:20:64:ad:04:5f  Root Port         : 2048
Internal RPC       : 10                       Remaining Hopcount: 19

-------------------------------------------------------------------------------
Spanning Tree Sap Specifics
-------------------------------------------------------------------------------
SAP Identifier     : 1/1/7:0                  Stp Admin State   : Up
Port Role          : Root                     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        : Dot1d
Root Guard         : Disabled                 Active Protocol   : Mstp
Last BPDU from     : 80:00.7c:20:64:ad:04:5f  Inside Mst Region : True
CIST Desig Bridge  : 80:00.7c:20:64:ad:04:5f  Designated Port   : 34816
MSTI 1 Port Prio   : 128                      Port Path Cost    : 10
MSTI 1 Desig Brid  : This Bridge              Designated Port   : 34816
MSTI 2 Port Prio   : 128                      Port Path Cost    : 10
MSTI 2 Desig Brid  : 00:02.7c:20:64:ad:04:5f  Designated Port   : 34816
Forward transitions: 17                       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     : 7310                     MST BPDUs tx      : 7277

SAP Identifier     : 1/1/8:0                  Stp Admin State   : Up
Port Role          : Alternate                Port State        : Discarding
Port Number        : 2049                     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   : Mstp
Last BPDU from     : 80:00.7c:20:64:ad:04:5f  Inside Mst Region : True
CIST Desig Bridge  : 80:00.7c:20:64:ad:04:5f  Designated Port   : 34817
MSTI 1 Port Prio   : 128                      Port Path Cost    : 10
MSTI 1 Desig Brid  : This Bridge              Designated Port   : 34817
MSTI 2 Port Prio   : 128                      Port Path Cost    : 10
MSTI 2 Desig Brid  : 00:02.7c:20:64:ad:04:5f  Designated Port   : 34817
Forward transitions: 14                       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     : 7326                     MST BPDUs tx      : 7307

SAP Identifier     : 1/1/9:0                  Stp Admin State   : Up
Port Role          : Designated               Port State        : Forwarding
Port Number        : 2050                     Port Priority     : 128
Port Path Cost     : 10                       Auto Edge         : Enabled
Admin Edge         : Disabled                 Oper Edge         : True
Link Type          : Pt-pt                    BPDU Encap        : Dot1d
Root Guard         : Disabled                 Active Protocol   : Mstp
Last BPDU from     : N/A                      Inside Mst Region : True
CIST Desig Bridge  : This Bridge              Designated Port   : 34818
MSTI 1 Port Prio   : 128                      Port Path Cost    : 10
MSTI 1 Desig Brid  : This Bridge              Designated Port   : 34818
MSTI 2 Port Prio   : 128                      Port Path Cost    : 10
MSTI 2 Desig Brid  : This Bridge              Designated Port   : 34818
Forward transitions: 2                        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      : 7415

SAP Identifier     : 1/1/25:0                 Stp Admin State   : Up
Port Role          : Alternate                Port State        : Discarding
Port Number        : 2051                     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   : Mstp
Last BPDU from     : 80:00.7c:20:64:ad:04:5f  Inside Mst Region : True
CIST Desig Bridge  : 80:00.7c:20:64:ad:04:5f  Designated Port   : 34820
MSTI 1 Port Prio   : 128                      Port Path Cost    : 10
MSTI 1 Desig Brid  : This Bridge              Designated Port   : 34819
MSTI 2 Port Prio   : 128                      Port Path Cost    : 10
MSTI 2 Desig Brid  : 00:02.7c:20:64:ad:04:5f  Designated Port   : 34820
Forward transitions: 10                       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     : 7329                     MST BPDUs tx      : 7303

SAP Identifier     : lag-1:0                  Stp Admin State   : Up
Port Role          : Alternate                Port State        : Discarding
Port Number        : 2052                     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   : Mstp
Last BPDU from     : 80:00.7c:20:64:ad:04:5f  Inside Mst Region : True
CIST Desig Bridge  : 80:00.7c:20:64:ad:04:5f  Designated Port   : 34822
MSTI 1 Port Prio   : 128                      Port Path Cost    : 10
MSTI 1 Desig Brid  : This Bridge              Designated Port   : 34820
MSTI 2 Port Prio   : 128                      Port Path Cost    : 10
MSTI 2 Desig Brid  : 00:02.7c:20:64:ad:04:5f  Designated Port   : 34822
Forward transitions: 11                       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     : 7322                     MST BPDUs tx      : 7299

===============================================================================
Sample output for 7210 SAS
*A:SAS>show>service>id# stp mst-instance 2

===============================================================================
MSTP specific info for service 5 MSTI 2
===============================================================================
Regional Root      : N/A                      Root Port         : N/A
Internal RPC       : 0                        Remaining Hopcount: 20

==================================================================
MSTP port info for MSTI 2
==================================================================
Sap/Sdp Id         Oper-     Port-      Port-       Port-  Same
                   State     Role       State       Num    Region
------------------------------------------------------------------
No data found.
==================================================================
*A:SAS>show>service>id#

Sample output with MSTP information:

*A:SAS>show>service>id# stp mst-instance 2

===============================================================================
MSTP specific info for service 5 MSTI 2
===============================================================================
Regional Root      : N/A                      Root Port         : N/A
Internal RPC       : 0                        Remaining Hopcount: 20

==================================================================
MSTP port info for MSTI 2
==================================================================
Sap/Sdp Id         Oper-     Port-      Port-       Port-  Same
                   State     Role       State       Num    Region
------------------------------------------------------------------
No data found.
==================================================================
*A:SAS>show>service>id#
Table 23. Output fields: STP

Label

Description

Bridge-id

The MAC address used to identify this bridge in the network.

Bridge fwd delay

How fast a bridge changes its state when moving toward the forwarding state.

Bridge Hello time

The amount of time between the transmission of Configuration BPDUs.

Bridge max age

The maximum age of Spanning Tree Protocol 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

The priority of the Spanning Tree Protocol instance associated with this service.

Topology change

Whether a topology change is currently in progress.

Last Top. change

The time (in hundredths of a second) since the last time a topology change was detected by the Spanning Tree Protocol instance associated with this service.

Top. change count

The total number of topology changes detected by the Spanning Tree Protocol instance associated with this service since the management entity was last reset or initialized.

Root bridge-id

The bridge identifier of the root of the spanning tree as determined by the Spanning Tree Protocol 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

The cost of the path to the root bridge as seen from this bridge.

Root forward delay

How fast the root changes its state when moving toward the forwarding state.

Root hello time

The amount of time between the transmission of configuration BPDUs.

Root max age

The maximum age of Spanning Tree Protocol information learned from the network on any port before it is discarded.

Root priority

The priority of the bridge that is currently selected as root-bridge for the network.

Root port

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

The type of encapsulation used on BPDUs sent out and received on this SAP.

Port Number

The value of the port number field which is contained in the least significant 12 bits of the 16-bit port ID associated with this SAP.

Priority

The value of the port priority field which is contained in the most significant 4 bits of the 16-bit port ID associated with this SAP.

Cost

The contribution of this port to the path cost of paths toward the spanning tree root which include this port.

Designated Port

The port identifier of the port on the designated bridge for this port's segment.

Designated Bridge

The bridge identifier of the bridge which this port considers to be the designated bridge for this port's segment.

dhcp
Syntax

dhcp

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

Commands in this context display DHCP information for the specified service.

statistics
Syntax

statistics [sap sap-id]

statistics [sdp sdp-id:vc-id] (not supported in access-uplink operating mode)

statistics [interface interface-name]

Context

show>service>id>dhcp

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command displays DHCP statistics information.

Parameters
sap sap-id

Specifies the physical port identifier portion of the SAP definition.

sdp-id

Specifies the SDP identifier.

Values

1 to 17407

interface interface-name

Displays information for the specified IP interface.

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 24. 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 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, including those operating in access-uplink mode

Description

This command displays DHCP configuration summary information.

Parameters
interface interface-name

Displays information for the specified IP interface.

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 25. Output fields: DHCP summary

Label

Description

Interface Name

The name of the router interface.

Arp Populate

Whether or not ARP populate is enabled. 7210 SAS does not support ARP populate.

Used/Provided

7210 SAS does not maintain lease state.

Info Option

Whether Option 82 processing is enabled on the interface.

Admin State

The administrative state.

dhcp6
Syntax

dhcp6

Context

show>service>id

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

Commands in this context display DHCPv6 information for the specified service.

statistics
Syntax

statistics

statistics [interface interface-name]

statistics sap sap-id

statistics sdp sdp-id:vc-id

Context

show>service>id>dhcp6

Platforms

7210 SAS-Mxp and 7210 SAS-Sx/S 1/10GE (standalone)

Description

This command displays DHCPv6 statistics information.

Parameters
interface-name

Displays information for the specified IP interface, up to 32 characters.

sap-id

Specifies the physical port identifier portion of the SAP definition.

Values

null

[port-id | lag-id ]

dot1q

[port-id | lag-id | pw-id]:qtag1

qinq

[port-id | lag-id | pw-id]:qtag1.qtag2

dot1q

[port-id | lag-id]:cp-id

port-id

slot/mda/port

lag-id

lag-id

lag keyword

id 1 to 25

pw-id

pw-id

pw keyword

id 1 to 10239

cp-id

cp-id

cp keyword

id 1 to 1000

qtag1

*, 0 to 4094

qtag2

*, 0 to 4094

sdp-id:vc-id

Specifies the SDP identifier.

Values

sdp-id — 1 to 17407

vc-id — 1 to 4294967295

Output

The following output is an example of DHCPv6 statistics information, and Output fields: DHCPv6 statistics describes the output fields.

Sample output
*A:7210# show service id 100 dhcp6 statistics sap 1/1/6 

=====================================================
DHCP6 Statistics, service 100  Sap 1/1/6
=====================================================
Client Packets Snooped               : 0
Client Packets Forwarded             : 0
Client Packets Dropped               : 0
Server Packets Snooped               : 0
Server Packets Forwarded             : 0
Server Packets Dropped               : 0
Invalid Packets Dropped              : 0
=====================================================
*A:7210#
Table 26. Output fields: DHCPv6 statistics

Label

Description

Client Packets Snooped

The number of packets received from the DHCPv6 clients that were snooped by the node

Client Packets Forwarded

The number of packets received from the DHCPv6 clients that were forwarded by the node

Client Packets Dropped

The number of packets received from the DHCPv6 clients that were discarded by the node

Server Packets Snooped

The number of packets received from the DHCPv6 server that were snooped by the node

Server Packets Forwarded

The number of packets received from the DHCPv6 server that were forwarded by the node

Server Packets Dropped

The number of packets received from the DHCPv6 server that were discarded by the node

Invalid Packets Dropped

The number of corrupted/invalid packets received from the DHCPv6 clients that were discarded by the node

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

Description

This command displays detailed information for all aspects of IGMP snooping on the VPLS service.

Output

The following outputs are examples of detailed IGMP snooping information, and Output fields: IGMP snooping all describes the output fields.

Sample output
*Sample output (7210 SAS-T in network mode)

*A:7210-SAS>show>service>id>igmp-snooping# all

===============================================================================
IGMP Snooping info for service 2
===============================================================================

-------------------------------------------------------------------------------
IGMP Snooping Base info
-------------------------------------------------------------------------------
Admin State : Down
Querier     : No querier found
-------------------------------------------------------------------------------
Sap/Sdp                Oper    MRtr Send    Max  MVR       Num
Id                     State   Port Queries Grps From-VPLS Grps
-------------------------------------------------------------------------------
sap:1/1/1              Up      No   No      None 1         1
sap:1/1/4              Up      No   No      None Local     0

-------------------------------------------------------------------------------
IGMP Snooping Querier info
-------------------------------------------------------------------------------
No querier found for this service.

-------------------------------------------------------------------------------
IGMP Snooping Multicast Routers
-------------------------------------------------------------------------------
MRouter          Sap/Sdp Id             Up Time        Expires   Version
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Number of mrouters: 0

-------------------------------------------------------------------------------
IGMP Snooping Proxy-reporting DB
-------------------------------------------------------------------------------
Group Address    Up Time
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Number of groups: 0

-------------------------------------------------------------------------------
IGMP Snooping SAP 1/1/1 Port-DB
-------------------------------------------------------------------------------
Group Address   Type    From-VPLS  Up Time        Expires  MC
                                                           Stdby
-------------------------------------------------------------------------------
224.0.0.1       dynamic 1          0d 00:11:01    246s
-------------------------------------------------------------------------------
Number of groups: 1

-------------------------------------------------------------------------------
IGMP Snooping SAP 1/1/4 Port-DB
-------------------------------------------------------------------------------
Group Address   Type    From-VPLS  Up Time        Expires  MC
                                                           Stdby
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Number of groups: 0

-------------------------------------------------------------------------------
IGMP Snooping Static Groups
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
IGMP Snooping Statistics
-------------------------------------------------------------------------------
Message Type            Received      Transmitted   Forwarded
-------------------------------------------------------------------------------
General Queries         0             0             0
Group Queries           0             0             0
V1 Reports              0             0             0
V2 Reports              68165         0             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  : 68129
MVR To SAP Cfg Drops     : 0

-------------------------------------------------------------------------------
IGMP Snooping Multicast VPLS Registration info
-------------------------------------------------------------------------------
IGMP Snooping Admin State : Down

MVR Admin State           : Down
MVR Policy                : None
-------------------------------------------------------------------------------
Local SAPs/SDPs
-------------------------------------------------------------------------------
Svc Id     Sap/Sdp                Oper      From       Num Local
           Id                     State     VPLS       Groups
-------------------------------------------------------------------------------
2          sap:1/1/1              Up        1          0
2          sap:1/1/4              Up        Local      0
-------------------------------------------------------------------------------
MVR SAPs (from-vpls=2)
-------------------------------------------------------------------------------
Svc Id     Sap/Sdp                Oper      From       Num MVR
           Id                     State     VPLS       Groups
-------------------------------------------------------------------------------
No MVR SAPs found.
===============================================================================
*A:7210-SAS>show>service>id>igmp-snooping#

Sample output for 7210 SAS in access-uplink mode

A:7210-SAS>show>service>id# igmp-snooping all

===============================================================================
IGMP Snooping info for service 1
===============================================================================

-------------------------------------------------------------------------------
IGMP Snooping Base info
-------------------------------------------------------------------------------
Admin State : Up
Querier     : 10.1.1.1 on SAP 1/1/1
-------------------------------------------------------------------------------
Sap/Sdp                Oper    MRtr Send    Max  Max  Num
Id                     State   Port Queries Grps Srcs Grps
-------------------------------------------------------------------------------
sap:1/1/1              Up      Yes  No      None None 0
sap:1/1/2              Up      No   No      None None 1

-------------------------------------------------------------------------------
IGMP Snooping Querier info
-------------------------------------------------------------------------------
Sap Id                  : 1/1/1
IP Address              : 10.1.1.1
Expires                 : 255s
Up Time                 : 0d 16:51:04
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.1.1.1          1/1/1                  0d 16:51:14    255s      2
-------------------------------------------------------------------------------
Number of mrouters: 1

-------------------------------------------------------------------------------
IGMP Snooping Proxy-reporting DB
-------------------------------------------------------------------------------
Group Address    Mode     Up Time        Num Sources
-------------------------------------------------------------------------------
224.0.0.2        exclude  0d 16:51:14    0
-------------------------------------------------------------------------------
Number of groups: 1

-------------------------------------------------------------------------------
IGMP Snooping SAP 1/1/1 Port-DB
-------------------------------------------------------------------------------
Group Address   Mode    Type    Up Time        Expires  Num
                                                        Src
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Number of groups: 0

-------------------------------------------------------------------------------
IGMP Snooping SAP 1/1/2 Port-DB
-------------------------------------------------------------------------------
Group Address   Mode    Type    Up Time        Expires  Num
                                                        Src
-------------------------------------------------------------------------------
224.0.0.2       exclude dynamic 0d 16:51:17    259s     0
-------------------------------------------------------------------------------
Number of groups: 1

-------------------------------------------------------------------------------
IGMP Snooping Static Source Groups
-------------------------------------------------------------------------------

-------------------------------------------------------------------------------
IGMP Snooping Statistics
-------------------------------------------------------------------------------
Message Type            Received      Transmitted   Forwarded
-------------------------------------------------------------------------------
General Queries         811311        0             811311
Group Queries           0             0             0
Group-Source Queries    0             0             0
V1 Reports              0             0             0
V2 Reports              18030         11928         0
V3 Reports              0             0             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
Exceeded Max Num Sources : 0
===============================================================================
Table 27. Output fields: IGMP snooping all

Label

Description

Admin State

The administrative state of the IGMP instance.

Querier

The address of the IGMP querier on the IP subnet to which the interface is attached.

Sap or SDP Id

The SAP or SDP IDs of the service ID.

Oper State

The operational state of the SAP or SDP IDs of the service ID.

Mrtr Port

Displays if the port is a multicast router port.

Send Queries

Whether the send-queries command is enabled or disabled.

Max Num Groups

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

The actual number of multicast groups that can be joined on this SAP or SDP.

MVR From VPLS Cfg Drops

The from VPLS drop count.

MVR To SAP Cfg Drops

The to SAP drop count.

MVR Admin State

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, including those operating in access-uplink mode

Description

This command displays the multicast FIB on the VPLS service.

Parameters
brief

Displays a brief output.

group grp grp-address

Displays the multicast FIB for a specific multicast group address.

Output

The following output is an example of multicast FIB information, and Output fields: 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
-------------------------------------------------------------------------------
224.0.0.4             sap:1/1/1                Local    Fwd
-------------------------------------------------------------------------------
Number of entries: 1
==============================================================================
A:7210-SAS>show>service>id#
Table 28. Output fields: MFIB

Label

Description

Group Address

The IPv4 multicast group address.

SAP ID

The SAP/SDP to which the corresponding multicast stream is forwarded/blocked.

Forwarding/Blocking

Whether the corresponding multicast stream is blocked/forwarded.

Number of Entries

The number of entries in the MFIB.

Forwarded Packets

The number of multicast packets forwarded for the corresponding source/group.

Forwarded Octets

The number of octets forwarded for the corresponding source/group.

Svc ID

The service to which the corresponding multicast stream is forwarded/blocked. Local means that the multicast stream is forwarded/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, including those operating in access-uplink mode

Description

This command displays all multicast routers.

Parameters
detail

Displays detailed information.

Output

The following output is an example of multicast router information, and Output fields: IGMP-snooping Mrouters describes the output fields.

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/1                  0d 16:53:44    254s      2
-------------------------------------------------------------------------------
Number of mrouters: 1
===============================================================================
A:7210-SAS>show>service>id#
Table 29. Output fields: IGMP-snooping Mrouters

Label

Description

MRouter

The multicast router port.

Sap/Sdp Id

The SAP and SDP ID multicast router ports.

Up Time

The length of time the mrouter has been up.

Expires

The amount of time left before the query interval expires.

Version

The configured version of IGMP running on this interface.

Number of Mrouters

The number of multicast routers.

mvr
Syntax

mvr

Context

show>service>id>igmp-snooping

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

Description

This command displays Multicast VPLS Registration (MVR) information.

Output

The following output is an example of MVR information, and Output fields: MVR describes the output fields.

Sample output
*A:7210-SAS>show>service>id>igmp-snooping# mvr

===============================================================================
IGMP Snooping Multicast VPLS Registration info for service 2
===============================================================================
IGMP Snooping Admin State : Down

MVR Admin State           : Down
MVR Policy                : None
-------------------------------------------------------------------------------
Local SAPs/SDPs
-------------------------------------------------------------------------------
Svc Id     Sap/Sdp                Oper      From       Num Local
           Id                     State     VPLS       Groups
-------------------------------------------------------------------------------
2          sap:1/1/1              Up        1          0
2          sap:1/1/4              Up        Local      0
-------------------------------------------------------------------------------
MVR SAPs (from-vpls=2)
-------------------------------------------------------------------------------
Svc Id     Sap/Sdp                Oper      From       Num MVR
           Id                     State     VPLS       Groups
-------------------------------------------------------------------------------
No MVR SAPs found.
===============================================================================
*A:7210-SAS>show>service>id>igmp-snooping#

Table 30. Output fields: MVR

Label

Description

MVR Admin State

The Administrative state.

MVR Policy

The Policy name.

Svc ID

The service identifier.

Sap/Sdp Id

The SAP and SDP IDs of the service ID.

Oper State

The operational state of the SAP and SDP IDs of the svcid.

Mrtr Port

If the port is a multicast router port.

From VPLS

Displays from which VPLS the multicast streams corresponding to the groups learned via this SAP are copied. If local, it is from its own VPLS.

Num Groups

The number of groups learned via this local SAP.

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, including those operating in access-uplink mode

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.

Values

1 — 4294967295

Default

For mesh SDPs only, all VC IDs.

Output

The following output is an example of IGMP snooping port database information, and Output fields: port database describes the output fields.

Sample output for 7210 SAS in network mode
*A:7210-SAS>show>service>id>igmp-snooping# port-db sap 1/1/1

===============================================================================
IGMP Snooping SAP 1/1/1 Port-DB for service 2
===============================================================================
Group Address   Type    From-VPLS  Up Time        Expires  MC
                                                           Stdby
-------------------------------------------------------------------------------
224.0.0.1       dynamic 1          0d 00:15:57    246s
-------------------------------------------------------------------------------
Number of groups: 1
===============================================================================
*A:7210-SAS>show>service>id>igmp-snooping#



===============================================================
*A:MTU-7210# 
*A:7210-SAS>show>service>id>igmp-snooping# port-db sap 1/1/1 detail

===============================================================================
IGMP Snooping SAP 1/1/1 Port-DB for service 2
===============================================================================
-------------------------------------------------------------------------------
IGMP Group 224.0.0.1
-------------------------------------------------------------------------------
Type             : dynamic
Up Time          : 0d 00:14:30          Expires          : 259s
Compat Mode      : IGMP Version 2
V1 Host Expires  : 0s                   V2 Host Expires  : 259s
MVR From-VPLS    : 1                    MVR To-SAP       : 1/1/4
MC Standby       : no
-------------------------------------------------------------------------------
Number of groups: 1
===============================================================================
*A:7210-SAS>show>service>id>i
Table 31. Output fields: port database

Label

Description

Group Address

The IP multicast group address for which this entry contains information.

Mode

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

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

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 regarding 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 IGMP Version 1 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 IGMP Version 2 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.

Source address

The source address for which this entry contains information.

Up Time

The time since the source group entry was created.

Expires

The amount of time remaining before this entry is aged out.

Number of sources

The number of IGMP group and source specific queries received on this SAP.

Forwarding/Blocking

Whether this entry is on the forward list or block list.

Number of groups

The number of groups configured for this SAP.

From VPLS

Displays from which VPLS the multicast streams corresponding to the groups learned via this SAP are copied. If local, it is from its own VPLS.

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, including those operating in access-uplink mode

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 reporting database information, and Output fields: proxy database describes the output fields.

Sample output
*A: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:7210#


*A: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:7210#
Table 32. Output fields: proxy database

Label

Description

Group Address

The IP multicast group address for which this entry contains information.

Mode

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

The 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, including those operating in access-uplink mode

Description

This command displays information about the IGMP snooping queriers for the VPLS service.

Output

The following output is an example of IGMP snooping querier information, and Output fields: querier describes the output fields.

Sample output
*A: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:7210# 


*A: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:T2# 
Table 33. Output fields: querier

Label

Description

SAP Id

The SAP ID of the service.

IP address

The IP address of the querier.

Expires

The time left, in seconds, that 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

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, including those operating in access-uplink mode

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. This parameter is not supported on 7210 SAS platforms operating in access-uplink mode.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID for which to display information. This parameter is not supported on 7210 SAS platforms operating in access-uplink mode.

Values

1 to 4294967295

Default

For mesh SDPs only, all VC IDs.

Output

The following output is an example of static IGMP snooping source group information, and Output fields: static describes the output fields.

Sample output
*A: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           
-------------------------------------------------------------------------------
228.8.8.8       
-------------------------------------------------------------------------------
Static (*,G) entries: 1
===============================================================================
*A:7210#
Table 34. Output fields: 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, including those operating in access-uplink mode

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. This parameter is not supported on 7210 SAS platforms operating in access-uplink mode.

Values

1 to 17407

vc-id

Specifies the virtual circuit ID on the SDP ID for which to display information. This parameter is not supported on 7210 SAS platforms operating in access-uplink mode.

Values

1 to 4294967295

Default

For mesh SDPs only, all VC IDs.

Output

The following outputs are examples of IGMP snooping statistics information, and Output Fields: IGMP-snooping statistics describes the output fields.

Sample output for 7210 SAS in network mode
*A:7210-SAS>show>service>id>igmp-snooping# statistics

===============================================================================
IGMP Snooping Statistics for service 2
===============================================================================
Message Type            Received      Transmitted   Forwarded
-------------------------------------------------------------------------------
General Queries         0             0             0
Group Queries           0             0             0
V1 Reports              0             0             0
V2 Reports              142207        0             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  : 142130
MVR To SAP Cfg Drops     : 0
===============================================================================
*A:7210-SAS>show>service>id>igmp-snooping#
Sample output for 7210 SAS-T in access-uplink mode
A:7210-SAS>show>service>id# igmp-snooping statistics

===============================================================================
IGMP Snooping Statistics for service 1
===============================================================================
Message Type            Received      Transmitted   Forwarded
-------------------------------------------------------------------------------
General Queries         816014        0             816014
Group Queries           0             0             0
Group-Source Queries    0             0             0
V1 Reports              0             0             0
V2 Reports              18134         11991         0
V3 Reports              0             0             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
Exceeded Max Num Sources : 0
===============================================================================
A:7210-SAS>show>service>id#
Table 35. Output Fields: IGMP-snooping statistics

Label

Description

Message Type

The column heading for IGMP or MLD 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 or MLDv1 report messages received, transmitted, and forwarded

V2 Reports

The number of IGMPv2 or MLDv2 report messages received, transmitted, and forwarded

V3 Reports

(IGMP only)

The number of IGMPv3 report messages received, transmitted, and forwarded

V2 Leaves

(IGMP only)

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 due to bad length

Bad IP Checksum

(IGMP only)

The number of packets dropped due to a bad IP checksum

Bad IGMP Checksum

The number of packets dropped due to a bad IGMP checksum

Bad Encoding

The number of packets dropped due to bad encoding

No Router Alert

The number of packets dropped because there was no router alert

Zero Source IP

The number of packets dropped due to a source IP address of 0.0.0.0 or 00:00:00:00:00:00:00:00

Wrong Version

The number of packets dropped due to a wrong version of IGMP or MLD

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

Exceeded Max Num Sources

The number of packets dropped because the maximum number of sources has been exceeded

endpoint
Syntax

endpoint [endpoint-name]

Context

show>service>id

Platforms

Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode

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 service 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 36. Output fields: service ID endpoint

Label

Description

Service endpoints

Endpoint name

The endpoint name.

Revert time

The revert time setting for the active spoke SDP.

Act Hold Delay

Not applicable

Ignore Standby Signaling

Whether standby signaling is ignored.

True: standby signaling is ignored

False: standby signaling is not ignored

Suppress Standby Signaling

Whether standby signaling is suppressed.

True: standby signaling is suppressed

False: standby signaling is not suppressed

Tx Active

The actively transmitting spoke SDP.

Tx Active Up Time

The length of time that the active spoke SDP has been up.

Revert Time Count Down

Not applicable

Tx Active Change Count

The number of times that there has been a change of active spoke SDPs.

Last Tx Active Change

The date and time when a different spoke SDP became the actively transmitting spoke SDP.

Members

Spoke-sdp

The primary and secondary spoke SDPs that are associated with this endpoint and shows their precedence value (0 precedence indicates the primary spoke SDP).

VPLS 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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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. This parameter is not supported on 7210 SAS platforms operating in access-uplink mode.

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. This parameter is not supported on 7210 SAS platforms operating in access-uplink mode.

spoke-sdp

Clears only service FDB entries associated with the specified spoke-SDP ID. For a spoke-SDP, the VC ID must be specified. This parameter is not supported on 7210 SAS platforms operating in access-uplink mode.

sdp-id

Specifies the SDP ID for which to clear associated FDB entries. This parameter is not supported on 7210 SAS platforms operating in access-uplink mode.

vc-id

Specifies the virtual circuit ID on the SDP ID for which to clear associated FDB entries. This parameter is not supported on 7210 SAS platforms operating in access-uplink mode.

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, except those operating in access-uplink mode

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.

Values

1 to 4294967295

Default

All VC IDs on the SDP ID.

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, except those operating in access-uplink mode

Description

This command clears and resets the spoke-SDP bindings for the service.

Parameters
sdp-id

The spoke-SDP ID to be reset.

Values

1 to 17407

vc-id

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, including those operating in access-uplink mode

Description

This command clears statistics for the SAP bound to the service.

Parameters
sap-id

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, including those operating in access-uplink mode

Description

This command clears all traffic 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, including those operating in access-uplink mode

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, except those operating in access-uplink mode

Description

This command clears the statistics for a particular mesh SDP bind.

Parameters
sdp-id[:vc-id]

sdp-id - [1..17407]

vc-id - [1..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, except those operating in access-uplink mode

Description

This command clears statistics for the spoke-SDP bound to the service.

Parameters
sdp-id

The spoke-SDP ID for which to clear statistics.

Values

1 to 17407

vc-id

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, including those operating in access-uplink mode

Description

Clears all spanning tree 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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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.

Values

1 to 4294967295

Default

For mesh SDPs only, all VC IDs.

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, including those operating in access-uplink mode

Description

This command clears the information about the IGMP snooping queriers for the VPLS service.

VPLS debug commands

id
Syntax

id service-id

Context

debug>service

Platforms

Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

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, including those operating in access-uplink mode

Description

This command enables STP debugging for a specific SDP.

1 In access-uplink mode, DHCP relay can be configured for the IES interface associated with the R-VPLS service. DHCP snooping cannot be configured on the VPLS SAPs in the R-VPLS service. In network mode, DHCP relay can be configured for the IES interface associated with the R-VPLS service. DHCP snooping cannot be configured on the VPLS SAPs in the R-VPLS Service.