[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring Link Services Acknowledgment Timers

For link services interfaces configured with MLFR FRF.16, each link end point in a bundle initiates a request for bundle operation with its peer by transmitting an add link message. A hello message notifies the peer end point that the local end point is up. Both ends of a link generate a hello message periodically, or as configured with the hello timer. A remove link message notifies the peer that the local end management is removing the link from bundle operation. End points respond to add link, remove link, and hello messages by sending acknowledgment messages.

You can configure the maximum period to wait for an add link acknowledgment, hello acknowledgment, or remove link acknowledgment by including the acknowledge-timer statement at the [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] hierarchy level:




acknowledge-timer milliseconds;

The acknowledgment timer can be from 1 through 10 milliseconds. The default is 4 milliseconds.

For link services interfaces, you can configure the number of retransmission attempts to be made for consecutive hello or remove link messages after the expiration of the acknowledgment timer by including the acknowledge-retries statement at the [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] hierarchy level:




acknowledge-retries number;

acknowledgment-retries can be a value from 1 through 5. The default is 2.

You can configure the rate at which hello messages are sent by including the hello-timer statement at the [edit interfaces ls-fpc/pic/port:channel mlfr-uni-nni-bundle-options] hierarchy level:




hello-timer milliseconds;

A hello message is transmitted after the specified period (in milliseconds) has elapsed. The hello timer can be from 1 through 180 milliseconds; the default is 10 milliseconds. When the hello timer expires, a link end point generates an add-link message.

[Contents] [Prev] [Next] [Index] [Report an Error]