HP 6125XLG - Adjusting LSP Parameters

11
inhibits the local AVF for a certain time to avoid loops. When the inhibition time expires, if the RB
is still the AVF of the VLAN, the RB restores the role of AVF.
• CSNP interval—On a broadcast network, the DRB advertises CSNPs at the CSNP interval to
perform network-wide LSDB synchronization. A CSNP records all LSP digests of the local LSDB.
When an RB receives a CSNP, the RB compares the CSNP against the local LSDB to verify whether
some LSPs are aged out or missing. If the CSNP has an LSP digest that the local LSDB does not have,
the RB sends a PSNP packet to request the LSP.
To configure TRILL timers:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter Layer 2 Ethernet
or aggregate interface
view.
interface interface-type
interface-number
N/A
3. Configure the Hello
interval.
trill timer hello interval
The default setting is 10 seconds.
This command sets the Hello interval for the
RB. The Hello interval of the DRB is 1/3 of the
Hello interval of the RB, so that the DRB
failures can be quickly detected.
4. Configure the Hello
multiplier.
trill timer holding-multiplier
count
The default setting is 3.
5. Configure the inhibition
time.
trill timer avf-inhibited time The default setting is 30 seconds.
6. Configure the CSNP
interval.
trill timer csnp interval The default setting is 10 seconds.
Adjusting LSP parameters
You can modify the following LSP parameters:
• LSP maximum age—An LSP originated by an RB uses the maximum age as the remaining lifetime.
When the remaining lifetime of an LSP in the LSDB is 0 seconds, the RB removes the LSP's content,
keeps the LSP's digest, and purges the LSP from the network by advertising the LSP that has the
remaining lifetime set to 0.
• LSP refresh interval—When the remaining lifetime of a locally originated LSP is no greater than
(maximum age – refresh interval), the LSP is refreshed even if no change occurs to it. This
mechanism avoids frequent LSP aging and ensures network stability.
• Maximum length of an LSP originated by an RB—The actual maximum LSP length is determined by
the smallest of following values:
{ The configured value.
{ The interface MTU.
{ The maximum length of an LSP originated by an RB (which is carried in LSPs).
• Maximum length of an LSP that can be received by an RB—When the RB receives an LSP
exceeding the length, the RB drops the LSP.
• Overload bit of LSPs—When the Overload bit in the LSPs sent by an RB is set, the RB fails and
cannot correctly perform route selection and packet forwarding. When the RB cannot record the