Last Modified: Apr 19, 2021
See more info
Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 11.6.4, 11.6.5, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 12.1.4, 126.96.36.199, 12.1.5, 188.8.131.52, 184.108.40.206, 220.127.116.11, 12.1.6, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Opened: Mar 04, 2016
When using the bladectl utility to capture a remote blade's console in a VIPRION 4xxx-series chassis, certain chassis-management functions may fail, including: - Controlling Chassis fan speed (which will default to 100% speed in the absence of positive control messages to the contrary) - Ability to update Chassis firmware (Fan tray and Annunciator firmware) - Monitoring of Chassis sensor status (Chassis sensors, fans, power supplies, front-panel annunciator, etc.) - Updating the front-panel display (annunciator)
- Chassis fans may operate at 100% speed - Chassis firmware updates may fail - Chassis sensor readings may fail - The front panel display may not be updated
This may occur if the bladectl utility is being used to capture the console of a remote blade, and then the bladectl utility is used with that remote console to capture yet another remote blade's console. This problem is particularly likely to occur when capturing one remote blade's console, then capturing the original blade's console from the remote console session (loop back to the original blade). This problem may occur at two such levels of indirection when operating within a VIPRION C4800 (8-slot) chassis. It is possible this problem may occur at more than two such levels of indirection when operating within a VIPRION C4400 or C4480 chassis. Capturing a remote console session in a VIPRION 4xxx-series chassis using the bladectl utility causes the remote console traffic to pass over the chassis management backplane (CAN bus) through the Host PICs and SPR (Serial Port Redirector) PICs. This bus and these PICs have limited bandwidth, which can be overwhelmed by such nested/looping console-redirection traffic.
1. If using the bladectl utility to capture a remote blade's console, make sure to exit the remote console session before attempt to access another remote blade's console. 2. Instead of using the bladectl utility to capture a remote blade's console, use one of the following alternatives: a. From the starting blade's console, use SSH to connect to a remote blade's console. For example, from the blade 1 console, use the following command to connect to the blade 2 console: ssh slot2 b. From a serial connection to one blade's serial console port, use the 'C' command from the SPR (Serial Port Redirector) menu to capture a remote blade's console.