Filter
Top Products
Chapter 5 System Controller 5-5
■ 4866668: When the message ’Dynamic FRUID packet discovery failure recovered’
shows in the logs for a blade, it is possible that some fault events will be missing
or only partially described.
This problem can occur if the System Controller is reset immediately after an
event has been reported on the serial console. In other words, it happens if the
System Controller has not completed writing the information to its event logs
when the reset is performed.
To avoid the problem, if you see an event reported on your serial console, wait at
least 30 seconds before executing the resetsc or setfailover command.
■ 4868129: Typing reset -xy sn (where n is the number of a blade slot) resets all
FRUs in a shelf.
The syntax of the above command is correct, but the software does not process it
correctly. The consequence, if you type the command in this way, is that all FRUs
in the chassis will be reset.
To avoid this problem, when you perform an externally initiated reset on a blade
(by using the -x option) and you specifically do not want to receive the
confirmation prompt (the -y option), make sure you separate the arguments as
follows when you type the command:
where n is the number of the slot containing the blade you want to reset.
sc>reset -x -y sn