FD 100/320Gbps NT and FX NT IHub Services Guide Virtual Leased Line Services
Issue: 13 3HH-11985-AAAA-TQZZA 135
4.6.5.2 control-word
Table 68 control-word command
4.6.5.3 hash-label
Table 69 hash-label command
Item Description
Syntax [no] control-word
Context configure>service>epipe>spoke-sdp
Description This command indicates whether the control word is used or not. The value of the control word
is negotiated with the peer.
The control word is indicated in the label message as part of pseudowire ID FEC as the C-bit.
The control word is not mandatory for an Epipe service. Therefore the usage of the control
word is negotiated between the endpoints of the pseudowire.
Item Description
Syntax [no] hash-label
Context configure>service>epipe>spoke-sdp
Description This command enables the use of the hash label on a VLL, or VPLS service bound to LDP
SDP.
When this feature is enabled, the ingress LER is modified so that the result of the hash on the
ingress packet header is communicated to the egress data path for use as index to select the
value of the label field of the hash label. The egress data path has a set of 128 different label
field values in the range 524.288 - 1.048.575. The egress data path appends the hash label at
the bottom of the stack (BoS) and sets the S-bit to 1 to indicate that.
The hash label, also referred to as entropy label, allows LSR nodes in a network to load
balance labeled packets in a more granular fashion than allowed by simply hashing on the
standard label stack. It also removes the need to have an LSR inspect the payload below the
label stack to check for an IPv4 or IPv6 header.
Since the ingress LER hashing routine maintains packet ordering within a conversation, this
guarantees that when an LSR sprays the packets over multiple LDP ECMP paths or multiple
paths over a LAG network port by hashing the extended label stack including the hash label,
the LSR will also maintain packet ordering within a conversation.Packets that are generated in
CPM and 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 1.
The no form of this command disables the use of the hash label.
Default no hash-label
To Next Page
Loading...
Need help?
General
