Skip to main content
edoutreleau
New Member
October 18, 2017
Question

my 1500D silently freeze

  • October 18, 2017
  • 9 replies
  • 11520 views

Hi 

 

i m using a cluster of 1500D running 5.2.11

and from time to time one member silently crash

there s nothing on the console , nothing in the log.

the only way to get it back to life is to pull off power cord.

 

when it reboot i got a mesage that i need to make a fsck but nothing else.

 

The only log i got is from the partner in the cluster who said that his companion is not there anymore. 

 

Oct 13 13:55:04 cns-fw date=2017-10-13 time=13:55:04 devname=fw-G1 devid=FG1K5D3I15803586 logid=0108037901 type=event subtype=ha level=critical vd="root" logdesc="Heartbeat device interface down" msg="Heartbeat device(interface) down" ha_role=slave hbdn_reason="neighbor-info-lost" devintfname="port40" Oct 13 13:55:04 cns-fw date=2017-10-13 time=13:55:03 devname=fw-G1 devid=FG1K5D3I15803586 logid=0108037893 type=event subtype=ha level=critical vd="root" logdesc="Virtual cluster member dead " msg="Virtual cluster detected member dead" vcluster=1 ha_group=100 sn="FG1K5D3I15803589" Oct 13 13:55:04 cns-fw date=2017-10-13 time=13:55:03 devname=fw-G1 devid=FG1K5D3I15803586 logid=0108037893 type=event subtype=ha level=critical vd="root" logdesc="Virtual cluster member dead " msg="Virtual cluster detected member dead" vcluster=2 ha_group=100 sn="FG1K5D3I15803589" Oct 13 13:55:04 cns-fw date=2017-10-13 time=13:55:04 devname=fw-G1 devid=FG1K5D3I15803586 logid=0108037901 type=event subtype=ha level=critical vd="root" logdesc="Heartbeat device interface down" msg="Heartbeat device(interface) down" ha_role=master hbdn_reason="neighbor-info-lost" devintfname="mgmt1" Oct 13 13:55:04 cns-fw date=2017-10-13 time=13:55:04 devname=fw-G1 devid=FG1K5D3I15803586 logid=0108037901 type=event subtype=ha level=critical vd="root" logdesc="Heartbeat device interface down" msg="Heartbeat device(interface) down" ha_role=master hbdn_reason="neighbor-info-lost" devintfname="mgmt2" Oct 13 13:55:06 cns-fw date=2017-10-13 time=13:55:06 devname=fw-G1 devid=FG1K5D3I15803586 logid=0108037892 type=event subtype=ha level=notice vd="root" logdesc="Virtual cluster member state moved" msg="Virtual cluster's member state moved" ha_role=master vcluster=1 vcluster_state=work vcluster_member=0 hostname="fw-G1" sn="FG1K5D3I15803586" Oct 13 13:55:06 cns-fw date=2017-10-13 time=13:55:06 devname=fw-G1 devid=FG1K5D3I15803586 logid=0108037892 type=event subtype=ha level=notice vd="root" logdesc="Virtual cluster member state moved" msg="Virtual cluster's member state moved" ha_role=master vcluster=2 vcluster_state=work vcluster_member=0 hostname="fw-G1" sn="FG1K5D3I15803586"

 

the fortigate support is really of no use 

 

how can i investigate on this problem? 

    9 replies

    Toshi_Esumi
    SuperUser
    SuperUser
    October 18, 2017

    I don't remember well because it was long time ago when we were running our 1500D clusters with 5.2.x and experienced similar issue. It happens only to slave/passive units and we dealt with Fortinet TAC quite some time and they eventually put a patch on the OS.

    I recommend you open a case with Fortinet TAC. It's probably specific to your HA setting.

    edoutreleau
    New Member
    October 19, 2017

    Thanks for your answer

     

    I will do that 

    Toshi_Esumi
    SuperUser
    SuperUser
    October 19, 2017

    Be patient until get it escalated up to Level 2 or 3. The solution might be only available on 5.4.x or 5.6.x though.

    Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
    Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
    Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT