Forum Discussion

Hannes_Rapp_162's avatar
Hannes_Rapp_162
Icon for Nacreous rankNacreous
Jun 20, 2016

One common issue to check for...

4. Ensure that both F5 1600 units can ping each other from the high-availability VLAN

What is your Port Lockdown setting (SelfIP)? Make sure it's not 'Allow None'. Preferred configurations for HA VLAN/SelfIPs are 'Allow Default' (the safe bet regardless of BigIP version), or 'Allow Custom' which includes all the ports that HA daemons use (varies across BigIP versions)

  • Chris_Reid_1643's avatar
    Chris_Reid_1643
    Icon for Nimbostratus rankNimbostratus
    Jun 20, 2016
    Hi Hannes, The "Port Lockdown" settings for the selfIP addresses are set to "Allow Default", and the units can ping each other from the selfIP addresses created for high-availability.
  • Hannes_Rapp_162's avatar
    Hannes_Rapp_162
    Icon for Nacreous rankNacreous
    Jun 20, 2016
    Ok. Have a look into /var/log/ltm file, issue a grep for 'daemon_heartbeat'. That file usually directly reports any changes to HA status, and the reason behind it
  • Chris_Reid_1643's avatar
    Chris_Reid_1643
    Icon for Nimbostratus rankNimbostratus
    Jun 20, 2016
    Will do. Thanks for the quick response.
  • Chris_Reid_1643's avatar
    Chris_Reid_1643
    Icon for Nimbostratus rankNimbostratus
    Jun 21, 2016
    After the "Device Group" configuration on the primary F5, the following error messages appear in the LTM log file: Error Messages on Primary F5 Unit: Jun 21 02:34:31 YPG-L-TLIDC4-001 err mcpd[4953]: 01071587:3: Commit ID message ignored, commit ID originator not specified Error Messages on Secondary F5 Unit: Jun 21 02:34:29 err mcpd[6588]: 01071587:3: Commit ID message ignored, commit ID originator not specified Jun 21 02:34:31 notice sod[7120]: 010c005c:5: Failover condition reported by /Common/ for traffic group /Common/traffic-group-1, it will not be able to go active.