For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

wsanders_233261's avatar
wsanders_233261
Icon for Nimbostratus rankNimbostratus
Jun 25, 2018

LTM HA meltdowns with nonsensical self IP

Our LTM HA is repeatedly melting down with this mcpd message in the logs:

 

Jun 25 11:59:26 ext-lb01 err mcpd[5764]: 01020036:3: The requested self IP (/Common/10.10.10.1) was not found.

 

There is no IP address 10.10.10.1 configured anywhere in the /config files.

 

The self IP address is actually 10.10.16.1

 

Anybody seen this? This is BIG-IP SW version 13.1.0.5.

 

application delivery
LTM

1 Reply

  • wsanders_233261's avatar
    wsanders_233261
    Icon for Nimbostratus rankNimbostratus
    Jul 06, 2018

    This turned out to possibly be bug 658716 as reported in 13.1.X release notes (https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/relnote-supplement-bigip-13-1-0-4.html)

     

    Support said this bug was actually introduced in 13.0, so we had to downgrade to 12.X, which was a huge PITA because the config files are not downstream-portable. Be careful with 13.X

     

    Jun 27 14:05:27 ext-lb02 warning mcpd[27298]: 01071aea:4: CMI heartbeat timer expired, status: 10.10.16.1 Followed by HA disconnecting and daemons restarting, etc.

     

    This happened on only one of two pairs of HA vCMP guests in a cluster. We left the other pair of guests and the hypervisor alone for now but downgrading fixed it.