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.


Access web problem as different heartbeat interfaces between primary/secondary devices when load sharing E8080E VRRP

Publication Date:  2012-09-22 Views:  117 Downloads:  0
Issue Description
Access the web page too slow or in failure because the different heartbeat Eth-trunk physical interfaces between the primary/secondary device when load sharing of E8080E VRRP. An oversea site Nat server provide website server, the speed is too slow or fail to access by the outside network. But it is no problem when by internal network. 
Alarm Information
Handling Process
Binding the secondary FW G/9/0/0 interface to the Eth-Trunk. The problem solved.
Root Cause
By the inspection, find the reason is that the heartbeat interface Eth-trunk 5 of main FW has seven physical interfaces, but the number of the secondary FW is only six. The number is different. Sending the message according to the physical interface in turn when Eth-Trunk backup the session. So when the main FW using the G9/0/0/0 interface backup the session from Eth-trunk 5, as the secondary FW don’t banding the G9/0/0/0 interface to the Eth-Trunk and add to the trust zone, the G1/0/0 of secondary FW drop the package after receive the package. So the session of main FW can’t backup to the secondary FW. the package dropped by the secondary FW because it can’t match the session when the response package reach the secondary FW
Load sharing when the number of primary/secondary FW heartbeat is different, some mistakes maybe happen such as the service package loss.