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
Supported on all 7210 SAS platforms as described in this document
This command binds a service to an existing Service Distribution Point (SDP).
The SDP has an operational state, which determines the operational state of the SDP within the service; for example, if the SDP is administratively or operationally down, the SDP for the service is down.
The SDP must already exist in the config>service>sdp context before it can be associated with an Epipe or VPL service. If the sdp sdp-id is not already configured, an error message is generated. If the sdp-id exists, a binding between the specific sdp-id and the service is created.
SDPs must be explicitly associated and bound to a service to allow far-end 7210 SAS-R6 and 7210 SAS-R12 devices to participate in the service.
The no form of this command removes the SDP binding from the service; the SDP configuration is not affected. When the SDP binding is removed, no packets are forwarded to the far-end router.
At most, 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 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.
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
Supported on all 7210 SAS platforms as described in this document
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 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, in accordance with Section 6.1 of RFC 4447. When the user also enables the control on 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 then becomes up in both nodes.
[no] control-channel-status
config>service>epipe>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command configures 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:
SDP signaling is off
control word is enabled (control word by default is disabled)
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.
no control-channel-status
[no] acknowledgment
config>service>epipe>spoke-sdp>control-channel-status
Supported on all 7210 SAS platforms as described in this document
This command configures the acknowledgment of control channel status messages. By default, no acknowledgment packets are sent.
refresh-timer value
no refresh-timer
config>service>epipe>spoke-sdp>control-channel-status
Supported on all 7210 SAS platforms as described in this document
This command configures the refresh timer for control channel status signaling packets. By default, no refresh packets are sent.
no refresh-timer
Specifies the refresh timer value.
request-timer request-timer request-timer-secs retry-timer retry-timer-secs timeout-multiplier multiplier
config>service>epipe>spoke-sdp>control-channel-status
Supported on all 7210 SAS platforms as described in this document
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, in accordance with RFC 6478. This command and a non-zero refresh-timer value are mutually exclusive.
Specifies the interval at which pseudowire status messages, including a reliable delivery TLV, with the ‟request” bit set, are sent.
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.
Specifies that, if a requesting node does not receive a valid response to a pseudowire status request within this multiplier times the retry timer, it assumes the pseudowire is down. This parameter is optional.
[no] force-vlan-vc-forwarding
config>service>epipe>spoke-sdp
config>service>vpls>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
This command forces vc-vlan-type forwarding in the datapath for spokes that have either vc-type. This command is not allowed on vlan-vc-type SDPs.
The no version of this command reverts to the default value.
disabled
hash-label [signal-capability]
no hash-label
config>service>epipe>spoke-sdp
7210 SAS-R6 IMMv2 and IMM-c cards and 7210 SAS-R12 IMMv2 and IMM-c cards
This command configures the use of the hash label on a VLL or VPLS service bound to LDP or RSVP SDP using the autobind mode with the ldp, rsvp-te, or mpls options. When this feature is enabled, the ingress datapath is modified 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. The egress datapath appends the hash label at the bottom of the stack (BoS) and sets the S-bit to one (1).
On 7210 SAS, the hash label is not used on the local node for purpose of ECMP hashing and LAG hashing. It is available for use by LSR nodes through which the traffic flows and that are capable of using the labels for hashing.
Packets generated in CPM and that are forwarded labeled within the context of a service (for example, OAM packets) must also include a hash label at the BoS and set the S-bit accordingly.
The TTL of the hash label is set to a value of 0.
The user enables the signaling of the hash-label capability under a VLL spoke-sdp, a VPLS spoke-sdp, or mesh-sdp interface by adding the signal-capability option. In this case, the decision whether to insert the hash label on the user and control plane packets by the local PE is solely determined by the outcome of the signaling process and can override the local PE configuration. The following rules apply when the hash-label option 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. Therefore, 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 the remote PE if they include a hash label. Note that the latter may be caused by a remote 7210 SAS PE that does not support the hash-label option, or that has the hash-label option enabled but does not support the signal-capability option, or does support both options but the user did not enable them because of a misconfiguration.
If remote PE sends Flow Label sub-TLV in the PW ID FEC element with T=TRUE and R=TRUE, the local PE enables the hash label capability. Therefore, local PE inserts a hash label in user and control plane packets it forwards on the spoke-SDP or mesh SDP. It also accepts user and control plane packets remote PE with or without a hash label.
If the hash-label option was enabled on the local configuration of the spoke-sdp or mesh-sdp at the remote PE, the pseudowire packets received by the local PE include the hash label. These packets must be dropped. The only way to solve this is to disable the signaling capability option on the local node, which results in the insertion of the hash label by both PE nodes.
If the hash-label option is not supported or was not enabled on the local configuration of the spoke-SDP or mesh SDP at the remote PE, the pseudowire received by the local PE does not have the hash label included.
The user can enable or disable the signal-capability option in CLI as needed. When doing so, the router must withdraw the label it sent to its peer and send a new label mapping message with the new value of the F bit in the flow label interface parameters sub-TLV of the PW ID FEC element.
This feature is supported only for VLL and VPLS services. It not supported for VPRN services. It is also not supported on multicast packets forwarded using RSVP P2MP LPS or mLDP LSP in both the base router instance and in the multicast VPN (mVPN) instance.
In 7x50 and possibly other vendor implementations, to allow applications where the egress LER infers the presence of the hash label implicitly from the value of the label, the Most Significant Bit (MSB) of the result of the hash is set before copying into the Hash Label. Therefore, 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 the hash label does not match a value in the reserved label range. This is not supported on 7210 SAS for service traffic (for MPLS OAM traffic the MSB bit is set). That is, 7210 SAS devices do not set the MSB bit in the hash label value for service traffic. If enabled, the user must ensure that both the ends are correctly configured to process hash labels.
The no form of this command disables the use of the hash label.
no hash-label
Keyword 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
config>service>epipe>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
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 value to the default.
4
Specifies the spoke-SDP precedence.
Specifies to make this the primary spoke-SDP.
[no] pw-path-id
config>service>epipe>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
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.
This command is configurable only if all the following conditions are true:
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, Cpipe, or IES/VPRN interface
mate SDP signaling is off for VC-switched services
The no form of this command deletes the PW path ID.
no pw-path-id
agi agi
no agi
config>service>epipe>spoke-sdp>pw-path-id
Supported on all 7210 SAS platforms as described in this document
This command configures the attachment group identifier for an MPLS-TP PW.
Specifies the attachment group identifier.
saii-type2 global-id:node-id:ac-id
no saii-type2
config>service>epipe>spoke-sdp>pw-path-id
Supported on all 7210 SAS platforms as described in this document
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.
Specifies the global ID at the source PE or T-PE for the MPLS-TP PW for a spoke-SDP.
Specifies the node ID at the source PE or T-PE for the MPLS-TP PW for a spoke-SDP.
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 global-id:node-id:ac-id
no taii-type2
config>service>epipe>spoke-sdp>pw-path-id
Supported on all 7210 SAS platforms as described in this document
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, it is at an S-PE, the values must match those of the taii-type2 of the mate spoke-sdp.
Specifies the global ID at the target PE or T-PE for the MPLS-TP PW for a spoke-SDP.
Specifies the node ID at the target PE or T-PE for the MPLS-TP PW for a spoke-SDP.
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.
[no] pw-status-signaling
config>service>epipe>spoke-sdp
Supported on all 7210 SAS platforms as described in this document
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
Supported on all 7210 SAS platforms as described in this document
This command configures the egress VC label.
Specifies a VC egress value that indicates a specific connection.
[no] vc-label vc-label
config>service>epipe>spoke-sdp>ingress
Supported on all 7210 SAS platforms as described in this document
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
Supported on all 7210 SAS platforms as described in this document
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 [icb]
config>service>epipe
Supported on all 7210 SAS platforms as described in this document
This command binds a service to an existing Service Distribution Point (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 SAS of the MS-PW. The 7210 SAS associates an SDP with a service. If an SDP is not already configured, an error message is generated. If the sdp-id does exist, a binding between that sdp-id and the service is created.
This command 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 Generalised 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 to add or remove a spoke-SDP association.
Keyword to configure the spoke-SDP as an inter-chassis backup SDP binding.
[no] auto-config
config>service>epipe>spoke-sdp-fec
Supported on all 7210 SAS platforms as described in this document
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 SAS 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 SAS 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 will initiate 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.
no auto-config
path name
no path
config>service>epipe>spoke-sdp-fec
Supported on all 7210 SAS platforms as described in this document
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 using the config>service>pw-routing context.
If no path is configured, each next-hop of the MS-PW used by the spoke-SDP will be chosen locally at each T-PE and S-PE.
no path
Specifies the name of the explicit path to be used, as configured in the config>service>pw-routing context.
precedence prec-value
precedence primary
no precedence
config>service>epipe>spoke-sdp-fec
Supported on all 7210 SAS platforms as described in this document
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 to the default value.
42
Specifies the spoke-SDP precedence.
Keyword to make this the primary spoke-SDP.
pw-template-bind policy-id
no pw-template-bind
config>service>epipe>spoke-sdp-fec
Supported on all 7210 SAS platforms as described in this document
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.
Specifies the existing policy ID.
retry-count retry-count
no retry-count
config>service>epipe>spoke-sdp-fec
Supported on all 7210 SAS platforms as described in this document
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 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
Supported on all 7210 SAS platforms as described in this document
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, a label withdraw message is received with the status code ‟AII unreachable”.
The no form of this command reverts to the 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
Supported on all 7210 SAS platforms as described in this document
This command configures the source attachment individual identifier for the spoke-sdp. This is only applicable to FEC129 AII type 2.
Specifies a global ID for this 7210 SAS T-PE. This value must correspond to one of the global_id values configured for a local-prefix in the config>service>pw-routing>local-prefix context.
Specifies the prefix, expressed as an IPv4-formatted address, on this 7210 SAS T-PE that the spoke-sdp SDP is associated with.This value must correspond to one of the prefixes configured in 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
Supported on all 7210 SAS platforms as described in this document
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, it 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 is initiating 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.
The no form of this command means that the 7210 SAS 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, as described previously.
auto
Specifies this 7210 SAS as the active T-PE for signaling this MS-PW.
[no] standby-signaling-slave
config>service>epipe>spoke-sdp-fec
Supported on all 7210 SAS platforms as described in this document
When this command is enabled, the node blocks the transmit forwarding direction of a spoke-SDP based on the setting of the standby bit received from a T-LDP peer.
This command is present at the endpoint level and spoke-SDP level. If the spoke-sdp is part of an explicit-endpoint, it is not possible to change this setting at the spoke-sdp level. An existing spoke-sdp can be made part of the explicit endpoint only if the settings do not conflict. A newly created spoke-sdp, which is part of a specific explicit-endpoint, inherits this setting from the endpoint configuration. An existing spoke-sdp cannot be moved to an endpoint if the setting of standby-signaling-slave is not the same as at the endpoint level. If the standby-signaling-slave setting is changed at the endpoint level, that change is automatically populated to the member spoke-sdps.This command cannot be configured for an endpoint that is part of an MC-LAG, ICB, and MC endpoint, or for which standby-signaling-master has been enabled.
If this command is disabled, the node assumes the existing Release 5.0 mode of behavior for forwarding on the spoke-SDP.
no standby-signaling-slave
taii-type2 global-id:prefix:ac-id
no taii-type2
config>service>epipe>spoke-sdp-fec
Supported on all 7210 SAS platforms as described in this document
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 in the config>service>pw-routing>local-prefix context.
Specifies the prefix, expressed as an IPv4-formatted address, on this 7210 T-PE that the spoke-sdp SDP is associated with.This value must correspond to one of the prefixes configured in the config>service>pw-routing>local-prefix context.
Specifies an unsigned integer representing a locally unique identifier for the spoke-SDP.