Configuring The Timeout Factor - 3Com MSR 50 Series Configuration Manual

Configuring the Timeout
Factor
forward delay time should be. Note that if the forward delay setting is too
small, temporary redundant paths may be introduced; if the forward delay
setting is too big, it may take a long time for the network to resume
connectivity. We recommend that you use the default setting.
An appropriate hello time setting enables the device to timely detect link
■
failures on the network without using excessive network resources. If the hello
time is set too long, the device will take packet loss on a link for link failure and
trigger a new spanning tree computing process; if the hello time is set too
short, the device will send repeated configuration BPDUs frequently, which
adds to the device burden and causes waste of network resources. We
recommend that you use the default setting.
If the max age time setting is too small, the network devices will frequently
■
launch spanning tree computing and may take network congestion to a link
failure; if the max age setting is too large, the network may fail to timely detect
link failures and fail to timely launch spanning tree computing, thus reducing
the auto-sensing capability of the network. We recommend that you use the
default setting.
The setting of hello time, forward delay and max age must meet the following
formulae; otherwise network instability will frequently occur.
2 × (forward delay - 1 second) ƒ max age
■
Ma x age ƒ 2 × (hello time + 1 second)
■
We recommend that you specify the network diameter in the stp
bridge-diameter bridge-number command and let MSTP automatically calculate
an optimal setting of these three timers.
Configuration example
# Set the forward delay to 1,600 centiseconds, hello time to 300 centiseconds,
and max age to 2,100 centiseconds.
<Sysname> system-view
[Sysname] stp timer forward-delay 1600
[Sysname] stp timer hello 300
[Sysname] stp timer max-age 2100
After the network topology is stabilized, each non-root-bridge device forwards
configuration BPDUs to the surrounding devices at the interval of hello time to
check whether any link is faulty. Typically, if a device does not receive a BPDU from
the upstream device within nine times the hello time, it will assume that the
upstream device has failed and start a new spanning tree computing process.
In a very stable network, this kind of spanning tree computing may occur because
the upstream device is busy. In this case, you can avoid such unwanted spanning
tree computing by lengthening the timeout time.
Configuration procedure
Follow these steps to configure the timeout factor:
To do...
Enter system view
Configuring the Root Bridge
Use the command...
system-view
465
Remarks
-