How to calculate the timeout period of packets on the STP interface

13

The timeout period of packets on the STP interface can be calculated based on the following formula: hello timer out = hello time * 3 * timer factor

By default, the value of hello time is 2s and the value of timer factor is 3s.

Other related questions:
What are the timeout mechanism of CAPWAP links and timeout period calculation
Timeout mechanism of CAPWAP links: 1. The timeout of CAPWAP links is detected by using keepalive (UDP port 5247) and echo (UDP port 5246) packets. - The keepalive packets detect the status of Link Layer Protocols. - The echo packets detect the status of Link Control Protocols (LCPs). 2. The AP sends the keepalive and echo packets. The AC sends response packets when receiving the keepalive and echo packets. 3. After the CAPWAP enters the Run state, the AP periodically sends the keepalive and echo packets at almost the same time. This interval is configured on the AC. 4. If the AP does not receive response packets from the AC during a certain period of time, the CAPWAP link is considered faulty and enters the Down state. This interval is the timeout period. 5. If the AC does not receive the keepalive or echo packets from the AP during the timeout period, the CAPWAP link is considered faulty and enters the Down state. Timeout period calculation: The timeout of CAPWAP link mechanism uses a timer to calculate the timeout period. A timer in the system is a countdown tool. For example, the AP sends the keepalive packets every 30s. When the CAPWAP link enters Run state, the AP immediately sends a keepalive packet and repeatedly sends keepalive packets at an interval of 30s. The timeout of CAPWAP link period is also calculated using a timer. For example, when the CAPWAP link enters the Run state, the AP immediately sends a keepalive packet, and the timer starts a countdown of 120s. When the AC sends a response packet, the timer restarts the countdown of 120s. If the timer restarts the countdown and the AP does not receive any response packet from the AC, the CAPWAP link is faulty. The timeout period of echo packets is calculated in the same way as the timeout period of keepalive packets. The timer is updated immediately when an echo packet is received from the AP.

What is the timeout period for LACPDUs
You can configure a switch to send an LACPDU every 1 or 30 seconds. The two sending intervals are defined in IEEE 802.3ad. You can run the lacp timeout { fast | slow } command to set the timeout period for receiving LACPDUs on an interface. After this command is used, the local end informs the peer end of the timeout period through LACPDUs. If fast is configured, the peer end sends LACPDUs every one second. If slow is configured, the peer end sends LACPDUs every 30 seconds. The timeout period of LACPDUs is three times the interval for sending LACPDUs. That is, if fast is configured, the timeout period for receiving LACPDUs is 3 seconds. If slow is configured, the timeout period for receiving LACPDUs is 90 seconds. You can configure different timeout periods on the two ends. To facilitate maintenance, however, you are advised to configure the same timeout period on both ends.

Configuring the IPSec SA lifetime on the firewall
Configure the IPSec SA lifetime on the USG. Configure the IPSec VPN SA lifetime. 1. Configure IKE SA hard lifetime. You can configure per-SA IKE lifetime, but cannot configure a global IKE lifetime. system-view //Access the system view. ike proposal proposal-number //Access the IKE proposal view. sa duration seconds //Configure the IKE SA hard lifetime. Notes for configuring IKE SA lifetime: a) If the hard lifetime expires, the IKE SA will be deleted and re-negotiated. The IKE negotiation involves DH calculation and may take a long time. To ensure the secure communications, you are advised to set the lifetime to a value larger than 600 seconds. b) When the soft lifetime expires, a new SA is negotiated to replace the original SA. Before the new SA is negotiated, the original SA is still in use. After the new SA is established, the new SA is used, and the original SA will be automatically deleted when the hard lifetime expires. The default IKE SA hard lifetime is 86,400 seconds (a day). 2. Configure IKE SA soft lifetime. system-view //Access the system view. ike peer peer-name //Access the IKE peer view. sa soft-duration time-based buffer seconds //Configure the IKE SA soft lifetime. The configuration applies only to IKEv1. a) By default, the soft lifetime is 9/10 of the hard lifetime. When the soft lifetime expires, a new SA is negotiated to replace the original SA. b) If the soft lifetime is specified and the hard lifetime is greater than the soft lifetime by more than 10s, the specified soft lifetime applies; otherwise, the default soft lifetime applies. display ike proposal //Display the configured IKE SA hard lifetime. [USG] display ike proposal priority authentication authentication encryption Diffie-Hellman duration method algorithm algorithm group (seconds) --- 10 PRE_SHARED MD5 DES_CBC MODP_768 5000 default PRE_SHARED SHA1 AES_CBC MODP_1024 86400 display ike peer [ brief | name peer-name ] //Display the configured IKE SA soft lifetime. [USG] display ike peer name b -- IKE peer: b Exchange mode: main on phase 1 Pre-shared key: %$%$biLQ*117FHI`Qe&-VY`>l%yp%$%$ Local certificate file name: Proposal: 10 Local ID type: IP Peer IP address: 202.38.169.1 VPN instance: Authentic IP address: IP address pool: Peer name: Peer domain name: VPN instance bound to the SA: NAT traversal: enable SA soft timeout buffer time: 22 seconds OCSP check: disable OCSP server URL: Applied to 1 policy: ppp1-1-isakmp

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top