Updated Date: 05/17/2013
This release note documents the following End-User Diagnostics (EUD) packages:
This release supports the following platforms:
If you are unsure which platform you have, you can look at the front of the chassis or the rear of the chassis for the platform number.
For information about obtaining, installing, and running the EUD on BIG-IP 1600 (C102), BIG-IP 3600 (C103), BIG-IP 3900 (C106), BIG-IP 6900 (D104), BIG-IP 8900 (D106), BIG-IP 8950 (D107), BIG-IP 11000 (E101), BIG-IP 11050 (E102), and Enterprise Manager 4000 platforms, please refer to the technical note Field Testing BIG-IP Hardware: 1600, 3600, 3900, 6900, 8900, 8950, 11000, 11050, EM 4000.
For information about obtaining, installing, and running the EUD on the BIG-IP 2000s (C112), BIG-IP 2200s (C112), BIG-IP 4200v (C113), 10200v (D113), please refer to the technical note Field Testing BIG-IP Hardware: 2000s/2200s/4000s/4200v/10200v.
For information about obtaining, installing, and running the EUD on the VIPRION B4300 blade (A108) in a VIPRION 4400 (J100/J101), 4480 (J102) or 4800 (S100) chassis, please refer to the technical note Field Testing BIG-IP Hardware: VIPRION B4300 Blades.
For information about obtaining, installing, and running the EUD on BIG-IP 1500 (C36), BIG-IP 3400 (C62), BIG-IP 3410 (C100), BIG-IP 4100 (D46), BIG-IP 6400 (D63), BIG-IP 6800 (D68), BIG-IP 8400 (D84), BIG-IP 8800 (D88), Enterprise Manager 500, and Secure Access Manager 4300, please refer to the technical note EUD 11.4.0 Field Testing BIG-IP Hardware.
For information about obtaining, installing, and running the EUD on the VIPRION 2400 chassis (F100), VIPRION 2100 blade (A109), please refer to the technical note Field Testing BIG-IP Hardware: VIPRION 2000 Series.
For information about obtaining, installing, and running the EUD on the VIPRION 4400 chassis (J100, J101), VIPRION 4100 blade (A100), VIPRION 4100 blade (A105), VIPRION 4200 blade (A107), or VIPRION 4200 blade (A111), please refer to the technical note Field Testing BIG-IP Hardware: VIPRION 4000 Series.
For information about obtaining, installing, and running the EUD on the Enterprise Manager 3000, WANJet 300, WANJet 500, and WebAccelerator 4500, please refer to the technical note EUD 10.4.0 Field Testing Enterprise Manager, WANJet, and WebAccelerator Hardware.
For platforms running BIG-IP versions 9.3.1 and earlier, we recommend running this version of the end-user diagnostic (EUD) from a USB CD-ROM as described in the installation notes.
This release adds the following fixes to EUD M.
|EUD installs on a platform that is not supported||ID 336730||Corrected a problem where EUD versions intended for older platforms could be installed on newer platforms.|
|Memory test bridging loop||ID 375510||Corrected a problem that could cause a bridging loop when running EUD tests with the previous version of EUD (12.10.0).|
This release supports a BIG-IP 4000s and BIG-IP 10200v platforms.
This release corrects a problem that prevented users from using mkdisk to make bootable media on the VIPRION 2000 (ID 406418).
This release corrects how the test summary is displayed. The test summary now clearly distinguishes if an error on the LED test was for the blade or the chassis front bezel (ID 378304).
This release corrects the acceptable measurement limits on a certain voltage limit on the 11000 and 11050 platforms (ID 381354).
This release includes support for the VIPRION B4300 blade.
This release includes support for the following platforms:
This release includes support for the VIPRION 2400 chassis and blades.
This release includes support for the 8950S platform.
This release supports the PB200N VIPRION blade platform.
This release includes hard drive firmware updates for the 3900 and EM4000 platforms that correct issues resulting either in extraneous errors being reported to the host or in command timeouts being seen by the host. Use the "Hard Drive Firmware Update" menu item <24> to update the firmware.
|B4300 Blade||ID 373478||On the B4300 blade, the Chassis Sensor Report may display the following benign message: Unknown (device busy). If you see this message we recommend you run the test again.|
|B4300 Blade||ID 374731||On the B4300 blade, error messages or failed tests may occur when running any chassis test. In such a case we recommend you remove all blades except the blade you are using to run EUD, cycle power, and boot directly to the EUD and run the chassis test again.|
|B4300 Blade||ID 378288||On the B4300 blade, the SFP/SFP+ test enables the front ports for a brief moment. This allows the test to read the contents of the optics.|
|B4300 Blade||ID 378486||On the B4300 blade, the Chassis Report may fail due to the following error: ERROR: failed to read LCD Firmware Version. If you see this message we recommend you run the test again.|
|B4300 Blade||ID 379371, ID 379369||On the B4300 blade, the Sensor Report may produce the following error: ERROR: Host RTC_BAT is too low. The battery voltage appears in the parentheses following the message. If the battery voltage is between 2.7 and 3.4 volts, please disregard this message. The battery is within tolerance and the message is benign.|
|B4300 Blade||ID 381735||While booted to EUD, with optics installed, and fiber connections exist, the 10G and 40G ports' LNK LED becomes erroneously asserted during the test.|
|4100, 4300||ID 367603||On the 4100 and 4300 platforms, the CPLD test fails when one power supply is turned off or unplugged.|
|EUD Hard Drive Firmware||ID 365218||After you initiate the EUD Hard Drive Firmware Update the following question is presented: Are you certain that you want to download firmware to the disk drives listed above? (Type 'Y' or 'N' and press ENTER). This question is automatically answered Yes. You should ignore this question and allow the update to proceed.|
|EUD 11.2 and later on the 3400||ID 347202||EUD versions 11.2 and later on the 3400 platform. The EUD versions 11.2 and later are not supported on the 3400 platform if the platform is running BIG-IP 10.0.1 and below with BIOS version 0 Ref F. If the BIOS is a higher version, you can run the latest EUD. You can find the BIOS version using the process described in SOL7119: Displaying BIOS version information for BIG-IP systems.|
|LED test||ID 359179||The LED test may leave some LEDs lit. This is benign and does not affect the functionality of the hardware.|
|USB LCD module||ID 353684||You cannot use the USB LCD keypad to answer the questions for the LED test. If you are using a USB LCD to run the EUD tests, you must run the LED tests from a console.|
|USB LCD module||ID 357170||When booting the EUD with the USB LCD attached, the EUD version information is not displayed.|
|EUD 12.9||ID 379370||On BIG-IP 11000, 11050, or 11050N platforms, periodically, the system reports the VDD_NB = 1.23V, and report a Fail, even though the measured voltages have been determined to be within acceptable limits.|
|EUD 12.9||ID 370118||The EUD eventually reboots the system if individual tests are run multiple times without a reboot. Each EUD test calls an individual test package which includes initial set up for dedicated testing components. Test results might be affected by running tests many times in a row without reboot.|
|EUD 12.8.1||ID 367075||If you run the System Report with a power cable removed from one PSU, the system reports failures on both power sources. You can get correct data from running the Sensor Test.|
|EUD 12.8.0||ID 360858||EUD build appears on the LCD instead of the EUD version information.|
|USB LCD module||ID 359849||After booting to the EUD a message may be displayed on the USB LCD module prompting the user to connect to the cluster primary. This message can be ignored. When the EUD LCD test is started the message is removed. This is a default message that occurs on the LCD module if the BIG-IP system detects that the blade is not the primary. Therefore if a blade that was primary is rebooted to the EUD it loses the primary status causing the message to display. The EUD clears the message after the LCD test is started.|
|EUD 12.1.0 VIPRION||ID 201964||In order to run the LCD tests on a VIPRION blade, follow this sequence of steps:
|EUD 12.7.1||ID 337831||The Mezzanine Packet Test is not displayed in the results when you choose the Run all tests options A, F, or N.|
|EUD 12.7.1||ID 337565||During the EUD installation you may see the following benign error: /usr/bin/upgrade_rpmdisk: line 41: [: too many arguments.|
|EUD 12.7||ID 201515||Some terminal emulators, such as TeraTerm, do not display the color red when an error or failure occurs. To correct this problem change the settings for the terminal emulator to Full Color.|
|6900 and 8900||ID 201413||During IM package installation on the 6900 and 8900 platforms you may see the following benign error messages: error: close request on non-existent handle. warning: boot entry st.eud does not exist. Handle to cpmirror.dat.share was never released.|
|WA4500, EM3000, WANJet 300 and 500||ID 201389||On the WA4500, EM3000, WANJet 300 and 500 platforms, the EUD banner is not stored in the eud.log file. F5 Networks recommends that you capture the EUD output from your session.|
|Boot message||ID 201293||You may see the following harmless error message when you boot the EUD: hub 1-0:1.0: Cannot enable port 3. Maybe the USB cable is bad?|
|3900, 6900, 8900||ID 201215||During the SMART test the following harmless messages may appear: /dev/sdc was not found and will not be tested. /dev/sdd was not found and will not be tested.|
|eud.log||ID 360207||When you run the System RAM Test, multiple lines of data show in the console. This data appears only on the console. The system does not store it in eud.log.|
|eud.log on version 9.4.7 and 9.4.8 partitions||ID 201052||The EUD cannot save the eud.log to the file system of a system downgraded from BIG-IP version 10.0.x to BIG-IP version 9.4.7 or 9.4.8. We recommend that you capture the EUD output from your session to save a history of the EUD tests you run.|
|mkdisk||ID 200984||Some Linux distributions attempt to automatically mount a USB mass storage device. This may cause the mkdisk utility to fail to mount the device correctly. If this happens you can use mkdisk to create an EUD USB mass storage device from a BIG-IP system.|
|1500||ID 200890||The EUD menu may not appear when you attempt to start the EUD from the boot menu on systems running BIG-IP version 9.4.7. You can work around this problem by installing the latest IM version of the EUD or running the EUD from a USB thumb drive or CD-ROM.|
|1600, 3600, 6900, 8900||Options to run all tests with USB mass storage device||When you use the options A, F, or N to run all tests any USB mass storage device inserted in the system is not displayed at the start of the test. This is a cosmetic issue and does not affect the performance of the tests.|
|1600, 3600, 3900, 6900, 8900, EM 4000||ID 289571||The voltage in the CPU used in Moonshot platforms may fluctuate during memory tests. This benign occurrence is due to power saving features built into the CPU.|
|EM 4000||ID 359418||To make a bootable thumbdrive for the EM 4000, choose 'BIG-IP 3900' from the platform-selection menu in mkdisk.|
For additional information, please visit http://www.f5.com.
You can find additional support resources and technical documentation through a variety of sources.
Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.
AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
The F5 DevCentral community helps you get more from F5 products and technologies. You can connect with user groups, learn about the latest F5 tools, and discuss F5 products and technology.