Bug ID 446713: Initial boot from non-Primary blades causes daemon restarts and error messages on VIPRION B4300/B4300N blades and on the VIPRION C2200 chassis.

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Opened: Jan 29, 2014
Severity: 3-Major

Symptoms

Initial boot from non-Primary blades causes daemon restarts and error messages on VIPRION B4300/B4300N blades and on the VIPRION C2200 chassis. Messages posted might appear similar to the following: -- snmpd[7175]: custom mib initialization completed. total 0 custom mib entry registered. -- snmpd[7175]: Turning on AgentX master support. -- restorecond: Reset file context /etc/mtab: system_u:object_r:etc_t:s0-system_u:object_r:etc_runtime_t:s0 -- sflow_agent[8639]: sflow_mcp.cpp::556: sflow_agent[8639]: Processed max messages (201) in a loop.

Impact

When this occurs, the system posts various error messages and the daemon restarts.

Conditions

This happens on each blade except blade1 (which is the Primary).

Workaround

Reboot. Subsequent reboots do not cause the daemon restarts.

Fix Information

None

Behavior Change