Last Modified: Nov 07, 2022
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
10.2.3, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4
Fixed In:
12.0.0, 11.6.0 HF5, 11.5.3 HF2, 11.4.1 HF9, 11.2.1 HF15
Opened: Oct 09, 2014 Severity: 3-Major Related Article:
K16210
The mcpd configuration errors on secondary blades of a VIPRION platform may disrupt data plane functionality. As a result of this issue, you may encounter the following symptom: The system logs messages in the /var/log/ltm file that appear similar to the following example: -- err mcpd[7624]: 01070935:3: Unexpected exception caught in MCPProcessor::rm_DBLowHighWide(). -- err bcm56xxd[5081]: 012c0010:3: Error trunk <trunk_name> on unit 0 does not exist bsx.c(2429).
VLAN and trunk members are not programmed correctly, resulting in disrupted traffic flow. If a trunk has members spanning multiple blades, and if the trunk hashing algorithm selects a member port on a secondary blade for a given traffic flow, that traffic flow will be disrupted.
This issue occurs when all of the following conditions are met: -- The mcpd process is restarted on a secondary blade of a VIPRION platform. -- The mcpd process receives an error when attempting to load the configuration. For example: err mcpd[7624]: 010717b5:3: HA group (HA) cannot be removed. It is used by traffic group (/Common/traffic-group-1 ).
None.
The system now handles these conditions so that the issue no longer occurs.
