标签归档:F5

F5前面板指示灯说明

Topic

This article applies to legacy BIG-IP platforms supported by BIG-IP 9.x through 11.1.0. For information about the LED behavior for current platforms supported by current versions, refer to the platform guide for your specific platform.

Note: For information about how to locate F5 product guides, refer to K12453464: Finding product documentation on AskF5.

Legacy platforms

  • BIG-IP 1500 (C36)
  • BIG-IP 3400 (C62)
  • BIG-IP 4100 (D46)
  • BIG-IP 6400 (D63)
  • BIG-IP 6800 (D68)
  • BIG-IP 8400 (D84)
  • BIG-IP 8800 (D88) – version 9.4 and later only

LED indicators

Legacy platforms use 4 front-panel LEDs to indicate a system’s status:

  • Power
  • Status
  • Activity
  • Alarm

Power LED indicator

The Power LED indicator reports the power status: on (green), off (none), or error (red).

LED behaviorDescription
Solid GreenNormal Power ON condition
Off (none)Normal Power OFF condition
Solid RedStandby Power/Failure

Note: Solid Red Failure indication occurs when there are rapid cycles of power (power-off, power-on, power-off, power-on). This condition can usually be corrected by powering off and waiting 2 minutes before turning the power back on.

Status LED indicator

The Status LED indicator reports the Active or Standby status: Active (green), or Standby (yellow).

LED behaviorDescription
Solid GreenActive
Solid YellowStandby

Activity LED indicator

The purpose of the Activity LED indicator is to indicate traffic going to the CPU for load balancing or other software processing. It is not intended as a substitute for the individual Activity LEDs present on each network interface.

The Activity LED uses hardware inputs as an indication of load balancing activity. On legacy platforms this is driven by a signal from a PHY on an internal Ethernet interface connecting the switch subsystem to the CPU subsystem. It is possible that the Activity LED flickers even when there are no active links on the network interfaces.

LED behaviorDescription
Intermittent YellowActivity on the switch to CPU Ethernet interface

Note: The 8400 platform activity LED illuminates while the system is power cycling, and turns off after the boot process has completed. For more information, refer to: K10161: The Activity LED operation on 8400 platforms.

Alarm LED indicator

A single LED (Alarm) conveys an alert level (warning, error, alert, critical, and emergency). The specific alert condition is communicated by an SNMP trap and a log message. Additionally, the specific alert condition will be indicated on the LCD screen.

Alert level LED behavior

There are 5 alert levels:

Alert LevelLED behavior
0 – WarningSolid Yellow
1 – ErrorBlink Yellow
2 – AlertSolid Red
3 – CriticalSolid Red
4 – EmergencyBlink Red

Alert conditions

Alerts that affect the behavior of the Alarm LED indicator are defined in the /etc/alertd/alert.conf file. The lcdwarn function of an alert definition defines which alerts will modify the Alarm LED indicator.

As an example, the default alertd process conditions in BIG-IP 9.2 are defined in the following table:

DescriptionAlert LevelLED behavior
CPU Temp too high3 – CriticalSolid Red
CPU fan too slow3 – CriticalSolid Red
CPU fan bad3 – CriticalSolid Red
Chassis Temp too high3 – CriticalSolid Red
Chassis Fan bad3 – CriticalSolid Red
Power Supply bad4 – EmergencyBlink Red
Unit going standby0 – WarningSolid Yellow
Unit going Active0 – WarningSolid Yellow
The license validation failed2 – AlertSolid Red
The license has expired2 – AlertSolid Red
Blocking DoS attack2 – AlertSolid Red
Hard disk is failing4 – EmergencyBlink Red

Note: An alert condition is no longer triggered when a node or member has been marked down. For additional information about this functionality, refer to K5486: BIG-IP does not signal an alert condition through the front panel Alarm LED when a node or member is marked down.

F5 BIG-IP平台上的LCD消息说明

This article applies to BIG-IP iSeries hardware platforms.

Description

