Applies To:

Show Versions Show Versions

Manual Chapter: Using Additional VIPRION Functionality
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

The VIPRION platform has LED displays in two locations: on the LCD panel and on the individual blades. On the LCD panel, the LEDs provide information regarding platform power, blade alarms, and status. On the blades, the LEDs provide information on whether the blade is a primary or secondary blade. The LEDs also show alarm and blade status.
There are several types of LED indicators on the faceplate of each unit. Each LED indicator serves a specific function. The LED indicator functions are defined in Tables 4.1, which shows chassis LED functions, and 4.2, which shows blade LED indicator functions.
The chassis front panel has one LED per power supply. There are eight power supply LEDs; however, only the first four are functional in the 4-slot chassis. The LEDs report that a power supply is present and operational (green), present but non-functioning (yellow), or does not have a power supply connected (off).
Reports the overall state of the chassis: function (green) or experiencing errors (yellow).
Reports both blade and chassis alarms. If a blade indicates an alarm condition, the chassis Alarm LED mirrors that state. In situations where more than one blade is generating an alarm, the chassis Alarm LED displays the most severe alarm status.
Reports a non-specific alert level. Use SNMP traps, system logs, or the LCD display for more information.
When the platform is in a standard operating state, the LEDs behave in a defined manner. The standard operating states are defined in Table 4.4, which shows the standard operating states of the VIPRION chassis, and Table 4.5, which shows the states of the LEDs on the blades.
On power up, the status LED of each blade turns yellow. When the BIG-IP® software successfully boots, the status then changes to green.
When there is an alert condition on the platform, the Alarm LED behaves in a specific manner. Table 4.6 lists the type of alarm and the corresponding LED behavior.
Alerts that cause the indicators to change are defined in the /etc/alertd/alert.conf file and /config/user_alert.conf files on the BIG-IP system. You should only edit the /config/user_alert.conf file to add new alerts. The /etc/alertd/alert.conf 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.
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"
Figure 4.1 Adding node status to the user_alert.conf file
This section includes some specific conditions that are not covered 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 platform is in a Standby state (yellow) or an Active state (green).
The blades each have a set of twelve SFP connector optic interfaces, a set of eight RJ45 10/100/1000 copper interfaces, and two 10GbE XFP optic interfaces that are connected internally. Each set of interfaces is numbered from 2.1 through 2.12. It is important to note some facts about these interfaces:
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 platform in active mode.
You may specify a media type or use auto for automatic detection.
Use auto for automatic selection.
All interfaces on the VIPRION system default to auto-negotiate speed and duplex settings. We recommend that you configure any network equipment that you plan to use with the VIPRION system to auto-negotiate speed and duplex settings. If you connect the platform to network devices with forced speed and duplex settings, you must also force the speed and duplex settings of the platform to match the settings of the other network device.
Warning: If the platform is attempting to auto-negotiate interface settings with an interface that has the speed and duplex settings forced, you may 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, an onscreen 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.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?

NOTE: Please do not provide personal information.

Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)