Alcatel-Lucent 7210 SAS M Service Manual page 236

Hide thumbs Also See for 7210 SAS M:
Table of Contents

Advertisement

VLL Service Configuration Commands
The (unmodified) result of the hash continues to be used for the purpose of ECMP and LAG spraying
of packets locally on the ingress LER. Note, however, that for VLL services, the result of the hash is
overwritten and the ECMP and LAG spraying will be based on service-id when ingress SAP shared
queuing is not enabled. However, the hash label will still reflect the result of the hash such that an
LSR can use it to perform fine grained load balancing of VLL PW packets.
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.
control-word
Syntax
[no] control-word
Context
config>service>cpipe>spoke-sdp
config>service>epipe>spoke-sdp
The control word command provides the option to add a control word as part of the packet
Description
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 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 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 will withdraw its original
label and will send a label mapping with the C-bit set to 1 and the VLL service will be up in both
nodes.
precedence
Syntax
precedence [precedence-value | primary]
no precedence
Context
config>service>cpipe>spoke-sdp
config>service>epipe>spoke-sdp
This command
Description
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
will begin to forward traffic.
The no form of the command returns the precedence value to the default.
4
Default
precedence-value — Specifies the spoke SDP precedence.
Parameters
Page 236
spe
cifies the precedence of the SDP binding when there are multiple SDP bindings
7210 SAS M Services Guide

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents