Enterasys 6000 Betriebsanweisung
Configuring Frame Relay
6-19
Excess Burst Size (In/Out)
(B
E
) is the incoming or outgoing (depending on the parameter) maximum amount of
data in excess of the
Committed Burst Size
that the network will attempt to transfer
during the time interval used for the
Committed Burst Size
. Any data exceeding this
value will be buffered in the FRX/FRM.
BECN Recovery Count
is a method of controlling the rate of return to maximum traffic flow after it has been
reduced due to congestion. If a packet is received with the BECN (backward explicit
congestion notification) bit set, the configured
reduced due to congestion. If a packet is received with the BECN (backward explicit
congestion notification) bit set, the configured
Excess Burst Size (Out)
will be ignored
and the effective value will become
0
(limting traffic flow to the value configured for
Committed Burst Size (Out)
). From that point on, for each "n" packets (where "n" is the
value of
BECN Recovery Count
) received (sequentially) without BECN set, the
effective
Excess Burst Size (Out)
will be increased by 1/8 of the configured value.
As long as no BECNs are received, the effective burst size will continue to increase
until it reaches the full configured value. Any time a BECN is received, however, the
effective value will return to the value of
until it reaches the full configured value. Any time a BECN is received, however, the
effective value will return to the value of
Committed Burst Size (Out)
.
Outgoing DLCI Priority
sets a priority for this DLCI among others over the physical port.
0
is the lowest pri-
ority,
4
the highest.
Backup Group Number
specifies (if configured as any number other than
0
) that this is a primary DLCI, and
identifies the backup DLCI(s) (see "Configuring Frame Relay Backup Groups" on
page 6-35) that will take over if this DLCI fails. This parameter is applicable only on
an "initiating" node, which is the node that will initiate the switchover to a backup
DLCI. At switchover, the initiating node notifies the remote node of the change.
page 6-35) that will take over if this DLCI fails. This parameter is applicable only on
an "initiating" node, which is the node that will initiate the switchover to a backup
DLCI. At switchover, the initiating node notifies the remote node of the change.
A DLCI cannot be both a backup and a primary.
Do not configure a
Backup Group Number
on this DLCI at the
remote (non-initiating) end.
Enable Backup Protocol?
specifies that (if
Y
) this DLCI will be used as a non-initiating backup. The DLCI will
wait for a backup protocol message from the initiating end, telling the backup where
to send the rest of the messages.
to send the rest of the messages.
Remote RLP/Port/DLCI
identifies the primary DLCI in the non-initiating (called "remote" for the purpose of
differentiating) node to which that this DLCI connects for normal operation.
differentiating) node to which that this DLCI connects for normal operation.
The primary and all of its backup DLCIs in the non-initiating
node must be on the same RLP.
node must be on the same RLP.