Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
11.0.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.5.1 HF1, 11.6.1 HF1, 11.5.1 HF2, 11.6.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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.6.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.0.0
Opened: Nov 25, 2015 Severity: 3-Major Related Article:
K13266073
If the DSC sync device object is renamed on a standalone configuration, the system posts a log message indicating that the device is going momentarily offline for traffic-group-1. That message looks like this: -- notice sod[...]: 010c0056:5: Deactivating traffic group /Common/traffic-group-1. -- notice sod[...]: 010c0057:5: Activating traffic group /Common/traffic-group-1. -- notice sod[...]: 010c0054:5: Offline for traffic group /Common/traffic-group-1. notice sod[...]: 010c006d:5: Leaving Offline for Active for dbvar not redundant. -- notice sod[...]: 010c0053:5: Active for traffic group /Common/traffic-group-1. This action is illegal if the device is part of a device trust group. On standalone configurations, setting the hostname through the GUI also implicitly renames the self device.
If this happens on a vCMP hypervisor, then guests on that chassis may momentarily go offline due to an HA table entry tripping: warning chmand[...]: 012a0004:4: hypervisor_offline take action is set warning sod[...]: 01140029:4: HA hypervisor_offline_t chmand fails action is go offline. On devices that are not vCMP hypervisors, there is no impact to traffic. sod going offline for a traffic group does not stop traffic when the device is configured as standalone. The GUI shows this behavior only when the device is configured as standalone.
This happens only when the device is not in trust with any other devices. There is no impact unless it occurs on a vCMP hypervisor.
There is no workaround for renaming the self device. The hostname can be changed using tmsh ('modify sys global-settings hostname new-hostname.com'), which unlike the GUI does not rename the self device.
None