F5CAB5: BIG-IP Administration Support and TroubleshootingDemo

By F5 · Question Mode

QuestionQ11

Determine resource utilization
warning tmm[<pid>]: 011e0002:4: sweeper_segment_cb_any: Aggressive mode /Common/default-eviction-policy activated (0) (global memory). (345209/690176 pages)  
warning tmm1[<pid>]: 011e0002:4: sweeper_segment_cb_any: Aggressive mode /Common/default-eviction-policy activated (1000000000000) (global memory). (345209/690176 pages)  
warning tmm[<pid>]: 011e0003:4: Aggressive mode sweeper: /Common/default-eviction-policy (0) (global memory) 1 Connections killed  
warning tmm1[<pid>]: 011e0003:4: Aggressive mode sweeper: /Common/default-eviction-policy (1000000000000) (global memory) 2 Connections killed  
warning tmm[<pid>]: 011e0003:4: Aggressive mode sweeper: /Common/default-eviction-policy (0) (global memory) 1 Connections killed

What is occurring when the BIG-IP Administrator observes the LTM log messages displayed above?

Choose two
  • A The global eviction policy is triggered due to swap memory being used too high
  • B The BIG-IP system starts reaping connections, all the connections will be dropped
  • C The BIG-IP system starts reaping connections, some connections will be dropped
  • D The global eviction policy is triggered due to TMM memory exhaustion
Explanation

A global BIG-IP eviction policy uses memory thresholds and activates an aggressive sweeper as TMM memory capacity is exhausted. The sweeper selects and terminates connections according to its eviction policy; the logged “Connections killed” counts show that some connections are dropped, not every connection. Linux swap usage is not the trigger for this global TMM eviction policy.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!