The LCD panel provides the ability to manage and monitor the unit without attaching a console or network cable. The different sensors that exist in the hardware platform provides information regarding the hardware health of the system by way of messages on the LCD screen. The following tables list messages that can appear on the LCD screen of iSeries platforms.

PSUx Status sensor messages

The PSUx sensor is a discrete sensor based on the Intelligent Platform Management Interface (IPMI) standard sensor type code of 0x8. The sensor indicates various power supply unit (PSU) states.

Alert messageAlert levelAlert nameError codeLog messageTrap OID
PSUx Status presentInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO     012a0045PSU# Status present.1.3.6.1.4.1.3375.2.4.0.190
PSUx Status absentInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO 012a0045PSU# Status absent.1.3.6.1.4.1.3375.2.4.0.190
PSUx Status input lostWarningBIGIP_LIBHAL_AOM_SENSOR_PWR_WARN012a0040PSU# Status input lost.1.3.6.1.4.1.3375.2.4.0.185
PSUx Status input activeInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO012a0045PSU# Status input active.1.3.6.1.4.1.3375.2.4.0.190
N/ANoticeBIGIP_LIBHAL_CHASSIS_PS1_POWERED_ON
BIGIP_LIBHAL_CHASSIS_PS2_POWERED_ON
BIGIP_LIBHAL_CHASSIS_PS3_POWERED_ON
BIGIP_LIBHAL_CHASSIS_PS4_POWERED_ON
BIGIP_LIBHAL_CHASSIS_PS_POWERED_ON
BIGIP_LIBHAL_CHASSIS_PS_IS_POWERED_ON
012a0046
012a0047
012a0048
012a0049
012a0017
012a0019
Chassis power module 1 turned on.
Chassis power module 2 turned on.
Chassis power module 3 turned on.
Chassis power module 4 turned on.
Chassis power module # turned on.
Chassis power module # is on.
.1.3.6.1.4.1.3375.2.4.0.147
N/AWarningBIGIP_LIBHAL_CHASSIS_PS1_POWERED_OFF
BIGIP_LIBHAL_CHASSIS_PS2_POWERED_OFF
BIGIP_LIBHAL_CHASSIS_PS3_POWERED_OFF
BIGIP_LIBHAL_CHASSIS_PS4_POWERED_OFF
BIGIP_LIBHAL_CHASSIS_PS_POWERED_OFF
BIGIP_LIBHAL_CHASSIS_PS_IS_POWERED_OFF
012a0050
012a0051
012a0052
012a0053
012a0018
012a0020
Chassis power module 1 turned off.
Chassis power module 2 turned off.
Chassis power module 3 turned off.
Chassis power module 4 turned off.
Chassis power module # turned off.
Chassis power module # is off.
.1.3.6.1.4.1.3375.2.4.0.148
N/ANoticeBIGIP_LIBHAL_CHASSIS_PS1_ABSENT
BIGIP_LIBHAL_CHASSIS_PS2_ABSENT
BIGIP_LIBHAL_CHASSIS_PS3_ABSENT
BIGIP_LIBHAL_CHASSIS_PS4_ABSENT
BIGIP_LIBHAL_CHASSIS_PS_ABSENT
012a0054
012a0055
012a0056
012a0057
012a0021
Chassis power module 1 absent.
Chassis power module 2 absent.
Chassis power module 3 absent.
Chassis power module 4 absent.
Chassis power module # absent.
.1.3.6.1.4.1.3375.2.4.0.149
Power supplies do not matchCriticalBIGIP_LIBHAL_CHASSIS_PSU_MISMATCH012a0060Power supplies do not match.
PSU #: modelnumber PSU #: modelnumber
N/A
PSUx Status config mismatchCriticalBIGIP_LIBHAL_AOM_SENSOR_PWR_CRIT012a0043PSU# Status config mismatch.1.3.6.1.4.1.3375.2.4.0.188
PSUx Status config matchInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO012a0045PSU# Status config match.1.3.6.1.4.1.3375.2.4.0.190
PSUx Status output lostCriticalBIGIP_LIBHAL_AOM_SENSOR_PWR_CRIT012a0043PSU# Status output lost.1.3.6.1.4.1.3375.2.4.0.188
PSUx Status output activeInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO012a0045PSU# Status output active.1.3.6.1.4.1.3375.2.4.0.190
PSUx Status PSU unidentifiedCriticalBIGIP_LIBHAL_AOM_SENSOR_PWR_CRIT012a0043PSU# Status PSU unidentified.1.3.6.1.4.1.3375.2.4.0.188
PSUx Status identifiedInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO012a0045PSU# Status PSU identified.1.3.6.1.4.1.3375.2.4.0.190

