The Nautica Implementation Of Bacp - Bay Networks Nautica 200 Reference Manual

NauticaRS Release 4.1 Reference Guide

The Nautica Implementation of BACP

1-26
After the negotiations for BACP have successfully taken place,
either peer can request that another link is added to the current
bundle via a BAP packet. Alternatively, if a link has already been
added to the current bundle, then a BAP
Link-Drop-Query-Request is submitted to the peer for release of
the additional bandwidth.
1. Call-Request: If a caller has reached pre-defined parameters,
the caller will make a Call-Request requesting a phone
number to dial for the additional bandwidth. The destination
can reply Yes or No to this request. If the caller receives a
No, the caller will continue with the current allocated
bandwidth. If the caller receives a Yes, the caller will call the
given Call Number (CNum).
2. Callback-Request: A Callback-Request is the opposite to a
Call-Request. When receivers match or exceed their
pre-defined parameters, they will send the caller a
Callback-Request. This request includes the number from the
receiver's CNum table. The caller will dial that specific
number.
In both these instances the caller is charged for the additional
bandwidth.
Before BACP can be used on a Nautica router, there are some
parameters that need to be set to support the feature.
• Multilink PPP and BACP must be enabled on both peers
(Advance>PPP in Nautica Wizard, ppp# context in BCC).
• Demand Threshold, Demand Threshold Period, Idle
Threshold PC, and Max Bandwidth are optional parameters
that can be turned on to work with Multilink and BACP
(Advance>Paths in Nautica Wizard, path configured object
in BCC).
• CNum (up to four callback numbers) should be set
(Advance>Paths in Nautica Wizard, path configured object
in BCC).
117237-C Rev. A