VLL spoke-SDP configuration

7210 SAS-R6 and 7210 SAS-R12 can be S-PE or T-PE and 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 stated as follows. Likewise, all existing functions on a specific service SAP are supported if the spoke-sdp that it is 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 enabled unless the ingress label, the egress label, the control word, and the pw-path-id are configured.

Example: VLL spoke-SDP configuration

*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-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 uses control channel status signaling instead of 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 as follows. Control-channel-status 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.

Note: A shutdown of a service results in the static PW status bits for the corresponding PW being 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 as either a 4-octet IP address format <a.b.c.d> or an unsigned integer format.

The control word must be enabled to use MPLS-TP on a spoke-SDP.

The pw-path-id only configurable if all of the following is true:

network mode D
SDP signaling is off
control word 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/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, then 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 allowed only if all of the following is true:

Network-mode D
SDP signaling is off
Control-ord enabled (control-word by default is disabled)
the service type is Epipe or VPLS interface
Mate SDP signaling is off (in VC-switched services)
PW status signaling is enabled (as follows)
PW path ID is configured for this spoke

The hash-label option is only configurable if SDP far-end is not 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 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.

The following commands are used 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 (as follows) are sent. This cannot be enabled if refresh-timer not equal to zero (0). retry-timer : 3-60s
This parameter determines the timeout interval if no response to a PW status is received. This defaults to zero (0) when no retry-timer. timeout-multiplier <value> - 3-15.
If a requesting node does not hear back after retry-timer times multiplier, then it must assume that the peer is down. This defaults to zero (0) when no retry-timer.