Bug ID 848777: Configuration for virtual server using shared object address-list in non-default partition in non-default route-domain does not sync to peer node.

Last Modified: Jul 22, 2021

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3

Fixed In:
16.0.0, 15.1.0.4, 14.1.2.7

Opened: Nov 12, 2019
Severity: 3-Major

Symptoms

Shared object address-list in non-default partition in non-default route-domain does not sync to peer node. The system reports the following exceptions when such an issue occurs: -- err mcpd[4941]: 0107004d:3: Virtual address (/TestwithRD1/0.0.0.0%1) encodes IP address (0.0.0.0%1) which differs from supplied IP address field (0.0.0.0). -- err mcpd[4941]: 01071488:3: Remote transaction for device group /Common/DG1 to commit id 500 6754270728594498269 /Common/bigiptest1 0 failed with error 0107004d:3: Virtual address (/TestwithRD1/0.0.0.0%1) encodes IP address (0.0.0.0%1) which differs from supplied IP address field (0.0.0.0).

Impact

Sync fails with error. Configuration does not sync to peer node. On VIPRION systems this may cause mcpd on a secondary blade to crash and fail to come up.

Conditions

-- Create custom partition. -- Create custom route-domain. -- Change custom partition. -- Create address list in non-default route domain. -- Create virtual server with previously created address list and any TCP port, or port list. -- Now, try to Sync to high availability (HA) peer.

Workaround

None

Fix Information

Configuration now syncs to peer node successfully.

Behavior Change