OPERATIONAL DEFECT DATABASE
...
...
For BIG-IP appliances: - The 'tmsh show sys hardware' command displays the product name (marketing name) for the appliance in the 'Name' field of the 'Platform' section. - The Platform ID of the appliance is displayed in the 'Type' field of the 'System Information' section. - The 200/400 level part number the appliance is displayed in the 'Level 200/400 Part' field of the 'System Information' section. For example: Platform Name BIG-IP 4200 System Information Type C113 Level 200/400 Part 200-0352-05 REV B For VIPRION 4000-series systems: - The 'tmsh show sys hardware' command displays the product name (marketing name) for the blade in the 'Name' field of the 'Platform' section. - The Platform ID of the blade is displayed in the 'Type' field of the 'System Information' section. - The 200/400 level part number the blade is displayed in the 'Level 200/400 Part' field of the 'System Information' section. For example: Platform Name BIG-IP VPR-B4300 System Information Type A108 Level 200/400 Part 400-0030-00 REV 6 For VIPRION 2000-series systems: - The 'tmsh show sys hardware' command displays the product name (marketing name) for the chassis in the 'Name' field of the 'Platform' section. - The Platform ID of the blade is displayed in the 'Type' field of the 'System Information' section. - The 200/400 level part number the chassis is displayed in the 'Level 200/400 Part' field of the 'System Information' section. For example: Platform Name BIG-IP VPR-C2400 System Information Type A109 Level 200/400 Part 400-0028-08 REV B
- Identification of the blade or chassis is inconsistent between VIPRION 4000-series and VIPRION 2000-series systems. - There is no direct way to identify the chassis in which a VIPRION 4000-series blade is installed.
VIPRION 4000-series and VIPRION 2000-series systems running affected versions of BIG-IP.
To identify the product name of the VIPRION 2000-series blade: Search the AskF5 site for references to the Platform ID displayed by 'tmsh show sys hardware', such as: - K9412: The BIG-IP release matrix (https://support.f5.com/csp/article/K9412) - K4309: F5 platform life cycle support policy, VIPRION Platform Life Cycles (https://support.f5.com/csp/article/K4309#viprion) - K9476: The F5 hardware/software compatibility matrix (https://support.f5.com/csp/article/K9476) - Field Testing BIG-IP Hardware: VIPRION B2000 Series Blades (https://support.f5.com/kb/en-us/products/big-ip_ltm/releasenotes/related/eud-vf.html) To identify the product name of the VIPRION 4000-series chassis: VIPRION C4800 chassis have eight (8) slots, versus four (4) slots for VIPRION C4400/C4480 chassis. A VIPRION C4800 chassis be distinguished from VIPRION C4400/C4480 chassis by examining the number of slots reported by the 'bladectl -v' command, or by the 'Slot Status' section of the 'tmsh show sys hardware' output. VIPRION C4400/C4480 chassis can be distinguished by the "chas_rev" value in the "cpld_stat" table viewable via the "tmctl" command. A chas_rev value of 3 indicates a VIPRION C4800 chassis: # tmctl cpld_stat name board_id board_rev cpld_rev chas_rev chas_id slot_id card_pres_a ------ -------- --------- -------- -------- ------- ------- ----------- 4/cpld 15 15 134 3 1 4 0 A chas_rev value of 2 indicates a VIPRION C4400/C4480 chassis: # tmctl cpld_stat name board_id board_rev cpld_rev chas_rev chas_id slot_id card_pres_a ------ -------- --------- -------- -------- ------- ------- ----------- 2/cpld 15 15 154 2 1 2 0
In the output of the 'tmsh show sys hardware' command, the Blade and Chassis Model Names and Platform IDs are both reported consistently between VIPRION 4000-series and VIPRION 2000-series systems. The Blade Model Name is reported under the Platform section. The Blade Platform ID is reported under the System Information section. The Chassis Model Name and Platform ID are reported under the Chassis Information section.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
