Bug ID 825445: Using broadcast or subnet address as self IP may cause interruption during config sync

Last Modified: Oct 16, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1

Opened: Sep 12, 2019
Severity: 3-Major

Symptoms

The mcpd daemon exits with -1 exit code, triggering restart of mcpd and some other system services. You might see messages in ltm.log: -- err mcpd[21618]: 0107142f:3: Can't connect to CMI peer 192.168.1.136, TMM outbound listener not yet created. -- err mcpd[21618]: 01070596:3: An unexpected failure has occurred, Cannot get route for dest 192.168.1.136 in rd0 Invalid entry type: 3 - net/validation/routing.cpp, line 1231, exiting.

Impact

This triggers interruption during config sync on the device initiating the exchange. Restart of mcpd and other important system services may cause temporary interruption in device operation.

Conditions

-- Device has been configured to use a non-unicast address as its self IP. -- There are attempts to establish device trust with it.

Workaround

Do not use non-unicast addresses for self IP configuration.

Fix Information

None

Behavior Change