Manual Chapter : Using Additional 4300 Platform

Applies To:

Show Versions Show Versions


  • 7.0.0, 6.1.0, 6.0.3


  • 8.0.0
Manual Chapter
When the unit is in a standard operating state, the LEDs behave in a defined manner. The standard operating states are defined in Table 4.2.
Alerts that cause the indicators to change are defined in the /etc/alertd/alert.conf and /config/user_alert.conf files. You should only edit the /config/user_alert.conf file to add new alerts. The /etc/alertd/alert.conf file defines standard system alerts.
Using a text editor, such as vi or pico, open the file user_alert.conf.
Add the lines shown in Figure 4.1 to the end of the file.
Save the file, and exit the text editor.
The front panel LEDs now indicate when nodes are marked down.
Figure 4.1 The user_alert.conf file
alert BIGIP_MCPD_MCPDERR_POOL_MEMBER_MON_DOWN "Pool member (.*?):(.*?) monitor status down." {
snmptrap OID=".";
lcdwarn description="Node down" priority="1"
alert BIGIP_MCPD_MCPDERR_NODE_ADDRESS_MON_DOWN "Node (.*?) monitor status down." {
snmptrap OID=".";
lcdwarn description="Node address down" priority="1"
Some specific conditions are not included in the definition tables in the /etc/alertd/alert.conf file. These conditions include:
A yellow intermittent Activity LED indicates that host traffic is present. Also, while the kernel is loading, the Activity LED indicator flashes yellow intermittently when the disk is accessed. This condition is normal and occurs only during start up.
When the Activity LED indicator flashes green intermittently, it indicates Ethernet traffic leaving the switch subsystem and going to the CPU subsystem. Because internal traffic might cause this indicator to be active, you may see the Activity indicator flicker green even though there is no external client/server traffic.
When the Status LED indicator is solid yellow or green, it indicates that the system is in a Standby state (yellow) or an Active state (green).
You can perform configuration tasks such as displaying interface status and settings, setting the media type, and setting the duplex mode using the bigpipe command.
When using the bigpipe utility, and a command calls for a list of interfaces, the list may consist of one or more interfaces, with multiple interfaces separated by spaces. For example:
From the command line interface, use the following syntax to display the current status and the settings for all installed interfaces:
Figure 4.2 shows an example of the output you see when you issue this command on an active/standby unit in active mode.
Figure 4.2 The bigpipe interface show command output
You may specify a media type or use auto for automatic detection.
Use auto for automatic selection.
All interfaces on the 4300 platform default to auto-negotiate speed and duplex settings. We recommend that you configure any network equipment that you plan to use with the BIG-IP® system to auto-negotiate speed and duplex settings. If you connect the BIG-IP® system to network devices with forced speed and duplex settings, you must also force the speed and duplex settings of the BIG-IP® system to match the settings of the other network device.
Warning: If the BIG-IP® system is attempting to auto-negotiate interface settings with an interface that has the speed and duplex settings forced, you will experience severe performance degradation.
You can set duplex mode to full or half duplex. If the media type does not accept the duplex mode setting, a message indicates this. If media type is set to auto, or if the interface does not accept the duplex mode setting, the duplex setting is not saved to the /config/bigip_base.conf file.