VLL services
This chapter provides information about Virtual Leased Line (VLL) services and implementation notes.
Epipe services
This section provides information about the Epipe services and implementation notes.
Epipe services overview
An Epipe service is a Layer 2 point-to-point service where the customer data is encapsulated and transported across a service provider network. An Epipe service is completely transparent to the subscriber data and protocols. The Epipe service does not perform any MAC learning. A local Epipe service consists of two SAPs on the same node, whereas a distributed Epipe service consists of two SAPs on different nodes.
Each SAP configuration includes a specific port on which service traffic enters the 7210 SAS router from the customer side (also called the access side). Each port is configured with an encapsulation type. If a port is configured with an IEEE 802.1Q (referred to as Dot1q) encapsulation, a unique encapsulation value (ID) must be specified.
The following figure shows Epipe/VLL customer service.
Epipe with PBB
Epipes with PBB are supported only on 7210 SAS-T operating in the network mode.
A PBB tunnel may be linked to an Epipe to a B-VPLS. MAC switching and learning is not required for the point-to-point service (all packets ingressing the SAP are PBB encapsulated and forwarded to the PBB tunnel to the backbone destination MAC address, and all the packets ingressing the B-VPLS destined for the ISID are PBB de-encapsulated and forwarded to the Epipe SAP).
A fully specified backbone destination address must be provisioned for each PBB Epipe instance to be used for each incoming frame on the related I-SAP. If the backbone destination address is not found in the B-VPLS FDB, packets may be flooded through the B-VPLSs
All B-VPLS constructs may be used, including B-VPLS resiliency and OAM. Not all generic Epipe commands are applicable when using a PBB tunnel.
Processing packets received with more than two tags on a QinQ SAP in Epipe service
This section applies to all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
The 7210 SAS platforms operating in access-uplink mode can process and forward packets with more than two tags. See Configuration notes for restrictions on the use of SAPs by platforms operating in access-uplink mode.
To forward packets with two or more tags using a QinQ SAP, an Epipe service type is available for use when 7210 SAS devices are operating in network mode. This service allows for configuration of a QinQ SAP as one endpoint and the following service entities as the other endpoint:
MPLS spoke-SDP with vc-type set to vlan
The vc-vlan-tag must match the inner-tag VLAN ID value specified in the QinQ SAP.
dot1q SAP
The VLAN value configured for the dot1q SAP must match the inner-tag VLAN ID value of the QinQ SAP.
QinQ SAP
The inner VLAN tag of both QinQ SAPs configured in the service must be the same.
In the forward direction, the device will process the packet as follows:
If the packet is received on a QinQ SAP, assign an incoming packet to this service based on matching the outermost two tags in the packet header (that is, the first two tags in the packet header). It will strip only the outermost tag (single tag) on ingress and forward the rest to the other endpoint in the service.
If the other endpoint the packet is sent out of is an MPLS SDP, MPLS encapsulation is added.
If the other endpoint that the packet is sent out of is a dot1q SAP, the packet is forwarded as is, without any egress VLAN checks. It is expected that the operator will ensure that the inner tag of the packet matches the dot1q VLAN value.
If the other endpoint that the packet is sent out of is another QinQ SAP (for example, Q1.Q2 SAP), another tag (that is, Q2 tag) is added to the packet and sent out of the QinQ SAP.
In the reverse direction, the device will process the packet as follows:
If the packet is received on an MPLS SDP, the vc-vlan tag is retained as is and the VLAN tag corresponding to the outermost tag configured for the QinQ SAP (that is, the other endpoint) is added to the packet. The system does not match the vc-vlan tag received in the packet with the configured value (that is, the inner tag of the QinQ SAP). It is expected that the operator will configure both end of the service appropriately to ensure that only appropriate packets enter the service.
If the packet is received on a dot1q SAP, the outermost tag is not stripped and the VLAN tag corresponding to the outermost tag configured for the QinQ SAP is added to the packet.
If the packet is received on a QinQ SAP, assign an incoming packet to this service based on matching the outermost two tags in the packet header (that is, the first two tags in the packet header). It will strip only the outermost tag (single tag) on ingress. The VLAN tag corresponding to the outermost tag configured for the QinQ SAP (that is, the other endpoint) is added to the packet, which is forwarded from the QinQ SAP.
Therefore, the device processes packets received with two or more tags using the MPLS SDP or a dot1q SAP while classifying on the QinQ SAP ingress using two tags.
Feature support, configuration notes, and restrictions
An svc-sap-type value qinq-inner-tag-preserve is available for configuring the service. This must be used when creating a new Epipe service if this functionality is needed (for example, epipe 10 svc-sap-type qinq-inner-tag-preserve create):
This service is available only in network mode.
Epipe service created with the parameter svc-sap-type set to qinq-inner-tag-preserve will allow for only one QinQ SAP and only one SDP of vc-type vlan. The system will not allow the use of any other SAP in this new service; that is, null SAP, Q1. * SAP, 0.* SAP, and so on, are not allowed for configuration in this service. The SDP cannot be of vc-type ether.
The user can configure the vlan-vc tag value for the SDP, the dot1q SAP VLAN tag value, and the inner tag VLAN value of a QinQ SAP to match the VLAN ID value of the inner tag specified in the Q1.Q2 SAP configured in the service. For example, if the SAP is 1/1/10:Q1.Q2, the vlan-vc tag must be set to Q2, the dot1q SAP VLAN value must be Q2, and the inner tag of another QinQ SAP must be set to Q2.
If any other value, other than the QinQ SAP inner tag is configured for the vlan-vc tag or dot1q SAP VLAN value, or for the inner tag of the QinQ SAP, it will be errored out by the software. If the vlan-vc tag value is not configured, it defaults to use the inner VLAN tag value. It is highly recommended that the customer configure the vlan-vc-tag value to match the VLAN ID value of the inner tag configured for the QinQ SAP, to avoid misconfiguration.
Existing QoS and ACL functionality for the Epipe service entities are available, with the following exceptions:
If the packet is received with more than two tags, IP match-criteria cannot be used with SAP ingress QoS classification and ACLs (both ingress and egress ACLs).
If the packet is received with more than two tags, the Ethertype value in the mac-criteria cannot be used with SAP ingress QoS classification and ACLs (both ingress and egress ACLs).
Dot1p bits from the outermost tag (that is, Q1 VLAN tag, if the SAP is 1/1/10:Q1.Q2) will be used for SAP ingress classification. Dot1p bits of the outermost tag will be marked on egress, if marking is enabled on the egress port. The Dot1p bit value of the vc-vlan-tag is not used to mark the Dot1p bits of the outermost VLAN tag, when the packets is exiting the QinQ SAP.
OAM tools
MPLS OAM tools such as vccv-ping, vccv-trace, and so on, are supported for the SDPs.
Accounting and Statistics for the service entities (for example, SAP and SDP) will be available as before.
CFM/Y.1731 tools are supported. Up and Down MEP is supported on the SAPs and the SDPs configured in the Epipe service.
The following redundancy mechanisms available in Epipe service are supported when using MPLS SDP:
Epipe PW redundancy
MC-LAG based protection for access SAPs using the service type (along with using PW redundancy)
Configuration example of Epipe services for processing of packets received with more than two tags on a QinQ SAP
The following is a sample output of an Epipe service with the vlan-vc-tag value configured to match the inner tag specified in the Q1.Q2 SAP in the service.
*A:7210SAS>config>service# info
----------------------------------------------
epipe 10 svc-sap-type qinq-inner-tag-preserve customer 1 create
sap 1/1/3:10.45 create
exit
spoke-sdp 111:69 vc-type vlan create
vlan-vc-tag 45
exit
no shutdown
----------------------------------------------
The following is a sample output of an Epipe service with QinQ SAP and dot1q SAP. The dot1q SAP (1/1/4:45) VLAN value 45, matches the inner tag VLAN value specified with QinQ SAP (1/1/3:10.45).
*A:7210>config>service# info
----------------------------------------------
epipe 10 svc-sap-type qinq-inner-tag-preserve customer 1 create
sap 1/1/3:10.45 create
no shutdown
exit
sap 1/1/4:45 create
no shutdown
exit
no shutdown
exit
----------------------------------------------
The following is a sample output of an Epipe service with two QinQ SAPs. The inner tag of both QinQ SAPs matches and is set to a value of 45.
*A:7210>config>service# info
------------------------------------------------------------------------------------
------
epipe 10 svc-sap-type qinq-inner-tag-preserve customer 1 create
sap 1/1/3:10.45 create
no shutdown
exit
sap 1/1/4:200.45 create
no shutdown
exit
no shutdown
exit
------------------------------------------------------------------------------------
----------
Epipe operational state decoupling
An Epipe service transitions to an operational state of down when only a single entity SAP or binding is active and the operational state of the mate is down or displays an equivalent state. The default behavior does not allow operators to validate the connectivity and measure performance metrics. With this feature, an option is provided to allow operators to validate the connectivity and measure performance metrics of an Epipe service before the customer handoff. The operator can also maintain performance and continuity measurement across their network regardless of the connectivity between the terminating node and the customer.
If the SAP between the operator and the customer enters a oper down state, the Epipe remains operationally up, so the results can continue to be collected uninterrupted. The operator receives applicable port or SAP alerts and alarms. This option is available only for the customer-facing SAP failures. If a network-facing SAP or spoke-SDP, fails the operational state of the Epipe service is set to down. That is, there is no option to hold the service in an up state, if a network component fails.
The following functionality is supported:
Configuration under SAP is required to change the default behavior of the Epipe service in response to the SAP failure.
The user can create a SAP on a LAG where the LAG has no port members. In this case, the operator configures the ignore-oper-state on the SAP and the service remains operational. However, because no ports exist in the LAG member group, there is no extraction function that can be created. This feature protects against an established working configuration with full forwarding capabilities from failing to collect PM data. The user should shutdown their equipment and place the Epipe SAP in an operationally down state.
The SAP connecting the provider equipment to the customer is configured to hold the Epipe service status up when the customer-facing SAP enters any failed state. Only one SAP per Epipe is allowed to be configured.
Any failure of the network entity (network SAP or SDP-binding) still causes the Epipe service to transition to operationally down.
While the service remains operationally up, all bindings should remain operationally up and should be able to receive and transmit data. The PW status represents the failed SAP in the LDP status message, but this does not prevent the data from using the PW as a transport, in or out. This is the same as LDP status messaging.
The SAP failure continues to trigger normal reactions, except the operational state of the service.
ETH-CFM PM measurement tools (DMM/SLM) can be used with the UP MEP on the failed SAP to collect performance metric. Additionally, CFM troubleshooting tools and connectivity (LBM, LTM, AIS, CCM) can be used and will function.
ETH-CFM CCM processing and fault propagation does not change. Even when a SAP fails with the hold service UP configuration, CCM sets the Interface Status TLV to down.
VPLS services remain operationally UP until the final entity in the service enters a failed operational state. There are no changes to VPLS services and the change is specific to Epipe.
Pseudowire switching
The 7210 SAS-T can only be configured as T-PE nodes.
The 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE can be configured as either T-PE or S-PE nodes.
The pseudowire switching feature provides the user with the ability to create a VLL service by cross-connecting two spoke-SDPs. This feature allows the scaling of VLL and VPLS services in a large network in which the otherwise full mesh of PE devices would require thousands of Targeted LDP (T-LDP) sessions per PE node.
Services with one SAP and one spoke-SDP are usually created on the PE; however, the target destination of the SDP is the pseudowire switching node instead of what is usually the remote PE.
The pseudowire switching node acts in a passive role with respect to signaling of the pseudowires. It waits until one or both of the PEs sends the label mapping message before relaying it to the other PE. This is because it needs to pass the interface parameters of each PE to the other.
A pseudowire switching point TLV is inserted by the switching pseudowire to record its system address when relaying the label mapping message. This TLV is useful in a few situations:
It allows for troubleshooting of the path of the pseudowire, especially if multiple pseudowire switching points exist between the two PEs.
It helps in loop detection of the T-LDP signaling messages where a switching point would receive back a label mapping message it had already relayed.
It is inserted in pseudowire status notification messages when they are sent end-to-end or from a pseudowire switching node toward a destination PE.
Pseudowire OAM is supported for the manual switching pseudowires and allows the pseudowire switching node to relay end-to-end pseudowire status notification messages between the two PEs. The pseudowire switching node can generate a pseudowire status and send it to one or both of the PEs by including its system address in the pseudowire switching point TLV. This allows a PE to identify the origin of the pseudowire status notification message.
In the following pseudowire service switching node example, the user configures a regular Epipe VLL service PE1 and PE2. These services each consist of a SAP and a spoke-SPD. However, the target destination of the SDP is not the remote PE but the pseudowire switching node. In addition, the user configures an Epipe VLL service on the pseudowire switching node using the two SDPs.
|7210 PE1 (Epipe)|---sdp 2:10---|7210 PW SW (Epipe)|---sdp 7:15---|7210 PE2 (Epipe)|
Pseudowire switching with protection
Pseudowire switching scales VLL and VPLS services over a multi-area network by removing the need for a full mesh of targeted LDP sessions between PE nodes. The following figure shows the use of pseudowire redundancy to provide a scalable and resilient VLL service across multiple IGP areas in a provider network.
In the network in the preceding figure, PE nodes act as leading nodes and pseudowire switching nodes act as followers for the purpose of pseudowire signaling. A switching node will need to pass the SAP interface parameters of each PE to the other. T-PE1 sends a label mapping message for the Layer 2 FEC to the peer pseudowire switching node; for example, S-PE1.
It will include the SAP interface parameters, such as MTU, in the label mapping message. S-PE1 checks the FEC against the local information and if a match exists, it appends the optional pseudowire switching point TLV to the FEC TLV in which it records its system address. T-PE1 then relays the label mapping message to S-PE2. S-PE2 performs similar operations and forwards a label mapping message to T-PE2.
The same procedures are followed for the label mapping message in the reverse direction; for example, from T-PE2 to T-PE1. S-PE1 and S-PE2 will affect the spoke-SDP cross-connect only when both directions of the pseudowire have been signaled and matched.
The pseudowire switching TLV is useful in a few situations. First, it allows for troubleshooting of the path of the pseudowire, especially if multiple pseudowire switching points exist between the two T-PE nodes. Second, it helps in loop detection of the T-LDP signaling messages where a switching point receives back a label mapping message it already relayed. Finally, it can be inserted in pseudowire status messages when they are sent from a pseudowire switching node toward a destination PE.
Pseudowire status messages can be generated by the T-PE nodes. Pseudowire status messages received by a switching node are processed and then passed on to the next-hop. An S-PE node appends the optional pseudowire switching TLV, with its system address added to it, to the FEC in the pseudowire status notification message, only if it originated the message or the message was received with the TLV in it. Otherwise, the message was originated by a T-PE node and the S-PE should process and pass the message without changes except for the VC ID value in the FEC TLV.
Pseudowire switching behavior
In the network in VLL Resilience with pseudowire redundancy and switching, PE nodes act as leading nodes and pseudowire switching nodes act as followers for the purpose of pseudowire signaling. A switching node must pass the SAP interface parameters of each PE to the other. T-PE1 sends a label mapping message for the Layer 2 FEC to the peer pseudowire switching node; for example, S-PE1.
It includes the SAP interface parameters, such as MTU, in the label mapping message. S-PE1 checks the FEC against the local information and if a match exists, it appends the optional pseudowire switching point TLV to the FEC TLV in which it records its system address. T-PE1 then relays the label mapping message to S-PE2. S-PE2 performs similar operations and forwards a label mapping message to T-PE2.
The same procedures are followed for the label mapping message in the reverse direction; for example, from T-PE2 to T-PE1. S-PE1 and S-PE2 will affect the spoke-SDP cross-connect only when both directions of the pseudowire have been signaled and matched.
The merging of the received T-LDP status notification message and the local status for the spoke-SDPs from the service manager at a PE complies with the following rules:
When the local status for both spokes is up, the S-PE passes any received SAP or SDP-binding generated status notification message unchanged; for example, the status notification TLV is unchanged but the VC ID in the FEC TLV is set to the value of the pseudowire segment to the next hop.
When the local operational status for any of the spokes is down, the S-PE always sends SDP-binding down status bits, regardless of whether the received status bits from the remote node indicated SAP up/down or SDP-binding up/down.
Pseudowire switching TLV
The following figure shows the format of the pseudowire switching TLV.
PW sw TLV Length
This field specifies the total length of all the following pseudowire switching point TLV fields in octets.
Type
This field encodes how the Value field is interpreted.
Length
This field specifies the length of the Value field in octets.
Value
The octet string of Length octets encodes information to be interpreted as specified by the Type field.
The format of the pseudowire switching point sub-TLVs is as follows:
pseudowire ID of last pseudowire segment traversed
This sub-TLV type contains a pseudowire ID in the format of the pseudowire ID.
pseudowire switching point description string
This is an optional description text string up to 80 characters.
IP address of pseudowire switching point
IPv4 or IPv6 address of pseudowire switching point
This is an optional sub-TLV.
MH VCCV capability indication
Static-to-dynamic pseudowire switching
When one segment of the pseudowire cross-connect at the S-PE is static while the other is signaled using T-LDP, the S-PE operates much like a T-PE from a signaling perspective and as an S-PE from a data plane perspective.
The S-PE signals a label mapping message as soon as the local configuration is complete. The control word C-bit field in the pseudowire FEC is set to the value configured on the static spoke-SDP.
When the label mapping for the egress direction is also received from the T-LDP peer, and the information in the FEC matches that of the local configuration, the static-to-dynamic cross-connect is effected.
It is possible for end nodes of a static pseudowire segment to be misconfigured. In that case, an S-PE or T-PE node may be receiving packets with the wrong encapsulation. Therefore, an invalid payload will be forwarded over the pseudowire or the SAP, respectively. Also, if the S-PE or T-PE node is expecting the control word in the packet encapsulation, and the received packet comes with no control word but the first nibble below the label stack is 0x0001, the packet may be mistaken for a VCCV OAM packet and may be forwarded to the CPM. In that case, the CPM will perform a check of the IP header fields, such as version, IP header length, and checksum. If any of this fails, the VCCV packet will be discarded.
Pseudowire redundancy
Pseudowire redundancy provides the ability to protect a pseudowire with a preprovisioned pseudowire and to switch traffic over to the secondary standby pseudowire in case of a SAP and network failure condition. Usually, pseudowires are redundant because of the SDP redundancy mechanism. For example, if the SDP is an RSVP LSP and is protected by a secondary standby path or by fast reroute (FRR) paths, the pseudowire is also protected. However, there are a couple of applications in which SDP redundancy does not protect the end-to-end pseudowire path:
There are two different destination PE nodes for the same VLL service. The main use case is the provision of dual-homing of a CPE or access node to two PE nodes located in different POPs. The other use case is the provision of a pair of active and standby BRAS nodes, or active and standby links to the same BRAS node, to provide service resiliency to broadband service subscribers.
The pseudowire path is switched in the middle of the network and the 7210 SAS pseudowire switching node fails.
Pseudowire and VPLS link redundancy extends link-level resiliency for pseudowires and VPLS to protect critical network paths against physical link or node failures. These innovations enable the virtualization of redundant paths across the metro or core IP network to provide seamless and transparent fail-over for point-to-point and multi-point connections and services. When deployed with multi-chassis LAG, the path for return traffic is maintained through the pseudowire or VPLS switchover, which enables carriers to deliver ‟always on” services across their IP/MPLS networks.
VLL resilience with two destination PE nodes
The following figure shows the application of pseudowire redundancy to provide Ethernet VLL service resilience for broadband service subscribers accessing the broadband service on the service provider BRAS.
If the Ethernet SAP on PE2 fails, PE2 notifies PE1 of the failure by either withdrawing the primary pseudowire label it advertised or by sending a pseudowire status notification with the code set to indicate a SAP defect. PE1 will receive it and will immediately switch its local SAP to forward over the secondary standby spoke-SDP. To avoid black holing of in-flight packets during the switching of the path, PE1 will accept packets received from PE2 on the primary pseudowire while transmitting over the backup pseudowire.
When the SAP on PE2 is restored, PE2 updates the new status of the SAP by sending a new label mapping message for the same pseudowire FEC or by sending a pseudowire status notification message indicating that the SAP is back up. PE1 then starts a timer and reverts back to the primary at the expiry of the timer. By default, the timer is set to 0, which means PE1 reverts immediately. A special value of the timer (infinity) will mean that PE1 should never revert to the primary pseudowire.
The behavior of the pseudowire redundancy feature is the same if PE1 detects or is notified of a network failure that brought the spoke-SDP operational status to down. The following are the events that will cause PE1 to trigger a switchover to the secondary standby pseudowire:
T-LDP peer (remote PE) node withdrew the pseudowire label.
T-LDP peer signaled a FEC status indicating a pseudowire failure or a remote SAP failure.
T-LDP session to the peer node times out.
SDP binding and VLL service went down as a result of a network failure condition, such as the SDP to peer node going operationally down.
The 7210 SAS routers support the ability to configure multiple secondary standby pseudowire paths. For example, PE1 uses the value of the user-configurable precedence parameter associated with each spoke-SDP to select the next available pseudowire path after the failure of the current active pseudowire (whether it is the primary or one of the secondary pseudowires). However, the revertive operation always switches the path of the VLL back to the primary pseudowire. There is no revertive operation between secondary paths, meaning that the path of the VLL will not be switched back to a secondary pseudowire of higher precedence when the latter comes back up again.
-The 7210 SAS routers support the ability for a user-initiated manual switchover of the VLL path to the primary or any of the secondary be supported to divert user traffic in case of a planned outage, such as in node upgrade procedures.
Dynamic multi-segment pseudowire routing
T-PE functionality is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
S-PE functionality is only supported on 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE.
The following sections describe the end-to-end solution with BGP PW-routing, assuming appropriate platforms are used for various functions.
Dynamic Multi-Segment Pseudowire (MS-PW) routing enables a complete MS-PW to be established, while only requiring per-pseudowire configuration on the T-PEs. No per-pseudowire configuration is required on the S-PEs. End-to-end signaling of the MS-PW is achieved using T-LDP, while multi-protocol BGP is used to advertise the T-PEs, allowing dynamic routing of the MS-PW through the intervening network of S-PEs. Dynamic MS-PWs are described in IETF draft-ietf-pwe3-dynamic-ms-pw-13.txt.
The following figure shows the operation of dynamic MS-PWs.
The FEC 129 Attachment Individual Identifier (AII) type 2 structure shown in the following figure is used to identify each individual pseudowire endpoint.
A four-byte global ID followed by a four-byte prefix and a four-byte attachment circuit ID are used to provide for hierarchical, independent allocation of addresses on a per service provider network basis. The first eight bytes (global ID + prefix) may be used to identify each individual T-PE or S-PE as a loopback Layer 2 address.
This new AII type is mapped into the MS-PW BGP NLRI (a new BGP AFI of L2VPN, and SAFI for network layer reachability information for dynamic MS-PWs. As soon as a new T- PE is configured with a local prefix address of global id:prefix, pseudowire routing will proceed to advertise this new address to all the other T- PEs and S-PEs in the network, as shown in the following figure.
In step 1, a new T-PE (T-PE2) is configured with a local prefix.
Next, in steps 2 to 5, MP-BGP will use the NLRI for the MS-PW routing SAFI to advertise the location of the new T-PE to all the other PEs in the network. Alternatively, static routes may be configured on a per T-PE/S-PE basis to accommodate non-BGP PEs in the solution.
As a result, pseudowire routing tables for all the S-PEs and remote T-PEs are populated with the next hop to be used to reach T-PE2.
VLL services can then be established, as shown in the following figure.
In step 1 and 1', the T-PEs are configured with the local and remote endpoint information, Source AII (SAII), Target AII (TAII). On the 7210 SAS, the AIIs are locally configured for each spoke-SDP, according to the model shown in the following figure. Therefore, the 7210 SAS provides for a flexible mapping of AII to SAP. That is, the values used for the AII are through local configuration, and it is the context of the spoke-SDP that binds it to a specific SAP.
Before T-LDP signaling starts, the two T-PEs determine an active and passive relationship using the highest AII (comparing the configured SAII and TAII) or the configured precedence. Next, the active T-PE (in the IETF draft this is referred to as the source T-PE or ST-PE) checks the PW routing table to determine the next signaling hop for the configured TAII, using the longest match between the TAII and the entries in the PW routing table.
This signaling hop is then used to choose the T-LDP session to the chosen next-hop S-PE. Signaling proceeds through each subsequent S-PE using similar matching procedures to determine the next signaling hop. Otherwise, if a subsequent S-PE does not support dynamic MS-PW routing, and therefore uses a statically configured PW segment, the signaling of individual segments follows the procedures already implemented in the PW switching feature.
BGP can install a PW AII route in the PW routing table with ECMP next hops. However, when LDP needs to signal a PW with matching TAII, it will choose only one next hop from the available ECMP next hops. PW routing supports up to four ECMP paths for each destination.
The signaling of the forward path ends when the PE matches the TAII in the label mapping message with the SAII of a spoke-SDP bound to a local SAP. The signaling in the reverse direction can now be initiated, which follows the entries installed in the forward path. The PW routing tables are not consulted for the reverse path. This ensures that the reverse direction of the PW follows exactly the same set of S-PEs as the forward direction.
This solution can be used in either a MAN-WAN environment or in an inter-AS/inter-provider environment, as shown in the following figure.
Data plane forwarding at the S-PEs uses pseudowire service label switching, as per the pseudowire switching feature.
Pseudowire routing
Each S-PE and T-PE has a pseudowire routing table that contains a reference to the T-LDP session to use to signal to a set of next-hop S-PEs to reach a specific T-PE (or the T-PE if that is the next hop). For VLLs, this table contains aggregated AII type 2 FECs and may be populated with routes that are learned through MP-BGP or that are statically configured.
MP-BGP is used to automatically distribute T-PE prefixes using the new MS-PW NLRI, or static routes can be used. The MS-PW NLRI is composed of a length, an eight-byte RD, a four-byte global ID, a four-byte local prefix, and (optionally) a four-byte AC ID. Support for the MS-PW address family is configured in CLI under config>router>bgp>family ms-pw.
MS-PW routing parameters are configured in the config>service>pw-routing context.
To enable support for dynamic MS-PWs on a 7210 SAS node to be used as a T-PE or S-PE, a single, globally unique, S-PE ID, known as the S-PE address, is first configured under config>service>pw-routing on each 7210 SAS to be used as a T-PE or S-PE. The S-PE address has the format global-id:prefix. It is not possible to configure any local prefixes used for pseudowire routing or to configure spoke-SPDs using dynamic MS-PWs at a T-PE unless an S-PE address has already been configured. The S-PE address is used as the address of a node used to populate the switching point TLV in the LDP label mapping message and the pseudowire status notification sent for faults at the S-PE.
Each T-PE is also be configured with the following parameters:
Global ID
This is a 4-byte identifier that uniquely identifies an operator or the local network.
Local prefix
One or more local (Layer 2) prefixes (up to a maximum of 16), which are formatted in the style of a 4-octet IPv4 address. A local prefix identifies a T-PE or S-PE in the PW routing domain.
For each local prefix, at least one 8-byte route distinguisher can be configured. It is also possible to configure an optional BGP community attribute.
For each local prefix, BGP then advertises each global ID/prefix tuple and unique RD and community pseudowire using the MS-PW NLRI, based on the aggregated FEC129 AII Type 2 and the Layer 2 VPN/PW routing AFI/SAFI 25/6, to each T-PE/S-PE that is a T-LDP neighbor, subject to local BGP policies.
The dynamic advertisement of each of these pseudowire routes is enabled for each prefix and RD, using the advertise-bgp command.
Exporting MS-PW routes in MP-BGP
An export policy is also required to export MS-PW routes in MP-BGP. This can be done using a default policy, such as the following:
*A:lin-123>config>router>policy-options# info
----------------------------------------------
policy-statement "ms-pw"
default-action accept
exit
exit
----------------------------------------------
However, the preceding would export all routes. A recommended choice is to enable filtering per-family, as follows:
*A:lin-123>config>router>policy-options# info
----------------------------------------------
policy-statement "to-mspw"
entry 1
from
family ms-pw
exit
action accept
exit
exit
exit
----------------------------------------------
The following command is then added in the config>router>bgp context:
export "to-mspw"
The local preference for iBGP and BGP communities can be configured under such a policy.
Static routing
In addition to support for BGP routing, static MS-PW routes may also be configured using the config>services>pw-routing>static-route command. Each static route comprises the target T-PE global ID and prefix, and the IP address of the T-LDP session to the next-hop S-PE or T-PE that should be used.
If a static route is set to 0, this represents the default route. If a static route exists to a specific T-PE, this is used in preference to any BGP route that may exist.
Explicit paths
A set of default explicit paths to a remote T-PE or S-PE prefix may be configured on a T-PE under config>services>pw-routing using the path name command. Explicit paths are used to populate the explicit route TLV used by MS-PW T-LDP signaling. Only strict (fully qualified) explicit paths are supported.
Note that it is possible to configure explicit paths independently of the configuration of BGP or static routing.
Configuring VLLs using dynamic MS-PW
One or more spoke-SDPs may be configured for distributed Epipe VLL services. Dynamic MS-PWs use FEC129 (also known as the Generalized ID FEC) with AII type 2 to identify the pseudowire, as opposed to FEC128 (also known as the PW ID FEC) used for traditional single segment pseudowires and for pseudowire switching. FEC129 spoke-SDPs are configured under the spoke-sdp-fec command in the CLI.
FEC129 AII type 2 uses a SAII and a TAII to identify the end of a pseudowire at the T-PE. The SAII identifies the local end, while the TAII identifies the remote end. The SAII and TAII are each structured as follows:
global ID
The global ID is a 4-byte identifier that uniquely identifies an operator or the local network.
prefix
This is 4-byte prefix, which should correspond to one of the local prefixes assigned under pw-routing.
AC ID
The AC ID is a 4-byte identifier for this end of the pseudowire. This should be locally unique within the scope of the global-id:prefix.
Active/passive T-PE selection
Dynamic MS-PWs use single-sided signaling procedures with double-sided configuration; a fully qualified FEC must be configured at both endpoints. That is, one T-PE (the source T-PE: ST-PE) of the MS-PW initiates signaling for the MS-PW, while the other end (the terminating T-PE: TT-PE) passively waits for the label mapping message from the far-end. The TT-PE only responds with a label mapping message to set up the opposite direction of the MS-PW when it receives the label mapping from the ST-PE. By default, the 7210 SAS will determine which T-PE is the ST-PE (the active T-PE) and which is the TT-PE (the passive T-PE) automatically, based on comparing the SAII with the TAII as unsigned integers. The T-PE with SAII>TAII assumes the active role. However, it is possible to override this behavior using the signaling {master | auto} command in the spoke-sdp-fec context. If master is selected at a specific T-PE, it will assume the active role. If a T-PE is at the endpoint of a spoke-SDP that is bound to an VLL SAP, and single-sided autoconfiguration is used, that endpoint is always passive. Therefore, signaling master should only be used when it is known that the far end will assume a passive behavior.
Automatic endpoint configuration
Automatic endpoint configuration allows the configuration of an endpoint without specifying the TAII associated with that spoke-SDP FEC. It allows a single-sided provisioning model where an incoming label mapping message with a TAII that matches the SAII of that spoke-SDP can be automatically bound to that endpoint. This is useful in scenarios where a service provider must separate the service configuration from the service activation phase.
Automatic endpoint configuration is supported and required for Epipe VLL spoke-SDP FEC endpoints bound to a VLL SAP. It is configured using the spoke-sdp-fec auto-config command, and excludes the TAII from the configuration. When autoconfiguration is used, the node assumes passive behavior with regards to T-LDP signaling. Therefore, the far-end T-PE must be configured for signaling master for that spoke-SDP FEC.
Selecting a path for an MS-PW
Path selection for signaling occurs in the outbound direction (ST-PE to TT-PE) for an MS-PW. In the TT-PE to ST-PE direction, a label mapping message follows the reverse of the path of the outgoing label mapping.
A node can use explicit paths, static routes, or BGP routes to select the next hop S-PE or T-PE. The order of preference used in selecting these routes is:
explicit path
static route
BGP route
To use an explicit path for an MS-PW, an explicit path must have been configured in the config>services>pw-routing>path path-name context. The user must then configure the corresponding path path-name in the spoke-sdp-fec context.
If an explicit path name is not configured, the TT-PE or S-PE will perform a longest match lookup for a route (static if it exists, and BGP if not) to the next-hop S-PE or T-PE to reach the TAII.
Pseudowire routing chooses the MS-PW path in terms of the sequence of S-PEs to use to reach a specific T-PE. It does not select the SDP to use on each hop, which is instead determined at signaling time. When a label mapping is sent for a specific pseudowire segment, an LDP SDP will be used to reach the next-hop S-PE/T-PE if such an SDP exists. If not, and an RFC 3107 labeled BGP SDP is available, then that will be used. Otherwise, the label mapping will fail and a label release will be sent.
Pseudowire templates
Dynamic MS-PWs support the use of the pseudowire template for specifying generic pseudowire parameters at the T-PE. The pseudowire template to use is configured in the spoke-sdp-fec>pw-template-bind policy-id context. Dynamic MS-PWs do not support the provisioned SDPs specified in the pseudowire template.
Pseudowire redundancy
Pseudowire redundancy is supported on dynamic MS-PWs used for VLLs. It is configured in a similar manner to pseudowire redundancy on VLLs using FEC128, whereby each spoke-SDP FEC within an endpoint is configured with a unique SAII/TAII.
The following figure shows the use of pseudowire redundancy.
The following is a summary of the key points to consider in using pseudowire redundancy with dynamic MS-PWs:
Each MS-PW in the redundant set must have a unique SAII/TAII set and is signaled separately. The primary pseudowire is configured in the spoke-sdp-fec>primary context.
Each MS-PW in the redundant set should use a diverse path (from the point of view of the S-PEs traversed) from every other MS-PW in that set, if path diversity is possible in a specific network topology. There are a number of possible ways to achieve this:
Configure an explicit path for each MS-PW.
Allow BGP routing to automatically determine diverse paths using BGP policies applied to different local prefixes assigned to the primary and standby MS-PWs.
Provide path diversity for each primary pseudowire through the use of a BGP route distinguisher.
If the primary MS-PW fails, it fails-over to a standby MS-PW, as per the normal pseudowire redundancy procedures. A configurable retry timer for the failed primary MS-PW is then started. When the timer expires, it attempts to reestablish the primary MS-PW using its original path, up to a maximum number of attempts as per the retry count parameter. The T-PE may then optionally revert to the primary MS-PW on successful reestablishment.
Because the SDP ID is determined dynamically at signaling time, it cannot be used as a tie breaker to choose the primary MS-PW between multiple MS-PWs of the same precedence. The user should therefore explicitly configure the precedence values to determine which MS-PW is active in the final selection.
VCCV OAM for dynamic MS-PWs
The primary difference between dynamic MS-PWs and those using FEC128 is support for FEC129 AII type 2. As in PW switching, VCCV on dynamic MS-PWs requires the use of the VCCV control word on the pseudowire. Both the vccv-ping and vccv-trace commands support dynamic MS-PWs.
VCCV-Ping on dynamic MS-PWs
VCCV-ping supports the use of FEC129 AII type 2 in the target FEC stack of the ping echo request message. The FEC to use in the echo request message is derived in one of two ways: either the user can explicitly specify the SAII and TAII to use, or the user can specify only the spoke-sdp-fec-id of the MS-PW in the vccv-ping command.
If the SAII:TAII is entered by the user in the vccv-ping command, those values are used for the VCCV-ping echo request. However, their order is reversed before being sent, so that they match the order for the downstream FEC element for an S-PE, or the locally configured SAII:TAII for a remote T-PE of that MS-PW.
If SAII:TAII is entered in addition to the spoke-sdp-fec-id, the system will verify the entered values against the values stored in the context for that spoke-sdp-fec-id.
If the SAII:TAII to use in the target FEC stack of the VCCV-ping message is not entered by the user, and if a switching point TLV was received in the initial label mapping message for the reverse direction of the MS-PW (with respect to the sending PE), the SAII:TAII to use in the target FEC stack of the VCCV-ping echo request message is derived by parsing that TLV based on the user-specified TTL (or a TTL of 255 if none is specified). In this case, the order of the SAII:TAII in the switching point TLV is maintained for the VCCV-ping echo request message.
If no pseudowire switching point TLV was received, the SAII:TAII values to use for the VCCV-ping echo request are derived from the MS-PW context, but their order is reversed before being sent, so that they match the order for the downstream FEC element for an S-PE, or the locally configured SAII:TAII for a remote T-PE of that MS-PW.
The use of spoke-sdp-fec-id in vccv-ping is only applicable at T-PE nodes, because it is not configured for a specific MS-PW at S-PE nodes.
VCCV-Trace on dynamic MS-PWs
The 7210 SAS supports the MS-PW path trace mode of operation for VCCV-trace, as per pseudowire switching, but using FEC129 AII type 2. As in the case of VCCV-ping, the SAII:TAII used in the VCCV-trace echo request message sent from the T-PE or S-PE, from which the vccv-trace command is executed, is specified by the user or derived from the context of the MS-PW.
The use of spoke-sdp-fec-id in vccv-trace is only applicable at T-PE nodes, since it is not configured for a specific MS-PW at S-PE nodes
Example dynamic MS-PW configuration
The following figure shows how to configure dynamic MS-PWs for a VLL service between a set of 7210 SAS nodes. The network consists of two 7210 T-PEs and two 7210 SAS nodes in the role of S-PEs. Each 7210 SAS peers with its neighbor using LDP and BGP.
This example uses BGP to route dynamic MS-PWs and T-LDP to signal them. Therefore, each node must be configured to support the MS-PW address family under BGP, and BGP and LDP peerings must be established between the T-PEs/S-PEs. The appropriate BGP export policies must also be configured.
Finally, pseudowire routing must be configured on each node. This includes an S-PE address for every participating node, and one or more local prefixes on the T-PEs. MS-PW paths and static routes may also be configured. When this routing and signaling infrastructure is established, spoke-SDP FECs can be configured on each of the T-PEs.
Sample configuration for T-PE1
The following is a sample configuration for T-PE1.
config
router
ldp
targeted-session
peer 10.20.1.5
exit
exit
policy-options
begin
policy-statement "exportMsPw"
entry 10
from
family ms-pw
exit
action accept
exit
exit
exit
commit
exit
bgp
family ms-pw
connect-retry 1
min-route-advertisement 1
export "exportMsPw"
rapid-withdrawal
group "ebgp"
neighbor 10.20.1.5
multihop 255
peer-as 200
exit
exit
exit
config
service
pw-routing
spe-address 3:10.20.1.3
local-prefix 3:10.20.1.3 create
exit
path "path1_to_F" create
hop 1 10.20.1.5
hop 2 10.20.1.2
no shutdown
exit
exit
epipe 1 customer 1 vpn 1 create
description "Default epipe
description for service id 1"
service-mtu 1400
service-name "XYZ Epipe 1"
sap 2/1/1:1 create
exit
spoke-sdp-fec 1 fec 129 aii-type 2 create
retry-timer 10
retry-count 10
saii-type2 3:10.20.1.3:1
taii-type2 6:10.20.1.6:1
no shutdown
exit
no shutdown
exit
Sample configuration for T-PE2
The following is a sample configuration for T-PE2.
config
router
ldp
targeted-session
peer 10.20.1.2
exit
exit
…
policy-options
begin
policy-statement "exportMsPw"
entry 10
from
family ms-pw
exit
action accept
exit
exit
exit
commit
exit
bgp
family ms-pw
connect-retry 1
min-route-advertisement 1
export "exportMsPw"
rapid-withdrawal
group "ebgp"
neighbor 10.20.1.2
multihop 255
peer-as 300
exit
exit
exit
config
service
pw-routing
spe-address 6:10.20.1.6
local-prefix 6:10.20.1.6 create
exit
path "path1_to_F" create
hop 1 10.20.1.2
hop 2 10.20.1.5
no shutdown
exit
exit
epipe 1 customer 1 vpn 1 create
description "Default epipe
description for service id 1"
service-mtu 1400
service-name "XYZ Epipe 1"
sap 1/1/3:1 create
exit
spoke-sdp-fec 1 fec 129 aii-type 2 create
retry-timer 10
retry-count 10
saii-type2 6:10.20.1.6:1
taii-type2 3:10.20.1.3:1
no shutdown
exit
no shutdown
exit
Sample configuration for S-PE1
The following is a sample configuration for S-PE1.
config
router
ldp
targeted-session
peer 10.20.1.3
exit
peer 10.20.1.2
exit
exit
…
bgp
family ms-pw
connect-retry 1
min-route-advertisement 1
rapid-withdrawal
group "ebgp"
neighbor 10.20.1.2
multihop 255
peer-as 300
exit
neighbor 10.20.1.3
multihop 255
peer-as 100
exit
exit
exit
service
pw-routing
spe-address 5:10.20.1.5
exit
Sample configuration for S-PE2
The following is a sample configuration for S-PE2.
config
router
ldp
targeted-session
peer 10.20.1.5
exit
peer 10.20.1.6
exit
exit
…
bgp
family ms-pw
connect-retry 1
min-route-advertisement 1
rapid-withdrawal
group "ebgp"
neighbor 10.20.1.5
multihop 255
peer-as 200
exit
neighbor 10.20.1.6
multihop 255
peer-as 400
exit
exit
exit
service
pw-routing
spe-address 2:10.20.1.2
exit
Master-slave operation
The standby-signaling-master command is supported on all 7210 SAS platforms as described in this document, except for those operating in access-uplink mode. The standby-signaling-slave command is not supported. In the following section, references to the standby-signaling-slave command are only used to describe the complete solution. The 7210 SAS platforms can only be used where the standby-signaling-master command is used in the example.
This section describes a mechanism in which one end on a pseudowire (the ‟master”) dictates the active PW selection, which is followed by the other end of the PW (the ‟slave”). This mechanism and associated terminology is specified in RFC 6870.
This section describes master-slave pseudowire redundancy. This redundancy adds the ability for the remote peer to react to the pseudowire standby status notification, even if only one spoke-SDP terminates on the VLL endpoint on the remote peer, by blocking the transmit (Tx) direction of a VLL spoke-SDP when the far-end PE signals standby. This solution enables the blocking of the Tx direction of a VLL spoke-SDP at both master and slave endpoints when standby is signalled by the master endpoint. This satisfies a majority of deployments where bidirectional blocking of the forwarding on a standby spoke-SDP is required.
The following figure shows the operation of master-slave pseudowire redundancy. In this scenario, an Epipe service is provided between CE1 and CE2. CE2 is dual-homed to PE2 and PE3, and therefore PE1 is dual-homed to PE2 and PE3 using Epipe spoke-SDPs. The objective of this feature is to ensure that only one pseudowire is used for forwarding in both directions by PE1, PE2, and PE3, in the absence of a native dual homing protocol between CE2 and PE2/PE3, such as MC-LAG. In normal operating conditions (the SAPs on PE2 and PE3 toward CE2 are both up and there are no defects on the ACs to CE2), PE2 and PE3 cannot choose which spoke-SDP to forward on based on the status of the AC redundancy protocol.
Master-slave pseudowire redundancy adds the ability for the remote peer to react to the pseudowire standby status notification, even if only one spoke-SDP terminates on the VLL endpoint on the remote peer. When the CLI command standby-signaling-slave is enabled at the spoke-SDP or explicit endpoint level in PE2 and PE3, any spoke-SDP for which the remote peer signals PW FWD standby will be blocked in the transmit direction.
This is achieved as follows. The standby-signaling-master state is activated on the VLL endpoint in PE1. In this case, a spoke-SDP is blocked in the transmit direction at this master endpoint if it is either in operDown state, or it has lower precedence than the highest precedence spoke-SDP, or the specific peer PE signals one of the following pseudowire status bits:
pseudowire not forwarding (0x01)
SAP (ingress) receive fault (0x02)
SAP (egress) transmit fault (0x04)
SDP binding (ingress) receive fault (0x08)
SDP binding (egress) transmit fault (0x10)
That the specific spoke-SDP has been blocked will be signaled to the LDP peer through the pseudowire status bit (PW FWD standby (0x20)). This will prevent traffic being sent over this spoke-SDP by the remote peer, but only in case that remote peer supports and reacts to pseudowire status notification. Previously, this applied only if the spoke-SDP terminated on an IES, VPRN, or VPLS.
Note that although master-slave operation provides bidirectional blocking of a standby spoke-SDP during steady-state conditions, it is possible that the Tx directions of more than one slave endpoint can be active for transient periods during a fail-over operation. This is because of slave endpoints transitioning a spoke-SDP from standby to active receiving and processing a pseudowire preferential forwarding status message before those transitioning a spoke-SDP to standby.
This transient condition is most likely when a forced switch-over is performed, or the relative preferences of the spoke-SDPs are changed, or the active spoke-SDP is shutdown at the master endpoint. During this period, loops of unknown traffic may be observed. Fail-overs because of common network faults that can occur during normal operation, or a failure of connectivity on the path of the spoke-SDP or the SAP, would not result in such loops in the datapath.
Operation of master-slave pseudowire redundancy with existing scenarios
This section describes how master-slave pseudowire redundancy could operate.
VLL resilience path
The following figure shows a VLL resilience path example. An sample configuration follows.
A revert-time value of zero (default) means that the VLL path will be switched back to the primary immediately after it comes back up.
Sample configuration for PE1
The following is a sample configuration for PE1.
configure service epipe 1
endpoint X
exit
endpoint Y
revert-time 0
standby-signaling-master
exit
sap 1/1/1:100 endpoint X
spoke-sdp 1:100 endpoint Y
precedence primary
spoke-sdp 2:200 endpoint Y
precedence 1
Sample configuration for PE2
The following is a sample configuration for PE2.
configure service epipe 1
endpoint X
exit
sap 2/2/2:200 endpoint X
spoke-sdp 1:100
standby-signaling-slave
Sample configuration for PE3
The following is a sample configuration for PE3.
configure service epipe 1
endpoint X
exit
sap 3/3/3:300 endpoint X
spoke-sdp 2:200
standby-signaling-slave
VLL resilience for a switched PW path
T-PE functionality is supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
S-PE functionality is only supported on 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE, and 7210 SAS-Sx 10/100GE.
The following figure shows VLL resilience for a switched pseudowire path example. A sample configuration follows.
Sample configuration of T-PE1
The following is a sample configuration of T-PE1.
configure service epipe 1
endpoint X
exit
endpoint Y
revert-time 100
standby-signaling-master
exit
sap 1/1/1:100 endpoint X
spoke-sdp 1:100 endpoint Y
precedence primary
spoke-sdp 2:200 endpoint Y
precedence 1
spoke-sdp 3:300 endpoint Y
precedence 1
Sample configuration of T-PE2
The following is a sample configuration of T-PE2.
configure service epipe 1
endpoint X
exit
endpoint Y
revert-time 100
standby-signaling-slave
exit
sap 2/2/2:200 endpoint X
spoke-sdp 4:400 endpoint Y
precedence primary
spoke-sdp 5:500 endpoint Y
precedence 1
spoke-sdp 6:600 endpoint Y
precedence 1
VC switching indicates a VC cross-connect so that the service manager does not signal the VC label mapping immediately, but will put this into passive mode.
Sample configuration of S-PE1
The following is a sample configuration of S-PE1.
configure service epipe 1 vc-switching
spoke-sdp 1:100
spoke-sdp 4:400
Access mode resilience Using MC-LAG and pseudowire redundancy
The following figure shows the use of both Multi-Chassis Link Aggregation (MC-LAG) in the access network and pseudowire redundancy in the core network to provide a resilient end-to-end VLL service to the customers.
In this application, a pseudowire status bit of active or standby indicates the status of the SAP in the MC-LAG instance in the 7210 SAS aggregation node. All spoke-SDPs are of secondary type and there is no use of a primary pseudowire type in this mode of operation.
Node A is in the active state according to its local MC-LAG instance, and therefore advertises active status notification messages to both its peer pseudowire nodes; for example, nodes C and D. Node D performs the same operation. Node B is in the standby state according to the status of the SAP in its local MC-LAG instance, and therefore advertises standby status notification messages to both nodes C and D. Node C performs the same operation.
The 7210 SAS node selects a pseudowire as the active path for forwarding packets when both the local pseudowire status and the received remote pseudowire status indicate active status. However, a 7210 SAS device in standby status according to the SAP in its local MC-LAG instance is capable of processing packets for a VLL service received over any of the pseudowires that are up. This is to avoid black holing of user traffic during transitions.
The 7210 SAS standby node forwards these packets to the active node via the Inter-Chassis Backup (ICB) pseudowire for this VLL service. An ICB is a spoke-SDP used by an MC-LAG node to back up an MC-LAG SAP during transitions. The same ICB can also be used by the peer MC-LAG node to protect against network failures causing the active pseudowire to go down.
Note that at configuration time, the user specifies a precedence parameter for each of the pseudowires that are part of the redundancy set as described in the application. A 7210 SAS node uses this to select which pseudowire to forward packet to in case both pseudowires show active/active for the local/remote status during transitions.
Only VLL service of type Epipe is supported in this application. Also, ICB spoke-SDP can only be added to the SAP side of the VLL cross-connect if the SAP is configured on a MC-LAG instance.
VLL resilience for a switched pseudowire path
The following figure shows the use of both pseudowire redundancy and pseudowire switching to provide a resilient VLL service across multiple IGP areas in a provider network.
Pseudowire switching is a method for scaling a large network of VLL or VPLS services by removing the need for a full mesh of T-LDP sessions between the PE nodes as the number of these nodes grows over time.
As in the application in VLL resilience for a switched pseudowire path, the T-PE1 node switches the path of a VLL to a secondary standby pseudowire, in the case of a network-side failure causing the VLL binding status to be down or if T-PE2 notified it that the remote SAP went down. This application requires that pseudowire status notification messages generated by either a T-PE node or a S-PE node be processed and relayed by the S-PE nodes.
It is possible that the secondary pseudowire path terminates on the same target PE as the primary; for example, T-PE2. This provides protection against network-side failures, but not against a remote SAP failure.
When the target destination PE for the primary and secondary pseudowires is the same, T-PE1 will usually not switch the VLL path onto the secondary pseudowire upon receipt of a pseudowire status notification indicating that the remote SAP is down. This occurs because the status notification is sent over both the primary and secondary pseudowires. However, the status notification on the primary pseudowire may arrive earlier than the one on the secondary pseudowire because of the differential delay between the paths. This will cause T-PE1 to switch the path of the VLL to the secondary standby pseudowire and remain there until the status notification is cleared. At that time, the VLL path is switched back to the primary pseudowire because of the revertive behavior operation. The path will not switch back to a secondary path when it comes up, even if it has a higher precedence than the currently active secondary path.
Pseudowire redundancy service models
This section describes the various MC-LAG and pseudowire redundancy scenarios, and the algorithm used to select the active transmit object in a VLL endpoint.
Redundant VLL service model
To implement pseudowire redundancy, a VLL service accommodates more than a single object on the SAP side and on the spoke-SDP side. The following figure shows the model for a redundant VLL service based on the concept of endpoints.
A VLL service supports, by default, two implicit endpoints managed internally by the system. Each endpoint can only have one object: a SAP or a spoke-SDP.
To add more objects, up to two explicitly named endpoints may be created per VLL service. The endpoint name is locally significant to the VLL service. They are referred to as endpoint X and endpoint Y as shown in the preceding figure.
The preceding figure is only an example and the Y endpoint can also have a SAP and/or an ICB spoke-SDP. The following describes the four types of endpoint objects supported and the rules used when associating them with an endpoint of a VLL service:
SAP
There can only be a maximum of one SAP per VLL endpoint.
primary spoke-SDP
The VLL service always uses this pseudowire and only switches to a secondary pseudowire when it is down. The VLL service switches the path to the primary pseudowire when it is back up. The user can configure a timer to delay reverting back to primary or to never revert. There can only be a maximum of one primary spoke-SDP per VLL endpoint.
secondary spoke-SDP
There can be a maximum of four secondary spoke-SDPs per endpoint. The user can configure the precedence of a secondary pseudowire to indicate the order in which a secondary pseudowire is activated.
inter-chassis backup (ICB) spoke-SDP
This is a special pseudowire used for MC-LAG and pseudowire redundancy applications. Forwarding between ICBs is blocked on the same node. The user has to explicitly indicate that the spoke-SDP is an ICB at creation time. There are a few scenarios, as follows, where the user can configure the spoke-SDP as an ICB or as a regular spoke-SDP on a specific node. The CLI for those cases will indicate both options.
A VLL service endpoint can only use one active object to transmit at a time, but can receive from all endpoint objects.
An explicitly named endpoint can have a maximum of one SAP and one ICB. When a SAP is added to the endpoint, only one more object of type ICB spoke-SDP is allowed. The ICB spoke-SDP cannot be added to the endpoint if the SAP is not part of a MC-LAG instance. A SAP that is not part of a MC-LAG instance cannot be added to an endpoint that already has an ICB spoke-SDP.
An explicitly named endpoint, which does not have a SAP object, can have a maximum of four spoke-SDPs and can include any of the following:
a single primary spoke-SDP
one or many secondary spoke-SDPs with precedence
a single ICB spoke-SDP
T-LDP status notification handling rules
Using Redundant VLL endpoint objects as a reference, the following are the rules for generating, processing, and merging T-LDP status notifications in VLL service with endpoints. Note that any allowed combination of objects as specified in Redundant VLL service model can be used on endpoints ‟X” and ‟Y”. The following sections refer to the specific combination objects in Redundant VLL endpoint objects as an example to describe the more general rules.
Processing endpoint SAP active/standby status bits
The advertised admin forwarding status of active/standby reflects the status of the local LAG SAP in the MC-LAG application. If the SAP is not part of a MC-LAG instance, the forwarding status of active is always advertised.
When the SAP in endpoint ‟X” is part of a MC-LAG instance, a node must send the T-LDP forwarding status bit of ‟SAP active/standby” over all ‟Y” endpoint spoke-SDPs, except the ICB spoke-SDP, whenever this status changes. The status bit sent over the ICB is always zero (active by default).
When the SAP in endpoint ‟X” is not part of a MC-LAG instance, the forwarding status sent over all ‟Y” endpoint spoke-SDPs should always be set to zero (active by default).
Processing and merging
Endpoint X is operationally up if at least one of its objects is operationally up. It is down if all its objects are operationally down.
If the SAP in endpoint X transitions locally to the down state, or receives a SAP down notification by SAP-specific OAM signal, the node must send T-LDP SAP down status bits on the Y endpoint ICB spoke-SDP only.
The Ethernet SAP does not support the SAP OAM protocol. All other SAP types cannot exist on the same endpoint as an ICB spoke-SDP because a non-Ethernet SAP cannot be part of an MC-LAG instance.
If the ICB spoke-SDP in endpoint X transitions locally to the down state, the node must send T-LDP SDP-binding down status bits on this spoke-SDP.
If the ICB spoke-SDP in endpoint X receives T-LDP SDP-binding down status bits or pseudowire not forwarding status bits, the node saves this status and takes no further action. The saved status is used for selecting the active transmit endpoint object.
If all objects in endpoint X have any of the following happen, the node must send status bits of SAP down over all Y endpoint spoke-SDPs, including the ICB:
transition locally to down state
receive a SAP down notification by remote T-LDP status bits or by SAP-specific OAM signal
receive status bits of SDP-binding down
receive status bits of pseudowire not forwarding
Endpoint Y is operationally up if at least one of its objects is operationally up. It is down if all its objects are operationally down.
If a spoke-SDP in endpoint Y, including the ICB spoke-SDP, transitions locally to down state, the node must send T-LDP SDP-binding down status bits on this spoke-SDP.
If a spoke-SDP in endpoint Y, including the ICB spoke-SDP, receive any of the following, the node saves this status and takes no further action:
T-LDP SAP down status bits
T-LDP SDP-binding down status bits
status bits of pseudowire not forwarding
The saved status is used for selecting the active transmit endpoint object.
If all objects in endpoint Y, except the ICB spoke-SDP, have any of the following happen, the node must send status bits of SDP-binding down over the X endpoint ICB spoke-SDP only:
transition locally to down state
receive T-LDP SAP down status bits
receive T-LDP SDP-binding down status bits
receive status bits of pseudowire not forwarding
If all objects in endpoint Y have any of the following happen, the node must send status bits of the SDP-binding down over the X endpoint ICB spoke-SDP, and must send a SAP down notification on the X endpoint SAP by the SAP-specific OAM signal, if applicable:
transition locally to down state
receive T-LDP SAP down status bits
receive T-LDP SDP-binding down status bits
receive status bits of pseudowire not forwarding
An Ethernet SAP does not support signaling status notifications.
Epipe configuration for MPLS-TP
MPLS-TP PWs are supported in Epipe services.
MPLS-TP is only supported on 7210 SAS-T operating in the network mode.
The following subsections describe how SDPs and spoke-SDPs are used with MPLS-TP LSPs and static PWs with MPLS-TP OAM.
SDPs
An SDP used for MPLS-TP supports the configuration of an MPLS-TP identifier as the far-end address, as an alternative to an IP address. MPLS-TP node identifiers are used if MPLS-TP tunnels are used. IP addresses are used if IP/MPLS LSPs are used by the SDP, or MPLS-TP tunnels identified by IPv4 source or destination addresses.
The following syntax shows the MPLS-TP options:
config
service
sdp
no description
network-domain "default"
signaling off
far-end node-id 0.0.0.43 global-id 4294967295
no mixed-lsp-mode
no ldp
no bgp-tunnel
lsp "unnumberedLSP"
no vlan-vc-etype
no pbb-etype
no path-mtu
no adv-mtu-override
keep-alive
shutdown
hello-time 10
hold-down-time 10
max-drop-count 3
timeout 5
no message-length
exit
no metric
no collect-stats
no accounting-policy
binding
no port
exit
no shutdown
----------------------------------------------
*A:7210SAS>config>service>sdp#
The far-end node-id ip-address global-id global-id command is used to associate an SDP far end with an MPLS-TP tunnel whose far-end address is an MPLS-TP node ID. If the SDP is associated with an RSVP-TE LSP, the far end must be a routable IPv4 address.
The system accepts the node-id being entered in either 4-octet IP address format <a.b.c.d> or unsigned integer format.
The SDP far end refers to an MPLS-TP node-id or global-id only if:
delivery type is MPLS
signaling is off
keep-alive is disabled
mixed-lsp-mode is disabled
adv-mtu-override is disabled
An LSP will only be allowed to be configured if the far-end info matches the LSP far-end info (whether MPLS-TP or RSVP):
Only one LSP is allowed if the far end is an MPLS-TP node-id or global-id.
MPLS-TP or RSVP-TE LSPs are supported. However, note that LDP and BGP LSPs are not blocked in CLI.
Signaling TLDP or BGP is blocked if:
far-end node-id or global-id is configured
control-channel-status is enabled on any spoke-SDP (or mate VC-switched spoke)
pw-path-id is configured on any spoke-SDP (or mate VC-switched spoke)
The following commands are blocked if a far-end node-id or global-id is configured:
class-forwarding
tunnel-far-end
mixed-lsp-mode
keep-alive
LDP or BGP-tunnel
adv-mtu-override
VLL spoke-SDP configuration
The 7210 SAS-T can only be a T-PE. MPLS-TP OAM related commands are applicable to spoke-SDPs configured under all services supported by MPLS-TP pseudowires. All commands and functions that are applicable to spoke-SDPs in the current implementation are supported, except for those that explicitly depend on an LDP session on the SDP or as described in this section. Likewise, all existing functions on a specific service SAP are supported if the spoke-SDPs that it are matched to is MPLS-TP.
The following describes how to configure MPLS-TP on an Epipe VLL. However, similar configuration applies to other VLL types.
A spoke-SDP bound to an SDP with the mpls-tp keyword cannot be no shutdown unless the ingress label, the egress label, the control word, and the PW path ID are configured, as follows:
*7210SAS>config>service>epipe# info
----------------------------------------------
sap 1/1/10:1.111 create
exit
spoke-sdp 1:111 create
[no] hash-label ingress
vc-label 2111
exit
egress
vc-label 2111
exit
control-word
pw-path-id
agi 0:111
saii-type2 4294967295:0.0.0.42:111
taii-type2 4294967295:0.0.0.43:111
exit
no shutdown
exit
no shutdown
----------------------------------------------
*7210SAS>config>service>epipe#
The pw-path-id context is used to configure the end-to-end identifiers for a MS-PW. These may not coincide with those for the local node if the configuration is at an S-PE. The SAII and TAII are consistent with the source and destination of a label mapping message for a signaled PW.
The control-channel-status command enables static PW status signaling. This is valid for any spoke-SDP where signaling none is configured on the SDP (for example, where T-LDP signaling is not in use). The refresh timer is specified in seconds, from 10 to 65535, with a default of 0 (off). This value can only be changed if control-channel-status is shutdown.
Commands that rely on PW status signaling are allowed if control-channel-status is configured for a spoke-SDP bound to an SDP with signaling off, but the system will use control channel status signaling rather than T-LDP status signaling. The ability to configure control channel status signaling on a specific spoke-SDP is determined by the credit-based algorithm described in Credit-based algorithm. The control-channel-status configuration for a particular PW only counts against the credit-based algorithm if it is in a no shutdown state and has a non-zero refresh timer.
Shutdown of a service will cause the static PW status bits for the corresponding PW to be set.
The spoke-SDP is held down unless the pw-path-id is complete.
The system accepts the node-id of the pw-path-id SAII or TAII being entered in either 4-octet IP address format <a.b.c.d> or unsigned integer format.
The control-word must be enabled to use MPLS-TP on a spoke-SDP.
The pw-path-id is only configurable if all of the following is true:
network mode D
SDP signaling is off
control-word is enabled (control-word is disabled by default)
service type Epipe or VPLS
mate SDP signaling is off for VC-switched services
an MPLS-TP node-id or global-id is configured under the config>router>mpls>mpls-tp context; this is required for OAM to provide a reply address
In the vc-switching case, if configured on a mate spoke-SDP, the TAII of the spoke-SDP must match the SAII of its mate, and SAII of spoke-SDP has to match the TAII of its mate.
A control-channel-status no shutdown is only allowed if all of the following is true:
network mode D
SDP signaling is off
control-word is enabled (control-word is disabled by default)
the service type is Epipe or VPLS interface
mate SDP signaling is off (in VC-switched services)
pw-status-signaling is enabled
pw-path-id is configured for this spoke
The hash-label option is only configurable if SDP far-end is not the node-id or global-id.
The control channel status request mechanism is enabled when the request-timer timer parameter is non-zero. When enabled, this overrides the normal RFC-compliant refresh timer behavior. The refresh timer value in the status packet defined in RFC 6478 is always set to zero.
The refresh timer in the sending node is taken from the request timer. The two mechanisms are not compatible with each other. One node sends a request timer while the other is configured for a refresh timer. In a specific node, the request timer can only be configured with both acknowledgment and refresh timers disabled.
When configured, the following procedures are used instead of the RFC 6478 procedures when a PW status changes.
Use the following syntax to configure control channel status requests:
[no] control-channel-status
[no] refresh-timer <value> //0,10-65535, default:0
[no] request-timer
[timeout-multiplier <value>]
[no] shutdown
exit
request-timer <timer1>: 0, 10-65535, defaults: 0.
This parameter determines the interval at which PW status messages, including a reliable delivery TLV, with the request bit set are sent. This cannot be enabled if refresh-timer is not equal to 0. retry-timer: 3-60s.
This parameter determines the timeout interval if no response to a PW status is received. This defaults to 0 when no retry-timer. timeout-multiplier <value> - 3-15.
If a requesting node does not hear back after the retry-timer value times the multiplier value, the node must assume that the peer is down. This defaults to zero (0) when no retry-timer.
Credit-based algorithm
To constrain the CPU resources consumed processing control channel status messages, the system should implement a credit-based mechanism. If a user enables control channel status on a PW[n], a specific number of credits (c_n) are consumed from a CPM-wide pool of max_credit credits. The number of credits consumed is inversely proportional to the configured refresh timer (the first three messages at 1 s intervals do not count against the credit). If the current_credit <= 0, the control channel status signaling cannot be configured on a PW (but the PW can still be configured, and no shutdown).
The following is an example algorithm:
If refresh timer > 0, c_n = 65535 / refresh_timer
Else c_n = 0.
For n=1, current_credit[n] = max_credits – c_n
Else current_credit [n] = current_credit [n-1] – c_n
By default, if a PE with a non-zero refresh timer configured does not receive control channel status refresh messages for 3.5 times the specified timer value, the PE will time out and assume a PW status of zero. A proprietary optional extension to the [RFC6478] protocol should be implemented to enable a node to resolve such a stale PW status condition by requesting the status from the far-end node in specific cases.
VLAN range for SAPs in an Epipe service
The 7210 SAS VLAN ranges provide a mechanism to group a range of VLAN IDs as a single service entity. This allows the operator to provide the service treatment (forwarding, ACL, QoS, accounting, and others) to the group of VLAN IDs as a whole.
Grouping a range of VLAN IDs to a SAP is supported only for Virtual Leased Line (VLL) Ethernet services.
Processing behavior for SAPs using VLAN ranges in access-uplink mode
The access SAPs that specify VLAN range values using connection profile (also known as dot1q range SAPs) are allowed in Epipe service and in VPLS service. For more information about functionality supported, see VLAN range SAPs feature support and restrictions. The system allows one range SAP in an Epipe service, and fails any attempt to configure more than one. Range SAPs can only be configured on access ports. The other endpoint in the Epipe service has to be a Q.* SAP in access-uplink mode. The processing and forwarding behavior for packets received on range SAPs are listed as follows:
No VLAN tags are removed/stripped on ingress of an access dot1q SAP configured to use VLAN ranges. A single tag (Q1) is added to the frame when it is forwarded out of the Q1.* access-uplink SAP.
When a packet is received on the access-uplink Q1.* SAP, the outermost tag is removed and the packet is forwarded out of the access dot1q range SAP. The system does not check if the inner VLAN tag matches the VLANs IDs (both range and individual values specified in the connection profile) of the dot1q access SAPs configured in the service.
The dot1q range SAP can be supported in a service with svc-sap-type set to dot1q-range.
VLAN range SAPs feature support and restrictions
The following restrictions apply to VLAN range SAPs:
The access SAPs that specify VLAN range values (using the connection profile) are only allowed in an Epipe service. The system allows only one range SAP in an Epipe service, and fails any attempt to configure more than one. Range SAPs can only be configured on access ports.
In access-uplink mode, the dot1q range SAP is only allowed to be configured in a service with svc-sap-type set to dot1q-range. In network mode, the dot1q range SAP is allowed to be configured in a service with svc-sap-type set to any.
The access SAPs using VLAN range values are only allowed for dot1q encapsulation ports or LAGs. A connection profile is used to specify either range of VLAN IDs or individual VLANs to be grouped together in a single SAP.
A connection profile is used to specify either range of VLAN IDs or individual VLANs to be grouped together in a single SAP.
Multiple connection profiles can be used per port or LAG, as long as the VLAN value specified by each of them does not overlap. The number of VLAN ranges available per port/LAG is limited. The available number must be shared among all the SAPs on the port/LAG.
The connection profile associated with a SAP cannot be modified. To modify a connection profile, it must be removed from all SAPs that are using it.
Processing behavior for SAPs using VLAN ranges in network operating mode
The access SAPs that specify VLAN range values (using the connection profile) are only allowed in an Epipe service. The system allows only one range SAP in an Epipe service, and fails any attempt to configure more than one. Range SAPs can only be configured on access ports. The other endpoint in the Epipe service has to be a Q.* access SAP or a spoke-SDP (PW) in network mode.
The spoke-SDP processing and forwarding behavior for packets received on range SAPs are as follows:
No VLAN tags are removed/stripped on ingress of the access dot1q SAPs using VLAN range connection profile.
When the other endpoint in the service is configured to be an Q1.* access SAP, 7210 adds another tag to the packet and forwards it out of that SAP.
If the other endpoint in the service is configured to be a spoke-SDP whose vc-type is set to vc-ether, the 7210 SAS adds the appropriate MPLS PW and LSP encapsulations and forwards it out of the SDP.
In the reverse direction, when the other endpoint is a Q1.* SAP and a packet is received on it, the 7210 SAS removes the outermost VLAN tag and forwards the packet out of the access dot1q SAP using VLAN ranges.
When the other endpoint is a spoke-SDP (whose vc-type is set to vc-ether), the 7210 SAS removes the MPLS PW and LSP encapsulation and forwards the packet out of the access dot1q SAP using VLAN ranges.
The system does not check if the VLAN in the packet matches the VLAN IDs of the dot1q access SAPs configured in the service.
ACLs, QoS, hardware, accounting, and mirroring are supported as follows:
For ACLs, filter policies are supported on SAP ingress. In 7210 SAS-T operating in access-uplink mode, IP criteria and MAC criteria-based filter policy is supported with access SAPs.
For more information about ACLs on range SAPs, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide.
In 7210 SAS devices operating in network mode, only MAC criteria-based filter policy is supported with access SAPs.
For more information about ACLs on range SAPs, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide.
For QoS, ingress classification and hierarchical metering are supported for SAP ingress. On the 7210 SAS-T, egress per port queues and shaping are supported. On the 7210 SAS-Mxp, egress per SAP queues and shaping are supported:
SAP ingress classification criteria that is available for use with VLAN range SAPs is similar to that available for other SAPs supported in an Epipe service. Dot1p-based ingress classification uses the dot1p bits in the outermost VLAN tag for matching. On access egress, dot1p received from the SDP (on a network port) from another access port is preserved.
The amount of hardware resources (such as CAM entries used for matching in QoS classification and ACL matching, meters used in SAP ingress policy, and others), consumed by a single range SAP, are equivalent to the amount of resources consumed by a single SAP that specifies a single VLAN ID for service identification. That is, the hardware has the ability to match a range of VLAN values, and therefore uses X resources for a SAP using a VLAN range, instead of X✕n, where n is the number of VLANs specified in the range and X is the amount of QoS or ACL resources needed.
Ingress accounting support is similar to the support available for other SAPs in an Epipe service. The count of packets or octets received from individual VLANs configured in the connection profile is not available. No support for Egress SAP statistics and accounting is available.
Mirroring is supported. In network mode, the use of service resiliency mechanisms, such as MC-LAG and Epipe PW redundancy, is supported.
VLL service considerations
This section describes various general service features and any special capabilities or considerations as they relate to VLL services.
SDPs
The most basic SDPs must have the following:
locally unique SDP identification (ID) number
system IP address of the originating and far-end routers
SDP encapsulation type, MPLS
SAP encapsulations
The Epipe service is designed to carry Ethernet frame payloads, so it can provide connectivity between any two SAPs that pass Ethernet frames. The following SAP encapsulations are supported on the Epipe service:
Ethernet null
Ethernet dot1q
QinQ
While different encapsulation types can be used, encapsulation mismatch can occur if the encapsulation behavior is not understood by connecting devices and they are unable to send and receive the expected traffic. For example, if the encapsulation type on one side of the Epipe is dot1q and the other is null, tagged traffic received on the null SAP will potentially be double tagged when it is transmitted out of the dot1q SAP.
QoS policies
The following QoS policies can be applied to an Epipe service:
traffic management
Traffic management of Ethernet VLLs is achieved through the application of ingress QoS policies to SAPs and access egress QoS policies applied to the port. All traffic management is forwarding-class aware, and the SAP ingress QoS policy identifies the forwarding class based on the rules configured to isolate and match the traffic ingressing on the SAP. Forwarding classes are determined based on the Layer 2 (dot1p, MAC) or Layer 3 (IP, DSCP) fields of contained packets, and this association of forwarding class at ingress will determine both the queuing and the Dot1P bit setting of packets on the Ethernet VLL on the egress.
SAP ingress classification and policing
The traffic at the SAP ingress is classified and metered according to the SLA parameters. All the traffic ingressing on the SAP is classified to a particular forwarding class. All the forwarding class is metered through and marked in-profile or out-of-profile, based on the meter parameters.
When applied to 7210 SAS Epipe services, service ingress QoS policies only create the unicast queues defined in the policy. The multipoint queues are not created on the service. Both Layer 2 or Layer 3 criteria can be used in the QoS policies for traffic classification in a service.
egress network dot1p marking
Marking of IEEE dot1p bits in VLAN tags is as per the FC-to-dot1p map. See the default network QoS policy in the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide for more information. This marking is applied at the port level on access ports and access-uplink ports.
Ingress network classification
Ingress network classification is based on the dot1p bits in the outer VLAN tag received on the access-uplink port. Dot1p-to-FC mapping is based on the network ingress QoS policy.
Filter policies
The 7210 SAS Epipe services can have a single filter policy associated on both ingress and egress. Both MAC and IP filter policies can be used on Epipe services.
MAC resources
Epipe services are point-to-point Layer 2 VPNs capable of carrying any Ethernet payloads. Although an Epipe is a Layer 2 service, the 7210 SAS Epipe implementation does not perform any MAC learning on the service, so Epipe services do not consume any MAC hardware resources.
Configuring a VLL service with CLI
This section describes how to configure Virtual Leased Line (VLL) services using the command line interface.
Common configuration tasks
This section provides a brief overview of the tasks that must be performed to configure the VLL services and provides the CLI commands:
Associate the service with a customer ID.
Define SAP parameters:
(Optional) Select ingress QoS policies (configured in the config>qos context).
(Optional) Select accounting policy (configured in the config>log context).
Define spoke-SDP parameters.
Note:Spoke-SDP parameters are only supported on 7210 SAS platforms operating in the network mode.
Enable the service.
Configuring VLL components
This section provides VLL configuration examples for the VLL services.
Creating an Epipe service in network mode
Use the following syntax to create an Epipe service.
config>service# epipe service-id [customer customer-id][create][vpn vpn-id]
description description-string
no shutdown
The following is a sample Epipe configuration output:
A:ALA-1>config>service# info
-------------------------------------------
...
1101 customer 1 vpn 1101 create
description "Default epipe description for service id 1101"
no shutdown
exit
----------------------------------------------
A:ALA-1>config>service#
Creating an Epipe service in access-uplink mode
This section only applies to 7210 SAS-T operating in access-uplink mode.
Use the following syntax to create an Epipe service.
config>service# epipe service-id [customer customer-id] [create] [svc-sap-type {null-star | dot1q | dot1q-preserve | any}] [customer- vid vlan-id] description description-string no shutdown
A:ALA-1>config>service# info
-------------------------------------------
...
epipe 500 customer 1 svc-sap-type null-star create
description "Local Epipe Service with NULL SVC_SAP_TYPE"
no shutdown
exit
----------------------------------------------
A:ALA-1>config>service#
Configuring Epipe SAP parameters
A default QoS policy is applied to each ingress SAP. Additional QoS policies can be configured in the config>qos context. Filter policies are configured in the config>filter context and explicitly applied to a SAP. There are no default filter policies.
Epipe SAP
config>service# epipe service-id [customer customer-id]
sap sap-id
accounting-policy policy-id
collect-stats
description description-string
no shutdown
egress
filter {ip ip-filter-name | mac mac-filter-name}
ingress
filter {ip ip-filter-name | mac mac-filter-name}
qos policy-id
Local Epipe SAPs
To configure a basic local Epipe service, enter the sap sap-id command twice with different port IDs in the same service configuration.
By default, QoS policy ID 1 is applied to ingress service SAPS. Existing filter policies or other existing QoS policies can be associated with service SAPs on ingress and egress ports.
Ingress and egress SAP parameters can be applied to local and distributed Epipe service SAPs.
The following is a sample of SAP configurations for local Epipe service 500 on SAP 1/1/2 and SAP 1/1/3 on ALA-1:
A:ALA-1>config>service# epipe 500 customer 5 create
config>service>epipe$ description "Local epipe service
config>service>epipe# sap 1/1/2 create
config>service>epipe>sap? ingress
config>service>epipe>sap>ingress# qos 20
config>service>epipe>sap>ingress# filter ip 1
config>service>epipe>sap>ingress# exit
config>service>epipe>sap# egress
config>service>epipe# sap 1/1/3 create
config>service>epipe>sap# ingress
config>service>epipe>sap>ingress# qos 555
config>service>epipe>sap>ingress# filter ip 1
config>service>epipe>sap>ingress# exit
config>service>epipe>sap# no shutdown
config>service>epipe>sap# exit
A:ALA-1>config>service# info
----------------------------------------------
...
epipe 500 customer 5 create
description "Local epipe service"
sap 1/1/2 create
ingress
qos 20
filter ip 1
exit
exit
sap 1/1/3 create
ingress
qos 555
filter ip 1
exit
exit
no shutdown
exit
----------------------------------------------
A:ALA-1>config>service#
Distributed Epipe Service
SDPs are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
To configure a distributed Epipe service, you must configure service entities on the originating and far-end nodes. You must use the same service ID on both ends (for example, Epipe 5500 on ALA-1 and Epipe 5500 on ALA-2). The spoke-sdp sdp-id:vc-id must match on both sides. A distributed Epipe consists of two SAPs on different nodes.
By default, QoS policy ID 1 is applied to ingress service SAPs. On egress, QoS policies are associated with a port. Existing filter policies can be associated with service SAPs on ingress and egress.
Meters (defined in SAP-ingress policies) can be applied on ingress, which is associated with SAPs. Scheduler policies can be applied on egress, which is associated with a port.
Ingress and egress SAP parameters can be applied to local and distributed Epipe service SAPs.
For SDP configuration information, see Configuring an SDP. For SDP binding information, see Configuring SDP bindings.
The following example configures a distributed service between ALA-1 and ALA-2:
A:ALA-1>epipe 5500 customer 5 create
config>service>epipe$ description "Distributed epipe service to east coast"
config>service>epipe# sap 221/1/3:21 create
config>service>epipe>sap# ingress
config>service>epipe>sap>ingress# qos 555
config>service>epipe>sap>ingress# filter ip 1
config>service>epipe>sap>ingress# exit
config>service>epipe>sap# no shutdown
config>service>epipe>sap# exit
config>service>epipe#
A:ALA-2>config>service# epipe 5500 customer 5 create
config>service>epipe$ description "Distributed epipe service to west coast"
config>service>epipe# sap 441/1/4:550 create
config>service>epipe>sap# ingress
config>service>epipe>sap>ingress# filter ip 1020
config>service>epipe>sap>ingress# exit
config>service>epipe>sap# egress
config>service>epipe>sap>egress# filter ip 6
config>service>epipe>sap>egress# exit
config>service>epipe>sap# no shutdown
config>service>epipe#
The following is a sample of the SAP configurations for ALA-1 and ALA-2:
A:ALA-1>config>service# info
----------------------------------------------
...
epipe 5500 customer 5 vpn 5500 create
description "Distributed epipe service to east coast"
sap 221/1/3:21 create
ingress
qos 555
filter ip 1
exit
exit
exit
...
----------------------------------------------
A:ALA-1>config>service#
A:ALA-2>config>service# info
----------------------------------------------
...
epipe 5500 customer 5 vpn 5500 create
description "Distributed epipe service to west coast"
sap 441/1/4:550 create
ingress
qos 654
filter ip 1020
exit
exit
exit
...
----------------------------------------------
A:ALA-2>config>service#
Configuring Ingress SAP Parameters
By default, QoS policy ID 1 is applied to ingress service SAPs. Existing filter policies or other existing QoS policies can be associated with service SAPs on ingress and egress ports.
Ingress and egress SAP parameters can be applied to local and distributed Epipe service SAPs.
The following is a sample of SAP ingress and egress parameters:
ALA-1>config>service# epipe 5500
config>service>epipe# sap 1/1/3:21
config>service>epipe>sap# ingress
config>service>epipe>sap>ingress# qos 555
config>service>epipe>sap>ingress# filter ip 1
config>service>epipe>sap>ingress# exit
config>service>epipe>sap#
The following is a sample Epipe SAP ingress configuration output:
A:ALA-1>config>service#
----------------------------------------------
...
epipe 5500 customer 5 vpn 5500 create
description "Distributed epipe service to east coast"
sap 1/1/3:21 create
ingress
qos 555
filter ip 1
exit
exit
no shutdown
exit
----------------------------------------------
A:ALA-1>config>service#
Creating an Epipe service for 7210 SAS-Mxp with range SAPs
The following is a sample of connection-profile used to configure a range of SAPs and an Epipe configuration output using the connection profile:
*A:7210SAS>config>connprof# info
----------------------------------------------
ethernet
ranges 0 2804-2805 2810-2811 2813 2832-2839
exit
----------------------------------------------
*A:7210SAS>config>service>epipe# info
----------------------------------------------
description "Default epipe description for service id 292"
sap 1/1/4:292.* create
description "Default sap description for service id 292"
exit
exit
sap 1/1/9:cp-292 create
description "Default sap description for service id 292"
exit
exit
no shutdown
----------------------------------------------
Configuring default QinQ SAPs for Epipe transit traffic in a ring scenario in access-uplink mode
Default QinQ SAPs are only supported on 7210 SAS platforms operating in the access-uplink mode.
In the following figure, 7210-1 is used to deliver some services to customers connected to the device, and additionally it needs to pass through transit from other nodes on the ring (for example, traffic from 7210-2 to 7210-3 or from 7210-2 to 7750-SR onto the core network).
Without default QinQ SAPs, the user would need to configure a service on 7210-1, with access-uplink SAPs for each service originating on some other node in the ring. With support for default QinQ SAPs, all traffic that does not need to be delivered to any customer service configured on 7210-1 can be switched using the Epipe service.
The following is a sample configuration output:
ALA-1>config>service# epipe 8 customer 1 svc-sap-type null-star create
sap 1/1/5:*.* create
statistics
ingress
exit
exit
exit
sap 1/1/6:*.* create
statistics
ingress
exit
exit
exit
no shutdown
exit
Configuring SDP bindings
SDPs are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
The following figure shows an example of a distributed Epipe service configuration between two routers, identifying the service and customer IDs, and the unidirectional SDPs required to communicate to the far-end routers.
A spoke-SDP is treated like the equivalent of a traditional bridge ‟port” where flooded traffic received on the spoke-SDP is replicated on all other ‟ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.
Use the following syntax to create a spoke-SDP binding with an Epipe service.
config>service# epipe service-id [customer customer-id]
spoke-sdp sdp-id:vc-id [vc-type {ether | vlan}]
vlan-vc-tag 0..4094
egress
filter {ip ip-filter-id}
vc-label egress-vc-label
ingress
filter {ip ip-filter-id}
vc-label ingress-vc-label
no shutdown
The following shows the command usage to bind an Epipe service between ALA-1 and ALA-2. This example assumes that the SAPs have already been configured (see Distributed Epipe Service).
A:ALA-1>config>service# epipe 5500
config>service>epipe# spoke-sdp 2:123
config>service>epipe>spoke-sdp# egress
config>service>epipe>spoke-sdp>egress# vc-label 5500
config>service>epipe>spoke-sdp>egress# exit
config>service>epipe>spoke-sdp# ingress
config>service>epipe>spoke-sdp>ingress# vc-label 6600
config>service>epipe>spoke-sdp>ingress# exit
config>service>epipe>spoke-sdp# no shutdown
ALA-2>config>service# epipe 5500
config>service>epipe# spoke-sdp 2:456
config>service>epipe>spoke-sdp# egress
config>service>epipe>spoke-sdp>egress# vc-label 6600
config>service>epipe>spoke-sdp>egress# exit
config>service>epipe>spoke-sdp# ingress
config>service>epipe>spoke-sdp>ingress# vc-label 5500
config>service>epipe>spoke-sdp>ingress# exit
config>service>epipe>spoke-sdp# no shutdown
The following is a sample SDP binding for the Epipe service between ALA-1 and ALA-2 configuration output:
A:ALA-1>config>service# info
----------------------------------------------
...
epipe 5500 customer 5 vpn 5500 create
description "Distributed epipe service to east coast"
sap 1/1/3:21 create
ingress
qos 555
filter ip 1
exit
exit
spoke-sdp 2:123 create
ingress
vc-label 6600
exit
egress
vc-label 5500
exit
exit
no shutdown
exit
...
----------------------------------------------
A:ALA-1>config>service#
A:ALA-2>config>service# info
----------------------------------------------
...
exit
epipe 5500 customer 5 vpn 5500 create
description "Distributed epipe service to west coast"
sap 441/1/4:550 create
ingress
qos 654
filter ip 1020
exit
exit
spoke-sdp 2:456 create
ingress
vc-label 5500
exit
egress
vc-label 6600
exit
exit
no shutdown
exit
...
----------------------------------------------
A:ALA-2>config>service#
Using spoke-SDP control words
SDPs are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
The control-word command provides the option to add a control word as part of the packet encapsulation for PW types for which the control word is optional. On the 7210 SAS, an option is provided to enable it for Ethernet PW (Epipe). The control word might be needed because when ECMP is enabled on the network, packets of a specific PW may be spread over multiple ECMP paths if the hashing router mistakes the PW packet payload for an IPv4 or IPv6 packet. This occurs when the first nibble following the service label corresponds to a value of 4 or 6.
The control word negotiation procedures described in Section 6.2 of RFC 4447 are not supported, and therefore the service will only come up if the same C-bit value is signaled in both directions. If a spoke-SDP is configured to use the control word, but the node receives a label mapping message with a C-bit clear, the node releases the label with an ‟Illegal C-bit” status code per Section 6.1 of RFC 4447. As soon as the user enables control of the remote peer, the remote peer withdraws its original label and sends a label mapping with the C-bit set to 1 and the VLL service is up in both nodes.
When the control word is enabled, VCCV packets also include the VCCV control word. In that case, the VCCV CC type 1 (OAM CW) is signaled in the VCCV parameter in the FEC. If the control word is disabled on the spoke-SDP, the router alert label is used. In that case, VCCV CC type 2 is signaled. Note that for a multi-segment PW (MS-PW), the CC type 1 is the only type supported, and therefore the control word must be enabled on the spoke-SDP to be able to use VCCV-ping and VCCV-trace.
The following is a sample spoke-SDP control word configuration output:
-Dut-B>config>service>epipe# info
----------------------------------------------
description "Default epipe description for service id 2100"
sap 1/2/7:4 create
description "Default sap description for service id 2100"
exit
spoke-sdp 1:2001 create
control-word
exit
no shutdown
----------------------------------------------
*A:ALA-Dut-B>config>service>epipe#
To disable the control word on spoke-sdp 1:2001:
*A:ALA-Dut-B>config>service>epipe# info
----------------------------------------------
description "Default epipe description for service id 2100"
sap 1/2/7:4 create
description "Default sap description for service id 2100"
exit
spoke-sdp 1:2001 create
exit
no shutdown
----------------------------------------------
*A:ALA-Dut-B>config>service>epipe#
Configuring VLL resilience
The following figure shows an example to create VLL resilience. Note that the zero revert-time value means that the VLL path will be switched back to the primary immediately after it comes back up.
PE1 configuration output
The following is a sample configuration output on PE1:
*A:ALA-48>config>service>epipe# info
----------------------------------------------
endpoint "x" create
exit
endpoint "y" create
exit
spoke-sdp 1:100 endpoint "y" create
precedence primary
exit
spoke-sdp 2:200 endpoint "y" create
precedence 1
exit
no shutdown
----------------------------------------------
*A:ALA-48>config>service>epipe#
Configuring VLL resilience for a switched pseudowire path
VLL resilience with pseudowire switching shows VLL resilience with pseudowire switching.
T-PE1 configuration output
The following is a sample configuration output on TPE1:
*A:ALA-48>config>service>epipe# info
----------------------------------------------
endpoint "x" create
exit
endpoint "y" create
exit
sap 1/1/1:100 endpoint "x" create
exit
spoke-sdp 1:100 endpoint "y" create
precedence primary
exit
spoke-sdp 2:200 endpoint "y" create
precedence 1
exit
spoke-sdp 3:300 endpoint "y" create
precedence 1
exit
no shutdown
----------------------------------------------
*A:ALA-48>config>service>epipe#
T-PE2 configuration output
The following is a sample configuration output on TPE2:
*A:ALA-49>config>service>epipe# info
----------------------------------------------
endpoint "x" create
exit
endpoint "y" create
revert-time 100
exit
spoke-sdp 4:400 endpoint "y" create
precedence primary
exit
spoke-sdp 5:500 endpoint "y" create
precedence 1
exit
spoke-sdp 6:600 endpoint "y" create
precedence 1
exit
no shutdown
----------------------------------------------
*A:ALA-49>config>service>epipe#
S-PE1 configuration output
The following is a sample configuration output on S-PE1:
*A:ALA-50>config>service>epipe# info
----------------------------------------------
...
spoke-sdp 1:100 create
exit
spoke-sdp 4:400 create
exit
no shutdown
----------------------------------------------
*A:ALA-49>config>service>epipe#
Service management tasks
This section provides information about VLL service management tasks.
Modifying Epipe service parameters
The following shows the command usage to add an accounting policy to an existing SAP.
- Example:
config>service# epipe 2 config>service>epipe# sap 1/1/3:21 config>service>epipe>sap# accounting-policy 14 config>service>epipe>sap# exit
SAP configuration output
The following is a sample SAP configuration output:
ALA-1>config>service# info
----------------------------------------------
epipe 2 customer 6 vpn 2 create
description "Distributed Epipe service to east coast"
sap 1/1/3:21 create
accounting-policy 14
exit
no shutdown
exit
----------------------------------------------
ALA-1>config>service#
Disabling an Epipe service
Use the following syntax to shut down an Epipe service without deleting the service parameters.
config>service> epipe service-id
shutdown
- Example:
config>service# epipe 2 config>service>epipe# shutdown config>service>epipe# exit
Re-enabling an Epipe service
Use the following syntax to re-enable an Epipe service that was shut down.
config>service# epipe service-id
no shutdown
- Example:
config>service# epipe 2 config>service>epipe# no shutdown config>service>epipe# exit
Deleting an Epipe service
Perform the following steps before deleting an Epipe service.
Shut down the SAP.
Delete the SAP.
Shut down the service.
Use the following syntax to delete an Epipe service.
config>service
[no] epipe service-id
shutdown
[no] sap sap-id
shutdown
- Example:
config>service# epipe 2 config>service>epipe# sap 1/1/3:21 config>service>epipe>sap# shutdown config>service>epipe>sap# exit config>service>epipe# no sap 1/1/3:21 config>service>epipe# epipe 2 config>service>epipe# shutdown config>service>epipe# exit config>service# no epipe 2
VLL services command reference
Command hierarchies
VLL service configuration commands
Epipe Service Configuration Commands
VLL service configuration commands
Epipe global commands (for access-uplink operating mode)
config
- service
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {null-star | dot1q-preserve | any | dot1q-range}] [customer-vid vlan-id]
- no epipe service-id
- description description-string
- no description
- sap sap-id [create] [no-endpoint]
- sap sap-id [create] endpoint endpoint-name
- no sap sap-id
- [no] shutdown
Epipe global commands (for network operating mode)
config
- service
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {any | qinq-inner-tag-preserve}] [customer-vid vlan-id] [pbb-epipe]
- no epipe service-id
- description description-string
- no description
- [no] endpoint endpoint-name [create]
- active-hold-delay active-endpoint-delay
- no active-hold-delay
- revert-time [revert-time | infinite]
- no revert-time
- standby-signaling-master
- [no] standby-signaling-master
- sap sap-id [create] [no-endpoint]
- sap sap-id [create] endpoint endpoint-name
- no sap sap-id
- service-mtu octets
- no service-mtu
- [no] service-mtu-check
- [no] shutdown
- spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] [no-endpoint]
- spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] endpoint
- no spoke-sdp sdp-id[:vc-id]
- spoke-sdp-fec spoke-sdp-fec-id [fec fec-type] [aii-type aii-type] [create]
- spoke-sdp-fec spoke-sdp-fec-id no-endpoint
- spoke-sdp-fec spoke-sdp-fec-id [fec fec-type] [aii-type aii-type] [create] endpoint name [icb]
- no spoke-sdp-fec spoke-sdp-fec-id
Epipe SAP configuration commands
config
- service
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {any | qinq-inner-tag-preserve}] [customer-vid vlan-id] [pbb-epipe]
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {null-star | dot1q-preserve | any | dot1q-range}] [customer-vid vlan-id]
- no epipe service-id
- sap sap-id [create] [no-endpoint]
- sap sap-id [create] endpoint endpoint-name
- no sap sap-id
- accounting-policy acct-policy-id
- no accounting-policy acct-policy-id
- [no] collect-stats
- description description-string
- no description
- eth-cfm
- [no] mep mep-id domain md-index association ma-index [direction {up | down}] primary-vlan-enable
- ais-enable [no]
- [no] client-meg-level [[level [level ...]]
- [no] interval {1 | 60}
- [no] priority priority-value
- [no] ccm-enable
- [no] ccm-ltm-priority priority
- [no] description
- [no] eth-test-enable
- [no] bit-error-threshold bit-errors
- [no] test-pattern {all-zeros | all-ones} [crc-enable]
- [no] fault-propagation-enable {use-if-tlv | suspendccm}
- low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
- [no] mac-address mac-address
- [no] one-way-delay-threshold seconds
- [no] shutdown
- mip [mac mac address]
- mip default-mac
- no mip
- ethernet
- [no] llf
- [no] ignore-oper-down
- [no] shutdown
Epipe SAP meter override commands
config
- service
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {any | qinq-inner-tag-preserve}] [customer-vid vlan-id] [pbb-epipe]
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {null-star | dot1q-preserve | any | dot1q-range}] [customer-vid vlan-id]
- no epipe service-id
- sap sap-id [create] [no-endpoint]
- sap sap-id [create] endpoint endpoint-name
- 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]
- no rate
Epipe SAP statistics commands
config
- service
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {any | qinq-inner-tag-preserve}] [customer-vid vlan-id] [pbb-epipe]
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {null-star | dot1q-preserve | any | dot1q-range}] [customer-vid vlan-id]
- no epipe service-id
- sap sap-id [create] [no-endpoint]
- sap sap-id [create] endpoint endpoint-name
- no sap sap-id
- statistics
- ingress
- counter-mode {in-out-profile-count | forward-drop-count}
- [no] drop-count-extra-vlan-tag-pkts
Epipe spoke-SDP configuration commands
Spoke-SDP commands are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
config
- service]
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {any | qinq-inner-tag-preserve}] [customer-vid vlan-id] [pbb-epipe]
- no epipe service-id
- spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] [no-endpoint]
- spoke-sdp sdp-id[:vc-id] [vc-type {ether | vlan}] [create] endpoint
- no spoke-sdp sdp-id[:vc-id]
- accounting-policy acct-policy-id
- no accounting-policy
- [no] collect-stats
- [no] control-word
- control-channel-status
- acknowledgment
- no acknowledgment
- refresh-timer seconds
- no refresh-timer
- request-timer request-timer request-timer-secs retry-timer retry-timer-secs timeout-multiplier multiplier
- [no] description
- [no] egress
- [no] vc-label egress-vc-label
- eth-cfm
- [no] mep mep-id domain md-index association ma-index [direction {up | down}]
- [no] ais-enable
- [no] client-meg-level [[level [level ...]]
- [no] interval {1 | 60}
- [no] priority priority-value
- [no] ccm-enable
- [no] ccm-ltm-priority priority
- [no] description
- [no] eth-test-enable
- [no] bit-error-threshold bit-errors
- [no] test-pattern {all-zeros | all-ones} [crc-enable]
- [no] fault-propagation-enable {use-if-tlv | suspendccm}
- low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
- [no] mac-address mac-address
- [no] one-way-delay-threshold seconds
- [no] shutdown
- mip [mac mac address]
- mip default-mac
- no mip
- [no] force-vlan-vc-forwarding
- hash-label
- hash-label [signal-capability]
- no hash-label
- [no] ingress
- [no] vc-label egress-vc-label
- precedence [precedence-value| primary]
- no precedence
- [no] pw-path-id
- agi attachment-group-identifier
- no agi
- no saii-type2
- saii-type2 global-id:node-id:ac-id
- no taii-type2
- taii-type2 global-id:node-id:ac-id
- no pw-status-signaling
- pw-status-signaling
- [no] shutdown
- vlan-vc-tag 0..4094
- no vlan-vc-tag [0..4094]
- spoke-sdp-fec spoke-sdp-fec-id [fec fec-type] [aii-type aii-type] [create]
- spoke-sdp-fec spoke-sdp-fec-id no-endpoint
- spoke-sdp-fec spoke-sdp-fec-id [fec fec-type] [aii-type aii-type] [create] endpoint name [icb]
- no spoke-sdp-fec spoke-sdp-fec-id
- [no] auto-config
- path name
- no path
- precedence prec-value
- precedence primary
- no precedence
- pw-template-bind policy-id
- no pw-template-bind
- retry-count retry-count
- no retry-count
- retry-timer retry-timer
- no retry-timer
- saii-type2 global-id:prefix:ac-id
- no saii-type2
- [no] shutdown
- taii-type2 global-id:prefix:ac-id
- no taii-type2
Epipe 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 (standalone) devices)
config
- service
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {any | qinq-inner-tag-preserve}] [customer-vid vlan-id] [pbb-epipe]
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {null-star | dot1q-preserve | any | dot1q-range}] [customer-vid vlan-id]
- no epipe service-id
- sap sap-id [create] [no-endpoint]
- sap sap-id [create] endpoint endpoint-name
- 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
Epipe SAP QoS and filter commands (for 7210 SAS-Mxp)
config
- service
- epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {any | qinq-inner-tag-preserve}] [customer-vid vlan-id] [pbb-epipe]
- no epipe service-id
- sap sap-id [create] [no-endpoint]
- sap sap-id [create] endpoint endpoint-name
- 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] (app
- 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
Connection profile commands
config
- connection-profile conn-prof-id [create]
- no connection-profile conn-prof-id
- description description-string
- no description
- ethernet
- no ranges
- ranges vlan ranges [vlan ranges...(up to 32 max)]
Show commands
show
- service
- egress-label start-label [end-label]
- id service-id
- all
- base
- endpoint [endpoint-name]
- epipe
- labels
- sap sap-id [detail]
- sdp [sdp-id | far-end ip-addr] [detail]
- split-horizon-group [group-name]
- stp [detail]]
- saii-type2-using global-id[:prefix[:ac-id]]
- sap-using [sap sap-id]
- sap-using [ingress | egress] filter filter-id
- sap-using [ingress] qos-policy qos-policy-id
- service-using [epipe] [vpls] [mirror] [b-vpls] [i-vpls] [m-vpls] [sdp sdp-id] [customer customer-id]
- sdp [sdp-id | far-end ip-address] [detail | keep-alive-history]
- spoke-sdp-fec-using [spoke-sdp-fec-id spoke-sdp-fec-id] [saii-type2 global-id:prefix:ac-id] [taii-type2 global-id:prefix:ac-id] [path name] [expired]
- taii-type2-using global-id[:prefix[:ac-id]]
show
- connection-profile [conn-prof-id] [associations]
Clear commands
clear
- service
- id service-id
- statistics
- id service-id
- counters
- sap sap-id {all | cem | counters | stp | l2pt}
Command descriptions
VLL service configuration commands
Generic commands
description
Syntax
description description-string
no description
Context
config>service>epipe
config>service>epipe>sap
config>service>epipe>spoke-sdp (not supported in access-uplink operating mode)
config>connection-profile
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 associated with the configuration context.
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 on), the entire string must be enclosed within double quotes.
shutdown
Syntax
[no] shutdown
Context
config>service>epipe
config>service>epipe>sap
config>service>epipe>spoke-sdp (not supported in access-uplink operating mode)
config>service>epipe>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 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.
VLL global commands
epipe
Syntax
epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {any | qinq-inner-tag-preserve}] [customer-vid vlan-id] [pbb-epipe]
no epipe 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 configures an Epipe service instance. This command is used to configure a point-to-point Epipe service. An Epipe connects two endpoints defined as Service Access Points (SAPs). In a local service, the SAPs may be defined in one 7210 SAS node and in distributed service the SAPs may be defined on two different 7210 SAS nodes.
On 7210 SAS, platforms operating in network mode, both local and distributed services are supported.
MAC learning and filtering are not supported on an Epipe service.
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.
The no form of this command deletes the Epipe service instance with the specified service-id. The service cannot be deleted until the service has been shut down and all instances of SAPs, mesh, or spokes have been deleted from the service.
Default
No Epipe services exist until they are explicitly created with this command.
Parameters
- service-id
The unique service identification number or string 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.
- 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.
- vpn vpn-id
Specifies the VPN ID number which allows you to identify virtual private networks (VPNs) by a VPN ID. If this parameter is not specified, the VPN ID uses the same service ID number.
- svc-sap-type
Specifies the service type and the allowed SAPs in the service. When the pbb-epipe keyword is not configured, a plain Epipe service can be configured with SAPs and SDPs.
- create
Keyword used to create the service instance. The create keyword requirement can be enabled or disabled in the environment>create context.
- pbb-epipe
Specifies a PBB Epipe service, which allows the software to allocate the appropriate resources for PBB Epipe. Only SAPs can be configured with a PBB Epipe service.
Note:PBB and the pbb-epipe keyword are supported only on 7210 SAS-T operating in the network mode.
epipe
Syntax
epipe service-id [customer customer-id] [create] [vpn vpn-id] [svc-sap-type {null-star | dot1q-preserve | any | dot1q-range}] [customer-vid vlan-id]
no epipe service-id
Context
config>service
Platforms
Only supported on 7210 SAS platforms configured in the access-uplink operating mode
Description
This command configures an Epipe service instance. This command is used to configure a point-to-point Epipe service. An Epipe connects two endpoints defined as SAPs. In a local service, the SAPs may be defined in one 7210 SAS node and in distributed service the SAPs may be defined on two different 7210 SAS nodes.
Distributed services are only supported on 7210 SAS platforms operating in the network mode. 7210 SAS platforms operating in access-uplink mode only support local SAP-to-SAP service.
MAC learning and filtering are not supported on an Epipe service.
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 parameter 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.
The no form of this command deletes the Epipe service instance with the specified service-id value. The service cannot be deleted until it has been shut down and all instances of SAPs have been deleted from the service.
Default
No Epipe services exist until they are explicitly created with this command.
Parameters
- service-id
Specifies the unique service identification number or string identifying the service in the service domain. The ID must be unique to the service and may not be used for any other service of any type. The service-id must be the same value for every 7210 SAS device on which this service is defined.
- customer customer-id
Specifies the customer ID to be associated with the service. This parameter is required on service creation and is optional for service editing or deletion.
- vpn vpn-id
Specifies the VPN ID , which allows you to identify virtual private networks (VPNs). If this parameter is not specified, the VPN ID uses the same number as the service ID.
- svc-sap-type
Specifies the service type and the SAPs allowed in the service.
- customer-vid vlan-id
Specifies the dot1q VLAN ID to be used while creating the local dot1q SAP for the svc-sap-type command with the dot1q-preserve option specified.
- create
Keyword used to create the service instance. The create keyword can be enabled or disabled in the environment>create context.
endpoint
Syntax
[no] endpoint endpoint-name
Context
config>service>epipe
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.
active-hold-delay
Syntax
active-hold-delay active-hold-delay
no active-hold-delay
Context
config>service>epipe>endpoint
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command specifies that the node delays sending the change in the T-LDP status bits for the VLL endpoint when the MC-LAG transitions the LAG subgroup which hosts the SAP for this VLL endpoint from active to standby or when any object in the endpoint. For example, SAP, ICB, or regular spoke-SDP, transitions from up to down operational state.
By default, when the MC-LAG transitioned the LAG subgroup which hosts the SAP for this VLL endpoint from active to standby, the node sends immediately new T-LDP status bits indicating the new value of "standby" over the spoke-SDPs which are on the mate-endpoint of the VLL. The same applies when any object in the endpoint changes an operational state from up to down.
There is no delay applied to the VLL endpoint status bit advertisement when the MC-LAG transitions the LAG subgroup which hosts the SAP from "standby" to "active" or when any object in the endpoint transitions to an operationally up state.
Default
0 — A value of zero means that when the MC-LAG transitioned the LAG subgroup which hosts the SAP for this VLL endpoint from active to standby, the node sends immediately new T-LDP status bits indicating the new value of standby over the spoke-SDPs which are on the mate-endpoint of the VLL. The same applies when any object in the endpoint changes an operational state from up to down.
Parameters
- active-hold-delay
Specifies the active hold delay in 100s of milliseconds.
revert-time
Syntax
revert-time [revert-time | infinite]
no revert-time
Context
config>service>epipe>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 back to the primary spoke-SDP defined on this service endpoint, after having failed over to a backup spoke-SDP.
The no form of this command resets the timer to the default value of 0.
Parameters
- revert-time
Specify the time, in seconds, to wait before reverting to the primary SDP.
- infinite
Causes the endpoint to be non-revertive.
standby-signaling-master
Syntax
[no] standby-signaling-master
Context
config>service>vll>endpoint
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command enables the pseudowire standby bit (value 0x00000020) to be sent to T-LDP peer for each spoke SPD of the endpoint that is selected as a standby.
This command is mutually exclusive with a VLL mate SAP created on an MC-LAG or ICB. It is also mutually exclusive with vc-switching.
Default
no standby-signaling-master
service-mtu
Syntax
service-mtu octets
no service-mtu
Context
config>service>epipe
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, 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 re-evaluated.
The no form of this command returns the default service-mtu for the indicated service type 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 (in octets) for specific VC types.
VC-type |
Example service MTU |
Advertised MTU |
|---|---|---|
Ethernet |
1514 |
1500 |
Ethernet (with preserved dot1q) |
1518 |
1504 |
VPLS |
1514 |
1500 |
VPLS (with preserved dot1q) |
1518 |
1504 |
VLAN (dot1p transparent to MTU value) |
1514 |
1500 |
VLAN (QinQ with preserved bottom Qtag) |
1518 |
1504 |
Parameters
- octets
Specifies the size of the MTU in octets, expressed as a decimal integer.
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).
service-mtu-check
Syntax
[no] service-mtu-check
Context
config>service>epipe
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
The no form of this command disables the 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. 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).
If TLDP is used for signaling, the configured value for service-mtu is used during a pseudowire setup.
Default
enabled
VLL SAP commands
sap
Syntax
sap sap-id [create] [no-endpoint]
sap sap-id [create] endpoint endpoint-name
no sap sap-id
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 creates a 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 device. Each SAP must be unique.
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.
In a single physical port only one SAP can belong to one service. Multiple SAPs can be defined over a physical port but each of these SAPs should belong to different service. This is true only for access-uplink mode. That is, for network mode, multiple SAPs on the same port can belong to the same service.
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. Additionally, in access-uplink mode, SAPs can be defined also on access-uplink port. Access-uplink SAPs are network facing SAPs representing Dot1q or QinQ tunnels used to transport traffic toward the service nodes.
If a port is shut down, all SAPs on that port become operationally down. When a service is shut down, SAPs for the service are not displayed as operationally down although all traffic traversing the service is discarded.
The operational state of a SAP is relative to the operational state f the port on which theo SAP is defined.
The following encapsulations are supported:
Ethernet access SAPs support null, dot1q
Ethernet access-uplink SAPs support only QinQ encapsulation.
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.
Default
No SAPs are defined.
Special Cases
- Default SAPs
A default SAP has the following format: port-id:*. This type of SAP is supported only on Ethernet MDAs and its creation is allowed only in the scope of Layer 2 services (Epipe and VPLS).
Parameters
- sap-id
Specifies the physical port identifier portion of the SAP. 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.
- no-endpoint
Keyword used to remove the association of a SAP or a spoke-SDP with an explicit endpoint name. This keyword is not supported on platforms operating in the access-uplink operating mode.
- endpoint-name
Specifies to add a SAP endpoint association, up to 32 characters. This parameter is not supported on platforms configured in the access-uplink operating mode.
accounting-policy
Syntax
accounting-policy acct-policy-id
no accounting-policy
Context
config>service>epipe>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.
collect-stats
Syntax
[no] collect-stats
Context
config>service>epipe>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, the counters written to the billing file include all the traffic while the no collect-stats command was in effect.
Default
no collect-stats
description
Syntax
description description-string
no description
Context
config>service>epipe>sap
config>service>epipe>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 defines an ASCII string associated with egress-multicast-group-name.
The no form of this command removes an existing description string from egress-multicast-group.
Parameters
- description-string
Specifies the description as an ASCII string of up to 80 characters. Only printable 127 bit ASCII characters are allowed. If the string contains spaces, the string must be specified with beginning and ending quotes.
eth-cfm
Syntax
eth-cfm
Context
config>service>epipe>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>epipe>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 provisions the maintenance endpoint (MEP).
For more information about ETH-CFM support, see the 7210 SAS-Mxp, R6, R12, S, Sx, T OAM and Diagnostics Guide.
The no form of this command reverts to the default values.
Parameters
- mep-id
Specifies the maintenance association end point identifier.
- md-index
Specifies the maintenance domain (MD) index value.
- ma-index
Specifies the MA index value.
- 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 with the primary VLAN configured under the bridge-identifier for the MA. This is only allowed if the mhf-creation method is static. MIPs cannot be changed from or to primary VLAN functions without first being deleted. 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 operating mode), 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-Mxp (network operating mode).
ais-enable
Syntax
[no] ais-enable
Context
config>service>epipe>sap>eth-cfm>mep
config>service>epipe>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 enables the generation and the reception of AIS messages.
client-meg-level
Syntax
client-meg-level [[level [level ...]]
no client-meg-level
Context
config>service>epipe>sap>eth-cfm>mep>ais-enable
config>service>epipe>spoke-sdp>eth-cfm>mep>ais-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 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.
interval
Syntax
interval {1 | 60}
no interval
Context
config>service>vpls>epipe>eth-cfm>mep>ais-enable
config>service>epipe>spoke-sdp>eth-cfm>mep>ais-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 specifies the transmission interval of AIS messages in seconds.
Parameters
- 1 | 60
Specifies the transmission interval of AIS messages in seconds.
priority
Syntax
priority priority-value
no priority
Context
config>service>vpls>epipe>eth-cfm>mep>ais-enable
config>service>epipe>spoke-sdp>eth-cfm>mep>ais-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 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>epipe>sap>eth-cfm>mep
config>service>epipe>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 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>epipe>sap>eth-cfm>mep
config>service>epipe>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 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.
eth-test-enable
Syntax
[no] eth-test-enable
Context
config>service>epipe>sap>eth-cfm>mep
config>service>epipe>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
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.
bit-error-threshold
Syntax
bit-error-threshold errors
no bit-error-threshold
Context
config>service>epipe>sap>eth-cfm>mep>eth-test-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 threshold value of bit errors.
test-pattern
Syntax
test-pattern {all-zeros | all-ones} [crc-enable]
no test-pattern
Context
config>service>epipe>sap>eth-cfm>mep>eth-test-enable
config>service>epipe>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.
fault-propagation-enable
Syntax
fault-propagation-enable {use-if-tlv | suspend-ccm}
no fault-propagation-enable
Context
config>service>epipe>sap>eth-cfm>mep
config>service>epipe>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 configures the fault propagation for the MEP.
Parameters
- use-if-tlv
Specifies to use the interface TLV.
- suspend-ccm
Specifies to suspend the continuity check messages.
low-priority-defect
Syntax
low-priority-defect {allDef | macRemErrXcon | remErrXcon | errXcon | xcon | noXcon}
Context
config>service>epipe>sap>eth-cfm>mep
config>service>epipe>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>epipe>spoke-sdp>eth-cfm>mep (not supported in access-uplink operating mode)
config>service>epipe>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.
agg-rate-limit
Syntax
agg-rate-limit agg-rate
no agg-rate-limit
Context
config>service>epipe>sap>egress
config>service>vpls>sap>egress
config>service>ies>sap>egress
config>service>vprn>sap>egress (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 a maximum total rate for all egress queues on a service SAP.
The SAP aggregate rate can be used only if SAP based scheduling mode is configured at the port level. It is not supported in FC-based scheduling mode.
When configured in SAP-based scheduling mode, the egress port scheduler distributes the available bandwidth to all the SAPs configured on the port, up to the configured aggregate rate for the SAP.
The no form of this command removes the aggregate rate limit from the SAP.
Parameters
- agg-rate
Defines the rate, in kilobits-per-second, that the maximum aggregate rate the queues on the SAP or MSS can operate.
tod-suite
Syntax
tod-suite tod-suite-name
no tod-suite
Context
config>service>epipe>sap
Platforms
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode.
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.
one-way-delay-threshold
Syntax
one-way-delay-threshold seconds
Context
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.
mip
Syntax
mip [mac mac-address]
mip default-mac
no mip
Context
config>service>epipe>sap>eth-cfm
config>service>epipe>spoke-sdp>eth-cfm (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 allows Maintenance Intermediate Points (MIPs) to be created if mhf-creation for the MA is configured using the default option.
Parameters
- mac-address
Specifies the MAC address of the MIP.
- default-mac
Using the no command deletes the MIP. If the operator needs to change the mac back to the default mac without having to delete the MIP and reconfiguring this command is useful.
ethernet
Syntax
ethernet
Context
config>service>epipe>sap
Platforms
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode.
Description
This command configures Ethernet properties in this SAP.
llf
Syntax
[no] llf
Context
config>service>epipe>sap>ethernet
Platforms
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode.
Description
This command enables Link Loss Forwarding (LLF) on an Ethernet port. It provides an end-to-end OAM fault notification for Ethernet VLL service.LLF on an Ethernet port brings down the port when there is a local fault on the pseudowire or service, or a remote fault on the SAP or pseudowire, signaled with label withdrawal or TLDP status bits. It ceases when the fault disappears.
The Ethernet port must be configured for null encapsulation.
The no form of this command disables LLF.
ignore-oper-down
Syntax
[no] ignore-oper-down
Context
config>service>epipe>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 user to configure the optional command for a specific SAP to ignore the transition of the operational state to down when a SAP fails. Only a single SAP in an Epipe may use this option.
Default
no ignore-oper-down
Service filter and QoS policy commands
egress
Syntax
egress
Context
config>service>epipe>spoke-sdp (not supported in access-uplink mode)
config>service>epipe>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 SAP parameters.
force-vlan-vc-forwarding
Syntax
[no] force-vlan-vc-forwarding
Context
config>service>epipe>spoke-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
This command forces vc-vlan-type forwarding in the datapath for spoke which have either vc-type. This comand is not allowed on vlan-vc-type SDPs.
The no version of this command sets default behavior.
Default
Per default this feature is disabled
hash-label
Syntax
hash-label [signal-capability]
no hash-label
Context
config>service>epipe>spoke-sdp
Platforms
7210 SAS-Mxp, 7210 SAS-R6 IMM-b, 7210 SAS-R6 IMM-c, 7210 SAS-R12 IMM-b, 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.
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 that are generated in the CPM and forwarded with a label in 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 interface, a VPLS spoke-SDP interface, or a VPLS mesh-SDP interface by configuring the signal-capability option. In this case, the decision 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 command and the signal-capability option are enabled on the local PE.
The 7210 SAS local PE inserts the Flow Label Interface Parameters sub-TLV with T=1 and R=1 in the PW ID FEC element in the label mapping message for that spoke SDP or mesh SDP.
If the remote PE does not send the Flow Label sub-TLV in the PW ID FEC element, or sends a Flow Label sub-TLV in the PW ID FEC element with T=FALSE and R=FALSE, the local node disables the hash label capability. Consequently, the 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. The latter may also be caused by a remote 7210 SAS PE that does not support the hash-label command, has the hash-label command enabled but does not support the signal-capability option, or does support both options but the user did not enable them because of a misconfiguration.
If the remote PE sends the Flow Label sub-TLV in the PW ID FEC element with T=TRUE and R=TRUE, the local PE enables the hash label capability. The 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 form the remote PE with or without a hash label.
If the hash-label command 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 command 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 required. When doing so, the router must withdraw the label it sent to its peer and send a new label mapping message with the new value of the F bit in the flow label interface parameters sub-TLV of the PW ID FEC element.
This feature is supported only for VLL and VPLS services. It is not supported for VPRN services. It is also not supported on multicast packets forwarded using RSVP P2MP LSPs or mLDP LSPs in both the base router instance and in the multicast VPN (mVPN) instance.
On the 7750 SR 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. That is, the value of the hash label is always in the range of 524,288 to 1,048,575 and does not overlap with the signaled or static LSP and signaled or 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 the 7210 SAS for service traffic (for MPLS OAM traffic the MSB bit is set). That is, 7210 SAS devices do not set the MSB in the hash label value for service traffic. Consequently, the user must ensure that both ends are correctly configured to either process hash labels or disable them.
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 hash label between the local and remote PE nodes.
ingress
Syntax
ingress
Context
config>service>epipe>sap
config>service>epipe>sap>statistics
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 Quality of Service (QoS) policies.
If no sap-ingress QoS policy is defined, the system default sap-ingress QoS policy is used for ingress processing.
aggregate-meter-rate
Syntax
aggregate-meter-rate rate-in-kbps [burst burst-in-kbits] [enable-stats]
no aggregate-meter-rate
Context
config>service>vpls>sap>egress
config>service>epipe>sap>egress (not supported on 7210 SAS-Mxp)
config>service>ies>sap>egress
config>service>vprn>sap>egress (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 SAP egress aggregate policer. The rate (PIR) of the SAP egress aggregate policer must be specified by the user. The user can optionally specify the burst size for the SAP aggregate policer. The aggregate policer monitors the traffic sent out of the SAP and determines if the packet is either forwarded or dropped.
An option is provided to associate a set of two counters to calculate total forwarded packets and octets, and total dropped packets and octets. When the counter is enabled, the resources required increases to twice the resources required when the counter is not used. If enable-stats keyword is specified during the creation of the meter, the counter is allocated by software (if available). To free up the counter and relinquish its use, the user can use the no aggregate-meter-rate command, and then recreate the meter again using the aggregate-meter rate command.
If egress frame-based accounting is used, the SAP egress aggregate meter rate accounts for the Ethernet frame overhead. The system accounts for 12 bytes of IFG and 8 bytes of start delimiter. Frame-based counting does not affect the count of octets maintained by the counter (if in use).
Before enabling this command for a SAP, resources must be allocated to this feature from the egress-internal-tcam resource pool using the command configure>system>resource-profile>egress-internal-tcam>egress-sap-aggregate-meter. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information.
The egress aggregate meter is not FC aware. The forward and drop decisions are taken based on the order the packets are sent out of the SAP by the egress port scheduler.
The no form of this command removes the egress aggregate policer from use.
Default
no aggregate-meter-rate
Parameters
- rate-in-kbps
Specifies the rate in kilobits per second.
- burst <burst-in-kilobits>
Specifies the burst size for the policer in kilobits. The burst size cannot be configured without configuring the rate.
- enable-stats
Specifies if counter to count forwarded and dropped count must be allocated or not. If this keyword is used while configuring the meter, counter is allocated.
aggregate-meter-rate
Syntax
aggregate-meter-rate rate-in-kbps [burst burst-in-kbits]
no aggregate-meter-rate
Context
config>service>vpls>sap>ingress
config>service>epipe>sap>ingress
config>service>ies>sap>ingress
config>service>vprn>sap>ingress (not supported in access-uplink operating mode)
Platforms
Supported on all 7210 SAS platforms as described in this document, including platforms configured in the access-uplink operating mode; not supported on 7210 SAS-Sx 10/100GE
Description
This command configures the SAP ingress aggregate policer. The rate of the SAP ingress aggregate policer must be specified by the user. The user can optionally specify the burst size for the SAP aggregate policer. The aggregate policer monitors the ingress traffic on different FCs and determines the final disposition of the packet. The packet is either forwarded to an identified profile or dropped.
When operating the 7210 SAS in access-uplink mode, this command is available only for access SAPs; it is not supported for access-uplink SAPs.
The sum of CIR of the individual FCs configured under the SAP cannot exceed the PIR rate configured for the SAP. Though the 7210 SAS software does not block this configuration, it is not recommended for use.
The following table provides information about the final disposition of the packet based on the operating rate of the per FC policer and the per SAP aggregate policer.
Per FC meter operating rate |
Per FC assigned color |
SAP aggregate meter operating rate |
SAP aggregate meter color |
Final packet color |
|---|---|---|---|---|
Within CIR |
Green |
Within PIR |
Green |
Green or In-profile |
Within CIR1 |
Green |
Above PIR |
Red |
Green or In-profile |
Above CIR, Within PIR |
Yellow |
Within PIR |
Green |
Yellow or Out-of-Profile |
Above CIR, Within PIR |
Yellow |
Above PIR |
Red |
Red or Dropped |
Above PIR |
Red |
Within PIR |
Green |
Red or Dropped |
Above PIR |
Red |
Above PIR |
Red |
Red or Dropped |
When the SAP aggregate policer is configured, per FC policer can be only configured in ‟trtcm2” mode (RFC 4115).
The meter modes ‟srtcm” and ‟trtcm1” are used in the absence of an aggregate meter.
The SAP ingress meter counters increment the packet or octet counts based on the final disposition of the packet.
If ingress Frame-based accounting is used, the SAP aggregate meter rate accounts for the Ethernet frame overhead. The system accounts for 12 bytes of IFG and 8 bytes of start delimiter.
The no form of this command removes the aggregate policer from use.
Default
no aggregate-meter-rate
Parameters
- rate-in-kbps
Specifies the rate in kilobits per second.
- burst burst-in-kilobits
Specifies the burst size for the policer in kilobits. The burst size cannot be configured without configuring the rate.
filter
Syntax
filter [ip ip-filter-id]
filter [ipv6 ipv6-filter-id]
filter [mac mac-filter-id]
no filter [ip ip-filter-id]
no filter [ipv6 ipv6-filter-id]
no filter [mac mac-filter-id]
Context
config>service>epipe>sap>egress
config>service>epipe>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 with an ingress or egress SAP or IP interface.
Filter policies control the forwarding and dropping of packets based on IP matching criteria. Only one filter can be applied to a SAP at a time.
The filter command is used to associate a filter policy with a specified filter-id with an ingress or egress SAP. The filter-id must already be defined before the filter command is executed. If the filter policy does not exist, the operation fails and an error message is returned.
IP filters apply only to IP packets. Frames that do not contain IP packets are not subject to the filter and are always be passed, even if the filter's default action is to drop.
For filter support available on different 7210 SAS platforms, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Router Configuration Guide.
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
- Epipe
Both MAC and IP filters are supported on an Epipe service SAP.
Parameters
- ip ip-filter-id
Specifies IP filter policy. The filter ID must already exist within the created IP filters.
- ipv6 ipv6-filter-id
Specifies the IPv6 filter policy. The filter ID must already exist within the created IPv6 filters.
- mac mac-filter-id
Specifies the MAC filter policy. The specified filter ID must already exist within the created MAC filters. The filter policy must already exist within the created MAC filters.
meter-override
Syntax
[no] meter-override
Context
config>service>epipe>sap>ingress
config>service>vpls>sap>ingress
config>service>ies>interface>sap>ingress
config>service>vprn>interface>sap>ingress (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, within the SAP ingress contexts, is used to create a CLI node for specific overrides to one or more meters created on the SAP through the sap-ingress QoS policies.
The no form of this command is used to remove any existing meter overrides.
Default
no meter-overrides
meter
Syntax
meter meter-id [create]
no meter meter-id
Context
config>service>epipe>sap>ingress>meter-override
config>service>vpls>sap>ingress>meter-override
config>service>ies>interface>sap>ingress>meter-override
config>service>vprn>interface>sap>ingress>meter-override (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, within the SAP ingress contexts, is used to create a CLI node for specific overrides to a specific meter created on the SAP through a sap-ingress QoS policies.
The no form of this command is used to remove any existing overrides for the specified meter-id.
Parameters
- meter-id
The meter-id parameter is required when executing the meter command within the meter-overrides context. The specified meter-id must exist within the sap-ingress QoS policy applied to the SAP. If the meter is not currently used by any forwarding class or forwarding type mappings, the meter does not exist on the SAP. This does not preclude creating an override context for the meter-id.
- create
The create keyword is required when a meter meter-id override node is being created and the system is configured to expect explicit confirmation that a new object is being created. When the system is not configured to expect explicit confirmation, the create keyword is not required.
adaptation-rule
Syntax
adaptation-rule [pir adaptation-rule] [cir adaptation-rule]
no adaptation-rule
Context
config>service>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>ies>interface>sap>ingress>meter-override>meter
config>service>vprn>interface>sap>ingress>meter-override>meter (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 can be used to override specific attributes of the specified meter adaptation rule parameters. The adaptation rule controls the method used by the system to derive the operational CIR and PIR settings when the meter is provisioned in hardware. For the CIR and PIR parameters individually, the system attempts to find the best operational rate depending on the defined constraint.
The no form of this command removes any explicitly defined constraints used to derive the operational CIR and PIR created by the application of the policy. When a specific adaptation-rule is removed, the default constraints for rate and cir apply.
Default
no adaptation-rule
Parameters
- pir
The pir parameter defines the constraints enforced when adapting the PIR rate defined within the meter-override meter meter-id command. The pir parameter requires a qualifier that defines the constraint used when deriving the operational PIR for the queue. When the meter-override command is not specified, the default applies.
Note:When the meter mode in use is 'trtcm2', this parameter is interpreted as EIR value. For more information, see the description and relevant notes for meter modes in the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide.
- cir
Specifies the constraints enforced when adapting the CIR rate defined within the meter-override meter meter-id command. The cir parameter requires a qualifier that defines the constraint used when deriving the operational CIR for the queue. When the cir parameter is not specified, the default constraint applies.
- adaptation-rule
Specifies the criteria to use to compute the operational CIR and PIR values for this meter, while maintaining a minimum offset.
cbs
Syntax
cbs size [kbits | bytes | kbytes]
no cbs
Context
config>service>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>ies>interface>sap>ingress>meter-override>meter
config>service>vprn>interface>sap>ingress>meter-override>meter (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 provides a mechanism to override the default CBS for the meter. The committed burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the CBS value then the packets are marked as in-profile by the meter to indicate that the traffic is complying meter configured parameters.
The no form of this command returns the CBS size to the default value.
Default
32 kbits
Parameters
- size
Specifies the value in either kbits, kilobytes or bytes.
mbs
Syntax
mbs size [kbits | bytes | kbytes]
no mbs
Context
config>service>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>ies>interface>sap>ingress>meter-override>meter
config>service>vprn>interface>sap>ingress>meter-override>meter (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 provides a mechanism to override the default MBS for the meter. The maximum burst size parameter specifies the maximum burst size that can be transmitted by the source while still complying with the CIR. If the transmitted burst is lower than the MBS value, the packets are marked as in-profile by the meter to indicate that the traffic is complying meter configured parameters.
The no form of this command returns the MBS size to the default value.
Default
512kbits
Parameters
- size
Specifies the value in either kbits, kilobytes or bytes.
mode
Syntax
mode mode
no mode
Context
config>service>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>ies>interface>sap>ingress>meter-override>meter
config>service>vprn>interface>sap>ingress>meter-override>meter (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 within the SAP ingress meter-overrides contexts is used to override the sap-ingress QoS policy configured mode parameters for the specified meter-id.
The no form of this command is used to restore the policy defined metering and profiling mode to a meter.
Parameters
- mode
Specifies the rate mode of the meter-override.
rate
Syntax
rate cir cir-rate [pir pir-rate]
no rate
Context
config>service>epipe>sap>ingress>meter-override>meter
config>service>vpls>sap>ingress>meter-override>meter
config>service>ies>interface>sap>ingress>meter-override>meter
config>service>vprn>interface>sap>ingress>meter-override>meter (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 within the SAP ingress meter-overrides contexts is used to override the sap-ingress QoS policy configured rate parameters for the specified meter-id.
The no form of this command is used to restore the policy defined metering and profiling rate to a meter.
Default
max
The max default specifies the amount of bandwidth in kilobits per second (thousand bits per second). The max value is mutually exclusive to the pir-rate value.
Parameters
- pir-rate
Specifies the administrative PIR rate, in kilobits, for the queue. When the rate command is executed, a valid PIR setting must be explicitly defined. When the rate command has not been executed, the default PIR of max is assumed. Fractional values are not allowed and must be specified as a positive integer.
Note:When the meter mode is set to 'trtcm2' the PIR value is interpreted as the EIR value. For more information, see the 7210 SAS-Mxp, R6, R12, S, Sx, T Quality of Service Guide.
The actual PIR rate is dependent on the queue adaptation-rule parameters and the actual hardware where the queue is provisioned.
- cir-rate
The cir parameter overrides the default administrative CIR used by the queue. When the rate command is executed, a CIR setting is optional. When the rate command has not been executed or the cir parameter is not explicitly specified, the default CIR (0) is assumed. Fractional values are not allowed and must be specified as a positive integer.
qos
Syntax
qos policy-id
qos policy-id [enable-table-classification] (for 7210 SAS-Mxp Epipe ingress only)
no qos policy-id
Context
config>service>epipe>sap>ingress
config>service>epipe>sap>egress (7210 SAS-Mxp with Epipe)
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 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 associates 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.
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 from the service ingress policy, which require CAM resources, are ignored. Only meters from the service ingress policy are used (and the meters still require CAM resources). The IP DSCP classification policy configured in the SAP ingress policy is used to assign FC and profile. The default FC is assigned from the SAP ingress policy.
By default, if no specific QoS policy is associated with the SAP for ingress or egress, the default QoS policy is used.
The no form of this command removes the QoS policy association from the SAP, and the QoS policy reverts to the default.
Parameters
- policy-id
Specifies the ingress or egress policy ID to associate with SAP on ingress or egress. The policy ID must already exist.
- 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. This parameter is only supported on the 7210 SAS-Mxp.
Epipe Service SAP Statistics Commands
statistics
Syntax
statistics
Context
config>service>epipe>sap
Platforms
7210 SAS-T (both network and access uplink mode), 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC)
Description
Commands in this context configure the counters associated with SAP ingress and egress.
ingress
Syntax
ingress
Context
config>service>epipe>sap>statistics
Platforms
7210 SAS-T (both network and access uplink mode), 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC)
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>epipe>sap>statistics>ingress
Platforms
7210 SAS-T (network and access-uplink mode), 7210 SAS-Mxp, 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC), and 7210 SAS-Sx 10/100GE (standalone)
Description
This command sets the counter mode for the counters associated with SAP ingress meters (also known as policers). A pair of counters is available with each meter. These counters count different events based on the counter mode value.
The counter mode can be changed if an accounting policy is associated with a SAP. If the counter mode is changed, the counters associated with the meter are reset and the counts are cleared. If an accounting policy is in use when the counter mode is changed, a new record is written into the current accounting file.
The configuration information is not saved across a reboot.
Execute the following sequence of commands on the specified SAP to ensure that the correct statistics are collected when the counter-mode is changed:
Execute the command config>service>epipe>sap>no collect-stats, to disable writing of accounting records for the SAP.
Change the counter-mode to the needed option, execute the command config>service>epipe>sap>counter-mode {in-out-profile-count | forward-drop-count}.
Execute the command config>service>epipe>sap>collect-stats, to enable writing of accounting records for the SAP.
Default
in-out-profile-count
Parameters
- forward-drop-count
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
Counts on one counter the total in-profile packets and octets received on ingress of a SAP, and on 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>epipe>sap>statistics>ingress
config>service>epipe>spoke-sdp>statistics>ingress
Platforms
7210 SAS-T (network operating mode), 7210 SAS-Mxp, and 7210 SAS-Sx/S 1/10GE (standalone and standalone-VC)
Description
This command associates a counter which enables the counting of extra VLAN-tag dropped packets for the SAP or spoke-SDP. A limited number of counters are available for use.
The no form of this command removes the associated counter.
VLL SDP Commands
VLL SDP commands are supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode. Any exceptions are noted explicitly.
spoke-sdp
Syntax
spoke-sdp sdp-id[:vc-id] [no-endpoint] [create]
spoke-sdp sdp-id[:vc-id] endpoint endpoint-name
no spoke-sdp sdp-id[:vc-id]
Context
config>service>epipe
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).
The SDP has an operational state that determines the operational state of the SDP within the service. For example, if the SDP is administratively or operationally down, the SDP for the service is down.
The SDP must already exist in the config>service>sdp context to associate an SDP with an Epipe or VPL service. If the sdp-id is not already configured, an error message is generated. If the sdp-id does exist, a binding between the specific sdp-id and the service is created.
SDPs must be explicitly associated and bound to a service to allow far-end 7210 SAS devices to participate in the service.
The no form of this command removes the SDP binding from the service; the SDP configuration is not affected. When the binding is removed, no packets are forwarded to the far-end router.
Default
no sdp-id is bound to a service
Special Cases
- Epipe
At most, only one sdp-id can be bound to an Epipe service. Since an Epipe is a point-to-point service, it can have, at most, two end points. The two end points can be one SAP and one SDP or two SAPs. VC-switching VLLs are an exception. If the VLL is a ‟vc-switching” VLL, the two endpoints must both be SDPs.
Parameters
- sdp-id
Specifies the SDP identifier.
- vc-id
Specifies the virtual circuit identifier.
- no-endpoint
Keyword to remove the association of a spoke-SDP with an explicit endpoint name.
- endpoint-name
Specifies the name of the service endpoint.
- create
Keyword to create spoke-SDP.
control-word
Syntax
[no] control-word
Context
config>service>epipe>spoke-sdp
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This command provides the option to add a control word as part of the packet encapsulation for pseudowire types for which the control word is optional. These are Ethernet pseudowires (Epipe).
The configuration for the two directions of the pseudowire must match because the control word negotiation procedures described in Section 6.2 of RFC 4447 are not supported. The C-bit in the pseudowire FEC sent in the label mapping message is set to 1 when the control word is enabled. Otherwise, it is set to 0.
The service only comes up if the same C-bit value is signaled in both directions. If a spoke-SDP is configured to use the control word but the node receives a label mapping message with a C-bit clear, the node releases the label with the an ‟Illegal C-bit” status code as per Section 6.1 of RFC 4447. As soon as the user also enabled the control the remote peer, the remote peer withdraws its original label and sends a label mapping with the C-bit set to 1 and the VLL service is up in both nodes.
control-channel-status
Syntax
[no] control-channel-status
Context
config>service>epipe>spoke-sdp
Platforms
7210 SAS-T
Description
This command enables the configuration of static pseudowire status signaling on a spoke-SDP for which signaling for its SDP is set to OFF.
A control-channel-status no shutdown is allowed only if all of the following is true:
The system is using network chassis mode D
SDP signaling is off
The control-word is enabled (control-word by default is disabled)
The service type is Epipe or VPLS.
Mate SDP signaling is off (in vc-switched services)
pw-path-id is configured for this spoke
The no form of this command removes control channel status signaling form a spoke-SDP. It can only be removed if control channel status is shutdown.
Default
no control-channel-status
acknowledgment
Syntax
[no] acknowledgment
Context
config>service>epipe>spoke-sdp>control-channel-status
Platforms
7210 SAS-T
Description
This command enables the acknowledgment of control channel status messages. By default, no acknowledgment packets are sent.
refresh-timer
Syntax
refresh-timer value
no refresh-timer
Context
config>service>epipe>spoke-sdp>control-channel-status
Platforms
7210 SAS-T
Description
This command configures the refresh timer for control channel status signaling packets. By default, no refresh packets are sent.
Default
no refresh-timer
Parameters
- value
Specifies the refresh timer value.
request-timer
Syntax
request-timer request-timer request-timer-secs retry-timer retry-timer-secs timeout-multiplier multiplier
Context
config>service>epipe>spoke-sdp>control-channel-status
Platforms
7210 SAS-T
Description
This command configures the control channel status request mechanism. When it is configured, control channel status request procedures are used. These augment the procedures for control channel status messaging from RFC 6478. This command is mutually exclusive with a non-zero refresh-timer value.
Parameters
- request-timer
Specifies the interval at which pseudowire status messages, including a reliable delivery TLV, with the ‟request” bit set, are sent.
- retry-timer
Specifies the timeout interval if no response to a pseudowire status request is received. This parameter must be configured. A value of zero (0) disables retries.
- timeout-multiplier
Specifies the optional timeout multiplier for the retry timer. If a requesting node does not receive a valid response to a pseudowire status request within this multiplier value times the retry timer value, it assumes the pseudowire is down.
precedence
Syntax
precedence [precedence-value | primary]
no precedence
Context
config>service>epipe>spoke-sdp
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This command specifies the precedence of the SDP binding when there are multiple SDP bindings attached to one service endpoint. The value of zero can only be assigned to one SDP bind making it the primary SDP bind. When an SDP binding goes down, the next highest precedence SDP binding begins to forward traffic.
The no form of this command returns the precedence value to the default.
Default
4
Parameters
- precedence-value
Specifies the spoke-SDP precedence.
- primary
Specifies to make this the primary spoke-SDP.
pw-path-id
Syntax
[no] pw-path-id
Context
config>service>epipe>spoke-sdp
Platforms
7210 SAS-T
Description
This command configures an MPLS-TP Pseudowire Path Identifier for a spoke-SDP. All elements of the PW path ID must be configured to enable a spoke-SDP with a PW path ID.
For an IES or VPRN spoke-SDP, the pw-path-id is only valid for Ethernet spoke-SDPs.
The pw-path-id is only configurable if all of the following is true:
The system is using network chassis mode D
SDP signaling is off
Control-word is enabled (control-word is disabled by default)
The service type is epipe, vpls, or IES/VPRN interface
Mate SDP signaling is off for vc-switched services
The no form of this command deletes the PW path ID.
Default
no pw-path-id
agi
Syntax
agi agi
no agi
Context
config>service>epipe>spoke-sdp>pw-path-id
Platforms
7210 SAS-T
Description
This command configures the attachment group identifier for an MPLS-TP PW.
Parameters
- agi
Specifies the attachment group identifier.
saii-type2
Syntax
saii-type2 global-id:node-id:ac-id
no saii-type2
Context
config>service>epipe>spoke-sdp>pw-path-id
Platforms
7210 SAS-T
Description
This command configures the source individual attachment identifier (SAII) for an MPLS-TP spoke-SDP. If this is configured on a spoke-SDP for which vc-switching is also configured, that is, if it is at an S-PE, the values must match those of the taii-type2 of the mate spoke-SDP.
Parameters
- global-id
Specifies the global ID at the source PE or T-PE for the MPLS-TP PW for a spoke-SDP.
- node-id
Specifies the node ID at the source PE or T-PE for the MPLS-TP PW for a spoke-SDP.
- ac-id
Specifies the attachment circuit ID at the source PE or T-PE for the MPLS-TP PW for a spoke-SDP. If this node is the source of the PW, the AC ID must be set to a locally unique value.
taii-type2
Syntax
taii-type2 global-id:node-id:ac-id
no taii-type2
Context
config>service>epipe>spoke-sdp>pw-path-id
Platforms
7210 SAS-T
Description
This command configures the source individual attachment identifier (SAII) for an MPLS-TP spoke-SDP. If this is configured on a spoke-SDP for which vc-switching is also configured (it is at an S-PE), the values must match those of the taii-type2 of the mate spoke-SDP.
Parameters
- global-id
Specifies the global ID at the target PE or T-PE for the MPLS-TP PW for a spoke-SDP.
- node-id
Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke-SDP.
- ac-id
Specifies the attachment circuit ID at the target PE or T-PE for the MPLS-TP PW for a spoke-SDP. If this node is the source of the PW, the AC ID must be set to a locally unique value.
pw-status-signaling
Syntax
[no] pw-status-signaling
Context
config>service>epipe>spoke-sdp
Platforms
7210 SAS-T
Description
This command enables pseudowire status signaling for this spoke-SDP binding.
The no form of this command disables the status signaling.
Default
pw-status-signaling
vc-label
Syntax
[no] vc-label vc-label
Context
config>service>epipe>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
A VC egress value that indicates a specific connection.
vc-label
Syntax
[no] vc-label vc-label
Context
config>service>epipe>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 a VC ingress label value for a connection.
vlan-vc-tag
Syntax
vlan-vc-tag 0..4094
no vlan-vc-tag [0..4094]
Context
config>service>epipe>spoke-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.
spoke-sdp-fec
Syntax
spoke-sdp-fec
spoke-sdp-fec spoke-sdp-fec-id [fec fec-type] [aii-type aii-type] [create]
spoke-sdp-fec spoke-sdp-fec-id no-endpoint
spoke-sdp-fec spoke-sdp-fec-id [fec fec-type] [aii-type aii-type] [create] endpoint name [icb]
Context
config>service>epipe
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 SDP, using a dynamic MS-PW.
A spoke-SDP is treated like the equivalent of a traditional bridge ‟port” where flooded traffic received on the spoke-SDP is replicated on all other ‟ports” (other spoke and mesh SDPs or SAPs) and not transmitted on the port it was received.
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.
When using dynamic MS-PWs, the particular SDP to bind to is automatically selected based on the Target Attachment Individual Identifier (TAII) and the path to use, specified under spoke-SDP FEC. The selected SDP terminates on the first hop S-PE of the MS-PW. Therefore, an SDP must already be defined in the config>service>sdp context that reaches the first hop 7210 of the MS-PW. The 7210 associates an SDP with a service. If an SDP is not already configured, an error message is generated. If the sdp-id does exists, a binding between that sdp-id and the service is created.
It differs from the spoke-sdp command in that the spoke-sdp command creates a spoke-SDP binding that uses a PW with the PW ID FEC. However, the spoke-sdp-fec command enables PWs with other FEC types to be used. In Release 9.0, only the Generalized ID FEC (FEC129) may be specified using this command.
The no form of this command removes the SDP binding from the service. The SDP configuration is not affected; only the binding of the SDP to a service. When removed, no packets are forwarded to the far-end router.
Parameters
- spoke-sdp-fec-id
Specifies an unsigned integer value of the spoke-SDP.
- fec fec-type
Specifies an unsigned integer value for the type of the FEC used by the MS-PW.
- aii-type aii-type
Specifies an unsigned integer value for the Attachment Individual Identifier (AII) type used to identify the MS-PW endpoints.
- endpoint endpoint-name
Specifies the name of the service endpoint.
- no endpoint
Adds or removes a spoke-SDP association.
- icb
Configures the spoke-SDP as an inter-chassis backup SDP binding.
auto-config
Syntax
[no] auto-config
Context
config>service>epipe>spoke-sdp-fec
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This command enables single-sided automatic endpoint configuration of the spoke-SDP. The 7210 SAS acts as the passive T-PE for signaling this MS-PW.
Automatic Endpoint Configuration allows the configuration of a spoke-SDP endpoint without specifying the TAII associated with that spoke-SDP. It allows a single-sided provisioning model where an incoming label mapping message with a TAII that matches the SAII of that spoke-SDP to be automatically bound to that endpoint. In this mode, the far end T-PE actively initiates MS-PW signaling and sends the initial label mapping message using T-LDP, while the 7210 T-PE for which auto-config is specified, acts as the passive T-PE.
The auto-config command is blocked in CLI if signaling active has been enabled for this spoke-SDP. It it is only applicable to spoke-SDPs configured under the Epipe, IES and VPRN interface context.
The no form of this command means that the 7210 T-PE either acts as the active T-PE (if signaling active is configured) or automatically determines which 7210 initiates MS-PW signaling based on the prefix values configured in the SAII and TAII of the spoke-SDP. If the SAII has the greater prefix value, the 7210 initiates MS-PW signaling without waiting for a label mapping message from the far end. However, if the TAII has the greater value prefix, then the 7210 assumes that the far end T-PE initiates MS-PW signaling and waits for that label mapping message before responding with a T-LDP label mapping message for the MS-PW in the reverse direction.
Default
no auto-config
path
Syntax
path name
no path
Context
config>service>epipe>spoke-sdp-fec
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This command specifies the explicit path, containing a list of S-PE hops, that should be used for this spoke-SDP. The path-name should correspond to the name of an explicit path configured in the config>service>pw-routing context.
If no path is configured, each next-hop of the MS-PW used by the spoke-SDP is chosen locally at each T-PE and S-PE.
Default
no path
Parameters
- path-name
The name of the explicit path to be used, as configured under config>service>pw-routing.
precedence
Syntax
precedence precedence-value
precedence primary
no precedence
Context
config>service>epipe>spoke-sdp-fec
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This command specifies the precedence of the SDP binding when there are multiple SDP bindings attached to one service endpoint. The value of zero can only be assigned to one SDP bind making it the primary SDP bind. When an SDP binding goes down, the next highest precedence SDP binding begins to forward traffic.
The no form of this command returns the precedence value to the default.
Default
42
Parameters
- precedence-value
Specifies the spoke-SDP precedence.
- primary
Specifies to make this the primary spoke-SDP.
pw-template-bind
Syntax
pw-template-bind policy-id
no pw-template-bind
Context
config>service>epipe>spoke-sdp-fec
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This command binds the parameters included in a specific PW Template to a spoke-SDP.
The no form of this command removes the values from the configuration.
Parameters
- policy-id
Specifies the existing policy ID.
retry-count
Syntax
retry-count retry-count
no retry-count
Context
config>service>epipe>spoke-sdp-fec
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This optional command specifies the number of attempts software should make to reestablish the spoke-SDP after it has failed. After each successful attempt, the counter is reset to zero.
When the specified number is reached, no more attempts are made and the spoke-SDP is put into the shutdown state.
Use the no shutdown command to bring up the path after the retry limit is exceeded.
The no form of this command reverts the parameter to the default value.
Default
30
Parameters
- retry-count
Specifies the maximum number of retries before putting the spoke-SDP into the shutdown state.
retry-timer
Syntax
retry-timer retry-timer
no retry-timer
Context
config>service>epipe>spoke-sdp-fec
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This command specifies a retry-timer for the spoke-SDP. This is a configurable exponential back-off timer that determines the interval between retries to reestablish a spoke-SDP if it fails and a label withdraw message is received with the status code ‟AII unreachable”.
The no form of this command reverts the timer to its default value.
Default
30
Parameters
- retry-timer
Specifies the initial retry-timer value in seconds.
saii-type2
Syntax
saii-type2 global-id:prefix:ac-id
no saii-type2
Context
config>service>epipe>spoke-sdp-fec
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This command configures the source attachment individual identifier for the spoke-SDP. This is only applicable to FEC129 AII type 2.
Parameters
- global-id
Specifies the global ID of this 7210 T-PE. This value must correspond to one of the global_id values configured for a local-prefix under config>service>pw-routing>local-prefix context.
- prefix
Specifies the prefix on this 7210 T-PE that the spoke-SDP SDP is associated with. This value must correspond to one of the prefixes configured under config>service>pw-routing>local-prefix context.
- ac-id
Specifies an unsigned integer representing a locally unique identifier for the spoke-SDP.
taii-type2
Syntax
taii-type2 global-id:prefix:ac-id
no taii-type2
Context
config>service>epipe>spoke-sdp-fec
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode.
Description
This command configures the target attachment individual identifier for the spoke-SDP. This is only applicable to FEC129 AII type 2.
This command is blocked in CLI if this end of the spoke-SDP is configured for single-sided auto configuration (using the auto-config command).
Parameters
- global-id
Specifies the Global ID of this 7210 T-PE. This value must correspond to one of the global_id values configured for a local-prefix under config>service>pw-routing>local-prefix context.
- prefix
Specifies the prefix on this 7210 T-PE that the spoke-SDP is associated with. This value must correspond to one of the prefixes configured under config>service>pw-routing>local-prefix context.
- ac-id
Specifies an unsigned integer representing a locally unique identifier for the spoke-SDP.
Connection profile commands
connection-profile
Syntax
connection-profile conn-prof-id [create]
no connection-profile conn-prof-id
Context
config
Platforms
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
Description
This command creates a list of VLAN values to be assigned to a Dot1q SAP in an Epipe service.
A connection profile can only be assigned to a Dot1q SAP which is part of an Epipe service.
The no form of this command deletes the profile from the configuration.
Parameters
- conn-prof-id
Specifies the profile number.
ethernet
Syntax
ethernet
Context
config>connprof
Platforms
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
Description
This command provides the context to configure the VLAN ranges values.
ranges
Syntax
no ranges
ranges vlan-ranges [vlan-ranges...(up to 32 max)]
Context
config>connprof>ethernet
Platforms
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
Description
Specifies the list of VLAN ranges or individual VLAN ID to be used for mapping the specific VLANs to the Epipe SAP.
The system validates that the values specified are valid VLAN ID in the range 0-4094 (VLAN ID 4095 is reserved). Ranges are specified in the format ‛a-b ’, the expression (a < b) should be true. Up to about 32 individual VLAN values or VLAN ranges can be specified. A maximum of up to 8 VLAN ranges are allowed per connection profile.
Parameters
- vlan-ranges
Specifies the list of VLAN ranges or individual VLAN ID to be used for mapping the specific VLANs to the Epipe SAP.
A list of space separated values specified as either a-b or individual VLAN IDs. Both the VLAN IDs and the value used for 'a' and 'b' must be in the range of 0-4094. Additionally, value 'a' must be less than value 'b'.
For example:
ranges
100-200 5 6 4000-4020
ranges
4 5 6 10 11 12
ranges
250-350 500-600 1000-1023
Show commands
id
Syntax
id service-id {all | arp | base | endpoint | fdb | interface | label | labels | sap | split-horizon-group | stp| interface | mstp-configuration}
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
Display the service identification number that identifies the service in the domain.
- all
Displays more information about the service.
- arp
Displays ARP entries for the service.
- base
Displays basic service information.
- endpoint
Displays service endpoint information.
- fdb
Displays FDB information.
- interface
Displays service interfaces.
- 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. This keyword in not supported on 7210 SAS platforms operating in access-uplink mode.
- split-horizon-group
Displays split horizon group information.
- stp
Displays STP information.
Output
The following output is an example of information for a specific service ID.
Sample output*A:ces-A# show service id 1 sap
=========================================================================
SAP(Summary), Service 1
=========================================================================
PortId SvcId Ing. Ing. Egr. Adm Opr
QoS Fltr Fltr
-------------------------------------------------------------------------
1/2/1.1 1 1 none none Up Up
-------------------------------------------------------------------------
Number of SAPs : 1
-------------------------------------------------------------------------
=========================================================================
*A:Dut-A# /show service id 1 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 1 Vpn Id : 0
Service Type : VPLS
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1 Creation Origin : manual
Last Status Change: 03/20/2023 12:49:45
Last Mgmt Change : 03/20/2023 12:49:45
Admin State : Up Oper State : Up
MTU : 1514 Def. Mesh VC Id : 1
MTU Check : Enabled
SAP Count : 1 SDP Bind Count : 1
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
SAP Type: : Any
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Allow IP Intf Bind: Disabled Fwd-IPv4-Mcast-To*: Disabled
VSD Domain : <none>
SPI load-balance : Disabled
TEID load-balance : Disabled
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:1/1/21 null 1514 1514 Up Up
sdp:1:1 S(2.2.2.2) Spok 0 9190 Up Up
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:Dut-A#
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 detailed information for all aspects of the service.
Output
The following outputs are examples of detailed service information, and the associated tables describe the output fields.
Sample output — Standard*A:Dut-A>show>service>id# all
===============================================================================
Service Detailed Information
===============================================================================
Service Id : 1501 Vpn Id : 1501
Service Type : Epipe
Description : Default epipe description for service id 1501
Customer Id : 1
Last Status Change: 02/21/2011 13:07:03
Last Mgmt Change : 02/21/2011 13:03:58
Admin State : Up Oper State : Up
MTU : 1514
MTU Check : Enabled
Vc Switching : False
SAP Count : 1 SDP Bind Count : 2
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Sdp Id 1413:1501 -(10.20.1.4)
-------------------------------------------------------------------------------
Description : Default sdp description
SDP Id : 1413:1501 Type : Spoke
VC Type : Ether VC Tag : n/a
Admin Path MTU : 0 Oper Path MTU : 9182
Far End : 10.20.1.4 Delivery : MPLS
Admin State : Up Oper State : Up
Acct. Pol : 14 Collect Stats : Enabled
Ingress Label : 130948 Egress Label : 130483
Ing mac Fltr : n/a Egr mac Fltr : n/a
Ing ip Fltr : n/a Egr ip Fltr : n/a
Admin ControlWord : Preferred Oper ControlWord : True
Admin BW(Kbps) : 0 Oper BW(Kbps) : 0
Last Status Change : 02/21/2011 13:07:12 Signaling : TLDP
Last Mgmt Change : 02/21/2011 13:03:58 Force Vlan-Vc : Disabled
Endpoint : coreSide Precedence : 1
Class Fwding State : Down
Flags : None
Peer Pw Bits : None
Peer Fault Ip : None
Peer Vccv CV Bits : lspPing
Peer Vccv CC Bits : pwe3ControlWord mplsRouterAlertLabel
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. : 48319 I. Fwd. Octs. : 5690869
E. Fwd. Pkts. : 34747 E. Fwd. Octets : 4013709
-------------------------------------------------------------------------------
Eth-Cfm Configuration Information
-------------------------------------------------------------------------------
Md-index : 1000 Direction : Down
Ma-index : 1150114 Admin : Enabled
MepId : 1 CCM-Enable : Enabled
LowestDefectPri : macRemErrXcon HighestDefect : none
Defect Flags : None
Mac Address : 7c:20:64:ad:04:07 ControlMep : False
CcmLtmPriority : 7
CcmTx : 11385 CcmSequenceErr : 0
Eth-1Dm Threshold : 3(sec)
Eth-Ais: : Disabled
Eth-Tst: : Disabled
LbRxReply : 0 LbRxBadOrder : 0
LbRxBadMsdu : 0 LbTxReply : 0
LbNextSequence : 1 LtNextSequence : 1
LtRxUnexplained : 0
Associated LSP LIST :
Lsp Name : A_D_21
Admin State : Up Oper State : Up
Time Since Last Tr*: 03h49m30s
-------------------------------------------------------------------------------
Sdp Id 1613:1501 -(10.20.1.6)
-------------------------------------------------------------------------------
Description : Default sdp description
SDP Id : 1613:1501 Type : Spoke
VC Type : Ether VC Tag : n/a
Admin Path MTU : 0 Oper Path MTU : 9182
Far End : 10.20.1.6 Delivery : MPLS
Admin State : Up Oper State : Up
Acct. Pol : 14 Collect Stats : Enabled
Ingress Label : 130526 Egress Label : 130424
Ing mac Fltr : n/a Egr mac Fltr : n/a
Ing ip Fltr : n/a Egr ip Fltr : n/a
Admin ControlWord : Not Preferred Oper ControlWord : False
Admin BW(Kbps) : 0 Oper BW(Kbps) : 0
Last Status Change : 02/21/2011 13:07:03 Signaling : TLDP
Last Mgmt Change : 02/21/2011 13:03:58 Force Vlan-Vc : Disabled
Endpoint : coreSide Precedence : 2
Class Fwding State : Down
Flags : None
Peer Pw Bits : pwFwdingStandby
Peer Fault Ip : None
Peer Vccv CV Bits : lspPing
Peer Vccv CC Bits : mplsRouterAlertLabel
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. : 25 I. Fwd. Octs. : 2776
E. Fwd. Pkts. : 23 E. Fwd. Octets : 2557
-------------------------------------------------------------------------------
Eth-Cfm Configuration Information
-------------------------------------------------------------------------------
Md-index : 1000 Direction : Down
Ma-index : 1150116 Admin : Enabled
MepId : 1 CCM-Enable : Enabled
LowestDefectPri : macRemErrXcon HighestDefect : none
Defect Flags : None
Mac Address : 7c:20:64:ad:04:07 ControlMep : False
CcmLtmPriority : 7
CcmTx : 11414 CcmSequenceErr : 0
Eth-1Dm Threshold : 3(sec)
Eth-Ais: : Disabled
Eth-Tst: : Disabled
LbRxReply : 0 LbRxBadOrder : 0
LbRxBadMsdu : 0 LbTxReply : 0
LbNextSequence : 1 LtNextSequence : 1
LtRxUnexplained : 0
Associated LSP LIST :
Lsp Name : A_F_21
Admin State : Up Oper State : Up
Time Since Last Tr*: 03h48m45s
-------------------------------------------------------------------------------
Number of SDPs : 2
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Service Access Points
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
SAP lag-3:1501.1501
-------------------------------------------------------------------------------
Service Id : 1501
SAP : lag-3:1501.1501 Encap : qinq
QinQ Dot1p : Default
Description : (Not Specified)
Admin State : Up Oper State : Up
Flags : None
Last Status Change : 02/21/2011 13:06:45
Last Mgmt Change : 02/21/2011 13:03:58
Admin MTU : 9212 Oper MTU : 9212
Ingr IP Fltr-Id : n/a Egr IP Fltr-Id : n/a
Ingr Mac Fltr-Id : 1501 Egr Mac Fltr-Id : n/a
tod-suite : None
Egr Agg Rate Limit : max
Endpoint : accessSide
Acct. Pol : Default Collect Stats : Enabled
-------------------------------------------------------------------------------
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 1500 Egress qos-policy : 1500
-------------------------------------------------------------------------------
Sap Egress Policy (1500)
-------------------------------------------------------------------------------
Scope : Template
Remark : False Remark Pol Id : 2
Accounting : frame-based
Description : Sap Egress Policy for svcList 1500
-------------------------------------------------------------------------------
Queue Rates and Rules
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId CIR CIR Adpt Rule PIR PIR Adpt Rule
-------------------------------------------------------------------------------
Queue1 10000 max 10000 max
Queue2 10000 max 10000 max
Queue3 10000 max 10000 max
Queue4 10000 max 10000 max
Queue5 10000 max 10000 max
Queue6 10000 max 10000 max
Queue7 10000 max 10000 max
Queue8 10000 max 10000 max
-------------------------------------------------------------------------------
Parent Details
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId Port CIR Level PIR Weight
-------------------------------------------------------------------------------
Queue1 True 1 1
Queue2 True 2 2
Queue3 True 3 3
Queue4 True 4 4
Queue5 True 5 5
Queue6 True 6 6
Queue7 True 7 7
Queue8 True 8 8
-------------------------------------------------------------------------------
High Slope
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId State Start-Avg(%) Max-Avg(%) Max-Prob(%)
-------------------------------------------------------------------------------
Queue1 Up 50 100 50
Queue2 Up 50 100 50
Queue3 Up 50 100 50
Queue4 Up 50 100 50
Queue5 Up 50 100 50
Queue6 Up 50 100 50
Queue7 Up 50 100 50
Queue8 Up 50 100 50
-------------------------------------------------------------------------------
Low Slope
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId State Start-Avg(%) Max-Avg(%) Max-Prob(%)
-------------------------------------------------------------------------------
Queue1 Up 10 50 50
Queue2 Up 10 50 50
Queue3 Up 10 50 50
Queue4 Up 10 50 50
Queue5 Up 10 50 50
Queue6 Up 10 50 50
Queue7 Up 10 50 50
Queue8 Up 10 50 50
-------------------------------------------------------------------------------
Burst Sizes and Time Average Factor
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
QueueId CBS MBS Time Average Factor Queue-Mgmt
-------------------------------------------------------------------------------
Queue1 200 400 10 qM_1500
Queue2 200 400 10 qM_1500
Queue3 200 400 10 qM_1500
Queue4 200 400 10 qM_1500
Queue5 200 400 10 qM_1500
Queue6 200 400 10 qM_1500
Queue7 200 400 10 qM_1500
Queue8 200 400 10 qM_1500
-------------------------------------------------------------------------------
Aggregate Policer (Available)
-------------------------------------------------------------------------------
rate : n/a burst : n/a
-------------------------------------------------------------------------------
Ingress QoS Classifier Usage
-------------------------------------------------------------------------------
Classifiers Allocated: 32 Meters Allocated : 16
Classifiers Used : 8 Meters Used : 5
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
Packets Octets
Ingress Stats: 34659 3241035
Egress Stats: 48099 5291928
Extra-Tag Drop Stats: n/a n/a
-------------------------------------------------------------------------------
Sap per Meter stats
-------------------------------------------------------------------------------
Packets Octets
Ingress Meter 1 (Unicast)
For. InProf : 7209 468585
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 : 0 0
For. OutProf : 0 0
Ingress Meter 5 (Unicast)
For. InProf : 27454 2772854
For. OutProf : 0 0
-------------------------------------------------------------------------------
Sap per Queue stats
-------------------------------------------------------------------------------
Packets Octets
Egress Queue 1 (be)
Fwd Stats : 0 0
Drop InProf : 0 0
Drop OutProf : 0 0
Egress Queue 2 (l2)
Fwd Stats : 3 180
Drop InProf : 0 0
Drop OutProf : 0 0
Egress Queue 3 (af)
Fwd Stats : 0 0
Drop InProf : 0 0
Drop OutProf : 0 0
Egress Queue 4 (l1)
Fwd Stats : 0 0
Drop InProf : 0 0
Drop OutProf : 0 0
Egress Queue 5 (h2)
Fwd Stats : 0 0
Drop InProf : 0 0
Drop OutProf : 0 0
Egress Queue 6 (ef)
Fwd Stats : 0 0
Drop InProf : 0 0
Drop OutProf : 0 0
Egress Queue 7 (h1)
Fwd Stats : 0 0
Drop InProf : 0 0
Drop OutProf : 0 0
Egress Queue 8 (nc)
Fwd Stats : 20842 1938306
Drop InProf : 0 0
Drop OutProf : 0 0
-------------------------------------------------------------------------------
Service Endpoints
-------------------------------------------------------------------------------
Endpoint name : coreSide
Description : (Not Specified)
Revert time : 0
Act Hold Delay : 0
Standby Signaling Master : true
Tx Active : 1413:1501
Tx Active Up Time : 0d 03:48:41
Revert Time Count Down : N/A
Tx Active Change Count : 2
Last Tx Active Change : 02/21/2011 13:07:12
-------------------------------------------------------------------------------
Members
-------------------------------------------------------------------------------
Spoke-sdp: 1413:1501 Prec:1 Oper Status: Up
Spoke-sdp: 1613:1501 Prec:2 Oper Status: Up
===============================================================================
Endpoint name : accessSide
Description : (Not Specified)
Revert time : 0
Act Hold Delay : 0
Standby Signaling Master : false
Tx Active : lag-3:1501.1501
Tx Active Up Time : 0d 03:49:08
Revert Time Count Down : N/A
Tx Active Change Count : 1
Last Tx Active Change : 02/21/2011 13:06:45
-------------------------------------------------------------------------------
Members
-------------------------------------------------------------------------------
SAP : lag-3:1501.1501 Oper Status: Up
===============================================================================
===============================================================================
*A:7210SAS>config>service# /show service id 1 all
===============================================================================
Service Detailed Information
===============================================================================
Service Id : 1 Vpn Id : 0
Service Type : VPLS
Name : (Not Specified)
Description : (Not Specified)
Customer Id : 1
Last Status Change: 01/07/2000 21:19:14
Last Mgmt Change : 01/07/2000 21:15:25
Admin State : Up Oper State : Up
MTU : 1514 Def. Mesh VC Id : 1
MTU Check : Enabled
SAP Count : 0 SDP Bind Count : 1
Snd Flush on Fail : Disabled Host Conn Verify : Disabled
SAP Type: : Any
Propagate MacFlush: Disabled Per Svc Hashing : Disabled
Allow IP Intf Bind: Disabled
-------------------------------------------------------------------------------
Split Horizon Group specifics
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
ETH-CFM service specifics
-------------------------------------------------------------------------------
Tunnel Faults : ignore V-Mep Extensions : Enabled
-------------------------------------------------------------------------------
Service Destination Points(SDPs)
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
Sdp Id 1:1 -(2.2.2.2)
-------------------------------------------------------------------------------
Description : (Not Specified)
SDP Id : 1:1 Type : Spoke
Spoke Descr : (Not Specified)
Split Horiz Grp : (Not Specified)
VC Type : Ether VC Tag : n/a
Admin Path MTU : 0 Oper Path MTU : 9190
Far End : 2.2.2.2 Delivery : MPLS
Tunnel Far End : 2.2.2.2 LSP Types : LDP
Hash Label : Enabled Hash Lbl Sig Cap : Disabled
Oper Hash Label : Enabled
Admin State : Up Oper State : Up
Acct. Pol : None Collect Stats : Disabled
Ingress Label : 131069 Egress Label : 131069
Ingr Mac Fltr-Id : n/a Egr Mac Fltr-Id : n/a
Ingr IP Fltr-Id : n/a Egr IP Fltr-Id : n/a
Ingr IPv6 Fltr-Id : n/a Egr IPv6 Fltr-Id : n/a
Admin ControlWord : Not Preferred Oper ControlWord : False
Last Status Change : 01/07/2000 21:19:14 Signaling : TLDP
Last Mgmt Change : 01/07/2000 21:15:25 Force Vlan-Vc : Disabled
Endpoint : N/A Precedence : 4
PW Status Sig : Enabled
Class Fwding State : Down
Flags : None
Local Pw Bits : None
Peer Pw Bits : None
Peer Fault Ip : None
Application Profile: None
Transit Policy : 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
BPDU Translation : Disabled
L2PT Termination : Disabled
MAC Pinning : Disabled
Ignore Standby Sig : False Block On Mesh Fail: False
Oper Group : (none) Monitor Oper Grp : (none)
Rest Prot Src Mac : Disabled
Auto Learn Mac Prot: Disabled RestProtSrcMacAct : Disable
Ingress Qos Policy : (none) Egress Qos Policy : (none)
Ingress FP QGrp : (none) Egress Port QGrp : (none)
Ing FP QGrp Inst : (none) Egr Port QGrp Inst: (none)
KeepAlive Information :
Admin State : Disabled Oper State : Disabled
Hello Time : 10 Hello Msg Len : 0
Max Drop Count : 3 Hold Down Time : 10
Statistics :
I. Fwd. Pkts. : 0 I. Fwd. Octs. : 0
E. Fwd. Pkts. : 0 E. Fwd. Octets : 0
Extra-Tag-Drop-Pkts: n/a Extra-Tag-Drop-Oc*: n/a
-------------------------------------------------------------------------------
Control Channel Status
-------------------------------------------------------------------------------
PW Status : disabled Refresh Timer : <none>
Peer Status Expire : false
Request Timer : <none>
Acknowledgement : false
-------------------------------------------------------------------------------
ETH-CFM SDP-Bind specifics
-------------------------------------------------------------------------------
V-MEP Filtering : Disabled
-------------------------------------------------------------------------------
LDP Information :
-------------------------------------------------------------------------------
LDP LSP Id : 65537
-------------------------------------------------------------------------------
RSVP/Static LSPs
-------------------------------------------------------------------------------
Associated LSP List :
No LSPs Associated
-------------------------------------------------------------------------------
Stp Service Destination Point specifics
-------------------------------------------------------------------------------
Stp Admin State : Up Stp Oper State : Down
Core Connectivity : Down
Port Role : N/A Port State : Forwarding
Port Number : 0 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
TC bit BPDUs rcvd : 0 TC bit 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.
-------------------------------------------------------------------------------
Service Access Points
-------------------------------------------------------------------------------
No Sap Associations
-------------------------------------------------------------------------------
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.c4:08:4a:59:b2:61 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: 0
Rcvd Hello Time : 0 Root Max Age : 0
Root Priority : 0 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
OAM-learned Count : 0 DHCP-learned 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
-------------------------------------------------------------------------------
IGMP Snooping Base info
-------------------------------------------------------------------------------
Admin State : Down
Querier : No querier found
-------------------------------------------------------------------------------
Sap/Sdp Oper MRtr Send Max MVR Num
Id State Port Qries Grps From-VPLS Grps
-------------------------------------------------------------------------------
sdp:1:1 Up No No None N/A 0
-------------------------------------------------------------------------------
Service Endpoints
-------------------------------------------------------------------------------
No Endpoints found.
-------------------------------------------------------------------------------
===============================================================================
VPLS Sites
===============================================================================
Site Site-Id Dest Mesh-SDP Admin Oper Fwdr
-------------------------------------------------------------------------------
|
Label |
Description |
|---|---|
|
Service Id |
The service identifier. |
|
VPN Id |
The number which identifies the VPN. |
|
Service Type |
The type of service. |
|
VLL Type |
The VLL type. |
|
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. |
|
Endpoint |
The name of the service endpoint. |
|
Flags |
The conditions that affect the operating status of this SAP. Display output includes: ServiceAdminDown, SapAdminDown, InterfaceAdminDown, PortOperDown, L2OperDown, RelearnLimitExceeded, RxProtSrcMac, ParentIfAdminDown, TodResourceUnavail, TodMssResourceUnavail, SapParamMismatch, SapIngressNamedPoolMismatch, SapEgressNamedPoolMismatch, NoSapEpipeRingNode. |
|
SAP Count |
The number of SAPs specified for this service. |
|
SDP Bind Count |
The number of SDPs bound to this service. |
|
Service Destination Points (SDPs) |
|
|
SDP Id |
The SDP identifier. |
|
Type |
Indicates whether this Service SDP binding is a spoke or a mesh. |
|
Admin Path MTU |
The needed 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. |
|
Jitter Buffer (packets) |
The jitter buffer length in number of packet buffers. |
|
Playout Threshold (packets) |
The playout buffer packets threshold in number of packet buffers. |
|
Playout Threshold (packets) |
The current packet depth of the jitter buffer. |
|
Peer Pw Bits |
The bits set by the LDP peer when there is a fault on its side of the pseudowire. LAC failures occur on the SAP that has been configured on the pipe service, PSN bits are set by SDP-binding failures on the pipe service. The pwNotForwarding bit is set when none of the preceding failures apply, such as an MTU mismatch failure. This value is only applicable if the peer is using the pseudowire status signalling method to indicate faults. pwNotForwarding — Pseudowire not forwarding lacIngressFault Local — Attachment circuit RX fault lacEgresssFault Local — Attachment circuit TX fault psnIngressFault Local — PSN-facing PW RX fault psnEgressFault Local — PSN-facing PW TX fault pwFwdingStandby — Pseudowire in standby mode |
|
LLF Admin State |
The Link Loss Forwarding administrative state. |
|
LLF Oper State |
The Link Loss Forwarding operational state. |
|
Standby Signaling Master |
If the parameter standby signaling master is enabled. |
|
Hash Label |
If use of PW hash label is enabled or not. |
|
Oper Hash Label |
If MPLS packet originated by the node, is using PW Hash label if the value displayed is "Enabled". If the value displayed is "Disabled", the MPLS packets originated by the node is not using Pseudowire Hash label. |
|
Hash Lbl Sig Cap |
If PW hash label signaling is enabled or not. |
A:7210SAS>show>service# id 1101 sap 1/2/1:1 detail
Ingress Meter Override
-------------------------------------------------------------------------------
Meter Id : 1
Admin PIR : 12000 Admin CIR : 10000
Oper PIR : 12000 Oper CIR : 10000
PIR Rule : closest* CIR Rule : closest*
MBS : 20 KBytes CBS : 15 Kbytes
Mode : Trtcm2*
* means the value is inherited
-------------------------------------------------------------------------------
A:7210SAS>show>service#
base
Syntax
base
Context
show>service>id
Platforms
Supported on all 7210 SAS platforms as described in this document, including those operating in access-uplink mode
Description
Displays basic information about the service ID including service type, description, SAPs.
Output
The following output is an example of basic service information, and Output fields: base describes the output fields.
Sample outputA:Dut-A# show service id 1101 base
===============================================================================
Service Basic Information
===============================================================================
Service Id : 1101 Vpn Id : 1101
Service Type : Epipe
Description : Default epipe description for service id 1101
Customer Id : 1
Last Status Change: 07/07/2009 18:13:43
Last Mgmt Change : 07/07/2009 14:39:14
Admin State : Up Oper State : Up
MTU : 1514
Vc Switching : False
SAP Count : 1 SDP Bind Count : 1
-------------------------------------------------------------------------------
Service Access & Destination Points
-------------------------------------------------------------------------------
Identifier Type AdmMTU OprMTU Adm Opr
-------------------------------------------------------------------------------
sap:lag-4:1101 q-tag 9212 9212 Up Up
sdp:1409:1101 S(10.20.1.4) n/a 0 9186 Up Up
===============================================================================
A:Dut-A#|
Label |
Description |
|---|---|
|
Service Id |
The service identifier. |
|
Vpn Id |
Specifies the VPN ID assigned to the service. |
|
Service Type |
The type of service: Epipe, VPLS |
|
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 desired state of the service. |
|
Oper |
The operating state of the service. |
|
Mtu |
The largest frame size (in octets) that the service can handle. |
|
Def. Mesh VC Id |
This object is only valid in services that accept mesh SDP bindings. It is used to validate the VC ID portion of each mesh SDP binding defined in the service. |
|
SAP Count |
The number of SAPs defined on the service. |
|
SDP Bind Count |
The number of SDPs bound to the service. |
|
Identifier |
Specifies the service access (SAP) points. |
|
Type |
Specifies the signaling protocol used to obtain the ingress and egress labels used in frames transmitted and received. |
|
AdmMTU |
Specifies the desired largest service frame size (in octets) that can be transmitted through this SAP, without requiring the packet to be fragmented. |
|
PBB Tunnel Point |
Specifies the endpoint in the B-VPLS environment where the Epipe terminates. |
|
Admin MTU |
Specifies the B-VPLS admin MTU. |
|
Backbone-Flooding |
Specifies whether or not the traffic is flooded in the B-VPLS for the destination instead of unicast. If the backbone destination MAC is in the B-VPLS FDB, it is unicast. |
|
ISID |
The 24 bit field carrying the service instance identifier associated with the frame. It is used at the destination PE as a demultiplexor field. |
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 the name of an existing endpoint for the service.
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-A>show>service>id# endpoint
===============================================================================
Service 1501 endpoints
===============================================================================
Endpoint name : coreSide
Description : (Not Specified)
Revert time : 0
Act Hold Delay : 0
Standby Signaling Master : true
Tx Active : 1413:1501
Tx Active Up Time : 0d 03:46:25
Revert Time Count Down : N/A
Tx Active Change Count : 2
Last Tx Active Change : 02/21/2011 13:07:12
-------------------------------------------------------------------------------
Members
-------------------------------------------------------------------------------
Spoke-sdp: 1413:1501 Prec:1 Oper Status: Up
Spoke-sdp: 1613:1501 Prec:2 Oper Status: Up
===============================================================================
Endpoint name : accessSide
Description : (Not Specified)
Revert time : 0
Act Hold Delay : 0
Standby Signaling Master : false
Tx Active : lag-3:1501.1501
Tx Active Up Time : 0d 03:46:52
Revert Time Count Down : N/A
Tx Active Change Count : 1
Last Tx Active Change : 02/21/2011 13:06:45
-------------------------------------------------------------------------------
Members
-------------------------------------------------------------------------------
SAP : lag-3:1501.1501 Oper Status: Up
===============================================================================
===============================================================================
|
Label |
Description |
|---|---|
|
Service endpoints |
|
|
Endpoint name |
Identifies the endpoint. |
|
Revert time |
Displays the revert time setting for the active spoke SDP. |
|
Act Hold Delay |
Not applicable. |
|
Ignore Standby Signaling |
Indicates whether standby signaling is ignored. True: standby signaling is ignored. False: standby signaling is not ignored. |
|
Suppress Standby Signaling |
Indicates whether standby signaling is suppressed. True: standby signaling is suppressed. False: standby signaling is not suppressed. |
|
Tx Active |
Identifies the actively transmitting spoke SDP. |
|
Tx Active Up Time |
Indicates the length of time that the active spoke SDP has been up. |
|
Revert Time Count Down |
Not applicable. |
|
Tx Active Change Count |
Indicates the number of times that there has been a change of active spoke SDPs. |
|
Last Tx Active Change |
Indicates the date and time when a different spoke SDP became the actively transmitting spoke SDP. |
|
Members |
|
|
Spoke-sdp |
Identifies the primary and secondary spoke SDPs that are associated with this endpoint and shows their precedence value (0 precedence indicates the primary spoke SDP). |
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:ALA-12# show service id 1 labels
==============================================================================
Martini Service Labels
==============================================================================
Svc Id Sdp Id Type I.Lbl E.Lbl
------------------------------------------------------------------------------
1 10:1 Mesh 0 0
1 20:1 Mesh 0 0
1 30:1 Mesh 0 0
1 40:1 Mesh 130081 131061
1 60:1 Mesh 131019 131016
1 100:1 Mesh 0 0
------------------------------------------------------------------------------
Number of Bound SDPs : 6
------------------------------------------------------------------------------
*A:ALA-12#
|
Label |
Description |
|---|---|
|
Svc Id |
The service identifier. |
|
Sdp Id |
The SDP identifier. |
|
Type |
Indicates whether the SDP is a spoke or a mesh. |
|
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. |
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-id
Displays SAPs for the service in the form slot/mda/port[.channel]. See Common CLI command descriptions for command syntax.
- interface interface-name
Displays information for the specified IP interface.
- ip-address ip-address
Displays information associated with the specified IP address.
- detail
Displays detailed information for the SAP.
Output
The following outputs are examples of SAP information, and Output fields: service ID SAP describes the output fields.
Sample outputA:Dut-A>config>service>epipe# show service id 2011 sap 1/1/18
===============================================================================
Service Access Points(SAP)
===============================================================================
Service Id : 2011
SAP : 1/1/18 Encap : null
Dot1Q Ethertype : 0x8100 QinQ Ethertype : 0x8100
Description : Default sap description for service id 2011
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
Admin MTU : 1514 Oper MTU : 1514
LLF Admin State : Up LLF Oper State : Clear
Ingress qos-policy : 10
Ingr IP Fltr-Id : n/a Egr IP Fltr-Id : n/a
Ingr Mac Fltr-Id : n/a Egr Mac Fltr-Id : n/a
tod-suite : None
Egr Agg Rate Limit : max Endpoint : N/A
Acct. Pol : None Collect Stats : Disabled
Ignore Oper Down : Disabled
===============================================================================
A:Dut-A>config>service>epipe#
A:Dut-A>config>service>epipe# show service id 2011 sap 1/1/18 detail
===============================================================================
Service Access Points(SAP)
===============================================================================
Service Id : 2011
SAP : 1/1/18 Encap : null
Dot1Q Ethertype : 0x8100 QinQ Ethertype : 0x8100
Description : Default sap description for service id 2011
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
Admin MTU : 1514 Oper MTU : 1514
LLF Admin State : Up LLF Oper State : Clear
Ingress qos-policy : 10
Ingr IP Fltr-Id : n/a Egr IP Fltr-Id : n/a
Ingr Mac Fltr-Id : n/a Egr Mac Fltr-Id : n/a
tod-suite : None
Egr Agg Rate Limit : max Endpoint : N/A
Acct. Pol : None Collect Stats : Disabled
Ignore Oper Down : Disabled
-------------------------------------------------------------------------------
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 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 : 0 0
For. OutProf : 0 0
===============================================================================
A:Dut-A>config>service>epipe#
*A:ces-A# show service id 1 sap 1/2/1.1 detail
===============================================================================
Service Access Points(SAP)
===============================================================================
Service Id : 1
SAP : 1/2/1.1 Encap : cem
Description : (Not Specified)
Admin State : Up Oper State : Up
Flags : None
Last Status Change : 07/06/2010 14:16:41
Last Mgmt Change : 07/06/2010 11:31:34
Admin MTU : 1514 Oper MTU : 1514
Endpoint : N/A
Acct. Pol : None Collect Stats : Disabled
Ignore Oper Down : Disabled
-------------------------------------------------------------------------------
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 1
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
Packets Octets
Ingress Stats: 2815 613670
Egress Stats: 2815 613670
-------------------------------------------------------------------------------
CEM SAP Configuration Information
-------------------------------------------------------------------------------
Endpoint Type : Unstruct. T1 Bit-rate : 24
Payload Size : 192 Jitter Buffer (ms) : 5
Jitter Buffer (packets): 6 Playout Threshold (packets): 4
Use RTP Header : No Differential : No
Timestamp Freq : 0 CAS Framing : No CAS
Effective PDVT : +/-2.984 ms
Cfg Alarm : stray malformed pktloss overrun underrun
Alarm Status :
-------------------------------------------------------------------------------
CEM SAP Statistics
-------------------------------------------------------------------------------
Packets Seconds Events
Egress Stats
Forwarded : 2915
Dropped : 0
Missing : 0
Reordered Forwarded : 0
Underrun : 0 0
Overrun : 0 0
Misordered Dropped : 0
Malformed Dropped : 0
LBit Dropped : 0
Multiple Dropped : 0
Error : 0
Severely Error : 0
Unavailable : 0
Failure Count : 0
Jitter Buffer Depth : 3
Ingress Stats
Forwarded : 2915
Dropped : 0
===============================================================================
*A:Dut-A>show# service id 104 sap 1/2/1.2 detail
===============================================================================
Service Access Points(SAP)
===============================================================================
Service Id : 104
SAP : 1/2/1.2 Encap : cem
Description : (Not Specified)
Admin State : Up Oper State : Up
Flags : None
Last Status Change : 12/15/2010 07:39:05
Last Mgmt Change : 12/15/2010 07:25:37
Admin MTU : 1514 Oper MTU : 1514
Endpoint : N/A
Acct. Pol : None Collect Stats : Disabled
Ignore Oper Down : Disabled
-------------------------------------------------------------------------------
QOS
-------------------------------------------------------------------------------
Ingress qos-policy : 1 Egress qos-policy : 1
-------------------------------------------------------------------------------
Aggregate Policer
-------------------------------------------------------------------------------
rate : n/a burst : n/a
-------------------------------------------------------------------------------
Sap Statistics
-------------------------------------------------------------------------------
Packets Octets
Ingress Stats: 786701 70803090
Egress Stats: 784531 70607790
Extra-Tag Drop Stats: n/a n/a
-------------------------------------------------------------------------------
CEM SAP Configuration Information
-------------------------------------------------------------------------------
Endpoint Type : NxDS0 Bit-rate : 1
Payload Size : 64 Jitter Buffer (ms) : 32
Jitter Buffer (packets): 4 Playout Threshold (packets): 3
Use RTP Header : No Differential : No
Timestamp Freq : 0 CAS Framing : No CAS
Effective PDVT : +/-16.0 ms
Cfg Alarm : stray malformed pktloss overrun underrun
Alarm Status :
-------------------------------------------------------------------------------
CEM SAP Statistics
-------------------------------------------------------------------------------
Packets Seconds Events
Egress Stats
Forwarded : 784407
Dropped : 132
Missing : 0
Reordered Forwarded : 0
Underrun : 2355 1
Overrun : 0 0
Misordered Dropped : 0
Malformed Dropped : 0
LBit Dropped : 132
Multiple Dropped : 0
Error : 1
Severely Error : 0
Unavailable : 18
Failure Count : 1
Jitter Buffer Depth : 2
Ingress Stats
Forwarded : 786762
Dropped : 0
===============================================================================
*A:Dut-A>show#
CLI output for 7210 SAS-T configured in access uplink mode:
*A:SAS-T-A0-2>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
Ignore Oper Down : 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
===============================================================================
*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
===============================================================================
|
Label |
Description |
|---|---|
|
Service Id |
The service identifier. |
|
SAP |
The SAP and qtag. |
|
Encap |
The encapsulation type of the SAP. |
|
Ethertype |
Specifies an Ethernet type II Ethertype value. |
|
Admin State |
The administrative state of the SAP. |
|
Oper State |
The operating state of the SAP. |
|
Flags |
Specifies the conditions that affect the operating status of this SAP. Display output includes: ServiceAdminDown, SapAdminDown, InterfaceAdminDown, PortOperDown, PortMTUTooSmall, L2OperDown, SapEgressQoSMismatch,RelearnLimitExceeded, RxProtSrcMac, ParentIfAdminDown, TodResourceUnavail, TodMssResourceUnavail, SapParamMismatch, ServiceMTUTooSmall, 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. |
|
Admin MTU |
The desired largest service frame size (in octets) that can be transmitted through the port 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 the port to the far-end router, without requiring the packet to be fragmented. |
|
Ingress qos-policy |
The ingress QoS policy ID assigned to the SAP. |
|
Egress qos-policy |
The egress 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 |
Indicates whether collect stats is enabled. |
|
Ignore Oper Down |
Whether the user has enabled or disabled ignore-oper-down parameter. |
|
LLF Admin State |
The Link Loss Forwarding administrative state. |
|
LLF Oper State |
The Link Loss Forwarding operational state. |
|
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 |
Indicates the use of table-based resource classification: Enabled (table-based) or Disabled (CAM-based) |
sdp
Syntax
sdp [sdp-id | far-end ip-addr] [detail]
Context
show>service>id
Platforms
Supported on all 7210 SAS platforms as described in this document, 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.
- far-end ip-addr
Displays only SDPs matching the specified far-end IP address.
- detail
Displays detailed SDP information.
Output
The following outputs are examples of service SDP information, and Output fields: service ID SDP describes the output fields.
Sample output 1A:Dut-A# show service id 1 sdp detail
===============================================================================
Services: Service Destination Points Details
===============================================================================
Sdp Id 1:1 -(10.20.1.2)
-------------------------------------------------------------------------------
Description : Default sdp description
SDP Id : 1:1 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
Ingress Label : 2048 Egress Label : 2048
Ing mac Fltr : n/a Egr mac Fltr : n/a
Ing ip Fltr : n/a Egr ip Fltr : n/a
Ing ipv6 Fltr : n/a Egr ipv6 Fltr : n/a
Admin ControlWord : Not Preferred Oper ControlWord : False
Last Status Change : 05/31/2007 00:45:43 Signaling : None
Last Mgmt Change : 05/31/2007 00:45:43
Class Fwding State : Up
Flags : None
Peer Pw Bits : None
Peer Fault Ip : None
Peer Vccv CV Bits : None
Peer Vccv CC Bits : 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 : Disabled Oper State : Disabled
Hello Time : 10 Hello Msg Len : 0
Max Drop Count : 3 Hold Down Time : 10
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
I. Fwd. Octs. : 0 I. Dro. Octs. : 0
E. Fwd. Pkts. : 0 E. Fwd. Octets : 0
MCAC Policy Name :
MCAC Max Unconst BW: no limit MCAC Max Mand BW : no limit
MCAC In use Mand BW: 0 MCAC Avail Mand BW: unlimited
MCAC In use Opnl BW: 0 MCAC Avail Opnl BW: unlimited
Associated LSP LIST :
Lsp Name : A_B_1
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m35s
Lsp Name : A_B_2
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m35s
Lsp Name : A_B_3
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m34s
Lsp Name : A_B_4
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m34s
Lsp Name : A_B_5
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m34s
Lsp Name : A_B_6
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m34s
Lsp Name : A_B_7
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m34s
Lsp Name : A_B_8
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m35s
Lsp Name : A_B_9
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m34s
Lsp Name : A_B_10
Admin State : Up Oper State : Up
Time Since Last Tr*: 00h26m34s
-------------------------------------------------------------------------------
Class-based forwarding :
-------------------------------------------------------------------------------
Class forwarding : enabled
Default LSP : A_B_10 Multicast LSP : A_B_9
===============================================================================
FC Mapping Table
===============================================================================
FC Name LSP Name
-------------------------------------------------------------------------------
af A_B_3
be A_B_1
ef A_B_6
h1 A_B_7
h2 A_B_5
l1 A_B_4
l2 A_B_2
nc A_B_8
===============================================================================
Stp Service Destination Point specifics
-------------------------------------------------------------------------------
Mac Move : Blockable
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
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#
|
Label |
Description |
|---|---|
|
Sdp Id |
The SDP identifier. |
|
Type |
Indicates whether the SDP is a spoke or a mesh. |
|
Split Horizon Group |
Name of the split horizon group that the SDP belongs to. |
|
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 |
Specifies the IP address of the remote end of the MPLS tunnel defined by this SDP. |
|
Delivery |
Specifies the type of delivery used by the SDP: MPLS. |
|
Admin State |
The administrative state of this SDP. |
|
Oper State |
The current state of this SDP. |
|
Ingress Label |
The label used by the far-end device to send packets to this device in this service by this SDP. |
|
Egress Label |
The label used by this device to send packets to the far-end device in this service by the SDP. |
|
Last Changed |
The date and time of the most recent change to the SDP. |
|
Signaling |
Specifies the signaling protocol used to obtain the ingress and egress labels used in frames transmitted and received on this SDP. |
|
Admin State |
The administrative state of the keepalive process. |
|
Oper State |
The operational state of the keepalive process. |
|
Hello Time |
Transmission frequency of the SDP echo request messages. |
|
Max Drop Count |
Specifies the maximum number of consecutive SDP echo request messages that can be unacknowledged before the keepalive protocol reports a fault. |
|
Hello Msg Len |
The length of the SDP echo request messages transmitted on this SDP. |
|
Hold Down Time |
Specifies the amount of time to wait before the keepalive operating status is eligible to enter the alive state. |
|
I. Fwd. Pkts. |
Specifies the number of forwarded ingress packets. |
|
I. Dro. Pkts |
Specifies the number of dropped ingress packets. |
|
E. Fwd. Pkts. |
Specifies the number of forwarded egress packets. |
|
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. |
The following output is an example of when both sides have the control word disabled.
*A:ALA-Dut-B>config>service>epipe# show service id 2100 sdp detail
===============================================================================
Services: Service Destination Points Details
===============================================================================
Sdp Id 1:2001 -(1.1.1.1)
-------------------------------------------------------------------------------
Description : Default sdp description
SDP Id : 1:2001 Type : Spoke
VC Type : Ether VC Tag : n/a
Admin Path MTU : 1600 Oper Path MTU : 1600
Far End : 1.1.1.1 Delivery : MPLS
Admin State : Up Oper State : Up
Acct. Pol : None Collect Stats : Disabled
Ingress Label : 115066 Egress Label : 119068
Ing mac Fltr : n/a Egr mac Fltr : n/a
Ing ip Fltr : n/a Egr ip Fltr : n/a
Ing ipv6 Fltr : n/a Egr ipv6 Fltr : n/a
Admin ControlWord : Not Preferred Oper ControlWord : False
Last Status Change : 02/05/2007 16:49:05 Signaling : TLDP
Last Mgmt Change : 02/05/2007 16:47:54
Flags : None
Peer Pw Bits : None
Peer Fault Ip : None
Peer Vccv CV Bits : None
Peer Vccv CC Bits : 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 : Disabled Oper State : Disabled
Hello Time : 10 Hello Msg Len : 0
Max Drop Count : 3 Hold Down Time : 10
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
E. Fwd. Pkts. : 0 E. Fwd. Octets : 0
Associated LSP LIST :
SDP Delivery Mechanism is not MPLS
-------------------------------------------------------------------------------
Number of SDPs : 1
===============================================================================
*A:ALA-Dut-B>config>service>epipe#
The following examples show both sides (PE nodes) when the control word is enabled.
*A:ALA-Dut-B>config>service>epipe# show service id 2100 sdp detail
===============================================================================
Services: Service Destination Points Details
-------------------------------------------------------------------------------
Sdp Id 1:2001 -(1.1.1.1)
-------------------------------------------------------------------------------
Description : Default sdp description
SDP Id : 1:2001 Type : Spoke
VC Type : Ether VC Tag : n/a
Admin Path MTU : 1600 Oper Path MTU : 1600
Far End : 1.1.1.1 Delivery : MPLS
Admin State : Up Oper State : Up
Acct. Pol : None Collect Stats : Disabled
Ingress Label : 115066 Egress Label : 119068
Ing mac Fltr : n/a Egr mac Fltr : n/a
Ing ip Fltr : n/a Egr ip Fltr : n/a
Ing ipv6 Fltr : n/a Egr ipv6 Fltr : n/a
Admin ControlWord : Preferred Oper ControlWord : True
Last Status Change : 02/05/2007 16:39:22 Signaling : TLDP
Last Mgmt Change : 02/05/2007 16:39:22
Class Fwding State : Up
Endpoint : N/A Precedence : 4
Flags : None
Peer Pw Bits : None
Peer Fault Ip : None
Peer Vccv CV Bits : None
Peer Vccv CC Bits : 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 : Disabled Oper State : Disabled
Hello Time : 10 Hello Msg Len : 0
Max Drop Count : 3 Hold Down Time : 10
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
E. Fwd. Pkts. : 0 E. Fwd. Octets : 0
Associated LSP LIST :
SDP Delivery Mechanism is not MPLS
-------------------------------------------------------------------------------
Number of SDPs : 1
===============================================================================
*A:ALA-Dut-B>config>service>epipe#
The following output is an example of when one side (PE) has the control word enabled (the pipe is down). The following is the side with the control word disabled.
*A:ALA-Dut-B>config>service>epipe# show service id 2100 sdp detail
===============================================================================
Services: Service Destination Points Details
===============================================================================
Sdp Id 1:2001 -(1.1.1.1)
-------------------------------------------------------------------------------
Description : Default sdp description
SDP Id : 1:2001 Type : Spoke
VC Type : Ether VC Tag : n/a
Admin Path MTU : 1600 Oper Path MTU : 1600
Far End : 1.1.1.1 Delivery : MPLS
Admin State : Up Oper State : Down
Acct. Pol : None Collect Stats : Disabled
Ingress Label : 115066 Egress Label : 119068
Ing mac Fltr : n/a Egr mac Fltr : n/a
Ing ip Fltr : n/a Egr ip Fltr : n/a
Ing ipv6 Fltr : n/a Egr ipv6 Fltr : n/a
Admin ControlWord : Not Preferred Oper ControlWord : False
Last Status Change : 02/05/2007 16:47:54 Signaling : TLDP
Last Mgmt Change : 02/05/2007 16:47:54
Flags : None
Peer Pw Bits : None
Peer Fault Ip : None
Peer Vccv CV Bits : None
Peer Vccv CC Bits : 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 : Disabled Oper State : Disabled
Hello Time : 10 Hello Msg Len : 0
Max Drop Count : 3 Hold Down Time : 10
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
E. Fwd. Pkts. : 0 E. Fwd. Octets : 0
Associated LSP LIST :
SDP Delivery Mechanism is not MPLS
-------------------------------------------------------------------------------
Number of SDPs : 1
===============================================================================
*A:ALA-Dut-B>config>service>epipe#
The following is the side with the control word enabled.
*A:ALA-B# show service id 2100 sdp detail
===============================================================================
Services: Service Destination Points Details
===============================================================================
Sdp Id 1:12000 -(3.3.3.3)
-------------------------------------------------------------------------------
Description : Default sdp description
SDP Id : 1:12000 Type : Spoke
VC Type : Ether VC Tag : n/a
Admin Path MTU : 1600 Oper Path MTU : 1600
Far End : 3.3.3.3 Delivery : MPLS
Admin State : Up Oper State : Down
Acct. Pol : None Collect Stats : Disabled
Ingress Label : 119066 Egress Label : 0
Ing mac Fltr : n/a Egr mac Fltr : n/a
Ing ip Fltr : n/a Egr ip Fltr : n/a
Ing ipv6 Fltr : n/a Egr ipv6 Fltr : n/a
Admin ControlWord : Preferred Oper ControlWord : True
Last Status Change : 02/04/2007 22:52:43 Signaling : TLDP
Last Mgmt Change : 02/04/2007 02:06:08
Flags : None
Peer Pw Bits : None
Peer Fault Ip : None
Peer Vccv CV Bits : None
Peer Vccv CC Bits : 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 : Disabled Oper State : Disabled
Hello Time : 10 Hello Msg Len : 0
Max Drop Count : 3 Hold Down Time : 10
Statistics :
I. Fwd. Pkts. : 0 I. Dro. Pkts. : 0
E. Fwd. Pkts. : 0 E. Fwd. Octets : 0
Associated LSP LIST :
SDP Delivery Mechanism is not MPLS
-------------------------------------------------------------------------------
Number of SDPs : 1
===============================================================================
*A:ALA-B#
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.
Output
The following output is an example of split horizon group information, and Output fields: Split Horizon group describes the output fields.
Sample output*A:7210-SAS>show>service# id 1 split-horizon-group
===============================================================================
Service: Split Horizon Group
===============================================================================
Name Description
-------------------------------------------------------------------------------
access
-------------------------------------------------------------------------------
R = Residential Split Horizon Group
A = Auto Created Split Horizon Group
No. of Split Horizon Groups: 1
===============================================================================
*A:7210-SAS>show>service# id 1 split-horizon-group access
===============================================================================
Service: Split Horizon Group
===============================================================================
Name Description
-------------------------------------------------------------------------------
access
-------------------------------------------------------------------------------
Associations
-------------------------------------------------------------------------------
-------------------------------------------------------------------------------
R = Residential Split Horizon Group
SAPs Associated : 0 SDPs Associated : 0
*A:7210-SAS>show>service#
|
Label |
Description |
|---|---|
|
Name |
The name of the split horizon group. When preceded by ‟R”, the group is a residential split horizon group. |
|
Description |
A description of the split horizon group as configured by the user. |
|
Associations |
A list of SAPs and SDPs associated with the split horizon group. |
stp
Syntax
stp [detail]
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 (STP) instance for the service.
Parameters
- detail
Displays detailed information.
Output
The following output is an example of STP information, and Output fields: STP describes the output fields.
Sample outputA: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
===============================================================================
|
Label |
Description |
|---|---|
|
RSTP Admin State |
Indicates the administrative state of the Rapid Spanning Tree Protocol instance associated with this service. |
|
Core Connectivity |
Indicates the connectivity status to the core. |
|
RSTP Oper State |
Indicates the operational state of the Rapid Spanning Tree Protocol instance associated with this service. This field is applicable only when STP is enabled on the router. |
|
Bridge-id |
Specifies the MAC address used to identify this bridge in the network. |
|
Hold Time |
Specifies the interval length during which no more than two Configuration BPDUs shall be transmitted by this bridge. |
|
Bridge fwd delay |
Specifies how fast a bridge changes its state when moving toward the forwarding state. |
|
Bridge Hello time |
Specifies the amount of time between the transmission of Configuration BPDUs. |
|
Bridge max age |
Specifies the maximum age of 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 |
Defines the priority of the Spanning Tree Protocol instance associated with this service. |
|
Topology change |
Specifies whether a topology change is currently in progress. |
|
Last Top. change |
Specifies the time (in hundredths of a second) since the last time a topology change was detected by the Spanning Tree Protocol instance associated with this service. |
|
Top. change count |
Specifies the total number of topology changes detected by the Spanning Tree Protocol instance associated with this service since the management entity was last reset or initialized. |
|
Root bridge-id |
Specifies the bridge identifier of the root of the spanning tree as determined by the 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 |
Specifies the cost of the path to the root bridge as seen from this bridge. |
|
Root forward delay |
Specifies how fast the root changes its state when moving toward the forwarding state. |
|
Root hello time |
Specifies the amount of time between the transmission of configuration BPDUs. |
|
Root max age |
Specifies the maximum age of Spanning Tree Protocol information learned from the network on any port before it is discarded. |
|
Root priority |
This object specifies the priority of the bridge that is currently selected as root-bridge for the network. |
|
Root port |
Specifies the port number of the port which provides the lowest cost path from this bridge to the root bridge. |
|
SAP Identifier |
The ID of the access port where this SAP is defined. |
|
RSTP State |
The operational state of RSTP. |
|
STP Port State |
Specifies the port identifier of the port on the designated bridge for this port's segment. |
|
BPDU encap |
Specifies the type of encapsulation used on BPDUs sent out and received on this SAP. |
|
Port Number |
Specifies the value of the port number field which is contained in the least significant 12 bits of the 16-bit port ID associated with this SAP. |
|
Priority |
Specifies the value of the port priority field which is contained in the most significant 4 bits of the 16-bit port ID associated with this SAP. |
|
Cost |
Specifies the contribution of this port to the path cost of paths toward the spanning tree root which include this port. |
|
Fast Start |
Specifies whether Fast Start is enabled on this SAP. |
|
Designated Port |
Specifies the port identifier of the port on the designated bridge for this port's segment. |
|
Designated Bridge |
Specifies the bridge identifier of the bridge which this port considers to be the designated bridge for this port's segment. |
sap-using
Syntax
sap-using [sap sap-id]
sap-using interface [ip-address | ip-int-name]
sap-using [ingress | egress] filter filter-id
sap-using [ingress | egress] qos-policy qos-policy-id
sap-using encap-type encap-type
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
- ip-addr
The IP address of the interface for which to display matching SAPs.
- ip-int-name
Specifies the IP interface name for which to display matching SAPs.
- ingress
Specifies matching an ingress policy.
- egress
Specifies matching an egress policy.
- qos-policy qos-policy-id
Specifies the ingress QoS Policy ID for which to display matching SAPs.
- filter filter-id
Specifies the ingress or egress filter policy ID for which to display matching SAPs.
- sap sap-id
Specifies the physical port identifier portion of the SAP definition. See Common CLI command descriptions for command syntax.
- encap-type encap-type
Displays the CEM encapsulation type.
Output
The following output is an example of service SAP information, and Output fields: SAP-using describes the output fields.
Sample output*A:Dut-A# show service sap-using
========================================================================
Service Access Points
===============================================================================
PortId SvcId Ing. Ing. Egr. Egr. Adm Opr
QoS Fltr QoS Fltr
------------------------------------------------------------------------
1/1/1:1 1 1 none 1 none Up Up
2/1/2:10/11 1 1 none 1 none Up Up
2/1/2:10/12 1 1 none 1 none Up Up
2/1/2:20/11 1 1 none 1 none Up Up
2/1/2:20/12 1 1 none 1 none Up Up
2/1/4:cp.10 10 1 none 1 none Up Up
2/1/4:cp.20 20 1 none 1 none Up Up
------------------------------------------------------------------------
Number of SAPs : 7
------------------------------------------------------------------------
========================================================================
A:Dut-A>config>service>vpls# show service sap-using
=========================================================================
Service Access Points
=========================================================================
PortId SvcId Ing. Ing. Egr. Adm Opr
QoS Fltr Fltr
-------------------------------------------------------------------------
lag-3:100 100 1 none none Up Up
1/1/3 101 10 mac none Up Up
lag-3:101 101 10 mac none Up Up
lag-3:102 102 10 mac none Up Up
lag-3:103 103 10 mac none Up Up
lag-3:104 104 10 mac none Up Up
lag-3:105 105 10 mac none Up Up
lag-3:201 201 10 mac none Up Up
lag-3:202 202 10 mac none Up Up
lag-3:203 203 10 mac none Up Up
lag-3:204 204 10 mac none Up Up
lag-3:205 205 10 mac none Up Up
1/1/16:301 301 10 mac none Up Up
lag-4:301 301 10 mac none Up Up
1/1/16:302 302 10 mac none Up Up
lag-4:302 302 10 mac none Up Up
1/1/16:303 303 10 mac none Up Up
lag-4:303 303 10 mac none Up Up
1/1/16:304 304 10 mac none Up Up
lag-4:304 304 10 mac none Up Up
1/1/16:305 305 10 mac none Up Up
lag-4:305 305 10 mac none Up Up
...
=========================================================================
A:Dut-A>config>service>vpls#
A:Dut-A>config>service# show service sap-using sap 1/1/16:305
=========================================================================
Service Access Points Using Port 1/1/16:305
=========================================================================
PortId SvcId Ing. Ing. Egr. Adm Opr
QoS Fltr Fltr
-------------------------------------------------------------------------
1/1/16:305 305 10 mac none Up Up
-------------------------------------------------------------------------
Number of SAPs : 1
=========================================================================
A:Dut-A>config>service#
A:ces-A# show service sap-using sap 1/2/1.1
=========================================================================
Service Access Points
=========================================================================
PortId SvcId Ing. Ing. Egr. Adm Opr
QoS Fltr Fltr
-------------------------------------------------------------------------
1/2/1.1 1 12 none none Up Up
-------------------------------------------------------------------------
Number of SAPs : 1
-------------------------------------------------------------------------
=========================================================================
A:ces-A#
*A:ces-A# show service sap-using sap 1/2/1.1
=========================================================================
Service Access Points
=========================================================================
PortId SvcId Ing. Ing. Egr. Adm Opr
QoS Fltr Fltr
-------------------------------------------------------------------------
1/2/1.1 1 1 none none Up Up
-------------------------------------------------------------------------
Number of SAPs : 1
-------------------------------------------------------------------------
=========================================================================
*A:ces-A# show service sap-using encap-type cem
=============================================================================
Service Access Points Using Encap Type 'cem'
=============================================================================
PortId SvcId Adm Opr Alarm
-----------------------------------------------------------------------------
1/2/1.1 1 Up Up No
1/2/2.1 2 Up Up No
1/2/3.1 3 Up Down Yes
1/2/4.1 4 Up Down Yes
-----------------------------------------------------------------------------
Number of SAPS : 4
-----------------------------------------------------------------------------
=============================================================================
|
Label |
Description |
|---|---|
|
Port ID |
The ID of the access port where the SAP is defined. |
|
Svc ID |
The service identifier. |
|
MTU |
The port MTU value. |
|
Ing. QoS |
The SAP ingress QoS policy number specified on the ingress SAP. |
|
Ing Fltr |
The MAC or IP filter policy ID applied to the ingress SAP. |
|
Egr. QoS |
The SAP egress QoS policy number specified on the egress SAP. |
|
Egr. Fltr |
The MAC or IP filter policy ID applied to the egress SAP. |
|
Adm |
The administrative state of the SAP. |
|
Opr |
The operational state of the SAP. |
sdp
Syntax
sdp [sdp-id | far-end ip-address] [detail | keep-alive-history]
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 SDP information.
If no optional parameters are specified, a summary SDP output for all SDPs is displayed.
Parameters
- sdp-id
The SDP ID for which to display information.
- far-end ip-address
Displays only SDPs matching with the specified far-end IP address.
- detail
Displays detailed SDP information.
- keep-alive-history
Displays the last fifty SDP keepalive events for the SDP.
Output
The following output is an example of SDP information, and Output fields: SDP describes the output fields.
Sample output*A:ALA-12# show service sdp
==============================================================================
Services: Service Destination Points
==============================================================================
SdpId Adm MTU Opr MTU IP address Adm Opr Deliver Signal
------------------------------------------------------------------------------
10 4462 4462 10.20.1.3 Up Dn NotReady MPLS TLDP
40 4462 1534 10.20.1.20 Up Up MPLS TLDP
60 4462 1514 10.20.1.21 Up Up MPLS TLDP
100 4462 4462 10.0.0.2 Down Down MPLS TLDP
500 4462 4462 10.20.1.50 Up Dn NotReady MPLS TLDP
------------------------------------------------------------------------------
Number of SDPs : 5
==============================================================================
*A:ALA-12#
*A:ALA-12# show service sdp 2 detail
===============================================================================
Service Destination Point (Sdp Id : 2) Details
===============================================================================
Sdp Id 2 -(10.10.10.104)
-------------------------------------------------------------------------------
Description : MPLS-10.10.10.104
SDP Id : 2
Admin Path MTU : 0 Oper Path MTU : 0
Far End : 10.10.10.104 Delivery : MPLS
Admin State : Up Oper State : Down
Flags : SignalingSessDown TransportTunnDown
Signaling : TLDP VLAN VC Etype : 0x8100
Last Status Change : 02/01/2007 09:11:39 Adv. MTU Over. : No
Last Mgmt Change : 02/01/2007 09:11:46
KeepAlive Information :
Admin State : Disabled Oper State : Disabled
Hello Time : 10 Hello Msg Len : 0
Hello Timeout : 5 Unmatched Replies : 0
Max Drop Count : 3 Hold Down Time : 10
Tx Hello Msgs : 0 Rx Hello Msgs : 0
Associated LSP LIST :
SDP Delivery Mechanism is not MPLS
===============================================================================
*A:ALA-12#
*A:ALA-12# show service sdp 8
==============================================================================
Service Destination Point (Sdp Id : 8)
==============================================================================
SdpId Adm MTU Opr MTU IP address Adm Opr Deliver Signal
------------------------------------------------------------------------------
8 4462 4462 10.10.10.104 Up Dn NotReady MPLS TLDP
==============================================================================
*A:ALA-12#
*A:ALA-12# show service sdp 8 detail
===============================================================================
Service Destination Point (Sdp Id : 8) Details
===============================================================================
Sdp Id 8 -(10.10.10.104)
-------------------------------------------------------------------------------
Description : MPLS-10.10.10.104
SDP Id : 8
Admin Path MTU : 0 Oper Path MTU : 0
Far End : 10.10.10.104 Delivery : MPLS
Admin State : Up Oper State : Down
Flags : SignalingSessDown TransportTunnDown
Signaling : TLDP VLAN VC Etype : 0x8100
Last Status Change : 02/01/2007 09:11:39 Adv. MTU Over. : No
Last Mgmt Change : 02/01/2007 09:11:46
KeepAlive Information :
Admin State : Disabled Oper State : Disabled
Hello Time : 10 Hello Msg Len : 0
Hello Timeout : 5 Unmatched Replies : 0
Max Drop Count : 3 Hold Down Time : 10
Tx Hello Msgs : 0 Rx Hello Msgs : 0
Associated LSP LIST :
Lsp Name : to-104
Admin State : Up Oper State : Down
Time Since Last Tran*: 01d07h36m
===============================================================================
* indicates that the corresponding row element may have been truncated.
*A:ALA-12#
|
Label |
Description |
|---|---|
|
SDP Id |
The SDP identifier. |
|
Adm 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. |
|
Opr 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. |
|
IP address |
The IP address of the remote end of the MPLS tunnel defined by this SDP. |
|
Adm Admin State |
The desired state of the SDP. |
|
Opr Oper State |
The operating state of the SDP. |
|
Deliver Delivery |
The type of delivery used by the SDP: MPLS. |
|
Flags |
All the conditions that affect the operating status of this SDP. |
|
Signal Signaling |
The signaling protocol used to obtain the ingress and egress labels used in frames transmitted and received on the SDP. |
|
Last Status Change |
The time of the most recent operating status change to this SDP. |
|
Last Mgmt Change |
The time of the most recent management-initiated change to this SDP. |
|
Number of SDPs |
The total number of SDPs displayed according to the criteria specified. |
|
Hello Time |
How often the SDP echo request messages are transmitted on this SDP. |
|
Number of SDPs |
The total number of SDPs displayed according to the criteria specified. |
|
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. |
|
Hello Timeout |
The number of seconds to wait for an SDP echo response message before declaring a timeout. |
|
Unmatched Replies |
The number of SDP unmatched message replies. |
|
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. |
|
TX Hello Msgs |
The number of SDP echo request messages transmitted since the keepalive was administratively enabled or the counter was cleared. |
|
Rx Hello Msgs |
The number of SDP echo request messages received since the keepalive was administratively enabled or the counter was cleared. |
|
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
Display services using SDP or far-end address options.
Parameters
- sdp-id
Displays only services bound to the specified SDP ID.
- vc-id
Specifies the virtual circuit identifier.
- far-end ip-address
Displays only services matching with the specified far-end IP address.
Output
The following output is an example of service 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
-------------------------------------------------------------------------------
1 300:1 Mesh 10.0.0.13 Up 131071 131071
2 300:2 Spok 10.0.0.13 Up 131070 131070
100 300:100 Mesh 10.0.0.13 Up 131069 131069
101 300:101 Mesh 10.0.0.13 Up 131068 131068
102 300:102 Mesh 10.0.0.13 Up 131067 131067
-------------------------------------------------------------------------------
Number of SDPs : 5
-------------------------------------------------------------------------------
*A:ALA-1#
*A:ces-A# show service sdp-using
===============================================================================
SDP Using
===============================================================================
SvcId SdpId Type Far End Opr S* I.Label E.Label
-------------------------------------------------------------------------------
1 12:1 Spok 2.2.2.2 Up 131063 131062
2 12:2 Spok 2.2.2.2 Up 131062 131069
3 122:3 Spok 2.2.2.2 Up 131069 131068
4 12:4 Spok 2.2.2.2 Up 131061 131061
-------------------------------------------------------------------------------
Number of SDPs : 4
-------------------------------------------------------------------------------
===============================================================================
*A:ces-A#
|
Label |
Description |
|---|---|
|
Svc ID |
The service identifier. |
|
Sdp ID |
The SDP identifier. |
|
Type |
Type of SDP: spoke or mesh. |
|
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 [sdp sdp-id] [b-vpls] [i-vpls] [m-vpls] [sdp sdp-id] [customer customer-id]
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 the services matching certain usage properties.
If no optional parameters are specified, all services defined on the system are displayed.
Parameters
- [service]
Displays information for the specified service type.
- b-vpls
Specifies the B-component instance of the Provider Backbone Bridging (PBB/IEEE 802.1ah) feature. It represents the multi-point tunneling component that multiplexes multiple customer VPNs (ISIDs) together. It is similar to a regular VPLS instance that operates on the backbone MAC addresses.
- i-vpls
Specifies the I-component instance of the Provider Backbone Bridging (PBB/IEEE 802.1ah) feature. It identifies the specific VPN entity associated to a customer multipoint (ELAN) service. It is similar to a regular VPLS instance that operates on the customer MAC addresses.
- m-vpls
Specifies the M-component (managed VPLS) instance of the Provider Backbone Bridging (PBB/IEEE 802.1ah) feature.
- sdp sdp-id
Displays only services bound to the specified SDP ID.
- customer customer-id
Displays services only associated with the specified customer ID.
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
300 Epipe Up Up 10 09/05/2006 13:24:15
------------------------------------------------------------------------------
Matching Services : 2
==============================================================================
*A:ALA-12#
*A:ALA-12# show service service-using
===============================================================================
Services
===============================================================================
ServiceId Type Adm Opr CustomerId Last Mgmt Change
-------------------------------------------------------------------------------
1 uVPLS Up Up 1 10/26/2006 15:44:57
2 Epipe Up Down 1 10/26/2006 15:44:57
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
999 uVPLS Down Down 1 10/26/2006 16:14:33
-------------------------------------------------------------------------------
Matching Services : 8
-------------------------------------------------------------------------------
*A:ALA-12#
|
Label |
Description |
|---|---|
|
Service Id |
The service identifier. |
|
Type |
The service type configured for the service ID. |
|
Adm |
The desired 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. |
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.
spoke-sdp
Syntax
spoke-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 spoke-SDP bindings for the service.
Parameters
- sdp-id
Specifies the spoke-SDP ID to be reset.
- vc-id
Specifies the virtual circuit ID on the SDP ID to be reset.
- ingress-vc-label
Specifies the ingress VC label to be cleared.
sap
Syntax
sap sap-id {all | cem | counters | stp}
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 SAP statistics for a SAP.
Parameters
- sap-id
Specifies the physical port identifier portion of the SAP definition. See Common CLI command descriptions for command syntax.
- all
Clears all SAP queue statistics and STP statistics.
- counters
Clears all queue statistics associated with the SAP.
- stp
Clears all STP statistics associated with the SAP.
- l2pt
Clears all L2PT statistics associated with the SDP.
sdp
Syntax
sdp sdp-id keep-alive
Context
clear>service>statistics
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command clears keepalive statistics associated with the SDP ID.
Parameters
- sdp-id
Specifies the SDP ID for which to clear keepalive statistics.
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.
spoke-sdp
Syntax
spoke-sdp sdp-id[:vc-id] {all | counters | stp}
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
Specifies the spoke-SDP ID for which to clear statistics.
- vc-id
Specifies the virtual circuit ID on the SDP ID to be reset.
- 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.
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
This command clears all spanning tree statistics for the service ID.
statistics
Syntax
statistics
Context
clear>service
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 statistics for a specific service entity.
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
The ID that uniquely identifies a service.
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.
event-type
Syntax
[no] event-type {arp | config-change | 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
- arp
Displays ARP events. This parameter is not supported for use with VLL services.
- config-change
Debugs configuration change events.
- svc-oper-status-change
Debugs service operational status changes.
Output
The following output is an example of event type debugging information.
Sample outputA:bksim180# debug service id 1000 sap 1/7/1 event-type arp
DEBUG OUTPUT show on CLI is as follows:
3 2008/11/17 18:13:24.35 UTC MINOR: DEBUG #2001 Base Service 1000 SAP 1/7/
1 "Service 1000 SAP 1/7/1:
RX: ARP_REQUEST (0x0001)
hwType : 0x0001
prType : 0x0800
hwLength : 0x06
prLength : 0x04
srcMac : 8c:c7:01:07:00:03
destMac : 00:00:00:00:00:00
srcIp : 10.1.1.2
destIp : 10.1.1.1
"
4 2008/11/17 18:13:24.35 UTC MINOR: DEBUG #2001 Base Service 1000 SAP 1/7/
1 "Service 1000 SAP 1/7/1:
TX: ARP_RESPONSE (0x0002)
hwType : 0x0001
prType : 0x0800
hwLength : 0x06
prLength : 0x04
srcMac : 00:03:0a:0a:0a:0a
destMac : 8c:c7:01:07:00:03
srcIp : 10.1.1.1
destIp : 10.1.1.2
"
sdp
Syntax
[no] sdp sdp-id:vc-id
Context
debug>service>id
Platforms
Supported on all 7210 SAS platforms as described in this document, except those operating in access-uplink mode
Description
This command enables debugging for a particular SDP.
Parameters
- sdp-id
Specifies the SDP ID.