Power Fault sensor messages

The Power Fault sensor is a discrete sensor indicating that a power fault has occurred.

Alert messageAlert levelAlert nameError codeLog messageTrap OID
Power Fault host assertedCriticalBIGIP_LIBHAL_AOM_SENSOR_PWR_CRIT012a0043Power Fault host asserted.1.3.6.1.4.1.3375.2.4.0.188
Power Fault host deassertedInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO012a0045Power Fault host deasserted.1.3.6.1.4.1.3375.2.4.0.190
Power Fault bay X assertedCriticalBIGIP_LIBHAL_AOM_SENSOR_PWR_CRIT012a0043Power Fault bay # asserted.1.3.6.1.4.1.3375.2.4.0.188
Power Fault bay X deassertedInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO012a0045Power Fault bay # deasserted.1.3.6.1.4.1.3375.2.4.0.190
Power Fault switchboard assertedCriticalBIGIP_LIBHAL_AOM_SENSOR_PWR_CRIT012a0043Power Fault switchboard asserted.1.3.6.1.4.1.3375.2.4.0.188
Power Fault switchboard deassertedInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO012a0045Power Fault switchboard deasserted.1.3.6.1.4.1.3375.2.4.0.190
Power Fault HDD x assertedCriticalBIGIP_LIBHAL_AOM_SENSOR_PWR_CRIT012a0043Power Fault HDD # asserted.1.3.6.1.4.1.3375.2.4.0.188
Power Fault HDD x deassertedInfoBIGIP_LIBHAL_AOM_SENSOR_PWR_INFO012a0045Power Fault HDD # deasserted.1.3.6.1.4.1.3375.2.4.0.190

CPU Fault sensor messages

The CPU Fault sensor is a discrete sensor indicating that a CPU fault has occurred.

