Investigating BIG-IP System Hardware Failure
Please, what can you make out of this log? I'm investigating a power unit failure. Thanks Dec 1 12:59:28 juliet crit chmand[6770]: 012a0013:2: Blade 0 hardware sensor critical alarm: : Bad Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor cha_spa3_pws_2: current reading 6 (.DA.), new actions: BROADCAST_MSG|BIGIP_ALARM_CRITICAL| Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor fan_system4: current reading 11619 (rpm), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor fan_system1: current reading 11806 (rpm), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor fan_system2: current reading 11619 (rpm), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor fan_system3: current reading 11806 (rpm), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:29 juliet info chmand[6770]: 012a0006:6: Alert from sensor outlet_ic_temp: current reading 20 (C), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION|SYSTEM_FANS_AUTO_LOW| Dec 1 12:59:30 juliet info chmand[6770]: 012a0006:6: Alert from sensor inlet_ic_temp: current reading 20 (C), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION|SYSTEM_FANS_AUTO_LOW| Dec 1 12:59:30 juliet info chmand[6770]: 012a0006:6: Alert from sensor main_1.8vsb: current reading 1787 (mV), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:31 juliet info chmand[6770]: 012a0006:6: Alert from sensor main_1.2v: current reading 1201 (mV), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:31 juliet info chmand[6770]: 012a0006:6: Alert from sensor main_12vsb: current reading 11956 (mV), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:31 juliet info chmand[6770]: 012a0006:6: Alert from sensor main_1.5v_PCH: current reading 1494 (mV), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION|
Investigating BIG-IP System Hardware Failure
Please, what can you make out of this log? I'm investigating a power unit failure. Thanks Dec 1 12:59:28 juliet crit chmand[6770]: 012a0013:2: Blade 0 hardware sensor critical alarm: : Bad Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor cha_spa3_pws_2: current reading 6 (.DA.), new actions: BROADCAST_MSG|BIGIP_ALARM_CRITICAL| Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor fan_system4: current reading 11619 (rpm), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor fan_system1: current reading 11806 (rpm), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor fan_system2: current reading 11619 (rpm), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:28 juliet info chmand[6770]: 012a0006:6: Alert from sensor fan_system3: current reading 11806 (rpm), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:29 juliet info chmand[6770]: 012a0006:6: Alert from sensor outlet_ic_temp: current reading 20 (C), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION|SYSTEM_FANS_AUTO_LOW| Dec 1 12:59:30 juliet info chmand[6770]: 012a0006:6: Alert from sensor inlet_ic_temp: current reading 20 (C), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION|SYSTEM_FANS_AUTO_LOW| Dec 1 12:59:30 juliet info chmand[6770]: 012a0006:6: Alert from sensor main_1.8vsb: current reading 1787 (mV), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:31 juliet info chmand[6770]: 012a0006:6: Alert from sensor main_1.2v: current reading 1201 (mV), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:31 juliet info chmand[6770]: 012a0006:6: Alert from sensor main_12vsb: current reading 11956 (mV), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION| Dec 1 12:59:31 juliet info chmand[6770]: 012a0006:6: Alert from sensor main_1.5v_PCH: current reading 1494 (mV), new actions: BROADCAST_MSG|BIGIP_NOMINAL_CONDITION|
Priority Boot to Primary Device over Secondary Device
Hi all, some network people were asking if they can "hardcode" a priority to F5 devices running in active/passive pair. For example, no matter who is the active box before a complete power failure, both boxes will boot up at the same time when power restores. If secondary device booted up faster than primary device, can F5 device "wait" to allow primary device to boot up and become active? In my opinion, whoever that boots up first will see that its peer device is not up and thus will take on the Active role. Question: Does priority booting exist in F5? Why is this behavior not recommended?Troubleshooting BIG-IP Power Failure
Hello, I have the qkview from a device which experienced a power failure. The qkview is currently uploaded to ihealth. Please, which logs am I supposed to check to see the logged info regarding the power failure? I searched for the keyword "power" in the logs and turned up one entry in the var/log/ltm log but couldn't locate anything descriptive about power failure. Please help, thanks very much.Troubleshooting BIG-IP Power Failure
Hello, I have the qkview from a device which experienced a power failure. The qkview is currently uploaded to ihealth. Please, which logs am I supposed to check to see the logged info regarding the power failure? I searched for the keyword "power" in the logs and turned up one entry in the var/log/ltm log but couldn't locate anything descriptive about power failure. Please help, thanks very much.