Skip to main content
Michio
Michio
New Member
January 17, 2023
Question

Bug ID 813207 (7.0.9) and 831885 (7.0.8) more infomation

  • January 17, 2023
  • 3 replies
  • 2609 views

I'm considering upgrading to 7.0.9.

I checked the release notes of 7.0.9.

I was wondering about the bug id 813207.

813207: Virtual MAC address is sent inside GARP by the secondary unit after a reboot.

For a few seconds, both become active?

This BUG looks deadly.

Will this BUG occur 100% of the time?

If anyone has any information, please let me know.

 

If 7.0.9 is NG, I'm considering upgrading to 7.0.8.

I checked the release notes of 7.0.8.

I was wondering about the bug id 831885.

831885: Unable to access GUI via HA management interface of secondary unit.

This is inconvenient.

Will this BUG occur 100% of the time?

If anyone has any information, please let me know.

3 replies

abarushka
Staff
abarushka
Staff
January 17, 2023

Hello,

 

You may consider to request bug scrub in case you have valid support contract:

 

https://community.fortinet.com/t5/Customer-Service/Support-Portal-Advanced-Services-Requests/ta-p/193492

Michio
MichioAuthor
New Member
January 18, 2023

Thank you.

 

I subscribe to Maintenance support.

Maintenance support says, "There are no reports or information on fatal defects."

I wrote because I wanted information whether it was a general error or a specific error.

pbazelmans
pbazelmans
New Member
March 17, 2023

I (maybe) encounter this issue in a cluster running 7.0.10. Sometimes, so not ALL the time, when the secondary unit boots, comes online, after that we encounter packetloss... at this moment, when we look at the switches (Cisco), there are "mac-flap" syslog messages appearing. We have to reboot the secondary unit again to solve this issue. When the unit comes back online for the second time, we have no problems anymore and the cluster is running ok. I am wondering if this could be the issue as mentioned by bug ID 813207. Shortly, we will update the units to 7.0.11 to see if this issue has been solved.

tthiruchelvam
tthiruchelvam
New Member
August 28, 2023

Hi,

 

Have you solved the issue after updating your cluster to 7.0.11 or to .12?

 

Thank you in advance.

 

Regards, Thusi.

srajeswaran
Staff
srajeswaran
Staff
August 28, 2023

7.0.11 include fix for both these issues, so ideally you are not expected to face this issue. If you face the same issue after upgrade to latest version 7.0.11/7.0.12, please open a TAC ticket to get it investigated.

Terms & ConditionsAccessibility statement