Python para Recopilación de Información en F5 BIG-IP
He creado un script de Python que te permite obtener información crucial de tu dispositivo F5 de manera rápida y sencilla. Con él, podrás obtener: 📋 Información del Sistema: Hostname, versión de TMOS, modelo de hardware y número de serie. 🚦 Estado de Alta Disponibilidad (HA) 🌐 Servidores Virtuales: Estado, dirección de destino, disponibilidad y un par de detalles importantes. El script utiliza la librería f5-sdk para conectarse a tu dispositivo F5 BIG-IP y extraer la información relevante. Solo necesitas proporcionar el nombre de usuario y la dirección IP del dispositivo como argumentos. https://github.com/exzo3/virtual-server/tree/main
Future F5 versions & automation support
Hi! Seeing that BigIP v17.x is EOL March 31, 2027, is there a v18.x in the pipeline some where in the future, or do we need to make the switch to BigIP NEXT? Ansible is highly supported for BigIP LTM, but not really for BigIP NEXT LTM. Is that still coming, or do we switch to something else like F5 FAST, AS3, or Infrastructure As Code? Kind Regards
show system - attribute values
After PSU has been changed values [power, temperature, voltage] remain at zero. When issuing the command ‘show system ‘ an hour later, it seems that the value of these sensors have been updated. And the question, whether this behavior is expected? Is there an hourly health check running? Model: r5600 # show system At 3pm: system health components component psu-1 hardware appliance/hardware/psu/psu1 state name psu-1 state health ok state severity info ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE NAME ATTRIBUTE DESCRIPTION HEALTH SEVERITY VALUE UPDATED AT ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- module:communication-error Module communication error ok info false 2025-01-03T15:01:33-05:00 psu:sensor:current-in PSU Current In (A) ok info 0 2025-01-03T15:01:33-05:00 psu:sensor:current-out PSU Current Out (A) ok info 0 2025-01-03T15:01:33-05:00 psu:sensor:fan1-speed PSU Fan 1 Speed (RPM) ok info 0 2025-01-03T15:01:33-05:00 psu:sensor:power-in PSU Power In (W) ok info 0 2025-01-03T15:01:33-05:00 At 4pm: # show system : system health components component psu-1 hardware appliance/hardware/psu/psu1 state name psu-1 state health ok state severity info ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE NAME ATTRIBUTE DESCRIPTION HEALTH SEVERITY VALUE UPDATED AT ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- module:communication-error Module communication error ok info false 2025-01-03T15:01:33-05:00 psu:sensor:current-in PSU Current In (A) ok info 1.078 2025-01-03T16:00:01-05:00 psu:sensor:current-out PSU Current Out (A) ok info 16.875 2025-01-03T16:00:01-05:00 psu:sensor:fan1-speed PSU Fan 1 Speed (RPM) ok info 9440 2025-01-03T16:00:01-05:00 psu:sensor:power-in PSU Power In (W) ok info 220 2025-01-03T16:00:01-05:00
FanSpeed is 0 in SNMP Traps
Hello, we are detecting that fanspeed is cero when we attack the OID: snmpwalk -c sd7364 localhost 1.3.6.1.4.1.3375.2.1.3.2.1.2.1.3 F5-BIGIP-SYSTEM-MIB::sysChassisFanSpeed.1 = Gauge32: 0 F5-BIGIP-SYSTEM-MIB::sysChassisFanSpeed.2 = Gauge32: 0 F5-BIGIP-SYSTEM-MIB::sysChassisFanSpeed.3 = Gauge32: 0 F5-BIGIP-SYSTEM-MIB::sysChassisFanSpeed.4 = Gauge32: 0 Do anyone why that is happening? I saw the same values in al the other F5 in our sites between different models and version Regards, Aitor