No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ-How to configure two-node cluster preemption delay of USG5300

Publication Date:  2012-09-11 Views:  271 Downloads:  0
Issue Description
FAQ-How to configure two-node cluster preemption delay of USG5300?
Alarm Information
Handling Process
Root Cause
Preemption always enabled after main USG5300 restart finished or failback. After main USG5300 restart, because of the higher priority of main USG5300 than backup USG5300, preemption operation enabled. If the preemption delay is too short, then main USG5300  will handover into main device, but the session table of original main USG5300 hasn’t backup completely yet, and that leads to incomplete session table on main USG5300, parts of operation will be interrupted if flow handover happens at this time, so, the preemption delay of main USG5300 needs to be a little longer (at least 16 seconds), but for backup USG5300, problem like this doesn’t exist (because preemption operation will not enabled after backup firewall restart ), so, short preemption delay can be configured.