Alert messageAlert levelAlert nameError codeLog messageTrap OID
CPU Fault CATERR assertedCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025CPU Fault CATERR asserted.1.3.6.1.4.1.3375.2.4.0.170
CPU Fault CATERR deassertedInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027CPU Fault CATERR deasserted.1.3.6.1.4.1.3375.2.4.0.172
CPU Fault THERMTRIP assertedEmergencyBIGIP_LIBHAL_AOM_SENSOR_TEMP_EMERG012a0032CPU Fault THERMTRIP asserted.1.3.6.1.4.1.3375.2.4.0.177
CPU Fault THERMTRIP deassertedInfoBIGIP_LIBHAL_AOM_SENSOR_TEMP_INFO012a0033CPU Fault THERMTRIP deasserted.1.3.6.1.4.1.3375.2.4.0.178
CPU Fault PROCHOT assertedCriticalBIGIP_LIBHAL_AOM_SENSOR_TEMP_CRIT012a0031CPU Fault PROCHOT asserted.1.3.6.1.4.1.3375.2.4.0.176
CPU Fault PROCHOT deassertedInfoBIGIP_LIBHAL_AOM_SENSOR_TEMP_INFO012a0033CPU Fault PROCHOT deasserted.1.3.6.1.4.1.3375.2.4.0.178
CPU Fault FIVR assertedEmergencyBIGIP_LIBHAL_AOM_ALERT_EMERG012a0026CPU Fault FIVR asserted.1.3.6.1.4.1.3375.2.4.0.171
CPU Fault FIVR deassertedInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027CPU Fault FIVR deasserted.1.3.6.1.4.1.3375.2.4.0.172
CPU Fault DIMM Event assertedWarningBIGIP_LIBHAL_AOM_ALERT_WARN012a0022CPU Fault DIMM asserted.1.3.6.1.4.1.3375.2.4.0.167
CPU Fault DIMM Event deassertedInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027CPU Fault DIMM deasserted.1.3.6.1.4.1.3375.2.4.0.172
CPU Fault MEMHOT assertedWarningBIGIP_LIBHAL_AOM_SENSOR_TEMP_WARN012a0028CPU Fault MEMHOT asserted.1.3.6.1.4.1.3375.2.4.0.173
CPU Fault MEMHOT deassertedInfoBIGIP_LIBHAL_AOM_SENSOR_TEMP_INFO012a0033CPU Fault MEMHOT deasserted.1.3.6.1.4.1.3375.2.4.0.178
CPU Fault VR Hot assertedWarningBIGIP_LIBHAL_AOM_SENSOR_TEMP_WARN012a0028CPU Fault VR Hot asserted.1.3.6.1.4.1.3375.2.4.0.173
CPU Fault VR Hot deassertedInfoBIGIP_LIBHAL_AOM_SENSOR_TEMP_INFO012a0033CPU Fault VR Hot deasserted.1.3.6.1.4.1.3375.2.4.0.178
CPU Fault CPU IERR assertedCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025CPU Fault IERR asserted.1.3.6.1.4.1.3375.2.4.0.170
CPU Fault CPU IERR deassertedInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027CPU Fault IERR deasserted.1.3.6.1.4.1.3375.2.4.0.172
CPU Fault CPU MCERR assertedCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025CPU Fault MCERR asserted.1.3.6.1.4.1.3375.2.4.0.170
CPU Fault CPU MCERR deassertedInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027CPU Fault MCERR deasserted.1.3.6.1.4.1.3375.2.4.0.172

Filter sensor messages

The Filter sensor sends an event when the chassis filter needs to be replaced. This is a threshold-based sensor.

Alert messageAlert levelAlert nameError codeLog messageTrap OID
Chassis air filter replacement dueInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027Chassis air filter replacement due.1.3.6.1.4.1.3375.2.4.0.172
Chassis air filter replacement overdueCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025Chassis air filter replacement overdue.1.3.6.1.4.1.3375.2.4.0.170

LCD Health sensor messages

The LCD Health sensor indicates whether or not the BMC can communicate with the LCD.

Alert messageAlert levelAlert nameError codeLog messageTrap OID
LCD Health communication OKInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027LCD Health communication OK.1.3.6.1.4.1.3375.2.4.0.172
LCD Health communication errorCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025LCD Health communication error.1.3.6.1.4.1.3375.2.4.0.170

Module Presence sensor messages

The Module Presence sensor indicates whether or not a module is present.

Alert messageAlert levelAlert nameError codeLog messageTrap OID
fan tray presentInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027fan tray present.1.3.6.1.4.1.3375.2.4.0.172
fan tray absentCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025fan tray absent.1.3.6.1.4.1.3375.2.4.0.170
bay x presentInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027bay # present.1.3.6.1.4.1.3375.2.4.0.172
bay x absentCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025bay # absent.1.3.6.1.4.1.3375.2.4.0.170
switchboard presentInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027switchboard present.1.3.6.1.4.1.3375.2.4.0.172
switchboard absentCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025switchboard absent.1.3.6.1.4.1.3375.2.4.0.170
LCD presentInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027LCD present.1.3.6.1.4.1.3375.2.4.0.172
LCD absentCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025LCD absent.1.3.6.1.4.1.3375.2.4.0.170
CPU 00 presentInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027CPU 00 present.1.3.6.1.4.1.3375.2.4.0.172
CPU 00 absentCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025CPU 00 absent.1.3.6.1.4.1.3375.2.4.0.170
CPU 01 presentInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027CPU 01 present.1.3.6.1.4.1.3375.2.4.0.172
CPU 01 absentCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025CPU 01 absent.1.3.6.1.4.1.3375.2.4.0.170

