Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
12.1.2, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0, 12.1.3, 11.6.2, 11.5.5
Opened: May 31, 2017 Severity: 3-Major
The device service clustering (DSC) connection between two BIG-IP units may fail to establish. One unit will log messages similar to the following example: -- err mcpd[7912]: 01071af4:3: Inbound CMI connection from IP (192.168.100.1) denied because it came from VLAN (v1542), not from expected VLAN (tmm). While the unit at the other end of the connection will log messages similar to the following example: -- notice mcpd[5730]: 01071432:5: CMI peer connection established to 192.168.200.1 port 6699 after 0 retries May 31 20:58:04 BIG-IP-c-sea notice mcpd[5730]: 0107143c:5: Connection to CMI peer 192.168.200.1 has been removed
Config-Sync and device discovery operations will fail between affected units.
This issue occurs when the Self-IP addresses used for Config-Sync by the two BIG-IP units are not in the same IP subnet, and special routing is configured between the BIG-IP units. Examples of special routing include a gateway pool or dynamic routing configurations with multiple routes to the same destination (i.e., ECMP routing).
You can work around this issue by using Self-IP addresses for Config-Sync that are on the same IP subnet or rely on simpler routing to achieve connectivity (i.e., a single route).
Config-Sync and device discovery operations no longer fail.