Loading...
Loading...
High Speed Logging (HSL) does not respect the configured pool's changes and continues to send logs to the previous state of the pool. For example, consider the following configuration: -- HSL configured to send logs to pool (pool-HSL) where pool-HSL has 2 members: pm-1, and pm-2. -- There is a manual update to pool-HSL to remove pm-2, or a monitor marks pm-2 down. -- That change is not honored, and HSL continues to send logs to pm-2.
HSL logs continue being forwarded according to the previous state of the configured pool. The new state is not reflected.
-- High Speed Logging configured to log to a pool of multiple members. -- Pool members change manually or due to a monitoring probe. -- Running one of the known affected TMOS versions.
None.
Updates to pool members used as HSL destination are correctly reflected in HSL log forwarding.
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.