Leonardo Daughter Card Absent messages

A single general-purpose input/output (GPIO) on Leonardo indicates that the daughter card is absent.

Alert messageAlert levelAlert nameError codeLog messageTrap OID
CM Daughter Card absentCriticalBIGIP_LIBHAL_AOM_ALERT_CRIT012a0025CM Daughter Card absent.1.3.6.1.4.1.3375.2.4.0.170
CM Daughter Card presentInfoBIGIP_LIBHAL_AOM_ALERT_INFO012a0027CM Daughter Card present.1.3.6.1.4.1.3375.2.4.0.172

FIPS Initialization Status messages

The Federal Information Processing Standards (FIPS) Initialization Status sensor tracks the state of the Full Box FIPS Mode initialization for the host application.

Alert messageAlert levelAlert nameError codeLog messageTrap OID
FIPS initialization error assertedWarningBIGIP_LIBHAL_AOM_ALERT_WARN012a0022FIPS initialization error asserted.1.3.6.1.4.1.3375.2.4.0.167
FIPS initialization error deassertedWarningBIGIP_LIBHAL_AOM_ALERT_WARN012a0022FIPS initialization error deasserted.1.3.6.1.4.1.3375.2.4.0.167

RAID Disk Failure messages

The RAID controller on a Dual-SSD system indicates that the member disk is removed from the RAID array.

Alert MessageAlert LevelAlert NameError codeLog messageTrap OID
RAID disk failure.CriticalBIGIP_RAID_DISK_FAILURE0x0Raid#:md#: Disk failure.1.3.6.1.4.1.3375.2.4.0.96

F5远程清除液晶屏和报警指示灯

Topic

You should consider using this procedure under the following condition:

  • You want to remotely clear LCD warnings and the Alarm LED.

Prerequisites

You must meet the following prerequisite to use this procedure:

  • You have command line access to the BIG-IP system.

Description

In some cases, you may want to remotely clear LCD warnings and the Alarm LED. Performing this action may prevent onsite personnel from discovering and reporting an old warning, or having to teach the onsite personnel how to clear the LCD. You can use the lcdwarn command line utility to control the LCD and the Alarm LED. To display its usage, run the lcdwarn command without any arguments.

Note: Starting in BIG-IP 12.1.0, you can use the tmsh show sys alert lcd command to display the list of alerts sent to the LCD front panel display.

Procedures

Clearing LCD warnings

Impact of procedure: Performing the following procedure should not have a negative impact on your system.You can use the lcdwarn command to remotely clear the LCD warnings. To do so, use the following command syntax appropriate for your BIG-IP version:

BIG-IP 12.1.5, BIG-IP 13.1.0 and later

lcdwarn -c <level>

In this command syntax, note the following:

  • <level> specifies the alert level to be cleared. Acceptable values include [0|1|2|3|4|5] or [warning|error|alert|critical|emergency|information]. The level can be seen under the “Priority” column when you run tmsh show sys alert from the Advanced Shell (bash) or show sys alert from within the tmsh shell:

    root@(C3553740-bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos)# show sys alert
    —————————————————————-
    Sys::LCDAlerts
    Slot          Timestamp  Priority         Id         Description
    —————————————————————-
    0     04/22/21 02:21:07      info  0x10c0019  Unit going Active.
    0     04/22/21 01:22:55      info  0x10c0019  Unit going Active.
    0     04/22/21 01:16:28      info  0x10c0019  Unit going Active.
    0     04/22/21 01:16:28      info  0x10c0019  Unit going Active.

For example, to clear LCD warnings with an alert level of 0, type the following command:

lcdwarn -c 0

BIG-IP 13.0.0, BIG-IP 12.1.4 and earlier

lcdwarn -c <level> <slotid>

