Updated Date: 12/02/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 800 (C114), 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: 800, 1600, 3600, 3900, 6900, 8900, 8950, 11000, 11050, EM 4000.
For information about obtaining, installing, and running the EUD on the BIG-IP BIG-IP 2000 (C112), BIG-IP 4000 (C113), BIG-IP 5000, BIG-IP 7000, and BIG-IP 10000 (D113), please refer to the technical note Field Testing BIG-IP Hardware: 2000, 4000, 5000, 7000, 10000.
For information about obtaining, installing, and running the EUD on the VIPRION 2400 chassis (F100), with VIPRION B2100 blades (A109) or VIPRION B2150 blades (A113), please refer to the technical note Field Testing BIG-IP Hardware: VIPRION B2100/B2150 Blades.
For information about obtaining, installing, and running the EUD on the VIPRION 2400 chassis (F100), with VIPRION B2250 blades (A112), please refer to the technical note Field Testing BIG-IP Hardware: VIPRION B2250 Blades.
For information about obtaining, installing, and running the EUD on the VIPRION 4400 chassis (J100, J101) or VIPRION 4480 chassis (J102, J103), with VIPRION 4100 blades (A100), VIPRION 4100 blades (A105), VIPRION 4200 blades (A107), or VIPRION 4200N blades (A111), please refer to the technical note Field Testing BIG-IP Hardware: VIPRION B4100/B4200 Blades.
For information about obtaining, installing, and running the EUD on the VIPRION 4480 chassis (J102, J103) or VIPRION 4800 chassis (S100, S101), with B4300 blades (A108) or VIPRION B4340 (A110) blade, 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 Field Testing BIG-IP Hardware.
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 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 supports the VIPRION 4800 chassis.
This release adds the following fixes to EUD_C.
|Blade and chassis test summary output for Alarm and Status LEDs||ID 374304||Fixed an issue where it was difficult to determine from the test summary if an error on the LCD test was on the blade or the chassis front bezel. The test summary now clearly distinguishes the difference.|
|EUD Host RTC_BAT is too low||ID 379371||Fixed an issue where a battery voltage error was produced when the battery voltage was within tolerance.|
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 supports the BIG-IP 800 platform.
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_M (12.10.0).|
|HSB reg test fails with unexpected data||ID 385592||Fixed an issue where the HSB reg test failed when running in loops over an extended period of time.|
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 following platforms:
This release adds the following fix to EUD_M.
|EUD 12.8.0||ID 355591, ID 360858||The EUD build number now appears on the LCD instead of EUD build.|
This release includes support for the 8950S platform.
This release supports the 11050 NEBS 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.
This release supports the VIPRION B2150 blade.
This release adds the following fixes to EUD_S.
|USB LCD module operation during LED test||ID 353684||You can now use the USB LCD keypad to answer the questions for the LED test.|
|USB LCD module fails to show EUD version||ID 357170||The USB LCD display now shows the EUD version and status of running tests.|
|LED test and active LEDs||ID 359179||Fixed an issue where the LED test left some LEDs lit.|
|eud.log||ID 360207||EUD System Ram test details are now stored in eud.log.|
|Defective fan tray showing as Passed in EUD||ID 393419||Fixed an issue where a defective fan tray passed EUD tests.|
This release corrects a problem that prevented users from using mkdisk to make bootable media on the VIPRION 2000 (ID 406418).
This release incorporates a new DIMM used in manufacturing (ID 428513, ID 428634, and ID 427881-1) and includes updated AOM firmware.
This release supports the BIG-IP 5000 Series and BIG-IP 7000 Series platforms.
This release supports the BIG-IP 4000s and BIG-IP 10200v platforms.
This release supports a BIG-IP 4200v part revision.
This release corrects an issue with creating a bootable USB thumb drive (ID 359515).
|800, 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.|
|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.|
|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.|
|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.|
|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.|
|Boot message||ID 201293||You might 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?|
|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.|
|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.|
|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.|
|EUD 12.1.0 VIPRION||ID 201964||To run the LCD tests on a VIPRION blade, follow this sequence of steps:
|800, 1600, 3600, 3900, 6900, 8900, EM 4000||ID 289571||The voltage in the CPU used in Moonshot platforms might fluctuate during memory tests. This benign occurrence is due to power saving features built into the CPU.|
|EUD 12.7.1||ID 337565||During the EUD installation you might see the following benign error: /usr/bin/upgrade_rpmdisk: line 41: [: too many arguments.|
|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 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.|
|USB LCD module||ID 359849||After booting to the EUD, a message might 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 starts, 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 starts.|
|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.|
|4100, 4300||ID 367603||On the 4100 and 4300 platforms, the CPLD test fails when one power supply is turned off or unplugged.|
|EUD 12.8||ID 379370||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.|
|B4300 Blade||ID 373478||On the B4300 blade, the Chassis Sensor Report might 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 might 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.|
|EUD 12.9||ID 370118||On BIG-IP 11000, 11050, or 11050N platforms, periodically, the system reports the VDD_NB = 1.23V and reports a Fail, even though the measured voltages have been determined to be within acceptable limits.|
|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.|
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.