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]
config>service>epipe
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 before it can be associated with an Epipe or VPL service. If the sdp command is not already configured, an error message is generated. If the sdp-id exists, 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 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.
Only one SDP ID can be bound to an Epipe service. Because an Epipe is a point-to-point service, it can have, at most, two endpoints. The two endpoints can be one SAP and one SDP or two SAPs.
Specifies the SDP identifier. Allowed values are integers for existing SDPs.
Specifies the virtual circuit identifier.
Keyword that removes the association of a spoke-SDP with an explicit endpoint name.
Specifies the name of the service endpoint.
[no] control-word
config>service>epipe>spoke-sdp
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command adds 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, as 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 comes up only 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, according to Section 6.1 of RFC 4447. When the user also enables the control the remote peer, the remote peer withdraws its original label and sends a label mapping with the C-bit set to 1; the VLL service is then up in both nodes.
hash-label [signal-capability]
no hash-label
config>service>epipe>spoke-sdp
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the hash label on VLL or VPLS services that are bound to RSVP SDP, 3107 BGP SDP, segment routing, or LDP SDP, using the auto-bind mode with the ldp, rsvp-te, or mpls options. When this command is enabled, the ingress datapath is modified so that the result of the hash on the packet header is communicated to the egress datapath for use as the value of the label field of the hash label. The ingress datapath appends the hash label at the bottom of the stack (BoS) and sets the S-bit to one (1).
On 7210 SAS devices, the hash label is not used on the local node for ECMP and LAG hashing. It is available for use by LSR nodes, through which the traffic flows, that are capable of using the labels for hashing.
Packets generated in the CPM that are forwarded with a label within the context of a service (for example, OAM packets) must also include a hash label at the BoS and set the S-bit accordingly.
The TTL of the hash label is set to 0.
Signaling of the hash label capability is enabled by adding the signal-capability option under the VLL spoke-SDP, VPLS spoke-SDP or mesh SDP interface, or PW template instance. In this case, the decision of the local PE to insert the hash label on the user and control plane packets is determined by the outcome of the signaling process and can override the local PE configuration. The following process flow applies when the hash-label and signal-capability options 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 the specific spoke-SDP or mesh SDP.
If a 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 the user and control plane packets that it forwards on the spoke-SDP or mesh SDP. The local PE also drops user and control plane packets received from a remote PE if they include a hash label. The dropped packets may be caused by the following:
a remote 7210 SAS PE that does not support the hash-label command
a remote 7210 SAS PE that has the hash-label command enabled but does not support the signal-capability option
a remote 7210 SAS PE that supports the hash-label command and the signal-capability option, but the user did not enable them due to a misconfiguration
If the remote PE sends a flow label sub-TLV in the PW ID FEC element with T=TRUE and R=TRUE, the local PE enables the hash label capability. Consequently, the local PE node inserts a hash label in the user and control plane packets that it forwards on the spoke-SDP or mesh SDP. The local PE node also accepts user and control plane packets from the remote PE with a hash label. The local PE node drops user and control plane packets from the remote PE without a hash label.
If the hash-label command is enabled on the local PE with the signal-capability option configured and on the remote PE without the signal-capability option configured on the spoke-SDP or mesh-SDP, the hash label is included in the pseudowire packets received by the local PE. These packets must be dropped. To resolve this situation, you must disable the signal-capability option on the local node, which results in the insertion of the hash label by both PE nodes.
If the hash-label option is not supported or is not enabled on the local configuration of the spoke-SDP or mesh-SDP at the remote PE, the hash label is not included in the pseudowire received by the local PE.
If the signal-capability option is enabled or disabled in the CLI, 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 LPS or mLDP LSP in both the base router instance and in the multicast VPN (mVPN) instance.
In 7750 and possibly other vendor implementations, to allow applications where the egress LER infers the presence of the hash label implicitly from the value of the label, the Most Significant Bit (MSB) of the result of the hash is set before copying into the hash label. This means that the value of the hash label is always in the range [524,288 to 1,048,575] and does not overlap with the signaled/static LSP and signaled/static service label ranges. This also guarantees that the hash label does not match a value in the reserved label range. 7210 SAS devices do not set the MSB in the hash label value for service traffic. Therefore, the user must ensure that both ends are correctly configured to either process hash labels or disable them. The MSB bit is set for MPLS/OAM traffic on 7210 SAS devices.
The cpe-ping, mac-ping, and svc-ping commands are not supported on the 7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C when the hash-label command is enabled.
The no form of this command disables the use of the hash label.
no hash-label
Keyword that specifies to enable the signaling and negotiation of the use of the hash label between the local and remote PE nodes.
precedence [precedence-value | primary]
no precedence
no precedence >service>epipe>spoke-sdp
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 be assigned to only 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 reverts the precedence to the default value.
4
Specifies the spoke-SDP precedence.
Specifies to make this the primary spoke-SDP.
[no] pw-status-signaling
config>service>epipe>spoke-sdp
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command enables pseudowire status signaling for this spoke-SDP binding.
The no form of this command disables the status signaling.
pw-status-signaling
[no] vc-label vc-label
config>service>epipe>spoke-sdp>egress
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the egress VC label.
Specifies a VC egress value that indicates a specific connection.
[no] vc-label vc-label
config>service>cpipe>spoke-sdp>ingress
config>service>epipe>spoke-sdp>ingress
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the ingress VC label.
Specifies a VC ingress value that indicates a specific connection.
vlan-vc-tag vlan-id
no vlan-vc-tag [vlan-id]
config>service>epipe>spoke-sdp
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command specifies an explicit dot1q value used when encapsulating to the SDP far end. When signaling is enabled between the near and far end, the configured dot1q tag can be overridden by a received TLV specifying the dot1q value expected by the far end. This signaled value must be stored as the remote signaled dot1q value for the binding. The provisioned local dot1q tag must be stored as the administrative dot1q value for the binding.
When the dot1q tag is not defined, the default value of zero is stored as the administrative dot1q value. Setting the value to zero is equivalent to not specifying the value.
The no form of this command disables the command.
no vlan-vc-tag
Specifies a valid VLAN identifier to bind an 802.1Q VLAN tag ID.
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
config>service>epipe
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 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.
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 to that service is not already configured, an error message is generated. If the SDP ID exists, a binding between that SDP ID and the service is created.
This command differs from the spoke-sdp command because 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.
Specifies an unsigned integer value identifying the spoke-SDP.
Specifies an unsigned integer value for the type of the FEC used by the MS-PW.
Specifies an unsigned integer value for the Attachment Individual Identifier (AII) type used to identify the MS-PW endpoints.
Specifies the name of the service endpoint.
Keyword that adds or removes a spoke-SDP association.
[no] auto-config
config>service>epipe>spoke-sdp-fec
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 contexts.
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 SAS 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 SAS initiates MS-PW signaling without waiting for a label mapping message from the far end. However, if the TAII has the greater value prefix, the 7210 SAS 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.
no auto-config
path name
no path
config>service>epipe>spoke-sdp-fec
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command specifies the explicit path, containing a list of S-PE hops, that should be used for this spoke-SDP. The path name value 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.
Specifies the name of the explicit path to be used, as configured under the config>service>pw-routing context.
precedence prec-value
precedence primary
no precedence
config>service>epipe>spoke-sdp-fec
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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 reverts the precedence to the default value.
42
Specifies the spoke-SDP precedence.
Keyword that specifies to make this the primary spoke-SDP.
pw-template-bind policy-id
no pw-template-bind
config>service>epipe>spoke-sdp-fec
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command binds a specific PW template to a spoke-SDP.
The no form of this command removes the values from the configuration.
Specifies the existing policy ID.
retry-count retry-count
no retry-count
config>service>epipe>spoke-sdp-fec
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This optional command specifies the number of attempts that should be made 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 to the default value.
30
Specifies the maximum number of retries before putting the spoke-SDP into the shutdown state.
retry-timer retry-timer
no retry-timer
config>service>epipe>spoke-sdp-fec
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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.
30
Specifies the initial retry-timer value, in seconds.
saii-type2 global-id:prefix:ac-id
no saii-type2
config>service>epipe>spoke-sdp-fec
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures the source attachment individual identifier for the spoke-SDP. This is applicable only to FEC129 AII type 2.
Specifies the global ID of this 7210 SAS T-PE. This value must correspond to one of the global_id values configured for a local-prefix under the config>service>pw-routing>local-prefix context.
Specifies the prefix on this 7210 SAS T-PE that the spoke-SDP is associated with.This value must correspond to one of the prefixes configured under the config>service>pw-routing>local-prefix context.
Specifies an unsigned integer representing a locally unique identifier for the spoke-SDP.
signaling signaling
config>service>epipe>spoke-sdp-fec
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
This command configures this 7210 SAS as the active or passive T-PE for signaling this MS-PW, or to automatically select whether this T-PE is active or passive based on the prefix.
In an active role, this endpoint initiates MS-PW signaling without waiting for a T-LDP label mapping message to arrive from the far end T-PE. In a passive role, the endpoing waits for the initial label mapping message from the far end before sending a label mapping for this end of the PW. In auto mode, if the SAII has the greater prefix value, the 7210 SAS initiates MS-PW signaling without waiting for a label mapping message from the far end. However, if the TAII has the greater value prefix, the 7210 SAS assumes that the far end T-PE initiates MS-PW signaling and will wait for that label mapping message before responding with a T-LDP label mapping message for the MS-PW in the reverse direction.
The no form of this command means that the 7210 T-PE automatically selects the 7210 SAS that will initiate MS-PW signaling based on the prefix values configured in the SAII and TAII of the spoke-SDP.
auto
Configures this 7210 SAS as the active T-PE for signaling this MS-PW.
taii-type2 global-id:prefix:ac-id
no taii-type2
config>service>epipe>spoke-sdp-fec
7210 SAS-K 2F6C4T and 7210 SAS-K 3SFP+ 8C
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).
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 the config>service>pw-routing>local-prefix context.
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 the config>service>pw-routing>local-prefix context.
Specifies an unsigned integer representing a locally unique identifier for the spoke-SDP.