Bug ID 637946: Do not manually create a sys management-ip on a clustered BIG-IP Platform through the admin_ip object.

Last Modified: Jun 10, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP All(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.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.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.0.1.1

Fixed In:
14.1.0

Opened: Jan 10, 2017
Severity: 4-Minor

Symptoms

The cluster member's blade-specific mgmt ip is not modified you run tmsh modify sys management-ip <ipaddr/netmask>.

Impact

Although the command is successful, the cluster does not use this management IP, and the blade-specific management IP is unchanged.

Conditions

This occurs when trying to change the management IP using tmsh modify sys management-ip <ipaddr/netmask> on a blade.

Workaround

Modify the blade-specific address of a cluster-member only through the sys cluster component. The correct command is tmsh modify sys cluster default members { <blade_number> { address <desired ipv4 addr> }}

Fix Information

A configuration error message is emitted which instructs the user to use the sys cluster component to modify the blade-specific address of a cluster-member.

Behavior Change

Administrators can no longer manually create a sys management-ip on any clustered BIG-IP Platform through the admin_ip object. Administrators are now guided to use the sys cluster component.