In this command syntax, note the following:

  • <level> specifies the alert level to be cleared. Acceptable values include [0|1|2|3|4|5] or [warning|error|alert|critical|emergency|information].
  • <slotid> specifies the slot for which warnings should be cleared. Acceptable values include [0|1|2|3|4|5|6|7|8].Note: In BIG-IP 13.0.0, BIG-IP 12.1.4 and earlier, specifying any slot other than 0 is necessary only on the VIPRION platform. On a VIPRION platform, the slot ID is counted from 1, so blade 2 is 2 in the command line.

For example, to clear LCD warnings with an alert level of 0, type the following command:

lcdwarn -c 0 0

On a VIPRION system, to clear LCD warnings with an alert level of 0 for slot 2, type the following command:

lcdwarn -c 0 2


Clearing the Alarm LED

To clear the Alarm LED, you must clear all LCD warnings at all alert levels (on all slots for VIPRION systems). To do so, perform the following single command appropriate for your BIG-IP platform:

Impact of procedure: Performing the following procedure should not have a negative impact on your system.


VIPRION platforms

You can clear all LCD warnings at all alert levels on all VIPRION slots using the following single command:

BIG-IP 12.1.5, BIG-IP 13.1.0 and later

for i in 0 1 2 3 4 5; do lcdwarn -c “${i}”; done

BIG-IP 13.0.0, BIG-IP 12.1.4 and earlier

for i in 0 1 2 3 4 5; do for j in 1 2 3 4 5 6 7 8; do lcdwarn -c “${i}” “${j}”; done; done

If you run this command on a VIPRION system that has unpopulated blade slots, the system logs benign error messages to the /var/log/ltm file that appear similar to the following example:

012a0004:4: ledSet error: LopDev: sendLopCmd: Lopd status: 1 packet: action=2 obj_id=3c sub_obj=0 slot_id=2 result=2 len=0 crc=e071 payload= (error code:0x2)

You can safely ignore this message; it does not affect the traffic processing capability of the VIPRION system.

To prevent this error message on a VIPRION system with unpopulated blade slots, adjust the input values for the j variable. For example, on a VIPRION system where only blade slots 1 and 2 are populated, type the following command:

for i in 0 1 2 3 4 5; do for j in 1 2; do lcdwarn -c “${i}” “${j}”; done; done


BIG-IP iSeries platforms

For information about clearing the Alarm LED on BIG-IP iSeries platforms, refer to K24127736: Clear LCD alarms on iSeries device.


All other BIG-IP platforms (except for VIPRION platforms and BIG-IP iSeries platforms)

You can clear all LCD warnings at all alert levels on all other BIG-IP platforms (except for VIPRION platforms) using the following single command:

BIG-IP 12.1.5, BIG-IP 13.1.0 and later

for i in 0 1 2 3 4 5; do lcdwarn -c “${i}”; done

BIG-IP 13.0.0, BIG-IP 12.1.4 and earlier

for i in 0 1 2 3 4 5; do lcdwarn -c “${i}” 0; done

Note: Running this command on legacy BIG-IP platforms that are not equipped with an LCD (such as the 1000, 2400, 5100, and 5110) only clear the Alarm LED.

F5 液晶屏显示’unit going active’、’unit going standby’的含义

Topic

When a BIG-IP system transitions from active to standby state or standby to active state, a message is displayed on the LCD display indicating the amount of time that has passed since the state transition occurred.

The BIG-IP system transitioning from standby to active displays a message similar to one of the following examples:

xxS unit going active

xxM unit going active

The BIG-IP system transitioning from active to standby displays a message similar to one of the following examples:

xxS unit going standby

xxM unit going standby

In these messages, S or M indicates the units in which time is measured: S indicates seconds, M indicates minutes. The xx characters represent the number of minutes or seconds the device has been in the current state. For example, a device that transitioned to the active state 15 minutes ago displays the following message:

15M unit going active

Note: These messages may appear on standalone systems or on members of a redundant pair.

Note: To determine the cause of an unexpected state change, examine the system log files.