on
09-Mar-2015
14:05
- edited on
05-Jun-2023
22:32
by
JimmyPackets
Problem this snippet solves:
This script will report on the impact of 2048bit keys on your BIG-IP infrastructure.
How to use this snippet:
Change is coming with new requirements for 2048-bit keys instead of the current industry-wide usage of 1024-bit keys. This tool will help users gain understanding into whether or not their LTM infrastructure is ready for the change.
This application will report the impact of 2048bit keys on your infrastructure:
genreport.py system1 system2 system3 filename.pdf
Note:This tool doesn't deal with the sub-second transaction rate (Please see Solution 6475 for more details.) at all - it's completely bound to the RRD information on-box, and as the size of the time frame grows, it'll smooth the max TPS numbers down for that period. This is the script is defaulted to 7 days - it seemed to be a decent compromise. For bursty, sub-second SSL environments: because the script relies on RRD, reporting on smoothed data can be misleading. The best way to handle these environments is to take sample packet captures throughout your peak periods and count handshakes in 10ms windows.
5.1 Required Packages
5.2 Procedure
Code :
# no snippet